Brocade Error Message Reference Guide v6.1.0 (53-1000600-02, June 2008)

Fabric OS Message Reference 513
53-1000600-02
SULB-1009
8
0x23 - firmwareDownload timed out. This error may occur because firmwareDownload has not
completed within the predefined timeout period. It is most often caused by network issues. If the
problem persists, contact your system administrator.
0x24 - out of disk space. This error may occur because some coredump files have not been
removed from the filesystem and are using up disk space. Remove these coredump files using the
supportSave command before proceeding.
0x29 - The pre-install script failed. This error may be caused by an unsupported blade type in the
chassis. Remove or power off the unsupported blades before proceeding. Another possible cause
may be an invalid chassisConfig option setting. In that case, reset the chassisConfig option before
retrying firmwareDownload.
0x2e - Invalid Red Hat package manager (RPM) package. This error maybe caused by an
inconsistent firmware image loaded on the file server. It may also be caused by temporary
networking issues. Please reload firmware packages on the file server, then retry
firmwareDownload. If the problem persists, contact your system administrator.
Table 11 lists the firmwareDownload state names and state values. They indicate where in the
firmwareDownload process the error occurred.
TABLE 11 Upgrade State and Code Value
Upgrade State Code
SUS_PEER_CHECK_SANITY 0x21
SUS_PEER_FWDL_BEGIN 0x22
SUS_SBY_FWDL_BEGIN 0x23
SUS_PEER_REBOOT 0x24
SUS_SBY_REBOOT 0x25
SUS_SBY_FABOS_OK 0x26
SUS_PEER_FS_CHECK 0x27
SUS_SELF_FAILOVER 0x28
SUS_SBY_FWDL1_BEGIN 0x29
SUS_SELF_FWDL_BEGIN 0x2a
SUS_SELF_COMMIT 0x2b
SUS_SBY_FWC_BEGIN 0x2c
SUS_SBY_COMMIT 0x2d
SUS_SBY_FS_CHECK 0x2e
SUS_ACT_FWC_BEGIN 0x2f
SUS_PEER_RESTORE_BEGIN 0x30
SUS_SBY_RESTORE_BEGIN 0x31
SUS_PEER_FWC_BEGIN 0x32
SUS_PEER_FS_CHECK1 0x33
SUS_FINISH 0x34
SUS_COMMIT 0x35