Software User Manual

Errors in all pat
hs to the external array
The following sections describe the recovery procedures for two examples when the error occurs in all
paths connecte
d to the external array.
If each node uses a different external array
In the configuration in Figure 64, all of the NAS Blade system's user LUs are volumes in the external array.
Each node uses the volume of a different array. All of node 1's user LUs are volumes in external array 1.
Therefore, if an error occurs in the path between the local array and external array 1, the error occurs in
all paths connected from node 1 to external array 1. In this situation, no user LU is available for node 1.
The situation in Figure 64 is as follows:
• The NAS Blade system attempts to change resource group 1's execution node to node 2 because
no user LU can be used from node 1 (failover). However, node 2 cannot access volumes in
external array 1, the failover function failed, and an srmd executable error appears as error
information for resource group 1.
• The filesystem'sstatusisblockedonnode2becauseofthefailureofthefailoverofresource
group 1.
• Clients cannot access volumes in external array 1, but can access volumes in external array 2.
• The local array recognizes that the status of all file systems and volumes in external array 1
are blocked.
Figure 64 Error occurs on the path to the external array used for node 1
1. Restore (for example, check the cable's connection status or change the switch) the status of the error
path between the local array and external array 1.
2. Exec
ute the Check Paths & Restore Vol. command using External Storage XP. For instructions, see
Checking the connection status and resuming external LU operations (Check Paths & Restore Vol.).
External Storage XP user guide
127