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.
Supported Target Versions
- Hitachi NAS Platform 4040, 4100 and 4060.
- Firmware version of HNAS Server should be greater than 12.4.
- Complete discovery support requires Gateway version 15.0.0 or above.
Version History
| Application Version | Bug fixes / Enhancements |
|---|---|
| 3.1.0 | This implementation introduces third-party CI alert mapping and OpsQL-based enhancements.Configure alert mappings to target CI systems through the application configuration. After configuration, the system automatically forwards alerts to the corresponding third-party platforms and maps them to the specified CIs, ensuring consistent integration and efficient alert management.Previously, resource filters in the app configuration required manual entry of resource core and custom attributes. With this enhancement, the configuration is moved to OpsQL-based filtering, where users can see the keys auto-populated as needed. |
| 3.0.2 | Resolved an issue with Volume Quota metrics. |
| 3.0.1 |
|
| 3.0.0 | API statistics, metric labels and API timeouts. |