Fujitsu Eternus

Application Version and Upgrade Details

Introduction

Eternus storage systems is a family of compatible all flash and hybrid storage systems. Eternus AF all flash arrays offer practically unlimited storage performance. Eternus DX hybrid storage systems are designed to store large amounts of unstructured data using cost efficient hard disk capacities while allowing fast access via SSDs. Eternus AF and Eternus DX offer an outstanding family of systems that allow the digital world to achieve the ideal balance between cost , capacity and speed.

Key Use cases

Discovery Use cases

The device discovery enables customers with an unified way of showing all of the elements making up a Eternus storage device along with the relationships.

Monitoring Use cases

The device monitoring helps to collect the metric values with respect to time and sends alerts to the intended customer team to act up immediately in case of any threshold breach or unexpected metric behavior observed based on configurations. In a way it helps the customer with smooth functioning of business with minimal or zero downtime in case of any infrastructure related issues occurring.

Prerequisites

• OpsRamp Classic Gateway 14.0.0 and above.
• OpsRamp NextGen Gateway 14.0.0 and above.
  Note: OpsRamp recommends using the latest Gateway version for full coverage of recent bug fixes, enhancements, etc.

Hierarchy of Eternus Storage

   Eternus Storage
        - Controller enclosure
        - Front-end enclosure
        - Drive enclosure
        - Disk drive
        - RAID Groups
        - Volume
        - Pool

Supported Metrics

Default Monitoring Configurations

Eternus has a default Global Device Management Policies, Global Templates, Global Monitors and Global Metrics in OpsRamp. Users can customize these default monitoring configurations as per your business use cases by cloning respective Global Templates and Global Device Management Policies. OpsRamp recommends doing this activity before installing the app to avoid noise alerts and data.

1. Default Global Device Management Policies

   OpsRamp has a Global Device Management Policy for each Native Type of Eternus. You 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: eternus Eternus Storage - 1 (i.e, appName = eternus, nativeType = Eternus Storage, version = 1)

2. Default Global Templates

   OpsRamp has a Global Template for each Native Type of Eternus. You 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: eternus Eternus Storage Template - 1 (i.e, appName = eternus, nativeType = Eternus Storage, version = 1)

3. Default Global Monitors

   OpsRamp will have a Global Monitors for each Native Type which has monitoring support. You 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: Eternus Storage Monitor eternus Eternus Storage 1(i.e, monitorKey = Eternus Storage Monitor, appName = eternus, nativeType = Eternus Storage, version = 1)

Configure and Install the Fujitsu ETERNUS Integration

1. From All Clients, select a client.
2. Go to Setup > Account.
3. Select the Integrations and Apps tab.
4. The Installed Integrations page, where all the installed applications are displayed.
   Note: If there are no installed applications, it will navigate to the Available Integrations and Apps page.
5. 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.

6. Click ADD in the Fujitsu ETERNUS tile.
7. In the Configurations page, click + ADD. The Add Configuration page appears.
8. Enter the below mentioned BASIC INFORMATION:

Notes:

• Eternus IP Address/Host Name and Eternus SSH Port should be accessible from Gateway.
• App Failure Notifications: if turned on, you will be notified in case of an application failure that is, Connectivity Exception, Authentication Exception.

9. 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).

10. 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.
11. In the DISCOVERY SCHEDULE section, select Recurrence Pattern to add one of the following patterns:
    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly
12. 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.

13. Under the ADVANCED SETTINGS, Select the Bypass Resource Reconciliation option, if you wish to bypass resource reconciliation when encountering the same resources discovered by multiple applications.

    Note: If two different applications provide identical discovery attributes, two separate resources will be generated with those respective attributes from the individual discoveries.

14. Click NEXT.

15. (Optional) Click +ADD to create a new collector by providing a name or use the pre-populated name.

16. Select an existing registered profile.

17. Click FINISH.

The application is 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 Fujitsu ETERNUS application.

View the Fujitsu Eternus details

The Fujitsu Eternus integration is displayed in the Infrastructure > Resources > Storage. You can navigate to the Attributes tab to view the discovery details, and the Metrics tab to view the metric details for Fujitsu Eternus.

Resource Filter Input 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:

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 existed critical alert is recovered.
• OpsRamp has validated this application with an Eternus model which has product code as “ET203 BU” and product name as “Eternus DX200 S3” which belongs to the product family of “Eternus DX.
• Support for Macro replacement for threshold breach alerts (i.e, customisation for threshold breach alert’s subject, description).
• No support of showing activity logs.
• The Template Applied Time will only be displayed if the collector profile (Classic and NextGen Gateway) is version 18.1.0 or higher.
• Application is not compatible with Cluster Gateway.
• This application supports both Classic Gateway and NextGen Gateway.

Troubleshooting

Before troubleshooting, ensure all prerequisites prerequisites are met.

If Fujitsu Eternus integrations fail to discover or monitor, troubleshoot using the following steps:

• If there is an error or alert related to the end device connectivity or authentication, try checking the reachability of the end device from the gateway with the following commands:
  • to ping the IP address provided in the configuration: {ping <IP Address>}
  • to try telnet: {telnet <IP Adress> <Port>}
  • to try SSH to an end device from a gateway: {ssh <username>@<IP Address>}
  • To run a SSH command:

    • Prepare the request payload by using below sample request:

      { “apiVersion”: “debug/v1”, “module”: “Debug”, “app”: “eternus”, “action”: “Reachability”, “payload”: { “ipAddressOrHostName”: “”, “protocol”: “https”, “port”: 443, “requestPath”: “”,

      “version”:“v1”,

      “requestMethod”:"<get/post>”, “userName”: “”, “password”: “” } }

    • Encode the request payload to base64

    • Log in to the gateway concole and connect to the GCLI terminal using the below command: {## gcli}

    • Run the command using the previously generated base64 encoded string {## sdkappdebug <base64 encoded string>}