Table 120. Upgrade error codes and recommended actions (continued)
Error
Code Explanation Action
01A9 Unable to stop performance
collection daemon.
Contact IBM Remote Technical Support.
01AB Internal upgrade error in
node_setup_system.
Contact IBM Remote Technical Support.
01B1 Management node replication
failed.
1. Follow the replication recovery
procedure. See Resolving issues
reported by lshealth for resolving the
management node replication failure.
2. Contact IBM Remote Technical
Support.
01B2 Unable to start performance
collection daemon.
Contact IBM Remote Technical Support.
01B3 Failed to copy upgrade package to
Storwize V7000.
This could be caused by a number of
issues. Check Monitoring > Events under
both the block tab and the file tab on the
management GUI for an event that could
have caused this error and follow the
recommended action. If there is no
obvious event that could have caused
this error, refer to “Ethernet connectivity
from file modules to the control
enclosure” on page 68.
01B4 Failed to start upgrade on Storwize
V7000 with the applysoftware
command.
This could be caused by a number of
issues. Check Monitoring > Events under
both the block tab and the file tab on the
management GUI for an event that could
have caused this error and follow the
recommended action. If there is no
obvious event that could have caused
this error, refer to “Ethernet connectivity
from file modules to the control
enclosure” on page 68.
01B5 Storwize V7000 multipaths are
unhealthy.
Check the Fibre Channel connections to
the system. Reseat Fibre Channel cables.
For more information, see Fibre Channel
connectivity between file modules and
control enclosure.
01B6 Storwize V7000 vdisks are
unhealthy as indicated by using the
lsvdisk command.
See Chapter 5, “Control enclosure,” on
page 203.
01B7 Failed to query status of Storwize
V7000 upgrade by using the svcinfo
lsupdate command.
This could be caused by a number of
issues. Check Monitoring > Events under
both the block tab and the file tab on the
management GUI for an event that could
have caused this error and follow the
recommended action. If there is no
obvious event that could have caused
this error, refer to “Ethernet connectivity
from file modules to the control
enclosure” on page 68.
Chapter 7. Recovery procedures 421