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.
The following helps you get started.
- To explore monitored metrics, see Supported Metrics and Default Monitoring Configuration.
- To verify prerequisites and configure, see Working with Fujitsu Eternus.
Key Use cases
Discovery Use cases
- Discovers all the high-level components such as Eternus Storage, Eternus Controller Enclosure, Eternus Frontend Enclosure, Eternus Drive Enclosure, Eternus Disk Drive, Eternus RAID Group, Eternus Volume, and Eternus Pool
- Publishes relationships between resources to enable a topological view and simplify maintenance
- Refer to the Resource Hierarchy for detailed structure.
Monitoring Use cases
- Provides monitoring related to availability, thermal, performance and usage.
- Alerts are generated when defined metric thresholds are breached, notifying users of potential issues.
- Refer to the Supported Metrics and Default Monitoring Configuration for complete details.
Supported Target Versions
- CLI commands used in the application are valid for all Eternus storage models.
- Tested on an Eternus model with product code “ET203 BU” with product name “Eternus DX200 S3” which belongs to the “Eternus DX” product family.
Resource Hierarchy
- Eternus Storage
- Eternus Controller Enclosure
- Eternus Frontend Enclosure
- Eternus Drive Enclosure
- Eternus Disk Drive
- Eternus RAID Group
- Eternus Volume
- Eternus Pool
Version History
| Application Version | Bug fixes / Enhancements |
|---|---|
| 1.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. |
| 1.0.8 |
|
| 1.0.7 | Metric data point conversion changes |
| 1.0.6 |
|
| 1.0.5 | Added support for NativeType Display order changes and resource grouping by type in UI. |
Click here to view the earlier version updates
| Application Version | Bug fixes / Enhancements |
|---|---|
| 1.0.4 |
|
| 1.0.3 | Full discovery Support. |
| 1.0.2 | Bug fixes - changed the few commands to get the response. |
| 1.0.1 | Activity logger related changes. |
| 1.0.0 | Initial resource discovery and monitoring implementations. |
×