For device management using this software, it is necessary to first conduct a device search. There are two methods for conducting a device search.
Information
The following devices are automatically registered when they are found:
Storage Cruiser's agent
VM host and VM guest in VMware vSphere
Even when detected a server node, the host name may not be resolved.
In this case, the host name is displayed in the format of "IP-IP address".
Even if an IPv6 address exists in a server to be searched, the Storage Cruiser's agent running on the operating systems shown below supports only the search with IPv4 address.
Platform | OS |
|---|---|
HP-UX | All versions |
AIX | All versions |
To detect devices in a subnet automatically, specify the target subnet on the Web Console screen. Through detection of the devices within the subnet, the automatic detection-compatible devices supported by the Manager are displayed on the screen. SNMP-based broadcasting processes are performed internally, and the devices supported by this software are automatically displayed. Devices must have SNMP access enabled for the Manager.
Devices with IPv6 address are not searched. If any device registered with IPv6 address exists, this function is not available. When managing any device with IPv6 address, specify its IP address to search it.
Devices using SNMPv3 are not searched. When managing any device using SNMPv3, specify its IP address to search it.
Note
Devices within subnets directly connected with the Management Server are subject to automatic detection regardless of the subnet being specified.
An environment which has broadcast processing pass through the target subnet is required for SNMP-based broadcast processing to be performed internally.
If the devices in the subnet cannot automatically be detected, check "1.1 Support Levels". For devices that do not support [Detect device in subnet] as described in "1.1 Support Levels", use the method described below "Detecting Device by Specifying IP Address".
If the IP address of Slave CM in an ETERNUS Disk storage system is set, both IP addresses of Master CM and Slave CM are detected. Refer to "5.2.3 Registering Device" to specify the device with the IP address of Master CM. If the IP address of Slave CM is specified, the access path cannot be set.
To detect Storage Cruiser's agent
Specify the IP address for the target device.
To detect the VM host and VM guest in VMware vSphere
Specify the IP address for the VM Host. Also, input the username and password used during login to the VM Host.
Information
By registering a VM host, all of the VM guests on the VM host are automatically registered.
With Web Console, perform the Reload Conf. operation for the VM host to detect VM guests created after the VM host was registered.
Note
To register a VM host (and its VM guests) with this software, the IP address, login name and password of the VM host are required.
It is not possible to specify and register only VM guests.
To detect any device other than above devices
When using SNMPv1, specify the IP address and the SNMP Community name for the target device.
When using SNMPv3, specify the IP address and the SNMPv3 username for the target device.
Note
If such a search for a product in the ETERNUS DX series, the ETERNUS AF All-Flash Arrays, or the ETERNUS DX200F fails, check the following items:
In the case that the SNMP environment has not been set up from ETERNUS Web GUI since installation of the device, the SNMP agent of the device is not active. Set up the SNMP environment as instructed in "4.3.1 ETERNUS DX Series, ETERNUS AF All-Flash Arrays, ETERNUS DX200F".
For the device detection, specify the IP address on the Master CM side. If the IP address on the CM slave side was specified for detection or registration, access path settings are not possible.
If the search for Storage Cruiser's agent fails, check whether the Storage Cruiser's agent is activated and that its level is compatible. If not activate, Storage Cruiser's agent. If the level is not compatible, upgrade the Storage Cruiser's agent.
If the search for Brocade Fibre Channel switch or PRIMERGY Fibre Channel switch blade fails, check the settings of SNMP MIB on the device side. Refer to "SNMP-MIB Setting" in "4.2.1 Brocade Fibre Channel Switch" for details.
On an AIX agent installed server, the following problems may occur:
It takes lots of time to register a server.
It takes lots of time to reload configuration.
The HBA port information for a target server may not be properly recognized.
If any of those mentioned above is seen, check all the HBA ports for proper connection. If there is any fibre channel device corresponding to an HBA port that is not connected, delete it if possible. To check HBA port-fibre channel device correspondence, refer to the AIX document. In addition, if the server is restarted, this operation may be needed again.
[Example of deleting unused fibre channel device fcs3]
# /usr/sbin/rmdev -Rdl fcs3
If a problem does not fall under those mentioned above, refer to "B.1 Collecting Troubleshooting Information" to collect analysis material and contact Fujitsu Technical Support.
