If you have an in-band storage subsystem, follow this procedure. Click Refresh after each step to make sure of the results.
Make sure that the is installed and running.
If you started the host before the host was connected to the controllers in the storage subsystem, the host-agent software
will not be able to find the controllers. If so, make sure that the hardware connections are secure, and restart the host-agent
software.
Make sure that the network can access the by using the ping command. Use the form ping<host-name-or-IP-address>.
Examine the Ethernet cables to make sure that you cannot see any damage and that they are securely connected.
Make sure that the applicable network configuration tasks have been performed (for example, IP addresses have been assigned
to each controller).
Make sure that the controller firmware is compatible with the storage management software on your management station.
If the controller firmware was upgraded, the storage management software might not have access to the storage subsystem. A
new version of storage management software might be needed to manage the storage subsystem with the new version of the controller
firmware. If this problem exists, contact your representative.
Look to see if there is too much network traffic to one or more controllers.
This problem corrects itself because the storage management software tries to re-establish communication with the controllers
in the storage subsystem at regular times. If the storage subsystem was unidentified and a subsequent try to connect to the
storage subsystem succeeds, the storage subsystem becomes responsive.
For an out-of-band storage subsystem, look to see if management operations are taking place on the storage subsystem from
other storage management stations.
The type of management operations being performed and the number of management sessions taking place together establish the
number of connections made to a controller. When the maximum number of TCP/IP connections have been made, the controller stops responding.
This problem corrects itself because, after some TCP/IP connections complete, the controller then becomes responsive to other
connection tries.
If the storage subsystem is still unidentified, problems might exist with the controllers. Contact your representative.