MAP4560 No valid subsystem status available

There is no one problem that will identify the various combinations of failures that created the No valid subsystem status available condition. This procedure will help you determine the highest priority problem to repair first.

About this task

Global subsystem status (GSS) exists for each Logical Subsystem (LSS). Two copies are kept, each on a separate array. If one copy becomes unavailable, a problem is created and a new second copy is created on a different array if possible. It stays in this new location even after the repair is complete. Normally, when a volume is unavailable, the array it is located on has status of offline or unknown.

An LSS can operate on just one GSS copy. If both GSS copies are unavailable, the LSS gives command rejects and check conditions of internal target failure to all SCSI host system requests to its volumes. There can be one or more problems for each GSS copy that is unavailable. It normally takes two or more failures to prevent the fault tolerant RAID architecture from accessing a particular array (rank).

If access to the GSS copies was lost, but the data is still valid, then the repair action should restore access. This will automatically reset the "No Valid Subsystem Status" condition.

If both copies lost the actual GSS data, then the GSS status for that LSS will have to be reset when determined by the next level of support. This can cause customer data loss.

There is no one problem that will identify the various combinations of failures that created the condition. Each GSS copy has at least one problem needing repair. There may be other non-related problems needing repair also. An example would be a problem for a DDM replacement on an array and FC-AL loop not part of the LSS with the condition.

MAP4560 Section-1

Procedure

Contact your next level of support.