A storage subsystem can have an Unresponsive Status
Important: It can take up to 5 minutes before the Enterprise Management software detects that a storage subsystem has become unresponsive or becomes responsive again. Before performing the suggested actions below, ensure you wait a sufficient amount of time before concluding that the storage subsystem is still unresponsive.
1 |
Check the Device Tree to see if all storage subsystems in the management domain are unresponsive. If so, check the storage management station network connection to ensure that it can reach the network; otherwise, continue with step 2. |
||||||||||||
2 |
Ensure that the controllers are installed and that there is power to the storage subsystem. If there is a problem, correct it. Otherwise:
|
||||||||||||
3 |
For a directly managed storage subsystem:
If there is a cable or network accessibility problem, fix the problem; otherwise go to step 5. |
||||||||||||
4 |
For a host-agent managed storage subsystem:
If there is a problem, make the appropriate host modifications, otherwise, continue with step 5. |
||||||||||||
5 |
Check with other administrators to see if a firmware upgrade was performed on the controllers from another storage management station. If a firmware upgrade was performed, the Enterprise Management software on your management station may not be able to locate the new Subsystem Management Window software needed to manage the storage subsystem with the new version of firmware. If this is the problem, contact your technical support, otherwise, continue with step 6. |
||||||||||||
6 |
Determine if there is an excessive amount of network traffic to one or more controllers. This is a self-correcting problem, because the Enterprise Management software periodically retries (in the background) to establish communication with the controllers in the storage subsystem. If the storage subsystem was unresponsive and a subsequent attempt to connect to the storage subsystem succeeds, the storage subsystem becomes responsive. For a directly managed storage subsystem, determine if management operations are taking place on the storage subsystem from other storage management stations. There is a controller-determined limit to the number of TCP/IP connections that can be made to the controller before it stops responding to subsequent connection attempts. The type of management operations being performed and the number of management sessions taking place together determine the number of TCP/IP connections made to a controller. This is a self-correcting problem, because after some TCP/IP connections terminate, the controller then becomes responsive to other connection attempts. |
||||||||||||
7 |
If the storage subsystem is still unresponsive, you probably have faulty controllers. Contact your technical support. |