A storage subsystem with an Unresponsive Status occurs when the only controller or both controllers cannot be reached by the storage management station. An Unresponsive Status is represented by this icon in the Device Tree or Device Table Views.
If the storage subsystem has an operational controller, you can launch the Subsystem Management Window, but all management operations that require communication with the unresponsive controller will fail. If both controllers are unresponsive, you will receive error notices if you attempt to launch the Subsystem Management Window. To recover from this, follow the procedures in Recovering from an Unresponsive Storage Subsystem Condition.
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 any suggested recovery procedures wait a sufficient amount of time before concluding that the storage subsystem is still unresponsive.
An individual storage subsystem can appear multiple times in the Device Tree. This occurs when: (1) a storage subsystem has been configured to be managed through each Ethernet connection on the controllers (directly managed) and through a host's network connection (host-agent managed), or (2) the storage subsystem is managed through more than one host with the Host-Agent Software installed (multiple host-agent managed).
If a storage subsystem is both directly managed and host-agent managed, a network connection problem on the controllers might prevent direct communication with the storage subsystem over the network, but the storage subsystem might still be manageable over the network management connections provided by the host. The reverse situation can also occur.
If a storage subsystem is managed through more than one host, it is possible that the storage subsystem might become unresponsive to communication over the connections provided by one host, but the storage subsystem might still be manageable over the connections provided by another host.
In the example, the storage subsystem named Human Resources is attached to both the Alpha and Beta hosts. Both Alpha and Beta have Host-Agent software installed. Therefore, each can provide management connections to Human Resources.
The storage subsystem displays an Optimalstatus under the Alpha host, meaning that the storage subsystem is accessible through the connections provided by Alpha.
The storage subsystem displays an Unresponsive status under the Beta host, meaning that both controllers in the storage subsystem are inaccessible through the connection provided by Beta.
Notes:
If there is a problem with the controllers, then all instances of the storage subsystem in the Device Tree display the Unresponsive icon.
In the Device Table, every storage subsystem is listed once, no matter how many times it appears in the Device Tree. An icon representing its hardware status (Optimal, Needs Attention, or Fixing) is displayed, unless the storage subsystem is unresponsive over all connections. If so, the storage subsystem's status is represented with an Unresponsive icon.
The Subsystem Management window never displays a status of Unresponsive; rather, this window displays the hardware status of the storage subsystem (Optimal, Needs Attention, or Fixing).