Upgrade Error Codes And Recommended Actions - IBM Storwize V7000 Unified Problem Determination Manual

292
Storwize V7000 Unified: Problem Determination Guide Version
Table 44. Upgrade error codes and recommended actions (continued)
Error
Code Explanation
01A4 Unable to stop backup jobs.
01A5 Backup cron jobs are running.
01A6 Unable to install CNCSM callbacks. Contact your next level of support.
01A7 Internal vital product data (VPD)
error.
01A8 Check the health of management
service.
01A9 Unable to stop performance
collection daemon.
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.
Action
1. Check the status of the backups by
typing lsjobstatus -j backup.
2. Attempt to stop backups by typing
stopbackup --all.
3. Contact your next level of support.
1. Check the condition of tasks by
typing lstask -t cron.
2. Attempt to remove the backup by
typing rmtask StartBackupTSM.
3. Contact your next level of support.
Contact your next level of support.
1. Attempt to start the management
service with startmgtsrv on active
management node
2. Contact your next level of support.
Contact your next level of support.
Contact your next level of support.
1. Follow the replication recovery
procedure
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 "Ethernet connectivity
from file modules to the control
enclosure" on page 29.
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 29.