Hitachi NAS

Introduction

Hitachi Network attached Storage (HNAS) storage systems are discovered via an SNMP agent that can be configured using the embedded System Management Unit (SMU). When an SNMP discovery finds a HNAS server’s IP address, a Storage Device node representing whether a Cluster or a HNAS Standalone Server is created. The creation or confirmation of the Storage Device node triggers the appropriate storage discovery pattern. The storage discovery pattern continues discovery of the storage entity using further SNMP requests to discover the associated storage components. Once discovered, the storage entities are modeled in BMC Discovery.

OpsRamp integrates with HNAS using REST APIs exposed through HNAS gateways.

Key Use cases

Discovery Use cases

• It discovers the Hitachi HNAS Storage device.

                 • Hitachi NAS File Device
                         •Hitachi NAS Nodes(Component-of file device)
                         •Hitachi NAS VirtualServers(component-of file device)
                         •Hitachi NAS Storage Pools(Component-of file device)
                                Hitachi NAS File Systems-(Component of Storage pools)
                         • Hitachi NAS System Drives(Component-of file device)

Monitoring Use cases

• Provides metrics related to storage management components and storage server statistics.
• Concern alerts will be generated for each metric to notify the administrator regarding the issue with the resource.

Prerequisites

• OpsRamp Classic Gateway 13.0.1 and above.
• OpsRamp gateway version should be 14.0.0 or above.

Application migration

1. Check for the gateway version as a prerequisite step - classic gateway-12.0.1 and above.
   Notes:
   • You only have to follow these steps when you want to migrate from sdk 1.0 to sdk 2.0.
   • For the first time installation below steps are not required.
2. Disable all configurations associated with sdk 1.0 adaptor integration application.
3. Install and Add the configuration to that sdk 2.0 application.
   Note: refer to Configure and install the integration & View the Hitachi NAS details sections of this document.
4. Once all discoveries are completed with the sdk 2.0 application, follow any one of the approaches.

   • Direct uninstallation of the sdk 1.0 adaptor application through the uninstall API with skipDeleteResources=true in the DELETE request.

     End-Point: https://{{host}}/api/v2/tenants/{tenantId}/integrations/installed/{installedIntgId}

     Request Body:

         {
         "uninstallReason": "Test",
         "skipDeleteResources": true
         }

     
     
     (OR)
     
     

   • Delete the configuration one by one through the Delete adaptor config API with the request parameter as skipDeleteResources=true in the DELETE request.

     End-Point: https://{{host}}/api/v2/tenants/{tenantId}/integrations/installed/config/{configId}?skipDeleteResources=true.

   • Finally, uninstall the adapter application through API with skipDeleteResources=true in the DELETE request.

     End-Point: https://{{host}}/api/v2/tenants/{tenantId}/integrations/installed/{installedIntgId}

     Request Body:

             {
         "uninstallReason": "Test",
         "skipDeleteResources": true
     }

     
     

Default Monitoring Configurations

Hitachi NASs has default Global Device Management Policies, Global Templates, Global Monitors and Global metrics in OpsRamp. You can customize these default monitoring configurations as per your business use cases by cloning respective global templates and global Device Management Policies. OpsRamp recommends performing the below activity before installing the application to avoid noise alerts and data.

1. Default Global Device Management Policies

   OpsRamp has a Global Device Management Policy for each Native Type of Hitachi Nas .We can find those Device Management Policies at Setup -> Resources -> Device Management Policies, search with suggested names in global scope. Each Device Management Policy follows below naming convention:

   {appName nativeType - version}

   Ex: hitachi-nas Hitachi NAS File Device- 2(i.e, appName = hitachi-nas, nativeType =Hitachi NAS File Device, version = 2)

2. Default Global Templates

   OpsRamp has a Global template for each Native Type of hitachi-nas. We can find those templates at Setup -> Monitoring -> Templates, search with suggested names in global scope. Each template follows below naming convention:

   {appName nativeType 'Template' - version}

   Ex: hitachi-nas Hitachi NAS File Device Template - 2 (i.e, appName = hitachi-nas, nativeType = Hitachi NAS File Device, version = 2)

3. Default Global Monitors

   OpsRamp has a Global Monitors for each Native Type which has monitoring support. We can find those monitors at Setup -> Monitoring -> Monitors, search with suggested names in global scope. Each Monitors follows below naming convention:

   {monitorKey appName nativeType - version}

   Ex: Hitachi NAS File Device Monitor hitachi-nas Hitachi NAS File Device 2 (i.e, monitorKey = Hitachi NAS File Device Monitor, appName = hitachi-nas, nativeType = Hitachi NAS File Device, version = 2)

Configure and install the integration

1. From All Clients, select a client.
2. Go to Setup > Integrations and Apps.
3. The INSTALLED INTEGRATIONS page, where all the installed applications are displayed.
   Note: If there are no installed applications, it will navigate to the ADD APP page.

4. Click + ADD on the INSTALLED INTEGRATIONS page. The AVAILABLE INTEGRATIONS AND APPS page displays all the available applications along with the newly created application with the version.
   Note: You can even search for the application using the search option available. Also you can use the All Categories option to search.

5. Click ADD in the Hitachi NAS application.
6. In the Configurations page, click + ADD. The Add Configuration page appears.
7. Enter the below mentioned BASIC INFORMATION:

Notes:

• By default the Is Secure checkbox is selected.
• Select the following:
  • App Failure Notifications: if turned on, you will be notified in case of an application failure that is, Connectivity Exception, Authentication Exception.

8. Select the below mentioned CUSTOM ATTRIBUTE:

Note: The custom attribute that you add here will be assigned to all the resources that are created by the integration. You can add a maximum of five custom attributes (key and value pair).

9. In the RESOURCE TYPE section, select:
   • ALL: All the existing and future resources will be discovered.
   • SELECT: You can select one or multiple resources to be discovered.
10. In the DISCOVERY SCHEDULE section, select Recurrence Pattern to add one of the following patterns:
    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly
11. Click ADD.

Now the configuration is saved and displayed on the configurations page after you save it.
Note: From the same page, you may Edit and Remove the created configuration.

12. Click NEXT.
13. In the Installation page, select an existing registered gateway profile, and click FINISH.

14. Below are the optional steps you can perform on the Installing page.
    • Under the ADVANCED SETTINGS, select the Bypass Resource Reconciliation checkbox.
      Note: To Bypass Resource Reconciliation for the same resource discovered by multiple applications, two separate resources will be created with their respective attributes from the individual discoveries.

• Click +ADD to create a new collector by providing a name or use the pre-populated name.

15. Select an existing registered profile.

16. Click FINISH.

    The integration is now installed and displayed on the Installed Integration page. Use the search field to find the installed integration.

Modify the Configuration

• See Modify an Installed Integration or Application article.

  Note: Select the Hitachi NAS application.

View the Hitachi NAS details

The Hitachi NAS integration is displayed in the Infrastructure >Search > Storage Arrays > Hitachi-Nas. You can navigate to the Attributes tab to view the discovery details, and the Metrics tab to view the metric details for Hitachi NAS.

Resource Filter Input Keys

Hitachi NAS application resources are filtered and discovered based on below keys:

Supported Alert Custom Macros

Customize the alert subject and description with below macros then it will generate alert based on customisation.
Supported macros keys:

                                ${resource.name}

                                ${resource.ip}

                                ${resource.mac}

                                ${resource.aliasname}

                                ${resource.os}

                                ${resource.type}

                                ${resource.dnsname}

                                ${resource.alternateip}

                                ${resource.make}

                                ${resource.model}

                                ${resource.serialnumber}

                                ${resource.systemId}

                                ${Custome Attributes in the resource}

                                ${parent.resource.name}

Supported metrics

Risks, Limitations & Assumptions

• Application can handle Critical/Recovery failure notifications for below two cases when user enables App Failure Notifications in configuration:
  • Connectivity Exception
  • Authentication Exception
• Application will not send any duplicate/repeat failure alert notification until the already existing critical alert is recovered.
• Using metrics for monitoring the resources and generating alerts when the threshold values are breached.
• Application cannot control monitoring pause/resume actions based on above alerts.
• This application supports only Classic Gateway and NextGen Gateway. Not supported with Cluster Gateway.
• Component level thresholds can be configured on each resource level.
• No support of showing activity log and applied time.
• The minimum support version for the option to get Latest snapshot metric is nextgen-14.0.0.
• Full discovery Support requires gateway version 15.0.0 or above.
• Alerts generated for metrics that are configured as per defined integration.