IBM Storwize V7000 Unified Series Problem Determination Manual page 293

Table 46. Upgrade error codes and recommended actions (continued)
Error
Code Explanation
01AB Internal upgrade error in
node_setup_system.
01B1 Management node replication
failed.
01B2 Unable to start performance
collection daemon.
01B3 Failed to copy upgrade package to
Storwize V7000.
01B4 Failed to start upgrade on Storwize
V7000 with the applysoftware
command.
01B5 Storwize V7000 multipaths are
unhealthy.
01B6 System volumes are unhealthy as
indicated by using the lsvdisk
command.
01B7 Failed to query status of upgrade
by using the
lssoftwareupgradestatus
command.
01B8 Failed to query status of Storwize
V7000 nodes by using the svcinfo
lsnode command.
Action
Contact your next level of support.
1. Go to "Resolving issues reported for
lshealth" on page 168.
2. Contact your next level of support.
Contact your next level of support.
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 "File module to control
enclosure" on page 27.
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 "File module to control
enclosure" on page 27.
Check the Fibre Channel connections to
the system. Reseat Fibre Channel cables.
For more information, see "Mounting a
file system" in the IBM Storwize V7000
Unified Information Center.
See Chapter 5, "Control enclosure," on
page 173.
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 "File module to control
enclosure" on page 27.
See Chapter 5, "Control enclosure," on
page 173.
Chapter 7. Recovery procedures
269