The scope of the storage management functions of this software that can be used varies with the storage device model being used. For this software, the scope of available functions is represented as support levels, which are used as settings of the fault monitoring function and for other purposes. The table below lists the support levels that can be selected.
Support Level | Typical Device Name | Device Detection | Fault Management | Management Window Linkage | Performance Management | ||
|---|---|---|---|---|---|---|---|
SNMP Trap Monitoring (*1) | Device Polling Monitoring (*1) | Acquisition of Device Status | |||||
A | ETERNUS DX S5/S4 series | Automatic | Y1 | Y1 | Y1 | Y1 | Y1 |
ETERNUS DX S3 series (earlier than V10L60 firmware) | Automatic | Y1 | Y1 | Y1 | Y1 | Y1 | |
B | Windows, Linux, Solaris OS, HP-UX, or AIX server node on which the Storage Cruiser's agent is already installed | Automatic | Y1 | Y1 | Y1 | - | - |
C | VMware vSphere | Automatic | - | Y1 | Y1 | - | - |
D | NetApp FAS Series | Manual | Y1 | Y1 | - | Manual setting | Y1 |
E | VDX 8770-4, VDX 8770-8, VDX 6740, VDX 6740T, VDX series (4.0 or later firmware) | Manual | Y1 | Y1 | - | Manual setting | - |
ETERNUS CS800 M1/CS800 S7/CS800 S6 | Manual | Y1 | Y1 | - | - | - | |
I | Server node on which the Storage Cruiser's agent is not installed | Manual | - | - | - | Manual setting | - |
Y1: Detail information on device internal elements can be displayed.
*1: The protocols used with SNMP Trap monitoring and device polling are as follows.
Typical Device Name | Protocol Name | |
|---|---|---|
SNMP Trap Monitoring | Device Polling Monitoring | |
ETERNUS DX series (excluding the ETERNUS DX60 S2) | SNMP(SNMPv1 or SNMPv3) | |
ETERNUS DX60 S2 | SNMP(SNMPv1) | |
ETERNUS AB/HB series | SNMP(SNMPv2c) | ping |
Server node on which Storage Cruiser's agent is already installed | SNMP(SNMPv1 or SNMPv3) | unique protocol |
VMware vSphere | - | VMware dedicated protocol |
Other | SNMP(SNMPv1) | ping |
*2: The "Detect device in subnet" function is not supported by the devices below. Specify and register the IP addresses.
Solaris OS, Windows, Linux, HP-UX, AIX server node on which Storage Cruiser's agent is already installed
VMware server node
The following switches may not be able to be detected in subnet depending on the firmware version, etc.
Brocade series, PRIMERGY BX600 Fibre Channel switch blade, VDX series, PRIMERGY BX Ethernet Fabric Switch
*3: For devices supporting LAN, ping monitoring is enabled by specifying an IP address at manual embedding.
*4: SNMP Trap transmission must be set for each device. (This software does not automatically make said setting.)
*5: There are concerns in performance information. Refer to [Note] in "7.1.1 Performance Information Types".
*6: For NetApp FAS Series only. To refer to the performance information that is collected on the NetApp FAS Series, must be linkage with Systemwalker Service Quality Coordinator. Contact Fujitsu Technical Support for details on performance information.
*7: Only as for devices whose firmware version number is 3.0.1 or later, the performance management function is supported.
*8: The automatic registration function is not supported for devices whose firmware version number is 4.0 or later. Revise the firmware version or register manually.
*9: It takes a maximum of one minute to acquire the device information.
*10: This product acquires the device status automatically, but does not acquire the device component status automatically.
