HP XP Data Shredder Software - Manual (Page 128)

3. Perform a forced stop operation using NAS Blade Manager for resource group 1, which displays the
status as an srmd executable error.
4. Stop node 1 using NAS Blade Manager.
5. Restart NAS OS 1 (NAS channel adapter's OS) using LUN Manager or NAS Blade Manager.
6. Start node 1 using NAS Blade Manager.
7. To release the blocked status of node 2's file system, perform the following operations:
a. Change resource group 2's execution node to node 1 using NAS Blade Manager (failover).
b. Restart NAS OS 2 (NAS channel adapter's) using LUN Manager or NAS Blade Manager.
c. Change resource group 2's execution node to node 2 (failback).
8. Start resource group 1 on node 1 using NAS Blade Manager.
If both nodes use the same external array
In the configuration in Figure 65 , all of the NAS Blade system's user LUs are volumes in the external array.
Only one external array is connected to the local array. Also, only one path is set between the local
array and external array. In this case, if an error occurs in the only set path, none of the volumes in the
external array can be used.
NOTE:
In the configuration in Figure 65 , HP recommends setting alternate paths to prevent the NAS Blade
system from being blocked because of the path failure. For more information, see Alternate paths .
The situation in Figure 65 is as follows:
• None of the user LUs can be used from node 1 or node 2.
• Clients cannot access volumes.
• The local array recognizes that the status of all file systems and volumes are blocked.
128 Troubleshooting NAS Blade systems that include external arrays