IBM Storwize V7000, Problem Determination Manual

Page: 287 / 314

make sure that there are no more block storage configuration changes until IBM
support has checked that it is safe for configuration changes to be allowed again.
The problem that caused the recovery to be triggered might have caused the file
volumes to go offline long enough to cause the file systems to become unmounted.
You can immediately remount the file systems without waiting for IBM support to
tell you that it is safe for you to re-enable the control enclosure CLI.
There is a known issue with the Fibre Channel adapter. The adapter stops scanning
for LUNs if the adapter cannot detect any. When this situation happens, the
multipath does not have any active connections to the volumes on the Storwize
V7000.
The most reliable work-around for this situation is to reboot each of the file
modules in turn by using the following procedure (allows multipath to see the file
volumes and the file systems to be automatically re-mounted):
1. Identify the passive and the active management nodes from the Description
column in the output from the CLI command :
lsnode -r
Reboot the file module that is the passive management node using the CLI
command:
initnode -r -n <node name of the passive mode>
2.
Wait until both nodes show
OK
in the Connection status column of the output
from the CLI command:
lsnode -r
3.
Reboot the file module that is the active management node using the CLI
command. The active management node fails over to the file module that you
rebooted first.
initnode -r -n <node name of the active mode>
or
initnode -r
4. Log back on to the Storwize V7000 Unified CLI. Then wait for GPFS to be
active on both file modules in the output of the CLI command:
lsnode -r
5. Check that the file systems are mounted by using the
lsmount -r
management
CLI command:
lsmount -r
6. See “Checking the GPFS file system mount on each file module” on page 162 if
any file systems are not mounted.
Note that the management GUI becomes very slow when the Storwize V7000 CLI
is restricted. When you log on to the management GUI, it issues a warning that the
Storwize V7000 CLI is restricted. The management GUI runs the fix procedure to
direct you to send logs to IBM. The fix procedure directs you back to this
procedure to make the file systems accessible again.
To collect the Storwize V7000 logs, select the
Collect Logs
option from the
navigation in the service assistant. Choose the
With statesave
option.
The fix procedure re-enables the control enclosure CLI, provided that IBM support
approved of this procedure.
Chapter 7. Recovery procedures
263