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 added automatically when devices are detected.
ETERNUS SF Storage Cruiser's agent, SSC agent
The VM host and VM guest on the following environment.
VMware Infrastructure 3 Version 3.5 or later
VMware vSphere 4 or later
VMware ESXi 3.5 or later
Even when detected a server node (host), the host name may not be resolved.
In this case, the host name is displayed in the format of "IP-IP address".
Even if IPv6 address exists in the searched servers, the agents shown below support only search with IPv4 address.
ETERNUS SF Storage Cruiser's agent that does not support IPv6 address
SSC agent
There are the following methods for automatic detection of devices in the subnet.
Specifying the target subnet in the Web Console screen.
Specifying the target subnet in the setting file (sanma.conf).
Through detection of the devices within the subnet, the automatic detection-compatible devices supported by Manager are displayed on the screen. SNMP-based broadcasting processes are performed internally and the devices supported by this software are automatically displayed.
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.
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.
Confirm the following if devices within the subnet cannot be automatically detected.
For devices that do not support [Detect device in subnet] as described in "1.2.6 Support levels", use the method described below "Detecting a device by specifying IP address".
When IP address on the Slave CM side is set in ETERNUS Disk storage system, use the method described below "Detecting a device by specifying IP address". Devices cannot be detected by automatic detection for the devices in the subnet.
To detect ETERNUS SF Storage Cruiser Agent or SSC Agent
Specify the IP address and SNMP Community name for the target device.
To detect the VM host and VM guest (VMware Infrastructure 3 Version 3.5 or later, VMware vSphere 4 or later, VMware ESXi 3.5 or later)
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.
To detect a VM guest which was set up after device registration for the VM host, use the Web Console to perform device deletion for the VM host which includes this VM guest and then perform the device registration again.
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
Specify the IP address and SNMP Community name for the target device
Note
If such a search for a product in the ETERNUS DX series, ETERNUS2000, ETERNUS4000, ETERNUS8000 fails, check the following items:
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 Disk array ETERNUS DX series, ETERNUS2000, ETERNUS4000, ETERNUS8000".
In the case of ETERNUS DX60/DX60 S2, DX80/DX80 S2, DX90/DX90 S2, DX400 S2 series, DX8000 S2 series
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 such a search for ETERNUS SF Storage Cruiser's agent or SSC agent fails, check whether ETERNUS SF Storage Cruiser's agent or SSC agent is activated. If not, activate ETERNUS SF Storage Cruiser's agent or SSC agent.
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 Troubleshooting information" to collect analysis material and contact a Fujitsu system engineer.
