Nimble Storage Systems
Nimble storage systems are discovered using the Nimble REST API. When a Nimble REST API discovery of an IP address finds a storage entity, a Storage Device node representing the chassis is created. The creation or confirmation of the Storage Device node triggers the Nimble Storage Systems pattern. The storage discovery pattern continues the discovery of the storage entity using further Nimble REST API requests to discover the associated storage components. Once discovered, the storage entities are modelled in BMC Discovery.
Supported Platforms
Nimble storage systems OS v.2.3 to 5.0.x.
Prerequisites
Global requirements
- BMC Discovery 11.3 or higher.
- The array must be running OS 2.3 to 5.0.x.
- The array must be installed, configured and reachable from the API client through its fully qualified domain name (FQDN) or array management IP address.
Connectivity requirements
Login Path
The Login Path field should be left as is if no changes were made on Nimble storage API side.
The field value (/v1/tokens) is not a login path but instead it is a token resource (to obtain a token for Rest API Authentication) on the Nimble storage API. This path is configurable on different versions of Nimble storage and hence left as a configurable option. It is recommended to use the default path. Contact your Nimble Storage vendor if the default path does not work and update the credential.
Credentials and Access Protocols
Valid credentials for the storage system IP address should be configured as Nimble Storage Web API:
- REST API: Use a username and password that allow successful login to the Nimble Management Interface over HTTPS/HTTP. These credentials are used during the initial heuristics for creation of the Nimble Storage Device. During the scanning phase of endpoint, Discovery performs a simple GET request on the target IP with ports 80/443 to get information from the login page of the Nimble Management Interface. The heuristic plugin analyzes the data on the received page to verify if it is a Nimble system or not. If the device page recognizes the heuristic plugin then it continues to collect extra information like OS version, vendor, serial etc., and creates a Nimble Storage device when they are collected successfully.
- Web_nimble_auth-https-5392: When the Storage device is successfully created, the Storage pattern is triggered as a part of the Nimble Storage System discovery. The pattern uses the Login Path to request tokens and uses the port 5392 via Rest API for further scanning and continues to create the Storage System node and discover all the associated Storage components.
Port Configuration
Port 80/443 (depending upon the Group Management GUI Login page access via HTTP/HTTPS) and port 5392 for Nimble Rest API to be open on the array. As per the vendor documentation the Port 80 would be redirected to 443, so validate the Management Interface access over HTTPS connection (see https://infosight.hpe.com/InfoSight/media/cms/active/public/pubs_GUI_Administration_Guide_NOS_50x.whz/sfe1501525261102.html for details).
Vendor Specific Information
No known vendor specific information.
Discovered Storage Information
Nimble Flash Storage Systems Discovered Information
Limitations
Pattern available with BMC Discovery 11.3 and higher only. See BMC Discovery 11.3 Release notes and notices for details.
Documentation Links