Page 1 53-1000600-02 12 March 2008 Fabric OS Message Reference Supporting Fabric OS v6.1.0...
Page 2 Copyright © 2005-2008 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, Fabric OS, File Lifecycle Manager, MyView, and StorageX are registered trademarks and the Brocade B-wing symbol, DCX, and SAN Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. All other brands, products, or service names are or may be trademarks or service marks of, and are used to identify, products or services of their respective owners.
Page 3 Title Publication Summary of changes Date number Fabric OS System Error Message 53-0000515-09 Updated for v4.4.0, August 2004 Reference Manual First RASLog release Fabric OS System Error Message 53-0000515-10 Added 22 ZONE messages April 2005 Reference Manual Fabric OS System Error Message 53-0000515-11 Added FICU-1010, HAMK-1004, and PLAT- July 2005...
Page 4 Fabric OS Message Reference 53-1000600-02...
Page 5: Table Of Contents
Contents About This Document In this chapter ........... xlvii How this document is organized .
Page 6 Responding to a System Message........11 Looking Up a System Message .
Page 7 AG-1026............30 AG-1027 .
Page 8 AUTH-1038 ............41 AUTH-1039 .
Page 9 BL-1026 ............55 BL-1027 .
Page 10 Chapter 9 CDR System Messages CDR-1001 ............71 CDR-1002 .
Page 11 EM-1029 ............83 EM-1031 .
Page 12 ESS-1005............96 Chapter 14 EVMD System Messages EVMD-1001 .
Page 13 FABR-1037............109 FABR-1038.
Page 14 Chapter 22 FCR System Messages FCR-1001............127 FCR-1002.
Page 15 FCR-1039............137 FCR-1040.
Page 16 FCR-1083............148 FCR-1084.
Page 17 FICN-1036 ............158 FICN-1037 .
Page 18 FICN-1073 ............168 FICN-1074 .
Page 19 Chapter 27 FSPF System Messages FSPF-1001 ............181 FSPF-1002.
Page 20 FW-1037 ............193 FW-1038 .
Page 21 FW-1134 ............205 FW-1135 .
Page 22 FW-1190 ............217 FW-1191 .
Page 23 FW-1307 ............229 FW-1308 .
Page 24 FW-1344 ............241 FW-1345 .
Page 25 FW-1401 ............254 FW-1402 .
Page 26 Chapter 32 HAMK System Messages HAMK-1001 ........... . .267 HAMK-1002 .
Page 27 HIL-1501 ............277 HIL-1502 .
Page 28 ICPD-1002 ............293 ICPD-1003 .
Page 29 Chapter 44 KSWD System Messages KSWD-1003........... . .307 Chapter 45 KTRC System Messages KTRC-1001 .
Page 30 MS-1003 ............322 MS-1004 .
Page 31 PDM-1014 ............334 PDM-1017 .
Page 32 Chapter 60 RAS System Messages RAS-1001............349 RAS-1002.
Page 33 Chapter 64 SAS System Messages SAS-1001............361 Chapter 65 SCN System Messages SCN-1001 .
Page 34 SEC-1046............374 SEC-1049.
Page 35 SEC-1092............384 SEC-1093.
Page 36 SEC-1142............395 SEC-1145.
Page 37 SEC-1193............406 SEC-1194.
Page 38 SEC-1323............416 SEC-1324.
Page 39 SULB-1018............434 SULB-1020 .
Page 40 SYSM-1002 ........... . .445 SYSM-1003 .
Page 41 UCST-1007 ............457 UCST-1020.
Page 42 ZONE-1027 ........... . . 471 ZONE-1028 .
Page 43 CONF-1022 ........... . .483 Chapter 4 AUDIT FW System Messages FW-3001 .
Page 44 SEC-3029 ............498 SEC-3030 .
Page 45 SULB-1023 ........... . .515 SULB-1024.
Page 46 xlvi Fabric OS Message Reference 53-1000600-02...
Page 47: About This Document
About This Document In this chapter • How this document is organized ....... . . xlvii •...
Page 48: What's New In This Document
• Brocade 4100, 4900, 5000, 7500, AP 7600 switches • Brocade 24000 director • Brocade 48000 director • FA4-16 blade • FC10-6 blade What’s new in this document The following changes have been made since this document was last released: •...
Page 49: Key Terms
bold text Identifies command names Identifies the names of user-manipulated GUI elements Identifies keywords and operands Identifies text to enter at the GUI or CLI italic text Provides emphasis Identifies variables Identifies paths and Internet addresses Identifies document titles text Identifies CLI output code Identifies command syntax examples...
Page 50: Additional Information
Additional information This section lists additional Brocade and industry-specific documentation that you might find helpful. Brocade resources To get up-to-the-minute information, join Brocade Connect. It’s free! Go to http://www.brocade.com and click Brocade Connect to register at no cost for a user ID and password. For practical discussions about SAN design, implementation, and maintenance, you can obtain Building SANs with Brocade Fabric Switches through: http://www.amazon.com...
Page 51: Document Feedback
• Detailed description of the problem, including the switch or fabric behavior immediately following the problem, and specific questions • Description of any troubleshooting steps already performed and the results • Serial console and Telnet session logs • syslog message logs 2.
Page 52 Fabric OS Message Reference 53-1000640-02...
Page 53: Overview Of System Messages
Chapter Introduction To System Messages This guide supports Fabric OS v6.1.0 and documents system messages that can help you diagnose and fix problems with a switch or fabric. The messages are organized first by event type, reliability, availability, and serviceability log (RASLog) or AUDIT, and then alphabetically by module name. A module is a subsystem in the Fabric OS.
Page 54: Event Auditing
Overview of System Messages • Messages are numbered sequentially from 1 to 2,147,483,647 (0x7ffffff). The sequence number will continue to increase beyond the storage limit of 1024 messages. The sequence number can be reset to 1 using the errClear command. The sequence number is persistent across power cycles and switch reboots.
Page 55: System Logging Daemon (Syslogd)
Overview of System Messages Fabric OS v6.1.0 generates the following component-specific Audit messages: • Authentication messages: AUTH 2001-3008 • Configuration messages: CONF-1000, 1020, 1022 • HTTP configuration messages: HTTP-1002 - 1003 • SNMP-related messages: SNMP-1004 - 1006 • Security-related messages (SFOS, RADIUS, login/logout, passwords, ACLs): SEC-3001 - 3038 •...
Page 56: Port Logs
Viewing and Configuring System Message Logs The system console displays system messages, Audit messages (if enabled) and panic dump messages. These messages are mirrored to the system console; they are always saved in one of the system logs. You can filter messages that appear on the system console by severity using the errFilterSet command.
Page 57 Viewing and Configuring System Message Logs TABLE 2 Commands for Viewing or Configuring the System Parameters and Logs Command Description agtCfgDefault Resets the SNMP recipients to default values. agtCfgSet Modifies the SNMP agent configuration. agtCfgShow Displays the current SNMP agent configuration. auditCfg Configures the audit message log.
Page 58: Viewing System Messages From Web Tools
Viewing and Configuring System Message Logs TABLE 2 Commands for Viewing or Configuring the System Parameters and Logs (Continued) Command Description supportFfdc Enables and disables FFDC (first failure data capture). supportSave Collects RASLog, trace files, and supportShow (active CP only) information for the local CP and then transfers the files to an FTP server.
Page 59: Viewing System Messages One Message At A Time
Viewing and Configuring System Message Logs 2004/07/28-17:04:51, [EM-1055], 3,, WARNING, switch, Media 27: Port media incompatible. Reason: Configured port speed. 2004/07/28-17:04:54, [FABR-1001], 4,, WARNING, switch, port 4, ELP rejected by the other switch 2004/07/28-17:05:06, [FW-1050], 5,, WARNING, switch, Sfp Supply Voltage 0, is below low boundary(High=3600, Low=3150).
Page 60: Reading A Ras System Message
Reading a RAS System Message 2. Verify the configuration: switch:admin> auditcfg --show Audit filter is enabled. 1-ZONE 2-SECURITY 3-CONFIGURATION 4-FIRMWARE 5-FABRIC 3. Enable the audit feature: switch:admin> auditcfg --enable Audit filter is enabled. 4. Configure up to six syslog servers to receive the audit events that will be generated through syslog (procedure will vary depending on server type).
Page 61: Audit Event Messages
Reading a RAS System Message TABLE 3 System Message Field Description (Continued) Example Variable Name Description Sequence Number The error message position in the log. When a new message is added to the log, this number is incremented by 1. When this message reaches the last position in the error log and becomes the oldest message in the log, it is deleted when a new message is added.
Page 62 Reading a RAS System Message AUDIT, 2005/12/10-09:54:03, [SEC-1000], WARNING, SECURITY, JohnSmith/root/192.168.132.10/Telnet/CLI, Domain A/JohnsSwitch, , Incorrect password during login attempt. The fields in the error message are described in Table TABLE 4 Audit Message Field Description Example Variable Name Description AUDIT Audit flag Identifies the message as an Audit message.
Page 63: Message Severity Levels
Responding to a System Message Message Severity Levels There are four levels of severity for messages, ranging from Critical (1) to Info (4). In general, the definitions are wide ranging and are to be used as general guidelines for troubleshooting. For all cases, you should look at each specific error message description thoroughly before taking action.
Page 64: Gathering Information About The Problem
Responding to a System Message Gathering Information About the Problem Common steps and questions to ask yourself when troubleshooting a system message are as follows: 1. What is the current Fabric OS level? 2. What is the switch hardware version? 3.
Page 65: Trace Dumps
System Module Descriptions The software watchdog process (SWD) is responsible for monitoring daemons critical to the function of a healthy switch. The SWD holds a list of critical daemons that ping the SWD periodically at a predetermined interval defined for each daemon. The ping interval is set at 133 seconds, with the exception of the Fabric Watch daemon and the IP storage demon, which ping the SWD every 333 seconds.
Page 66 System Module Descriptions TABLE 5 System Module Descriptions (Continued) System Description Module Blade management error messages are a result of autoleveling firmware upgrades performed by the control processor (CP). Condor application specific integrated circuit (ASIC) driver error messages. This is the core edge routing module on the Brocade director platforms. CONF Status messages for configUpload and configDownload operations.
Page 67 System Module Descriptions TABLE 5 System Module Descriptions (Continued) System Description Module FSSM The Fabric OS state synchronization management module is defined both as a component and a service. A component is a module in Fabric OS implementing a related set of functionality. A service is a collection of components grouped together to achieve a modular software architecture.
Page 68 System Module Descriptions TABLE 5 System Module Descriptions (Continued) System Description Module KSWD The kernel software watchdog (KSWD) watches daemons for unexpected terminations and “hang” conditions and informs the HAM module to take corrective actions such as failover or reboot. The following daemons are monitored by KSWD: •...
Page 69 System Module Descriptions TABLE 5 System Module Descriptions (Continued) System Description Module The Management Service enables the user to obtain information about the Fibre Channel fabric topology and attributes by providing a single management access point. MS provides for both monitoring and control of the following areas: Fabric Configuration Server.
Page 70 System Module Descriptions TABLE 5 System Module Descriptions (Continued) System Description Module SNMP Simple Network Management Protocol is a universally supported low-level protocol that allows simple get, get next, and set requests to go to the switch (acting as an SNMP agent). It also allows the switch to send traps to the defined and configured management station.
Page 71 Section RASLog Messages This section provides the RASLog messages, including: • AG System Messages ......... . . 23 •...
Page 72 • HMON System Messages ........285 •...
Page 73 DRAFT: BROCADE CONFIDENTIAL • TRCK System Messages ........451 •...
Page 75: Ag-1001
Chapter AG System Messages AG-1001 Message <timestamp>, [AG-1001], <sequence-number>,, ERROR, <system-name>, N_Port ID virtualization (NPIV) is not supported by fabric port connected to port <port>. Probable Cause N_Port ID virtualization (NPIV) capability is not supported by the fabric port to which the Access Gateway is connected.
Page 76: Ag-1004
AG-1004 Severity WARNING AG-1004 Message <timestamp>, [AG-1004], <sequence-number>,, ERROR, <system-name>, Invalid response to fabric login (FLOGI) request from the fabric for N_Port <port>. Probable Cause Indicates that the fabric sent an invalid response to the FLOGI Extended Link Service (ELS) for the specified N_Port.
Page 77: Ag-1008
AG-1008 Recommended Check the connectivity between the Access Gateway N_Port and the fabric switch port. Action Severity WARNING AG-1008 Message <timestamp>, [AG-1008], <sequence-number>,, WARNING, <system-name>, Invalid port login (PLOGI) response from the fabric on the N_Port <port>. Probable Cause Indicates that the fabric switch management server did not accept the N_Port Login (PLOGI) request sent by the Access Gateway.
Page 78: Ag-1011
AG-1011 AG-1011 Message <timestamp>, [AG-1011], <sequence-number>,, WARNING, <system-name>, Sending FDISC failed on N_Port <port>. Probable Cause Indicates failure of sending the discover F_Port service parameter request from the Access Gateway to the fabric switch. Recommended Please check the configuration of the fabric switch connected to the Access Gateway. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers;...
Page 79: Ag-1015
AG-1015 Severity INFO AG-1015 Message <timestamp>, [AG-1015], <sequence-number>,, WARNING, <system-name>, Unable to find online N_Ports to connect to the fabric. Probable Cause Either no other N_Port is configured or all N_Ports are currently offline. Recommended Please check whether or not any other N_Port is configured. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers;...
Page 80: Ag-1019
AG-1019 Recommended Run switchShow to display the status of all ports in the system. Run portCfgShow to display a list of Action ports currently configured as N_Port(s). Ensure that the host is connected to an F_port. Severity ERROR AG-1019 Message <timestamp>, [AG-1019], <sequence-number>,, WARNING, <system-name>, Unable to failover N_Port <port>.
Page 81: Ag-1023
AG-1023 Probable Cause Indicates that the specified F_Port is failing over to its preferred N_Port. Recommended Please run ag --mapshow to display the updated F_Port to N_Port mapping. Action Severity INFO AG-1023 Message <timestamp>, [AG-1023], <sequence-number>,, INFO, <system-name>, F_Port <fport> mapped to offline N_Port <nport>...
Page 82: Ag-1026
AG-1026 AG-1026 Message <timestamp>, [AG-1026], <sequence-number>,, WARNING, <system-name>, Unable to handle the login request on port <port> due to insufficient resources. Probable Cause Insufficient resources. Recommended Run configure CLI on AG switch and increase the number of allowed logins on this port. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers;...
Page 83: Auth-1001
Chapter AUTH System Messages AUTH-1001 Message <timestamp>, [AUTH-1001], <sequence-number>,, INFO, <system-name>, <Operation type> has been successfully completed. Probable Cause Indicates that the secret database operation has been updated using the secAuthSecret command. The values for Operation type can be “set” or “remove”. Recommended No action is required.
Page 84: Auth-1004
AUTH-1004 AUTH-1004 Message <timestamp>, [AUTH-1004], <sequence-number>,, ERROR, <system-name>, Failed to set <data type> type to <setting value>. Probable Cause Indicates that the authUtil command has failed to set the authentication configuration value. The data type is either “authentication type”, “DH group type”, or “policy type”. Recommended Retry the authUtil command.
Page 85: Auth-1008
AUTH-1008 Recommended Run the authUtil command to make sure the local switch supports the specified protocols: Fibre Action channel authentication protocol (FCAP) or Diffie Hellman - challenge handshake authentication protocol (DH-CHAP). Severity ERROR AUTH-1008 Message <timestamp>, [AUTH-1008], <sequence-number>,, ERROR, <system-name>, No security license, operation failed.
Page 86: Auth-1012
AUTH-1012 AUTH-1012 Message <timestamp>, [AUTH-1012], <sequence-number>,, WARNING, <system-name>, Authentication <code> is rejected: port <port number> explain <explain code> reason <reason code>. Probable Cause Indicates that an authentication is rejected because the remote entity does not support authentication. Recommended Make sure the entity at the other end of the link supports authentication. Action Severity WARNING...
Page 87: Auth-1017
AUTH-1017 Probable Cause This may relate to an internal failure. Recommended Copy the message, collect switch information using the supportShow command, and contact your Action switch service provider. Severity ERROR AUTH-1017 Message <timestamp>, [AUTH-1017], <sequence-number>,, ERROR, <system-name>, Invalid value to start authentication request: port <port number>, operation code <operation code>.
Page 88: Auth-1022
AUTH-1022 If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity INFO AUTH-1022 Message <timestamp>, [AUTH-1022], <sequence-number>,, ERROR, <system-name>, Failed to extract <data type> from <message> payload: port <port number>. Probable Cause Indicates that the authentication process failed to extract a particular value from the receiving payload.
Page 89: Auth-1025
AUTH-1025 Severity ERROR AUTH-1025 Message <timestamp>, [AUTH-1025], <sequence-number>,, ERROR, <system-name>, Failed to get <data type> during <authentication phase>: port <port number>. Probable Cause Indicates that the authentication process failed to get the expected information during the specified authentication phase. Recommended Usually this problem is transient.
Page 90: Auth-1028
AUTH-1028 Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity ERROR AUTH-1028...
Page 91: Auth-1031
AUTH-1031 Probable Cause Indicates the receiving payload does not have valid message code for a particular authentication phase. Recommended Usually this problem is transient. The authentication might fail. Action Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands.
Page 92: Auth-1034
AUTH-1034 Probable Cause Indicates that an entity was not configured in the switch connection control (SCC) policy and tried to connect to the port. Recommended Add the entity's world-wide name (WWN) to the SCC policy and reinitialize authentication by using Action the portDisable and portEnable commands or the switchDisable and switchEnable commands.
Page 93: Auth-1037
AUTH-1037 If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity ERROR AUTH-1037 Message <timestamp>, [AUTH-1037], <sequence-number>,, ERROR, <system-name>, Failed to <operation type> response for <authentication message>: init_len <data length>, resp_len <data length>, port <port number>.
Page 94: Auth-1040
AUTH-1040 Recommended Correct the switch policy configuration on either of the switches using the authUtil command, and Action then enable the port using the portEnable command. Severity ERROR AUTH-1040 Message <timestamp>, [AUTH-1040], <sequence-number>,, INFO, <system-name>, Reject authentication on port <Port Number>, because switch authentication policy is set to OFF.
Page 95: Auth-1043
AUTH-1043 Recommended Check the connection port for a possible security attack. Action Check the shared secrets using secAuthSecret and reinitialize authentication using the portDisable and portEnable commands. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
Page 96 AUTH-1044 Fabric OS Message Reference 53-1000600-02...
Page 97: Bksw-1003
Chapter BKSW System Messages BKSW-1003 Message <timestamp>, [BKSW-1003], <sequence-number>,, WARNING, <system-name>, kSWD: <warning message>. Probable Cause Indicates a warning state within the system. A critical application error was reported in the watchdog subsystem. This message is used to convey information that might be of interest to the customer regarding the state of the system. Refer to the string at the end of the error message for specific information.
Page 98 BKSW-1003 Fabric OS Message Reference 53-1000600-02...
Page 99: Bl-1000
Chapter BL System Messages BL-1000 Message <timestamp>, [BL-1000], <sequence-number>,, INFO, <system-name>, Initializing ports... Probable Cause Indicates that the switch has started initializing the ports. Recommended No action is required. Action Severity INFO BL-1001 Message <timestamp>, [BL-1001], <sequence-number>,, INFO, <system-name>, Port initialization completed.
Page 100: Bl-1003
BL-1003 Run the diagPost command to ensure that Power-On Self-Test (POST) is enabled. Additional blade fault messages precede and follow this error, providing more information. See other error messages for recommended action. If the message persists, replace the blade. Severity CRITICAL BL-1003 Message...
Page 101: Bl-1007
BL-1007 Probable Cause Indicates that the errors (mostly synchronization errors) on this blade are harmless. Probably, the standby control processor (CP) blade connected to the active CP blade has experienced transitory problems. Recommended Use the haShow command to verify that the standby CP is healthy. If the standby CP was removed Action or faulted by user intervention, no action is required.
Page 102: Bl-1010
BL-1010 Recommended Make sure that the blade is seated correctly. Action If the blade is seated correctly, reboot or power cycle the blade. Run the systemVerification command to verify that the blade does not have hardware problems. Run the diagPost command to ensure that Power-On Self-Test (POST) is enabled. Refer to the Fabric OS Command Reference for more information on these commands.
Page 103: Bl-1012
BL-1012 BL-1012 Message <timestamp>, [BL-1012], <sequence-number>,, ERROR, <system-name>, bport <port number> port int. is disabled. status=0x<interrupt status> Port <port number> will be re-enabled in 1 minute. Probable Cause Indicates that the port generated an excessive number of interrupts that might prove unrecoverable to the switch operation.
Page 104: Bl-1015
BL-1015 Recommended Make sure to capture the console output during this process. Action On a bladed switch, run the slotPowerOff and slotPowerOn commands. On a nonbladed switch, reboot the switch. Run the systemVerification command to determine if there is a hardware error. Run the diagPost command to ensure that Power-On Self-Test (POST) is enabled.
Page 105: Bl-1017
BL-1017 Recommended Make sure that the blade is seated correctly. Action If the blade is seated correctly, reboot or power cycle the blade. Run the systemVerification command to verify that the blade does not have hardware problems. Run the diagPost command to ensure that Power-On Self-Test (POST) is enabled. Refer to the Fabric OS Command Reference for more information on these commands.
Page 106: Bl-1020
BL-1020 BL-1020 Message <timestamp>, [BL-1020], <sequence-number>,, CRITICAL, <system-name>, Switch timed out initializing the chips. Probable Cause Indicates that the switch has failed to initialize the application-specific integrated circuit (ASIC) chips. Recommended Reboot or power cycle the switch. Action Run the systemVerification command to verify that the switch does not have hardware problems. Run the diagPost command to ensure that Power-On Self-Test (POST) is enabled.
Page 107: Bl-1023
BL-1023 BL-1023 Message <timestamp>, [BL-1023], <sequence-number>,, CRITICAL, <system-name>, Blade in <slot number> slot was reset before blade init completed. As a result the blade is faulted. Probable Cause Indicates that the blade was reset before the initialization completed. Recommended Reboot or power cycle the blade. Action If the message persists, replace the blade.
Page 108: Bl-1027
BL-1027 Recommended Collect supportSave information, then reboot switch and run the diagPost command to ensure Action Power-On Self-Test (POST) is enabled. If problem persists, replace switch. Severity CRITICAL BL-1027 Message <timestamp>, [BL-1027], <sequence-number>,, CRITICAL, <system-name>, Blade in slot <slot number> faulted, boot failed; status 0x<boot status> 0x<1250 0 boot status>...
Page 109: Bl-1030
BL-1030 BL-1030 Message <timestamp>, [BL-1030], <sequence-number>,, INFO, <system-name>, All GigE/FCIP Virtualization/FC Fastwrite ports on the switch will be reset as part of the firmware upgrade. Probable Cause Indicates that a recent firmware upgrade caused the switch's internal processor firmware to be upgraded and resulted in the cold upgrade.
Page 110: Bl-1034
BL-1034 Probable Cause Indicates that the system timed out while waiting for disable messages from the user ports after disabling the ports. Recommended Reboot or power cycle the blade. Run the systemVerification command to verify that the blade does Action not have hardware problems.
Page 111: Bl-1037
BL-1037 BL-1037 Message <timestamp>, [BL-1037], <sequence-number>,, CRITICAL, <system-name>, Faulting chip in slot = <slot number>, miniS = <miniS number>,port = <port number> due to BE/BI port fault. Probable Cause Fault the chip and disable all the ports on that chip. Recommended No action is required.
Page 112 BL-1037 Fabric OS Message Reference 53-1000600-02...
Page 113: Bll-1000
Chapter BLL System Messages BLL-1000 Message <timestamp>, [BLL-1000], <sequence-number>, FFDC, CRITICAL, <system-name>, ASIC driver detected Slot <slot number> port <port number> as faulty (reason: <reason>) Probable Cause Indicates that a blade regulation problem was reported on the specified slot number. The blade is faulted.
Page 114 BLL-1000 If the message persists, replace the blade. Severity CRITICAL Fabric OS Message Reference 53-1000600-02...
Page 115: Bm-1001
Chapter BM System Messages BM-1001 Message <timestamp>, [BM-1001], <sequence-number>,, ERROR, <system-name>, BM protocol version <Protocol version> in slot <Slot number>. Probable Cause Indicates that the software running on the CP cannot communicate with the AP blade in the indicated slot, in order to determine AP blade's firmware version. This can be due to one of the following: •...
Page 116: Bm-1004
BM-1004 Recommended Use the slotPowerOff and slotPowerOn commands or reseat the affected blade. Action Severity WARNING BM-1004 Message <timestamp>, [BM-1004], <sequence-number>,, INFO, <system-name>, Blade firmware <Blade firmware> on slot <Slot> is not consistent with system firmware <System firmware>. Auto-leveling blade firmware to match system firmware. Probable Cause The policy of the specified blade is to auto-level the blade firmware to the system firmware.The inconsistency may be due to either of the following reasons:...
Page 117: Bm-1007
BM-1007 BM-1007 Message <timestamp>, [BM-1007], <sequence-number>,, INFO, <system-name>, Clearing <Slot number>. EX/VEX/FC port configuration for all ports for blade in slot Probable Cause The specified blade was detected for the first time after an FR4-18i was previously configured in the same slot. The new blade requires the specified port configurations to be cleared. Recommended The blade ports are cleared automatically.
Page 118: Bm-1053
BM-1053 Severity INFO BM-1053 Message <timestamp>, [BM-1053], <sequence-number>,, WARNING, <system-name>, Failed to establish connection between CP and Application Processor. Faulting switch. Probable Cause The control processor (CP) could not establish a connection to the application processor to communicate. Recommended On the Brocade 7500 or 7600, switch off and on all primary power to power-cycle the unit. Action Severity WARNING...
Page 119: Bm-1058
BM-1058 Probable Cause The policy of the specified switch is to persistently disable all ports the first time the application processor (AP) blade is detected. This may be cause by one of the following: • The AP was detected for the first time on this switch. •...
Page 120 BM-1058 Fabric OS Message Reference 53-1000600-02...
Page 121: C2 System Messages
Chapter C2 System Messages C2-1001 Message <timestamp>, [C2-1001], <sequence-number>,, ERROR, <system-name>, Port <port number> port fault (the configured speed may not be supported by the SFP). Please change the SFP or check the cable. Probable Cause Indicates a deteriorated SFP, an incompatible SFP pair, or a faulty cable between the peer ports. Recommended Verify that you are using compatible SFPs on the peer ports.
Page 122: C2-1005
C2-1005 C2-1005 Message <timestamp>, [C2-1005], <sequence-number>,, ERROR, <system-name>, Rate limit configuration is not effective on S(<slot number>) user port <port number> because QoS license is not present. Probable Cause Indicates that the switch does not have the QoS license added. Rate Limit is a licensed feature and requires QoS license.
Page 123: Cdr-1001
Chapter CDR System Messages CDR-1001 Message <port <timestamp>, [CDR-1001], <sequence-number>,, ERROR, <system-name>, Port number> port fault. Please change the SFP or check cable Probable Cause Indicates a deteriorated small form-factor pluggable (SFP), an incompatible SFP pair, a faulty cable between peer ports, or the port speed configuration does not match the capability of the SFP. Recommended Verify that you are using compatible SFPs on the peer ports.
Page 124: Cdr-1004
CDR-1004 Severity CRITICAL CDR-1004 Message <timestamp>, [CDR-1004], <sequence-number>, FFDC, ERROR, <system-name>, <slot number>, <chip index>: invalid DMA ch pointer, chan:<Channel number>, good_addr:0x<Good address>, bad_addr:0x<Bad address>. Probable Cause Indicates an internal error in the application specific integrated circuit (ASIC) hardware that may degrade data traffic.
Page 125: Cer-1001
Chapter CER System Messages CER-1001 Message <timestamp>, [CER-1001], <sequence-number>,, ERROR, <system-name>, HA Sync broken, since standby Advanced Performance Tuning module does not support FICON Management Server (FMS). Probable Cause Indicates that the high-availability (HA) synchronization between the active and standby control processors (CPs) is broken, because there is downlevel firmware loaded on the standby CP.
Page 126 CER-1001 Fabric OS Message Reference 53-1000600-02...
Page 127: Conf-1000
Chapter CONF System Messages CONF-1000 Message <timestamp>, [CONF-1000], <sequence-number>, AUDIT, INFO, <system-name>, <Info about the parameters and AD> configDownload completed successfully. Probable Cause Indicates that the configDownload operation was initiated and completed successfully. The message string that follows is a description of the class of configuration parameters that were downloaded.
Page 128: Conf-1021
CONF-1021 CONF-1021 Message <timestamp>, [CONF-1021], <sequence-number>,, INFO, <system-name>, configUpload <AD Number if AD is configured on the system> not permitted Probable Cause There are many possible causes. Recommended Check the error log for a possible cause. Please correct the error and upload the configuration Action again.
Page 129: Em-1001
Chapter EM System Messages EM-1001 Message <FRU <timestamp>, [EM-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, ID> is over heating: Shutting down. Probable Cause Indicates that a field-replaceable unit (FRU) is shutting down due to overheating. This is typically due to a faulty fan but can also be caused by the switch environment. Recommended Verify that the location temperature is within the operational range of the switch.
Page 130: Em-1004
EM-1004 Run the systemVerification command to verify that the switch does not have hardware problems. Refer to the Fabric OS Command Reference for more information on this command. On the Brocade 24000 and 48000, replace the specified FRU. For the Brocade 3900, replace the motherboard FRU. For the Brocade 200E, 3016, 3250, 3850, 4012, 4016, 4018, 4020, 4024, 4100, 4900, 5000, 7500, and AP7600, replace the switch.
Page 131: Em-1006
EM-1006 EM-1006 Message <FRU <timestamp>, [EM-1006], <sequence-number>, FFDC, CRITICAL, <system-name>, Id> has faulted. Sensor(s) below minimum limits. Probable Cause Indicates that the sensors show the voltage is below minimum limits. The switch or specified blade is being shut down for environmental reasons; the voltage is too low. Recommended If this problem occurs on a blade, it usually indicates a hardware problem on the blade;...
Page 132: Em-1010
EM-1010 Probable Cause Indicates that the environmental monitor (EM) received an unexpected power-down notification from the specified field-replaceable unit (FRU). This might indicate a hardware malfunction in the FRU. Recommended Try reseating the FRU. If the message persists, replace the FRU. Refer to the Brocade 48000 Action Hardware Reference Manual for more information about chassisConfig modes and supported blades.
Page 133: Em-1013
EM-1013 Run the systemVerification command to verify that the switch does not have hardware problems. Refer to the Fabric OS Command Reference for more information on this command. If the message persists, replace the FRU. Severity CRITICAL EM-1013 Message <timestamp>, [EM-1013], <sequence-number>,, ERROR, <system-name>, Failed to <FRU Id>.
Page 134: Em-1016
EM-1016 EM-1016 Message <timestamp>, [EM-1016], <sequence-number>,, WARNING, <system-name>, Cold recovery <Return code> failed ( Probable Cause Indicates that a problem was discovered when performing consistency checks during a cold boot. Recommended Monitor the switch. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
Page 135: Em-1031
EM-1028 Recommended Either change the chassisConfig option to 1 with the chassisConfig command, or upgrade the Action firmware on the standby to the version running on the active CP. Severity WARNING EM-1028 Message <timestamp>, [EM-1028], <sequence-number>, FFDC, CRITICAL, <system-name>, HIL Error: <function>...
Page 136: Em-1033
EM-1033 Recommended Close the ejector switch (raise the slider in most blades, or completely screw in the upper Action thumbscrew for the FC4-48 port blade) if the field-replaceable unit (FRU) is intended for use. Refer to the appropriate hardware manual for instructions on inserting the switch blades. Severity ERROR EM-1033...
Page 137: Em-1036
EM-1036 Probable Cause Suggests that since both Power Supplies associated with one of the 2 main circuits are present but faulty, maybe the circuit's switch has been turned off, or the AC power source has been interrupted for that circuit. The Switch side value is either “left”...
Page 138: Em-1041
EM-1041 EM-1041 Message <timestamp>, [EM-1041], <sequence-number>,, WARNING, <system-name>, Sensor values for <FRU Id>: <Sensor Value> <Sensor Value> <Sensor Value> <Sensor Value> <Sensor Value> <Sensor Value> <Sensor Value>. Probable Cause Indicates that sensors detected a warning condition. All significant sensors for the field-replaceable unit (FRU) are displayed;...
Page 139: Em-1045
EM-1045 Probable Cause Indicates that the specified field-replaceable unit (FRU) cannot be powered on because the associated logical switch is shut down. Recommended Run the switchStart command on the associated logical switch. Action Severity WARNING EM-1045 Message <timestamp>, [EM-1045], <sequence-number>,, WARNING, <system-name>, <FRU Id> is being powered <new state>.
Page 140: Em-1048
EM-1048 Recommended No action is required. Action Severity INFO EM-1048 Message <timestamp>, [EM-1048], <sequence-number>,, INFO, <system-name>, <FRU Id> I2C access recovered: state <current state> Probable Cause Indicates that the I2C bus problems have been resolved and I2C access to the field-replaceable unit (FRU) has become available again.
Page 141: Em-1055
EM-1055 Probable Cause Indicates that an inconsistent state was found in the field-replaceable unit (FRU). This occurs if the state of the FRU was changing during a failover. The FRU is reinitialized and traffic might have been disrupted. Recommended No action is required. Action Severity INFO...
Page 142: Em-1058
EM-1058 Recommended No action is required if the switch does not reach the reset threshold for the switch/blade. If the Action reset threshold is reached on the switch/blade, the switch/blade will be faulted and should be replaced. Severity WARNING EM-1058 Message <timestamp>, [EM-1058], <sequence-number>,, WARNING, <system-name>, Switch gets <Fault reason>...
Page 143: Em-1061
EM-1061 EM-1061 Message <timestamp>, [EM-1061], <sequence-number>,, WARNING, <system-name>, <Blade Type Id> Synchronization halted. Remove all blades of type or upgrade your standby CP, then reboot or run haSyncStart. Probable Cause A blade in the system is not supported by the release on the standby control processor (CP). Recommended Please remove all blades of this type or upgrade your standby CP.
Page 144: Em-1065
EM-1065 Recommended Contact support. Action Severity CRITICAL EM-1065 Message <timestamp>, [EM-1065], <sequence-number>,, CRITICAL, <system-name>, SAS Virtualization Services are not available due to incompatiblity between the FOS and SAS versions <Slot number or blank for single board systems>. Probable Cause The version of either the control processor firmware (CFOS) or the blade processor firmware (BFOS) is not compatible with the Storage Application Services (SAS) or other application firmware version(s).
Page 145 EM-2003 • Run the systemverification command to verify that the switch does not have hardware problems. Refer to theFabric OS Reference Manual for more information on this command. • On bladed systems, replace the specified FRU, otherwise replace the switch. Severity ERROR Fabric OS Message Reference...
Page 146 EM-2003 Fabric OS Message Reference 53-1000600-02...
Page 147: Ess-1001
Chapter ESS System Messages ESS-1001 Message <timestamp>, [ESS-1001], <sequence-number>,, WARNING, <system-name>, A few switches in the fabric do not support the Coordinated HotCode protocol. Probable Cause One or more switches in the fabric do not support the Coordinated HotCode protocol. Continuing with the firmware download may cause data traffic disruption.
Page 148: Ess-1004
ESS-1004 ESS-1004 Message <timestamp>, [ESS-1004], <sequence-number>,, WARNING, <system-name>, The resume message is rejected by the domain <domain id>. Probable Cause During the Coordinated HotCode protocol, a switch in the fabric has rejected the resume message which prevented the protocol from completing. Any data traffic disruption observed during the firmware download may have been due to the rejected resume message.
Page 149: Evmd-1001
Chapter EVMD System Messages EVMD-1001 Message <timestamp>, [EVMD-1001], <sequence-number>,, WARNING, <system-name>, Event could <Remote proxy switch id.> not be sent to remote proxy. = Probable Cause The event could not be sent to the remote proxy because the remote proxy switch cannot be reached through in-band.
Page 150 EVMD-1001 Fabric OS Message Reference 53-1000600-02...
Page 151: Fabr-1001
Chapter FABR System Messages FABR-1001 Message <timestamp>, [FABR-1001], <sequence-number>,, WARNING, <system-name>, port <port number>, <segmentation reason>. Probable Cause Indicates that the specified switch port is isolated because of a segmentation due to mismatched configuration parameters. Recommended Based on the segmentation reason displayed within the message, look for a possible mismatch of Action relevant configuration parameters in the switches at both ends of the link.
Page 152: Fabr-1004
FABR-1004 Run the fabStateShow command on both the receiving and transmitting switches. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING FABR-1004 Message <timestamp>, [FABR-1004], <sequence-number>,, WARNING, <system-name>, port: <port number>, req iu: 0x<address of IU request sent>, state: 0x<command sent>, resp iu:...
Page 153: Fabr-1007
FABR-1007 Recommended In case of severe memory corruption, the system might recover by performing an automatic Action failover. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING FABR-1007...
Page 154: Fabr-1010
FABR-1010 Recommended The fabric daemon will discard the EFP. The system will recover through the EFP retrial process. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING FABR-1010...
Page 155: Fabr-1013
FABR-1013 FABR-1013 Message <timestamp>, [FABR-1013], <sequence-number>, FFDC, CRITICAL, <system-name>, No Memory: pid=<fabric process id> file=<source file name> line=<line number within the source file>. Probable Cause Indicates that there is not enough memory in the switch for the fabric module to allocate. This message is rare and usually indicates a problem with the Fabric OS.
Page 156: Fabr-1016
FABR-1016 FABR-1016 Message <timestamp>, [FABR-1016], <sequence-number>,, WARNING, <system-name>, ficonMode is enabled. Probable Cause Indicates that FICON mode is enabled on the switch through a user interface command. Recommended No action is required. Action Severity WARNING FABR-1017 Message <timestamp>, [FABR-1017], <sequence-number>,, WARNING, <system-name>, ficonMode is disabled.
Page 157: Fabr-1020
FABR-1020 Probable Cause Indicates that this switch is a value-line switch and has exceeded the limited fabric size: that is, a specified limit to the number of domains. This limit is defined by your specific value-line license key. The fabric size has exceeded this specified limit, and the grace period counter has started. If the grace period is complete and the size of the fabric is still outside the specified limit, Web Tools is disabled.
Page 158: Fabr-1023
FABR-1023 Probable Cause Indicates that the fabric size has exceeded the value-line limit, and the grace period counter has started. If the grace period is complete and the size of the fabric is still outside the specified limit, Web Tools is disabled. Recommended Bring the fabric size within the licensed limits.
Page 159: Fabr-1030
FABR-1030 • VC_RDY mode: Virtual-channel flow control mode. This is a proprietary protocol. • R_RDY mode: Receiver-ready flow control mode. This is the Fibre Channel standard protocol, that uses R_RDY primitive for flow control. • DUAL_CR mode: Dual-credit flow control mode. In both of the previous modes, the buffer credits are fixed, based on the port configuration information.
Page 160: Fabr-1034
FABR-1034 Severity WARNING FABR-1034 Message <timestamp>, [FABR-1034], <sequence-number>, INFO, <system-name>, Area <Area that has already been acquired> have been acquired by port <Port that has already acquired the area>. Persistently disabling port <Port that is being disabled>. Probable Cause User must enable Trunk Area on a port for another port to use the same area. Recommended The user has to move the cable to a port area that is not in use, or the user must disable Trunk Action...
Page 161: Fabr-1037
FABR-1037 FABR-1037 Message <timestamp>, [FABR-1037], <sequence-number>, INFO, <system-name>, Port configuration incompatible with Trunk Area enabled port. Persistently disabling port <Port that is being disabled>. Probable Cause When the port attempts to go online, Switch finds the Trunk Area enabled with incompatible port configuration such as long distance, port mirror, fast write or EX_port.
Page 162 FABR-1039 Fabric OS Message Reference 53-1000600-02...
Page 163: Fabs-1001
Chapter FABS System Messages FABS-1001 Message <timestamp>, [FABS-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, <Function name> <Description of memory need> Probable Cause Indicates that the system is low on memory and cannot allocate more memory for new operations. This is usually an internal Fabric OS problem or file corruption. Description of memory need indicates how much memory was being requested.
Page 164: Fabs-1005
FABS-1005 FABS-1005 Message <timestamp>, [FABS-1005], <sequence-number>,, WARNING, <system-name>, <Function name and description of problem> (<ID type>= <ID number>) Probable Cause Indicates that an unsupported operation has been requested. This is usually an internal Fabric OS problem or file corruption. The possible values for function name and description of problem are: fabsys_write: Unsupported write operation: process xxx where "xxx"...
Page 165: Fabs-1008
FABS-1008 Severity WARNING FABS-1008 Message <Function <timestamp>, [FABS-1008], <sequence-number>,, WARNING, <system-name>, name> : Media oid mapping failed Probable Cause Indicates that the Fabric OS was unable to locate a necessary object handle. This is usually an internal Fabric OS problem or file corruption. Recommended Reboot or power cycle the switch.
Page 166: Fabs-1012
FABS-1012 Recommended Reboot or power-cycle the CP or system. Action If the message persists, run the firmwareDownload command to update the firmware. Severity ERROR FABS-1012 Message <timestamp>, [FABS-1012], <sequence-number>,, ERROR, <system-name>, <Method name>[<Method tag number>]:FRU state transition failed. Current state 0x<Current state of FRU>...
Page 167: Fabs-1015
FABS-1015 Severity ERROR FABS-1015 Message <timestamp>, [FABS-1015], <sequence-number>,, ERROR, <system-name>, <Method name>[<Method tag number>]:Request to enable FRU type 0x<FRU Object type>, unit <Unit number> failed. err code <Error code> Probable Cause Indicates the specified FRU could not be enabled. This is usually an internal Fabric OS problem. Recommended Try removing and reinserting the FRU.
Page 168 FABS-1015 Fabric OS Message Reference 53-1000600-02...
Page 169: Fbc-1001
Chapter FBC System Messages FBC-1001 Message <timestamp>, [FBC-1001], <sequence-number>,, ERROR, <system-name>, Firmware version on AP blade is incompatible with that on the CP. Probable Cause The CP determined that the version of firmware running on the AP blade is not compatible with the version of firmware running on the CP.
Page 170 FBC-1001 Fabric OS Message Reference 53-1000600-02...
Page 171: Fcip-1000
Chapter FCIP System Messages FCIP-1000 Message <timestamp>, [FCIP-1000], <sequence-number>, FFDC, ERROR, <system-name>, <command name> of GE <port number> failed. Please retry the command. Data: inst=<ASIC instance> st=<ASIC initializing state> rsn=<reason code> fn=<message function> oid=<ASIC ID> Probable Cause Indicates that the hardware is not responding to a command request; possibly because it is busy. Recommended Retry the command.
Page 172 FCIP-1001 Fabric OS Message Reference 53-1000600-02...
Page 173: Fcmc-1001
Chapter FCMC System Messages FCMC-1001 Message <timestamp>, [FCMC-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, System is low on memory and has failed to allocate new memory. Probable Cause Indicates that the switch is low on memory and failed to allocate new memory for an information unit (IU).
Page 174 FCMC-1001 Fabric OS Message Reference 53-1000600-02...
Page 175: Fcpd-1001
Chapter FCPD System Messages FCPD-1001 Message <timestamp>, [FCPD-1001], <sequence-number>,, WARNING, <system-name>, Probing <error string>. failed on Probable Cause Indicates that a fibre channel protocol (FCP) switch probed devices on a loop port, and the probing failed on the either the L_Port, AL_PA address, or the F_Port. For the AL_PA, the valid range is 00 through FF.
Page 176 FCPD-1003 Fabric OS Message Reference 53-1000600-02...
Page 177: Fcph-1001
Chapter FCPH System Messages FCPH-1001 Message <timestamp>, [FCPH-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, <function>: <failed function call> failed, out of memory condition Probable Cause Indicates that the switch is low on memory and failed to allocate new memory for a Fibre Channel driver instance.
Page 178 FCPH-1001 Fabric OS Message Reference 53-1000600-02...
Page 179: Fcr-1001
Chapter FCR System Messages FCR-1001 Message <timestamp>, [FCR-1001], <sequence-number>,, INFO, <system-name>, FC router proxy <port number> device in edge created at port Probable Cause Indicates that a proxy device in the edge fabric has been imported at the specified port. Recommended No action is required.
Page 180: Fcr-1005
FCR-1005 Recommended Verify that the device(s) were intended to be taken offline. Action If not, verify that the devices are functioning properly. Verify that all small form-factor pluggables (SFPs) are seated correctly. Check for faulty cables, deteriorated SFPs, or dirty connections. Replace the cables and SFPs if necessary.
Page 181: Fcr-1009
FCR-1009 Probable Cause Indicates that a logical storage area network (LSAN) zone was created at the specified port in the edge fabric. Recommended No action is required. Action Severity INFO FCR-1009 Message <timestamp>, [FCR-1009], <sequence-number>,, INFO, <system-name>, FC router LSAN zone enabled at port <port number>: <enabled name>.
Page 182: Fcr-1012
FCR-1012 FCR-1012 Message <timestamp>, [FCR-1012], <sequence-number>,, INFO, <system-name>, FC Router fabric build completed on port <port number>. Probable Cause Indicates that the fibre channel router has completed a fabric build at the specified port. Recommended No action is required. Action Severity INFO FCR-1013...
Page 183: Fcr-1018
FCR-1018 FCR-1018 Message <timestamp>, [FCR-1018], <sequence-number>,, ERROR, <system-name>, FC router <port number> proxy device entries exhausted on port Probable Cause Indicates that the number of proxy devices is greater than allowed by the port resource. Recommended Remove excess logical storage area network (LSAN) zones or devices until the number of proxy Action devices exported is within the range allowed by the port resource.
Page 184: Fcr-1021
FCR-1021 3. Use Zoning commands on the edge fabrics, to reduce the LSAN zone entries on the edge fabrics. 4. Run portEnable on each EX_Port, one at a time, to reenable the EX_Ports, and verify that this error is not reported again. Severity WARNING FCR-1021...
Page 185: Fcr-1024
FCR-1024 FCR-1024 Message <timestamp>, [FCR-1024], <sequence-number>,, WARNING, <system-name>, Local LSAN <zone name> zone device entries for edge LSAN exhausted. Probable Cause Indicates that the number of devices in a logical storage area network (LSAN) defined in the edge fabric exceeds the local LSAN zone database limitations. Recommended Remove excess device entries from this LSAN zone until the number of devices is within the range Action...
Page 186: Fcr-1028
FCR-1028 Probable Cause Indicates that the port world-wide name (WWN) pool has rolled over in the specified slot, and WWN entries detected to not be in use are reused as needed. Recommended It is unlikely that WWN conflicts will occur as a result of pool rollover unless the switch is deployed Action in a very large MetaSAN environment with large number of logical storage area network (LSAN) devices and fabrics, or there are highly dynamic changes to EX_Port connectivity.
Page 187: Fcr-1030
FCR-1030 FCR-1030 Message <timestamp>, [FCR-1030], <sequence-number>,, INFO, <system-name>, Physical device <device WWN> came online at fabric <fabric ID>. Probable Cause Indicates that the physical device world-wide name (WWN) came online in the specified fabric. Recommended No action is required. Action Severity INFO FCR-1031...
Page 188: Fcr-1034
FCR-1034 FCR-1034 Message <timestamp>, [FCR-1034], <sequence-number>,, INFO, <system-name>, LSAN zone added in backbone fabric. Probable Cause Indicates that a new logical storage area network (LSAN) zone was added to the backbone fabric. Recommended No action is required. Action Severity INFO FCR-1035 Message <timestamp>, [FCR-1035], <sequence-number>,, INFO, <system-name>, LSAN zone...
Page 189: Fcr-1038
FCR-1038 FCR-1038 Message <timestamp>, [FCR-1038], <sequence-number>,, WARNING, <system-name>, Total zone entries exceeded local fabric limits by <overflow> entries, in zone: <zone name>, zone limit: <LSAN zone limit>. Probable Cause Indicates that the number of cfg/zone/alias entries created in a local fabric is greater than the local switch's zone database limitations.
Page 190: Fcr-1042
FCR-1042 Severity INFO FCR-1042 Message <timestamp>, [FCR-1042], <sequence-number>,, INFO, <system-name>, LSAN zone removed in the backbone fabric. Probable Cause Indicates that a logical storage area network (LSAN) zone within the backbone fabric was removed. Recommended No action is required. Action Severity INFO FCR-1043...
Page 191: Fcr-1053
FCR-1053 Recommended Run the portEnable and portDisable commands to enable and disable the port. Action If the problem persists contact your switch service provider. Severity ERROR FCR-1053 Message <timestamp>, [FCR-1053], <sequence-number>,, WARNING, <system-name>, Port <port number> was disabled, <disable reason>. Probable Cause Indicates that the specified port was disabled because of a mismatched configuration parameter.
Page 192: Fcr-1056
FCR-1056 Severity INFO FCR-1056 Message <timestamp>, [FCR-1056], <sequence-number>,, INFO, <system-name>, Switch <switch WWN> with front domain ID <domain ID> does not support backbone to edge imports. Probable Cause Indicates that a switch that does not support backbone-to-edge routing is running in the MetaSAN. Recommended No action is required if backbone-to-edge routing is not needed.
Page 193: Fcr-1059
FCR-1059 FCR-1059 Message <port <timestamp>, [FCR-1059], <sequence-number>,, INFO, <system-name>, EX_Port number> was disabled due to an authentication failure. Probable Cause Indicates that the authentication, which uses the Diffie Hellman - challenge handshake authentication Protocol (DH-CHAP), failed on the EX_Port. Recommended Verify that the shared secrets on both sides of the link match.
Page 194: Fcr-1063
FCR-1063 Probable Cause Indicates that the maximum number of supported EX_ports or VEX_ports was exceeded. To enable the specified port, disable any other operational port then re-enable the port. Recommended No action is required. Action Severity INFO FCR-1063 Message <timestamp>, [FCR-1063], <sequence-number>,, INFO, <system-name>, Fabric <fabric ID>...
Page 195: Fcr-1066
FCR-1066 FCR-1066 Message <timestamp>, [FCR-1066], <sequence-number>,, ERROR, <system-name>, Fabric on port <port number> has the same fabric ID as another fabric. Probable Cause Indicates that either the fabric split, or there is another fabric (possibly the backbone) that has the same fabric ID as the fabric connected to the specified port.
Page 196: Fcr-1070
FCR-1070 Probable Cause Indicates that the FC Routing service is enabled. This is caused by either fosConfig –-enable fcr, or a configDownload with the fcrState set to 1 (enabled). Note that the FC Routing service is disabled by the factory. Recommended No action is required.
Page 197: Fcr-1073
FCR-1073 FCR-1073 Message <timestamp>, [FCR-1073], <sequence-number>,, INFO, <system-name>, Switch with domain ID <domain ID> in fabric <fabric ID> has lower limit of LSAN Zones supported. Probable Cause Indicates that a switch in the backbone/edge that supports different limit of logical storage area network (LSAN) zones was detected.
Page 198: Fcr-1076
FCR-1076 FCR-1076 Message <timestamp>, [FCR-1076], <sequence-number>,, ERROR, <system-name>, Port <port number> disabled, system only supports <maximum fds> front domains. Probable Cause Indicates that the maximum number of supported front domains was exceeded. To enable the specified port, disable any other operational front domain and then re-enable the port. Recommended Make sure to remain within the maximum of supported front domains.
Page 199: Fcr-1080
FCR-1080 Recommended Change the matrix database. Action Severity WARNING FCR-1080 Message <timestamp>, [FCR-1080], <sequence-number>,, WARNING, <system-name>, The pause response timer for domain <Domain> expired. Probable Cause During the Coordinated HotCode protocol, a switch in the fabric has not responded to the pause message which prevented the protocol from completing.
Page 200: Fcr-1083
FCR-1083 FCR-1083 Message <timestamp>, [FCR-1083], <sequence-number>,, WARNING, <system-name>, The resume message is rejected by the domain <Domain>. Probable Cause During the Coordinated HotCode protocol, a switch in the fabric has rejected the pause message which prevented the protocol from completing. Any data traffic disruption observed during the firmware download may have been due to the rejected resume message.
Page 201: Ficn-1003
Chapter FICON System Messages The FICON messages in this chapter include in many of the messages. The FICON <FICON Path> Path is a string that includes, where: VEHDHPDDDPLPCUDV VE - VE Port Number: This number represents the FCIP Tunnel number through its VE Port number. HD - Host switch Domain number: This is a 1 byte hexidecimal value that represents the domain of the switch that the FICON Channel is directly connected to.
Page 202: Ficn-1005
FICN-1005 FICN-1005 Message <timestamp>, [FICN-1005], <sequence-number>,, INFO, <system-name>, FICON GEPort <GE port number> TID <tunnel number> Feature Change verified Xrc <1 or 0 - XRC Emulation Enabled or Disabled> TapeWrt <1 or 0 - Tape Write Emulation Enabled or Disabled> TapeRd <1 or 0 - FICON Tape Read Emulation Enabled or Disabled> TinTir <1 or 0 - FICON TIN/TIR Emulation Enabled or Disabled>...
Page 203: Ficn-1008
FICN-1008 FICN-1008 Message <timestamp>, [FICN-1008], <sequence-number>,, ERROR, <system-name>, DevDiskEgr:FICON Purge Path received Path=<FICON PATH>. Probable Cause FICON Purge Path received from the channel as a part of path recovery. Recommended If there was a job failure associated with this event, please contact your vendor's customer support Action for assistance.
Page 204: Ficn-1012
FICN-1012 Recommended If there was an XRC volume or session suspended associated with this event, please contact your Action vendor's customer support for assistance. Severity ERROR FICN-1012 Message <timestamp>, [FICN-1012], <sequence-number>,, ERROR, <system-name>, DevDiskIng:Device level exception found for Path=<FICON PATH>: Oxid=0x<The OXID reported in the Device Level Exception Frame>.
Page 205: Ficn-1015
FICN-1015 FICN-1015 Message <timestamp>, [FICN-1015], <sequence-number>,, ERROR, <system-name>, DevEgr:cuPath=<FICON PATH>:Discarding Invalid LRCd SOF=0x<the received frame SOF type> count=<the running total number of discarded invalid LRC frames>. Probable Cause A frame was received from the peer emulation processing with an invalid LRC. This indicates data corruption between the emulation processing components.
Page 206: Ficn-1019
FICN-1019 FICN-1019 Message <timestamp>, [FICN-1019], <sequence-number>,, ERROR, <system-name>, DevTapeEgr:AS Link Level Reject (LRJ) from Chan on Path=<FICON PATH> LastCmd=0x<the Last 4 commands issued to the device> LastStatus=0x<the Last 4 status values received from the device>. Probable Cause The FICON channel indicated in the path issued a LRJ frame for a sequence from the device. Recommended If there was a job failure associated with this event, please contact your vendor's customer support Action...
Page 207: Ficn-1023
FICN-1023 Probable Cause The FICON channel issued a Selective Reset for a device that was active in emulation. Recommended If there was an unexpected job failure associated with this event, please contact your vendor's Action customer support for assistance. Severity ERROR FICN-1023 Message...
Page 208: Ficn-1026
FICN-1026 FICN-1026 Message <timestamp>, [FICN-1026], <sequence-number>,, INFO, <system-name>, DevTapeIng:UnusualStatus:WriteCancelSelr:Generating Final Ending Status Path=<FICON PATH>. Probable Cause The FICON tape write pipeline is completing an emulated Selective Reset sequence. Recommended If there was an unexpected job failure or IO Error associated with this event, please contact your Action vendor's customer support for assistance.
Page 209: Ficn-1030
FICN-1030 Recommended If there was an unexpected job failure or IO Error associated with this event, please contact your Action vendor's customer support for assistance. Severity ERROR FICN-1030 Message <timestamp>, [FICN-1030], <sequence-number>,, ERROR, <system-name>, HostDiskIng:FICON Purge received:Path=<FICON PATH>. Probable Cause An active disk emulation device received a FICON Purge Path from the channel.
Page 210: Ficn-1034
FICN-1034 Recommended No action is required. This is a part of the FICON path initialization. Action Severity INFO FICN-1034 Message <timestamp>, [FICN-1034], <sequence-number>,, ERROR, <system-name>, HostEgr:Discarding Invalid LRCd Frame on Path=<FICON PATH> count=<The total number of frames that have been received with an invalid LRC>. Probable Cause The channel emulation processing received a frame with an invalid FICON LRC from the peer.
Page 211: Ficn-1038
FICN-1038 Probable Cause A locally connected FICON Channel issued an Establish Logical Path sequence to the specified FICON Control Unit. Recommended No action is required. This is a part of the FICON path activation. Action Severity INFO FICN-1038 Message <timestamp>, [FICN-1038], <sequence-number>,, ERROR, <system-name>, fcFicIngHost:FDCB Lookup failed for Path=<FICON PATH>.
Page 212: Ficn-1041
FICN-1041 FICN-1041 Message <timestamp>, [FICN-1041], <sequence-number>,, ERROR, <system-name>, HostTapeEgr:AS Link Level Reject (LRJ) from CU Rx Path=<FICON PATH> LastCmd=0x<Last 4 commands issued to this device from the channel> LastStatus=0x<Last 4 status values sent to the channel from this device>. Probable Cause An LRJ received from a device indicates that the CU has lost the logical path to the LPAR.
Page 213: Ficn-1045
FICN-1045 Probable Cause Protocol errors in emulation in the CU or network errors can cause Selective Reset. Recommended If this was an unexpected event, please contact your vendor's customer support for assistance. Action Severity ERROR FICN-1045 Message <timestamp>, [FICN-1045], <sequence-number>,, WARNING, <system-name>, HostTapeIng:FICON Purge received:Path=<FICON PATH>.
Page 214: Ficn-1048
FICN-1048 FICN-1048 Message <timestamp>, [FICN-1048], <sequence-number>,, WARNING, <system-name>, DevDiskEgr:FICON Cancel received Path=<FICON PATH> state=0x<Current emulation state of the FICON device> sflags=0x<The current emulation status flags>. Probable Cause The operator has cancelled a read or write job. Recommended This is an unexpected event, please contact your vendor's customer support for assistance. Action Severity WARNING...
Page 215: Ficn-1052
FICN-1052 Recommended No action is required. This is a part of the XRC session establishment. Action Severity INFO FICN-1052 Message <timestamp>, [FICN-1052], <sequence-number>,, INFO, <system-name>, XRC Session Terminated: SessID=<SDM Assigned Session ID>, Path=<FICON PATH>. Probable Cause A terminate XRC session PSF command has been received to break an XRC session with the extended DASD device.
Page 216: Ficn-1056
FICN-1056 Probable Cause A suspend all devices from XRC session PSF command has been received to break an XRC session with the extended DASD device. Recommended If this was an unexpected event, please contact your vendor's customer support for assistance. Action Severity WARNING...
Page 217: Ficn-1059
FICN-1059 FICN-1059 Message <timestamp>, [FICN-1059], <sequence-number>,, ERROR, <system-name>, Error return from frame generation for a FICON Image: Path=<FICON PATH>. Probable Cause An internal resource shortage caused error such that an emulation frame could not be created and sent to an LPAR. Recommended This is an unexpected event, please contact your vendor's customer support for assistance.
Page 218: Ficn-1063
FICN-1063 FICN-1063 Message <timestamp>, [FICN-1063], <sequence-number>,, ERROR, <system-name>, Egress Abort:Oxid=0x<the OXID of the aborted exchange>:Path=<FICON PATH>:LastStates=0x<emulation state>. Probable Cause An abort operation has been received from the local FC interface for an active emulation exchange. Recommended This is an unexpected event, please contact your vendor's customer support for assistance. Action Severity ERROR...
Page 219: Ficn-1067
FICN-1067 Recommended This is an unexpected event, either the maximum number of emulation devices are already in use Action or there is an internal memory leak, please contact your vendor's customer support for assistance. Severity WARNING FICN-1067 Message <timestamp>, [FICN-1067], <sequence-number>,, ERROR, <system-name>, Ingress Abort:Oxid=0x<the OXID of the aborted exchange>:Abort for CH=0x<FICON PATH>.
Page 220: Ficn-1071
FICN-1071 Probable Cause The normal end of tape status (0x0D or 0x05) is received from the device or error status (including Unit Check 0x02) is received from an active emulation device. Recommended The end of tape is a normal event during pipelining and not the unit check. If there are associated Action IO error messages with this event, please contact your vendor's customer support for assistance.
Page 221: Ficn-1074
FICN-1074 FICN-1074 Message <timestamp>, [FICN-1074], <sequence-number>,, INFO, <system-name>, HostTapeIngr:WriteReport:Path=<FICON PATH>:Emuls=0x<the number of idle state to non-idle state transitions while this tape was loaded>:Cmds=0x<the number of emulated host write commands processed while this tape was loaded>:Chains=0x<the number of emulated host chains processed while this tape was loaded>:MBytes=<the number of emulated write megabytes processed while this tape was loaded>.
Page 222: Ficn-1077
FICN-1077 FICN-1077 Message <timestamp>, [FICN-1077], <sequence-number>,, INFO, <system-name>, DevTapeEgr:Unloaded:Path=<FICON PATH>:states=0x<4 prior emulation states>:cmds=0x<last 4 commands received from the channel for this device>:status=0x<last 4 status values received from the channel for this device>:flags=0x<tape report bit flags>. Probable Cause A Rewind and Unload IO has been processed from a remotely connected LPAR, which indicates that a tape should be unloaded on a device.
Page 223: Ficn-1080
FICN-1080 FICN-1080 Message <timestamp>, [FICN-1080], <sequence-number>,, INFO, <system-name>, DevTapeEgr:ReadCpReport:Path=<FICON PATH>:Emuls=0x<the number of idle state to non-idle state transitions while this tape was loaded>:Cmds=0x<the number of emulated host read commands processed while this tape was loaded>:Chains=0x<the number of emulated host chains processed while this tape was loaded>:MBytes=<the number of emulated read Kilobytes processed while this tape was loaded>.
Page 224: Ficn-1084
FICN-1084 Probable Cause An attached port with the established FICON emulated path has logged out from the switch. Recommended This may be an unexpected event, please contact your vendor's customer support for assistance. Action Severity WARNING FICN-1084 Message <timestamp>, [FICN-1084], <sequence-number>,, ERROR, <system-name>, fcFicInit: No DRAM2 memory available, FICON emulation is disabled.
Page 225: Ficu-1001
Chapter FICU System Messages FICU-1001 Message <timestamp>, [FICU-1001], <sequence-number>,, ERROR, <system-name>, <function name>: config<config Set(key)|Get(key)| Save> failed rc = <error>. Probable Cause Indicates that one of the configuration management functions failed. The key variable is part of the Fabric OS configuration database and is for support use only. The error variable is an internal error number.
Page 226: Ficu-1004
FICU-1004 Severity WARNING FICU-1004 Message <timestamp>, [FICU-1004], <sequence-number>,, WARNING, <system-name>, <function name>: Failed to set fabric manager server (FMS) mode: conflicting PID Format:<pid_format>, FMS Mode:<mode>. Probable Cause Indicates that a process ID (PID) format conflict was encountered. The core PID format is required for fibre connectivity control unit port (FICON-CUP).
Page 227: Ficu-1007
FICU-1007 Recommended Check if the FICON channel corresponding to the PID in the message is functioning correctly. Action Severity WARNING FICU-1007 Message <timestamp>, [FICU-1007], <sequence-number>,, WARNING, <system-name>, <function name>: Failed to allocate memory while performing <message>. Probable Cause Indicates that memory resources are low. This might be a transient problem. Recommended If the message persists, check the memory usage on the switch, using the memShow command.
Page 228: Ficu-1010
FICU-1010 FICU-1010 Message <timestamp>, [FICU-1010], <sequence-number>,, WARNING, <system-name>, FMS Mode <port number>. enable failed due to address conflict with port Probable Cause Indicates that the fibre connectivity FICON Management Server mode (fmsMode) was not enabled because the specified port has an address conflict with the CUP management port is in use. Recommended Use the portDisable command to disable the specified port to avoid the port address conflict.
Page 229: Fklb-1001
Chapter FKLB System Messages FKLB-1001 Message <timestamp>, [FKLB-1001], <sequence-number>,, WARNING, <system-name>, exchange <xid> overlapped, pid=<pid> Probable Cause Indicates that the FC kernel driver has timed out the exchange while the application is still active. When the FC kernel driver reuses the exchange, the application will overlap. This happens on a timed-out exchange;...
Page 230 FKLB-1001 Fabric OS Message Reference 53-1000600-02...
Page 231: Flod-1001
Chapter FLOD System Messages FLOD-1001 Message <timestamp>, [FLOD-1001], <sequence-number>, FFDC, WARNING, <system-name>, Unknown LSR type: port <port number>, type <LSR header type> Probable Cause Indicates that the link state record (LSR) type is unknown. 1-Unicast and 3-Multicast are the only two LSR header types.
Page 232: Flod-1006
FLOD-1006 Probable Cause Indicates that the received LSR contained an invalid domain number. Recommended No action is required; the LSR is discarded. Action Severity WARNING FLOD-1006 Message <timestamp>, [FLOD-1006], <sequence-number>,, WARNING, <system-name>, <domain number> Transmitting invalid domain ID: Probable Cause Indicates that the transmit LSR contained an invalid domain number.
Page 233: Fspf-1001
Chapter FSPF System Messages FSPF-1001 Message <timestamp>, [FSPF-1001], <sequence-number>,, ERROR, <system-name>, Input Port <port number> out of range Probable Cause Indicates that the specified input port number is out of range; it does not exist on the switch. Recommended No action is required. Action Severity ERROR...
Page 234: Fspf-1005
FSPF-1005 FSPF-1005 Message <timestamp>, [FSPF-1005], <sequence-number>,, ERROR, <system-name>, Wrong Section Id <section number>, should be <section number>, input port = <port number> Probable Cause Indicates that an incorrect section ID was reported from the specified input port. The section ID is used to identify a set of switches that share an identical topology database.
Page 235: Fss-1001
Chapter FSS System Messages FSS-1001 Message <timestamp>, [FSS-1001], <sequence-number>,, WARNING, <system-name>, Component (<component name>) dropping HA data update (<update ID>). Probable Cause Indicates that an application has dropped a high availability (HA) data update. Recommended Run the haSyncStart command if this is a dual-CP system, or reboot the switch if it is a nonbladed Action system.
Page 236: Fss-1004
FSS-1004 Severity WARNING FSS-1004 Message <timestamp>, [FSS-1004], <sequence-number>,, ERROR, <system-name>, Memory shortage Probable Cause Indicates that the system ran out of memory. Recommended Run the memShow command to view memory usage. Action Run the haSyncStart command if this is a dual-CP system, or reboot the switch if it is a nonbladed system.
Page 237 FSS-1007 Probable Cause Indicates that the Ethernet connection between the active control processor (CP) and standby CP is not healthy. The error occurs when the standby CP does not respond to a request from the active CP within 5 seconds. This usually indicates a problem with the internal Ethernet connection and a disruption of the synchronization process.
Page 238 FSS-1007 Fabric OS Message Reference 53-1000600-02...
Page 239: Fssm-1002
Chapter FSSM System Messages FSSM-1002 Message <timestamp>, [FSSM-1002], <sequence-number>,, INFO, <system-name>, HA State is in sync. Probable Cause Indicates that the high availability (HA) state for the active control processor (CP) is in synchronization with the HA state of the standby CP. If the standby CP is healthy, then a failover is nondisruptive.
Page 240 FSSM-1004 Probable Cause Indicates that the active control processor (CP) and the standby CP in a dual CP system are running firmware that are incompatible with each other. If the active CP fails, the failover will be disruptive. In a non-bladed system, this message is logged when the firmware upgrade/downgrade was invoked.
Page 241: Fw-1001
Chapter FW System Messages FW-1001 Message <timestamp>, [FW-1001], <sequence-number>,, INFO, <system-name>, <label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the internal temperature of the switch has changed. Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation.
Page 242: Fw-1004
FW-1004 Severity WARNING FW-1004 Message <timestamp>, [FW-1004], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the internal temperature of the switch has changed from a value outside of the acceptable range to a value within the acceptable range.
Page 243: Fw-1007
FW-1007 FW-1007 Message <timestamp>, [FW-1007], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the speed of the fan has risen above the high boundary. Fan problems typically contribute to temperature problems. Recommended Consistently abnormal fan speeds generally indicate that the fan is failing.
Page 244: Fw-1011
FW-1011 Recommended Verify that you have installed the power supply correctly and that it is correctly seated in the Action chassis. If the problem persists, replace the faulty power supply. Severity WARNING FW-1011 Message <timestamp>, [FW-1011], <sequence-number>,, INFO, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>).
Page 245: Fw-1035
FW-1035 Probable Cause Indicates that the temperature of the small form-factor pluggable (SFP) has fallen below the low boundary. Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation. Severity WARNING FW-1035...
Page 246: Fw-1038
FW-1038 Severity INFO FW-1038 Message <timestamp>, [FW-1038], <sequence-number>,, WARNING, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the receive power value of the small form-factor pluggable (SFP) has fallen below the low boundary.
Page 247: Fw-1041
FW-1041 FW-1041 Message <timestamp>, [FW-1041], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the transmit power value of the small form-factor pluggable (SFP) has changed. The transmit performance area measures the amount of outgoing laser to help you determine if the SFP is in good working condition or not.
Page 248: Fw-1044
FW-1044 FW-1044 Message <timestamp>, [FW-1044], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the transmit power value of the small form-factor pluggable (SFP) has changed from a value outside of the acceptable range to a value within the acceptable range.
Page 249: Fw-1048
FW-1048 Probable Cause Indicates that the value of the small form-factor pluggable (SFP) voltage has risen above the high boundary. The supplied current of the SFP transceiver is outside of the normal range, indicating possible hardware failure. Recommended If the current rises above the high boundary, you must replace the SFP. Action Severity WARNING...
Page 250: Fw-1051
FW-1051 FW-1051 Message <timestamp>, [FW-1051], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the value of the small form-factor pluggable (SFP) voltage has risen above the high boundary. High voltages indicate possible hardware failures. Frequent voltage fluctuations are an indication that the SFP is deteriorating.
Page 251: Fw-1115
FW-1115 Probable Cause Indicates that the number of times E_Ports have gone down has fallen below the low boundary. E_Ports go down each time you remove a cable or small form-factor pluggable (SFP). SFP failures also cause E_Ports to go down. E_Port downs might be caused by transient errors. A low number of E_Port failures means that the switch is functioning normally.
Page 252: Fw-1118
FW-1118 • two fabrics have joined. • an E_Port has gone offline. • a principal link has segmented from the fabric. Recommended Verify that the cable is properly connected at both ends. Verify that the small form-factor pluggables Action (SFPs) have not become faulty. An inexplicable fabric reconfiguration might be a transient error and might not require troubleshooting.
Page 253: Fw-1120
FW-1120 FW-1120 Message <timestamp>, [FW-1120], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of fabric reconfigurations has changed from a value outside of the acceptable range to a value within the acceptable range.
Page 254: Fw-1123
FW-1123 FW-1123 Message <timestamp>, [FW-1123], <sequence-number>,, INFO, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of domain ID changes has risen above the high boundary. Domain ID changes occur when there is a conflict of domain IDs in a single fabric and the principal switch has to assign another domain ID to the switch.
Page 255: Fw-1126
FW-1126 FW-1126 Message <timestamp>, [FW-1126], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of segmentations has fallen below the low boundary. Segmentation changes might occur due to: •...
Page 256: Fw-1129
FW-1129 • Zone conflicts. • Domain conflicts. • Segmentation of the principal link between two switches. • Incompatible link parameters. During E_Port initialization, ports exchange link parameters. Rarely, incompatible parameters result in segmentation. Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation.
Page 257: Fw-1132
FW-1132 Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation. Severity INFO FW-1132 Message <timestamp>, [FW-1132], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value>...
Page 258: Fw-1135
FW-1135 FW-1135 Message <timestamp>, [FW-1135], <sequence-number>,, INFO, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of fabric logins has risen above the high boundary. Fabric logins occur when a port or device initializes with the fabric. The event is called a fabric login or FLOGI. Recommended No action is required.
Page 259: Fw-1139
FW-1139 Probable Cause Indicates that the number of small form-factor pluggable (SFP) state changes has fallen below the low boundary. SFP state changes occur when the SFP is inserted or removed. A low number of SFP state changes means that the switch is functioning normally. Recommended No action is required.
Page 260: Fw-1161
FW-1161 Recommended Check both ends of your cable connection. Verify that the cable and small form-factor pluggables Action (SFPs) are not faulty. Losses of synchronization commonly causes link failures. If you receive concurrent loss of synchronization errors, troubleshoot the loss of synchronization. Severity INFO FW-1161...
Page 261: Fw-1164
FW-1164 Probable Cause Indicates that the number of link failures that the port experiences has changed from a value outside of the acceptable range to a value within the acceptable range. Link loss errors occur when a link experiences a loss of signal and fails. Both physical and hardware problems can cause link loss errors.
Page 262: Fw-1167
FW-1167 Probable Cause Indicates that the number of synchronization losses that the port experiences has risen above the high boundary. Loss-of-synchronization errors frequently occur due to a faulty small form-factor pluggable (SFP) or cable. Signal losses often create synchronization losses. Recommended Check both ends of your cable connection.
Page 263: Fw-1170
FW-1170 Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation. A low number of signal loss errors means that the switch is functioning normally. Severity INFO FW-1170 Message <timestamp>, [FW-1170], <sequence-number>,, WARNING, <system-name>, <Port Name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>).
Page 264: Fw-1173
FW-1173 Severity INFO FW-1173 Message <timestamp>, [FW-1173], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of protocol errors that the port experiences has fallen below the low boundary.
Page 265: Fw-1176
FW-1176 FW-1176 Message <timestamp>, [FW-1176], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of invalid words that the port experiences has changed. Invalid words usually indicate a hardware problem with an small form-factor pluggable (SFP) or cable. Recommended Check both ends of your connections, your SFP, and your cable to verify that none are faulty.
Page 266: Fw-1180
FW-1180 Probable Cause Indicates that the number of invalid words that the port experiences has changed from a value outside of the acceptable range to a value within the acceptable range. Invalid words usually indicate a hardware problem with an small form-factor pluggable (SFP) or cable. Recommended No action is required.
Page 267: Fw-1183
FW-1183 Recommended This error generally indicates an deteriorating fabric hardware. Check your small form-factor Action pluggables (SFPs), cables, and connections for faulty hardware. Verify that all optical hardware is clean. Severity WARNING FW-1183 Message <timestamp>, [FW-1183], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>).
Page 268: Fw-1186
FW-1186 FW-1186 Message <timestamp>, [FW-1186], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the percentage of incoming traffic that the port experiences has risen above the high boundary.
Page 269: Fw-1190
FW-1190 Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation. Severity INFO FW-1190 Message <timestamp>, [FW-1190], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value>...
Page 270: Fw-1193
FW-1193 FW-1193 Message <timestamp>, [FW-1193], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of state changes that the port experiences has fallen below the low boundary.
Page 271: Fw-1216
FW-1216 FW-1216 Message <timestamp>, [FW-1216], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of arbitrated loop physical address (AL_PA) cyclic redundancy check (CRC) errors has changed. This indicates that errors have been detected in the FC frame. Invalid CRC messages occur when the number of CRC errors in Fibre Channel frames for specific source ID (S_ID) and destination ID (D_ID) pairs change.
Page 272: Fw-1219
FW-1219 Recommended You should configure a five- or six-figure high boundary for this area. Only five-figure (or higher) Action values for CRC errors indicate problems. When an “above” message is received, check for a faulty cable or deteriorated small form-factor pluggable (SFP). Replace the cable or SFP if necessary. Try cleaning the connectors.
Page 273: Fw-1242
FW-1242 Probable Cause Indicates that the number of end-to-end (EE) cyclic redundancy check (CRC) errors has fallen below the low boundary. Invalid CRC messages occur when the number of CRC errors in Fibre Channel frames for specific source ID (S_ID) and destination ID (D_ID) pairs change. These messages might also be caused by dirty equipment, temperature fluctuations, and aging equipment.
Page 274: Fw-1245
FW-1245 Probable Cause Indicates that the number of end-to-end (EE) word frames that the switch receives has changed. Receive performance messages appear due to the number of word frames that travel from the configured S_ID to the D_ID pair. Recommended No action is required.
Page 275: Fw-1248
FW-1248 Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation. Severity INFO FW-1248 Message <timestamp>, [FW-1248], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of end-to-end (EE) word frames that the switch transmits has changed.
Page 276: Fw-1251
FW-1251 FW-1251 Message <timestamp>, [FW-1251], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of end-to-end (EE) word frames that the switch transmits has changed from a value outside of the acceptable range to a value within the acceptable range.
Page 277: Fw-1275
FW-1275 Probable Cause Indicates that the number of frame types or commands that the port receives has risen above the high boundary. The port has received a small computer system interface (SCSI) Read, SCSI Write, SCSI Read and Write, SCSI Traffic, or IP commands in a frame. Recommended No action is required.
Page 278: Fw-1298
FW-1298 Probable Cause Indicates that the number of Telnet violations has fallen below the low boundary. Telnet violations indicate that a Telnet connection request has been received from an unauthorized IP address. The TELNET_POLICY contains a list of internet protocol (IP) addresses that are authorized to establish Telnet connections to switches in the fabric.
Page 279: Fw-1301
FW-1301 Probable Cause Indicates that the number of hypertext transfer protocol (HTTP) violations has changed. HTTP violations indicate that a browser connection request has been received from an unauthorized IP address. The HTTP_POLICY contains a list of internet protocol (IP) addresses that are authorized to establish browser connections to the switches in the fabric.
Page 280: Fw-1304
FW-1304 Probable Cause Indicates that the number of hypertext transfer protocol (HTTP) violations has changed from a value outside of the acceptable range to a value within the acceptable range. HTTP violations indicate that a browser connection request has been received from an unauthorized IP address. The HTTP_POLICY contains a list of internet protocol (IP) addresses that are authorized to establish browser connections to the switches in the fabric.
Page 281: Fw-1307
FW-1307 Probable Cause Indicates that the number of application programming interface (API) violations has risen above the high boundary. API violations indicate that an API connection request has been received from an unauthorized IP address. The simple network management protocol policy (SNMP_POLICY) contains a list of internet protocol (IP) addresses that are authorized to establish API connections to switches in the fabric.
Page 282: Fw-1310
FW-1310 Probable Cause Indicates that the number of simple network management protocol read (RSNMP) violations has fallen below the low boundary. RSNMP violations indicate that an SNMP “get” operation request has been received from an unauthorized IP address. Recommended No action is required. Action Severity INFO...
Page 283: Fw-1313
FW-1313 Recommended Run the errShow command to determine the IP address that sent the request. Responses to Action security-class messages depend on user policies. Consult your security administrator for response strategies and policies. Severity INFO FW-1313 Message <timestamp>, [FW-1313], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>).
Page 284: Fw-1316
FW-1316 Severity INFO FW-1316 Message <timestamp>, [FW-1316], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of SES violations has changed. SES violations indicate that an small computer system interface (SCSI) Enclosure Services (SES) request has been received from an unauthorized world-wide name (WWN).
Page 285: Fw-1319
FW-1319 FW-1319 Message <timestamp>, [FW-1319], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of SES violations has changed from a value outside of the acceptable range to a value within the acceptable range.
Page 286: Fw-1322
FW-1322 FW-1322 Message <timestamp>, [FW-1322], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of simple network management server (MS) violations has risen above the high boundary. MS violations indicate that a MS access request has been received from an unauthorized world-wide name (WWN).
Page 287: Fw-1325
FW-1325 FW-1325 Message <timestamp>, [FW-1325], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of serial violations has fallen below the low boundary. Serial violations indicate that an unauthorized serial port request has been received. The SERIAL_POLICY contains a list of switch world-wide names (WWNs) for which serial port access is enabled.
Page 288: Fw-1328
FW-1328 FW-1328 Message <timestamp>, [FW-1328], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of front panel violations has changed. Front panel violations indicate that an unauthorized front panel request has been received. The FRONTPANEL_POLICY contains a list of switch world-wide names (WWNs) for which front panel access is enabled.
Page 289: Fw-1331
FW-1331 FW-1331 Message <timestamp>, [FW-1331], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of front panel violations has changed from a value outside of the acceptable range to a value within the acceptable range.
Page 290: Fw-1334
FW-1334 FW-1334 Message <timestamp>, [FW-1334], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of switch connection control policy (SCC) violations has risen above the high boundary. SCC violations indicate that an unauthorized switch tried to join the fabric. The SCC_POLICY contains a list of switches by world-wide names (WWNs) that are allowed to be members of a fabric.
Page 291: Fw-1337
FW-1337 FW-1337 Message <timestamp>, [FW-1337], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of device cable connection (DCC) violations has fallen below the low boundary. DCC violations indicate that an unauthorized device tried to join the fabric. The DCC_POLICY allows for the specification of rules for binding device ports (typically host bus adaptor (HBA) ports) to specific switch ports.
Page 292: Fw-1340
FW-1340 Probable Cause Indicates that the number of device cable connection (DCC) violations has changed from a value outside of the acceptable range to a value within the acceptable range. DCC violations indicate that an unauthorized device tried to join the fabric. The DCC_POLICY allows for the specification of rules for binding device ports (typically host bus adaptor (HBA) ports) to specific switch ports.
Page 293: Fw-1343
FW-1343 Recommended Run the errShow command to determine the IP location of the login attempt. Responses to Action security-class messages depend on user policies. Consult your security administrator for response strategies and policies. Severity WARNING FW-1343 Message <timestamp>, [FW-1343], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>).
Page 294: Fw-1346
FW-1346 Probable Cause Indicates that the number of invalid timestamps has fallen below the low boundary. Invalid-timestamp violations indicate a packet with an invalid timestamp has been received from the primary world-wide name (WWN). When the primary fabric configuration server (FCS) downloads a new configuration to other switches in the fabric, the packet is tagged with a timestamp.
Page 295: Fw-1348
FW-1348 FW-1348 Message <timestamp>, [FW-1348], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of invalid signatures has changed. Invalid-signature violations indicate that a packet with an invalid signature has been received from the primary fabric configuration server (FCS).
Page 296: Fw-1351
FW-1351 Severity WARNING FW-1351 Message <timestamp>, [FW-1351], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of invalid signatures has changed from a value outside of the acceptable range to a value within the acceptable range.
Page 297: Fw-1354
FW-1354 Probable Cause Indicates that the number of invalid certificates has fallen below the low boundary. This violation indicates that a packet with an invalid certificate has been received from the primary fabric configuration server (FCS). Before a new primary FCS switch sends any configuration data to any switch in the fabric, it first sends its certificate to all the switches in the fabric.
Page 298: Fw-1356
FW-1356 FW-1356 Message <timestamp>, [FW-1356], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of authentication failures has changed. Authentication failures can occur for many reasons. The switch on the other side might not support the protocol, have an invalid certificate, not be signed properly, or send unexpected packets.
Page 299: Fw-1359
FW-1359 FW-1359 Message <timestamp>, [FW-1359], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of authentication failures has changed from a value outside of the acceptable range to a value within the acceptable range.
Page 300: Fw-1362
FW-1362 FW-1362 Message <timestamp>, [FW-1362], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of switch link authentication protocol (SLAP) faulty packets has risen above the high boundary. This counter keeps track of the number of unexpected SLAP packets and SLAP packets with faulty transmission IDs.
Page 301: Fw-1366
FW-1366 Probable Cause Indicates that the number of time service (TS) out-of-sync violations has fallen below the low boundary. Recommended No action is required. Action Severity INFO FW-1366 Message <timestamp>, [FW-1366], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>.
Page 302: Fw-1369
FW-1369 Severity INFO FW-1369 Message <timestamp>, [FW-1369], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of no-FCS violations has fallen below the low boundary. This counter records how often the switch loses contact with the primary fabric configuration server (FCS) switch.
Page 303: Fw-1372
FW-1372 Probable Cause Indicates that the number of no-FCS violations has changed from a value outside of the acceptable range to a value within the acceptable range. This counter records how often the switch loses contact with the primary fabric configuration server (FCS) switch. When the primary FCS switch in the fabric sends its certificate to a switch, the receiving switch saves the world-wide name WWN of that primary FCS switch.
Page 304: Fw-1374
FW-1374 FW-1374 Message <timestamp>, [FW-1374], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of incompatible security database violations has risen above the high boundary. This violation indicates the number of secure switches with different version stamps have been detected.
Page 305: Fw-1377
FW-1377 FW-1377 Message <timestamp>, [FW-1377], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of illegal commands has fallen below the low boundary. This counter tracks how many times commands allowed only on the primary fabric configuration server (FCS) switch have been executed on a non-primary FCS switch.
Page 306: Fw-1400
FW-1400 Recommended No action is required. Action Severity INFO FW-1400 Message <timestamp>, [FW-1400], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the flash usage percentage has changed. Flash increases and decreases slightly with normal operation of the switch.
Page 307: Fw-1403
FW-1403 FW-1403 Message <timestamp>, [FW-1403], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the flash usage percentage has changed from a value outside of the acceptable range to a value within the acceptable range.
Page 308: Fw-1427
FW-1427 Recommended Replace the faulty or missing power supply. Action Severity WARNING FW-1427 Message <timestamp>, [FW-1427], <sequence-number>,, WARNING, <system-name>, Switch status <Number Bad> change contributing factor Power supply: bad. Probable Cause Indicates that the switch status is not in a healthy state. This occurred because the number of faulty power supplies is greater than or equal to the policy set by the switchStatusPolicySet command.
Page 309: Fw-1430
FW-1430 FW-1430 Message <timestamp>, [FW-1430], <sequence-number>,, WARNING, <system-name>, Switch status change contributing factor <string>. Probable Cause Indicates that the switch status is not in a healthy state. This occurred because the number of faulty temperature sensors is greater than or equal to the policy set by the switchStatusPolicySet command.
Page 310: Fw-1434
FW-1434 Probable Cause Indicates that the switch status is not in a healthy state. This occurred because the number of faulty CPs is greater than or equal to the policy set by the switchStatusPolicySet command. The CPs are non-redundant. If you power cycle a Brocade 24000 chassis in dual-domain configuration, and then reset the micro-switch of the active CP before the heartbeat is up, this will cause both CPs to come up in a non-redundant state.
Page 311: Fw-1437
FW-1437 Probable Cause Indicates that the switch status is not in a healthy state. This occurred because the number of marginal ports is greater than or equal to the policy set using the switchStatusPolicySet command. A port is faulty when the port value for Link Loss, Synchronization Loss, Signal Loss, Invalid word, Protocol error, cyclic redundancy check (CRC) error, Port state change or Buffer Limited Port is above the high boundary.
Page 312: Fw-1440
FW-1440 Recommended Run the switchEnable command. Action Severity WARNING FW-1440 Message <timestamp>, [FW-1440], <sequence-number>,, INFO, <system-name>, <FRU label> state has changed to <FRU state>. Probable Cause Indicates that the state of the specified field-replaceable unit (FRU) has changed to “absent”. Recommended No action is required.
Page 313: Fw-1444
FW-1444 Recommended No action is required. Verify that the event was planned. Action Severity INFO FW-1444 Message <timestamp>, [FW-1444], <sequence-number>,, WARNING, <system-name>, <FRU label> state has changed to <FRU state>. Probable Cause Indicates that the state of the specified field-replaceable unit (FRU) has changed to “faulty”. Recommended Replace the FRU.
Page 314: Fw-1500
FW-1500 Severity WARNING FW-1500 Message <timestamp>, [FW-1500], <sequence-number>,, WARNING, <system-name>, Mail overflow - Alerts being discarded. Probable Cause Indicates that mail alert overflow condition has occurred. Recommended Resolve or disable the mail alert using the fwMailCfg command. Action Severity WARNING FW-1501 Message <timestamp>, [FW-1501], <sequence-number>,, INFO, <system-name>, Mail overflow...
Page 315: Ham System Messages
Chapter HAM System Messages HAM-1001 Message <timestamp>, [HAM-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, Standby CP is not healthy, device <device name> status BAD, Severity = <Log="YES" Class="NONE" Severity> Probable Cause Indicates that a standby control processor (CP) device error is reported by the high-availability manager (HAM) Health Monitor, with a specific device and Log="YES”...
Page 316: Ham-1005
HAM-1005 • Unknown • Fastboot • Giveup Master:SYSM • CP Faulty:SYSM • FirmwareDownload • ConfigDownload:MS • ChangeWWN:EM • Reboot:WebTool • Fastboot:WebTool • Software Fault:Software Watchdog • Software Fault:Kernel Panic • Software Fault:ASSERT • Reboot:SNMP • Fastboot:SNMP • Reboot • Chassis Config •...
Page 317 HAM-1006 Recommended The standby CP will take over and reset the active CP.The system will be non-redundant as the Action standby becomes the active CP. Severity CRITICAL Fabric OS Message Reference 53-1000600-02...
Page 318 HAM-1006 Fabric OS Message Reference 53-1000600-02...
Page 319: Hamk-1001
Chapter HAMK System Messages HAMK-1001 Message <timestamp>, [HAMK-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, Warm recovery failed. Probable Cause The switch failed in the warm recovery. Recommended This message triggers a switch reboot automatically and attempts a cold recovery. RUn supportFtp Action (as needed) to set up automatic FTP transfers;...
Page 320: Hamk-1004
HAMK-1004 HAMK-1004 Message <timestamp>,[HAMK-1004], <sequence-number>,, INFO, <system-name>, Resetting standby CP (double reset may occur). Probable Cause Indicates that the standby control processor (CP) is being reset due to a loss of heartbeat. This message is typically seen when the standby CP has been rebooted. Note that in certain circumstances a CP may experience a double reset and reboot twice in a row.
Page 321: Hil-1101
Chapter HIL System Messages HIL-1101 Message <timestamp>, [HIL-1101], <sequence-number>,, ERROR, <system-name>, Slot <slot number> faulted, <nominal voltage> (<measured voltage>) is above threshold. Probable Cause Indicates that the blade voltage is above the threshold. Recommended Replace the faulty blade or switch (for nonbladed switches). Action Severity ERROR...
Page 322: Hil-1104
HIL-1104 HIL-1104 Message <timestamp>, [HIL-1104], <sequence-number>,, ERROR, <system-name>, Blower <blower number> faulted, <nominal voltage> (<measured voltage>) is below threshold. Probable Cause Indicates that the fan voltage is below the threshold. Recommended Run the psShow command to verify the power supply status. Action Try to reseat the faulty fan field-replaceable unit (FRU) and power supply FRU to verify that they are seated properly.
Page 323: Hil-1107
HIL-1107 HIL-1107 Message <timestamp>, [HIL-1107], <sequence-number>,, ERROR, <system-name>, Switch faulted, <nominal voltage> (<measured voltage>)above threshold. Probable Cause Indicates that the switch voltage is above threshold. This message is specific to nonbladed switches and is not applicable to the Brocade 24000, or 48000. Recommended For the Brocade 200E, 3250, 3850, 4012, 4016, 4018, 4020, and 4024 the entire switch must be Action...
Page 324: Hil-1202
HIL-1202 If the fan continues to generate this message, replace the fan field-replaceable unit (FRU). Severity WARNING HIL-1202 Message <timestamp>, [HIL-1202], <sequence-number>,, ERROR, <system-name>, Blower <blower number> faulted, speed (<measured speed> RPM) below threshold. Probable Cause Indicates that the specified fan speed (in RPM) has fallen below the minimum threshold. Recommended Replace the fan field-replaceable unit (FRU).
Page 325: Hil-1206
HIL-1206 HIL-1206 Message <timestamp>, [HIL-1206], <sequence-number>,, ERROR, <system-name>, Fan <fan number> sensor <sensor number> , speed (<measured speed> RPM) below threshold. Probable Cause Indicates that the specified fan speed (in RPM) has fallen below the minimum threshold. This problem can quickly cause the switch to overheat. This message is specific to nonbladed switches and is not applicable to the Brocade 24000, or 48000.
Page 326: Hil-1301
HIL-1301 HIL-1301 Message <timestamp>, [HIL-1301], <sequence-number>,, WARNING, <system-name>, 1 blower failed or missing. Replace failed or missing blower assembly immediately. Probable Cause Indicates that a fan field-replaceable unit (FRU) has failed or has been removed. This message is often preceded by a low speed error message. This problem can cause the switch to overheat. Recommended Replace the affected fan FRU immediately.
Page 327: Hil-1305
HIL-1305 Severity ERROR HIL-1305 Message <timestamp>, [HIL-1305], <sequence-number>,, ERROR, <system-name>, One or two fan(s) failed. Replace failed fan FRUs immediately. Probable Cause Indicates that multiple fan field-replaceable units (FRUs) have failed. This message is often preceded by a low fan speed message. Recommended Replace the faulty fan FRUs immediately.
Page 328: Hil-1309
HIL-1309 Recommended Replace the faulty fan field-replaceable units (FRUs) immediately. Action Severity ERROR HIL-1309 Message <count> <timestamp>, [HIL-1309], <sequence-number>,, ERROR, <system-name>, FRUs failed. Replace failed fan FRUs immediately. Probable Cause Indicates that multiple fans have failed. This message is often preceded by a low fan speed message.
Page 329: Hil-1402
HIL-1402 Probable Cause Indicates that one fan field-replaceable unit (FRU) has been removed. Recommended Install the missing fan FRU. Action Severity WARNING HIL-1402 Message <timestamp>, [HIL-1402], <sequence-number>,, WARNING, <system-name>, Two fan FRUs missing. Install fan FRUs immediately. Probable Cause Indicates that two fan field-replaceable units (FRUs) have been removed. Recommended Install the missing fan FRUs immediately.
Page 330: Hil-1502
HIL-1502 Recommended Run the fanShow command to verify all the fans are working properly. Action Make sure that the area is well ventilated and that the room temperature is within operational range of your switch. Refer to the hardware reference manual for your switch for the operational temperature range.
Page 331: Hil-1505
HIL-1505 Recommended No action is required. Action Severity INFO HIL-1505 Message <timestamp>, [HIL-1505], <sequence-number>,, WARNING, <system-name>, High <measured temperature> temperature ( C) exceeds environmental specifications. Probable Cause Indicates that temperatures in the system have risen above the warning threshold. Recommended Run the fanShow command to verify all the fans are working properly.
Page 332: Hil-1508
HIL-1508 HIL-1508 Message <timestamp>, [HIL-1508], <sequence-number>, FFDC, CRITICAL, <system-name>, Fan faulty warning time expired. System preparing for shutdown. Probable Cause Indicates that temperatures in the system have remained above the critical threshold too long. Recommended In order to avoid causing damage to the switch, the system shuts down automatically. To help Action prevent future problems, make sure that all the fans are working properly.
Page 333: Hil-1601
HIL-1601 HIL-1601 Message <timestamp>, [HIL-1601], <sequence-number>,, ERROR, <system-name>, Using backup temperature sensor. Service immediately. Probable Cause Indicates that temperature readings from the primary sensor are out of range. Recommended Run the fanShow command to verify that all fans are operating correctly. Replace any deteriorating Action fan field-replaceable units (FRUs).
Page 334 HIL-1650 Severity ERROR Fabric OS Message Reference 53-1000600-02...
Page 335: Hlo-1001
Chapter HLO System Messages HLO-1001 Message <timestamp>, [HLO-1001], <sequence-number>, FFDC, ERROR, <system-name>, Incompatible Inactivity timeout <dead timeout> from port <port number>, correct value <value>. Probable Cause Indicates that the HLO message was incompatible with the value specified in the FSPF protocol. The Brocade switch will not accept FSPF frames from the remote switch.
Page 336 HLO-1003 The switch has received an invalid HLO because either the domain or port number in the HLO message has an invalid value. This error can only occur when the Brocade switch is connected to a switch from another manufacturer. Recommended The HLO message of the remote switch must be compatible with the value specified in the FSPF Action...
Page 337: Hmon-1001
Chapter HMON System Messages HMON-1001 Message <timestamp>, [HMON-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, <Failure description> Probable Cause Indicates that there was a problem reading an essential file containing configuration information from the nonvolatile storage device. This could be the result of a missing file or a corrupt file system.
Page 338 HMON-1001 Fabric OS Message Reference 53-1000600-02...
Page 339: Http-1001
Chapter HTTP System Messages HTTP-1001 Message <timestamp>, [HTTP-1001], <sequence-number>,, INFO, <system-name>, Switch <current PID format> PIDformat has changed to Probable Cause Indicates that the PID format was changed by the administrator. Recommended No action is required. For more information on PID, format refer to the Fabric OS Administrator’s Action Guide.
Page 340 HTTP-1003 Fabric OS Message Reference 53-1000600-02...
Page 341: Ibd-1001
Chapter IBD System Messages IBD-1001 Message <timestamp>, [FKLB-1001], <sequence-number>,, ERROR, <system-name>, Slot <slot number>, Port GE<port number>: Maximum attempts to restart failed. Disabling port. Probable Cause Indicates that the specified port has crashed unexpectedly and restarting attempts have failed. Recommended Power off and power on the blade using the slotPowerOff and slotPowerOn commands.
Page 342 IBD-1001 Fabric OS Message Reference 53-1000600-02...
Page 343: Ibpd-1001
Chapter IBPD System Messages IBPD-1001 Message <timestamp>, [IBPD-1001], <sequence-number>,, WARNING, <system-name>, <Function name>:<Line number> initiator name length exceeds the <Max length limit> character limit [<Initiator name>] Probable Cause Indicates that the initiator name length exceeds the supported limit of characters. Recommended Change the initiator name, keeping the number of characters within the supported limit.
Page 344 IBPD-1003 Fabric OS Message Reference 53-1000600-02...
Page 345: Icpd-1001
Chapter ICPD System Messages ICPD-1001 Message <timestamp>, [ICPD-1001], <sequence-number>,, ERROR, <system-name>, Failed to <function name> allocate memory: ( Probable Cause Indicates that the specified function failed to allocate memory. Recommended Check memory usage on the switch using the memShow command. Action Reboot or power cycle the switch.
Page 346: Icpd-1005
ICPD-1005 Recommended Enable the iSNS Client service on a single switch in the fabric using the fosConfig command. Refer Action to the Fabric OS Command Reference for more information on this command. Severity WARNING ICPD-1005 Message <timestamp>, [ICPD-1005], <sequence-number>,, WARNING, <system-name>, iSCSI configuration between local switch (<local domain id>) and peer (<peer domain id>) is out of sync.
Page 347 ICPD-1008 Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1000600-02...
Page 348 ICPD-1008 Fabric OS Message Reference 53-1000600-02...
Page 349: Ipad-1000
Chapter IPAD System Messages IPAD-1000 Message <timestamp>, [IPAD-1000], <sequence-number>,, INFO, <system-name> <Type of managed entity> <Instance number of managed entity> <Type of network interface> <Instance number of network interface> <Protocol address family> <Source of address change> <Value of address and prefix> <DHCP enabled or not> Probable Cause Indicates that a change in local IP address has occurred.
Page 350 DRAFT: BROCADE CONFIDENTIAL IPAD-1001 Fabric OS Message Reference 53-1000600-02...
Page 351: Ips-1001
Chapter IPS System Messages IPS-1001 Message <timestamp>, [IPS-1001], <sequence-number>,, WARNING, <system-name>, <message> FCIP License Not Installed (<error>) Probable Cause Indicates that the FCIP license is not installed on the switch. Recommended Run the licenseShow command to check the installed licenses on the switch. Contact your switch Action supplier for a FCIP license.
Page 352: Ips-1005
IPS-1005 Probable Cause Indicates that configured Port Mode is different from intended use. Recommended Change the port configuration (by deleting configured FCIP tunnels or iSCSI sessions) to return the Action port mode to neutral before attempting to configure the port for a different mode or use. Severity WARNING IPS-1005...
Page 353: Iscs-1000
Chapter ISCS System Messages ISCS-1000 Message <timestamp>, [ISCS-1000], <sequence-number>,, ERROR, <system-name>, Slot <slot number> Port GE<port number> crashed unexpectedly. Probable Cause Indicates that specified port has crashed. Recommended No action is required; the port will restart automatically. Action Severity ERROR Fabric OS Message Reference 53-1000600-02...
Page 354 ISCS-1000 Fabric OS Message Reference 53-1000600-02...
Page 355: Isns-1001
Chapter ISNS System Messages ISNS-1001 Message <timestamp>, [ISNS-1001], <sequence-number>,, INFO, <system-name>, Configuration peering with external iSNS server <New config iSNS server IP address> slot/port <New config Slot number>/ge<New config port number> (current <Current iSNS server IP address> <Current slot number>/ge<Current port number>). Probable Cause Indicates that the user has issued the isnscCfg command.
Page 356: Isns-1004
ISNS-1004 ISNS-1004 Message <timestamp>, [ISNS-1004], <sequence-number>,, WARNING, <system-name>, Timeout refreshing iSNS database with iSNS server <iSNS server IP address> slot/port <Slot number>/ge<Port number> Reg-Period <Registration-Period in seconds>. Probable Cause Indicates that the internet storage name service (iSNS) client failed to receive a successful response for a DevAttrQry within the specified Registration-Period.
Page 357: Isns-1009
ISNS-1009 Recommended No action is required. You may change the configuration and retry the peering with the external Action iSNS server. Severity INFO ISNS-1009 Message <timestamp>, [ISNS-1009], <sequence-number>,, INFO, <system-name>, Peering with external iSNS server <iSNS server IP address>not started because no virtual targets found.
Page 358: Isns-1014
ISNS-1014 Probable Cause Indicates that the internet storage name service (iSNS) client failed to establish a connection with the iSNS server. Recommended Verify the connection of the iSNS server to the slot/port. Use the isnscCfg command to display or Action correct the server IP address.
Page 359: Kswd-1003
Chapter KSWD System Messages KSWD-1003 Message <timestamp>, [KSWD-1003], <sequence-number>, FFDC, WARNING, <system-name>, kSWD: <Warning message>. Probable Cause Indicates a warning state within the system. A critical application error was reported in the watchdog subsystem. Refer to the string at the end of the error message for specific information.
Page 360 KSWD-1003 Fabric OS Message Reference 53-1000600-02...
Page 361: Ktrc-1001
Chapter KTRC System Messages KTRC-1001 Message <timestamp>, [KTRC-1001], <sequence-number>,, WARNING, <system-name>, Dump memory size exceeds dump file size Probable Cause Indicates that the dump memory size has exceeded the dump file size. Recommended No action is required. Action Severity WARNING KTRC-1002 Message <timestamp>, [KTRC-1002], <sequence-number>,, INFO, <system-name>, Concurrent...
Page 362: Ktrc-1005
KTRC-1005 Recommended No action is required. Action Severity ERROR KTRC-1005 Message <timestamp>, [KTRC-1005], <sequence-number>,, ERROR, <system-name>, Trace initialization failed. <Reason initialization failed>. <Internal error code>. Probable Cause Indicates that Trace was unable to initialize. Recommended No action is required. Action Severity ERROR Fabric OS Message Reference...
Page 363: Log-1000
Chapter LOG System Messages LOG-1000 Message <timestamp>, [LOG-1000], <sequence-number>,, INFO, <system-name>, Previous <repeat count> message repeated time(s) Probable Cause Indicates that the previous message repeated the specified number of times. Recommended No action is required. Action Severity INFO LOG-1001 Message <timestamp>, [LOG-1001], <sequence-number>, FFDC, WARNING, <system-name>, A log message was dropped Probable Cause...
Page 364: Log-1003
LOG-1003 LOG-1003 Message <timestamp>, [LOG-1003], <sequence-number>,, INFO, <system-name>, The log has been cleared. Probable Cause Indicates that the persistent error log has been cleared. Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1000600-02...
Page 365: Lsdb-1001
Chapter LSDB System Messages LSDB-1001 Message <timestamp>, [LSDB-1001], <sequence-number>,, ERROR, <system-name>, Link State ID <link state ID> out of range Probable Cause Indicates that the specified link state database ID is out of the acceptable range. The valid link state ID is the same as the valid domain ID, whose range is from 1 through 239. The switch will discard the record because it is not supported.
Page 366: Lsdb-1004
LSDB-1004 Recommended Run the switchDisable and switchEnable commands. A new local link state record is generated Action during the switch enable. Severity CRITICAL LSDB-1004 Message <timestamp>, [LSDB-1004], <sequence-number>,, WARNING, <system-name>, No Link <local domain> State Record for domain Probable Cause Indicates that there is no link state record for the specified local domain.
Page 367: Mfic-1001
Chapter MFIC System Messages MFIC-1001 Message <timestamp>, [MFIC-1001], <sequence-number>,, ERROR, <system-name>, failure at <failure reason> sysmod_scn registry rc= Probable Cause Indicates that the system is temporarily out of resources. Recommended No action is required; this message is often transitory. Action If the message persists, run a switch reboot or an haFailover (if applicable).
Page 368 MFIC-1003 IDID mode can be set using the configure command in the CLI or checking the Advanced Web Tools Switch Admin > Configure Tab > Fabric Subtab > Insistent Domain ID Mode checkbox. The switch must be disabled to change the IDID mode. Severity WARNING Fabric OS Message Reference...
Page 369: Mpth-1001
Chapter MPTH System Messages MPTH-1001 Message <timestamp>, [MPTH-1001], <sequence-number>, FFDC, ERROR, <system-name>, Null <number> parent, lsId = Probable Cause Indicates that a null parent was reported. MPATH uses a tree structure in which the parent is used to connect to the root of the tree. Recommended No action is required.
Page 370 MPTH-1003 Fabric OS Message Reference 53-1000600-02...
Page 371: Mq-1004
Chapter MQ System Messages MQ-1004 Message <timestamp>, [MQ-1004], <sequence-number>,, ERROR, <system-name>, mqRead, queue = <queue name>, queue ID = <queue ID>, type = <message type> Probable Cause Indicates that an unexpected message has been received in the specified message queue. The queue name is always fspf_q.
Page 372 MQ-1004 Fabric OS Message Reference 53-1000600-02...
Page 373: Ms-1001
Chapter MS System Messages MS-1001 Message <timestamp>, [MS-1001], <sequence-number>,, WARNING, <system-name>, MS Platform Segmented port=<port number>(<reason for segmentation> <domain>) Probable Cause Indicates that the management server (MS) has segmented from another switch domain at the specified port number due to errors or inconsistencies defined in the MS platform service. Recommended Reboot or power cycle the switch.
Page 374: Ms-1003
MS-1003 • <GCAP Rejected (reason =BUSY) by> Run the firmwareDownload command to upgrade the firmware level on the switch to a level that supports RCS. RCS is supported in Fabric OS v2.6, v3.1 and greater, and v4.1 and greater. • <Reject EXGPLDB from>...
Page 375: Ms-1005
MS-1005 Severity INFO MS-1005 Message <timestamp>, [MS-1005], <sequence-number>,, ERROR, <system-name>, MS Invalid CT <domain> Response from d= Probable Cause Indicates that the management server (MS) received an invalid common transport (CT) response from switch domain. MS expects either a CT accept IU or a reject IU; MS received neither response, which violates the Fibre Channel Generic Services (FS-GS) specification.
Page 376: Ms-1009
MS-1009 MS-1009 Message <timestamp>, [MS-1009], <sequence-number>,, ERROR, <system-name>, RLIR event. Switch Port ID is <PID>. Device Port Tag is <port tag>. <message>. Probable Cause A Registered Link Incident Record (RLIR) has been generated for one of the actions clarified by the <message>...
Page 377: Ms-1023
MS-1023 MS-1023 Message <timestamp>, [MS-1023], <sequence-number>,, INFO, <system-name>, Management <Enabled or Disabled> Server Topology Discovery Service Probable Cause Indicates that Management Server Topology Discovery Service is being enabled or disabled. Recommended No action is required. Action Severity INFO MS-1024 Message <timestamp>, [MS-1024], <sequence-number>,, INFO, <system-name>, Management Server Access Control List is Updated Probable Cause...
Page 378 MS-1024 Fabric OS Message Reference 53-1000600-02...
Page 379: Nbfs-1001
Chapter NBFS System Messages NBFS-1001 Message <timestamp>, [NBFS-1001], <sequence-number>,, INFO, <system-name>, Duplicate E_Port SCN from port <portnumber> in state <state change name> (<state change number>) Probable Cause Indicates that a duplicate E_Port State Change Number was reported. The neighbor finite state machine (NBFSM) states are as follows: •...
Page 380: Nbfs-1003
NBFS-1003 Severity ERROR NBFS-1003 Message <timestamp>, [NBFS-1003], <sequence-number>,, WARNING, <system-name>, DB_XMIT_SET flag not set in state <current state name>, input <state name>, port <portnumber> Probable Cause Indicates that the database transmit set flag was not set for the specified input state on the specified port.
Page 381: Ns-1001
Chapter NS System Messages NS-1001 Message <timestamp>, [NS-1001], <sequence-number>,, WARNING, <system-name>, The response for request 0x<CT command code> from remote switch 0x<Domain Id> is larger than the max frame size the remote switch can support! Probable Cause Indicates that the response payload exceeds the maximum frame size that the remote switch can handle.
Page 382: Ns-1004
NS-1004 Recommended To avoid disruption of traffic in the event of an unplanned failover, schedule a firmwareDownload Action so that the active and standby CPs have the same firmware version. Reduce the local device count to follow the capability of the lowest version of firmware. Severity INFO NS-1004...
Page 383: Pdm-1001
Chapter PDM System Messages PDM-1001 Message <timestamp>, [PDM-1001], <sequence-number>,, WARNING, <system-name>, Failed to parse the pdm config. Probable Cause Indicates that the parity data manager (PDM) process could not parse the configuration file. This might be caused by a missing configuration file during the installation. Recommended Run the firmwareDownload command to reinstall the firmware.
Page 384: Pdm-1004
PDM-1004 PDM-1004 Message <timestamp>, [PDM-1004], <sequence-number>,, WARNING, <system-name>, PDM memory shortage. Probable Cause Indicates that the parity data manager (PDM) process ran out of memory. Recommended Reboot or power cycle the switch. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
Page 385: Pdm-1008
PDM-1008 Recommended Run the firmwareDownload command to reinstall the firmware. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING PDM-1008 Message <timestamp>, [PDM-1008], <sequence-number>,, WARNING, <system-name>, Failed to get the number of U_Ports.
Page 386: Pdm-1011
PDM-1011 PDM-1011 Message <timestamp>, [PDM-1011], <sequence-number>,, WARNING, <system-name>, File read failed: <file name>, Length(read=<Number of character read>, expected=<Number of characters expected>), errno=<errno returned by read>. Probable Cause Indicates that the parity data manager (PDM) process could not read data from the specified file. Recommended Run the firmwareDownload command to reinstall the firmware.
Page 387: Pdm-1017
PDM-1017 Recommended Run the firmwareDownload command to reinstall the firmware. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING PDM-1017 Message <timestamp>, [PDM-1017], <sequence-number>, FFDC, CRITICAL, <system-name>, System (<Error Code>): <Command>.
Page 388: Pdm-1021
PDM-1021 PDM-1021 Message <timestamp>, [PDM-1021], <sequence-number>,, WARNING, <system-name>, Failed to download area port map. Probable Cause Indicates that a system call failed. Recommended Run the firmwareDownload command to reinstall the firmware. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
Page 389 PDM-1024 Recommended Run the firmwareDownload command to reinstall the firmware. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING Fabric OS Message Reference 53-1000600-02...
Page 390 PDM-1024 Fabric OS Message Reference 53-1000600-02...
Page 391: Pdtr-1001
Chapter PDTR System Messages PDTR-1001 Message < <timestamp>, [PDTR-1001], <sequence-number>,, INFO, <system-name>, informational message > Probable Cause Indicates that information has been written to the panic dump files. The watchdog register codes are as follows: • 0x10000000 bit set means that the watch dog timer (WDT) forced a core reset. •...
Page 392 PDTR-1002 Fabric OS Message Reference 53-1000600-02...
Page 393: Plat-1000
Chapter PLAT System Messages PLAT-1000 Message <timestamp>, [PLAT-1000], <sequence-number>, FFDC, CRITICAL, <system-name>, <Function name> <Error string> Probable Cause Indicates that nonrecoverable PCI errors have been detected. Recommended The system will be faulted and might automatically reboot. Action If the system does not reboot, then try issuing the reboot command from a command-line prompt. Run supportFtp (as needed) to set up automatic FTP transfers;...
Page 394: Plat-1003
PLAT-1003 Severity CRITICAL PLAT-1003 Message <timestamp>, [PLAT-1003], <sequence-number>, FFDC, CRITICAL, <system-name>, <Info message> Slot <Blade Slot number> C/BE: <Captured Command/Byte-Enables data> ADBUS: <Captured AD bus data> misc_intr <Bridge reset interrupts>. Probable Cause Indicates that a PCI bus hang was detected. Recommended The FRU must be replaced.
Page 395: Port-1003
Chapter PORT System Messages PORT-1003 Message <port <timestamp>, [PORT-1003], <sequence-number>,, WARNING, <system-name>, Port number> Faulted because of many Link Failures Probable Cause Indicates that the specified port is now disabled because the link on this port had multiple failures that exceed an internally set threshold on the port. This problem is typically related to hardware. Recommended Check and replace (if necessary) the hardware attached to both ends of the specified port number, Action...
Page 396 PORT-1005 Recommended Invoke the portCfgLport to clear the L_port configuration. Action Severity WARNING Fabric OS Message Reference 53-1000600-02...
Page 397: Ps-1000
Chapter PS System Messages PS-1000 Message <timestamp>, [PS-1000], <sequence-number>, FFDC, CRITICAL, <system-name>, Failed to initialize Advanced Performance Monitoring. Probable Cause Indicates that an unexpected software error has occurred in Advanced Performance Monitoring. The Performance Monitor has failed to initialize. Recommended The CP should reboot (or fail over) automatically.
Page 398: Ps-1004
PS-1004 Probable Cause Indicates that the restoring configuration has attempted to set the end-to-end monitoring mask on at least one ISL port. Recommended No action is required. End-to-end monitoring is not supported on ISL ports when ISL monitoring is Action enabled.
Page 399: Pswp-1001
Chapter PSWP System Messages PSWP-1001 Message <timestamp>, [PSWP-1001], <sequence-number>,, INFO, <system-name>, Areas for port <wwn name corresponding to source port> and port <wwn name corresponding to destination port> are swapped. New area for port <wwn name corresponding to source port> is <wwn name corresponding to destination port> and port <new area corresponding to source wwn>...
Page 400 PSWP-1003 Fabric OS Message Reference 53-1000600-02...
Page 401: Ras-1001
Chapter RAS System Messages RAS-1001 Message <timestamp>, [RAS-1001], <sequence-number>,, INFO, <system-name>, First failure data capture (FFDC) event occurred. Probable Cause Indicates that a failure happened and the failure data was captured. Recommended Run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command Action and contact your switch service provider.
Page 402: Ras-1006
RAS-1006 Probable Cause Indicates an internal software error. Recommended Run the supportSave command and contact your switch service provider. Action Severity WARNING RAS-1006 Message <timestamp>, [RAS-1006], <sequence-number>, INFO, <system-name>, Support data file (<Uploaded file name>) automatically transferred to remote address ' <Remote target designated by user>...
Page 403: Ras-3001
RAS-3001 Probable Cause A user has changed the configured classes of the audit feature. Recommended No action is required. Action Severity INFO RAS-3001 Message <timestamp>, [RAS-3001], <sequence-number>, INFO, <system-name>, USB storage device plug-in detected. Probable Cause Indicates that the USB storage device plug-in is being detected. Recommended No action is required.
Page 404 RAS-3004 Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1000600-02...
Page 405: Rcs-1001
Chapter RCS System Messages RCS-1001 Message <timestamp>, [RCS-1001], <sequence-number>,, INFO, <system-name>, RCS has been disabled. Some switches in the fabric do not support this feature. Probable Cause Indicates that the RCS feature has been disabled on the local switch because not all switches in the fabric support RCS or the switch is in nonnative mode.
Page 406: Rcs-1004
RCS-1004 RCS-1004 Message <timestamp>, [RCS-1004], <sequence-number>,, ERROR, <system-name>, Application(<application name>) not registered.(<error string>) Probable Cause Indicates that a specified application did not register with RCS. Recommended Run the haShow command to view the HA state. Action Run the haDisable and the haEnable commands. Run the rcsInfoShow command to view RCS capability on the fabric.
Page 407: Rcs-1007
RCS-1007 Severity INFO RCS-1007 Message <timestamp>, [RCS-1007], <sequence-number>,, ERROR, <system-name>, Zone DB size and propogation overhead exceeds domain <domain number>'s maximum supported Zone DB size <max zone db size>. Retry after reducing the Zone DB size. Probable Cause Indicates that a domain cannot handle the zone database being committed. Recommended Reduce the zone database size.
Page 408 RCS-1008 Fabric OS Message Reference 53-1000600-02...
Page 409: Rpcd-1001
Chapter RPCD System Messages RPCD-1001 Message <timestamp>, [RPCD-1001], <sequence-number>,, WARNING, <system-name>, Authentication Error: client \"<IP address>\" has bad credentials: <bad user name and password pair> Probable Cause Indicates that an authentication error was reported. The specified client IP address has faulty credentials.
Page 410: Rpcd-1004
RPCD-1004 RPCD-1004 Message <timestamp>, [RPCD-1004], <sequence-number>,, WARNING, <system-name>, Invalid certificate file. Secure RPCd is disabled. Probable Cause Indicates that the SSL certificate file has been corrupted. Recommended To enable RPCD in Secure mode, install a valid SSL certificate the switch. Action Severity WARNING...
Page 411: Rtwr-1001
Chapter RTWR System Messages RTWR-1001 Message <timestamp>, [RTWR-1001], <sequence-number>,, ERROR, <system-name>, RTWR <routine: error message> 0x<detail 1>, 0x<detail 2>, 0x<detail 3>, 0x<detail 4>, 0x<detail 5> Probable Cause Indicates that an error occurred in the RTWR. The message provides the name of the routine having the error, and more specific error information.
Page 412: Rtwr-1003
RTWR-1003 RTWR-1003 Message <timestamp>, [RTWR-1003], <sequence-number>,, INFO, <system-name>, <module name>: RTWR retry <number of times retried> to domain <domain ID>, iu_data <first word of iu_data> Probable Cause Indicates how many times RTWR failed to get a response and retried. Recommended Run the dom command to verify that the specified domain ID is reachable.
Page 413: Sas-1001
Chapter SAS System Messages SAS-1001 Message <timestamp>, [SAS-1001], <sequence-number>,, ERROR, <system-name>, string description of command which failed> of GE <GE port number which failed> failed. Please retry the command. Data inst=<chip instance> st=<chip init state> rsn=<failure reason> fn=<message function> oid=<chip OID>. Probable Cause The Hardware is not responding to the command request;...
Page 414 SAS-1001 Fabric OS Message Reference 53-1000600-02...
Page 415: Scn System Messages
Chapter SCN System Messages SCN-1001 Message <timestamp>, [SCN-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, SCN <daemon name> queue overflow for process Probable Cause Indicates that an attempt to write a state change notification (SCN) message to a specific queue has failed because the SCN queue for the specified daemon name is full. This might be caused by the daemon hanging or if the system is busy.
Page 416 SCN-1001 Fabric OS Message Reference 53-1000600-02...
Page 417: Sec-1001
Chapter SEC System Messages SEC-1001 Message <timestamp>, [SEC-1001], <sequence-number>,, ERROR, <system-name>, RCS process <reason code> fails: Probable Cause Indicates that the reliable commit service (RCS) process fails to complete. RCS is a mechanism for transferring data from one switch to other switches within the fabric. RCS ensures that either all or none of the switches commit to the database.
Page 418: Sec-1003
SEC-1003 SEC-1003 Message <timestamp>, [SEC-1003], <sequence-number>,, WARNING, <system-name>, Fail to download security data to domain <Domain number> after <Number of retires> retries Probable Cause Indicates that the specified domain failed to download security data after the specified number of attempts, and that the failed switch encountered an error accepting the database download. The primary switch will segment the failed switch after 30 tries.
Page 419: Sec-1007
SEC-1007 SEC-1007 Message <timestamp>, [SEC-1007], <sequence-number>,, INFO, <system-name>, Security <IP address of the violating violation: Unauthorized host with IP address host> tries to establish API connection. Probable Cause Indicates that a security violation was reported. The IP address of the unauthorized host is displayed in the message.
Page 420: Sec-1022
SEC-1022 Recommended Check for unauthorized access to the switch through the SSH connection. Action Severity INFO SEC-1022 Message <timestamp>, [SEC-1022], <sequence-number>,, WARNING, <system-name>, Failed to <operation> PKI objects. Probable Cause Indicates that the fabric failed to generate or validate either the public or private key pair or the certificate signing request (CSR).
Page 421: Sec-1026
SEC-1026 SEC-1026 Message <timestamp>, [SEC-1026], <sequence-number>,, ERROR, <system-name>, Invalid format <switch member ID> or character in switch member Probable Cause Indicates that a corruption occurred during the distribution of the security database. This can occur only when the primary fabric configurations server (FCS) distributes the security database to the other switches in the fabric, then local validation finds the error in the security database.
Page 422: Sec-1030
SEC-1030 SEC-1030 Message <timestamp>, [SEC-1030], <sequence-number>, ERROR, <system-name>, The length of the name invalid. Probable Cause Indicates that a corruption occurred during the distribution of the security database. This can occur only when the primary fabric configurations server (FCS) distributes the security database to the other switches in the fabric, then local validation finds the error in the security database.
Page 423: Sec-1034
SEC-1034 Probable Cause Indicates that a member parameter in the secPolicyAdd command is invalid (e. g., it may include an invalid character, such as an asterisk). A valid switch identifier (a WWN, a domain ID, or a switch name) must be provided as a member parameter in the secPolicyAdd command. Only the secPolicyCreate command supports use of the asterisk for adding switches to policies.
Page 424: Sec-1037
SEC-1037 SEC-1037 Message <timestamp>, [SEC-1037], <sequence-number>,, ERROR, <system-name>, Invalid WWN <invalid WWN> format Probable Cause Indicates that the world-wide name (WWN) entered in the policy member list had an invalid format. Recommended Run the command again using the standard WWN format, 16 hexadecimal digits grouped as eight Action colon separated pairs.
Page 425: Sec-1042
SEC-1042 Severity ERROR SEC-1042 Message <timestamp>, [SEC-1042], <sequence-number>,, ERROR, <system-name>, Invalid index/area member <port member> in portlist (<Port list>). Out of range (<Minimum value> - <Maximum value>). Probable Cause Indicates that the specified index or area member is not within the minimum and maximum range. Recommended Use valid syntax when entering index or area numbers.
Page 426: Sec-1046
SEC-1046 Recommended Run the secFabricShow command to verify that the fabric is still consistent. All the switches should Action be in the ready state. If a switch is in the error state, the database might not be correctly updated for that specific switch. Severity ERROR SEC-1046...
Page 427: Sec-1051
SEC-1051 Severity ERROR SEC-1051 Message <timestamp>, [SEC-1051], <sequence-number>,, ERROR, <system-name>, Missing brace <port list> for port list Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.
Page 428: Sec-1054
SEC-1054 SEC-1054 Message <timestamp>, [SEC-1054], <sequence-number>,, ERROR, <system-name>, Invalid FCS <list length> list length Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.
Page 429: Sec-1057
SEC-1057 SEC-1057 Message <timestamp>, [SEC-1057], <sequence-number>,, ERROR, <system-name>, No change. Both positions are the same. Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.
Page 430: Sec-1064
SEC-1064 Severity ERROR SEC-1064 Message <timestamp>, [SEC-1064], <sequence-number>,, ERROR, <system-name>, Failed to sign message. Probable Cause Indicates that the public key infrastructure (PKI) objects on the switch are not in a valid state and the signature operation failed. Recommended Run the pkiShow command to verify that all PKI objects are valid. If PKI objects are not valid, Action generate the PKI objects and install the certificate by following the field upgrade process.
Page 431: Sec-1072
SEC-1072 Severity ERROR SEC-1072 Message <Policy <timestamp>, [SEC-1072], <sequence-number>,, ERROR, <system-name>, type> Policy List is Empty! Probable Cause Indicates that the specific policy type is empty. The security database is corrupted for unknown reasons. Recommended Run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command Action and contact your switch service provider.
Page 432: Sec-1076
SEC-1076 Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.
Page 433: Sec-1079
SEC-1079 SEC-1079 Message <timestamp>, [SEC-1079], <sequence-number>,, ERROR, <system-name>, The policy <policy name> name is invalid. Probable Cause Indicates that the policy name entered in the secPolicyCreate|Activate|Add|Delete command was invalid. Recommended Run the command again using a valid policy name. Action Severity ERROR SEC-1080...
Page 434: Sec-1083
SEC-1083 Recommended Use proper syntax when creating policies. If the security database is too large, you must delete Action other members within the database before adding new members to a policy. Severity ERROR SEC-1083 Message <timestamp>, [SEC-1083], <sequence-number>,, ERROR, <system-name>, Name already exists.
Page 435: Sec-1087
SEC-1087 Probable Cause Indicates that the security database has more data than the flash can accommodate. Recommended Reduce the number of entries in some policies to decrease the security database size. Action Severity ERROR SEC-1087 Message <timestamp>, [SEC-1087], <sequence-number>,, ERROR, <system-name>, The security <fabric data database is larger than the data distribution limit of fabric distribution limit>...
Page 436: Sec-1090
SEC-1090 SEC-1090 Message <timestamp>, [SEC-1090], <sequence-number>,, ERROR, <system-name>, SCC list contains FCS member. Please remove member from the FCS policy first. Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.
Page 437: Sec-1094
SEC-1094 Probable Cause Indicates that the new fabric configurations server (FCS) list does not have a common member with the existing FCS list. Recommended Resubmit the command with at least one member of the new FCS list in common with the current Action FCS list.
Page 438: Sec-1097
SEC-1097 Severity ERROR SEC-1097 Message <timestamp>, [SEC-1097], <sequence-number>,, ERROR, <system-name>, Cannot find <active or defined> policy set. Probable Cause Indicates that the specified policy could not be found. Recommended If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the Action supportSave command and contact your switch service provider.
Page 439: Sec-1101
SEC-1101 Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.
Page 440: Sec-1105
SEC-1105 Recommended Verify that the primary switch has a valid certificate installed and retry the operation. If a valid Action certificate is not installed, install a certificate by following the procedure specified in the Secure Fabric OS Administrator's Guide. Severity ERROR SEC-1105 Message...
Page 441: Sec-1108
SEC-1108 SEC-1108 Message <timestamp>, [SEC-1108], <sequence-number>,, ERROR, <system-name>, Fail to reset stamp on all switches. Probable Cause Indicates that a version reset operation failed either because the switch could not get all the required resources to perform the operation or because it failed to send the message to all switches in the fabric.
Page 442: Sec-1113
SEC-1113 Probable Cause Indicates that either a security policy download is attempted with an active policy that does not have the fabric configurations server (FCS) policy as the first policy or the FCS policy is not same as the current FCS policy on the switch. Recommended Make sure that the new FCS policy is the same as the current FCS policy on the switch.
Page 443: Sec-1116
SEC-1116 SEC-1116 Message <timestamp>, [SEC-1116], <sequence-number>,, ERROR, <system-name>, Fail to commit failover. Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.
Page 444: Sec-1121
SEC-1121 Recommended Verify that the security event was planned. If the security event was planned, there is no action Action required. If the security event was not planned, take appropriate action as defined by your enterprise security policy. Severity INFO SEC-1121 Message <timestamp>, [SEC-1121], <sequence-number>,, ERROR, <system-name>, Time is out of...
Page 445: Sec-1124
SEC-1124 SEC-1124 Message <timestamp>, [SEC-1124], <sequence-number>,, INFO, <system-name>, Secure Mode is off. Probable Cause Indicates that a secure mode disable is attempted in a non-secure fabric. Recommended No action is required. Action Severity INFO SEC-1126 Message <timestamp>, [SEC-1126], <sequence-number>,, INFO, <system-name>, Secure mode has been disabled.
Page 446: Sec-1136
SEC-1136 SEC-1136 Message <timestamp>, [SEC-1136], <sequence-number>,, ERROR, <system-name>, Failed to <data type, MUA, policy, etc.,> verify signature Probable Cause Indicates that the receiving switch fails to validate the security database sending from the primary fabric configurations server (FCS) switch. This message usually indicates that the data package is corrupted, the time stamp on the package is out of range as a result of a replay attack or out-of-sync time service, or the signature verification failed.
Page 447: Sec-1139
SEC-1139 SEC-1139 Message <timestamp>, [SEC-1139], <sequence-number>,, ERROR, <system-name>, The RSNMP_POLICY cannot exist without the WSNMP_POLICY. Probable Cause Indicates that the receiving switch fails to validate the security database sending from the primary fabric configurations server (FCS) switch. This message usually indicates that the data package is corrupted, the time stamp on the package is out of range as a result of a replay attack or out-of-sync time service, or the signature verification failed.
Page 448: Sec-1146
SEC-1146 SEC-1146 Message <timestamp>, [SEC-1146], <sequence-number>,, INFO, <system-name>, PID changed: <State> Probable Cause Indicates that the PID format of the switch was changed either to extended-edge PID or from extended-edge PID. If the device connection control (DCC) polices existed, all index/area ID values either increased or decreased by 16.
Page 449: Sec-1155
SEC-1155 SEC-1155 Message <timestamp>, [SEC-1155], <sequence-number>,, INFO, <system-name>, PID change failed: <Reason> <defined status> <active status>. Probable Cause Indicates that either the defined or active policy was too large after modifying the index/area ID. The status values can be either defined, active, or both. A negative value means that a policy set was failed by the daemon.
Page 450: Sec-1159
SEC-1159 Probable Cause Indicates that the specified name is invalid. The name can be a policy name or a switch name. Recommended Enter a valid name. Action Severity INFO SEC-1159 Message <timestamp>, [SEC-1159], <sequence-number>,, INFO, <system-name>, Non_Reachable <Domain ID> domain Probable Cause Indicates that there has been a corruption during the distribution of the security database.
Page 451: Sec-1164
SEC-1164 SEC-1164 Message <timestamp>, [SEC-1164], <sequence-number>,, ERROR, <system-name>, Lockdown option cannot be applied on a non-FCS switch. Probable Cause Indicates that the attempt to enable security is made on a switch that is not present in the fabric configurations server (FCS) list. Recommended Add the switch into the FCS policy list when using the lockdown option to enable security.
Page 452: Sec-1168
SEC-1168 Recommended Verify that the security event was planned. If the security event was planned, retry fabric Action configurations server (FCS) failover after current failover has completed, if this switch should become primary FCS. If the security event was not planned, take appropriate action as defined by your enterprise security policy.
Page 453: Sec-1172
SEC-1172 Run the licenseAdd command to install the required license key. Refer to your switch supplier to obtain a license if you do not have one. Severity ERROR SEC-1172 Message <timestamp>, [SEC-1172], <sequence-number>,, ERROR, <system-name>, Failed to identify role. Probable Cause Indicates that the switch is unable to determine its role (primary FCS or backup FCS) in the secure fabric.
Page 454: Sec-1176
SEC-1176 Recommended Verify that all switches in the fabric are in time synchronization with the primary and that no Action external entity is trying to access the fabric. When verification is complete, retry the operation. Severity ERROR SEC-1176 Message <timestamp>, [SEC-1176], <sequence-number>,, ERROR, <system-name>, Failed to generate new version stamp.
Page 455: Sec-1183
SEC-1183 Recommended No action is required. Action Severity INFO SEC-1183 Message <timestamp>, [SEC-1183], <sequence-number>,, ERROR, <system-name>, Policy to <port number> binary conversion error: Port is out range. Probable Cause Indicates that a security database conversion has failed because of an invalid value. Recommended Retry the command with a valid value.
Page 456: Sec-1186
SEC-1186 SEC-1186 Message <action> <timestamp>, [SEC-1186], <sequence-number>,, INFO, <system-name>, <action> Configuration. Probable Cause Indicates that the remote authentication dial-in user service (RADIUS/LDAP) configuration was enabled or disabled as the primary authentication, accounting, and authorization (AAA) mechanism. Recommended No action is required. Action Severity INFO...
Page 457: Sec-1189
SEC-1189 SEC-1189 Message <timestamp>, [SEC-1189], <sequence-number>,, INFO, <system-name>, Security <IP address> violation: Unauthorized host with IP address tries to do SNMP write operation. Probable Cause Indicates that an SNMP security violation was reported. The specified unauthorized host attempted to perform a write SNMP operation. Recommended Check the WSNMP policy and verify which hosts are allowed access to the fabric through SNMP.
Page 458: Sec-1192
SEC-1192 SEC-1192 Message <timestamp>, [SEC-1192], <sequence-number>,, INFO, <system-name>, Security <connection method> violation: Login failure attempt via Probable Cause Indicates that a serial or modem login security violation was reported. An incorrect password was used while trying to log in through a serial or modem connection; the login failed. Recommended Use the correct password.
Page 459: Sec-1196
SEC-1196 Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.
Page 460: Sec-1199
SEC-1199 Severity INFO SEC-1199 Message <timestamp>, [SEC-1199], <sequence-number>,, INFO, <system-name>, Security <switch instance> violation: Unauthorized access to serial port of switch Probable Cause Indicates that a serial connection policy security violation was reported. An attempt was made to access the serial console on the specified switch instance when it is disabled. Recommended Check to see if an authorized access attempt is being made on the console.
Page 461: Sec-1202
SEC-1202 SEC-1202 Message <timestamp>, [SEC-1202], <sequence-number>,, INFO, <system-name>, Security violation: Unauthorized access from MS device node name <device node name>, device port name <device port name>. Probable Cause Indicates that a management server (MS) security violation was reported. The unauthorized device specified in the message attempted to establish a connection.
Page 462: Sec-1253
SEC-1253 Recommended Retry the failed security command. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity ERROR SEC-1253 Message <timestamp>, [SEC-1253], <sequence-number>,, ERROR, <system-name>, Bad DCC interface state during <Phase>, state=<state>.
Page 463: Sec-1305
SEC-1303 Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.
Page 464: Sec-1306
SEC-1306 Probable Cause Indicates that there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configurations server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.
Page 465: Sec-1309
SEC-1309 Severity INFO SEC-1309 Message <timestamp>, [SEC-1309], <sequence-number>,, INFO, <system-name>, Waiting for RCS <Wait time in seconds> transaction to complete: secs Probable Cause Indicates that Secure Fabric OS is still waiting for the reliable commit service (RCS) transaction to complete. Recommended Verify if there are any RCS or RTWR errors.
Page 466: Sec-1313
SEC-1313 Probable Cause Indicates that the passwdCfg parameters changed. Recommended Verify that the security event was planned. If the security event was planned, no action is required. Action If the security event was not planned, take appropriate action as defined by your enterprise security policy.
Page 467: Sec-1316
SEC-1316 SEC-1316 Message <timestamp>, [SEC-1316], <sequence-number>,, WARNING, <system-name>, <Policy Name> policy is conflicting with domain <Domain Number> Probable Cause Indicates that the newly added switches to the fabric, as specified by Domain Number, have a conflicting policy with the local switch. Recommended Check the conflicting policy and make the new switches and the local switch policies the same.
Page 468: Sec-1320
SEC-1320 SEC-1320 Message <timestamp>, [SEC-1320], <sequence-number>,, WARNING, <system-name>, Non-acl <Domain Number> domain tries to join a fabric with strict fabric wide policy Probable Cause Indicates that a domain not supporting an access control list (ACL) policy tried to join a fabric with a strict fabric-wide policy.
Page 469: Sec-1324
SEC-1324 Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was Action not planned, take appropriate action as defined by your enterprise security policy. Severity INFO SEC-1324 Message <timestamp>, [SEC-1324], <sequence-number>,, INFO, <system-name>, Fabric <Error code>...
Page 470: Sec-1328
SEC-1328 Probable Cause Strict policy is conflicting. Recommended None, the domain is denied by disallowing all its E-ports connected to the fabric. If the domain Action should be allowed to merge with the fabric, then resolve the issue by making the conflicting policies same.
Page 471: Sec-1331
SEC-1331 SEC-1331 Message <timestamp>, [SEC-1331], <sequence-number>,, ERROR, <system-nam>, Attempt to enable secure mode failed. Reason: <Reason>. Probable Cause Indicates that the secModeEnable command failed on the fabric, because default IP Filter policies are not active on the switch, or an active transaction exists on IP Filter policies. Recommended Verify that the security event was planned.
Page 472 SEC-1332 Fabric OS Message Reference 53-1000600-02...
Page 473: Snmp-1001
Chapter SNMP System Messages SNMP-1001 Message <timestamp>, [SNMP-1001], <sequence-number>,, ERROR, <system-name>, SNMP service <Reason> is not available Probable Cause Indicates that the simple network management protocol (SNMP) service could not be started because of the specified Reason. You will not be able to query the switch through SNMP. Recommended Verify that the IP address for the Ethernet and Fibre Channel interface is set correctly.
Page 474: Snmp-1004
SNMP-1004 SNMP-1004 Message <timestamp>, [SNMP-1004], <sequence-number>, FFDC, ERROR, <system-name>, Incorrect SNMP configuration. Probable Cause Indicates that the simple network management protocol (SNMP) configuration is incorrect and the SNMP service will not work correctly. Recommended Change the SNMP configuration back to the default. Action Severity ERROR...
Page 475: Ss-1000
Chapter SS System Messages SS-1000 Message <timestamp>, [SS-1000], <sequence-number>,, INFO, <system-name>, supportSave has uploaded support information to the host with IP address <host ip>. Probable Cause Indicates that the supportSave command was used to transfer support information to a remote location.
Page 476: Ss-1003
SS-1003 SS-1003 Message <timestamp>, [SS-1003], <sequence-number>,, WARNING, <system-name>, supportSave's operation to USB storage device aborted. Probable Cause Indicates that a USB operation error occurred during execution of the supportSave command. Complete error information cannot always be displayed in this message due to possible errors in subcommands being executed by the supportSave command.
Page 477: Sulb-1001
Chapter SULB System Messages SULB-1001 Message <timestamp>, [SULB-1001], <sequence-number>, AUDIT, WARNING, <system-name>, Firmwaredownload command has started. Probable Cause Indicates that the firmwareDownload command has been entered. This process should take approximately 17 minutes. The process is set to time out after 30 minutes. Recommended Do not fail over or power down the system during firmware upgrade.
Page 478: Sulb-1004
SULB-1004 SULB-1004 Message <timestamp>, [SULB-1004], INFO, FIRMWARE, <event-initiator-details>, <event-location>, , Firmwarecommit has completed. Probable Cause Indicates that the FirmwareCommit command is executed. Recommended No action is required. Run the firmwareDownloadStatus command for more information. Action Severity INFO SULB-1005 Message <timestamp>, [SULB-1005], <sequence-number>,, INFO, <system-name>, Current Active CP is preparing to failover.
Page 479: Sulb-1008
SULB-1008 SULB-1008 Message <timestamp>, [SULB-1008], <sequence-number>,, INFO, <system-name>, Standby CP booted successfully with new firmware. Probable Cause Indicates that the standby CP has rebooted successfully. Recommended No action is required. The firmwareDownload command is progressing as expected. Action Run the firmwareDownloadStatus command for more information. Severity INFO SULB-1009...
Page 480 SULB-1009 TABLE 6 Status Messages and Status Codes Status Message Status Code “firmwareCommit operation failed due to IPC error.” 0x55 "Unable to check the firmware version on Standby CP due to IPC error." 0x56 “Unable to restore the original firmware due to Standby CP timeout.” 0x57 "Standby CP failed to reboot and was not responding."...
Page 481 SULB-1009 TABLE 6 Status Messages and Status Codes Status Message Status Code "The original firmware has been restored successfully on Standby CP." 0x7e "Unable to restore the original firmware on Standby CP." 0x7f "Standby CP reboots." 0x80 "Standby CP failed to reboot." 0x81 "Standby CP booted up with new firmware."...
Page 482 SULB-1009 TABLE 6 Status Messages and Status Codes Status Message Status Code “firmwareRestore is entered. System will reboot and a firmwareCommit operation will start 0xa8 upon boot up.” "Switch is relocating the AP image." 0xa9 "The AP image is relocated successfully." 0xaa "Switch reboots during relocating the AP image.
Page 483 SULB-1009 TABLE 7 Error Messages and Error Codes Error Message Error Code "Both images are mounted to the same device." 0x20 “Unable to unionist old packages.” 0x21 “firmwareDownload is already in progress.” 0x22 “firmwareDownload timed out.” 0x23 "Our of disk space." 0x24 “Primary filesystem is inconsistent.
Page 484 SULB-1009 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.
Page 485: Sulb-1010
SULB-1010 Recommended Run the firmwareDownloadStatus command for more information. Action In a director-class switch, when firmwareDownload fails, the command will synchronize the firmware on the two partitions of each CP by starting a firmware commit operation. Wait until this operation completes (about 10 minutes) before attempting another firmwareDownload. In a director-class switch, when firmwareDownload fails, the two CPs may end up with different versions of firmware and they may not gain high-availability (HA) sync.
Page 486: Sulb-1018
SULB-1018 Probable Cause Indicates that firmwareDownload failed in the specified blade. The error may be caused by an inconsistent AP blade firmware stored on the active CP. It may also caused by an internal Ethernet issue or by a persistent storage hardware failure. Recommended Run the slotShow command.
Page 487: Sulb-1022
SULB-1022 Recommended Run the firmwareDownloadStatus command to monitor the firmwareDownload progress. After it Action finishes, run the firmwareShow command to verify the firmware versions. Severity WARNING SULB-1022 Message <timestamp>, [SULB-1022], <sequence-number>,, WARNING, <system-name>, The blade <Slot number> in slot has rebooted successfully with new firmware. Probable Cause Indicates that the blade in the specified slot has rebooted with new firmware.
Page 488: Sulb-1025
SULB-1025 Severity WARNING SULB-1025 Message <timestamp>, [SULB-1025], <sequence-number>,, WARNING, <system-name>, The blade <Slot number> in slot will reboot with the new firmware. Probable Cause Indicates that new firmware has been downloaded to the specified AP blade and that the AP blade will reboot to active it.
Page 489: Sulb-1033
SULB-1033 Probable Cause Indicates that the switch has rebooted with the new firmware and is relocating the AP firmware. Recommended Wait for the operation to complete. Action Severity WARNING SULB-1033 Message <timestamp>, [SULB-1033], <sequence-number>, AUDIT, WARNING, <system-name>, Switch has completed relocating the internal firmware image. Probable Cause Indicates that the firmwareDownload process has completed normally on the switch.
Page 490: Sulb-1036
SULB-1036 SULB-1036 Message <The Version <timestamp>, [SULB-1036], <sequence-number>,, INFO, <system-name>, being logged><Version String> Probable Cause Indicates the firmware version running in the system. This is generally logged before download and after download of the firmware to store version information. Recommended No action is required.
Page 491: Swch-1001
Chapter SWCH System Messages SWCH-1001 Message <timestamp>, [SWCH-1001], <sequence-number>,, ERROR, <system-name>, Switch is not in ready state - Switch enable failed switch status= 0x<switch status>, c_flags = 0x<switch control flags>. Probable Cause Indicates that the switch is enabled before it is ready. Recommended If the message persists, run supportFtp (as needed) to set up automatic FTP transfers;...
Page 492: Swch-1004
SWCH-1004 SWCH-1004 Message <timestamp>, [SWCH-1004], <sequence-number>,, ERROR, <system-name>, Blade attach <slot number>. failed during recovery, disabling slot = Probable Cause Indicates that a blade has failed during failover or recovery. Recommended On a Brocade 24000 or 48000 switch, run the slotPowerOff command and then the slotPowerOn Action command.
Page 493: Swch-1008
SWCH-1008 Recommended Based on the disable reason displayed, proper corrective action may to be required to restore the Action port. If insufficient frame buffers is the disable reason, reduce the distance or speed settings for the port to reduce the buffer requirement of the link. Alternatively, one or more ports in the port group must be disabled to make more buffers available for the link.
Page 494: Swch-1011
SWCH-1011 Severity WARNING SWCH-1011 Message <timestamp>, [SWCH-1011], <sequence-number>,, WARNING, <system-name>, HA state out of sync: Standby CP (ver = <standby SWC version>) does not support Trunk Area functionality. (active ver = <active SWC version>, Trunk Area enabled on switch = <'1' if Trunk Area ports exist;...
Page 495: Sysc-1001
Chapter SYSC System Messages SYSC-1001 Message <timestamp>, [SYSC-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, Failed to run <Name of program that could not be run (string)>:<System internal error message (string)>. Probable Cause Indicates that during the boot sequence, one of the programs would not run on the system. Recommended If the message is reported during a reboot after new firmware has been loaded, try reloading the Action...
Page 496: Sysc-1004
SYSC-1004 It could also indicate that the current option number could not be read from the chassis option storage device (the world-wide name (WWN) card). This message occurs only on the Brocade 24000 and 48000. Recommended As indicated in the message, run the chassisConfig command to change to one that is valid on this Action platform running this firmware.
Page 497: Sysm-1001
Chapter SYSM System Messages SYSM-1001 Message <timestamp>, [SYSM-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, No memory. Probable Cause Indicates that the switch has run out of system memory. Recommended Run the memShow command to view the switch memory usage. Action Reboot or power cycle the switch. Run supportFtp as needed) to set up automatic FTP transfers;...
Page 498: Sysm-1004
SYSM-1004 SYSM-1004 Message <timestamp>, [SYSM-1004], <sequence-number>,, ERROR, <system-name>, Failed to <Unknown> retrieve current chassis configuration option, ret= Probable Cause Indicates that there was a failure to read configuration data from the WWN card. Recommended Verify that the world-wide name (WWN) card is present and operational and that the affected Action control processor (CP) is properly seated in its slot.
Page 499: Trce-1001
Chapter TRCE System Messages TRCE-1001 Message <timestamp>, [TRCE-1001], <sequence-number>,, WARNING, <system-name>, Trace dump available< optional slot indicating on which slot the dump occurs >! (reason: <Text explanation of what triggered the dump. (PANIC DUMP, WATCHDOG EXPIRED, MANUAL, TRIGGER)>) Probable Cause Indicates that trace dump files have been generated on the switch or the indicated slot.
Page 500: Trce-1004
TRCE-1004 Recommended If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the Action supportSave command and contact your switch service provider. Severity ERROR TRCE-1004 Message < <timestamp>, [TRCE-1004], <sequence-number>,, WARNING, <system-name>, Trace dump optional slot indicating on which slot the dump occurs >...
Page 501: Trce-1007
TRCE-1007 TRCE-1007 Message <timestamp>, [TRCE-1007], <sequence-number>,, ERROR, <system-name>, Notification of this CP has failed. Parameters temporarily out of synch with other CP. Probable Cause Indicates that the active CP is unable to alert the standby CP of a change in trace status. This message is only applicable to the Brocade 24000, and 48000.
Page 502: Trce-1011
TRCE-1011 Probable Cause Indicates that the trace daemon (traced), used for transferring trace files, failed to start. The trace capability within the switch is unaffected. The traced facility is normally restarted automatically by the system after a brief delay. Recommended If the message persists, reboot the CP (dual-CP system) or restart the switch.
Page 503: Trck-1001
Chapter TRCK System Messages TRCK-1001 Message <timestamp>, [TRCK-1001], <sequence-number>,, INFO, <system-name>, Successful <User> login by user Probable Cause Indicates that the track change feature recorded a successful login. Recommended No action is required. Action Severity INFO TRCK-1002 Message <timestamp>, [TRCK-1002], <sequence-number>,, INFO, <system-name>, Unsuccessful <User>...
Page 504: Trck-1005
TRCK-1005 Probable Cause Indicates that the track change feature recorded a configuration change for the switch. The track change feature records any change to the configuration file in nonvolatile memory, including a configDownload. This message is not generated for a configUpload. All configuration changes occur through the PDM server, so the PDMIPC is the only task possible.
Page 505: Ts System Messages
Chapter TS System Messages TS-1001 Message <timestamp>, [TS-1001], <sequence-number>,, WARNING, <system-name>, NTP Query <error code> failed: Probable Cause Indicates that a network time protocol (NTP) query to the configured external clock server failed. Local clock time on the principal or primary fabric configuration server (FCS) switch is used for fabric synchronization.
Page 506: Ts-1006
TS-1006 TS-1006 Message <message> <timestamp>, [TS-1006], <sequence-number>,, INFO, <system-name>, Probable Cause Indicates that a time service event is occurring or has failed. The message might be one of the following: • Init failed. Time Service exiting Probable Cause: Initialization error, Time Server exits. •...
Page 507 TS-1008 Severity WARNING Fabric OS Message Reference 53-1000600-02...
Page 508 TS-1008 Fabric OS Message Reference 53-1000600-02...
Page 509: Ucst-1003
Chapter UCST System Messages UCST-1003 Message <timestamp>, [UCST-1003], <sequence-number>,, INFO, <system-name>, Duplicate Path to Domain <domain ID>, Output Port = <port number>, PDB pointer = 0x<value> Probable Cause Indicates that duplicate paths were reported to the specified domain from the specified output port.
Page 510 UCST-1020 Fabric OS Message Reference 53-1000600-02...
Page 511: Upth-1001
Chapter UPTH System Messages UPTH-1001 Message <timestamp>, [UPTH-1001], <sequence-number>,, WARNING, <system-name>, No minimum cost path in candidate list Probable Cause Indicates that the specified switch is unreachable because no minimum cost path (FSPF UPATH) exists in the candidate list (domain ID list). Recommended No action is required.
Page 512 UPTH-1001 Fabric OS Message Reference 53-1000600-02...
Page 513: Webd-1001
Chapter WEBD System Messages WEBD-1001 Message <timestamp>, [WEBD-1001], <sequence-number>,, WARNING, <system-name>, Missing or Invalid Certificate file -- HTTPS is configured but could not be started. Probable Cause Indicates that the SSL certificate file is either invalid or absent. Recommended Install a valid key file. Action Severity WARNING...
Page 514: Webd-1006
WEBD-1006 Recommended No action is required. Action Severity WARNING WEBD-1006 Message <timestamp>, [WEBD-1006], <sequence-number>,, INFO, <system-name>, HTTP server restarted due to logfile truncation Probable Cause Indicates that the size of HTTP logfile exceeded the maximum limit. Recommended No action is required. Action Severity INFO...
Page 515: Zolb-1001
Chapter ZOLB System Messages ZOLB-1001 Message <timestamp>, [ZOLB-1001], <sequence-number>,, ERROR, <system-name>, ZONELIB <error message> Probable Cause Indicates that there was an internal timeout on the inter process communication (IPC) between the name server (NS) and the zoning modules. This usually indicates that the system was busy. Recommended This message generates core dump files of the related modules (zoned, nsd, rcsd).
Page 516 ZOLB-1001 Fabric OS Message Reference 53-1000600-02...
Page 517: Zone-1002
Chapter ZONE System Messages ZONE-1002 Message <timestamp>, [ZONE-1002], <sequence-number>,, WARNING, <system-name>, WWN zoneTypeCheck or zoneGroupCheck warning(<warning string>) at port(<port number>) Probable Cause Indicates that a zone filter or zone group check failure occurred. The frame filter logic reported a failure when creating or adding zone groups during port login (PLOGI) trap processing. This messages usually indicates problems when adding content-addressable memory (CAM) entries before the filter setup.
Page 518: Zone-1005
ZONE-1005 In session-based zoning, the zone enforcement is checked by the software. In hardware-enforced zoning, zone or alias members are defined using <domain, portarea> exclusively or using WWNs exclusively: that is, using one method or the other to define all objects in the zoning database. If the devices on the port are defined by a mixture of port IDs and WWNs, the zone enforcement is session based.
Page 519: Zone-1007
ZONE-1007 ZONE-1007 Message <timestamp>, [ZONE-1007], <sequence-number>,, INFO, <system-name>, Ioctl(<function>) in (<error message>) at port (<port number>) returns code (<error string>) and reason string (<reason string>). Probable Cause Indicates that frame filter logic reported a failure during one of the IOCTL calls. The IOCTL call from which the failure is reported is listed as part of the error message.
Page 520: Zone-1013
ZONE-1013 Recommended Check the device connection. Action Severity WARNING ZONE-1013 Message <timestamp>, [ZONE-1013], <sequence-number>,, WARNING, <system-name>, Quick Loop not supported. Probable Cause Indicates that the QuickLoop feature is not supported in the current code release. If the QuickLoop zoning configuration is enabled on the switch, it will not be supported. Recommended Edit the zone database to remove the QuickLoop zoning definition in the effective configuration.
Page 521: Zone-1018
ZONE-1018 Probable Cause Indicates that the fabric assist (FA) zoning configuration has more than one initiator. The probable cause is incorrect entries in the FA zoning configuration. Recommended Edit the zone database to ensure that only one initiator is set for each FA zone configuration. Action Severity ERROR...
Page 522: Zone-1022
ZONE-1022 ZONE-1022 Message <timestamp>, [ZONE-1022], <sequence-number>,, INFO, <system-name>, The effective configuration has changed to <Effective configuration name>. <AD Id> Probable Cause Indicates that the effective zone configuration has changed to the name displayed. Recommended Verify that this zone configuration change was done on purpose. If the new effective zone Action configuration is correct, no action is necessary.
Page 523: Zone-1027
ZONE-1027 ZONE-1027 Message <timestamp>, [ZONE-1027], <sequence-number>,, INFO, <system-name>, Zoning transaction aborted <error reason>. <AD Id>. Probable Cause Indicates that the zoning transaction was aborted due to a variety of potential errors. The error reason variable can be one of the following: •...
Page 524: Zone-1030
ZONE-1030 If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING ZONE-1030 Message <timestamp>, [ZONE-1030], <sequence-number>,, WARNING, <system-name>, Converting the zone db for PID format change failed. Probable Cause Indicates that the current zone database could not be converted to reflect the PID format change.
Page 525: Zone-1034
ZONE-1034 Probable Cause Indicates that the specified domain has the lowest memory available for the zone database in the fabric. The zone database must be smaller than the memory available on this domain. Recommended Reduce the size of the zone database and retry the operation. Action Severity ERROR...
Page 526: Zone-1037
ZONE-1037 ZONE-1037 Message <timestamp>, [ZONE-1037], <sequence-number>,, ERROR, <system-name>, Unable to examine <config file name>: error message <System Error Message>. Probable Cause Indicates that the Fabric OS cannot examine the zone configuration file. Typically the zone configuration is too large for the memory available on the switch. Recommended Reduce the size of the zone database and retry the operation.
Page 527: Zone-1041
ZONE-1041 Severity INFO ZONE-1041 Message <timestamp>, [ZONE-1041], <sequence-number>,, WARNING, <system-name>, Unstable <Port number> link detected during merge at port ( Probable Cause Indicates a possible unstable link or faulty cable. Recommended Check the SFP and cable at the specified port and verify that they are not faulty. Replace the SFP Action and cable as necessary.
Page 528: Zone-1045
ZONE-1045 ZONE-1045 Message <timestamp>, [ZONE-1045], <sequence-number>,, INFO, <system-name>, The Default Zone access mode is already set to No Access. Probable Cause Indicates that the Default Zone access mode is already set to No Access. Recommended No action is required. Action Severity INFO ZONE-1046...
Page 529 Section Audit Log Messages This section provides the Audit messages, including: • AUDIT AUTH System Messages........479 •...
Page 531: Auth-3001
Chapter AUDIT AUTH System Messages AUTH-3001 Message AUDIT, <timestamp>, [AUTH-3001], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: <Data type> type has been changed from [<Old value>] to [<New value>]. Probable Cause Indicates that an authentication configuration value was set to a specified value. The data type is “authentication type”, “DH group type”, “Hash type”, or “policy type”.
Page 532: Auth-3004
AUTH-3004 AUTH-3004 Message AUDIT, <timestamp>, [AUTH-3004], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: failed, Info: Neighboring switch has a conflicting authentication policy; Port <Port Number> disabled. Probable Cause The specified E_Port was disabled because the neighboring switch rejected the authentication negotiation, and the local switch has a strict switch authentication policy.
Page 533: Auth-3007
AUTH-3007 AUTH-3007 Message AUDIT, <timestamp>, [AUTH-3007], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: failed, Info: Port <port number> disabled due to receiving an authentication reject with code '<Reason String>' and explanation '<Explanation String>'. Probable Cause Indicates that the specified port was disabled due to receiving an authentication reject response from the connected switch/device.
Page 534 AUTH-3008 Fabric OS Message Reference 53-1000600-02...
Page 535: Conf-1020
Chapter AUDIT CONF System Messages CONF-1000 Message AUDIT, <timestamp>, [CONF-1000], INFO, CFG, <event-initiator-details>, <Info about the <event-location>, , configDownload completed successfully. parameters and AD> Probable Cause The configDownload process was initiated and completed successfully. The message string describes the class of configuration parameters that were downloaded. If admin domain (AD) is enabled, the AD number is specified in the description.
Page 536 CONF-1022 Fabric OS Message Reference 53-1000600-02...
Page 537: Fw-3001
Chapter AUDIT FW System Messages FW-3001 Message AUDIT, <timestamp>, [FW-3001], INFO, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info:<Event Related info> Probable Cause Indicates that Port Fencing was enabled/disabled successfully. Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1000600-02...
Page 538 FW-3001 Fabric OS Message Reference 53-1000600-02...
Page 539: Http-1002
Chapter AUDIT HTTP System Messages HTTP-1002 Message AUDIT, <timestamp>, [HTTP-1002], INFO, ZONE, <event-initiator-details>, <event-location>, , Zoning transaction initiated by User: <User Name>, Role: <User Role> completed successfully. Probable Cause Indicates that the zoning database has been changed. Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was Action not planned, take appropriate action as defined by your enterprise security policy.
Page 540 HTTP-1003 Fabric OS Message Reference 53-1000600-02...
Page 541: Sec-3001
Chapter AUDIT SEC System Messages SEC-3001 Message AUDIT, <timestamp>, [SEC-3001], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Security mode <State change: Enabled or Disabled> on the fabric. Probable Cause Indicates that the security mode of the fabric was either enabled or disabled. Recommended Verify that the security mode change was planned.
Page 542: Sec-3004
SEC-3004 Probable Cause Indicates that a new security policy was created with entries. Note: If you use a wildcard (for example, an asterisk) in creating a policy, the audit report displays the wildcard in the event info field. Recommended Verify that the new policy creation was planned. If the new policy creation was planned, no action is Action required.
Page 543: Sec-3007
SEC-3007 Probable Cause Indicates that a user has removed the specific members from the specified security policy. Note: If you use a wildcard (for example, an asterisk) in removing members from a policy, the audit report displays the wildcard in the event info field. Recommended Verify that the removal of members to the policy was planned.
Page 544: Sec-3010
SEC-3010 Severity INFO SEC-3010 Message AUDIT, <timestamp>, [SEC-3010], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Reset [<Name of security stat(s) reset>] security stat(s). Probable Cause Indicates that a user has reset all the security statistics. Recommended Verify that the security statistics were intentionally reset.
Page 545: Sec-3014
SEC-3014 Probable Cause Indicates that a user has reset the security version stamp. Recommended Verify that the security version stamp was intentionally reset. If the security event was planned, no Action action is required. If the security version stamp was not intentionally reset, take appropriate action as defined by your enterprise security policy.
Page 546: Sec-3017
SEC-3017 Recommended Verify that the RADIUS attribute was intentionally changed. If the RADIUS attribute was intentionally Action changed, no action is required. If the RADIUS attribute was not intentionally changed, take appropriate action as defined by your enterprise security policy. Severity INFO SEC-3017...
Page 547: Sec-3018
SEC-3018 SEC-3018 Message AUDIT, <timestamp>, [SEC-3018], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Parameter [<Parameter Name>] changed from [<Old Value>] to [<New Value>]. Probable Cause Indicates that the specified passwdCfg parameter is changed. Recommended Verify that the passwdCfg parameter was intentionally changed. If the passwdCfg parameter was Action intentionally changed, no action is required.
Page 548: Sec-3022
SEC-3022 Recommended Verify that the security event was planned. If the security event was planned, no action is required. Action If the security event was not planned, take appropriate action as defined by your enterprise security policy. Severity INFO SEC-3022 Message AUDIT, <timestamp>, [SEC-3022], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Successful logout...
Page 549: Sec-3025
SEC-3025 SEC-3025 Message AUDIT, <timestamp>, [SEC-3025], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: User account [<User Name>] added. Role: [<Role Type>], Password [<Password Expired or not>], Home AD [<Home AD>], AD list [<AD membership List>]. Probable Cause Indicates a new user account was created.
Page 550: Sec-3029
SEC-3029 Recommended Verify that the security event was planned. If the security event was planned, no action is required. Action If the security event was not planned, take appropriate action as defined by your enterprise security policy. Severity INFO SEC-3029 Message AUDIT, <timestamp>, [SEC-3029], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Backup user...
Page 551: Sec-3032
SEC-3032 SEC-3032 Message AUDIT, <timestamp>, [SEC-3032], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Switch is configured to <accept or reject> <Database name> database. Probable Cause Indicates that the specified event has occurred to accept or reject a certain database. Recommended Verify that the event was planned.
Page 552: Sec-3036
SEC-3036 Recommended Verify that the security event was planned. If the security event was planned, no action is required. Action If the security event was not planned, take appropriate action as defined by your enterprise security policy. Severity INFO SEC-3036 Message AUDIT, <timestamp>, [SEC-3036], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: ipfilter, Status: failed, Info: Failed to save changes...
Page 553: Sec-3039
SEC-3039 SEC-3039 Message AUDIT, <timestamp>, [SEC-3039], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: Securty Violation, Status: failed, Info: Unauthorized host with IP address <IP address of the violating host> tries to establish connection using <Protocol Connection Type>. Probable Cause Indicates that a security violation was reported. The IP address of the unauthorized host is displayed in the message.
Page 554: Sec-3045
SEC-3045 SEC-3045 Message AUDIT, <timestamp>, [SEC-3045], INFO, SECURITY, <event-initiator-details>, <event-location>, System has been zeroized. Probable Cause Indicates that the system has been zeroized. Recommended Verify that the security event was planned. If the security event was planned, no action is required. Action If the security event was not planned, take appropriate action as defined by your enterprise security policy.
Page 555: Sec-3049
SEC-3049 Severity INFO SEC-3049 Message AUDIT, <timestamp>, [SEC-3049], INFO, SECURITY, <event-initiator-details>, <event-location>, Status of bootprom access is changed using fipscfg CLI to : <Access Status>. Probable Cause Indicates that the status of bootprom access is changed using the fipscfg CLI. Recommended No action is required.
Page 556 SEC-3050 Fabric OS Message Reference 53-1000600-02...
Page 557: Snmp-1005
Chapter AUDIT SNMP System Messages SNMP-1004 Message AUDIT, <timestamp>, [SNMP-1004], ERROR, CONFIGURATION, <event-initiator-details>, <event-location>, , Incorrect SNMP configuration. Probable Cause Indicates that the simple network management protocol (SNMP) configuration s incorrect and the SNMP service will not work correctly. Recommended Reset the SNMP configuration to default.
Page 558 SNMP-1006 Fabric OS Message Reference 53-1000600-02...
Page 559: Sulb-1002
Chapter AUDIT SULB System Messages SULB-1001 Message AUDIT, <timestamp>, [SULB-1001], WARNING, FIRMWARE, <event-initiator-details>, <event-location>, , Firmwaredownload command has started. Probable Cause Indicates that the firmwareDownload command has been entered. This process should take approximately 17 minutes. The process is set to time out after 30 minutes. Recommended No action is required.
Page 560: Sulb-1009
SULB-1004 SULB-1004 Message AUDIT, <timestamp>, [SULB-1004], INFO, FIRMWARE, <event-initiator-details>, <event-location>, , Firmwarecommit has completed. Probable Cause Indicates that the FirmwareCommit command is executed. Recommended No action is required. Run the firmwareDownloadStatus command for more information. Action Severity INFO SULB-1009 Message AUDIT, <timestamp>, [SULB-1009], INFO, FIRMWARE, <event-initiator-details>, <event-location>, , Firmwaredownload command failed.
Page 561 SULB-1009 TABLE 9 Status Messages and Status Codes Status Message Status Code “firmwareCommit operation failed due to IPC error.” 0x55 "Unable to check the firmware version on Standby CP due to IPC error." 0x56 “Unable to restore the original firmware due to Standby CP timeout.” 0x57 "Standby CP failed to reboot and was not responding."...
Page 562 SULB-1009 TABLE 9 Status Messages and Status Codes Status Message Status Code "The original firmware has been restored successfully on Standby CP." 0x7e "Unable to restore the original firmware on Standby CP." 0x7f "Standby CP reboots." 0x80 "Standby CP failed to reboot." 0x81 "Standby CP booted up with new firmware."...
Page 563 SULB-1009 TABLE 9 Status Messages and Status Codes Status Message Status Code “firmwareRestore is entered. System will reboot and a firmwareCommit operation will start 0xa8 upon boot up.” "Switch is relocating the AP image." 0xa9 "The AP image is relocated successfully." 0xaa "Switch reboots during relocating the AP image.
Page 564 SULB-1009 TABLE 10 Error Messages and Error Codes Error Message Error Code "Both images are mounted to the same device." 0x20 “Unable to unionist old packages.” 0x21 “firmwareDownload is already in progress.” 0x22 “firmwareDownload timed out.” 0x23 "Our of disk space." 0x24 “Primary filesystem is inconsistent.
Page 565 SULB-1009 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.
Page 566: Sulb-1017
SULB-1010 Recommended Run the firmwareDownloadStatus command for more information. Action In a director-class switch, when firmwareDownload fails, the command will synchronize the firmware on the two partitions of each CP by starting a firmware commit operation. Wait until this operation completes (about 10 minutes) before attempting another firmwareDownload. In a director-class switch, when firmwareDownload fails, the two CPs may end up with different versions of firmware and they may not gain high-availability (HA) sync.
Page 567: Sulb-1020
SULB-1020 Probable Cause The error may be caused by a blade initialization issue after the new firmware is downloaded and the blade is rebooted. The error may also be caused by an internal Ethernet issue or by a persistent storage failure. Recommended Run the slotShow command.
Page 568: Sulb-1024
SULB-1024 Recommended firmwareCommit will be started automatically after the blade boots up to repair the secondary Action partition. If at the end of firmwareCommit, the blade firmware version is still inconsistent with the active CP firmware, firmwareDownload will automatically be restarted on the blade. Run the firmwareDownloadStatus command to monitor the progress.
Page 569: Sulb-1031
SULB-1031 Recommended firmwareDownload will continue after the switch has rebooted. Run the firmwareDownloadStatus Action command to monitor progress. If the problem persists, contact your switch service provider. Severity WARNING SULB-1031 Message AUDIT, <timestamp>, [SULB-1032], WARNING, FIRMWARE, <event-initiator-details>, <event-location>, , Relocating an internal firmware image on the CP. Probable Cause Indicates that the switch has rebooted with the new firmware and is relocating the AP firmware.
Page 570: Sulb-1035
SULB-1035 Recommended Reboot the switch. This will cause the internal image to be relocated again. Use the Action firmwareDownloadStatus to monitor the progress. If the problem persists, contact your switch service provider. Severity ERROR SULB-1035 Message AUDIT, <timestamp>, [SULB-1035], ERROR, FIRMWARE, <event-initiator-details>, <event-location>, , An error has occurred relocation of the internal image.
Page 571: Zone-3001
Chapter AUDIT ZONE System Messages ZONE-3001 Message AUDIT, <timestamp>, [ZONE-3001], INFO, ZONE, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: <Zone object type> \"<Zone object member list>\" added to <Zone object set type> \"<Zone object set name>\". Probable Cause Indicates that a new zone object member or members have been added to the specified zone object set.
Page 572: Zone-3004
ZONE-3004 The zone object type can be “alias”, “zone member”, “zone” or “zone configuration”. The string “...” appears at the end of the zone object member list if the list was truncated in the message. Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was Action not planned, take appropriate action as defined by your enterprise security policy.
Page 573: Zone-3007
ZONE-3007 ZONE-3007 Message AUDIT, <timestamp>, [ZONE-3007], INFO, ZONE, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Zone configuration \"<Zone configuration>\" enabled. <AD Id>. Probable Cause Indicates that the specified zone configuration has been enabled. Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was Action not planned, take appropriate action as defined by your enterprise security policy.
Page 574: Zone-3011
ZONE-3011 Severity INFO ZONE-3011 Message AUDIT, <timestamp>, [ZONE-3011], INFO, ZONE, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Zone object \"<Zone object name>\" expunged. Probable Cause Indicates that the specified zone object has been expunged. Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was Action not planned, take appropriate action as defined by your enterprise security policy.
Page 575: Zone-3015
ZONE-3015 An AD object set type is “AD member”. The string “...” appears at the end of the AD object member list if the list was truncated in the message. Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was Action not planned, take appropriate action as defined by your enterprise security policy.
Page 576: Zone-3018
ZONE-3018 ZONE-3018 Message AUDIT, <timestamp>, [ZONE-3018], INFO, FABRIC, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: <AD object name> has been deactivated. Probable Cause Indicates that the specified admin domain (AD) object has been deactivated. Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was Action not planned, take appropriate action as defined by your enterprise security policy.
Page 577: Zone-3022
ZONE-3022 Severity INFO ZONE-3022 Message AUDIT, <timestamp>, [ZONE-3022], INFO, FABRIC, <event-initiator-details>, <Event Name> <event-location>, , Event: , Status: success, Info: Current AD configuration saved to flash. Probable Cause Indicates that the current admin domain (AD) configuration has been saved to flash. Recommended Verify that the event was planned.
Page 578 ZONE-3025 Severity INFO Fabric OS Message Reference 53-1000600-02...

This manual is also suitable for:

Ae370a - brocade 4gb san switch 4/12 Am866a - storageworks 8/8 base san switch 8/24 8/40 8/8 8/80 ... Show all

Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base Reference Manual

Chapter 1 Introduction to System Messages

Chapter 2 AG System Messages

Chapter 3 AUTH System Messages

Chapter 4 BKSW System Messages

Chapter 5 BL System Messages

Chapter 6 BLL System Messages

Chapter 7 BM System Messages

Chapter 8 C2 System Messages

Chapter 9 CDR System Messages

Chapter 10 CER System Messages

Chapter 11 CONF System Messages

Chapter 12 EM System Messages

Chapter 13 ESS System Messages

Chapter 14 EVMD System Messages

Chapter 15 FABR System Messages

Chapter 16 FABS System Messages

Quick Links

Related Manuals for Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base

Summary of Contents for Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base