Brocade Communications Systems A7533A - Brocade 4Gb SAN Switch Base Reference Manual
Brocade fabric os message reference guide v6.2.0 (53-1001157-01, april 2009)
Hide thumbs
Also See for A7533A - Brocade 4Gb SAN Switch Base:
- Reference manual (1240 pages) ,
- Command reference manual (894 pages) ,
- Reference (550 pages)
Subscribe to Our Youtube Channel
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
- Page 1 53-1001157-01 24 November 2008 Fabric OS Message Reference Supporting Fabric OS v6.2.0...
- Page 2 Copyright © 2007-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 Title Publication Summary of changes Date number Fabric OS Message Reference 53-1000600-01 Updated for Fabric OS v6.0.0: October 2007 -Added new chapters: C2, ESS, FICON -Added new messages to: AG, BL, BM, C2, FCIP, ISW, NS, PLAT, SS, HIL -Added Audit messages: SEC, SULB -Updated Introductory chapters.
-
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............31 AG-1027 .
- Page 8 AUTH-1037............43 AUTH-1038 .
- Page 9 BL-1025 ............57 BL-1026 .
- Page 10 C2-1005............72 Chapter 9 CDR System Messages CDR-1001 .
- Page 11 CNM-1021 ............84 CNM-1022 .
- Page 12 CVLC-1002............95 CVLC-1003.
- Page 13 EM-1002 ............105 EM-1003 .
- Page 14 EM-1055 ............117 EM-1056 .
- Page 15 FABR-1010............130 FABR-1011.
- Page 16 FABS-1006............142 FABS-1007 .
- Page 17 FCR-1005............158 FCR-1006.
- Page 18 FCR-1048............168 FCR-1049.
- Page 19 FCR-1088............179 FCR-1089.
- Page 20 FICN-1036 ............190 FICN-1037 .
- Page 21 FICN-1073 ............200 FICN-1074 .
- Page 22 Chapter 32 FSPF System Messages FSPF-1001 ............213 FSPF-1002.
- Page 23 FW-1033 ............224 FW-1034 .
- Page 24 FW-1130 ............236 FW-1131 .
- Page 25 FW-1186 ............248 FW-1187 .
- Page 26 FW-1299 ............259 FW-1300 .
- Page 27 FW-1336 ............272 FW-1337 .
- Page 28 FW-1373 ............284 FW-1374.
- Page 29 Chapter 36 HAM System Messages HAM-1001 ............297 HAM-1002 .
- Page 30 HIL-1306 ............309 HIL-1307 .
- Page 31 Chapter 42 IBD System Messages IBD-1001 ............323 Chapter 43 IBPD System Messages IBPD-1001 .
- Page 32 ISNS-1005 ............338 ISNS-1006 .
- Page 33 LOG-1001............349 LOG-1002 .
- Page 34 Chapter 59 NBFS System Messages NBFS-1001 ........... . .365 NBFS-1002 .
- Page 35 PDTR-1002 ........... . .377 Chapter 63 PLAT System Messages PLAT-1000 .
- Page 36 Chapter 68 RAS System Messages RAS-1001............391 RAS-1002.
- Page 37 Chapter 72 RTWR System Messages RTWR-1001 ........... . .403 RTWR-1002 .
- Page 38 SEC-1042............417 SEC-1043.
- Page 39 SEC-1088............427 SEC-1089.
- Page 40 SEC-1136............437 SEC-1137.
- Page 41 SEC-1189............448 SEC-1190.
- Page 42 SEC-1319............459 SEC-1320.
- Page 43 SPC-2001............472 SPC-2002 .
- Page 44 SPM-1009 ............483 SPM-1010 .
- Page 45 SULB-1037............500 Chapter 81 SWCH System Messages SWCH-1001 .
- Page 46 TRCE-1004............512 TRCE-1005.
- Page 47 WEBD-1002 ........... . .525 WEBD-1004 .
- Page 48 ZONE-1034 ........... . .537 ZONE-1035 .
- Page 49 CONF-1020 ........... . .551 CONF-1022 .
- Page 50 SEC-3012............568 SEC-3013.
- Page 51 SEC-3051............578 Chapter 99 AUDIT SNMP System Messages SNMP-1004 .
- Page 52 UCST-1024............596 UCST-1025.
-
Page 53: About This Document
About This Document In this chapter • How this document is organized ....... . . xlvii •... -
Page 54: What's New In This Document
• Brocade 4018 switch • Brocade 4020 switch • Brocade 4024 switch • Brocade 4100 switch • Brocade 4900 switch • Brocade 5000 switch • Brocade 5100 switch • Brocade 5300 switch • Brocade 7500 Extension Switch • Brocade 7500E Extension Switch •... -
Page 55: Document Conventions
• “LFM System Messages” • “PMGR System Messages” • “TAPE System Messages” For further information about new features and documentation updates for this release, refer to the release notes. Document conventions This section describes text formatting conventions and important notice formats used in this document. -
Page 56: Key Terms
Notes, cautions, and warnings The following notices and statements are used in this manual. They are listed below in order of increasing severity of potential hazards. NOTE A note provides a tip, guidance or advice, emphasizes important information, or provides a reference to related information. -
Page 57: Other Industry Resources
http://www.brocade.com Release notes are available on the Brocade Connect Web site and are also bundled with the Fabric OS firmware. Other industry resources For information about the Fibre Channel industry, visit the Fibre Channel Industry Association Web site: http://www.fibrechannel.org Getting technical help Contact your switch support supplier for hardware, firmware, and software support, including product repairs and part ordering. -
Page 58: Document Feedback
• Brocade DCX-4S—On the bottom right on the port side of the chassis, directly above the cable management comb. 3. World Wide Name (WWN) Use the wwn command to display the switch WWN. • If you cannot use the wwn command because the switch is inoperable, you can get the WWN from the same place as the serial number, except for the Brocade DCX. -
Page 59: Chapter 1 Introduction To System Messages
Chapter Introduction To System Messages In this chapter • Overview of System Messages ........1 •... -
Page 60: Event Auditing
Overview of System Messages • Trace dump, first-time failure detection capture (FFDC), and core dump files can be uploaded to the FTP server using the supportSave command. • It is recommended to configure the syslogd facility as a management tool for error logs. This is particularly important for dual-domain switches because the syslogd facility saves messages from two logical switches as a single file and in sequential order. -
Page 61: System Logging Daemon (Syslogd)
Overview of System Messages • FCIP-related messages: FCIP 1002 and 1003 • FICU-related messages: FICU 1011 and 1012 • FW-related messages: FW - 3001 • HTTP configuration messages: HTTP-1002, 1003 • IPAD-related messages: IPAD 1002 • PORT related messages: PORT 1006 - 1009 •... -
Page 62: System Console
Viewing and Configuring System Message Logs System Console The system console displays messages only through the serial port. If you log in to a switch through the Ethernet port or modem port, you will not receive system console messages. The system console displays system messages, Audit messages (if enabled) and panic dump messages. - Page 63 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 64: 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 65: 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 66: 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 67: 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 68 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 69: 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 70: 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 71: 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 72 System Module Descriptions TABLE 5 System Module Descriptions (Continued) System Description Module Blade error messages are a result of faulty hardware, transient out-of-memory conditions, application specific integrated circuit (ASIC) errors, or inconsistencies in the software state between a blade and the EM (environment monitor) module.
- Page 73 System Module Descriptions TABLE 5 System Module Descriptions (Continued) System Description Module FCPD The Fibre Channel Protocol daemon is responsible for probing the devices attached to the loop port. Probing is a process the switch uses to find the devices attached to the loop ports and to update the Name Server with the information.
- Page 74 System Module Descriptions TABLE 5 System Module Descriptions (Continued) System Description Module ICPD ICPD stands for iSCSI gateway daemon on a control processor (CP). It manages iSCSI configurations such as CHAP, VT/LUN, DD/DDSet and portal configurations, and statistics such as iSCSI session/connection information.
- Page 75 System Module Descriptions TABLE 5 System Module Descriptions (Continued) System Description Module KTRC Kernel RAS trace module. LFM error messages indicate problems with the logical fabric manager module that is responsible for making a logical switch use XISLs. This involves creating and managing LISLs in a logical fabric. RASLog subsystem.
- Page 76 System Module Descriptions TABLE 5 System Module Descriptions (Continued) System Description Module The reliable commit service daemon generates log entries when it receives a request from the zoning, security, or management server for passing data messages to switches in the fabric. RCS then requests reliable transport write and read (RTWR) to deliver the message.
- Page 77 System Module Descriptions TABLE 5 System Module Descriptions (Continued) System Description Module TRCK The track change feature tracks the following events: Turning on or off the track change feature CONFIG_CHANGE LOGIN LOGOUT FAILED_LOGIN If any of these events occur, a message is sent to the system message log. Additionally, if the SNMP trap option is enabled, an SNMP trap is also sent.
- Page 78 System Module Descriptions Fabric OS Message Reference 53-1001157-01...
- Page 79 Section RASLog Messages This section provides the RASLog messages, including: • AG System Messages ......... . . 25 •...
- Page 80 • FSS System Messages ......... 215 •...
- Page 81 • RTWR System Messages........403 •...
-
Page 83: 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 84: 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 the fabric sent an invalid response to the FLOGI Extended Link Service (ELS) for the specified N_Port. -
Page 85: 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 the fabric switch management server did not accept the N_Port Login (PLOGI) request sent by the Access Gateway. -
Page 86: 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 there was a failure sending discover F_Port service parameter request from the Access Gateway to the fabric switch. Recommended 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 87: 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 Indicates either no other N_Port is configured or all N_Ports are currently offline. Recommended 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 88: 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_Ports. 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 89: Ag-1023
AG-1023 Probable Cause Indicates the specified F_Port is failing over to its preferred N_Port. Recommended 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> is failed over to its preferred N_Port <pport>. Probable Cause Indicates the specified N_Port has failed to come online. -
Page 90: Ag-1027
AG-1027 Probable Cause Indicates there are 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; then run the supportSave command and contact your switch service provider. -
Page 91: 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 92: 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 93: 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 94: 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 95: 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 96: 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 97: 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 98: 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 99: 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 100: 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 101: 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 102: 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 103: 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 104 AUTH-1044 Fabric OS Message Reference 53-1001157-01...
-
Page 105: 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 you regarding the state of the system. Refer to the string at the end of the error message for specific information. - Page 106 BKSW-1003 Fabric OS Message Reference 53-1001157-01...
-
Page 107: 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 108: 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 109: 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 110: 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 111: 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 112: 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 113: 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 114: 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 115: 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 116: 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 117: 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 118: 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 119: 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 120 BL-1037 Fabric OS Message Reference 53-1001157-01...
-
Page 121: 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 a blade regulation problem was reported on the specified slot number. The blade is faulted. - Page 122 BLL-1000 If the message persists, replace the blade. Severity CRITICAL Fabric OS Message Reference 53-1001157-01...
-
Page 123: 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 the firmware running on the control processor (CP) cannot communicate with the application processor (AP) blade in the indicated slot and determine the AP blade's firmware version. -
Page 124: 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 Indicates the policy of the specified blade is to auto-level the blade firmware to the system firmware. -
Page 125: 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 Indicates 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. The blade ports are cleared automatically. -
Page 126: Bm-1053
BM-1053 Recommended The blade ports are cleared automatically. No action is required. Action 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 Indicates the control processor (CP) could not establish a connection to the application processor to communicate. -
Page 127: Bm-1056
BM-1056 BM-1056 Message <timestamp>, [BM-1056], <sequence-number>,, INFO, <system-name>, AP is not configured. Persistently disabling all ports on the switch. Probable Cause Indicates the policy of the specified switch is to persistently disable all ports the first time the AP is detected. - Page 128 BM-1058 Fabric OS Message Reference 53-1001157-01...
-
Page 129: C2-1001
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 130: 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 131: 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 132: 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 133: 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 134 CER-1001 Fabric OS Message Reference 53-1001157-01...
-
Page 135: Chassis-1002
Chapter CHASSIS System Messages CHASSIS-1002 Message <timestamp>, [CHASSIS-1002], <sequence-number>,, ERROR, <system-name>, ki_gd_register_action failed with rc =<ret val>. Probable Cause Indicates an internal error. Recommended For a bladed system, run the slotPowerOff command and slotPowerOn command on the blade to Action recover the system. -
Page 136: Chassis-1005
CHASSIS-1005 CHASSIS-1005 Message <timestamp>, [CHASSIS-1005], <sequence-number>,, ERROR, <system-name>, Diag attach failed during recovery, disabling slot = <slot number>. Probable Cause Indicates that the Diag blade attach has failed during failover or recovery. Recommended On a Brocade 24000 or 48000 switch, run the slotPowerOff command followed by the slotPowerOn Action command. -
Page 137: Cnm-1001
Chapter CNM System Messages CNM-1001 Message <timestamp>, [CNM-1001], <sequence-number>,, ERROR, <system-name>, Failed to allocate memory: <function name>. Probable Cause Indicates that the specified function failed to allocate memory. Recommended Check memory usage on the switch using the memShow command. Reboot or power cycle the Action switch. -
Page 138: Cnm-1005
CNM-1005 Probable Cause Indicates that the Crypto service is enabled or disabled on the switch. Recommended No action is required. Action Severity INFO CNM-1005 Message <timestamp>, [CNM-1005], <sequence-number>,, INFO, <system-name>, Posting event CNM_EVT_GRP_LEADER_ELECTED Name [<nodeName>], WWN [<WWn>]. Probable Cause Indicates that the cluster encryption group leader is elected. Recommended No action is required. -
Page 139: Cnm-1009
CNM-1009 Recommended No action is required. Action Severity INFO CNM-1009 Message <timestamp>, [CNM-1009], <sequence-number>,, INFO, <system-name>, Posting event CNM_EVT_STANDALONE_MODE. Probable Cause Indicates that the node is in standalone mode. Recommended No action is required. Action Severity INFO CNM-1010 Message <timestamp>, [CNM-1010], <sequence-number>,, INFO, <system-name>, Posting event CNM_EVT_CLUSTER_UDATA_UPDATE cid [<client id>], ulen [<udata len>]. -
Page 140: Cnm-1013
CNM-1013 Recommended No action is required. Action Severity INFO CNM-1013 Message <timestamp>, [CNM-1013], <sequence-number>,, INFO, <system-name>,Posting event GL Node Split condition, isolating peer GL node <nodeName>. Probable Cause Indicates that the encryption group (EG) is split. Recommended No action is required. Action Severity INFO... -
Page 141: Cnm-1017
CNM-1017 Recommended No action is required. Action Severity INFO CNM-1017 Message <timestamp>, [CNM-1017], <sequence-number>,, INFO, <system-name>,Got JOIN REQUEST from un-recognized GL node [<rxglname>], configured GL node is [<glname>]. Probable Cause Indicates a join request was received from an invalid group leader (GL) node. Recommended No action is required. -
Page 142: Cnm-1021
CNM-1021 Probable Cause Indicates Node Admission Control failed. Recommended No action is required. Action Severity INFO CNM-1021 Message <timestamp>, [CNM-1021], <sequence-number>,, INFO, <system-name>, Failed to sign the node authentication message, admission control might fail. Probable Cause Indicates Node Admission Control failed. Recommended No action is required. -
Page 143: Cnm-1025
CNM-1025 Probable Cause Indicates an operation is not required on a group leader (GL) node. Recommended No action is required. Action Severity INFO CNM-1025 Message <timestamp>, [CNM-1025], <sequence-number>,, INFO, <system-name>, Operation not allowed, as member is active with the Cluster. Eject member node and retry. Probable Cause Indicates an operation is not allowed because a member node is active with the cluster. -
Page 144: Cnm-1029
CNM-1029 Probable Cause Indicates that the certificate file for the node already exists. Recommended No action is required. Action Severity INFO CNM-1029 Message <timestamp>, [CNM-1029], <sequence-number>,, INFO, <system-name>, Certfile <cfname> content does not match the cert sent by GL. Probable Cause Indicates that the contents of the node's certificate file is different from the certificate file sent by the group leader (GL) node. -
Page 145: Cnm-1033
CNM-1033 Probable Cause Indicates that there is a size mismatch between a node's certificate file and the certificate file received from the group leader. Recommended No action is required. Action Severity INFO CNM-1033 Message <timestamp>, [CNM-1033], <sequence-number>,, INFO, <system-name>, Some of the defined nodes in the Encryption Group are not ONLINE. -
Page 146: Cnm-1037
CNM-1037 Probable Cause Indicates an event is being posted to indicate the cluster is in a converged state. Recommended No action is required. Action Severity INFO CNM-1037 Message <timestamp>, [CNM-1037], <sequence-number>,, INFO, <system-name>, Split-Brain Arbitration lost!, minority GL Node, remote:local [<rem_count>:<loc_gl_ncount>]. Probable Cause Indicates that split arbitration is lost. -
Page 147: Cnm-1041
CNM-1041 Recommended No action is required. Action Severity INFO CNM-1041 Message <timestamp>, [CNM-1041], <sequence-number>,, INFO, <system-name>, Updating persistent Cluster DB, please avoid powering off the switch. Probable Cause Indicates the system is updating the persistent database. Recommended No action is required. Action Severity INFO... - Page 148 CNM-1044 Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1001157-01...
-
Page 149: Conf-1000
Chapter CONF System Messages CONF-1000 Message <timestamp>, [CONF-1000], <sequence-number>, AUDIT, INFO, <system-name>, configDownload completed successfully. <Info about the parameters and AD>. Probable Cause Indicates that the configDownload operation was initiated and completed successfully. The statement that follows, message strings, is the description of the classes of configuration parameters that were downloaded. -
Page 150: Conf-1021
CONF-1021 CONF-1021 Message <timestamp>, [CONF-1021], <sequence-number>,, INFO, <system-name>, configUpload not permitted <AD Number if AD is configured on the system>. Probable Cause Indicates a configUpload operation is not permitted. There are many possible causes. Recommended Check the error log, correct the error and rerun configupload. Action Severity INFO... -
Page 151: Ctap-1001
Chapter CTAP System Messages CTAP-1001 Message <timestamp>, [CTAP-1001], <sequence-number>,, INFO, <system-name>, Key acquisition for <Pool or Container> <Begins or Complete>. Probable Cause Indicates that a change in the tape pool database has triggered the key acquisition process for each pool. Recommended Do not start tape backup or restore operations involving tape pools until the process is complete. - Page 152 CTAP-1001 Fabric OS Message Reference 53-1001157-01...
-
Page 153: Cvlc-1001
Chapter CVLC System Messages CVLC-1001 Message <timestamp>, [CVLC-1001], <sequence-number>,, INFO, <system-name>, <Re-key type (First time encryption/Key expired/Manual)> re-key <Re-key action (started/completed/failed/cancelled)>, LUN SN: <LUN serial number>.\nContainer: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Probable Cause Indicates the First time encryption, Key expired or Manual re-key operation is performed. The operation has been started, completed or cancelled. -
Page 154: Cvlc-1004
CVLC-1004 CVLC-1004 Message <timestamp>, [CVLC-1004], <sequence-number>,, INFO, <system-name>, Forceful encryption LUN removal while re-key session is still active.\nContainer: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Probable Cause Indicates that the encryption LUN was forcefully removed while a re-key session was still active. Recommended No action is required. -
Page 155: Cvlc-1009
CVLC-1009 Severity ERROR CVLC-1009 Message <timestamp>, [CVLC-1009], <sequence-number>,, ERROR, <system-name>, Wrong device type: should be <Expected device type (Disk/Tape)>, found <Discovered device type (Disk/Tape)>.\nContainer: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Probable Cause Indicates that the wrong device type was found. Recommended No action is required. -
Page 156: Cvlc-1013
CVLC-1013 Recommended Use cryptocfg command to change the LUN's metadata mode. Action Severity ERROR CVLC-1013 Message <timestamp>, [CVLC-1013], <sequence-number>,, ERROR, <system-name>, Unable to retrieve key record from the key archive.\nContainer: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Probable Cause Indicates that the encryption engine is unable to retrieve the key record base on the key ID found in the metadata. -
Page 157: Cvlc-1016
CVLC-1016 CVLC-1016 Message <timestamp>, [CVLC-1016], <sequence-number>,, INFO, <system-name>, LUN is out of read only mode. Reason: <Reason for LUN is out of read only mode>.\nContainer: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Probable Cause Indicates that the LUN is set back to read/write. Recommended No action is required. -
Page 158: Cvlc-1020
CVLC-1020 Severity ERROR CVLC-1020 Message <timestamp>, [CVLC-1020], <sequence-number>,, ERROR, <system-name>, Metadata exists while LUN is clear text.\nContainer: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Probable Cause Indicates that metadata exists on the LUN that is clear text. Recommended Use cryptocfg command to confirm the configuration. -
Page 159: Cvlm-1001
Chapter CVLMSystem Messages CVLM-1001 Message <timestamp>, [CVLM-1001], <sequence-number>,, ERROR, <system-name>, Failed to allocate memory: (<function name>). Probable Cause Indicates that the specified function failed to allocate memory. • Recommended Check memory usage on the switch using the memShow command. Action •... -
Page 160: Cvlm-1005
CVLM-1005 Probable Cause Indicates that encryption engine nodes in the cluster encryption group have different configurations. Recommended Synchronize the configuration in the cluster group using the cryptocfg --commit command. Refer to Action the Fabric OS Command Reference Manual for more information on this command. Severity WARNING CVLM-1005... -
Page 161: Cvlm-1009
CVLM-1009 Probable Cause Indicates that the member of HAC is not in the fabric. Recommended Check the ISL port connected to the fabric. Action Severity WARNING CVLM-1009 Message <timestamp>, [CVLM-1009], <sequence-number>,, INFO, <system-name>, The member (<EE node WWN> <EE slot num>) of HAC (<HAC name>) is in the fabric. Probable Cause Indicates that the member of HAC is in the fabric. - Page 162 CVLM-1012 Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1001157-01...
-
Page 163: 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 164: 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 165: Em-1006
EM-1006 EM-1006 Message <FRU <timestamp>, [EM-1006], <sequence-number>, FFDC, CRITICAL, <system-name>, Id> has faulted. Sensors 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 166: Em-1009
EM-1009 EM-1009 Message <FRU <timestamp>, [EM-1009], <sequence-number>, FFDC, CRITICAL, <system-name>, Id> powered down unexpectedly. 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. -
Page 167: Em-1013
EM-1013 Probable Cause Indicates that a switch blade or nonbladed switch failed to transition from one state to another. It is faulted. The specific failed target state is displayed in the message. There are serious internal Fabric OS configuration or hardware problems on the switch. Recommended On Brocade DCX, 24000 and 48000, try reseating the indicated field-replaceable unit (FRU). -
Page 168: Em-1016
EM-1016 Severity WARNING 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 169: Em-1028
EM-1028 Probable Cause Indicates that the current chassisConfig option is not supported by the firmware on the standby control processor (CP). This is true even if the standby comes up and appears to be operational. High availability (HA) synchronization of the CPs will not be allowed. Recommended Either change the chassisConfig option to 1 with the chassisConfig command, or upgrade the Action... -
Page 170: Em-1033
EM-1033 Probable Cause Indicates that the environmental monitor (EM) has found a switch blade that is inserted, but the ejector switch is not closed. The blade in the specified slot is treated as not inserted. 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. -
Page 171: Em-1036
EM-1036 Probable Cause Suggests that since both power supplies associated with one of the two 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 172: 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 173: 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 174: Em-1048
EM-1048 Probable Cause Indicates that the control processor (CP) is no longer faulted. This message usually follows EM-1033. The new standby CP is in the process of rebooting and has turned off the CP_ERR signal. Recommended No action is required. Action Severity INFO... -
Page 175: Em-1051
EM-1051 EM-1051 Message <FRU Id> <timestamp>, [EM-1051], <sequence-number>,, INFO, <system-name>, Inconsistency detected, FRU re-initialized. 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. -
Page 176: Em-1058
EM-1058 Probable Cause Indicates the blade is being automatically reset because of known resetable transient errors such as an application-specific integrated circuit (ASIC) parity error. Recommended No action is required if the switch does not reach the reset threshold for the switch or blade. If the Action reset threshold is reached on the switch or blade, the switch or blade will be faulted and should be replaced. -
Page 177: Em-1061
EM-1061 Severity WARNING 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 Indicates a blade in the system is not supported by the release on the standby control processor (CP). -
Page 178: Em-1065
EM-1065 Probable Cause Indicates the blade is being powered off because a hardware (HW) application specific integrated circuit (ASIC) ERROR was detected, and you have selected to power off the problem blade when such a condition occurred. Recommended Contact support. Action Severity CRITICAL... -
Page 179: Em-1068
EM-1068 EM-1068 Message <timestamp>, [EM-1068], <sequence-number>,, ERROR, <system-name>, High Availability Service Management subsystem failed to respond. A required component is not operating. Probable Cause Indicates that the HA subsystem has not returned a response within four minutes of the request from the Environmental Manager. - Page 180 EM-2003 Recommended On bladed systems, try reseating the specified FRU. Action On nonbladed switches, reboot or power cycle the switch. If the problem persists: • 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. •...
-
Page 181: 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 Indicates 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 182: 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 Indicates that 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 183: 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 Indicates the event could not be sent to remote proxy. This could happen if the remote proxy switch cannot be reached through in-band. - Page 184 EVMD-1001 Fabric OS Message Reference 53-1001157-01...
-
Page 185: 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 resulting from 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 186: 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 187: 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 188: 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 189: 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 190: 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 191: 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 192: 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 193: 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 194: 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 Indicates you must enable Trunk Area on a port for another port to use the same area. Recommended Move the cable to a port area that is not in use, or disable Trunk Area. -
Page 195: Fabr-1038
FABR-1038 Probable Cause Indicates the specified port is being disabled because when the port attempts to go online, the Switch finds that Trunk Area enabled is incompatible with port configuration such as long distance, port mirror, fast write or EX_port. Recommended Check the port configuration to disable long distance, port mirror, fast write or EX_port. -
Page 196: Fabr-1041
FABR-1041 FABR-1041 Message <timestamp>, [FABR-1041], <sequence-number>, ERROR, <system-name>, Port <Port that is being disabled> is disabled due to trunk protocol error. Probable Cause Indicates that a link reset was received before the completion of the trunking protocol on the port. Recommended Enable the port by running portEnable command. -
Page 197: Fabr-1046
FABR-1046 Recommended Make sure that all the switches in the fabric have the same Base Switch attribute or disable VF Action mode for the conflicting switch using the fosconfig command. Severity ERROR FABR-1046 Message <timestamp>, [FABR-1046], <sequence-number>, ERROR, <system-name>, Detected Base Switch conflict with neighbor switch <Switchname>... - Page 198 FABR-1046 Fabric OS Message Reference 53-1001157-01...
-
Page 199: 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 200: 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 value for function name and description of problem is: fabsys_write: Unsupported write operation: process xxx where xxx is the process ID (PID), which could be any whole number. -
Page 201: 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 202: 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 203: 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 204 FABS-1015 Fabric OS Message Reference 53-1001157-01...
-
Page 205: 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 206 FBC-1001 Fabric OS Message Reference 53-1001157-01...
-
Page 207: 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 208: Fcip-1004
FCIP-1004 Probable Cause Indicates that an IPsec/IKE policy was deleted and the config file was updated. Recommended No action is required. Action Severity INFO FCIP-1004 Message <timestamp>, [FCIP-1004], <sequence-number>, INFO, CFG, <system-name>, Tape Read Pipelining is being disabled slot (<slot number>) port (<user port index>) tunnel (<The configured tunnel ID (0-7)>). -
Page 209: 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 210 FCMC-1001 Fabric OS Message Reference 53-1001157-01...
-
Page 211: 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 probing failed on the L_Port, or AL_PA address, or the F_Port. For the AL_PA, the valid range is 00 through FF. - Page 212 FCPD-1003 Fabric OS Message Reference 53-1001157-01...
-
Page 213: 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 214 FCPH-1002 Fabric OS Message Reference 53-1001157-01...
-
Page 215: Fcr-1001
Chapter FCR System Messages FCR-1001 Message <timestamp>, [FCR-1001], <sequence-number>,, INFO, <system-name>, FC router proxy device in edge created at port <port number>. Probable Cause Indicates that a proxy device in the edge fabric has been imported at the specified port. Recommended No action is required. -
Page 216: Fcr-1005
FCR-1005 Recommended Verify that the devices 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 217: 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 218: 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 219: Fcr-1018
FCR-1018 FCR-1018 Message <timestamp>, [FCR-1018], <sequence-number>,, ERROR, <system-name>, FC router proxy device entries exhausted on port <port number>. 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 220: 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 221: 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 222: 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 223: 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... -
Page 224: 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 225: 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 226: 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 227: 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 228: 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 229: 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 230: 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 231: 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 232: 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 233: 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 234: 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 235: 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 236: 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 237: Fcr-1087
FCR-1087 Recommended Disable Condor2-based EX_ports or upgrade the remote CP. Action Severity ERROR FCR-1087 Message <timestamp>, [FCR-1087], <sequence-number>,, ERROR, <system-name>, ExPort <ExPort> connects to fabric <fabric> with capability to use XISL domain <domain>. Probable Cause Indicates that the EX_Port connects to logical fabric containing a domain has the capability to use XISL. - Page 238 FCR-1089 Fabric OS Message Reference 53-1001157-01...
-
Page 239: 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 240: 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 241: 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 Indicates a FICON Purge Path was 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 242: 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 243: 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 Indicates a frame was received from the peer emulation processing with an invalid LRC. This indicates data corruption between the emulation processing components. -
Page 244: 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 Indicates the FICON channel indicated in the path issued an LRJ frame for a sequence from the device. -
Page 245: Ficn-1023
FICN-1023 Probable Cause Indicates 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, contact your vendor's customer Action support for assistance. Severity ERROR FICN-1023 Message... -
Page 246: 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 Indicates 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, contact your vendor's Action customer support for assistance. -
Page 247: Ficn-1030
FICN-1030 Recommended If there was an unexpected job failure or IO Error associated with this event, contact your vendor's Action 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 Indicates an active disk emulation device received a FICON Purge Path from the channel. Recommended If there was an unexpected job failure or IO Error associated with this event, contact your vendor's Action... -
Page 248: 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 Indicates the channel emulation processing received a frame with an invalid FICON LRC from the peer. -
Page 249: Ficn-1038
FICN-1038 Probable Cause Indicates 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 250: 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 Indicates an LRJ received from a device indicates that the CU has lost the logical path to the LPAR. -
Page 251: Ficn-1045
FICN-1045 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>. Probable Cause Indicates a purge path was received from the locally connected FICON channel. This is performed during the path recovery. -
Page 252: 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 Indicates the operator has cancelled a read or write job. Recommended This is an unexpected event; contact your vendor's customer support for assistance. Action Severity WARNING... -
Page 253: 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 Indicates a PSF command has been received to break an XRC session with the extended DASD device. -
Page 254: Ficn-1056
FICN-1056 Probable Cause Indicates 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, contact your vendor's customer support for assistance. Action Severity WARNING... -
Page 255: 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 Indicates an internal resource shortage caused an error such that an emulation frame could not be created and sent to an LPAR. Recommended This is an unexpected event, contact your vendor's customer support for assistance. -
Page 256: Ficn-1063
FICN-1063 Severity ERROR 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 Indicates an abort operation has been received from a peer FC interface for an active emulation exchange. Recommended This is an unexpected event, contact your vendor's customer support for assistance. Action Severity ERROR... -
Page 257: Ficn-1067
FICN-1067 Probable Cause Indicates an internal resource limit has been encountered such that additional control block memory could not be allocated. 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, contact your vendor's customer support for assistance. Severity WARNING FICN-1067... -
Page 258: Ficn-1070
FICN-1070 FICN-1070 Message <timestamp>, [FICN-1070], <sequence-number>,, INFO, <system-name>, DevTapeIngr:Exceptional Status rcvd on Path=<FICON PATH> state=0x<current emulation state> status=0x<the exceptional status value>. Probable Cause Indicates 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. -
Page 259: Ficn-1074
FICN-1074 Recommended No action is required. Action Severity INFO 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 260: Ficn-1077
FICN-1077 Recommended No action is required. Action Severity INFO 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 Indicates 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 261: Ficn-1080
FICN-1080 Recommended No action is required. Action Severity INFO 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 262: Ficn-1083
FICN-1083 FICN-1083 Message <timestamp>, [FICN-1083], <sequence-number>,, WARNING, <system-name>, EmulEls:SW_RSCN received on GEPort=<GEPortNumber> VEPort=<VEPortNumber> Domain=0x<Domain Port Host> Port=0x<Device Side>. Probable Cause Indicates an attached port with the established FICON emulated path has logged out from the switch. Recommended This may be an unexpected event, contact your vendor's customer support for assistance. Action Severity WARNING... -
Page 263: 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 264: 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 265: 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 266: 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 which has an address conflict with the CUP management port is in use. -
Page 267: 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 268 FKLB-1001 Fabric OS Message Reference 53-1001157-01...
-
Page 269: 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. The following two LSR header types are the only known types: 1 - Unicast and 3 - Multicast. -
Page 270: 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 271: 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 272: 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 273: 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 274: 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 275: Fss-1008
FSS-1008 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 five seconds. This usually indicates a problem with the internal Ethernet connection and a disruption of the synchronization process. -
Page 276: Fss-1011
FSS-1011 FSS-1011 Message <timestamp>, [FSS-1011], <sequence-number>,, INFO, <system-name>, FSS Info: <Info Message>. Probable Cause Indicates that an error has occurred. Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1001157-01... -
Page 277: 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 278 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 switch system, this message is logged when a firmware upgrade/downgrade was invoked. The new firmware version is not compatiable with the current running version.
-
Page 279: 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 280: 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 281: 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 282: 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 283: 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 284: 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 285: 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 286: 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 287: 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 288: 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 289: 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 290: 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 291: 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 292: 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 293: 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 294: 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 295: 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 296: 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 297: 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 298: 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 299: 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 300: 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 301: 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 302: 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 303: 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 304: 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 305: 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 306: 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 307: 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 308: 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 309: Fw-1196
FW-1196 FW-1196 Message <timestamp>, [FW-1196], <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 link resets that the port experiences has changed. Link resets occur due to link timeout errors that indicate no frame activity at all. -
Page 310: Fw-1216
FW-1216 Probable Cause Indicates that the number of link resets that the port experiences has changed from a value outside of the acceptable range to a value within the acceptable range. Link resets occur due to link timeout errors that indicate no frame activity at all. Both physical and hardware problems can cause link resets to increase. -
Page 311: Fw-1218
FW-1218 FW-1218 Message <timestamp>, [FW-1218], <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 cyclic redundancy check (CRC) errors has risen above the high boundary. 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 312: Fw-1241
FW-1241 Severity INFO FW-1241 Message <timestamp>, [FW-1241], <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 end-to-end (EE) cyclic redundancy check (CRC) errors has fallen below the low boundary. -
Page 313: Fw-1244
FW-1244 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-1244 Message <timestamp>, [FW-1244], <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 receives has changed. -
Page 314: Fw-1247
FW-1247 FW-1247 Message <timestamp>, [FW-1247], <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 receives has changed from a value outside of the acceptable range to a value within the acceptable range. -
Page 315: Fw-1251
FW-1251 Probable Cause Indicates that the number of end-to-end (EE) word frames that the switch transmits has risen above the high boundary. Transmit 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 316: Fw-1274
FW-1274 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-1274 Message <timestamp>, [FW-1274], <sequence-number>,, INFO, <system-name>, <Label>, is above high boundary(High=<Filter Counter>, Low=<Low value>). Current value is <Value>... -
Page 317: Fw-1297
FW-1297 Severity INFO FW-1297 Message <timestamp>, [FW-1297], <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 Telnet violations has fallen below the low boundary. Telnet violations indicate that a Telnet connection request has been received from an unauthorized IP address. -
Page 318: Fw-1300
FW-1300 Severity INFO FW-1300 Message <timestamp>, [FW-1300], <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 hypertext transfer protocol (HTTP) violations has changed. HTTP violations indicate that a browser connection request has been received from an unauthorized IP address. -
Page 319: Fw-1303
FW-1303 FW-1303 Message <timestamp>, [FW-1303], <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 hypertext transfer protocol (HTTP) violations has changed from a value outside of the acceptable range to a value within the acceptable range. -
Page 320: Fw-1306
FW-1306 FW-1306 Message <timestamp>, [FW-1306], <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 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. -
Page 321: Fw-1309
FW-1309 FW-1309 Message <timestamp>, [FW-1309], <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 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. -
Page 322: Fw-1312
FW-1312 FW-1312 Message <timestamp>, [FW-1312], <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 simple network management protocol write (WSNMP) violations has changed. WSNMP violations indicate that an SNMP “get/set” operation request has been received from an unauthorized IP address. -
Page 323: Fw-1315
FW-1315 FW-1315 Message <timestamp>, [FW-1315], <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 simple network management protocol write (WSNMP) violations has changed from a value outside of the acceptable range to a value within the acceptable range. WSNMP violations indicate that an SNMP “get/set”... -
Page 324: Fw-1318
FW-1318 FW-1318 Message <timestamp>, [FW-1318], <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 SES violations has risen above the high boundary. SES violations indicate that a small computer system interface (SCSI) Enclosure Services (SES) request has been received from an unauthorized world wide name (WWN). -
Page 325: Fw-1321
FW-1321 FW-1321 Message <timestamp>, [FW-1321], <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 simple network management server (MS) violations has fallen below the low boundary. MS violations indicate that an MS access request has been received from an unauthorized world wide name (WWN). -
Page 326: Fw-1324
FW-1324 FW-1324 Message <timestamp>, [FW-1324], <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 serial violations has changed. 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 327: Fw-1327
FW-1327 FW-1327 Message <timestamp>, [FW-1327], <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 serial violations has changed from a value outside of the acceptable range to a value within the acceptable range. -
Page 328: Fw-1330
FW-1330 FW-1330 Message <timestamp>, [FW-1330], <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 front panel violations has risen above the high boundary. 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 329: Fw-1333
FW-1333 FW-1333 Message <timestamp>, [FW-1333], <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 switch connection control policy (SCC) violations has fallen below the low 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 330: Fw-1336
FW-1336 FW-1336 Message <timestamp>, [FW-1336], <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 device cable connection (DCC) violations has changed. 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 331: Fw-1339
FW-1339 Recommended Run the errShow command to determine the device WWN, switch WWN, and switch port. Action Responses to security-class messages depend on user policies. Consult your security administrator for response strategies and policies. Severity WARNING FW-1339 Message <timestamp>, [FW-1339], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). -
Page 332: Fw-1342
FW-1342 Severity INFO FW-1342 Message <timestamp>, [FW-1342], <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 login violations has risen above the high boundary. Login violations indicate that a login failure has been detected. -
Page 333: Fw-1345
FW-1345 FW-1345 Message <timestamp>, [FW-1345], <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 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). -
Page 334: Fw-1348
FW-1348 Recommended No action is required. Action Severity INFO 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 335: Fw-1351
FW-1351 Probable Cause Indicates that the number of invalid signatures has risen above the high boundary. Invalid-signature violations indicate that a packet with an invalid signature has been received from the primary fabric configuration server (FCS). When the primary FCS downloads a new configuration to the other switches in the fabric, the packet is signed using the private key of the primary FCS. -
Page 336: Fw-1353
FW-1353 FW-1353 Message <timestamp>, [FW-1353], <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 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). -
Page 337: Fw-1356
FW-1356 Recommended No action is required. Action Severity INFO 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. -
Page 338: Fw-1359
FW-1359 Recommended Responses to security-class messages depend on user policies. Consult your security administrator Action for response strategies and policies. Severity WARNING 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>... -
Page 339: 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 340: 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 341: 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 342: 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 343: 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 344: 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 345: 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 346: 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 347: 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 348: 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 349: 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 350: 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 351: Fw-1440
FW-1440 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. Verify that the event was planned. Action Severity INFO... -
Page 352: Fw-1444
FW-1444 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. Action Severity WARNING FW-1445 Message... -
Page 353: Fw-1500
FW-1500 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 <Mails discarded>... - Page 354 FW-1510 Fabric OS Message Reference 53-1001157-01...
-
Page 355: Ham-1001
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 356: Ham-1005
HAM-1005 • 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 • Reboot:API •... -
Page 357: Ham-1007
HAM-1007 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 HAM-1007 Message <timestamp>, [HAM-1007], <sequence-number>,, CRITICAL, <system-name>,Need to reboot the system for recovery, reason: <reason name>. Probable Cause Indicates that the system in current condition needs to be rebooted to achieve a reliable recovery. - Page 358 HAM-1009 Fabric OS Message Reference 53-1001157-01...
-
Page 359: Hamk-1001
Chapter HAMK System Messages HAMK-1001 Message <timestamp>, [HAMK-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, Warm recovery failed. Probable Cause Indicates the switch failed during 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 360: 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 361: 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 362: 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 363: 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 Action... -
Page 364: Hil-1202
HIL-1202 If the fan continues to generate this message, replace the fan 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 RPMs) has fallen below the minimum threshold. Recommended Replace the fan field-replaceable unit (FRU). -
Page 365: 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 RPMs) 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 366: 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 367: Hil-1305
HIL-1305 Severity ERROR HIL-1305 Message <timestamp>, [HIL-1305], <sequence-number>,, ERROR, <system-name>, One or two fans 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 368: 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 369: 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 370: 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 371: 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 372: 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 To avoid causing damage to the switch, the system shuts down automatically. To help prevent Action future problems, make sure that all the fans are working properly. -
Page 373: 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 374: Hil-1650
HIL-1650 Recommended Ensure the power cord is connected to the unit with a valid power source and then switch on the Action unit. If the problem persists, try reseating the unit. If the problem still persists replace the FRU. Severity WARNING HIL-1650 Message... -
Page 375: 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 376 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 377: Hmon-1001
Chapter HMON System Messages HMON-1001 Message <timestamp>, [HMON-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, <Failure description> Probable Cause Indicates 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. Recommended Run the firmwareDownload command to reinstall the firmware to your switch. - Page 378 HMON-1001 Fabric OS Message Reference 53-1001157-01...
-
Page 379: Http-1001
Chapter HTTP System Messages HTTP-1001 Message <timestamp>, [HTTP-1001], <sequence-number>,, INFO, <system-name>, Switch PIDformat has changed to <current PID format>. 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 380 HTTP-1003 Fabric OS Message Reference 53-1001157-01...
-
Page 381: 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 382 IBD-1001 Fabric OS Message Reference 53-1001157-01...
-
Page 383: 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 384 IBPD-1003 Fabric OS Message Reference 53-1001157-01...
-
Page 385: Icpd-1001
Chapter ICPD System Messages ICPD-1001 Message <timestamp>, [ICPD-1001], <sequence-number>,, ERROR, <system-name>, Failed to allocate memory: (<function name>). 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 386: 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 387 ICPD-1008 Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1001157-01...
- Page 388 ICPD-1008 Fabric OS Message Reference 53-1001157-01...
-
Page 389: 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 the local IP address has occurred. - Page 390 IPAD-1001 Fabric OS Message Reference 53-1001157-01...
-
Page 391: 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 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 392: Ips-1005
IPS-1005 Probable Cause Indicates that configured Port Mode is different from the 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 393: 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 the specified port has crashed. Recommended No action is required; the port will restart automatically. Action Severity ERROR Fabric OS Message Reference 53-1001157-01... - Page 394 ISCS-1000 Fabric OS Message Reference 53-1001157-01...
-
Page 395: 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 396: 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 397: 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 398: 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 399: Kac-1002
Chapter KAC System Messages KAC-1002 Message <timestamp>, [KAC-1002], <sequence-number>,, ERROR, <system-name>, KAC(<Key Vault Type>) communication Error: Error connecting to <Backup or Primary>. Probable Cause Indicates that the key archival client is unable to communicate with the primary or backup key vault. -
Page 400: Kac-1008
KAC-1008 Probable Cause Indicates that the key archival client is unable to put to the primary or backup key vault. Recommended Determine whether the configured key value is operational, and if it is not, change the switch key Action vault settings. Severity ERROR KAC-1008... -
Page 401: Kswd-1001
Chapter KSWD System Messages KSWD-1001 Message <timestamp>, [KSWD-1001], <sequence-number>, FFDC, WARNING, <system-name>, <Software component>:<Software component Process ID> failed to refresh (<Current time>:<Refresh time>). Probable Cause Indicates one of the critical daemons is found to be nonresponsive. An abort signal is sent. Recommended Copy the warning message along with any core file information, and contact your switch service Action... - Page 402 KSWD-1003 Recommended SIGABRT is the signal thrown by the programs to abort the process. Run the supportSave command Action to determine if any core files were created. If a core file is found, run supportFtp to send all core files to a secure server location. Copy the warning message along with any core file information, and contact your switch service provider.
-
Page 403: 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 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 trace dumping. -
Page 404: 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 a trace was unable to initialize. Recommended No action is required. Action Severity ERROR... -
Page 405: Lfm-1001
Chapter LFM System Messages LFM-1001 Message <timestamp>, [LFM-1001], <sequence-number>,, INFO, <system-name>, The Logical Fabric Manager service is disabled. Probable Cause Indicates that the Logical Fabric Manager service is disabled. Note that the Logical Fabric Manager service is enabled by the factory setting and it is not user configurable. Recommended No action is required. -
Page 406: Lfm-1004
LFM-1004 LFM-1004 Message <timestamp>, [LFM-1004], <sequence-number>,, CRITICAL, <system-name>, HA is out of sync for opcode <HA OPCODE>, error value <error value>. Probable Cause Indicates the trigger for some internal logging purpose. Recommended Send the ffdc log to the support. Action Severity CRITICAL LFM-1005... -
Page 407: Log-1000
Chapter LOG System Messages LOG-1000 Message <timestamp>, [LOG-1000], <sequence-number>,, INFO, <system-name>, Previous <repeat count> message repeated times Probable Cause Indicates 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 Indicates a log message was dropped. -
Page 408: Log-1003
LOG-1003 LOG-1003 Message <timestamp>, [LOG-1003], <sequence-number>,, INFO, <system-name>, The log has been cleared. Probable Cause Indicates the persistent error log has been cleared. Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1001157-01... -
Page 409: 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 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. -
Page 410: Lsdb-1004
LSDB-1004 Severity CRITICAL LSDB-1004 Message <timestamp>, [LSDB-1004], <sequence-number>,, WARNING, <system-name>, No Link <local domain> State Record for domain Probable Cause Indicates there is no link state record for the specified local domain. Recommended No action is required. The other switch will pass the LSD once the fabric is stable. Action Severity WARNING... -
Page 411: 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 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 command (if applicable). If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers;... - Page 412 MFIC-1003 Recommended IDID mode is a fabric-wide mode; make sure that any switches added to the fabric are configured Action with the same IDID mode as the fabric. If you are enabling or disabling IDID mode, this message is for information purposes only, and no action is required. IDID mode can be set using the configure command in the CLI or checking the Advanced Web Tools Switch Admin >...
-
Page 413: 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 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 414 MPTH-1003 Fabric OS Message Reference 53-1001157-01...
-
Page 415: 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 an unexpected message has been received in the specified message queue. The queue name is always fspf_q. - Page 416 MQ-1004 Fabric OS Message Reference 53-1001157-01...
-
Page 417: Ms-1001
Chapter MS System Messages MS-1001 Message <timestamp>, [MS-1001], <sequence-number>,, WARNING, <system-name>, MS Platform Segmented port=<port number> (<port number (hex)>) (<reason for segmentation> <domain> (<domain (hex)>)) Probable Cause Indicates the management server (MS) has segmented from another switch domain at the specified port number because of errors or inconsistencies defined in the MS platform service. -
Page 418: 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 419: 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 the management server (MS) received an invalid common transport (CT) response from the switch domain. MS expects either a CT accept IU or a reject IU; the MS received neither response, which violates the Fibre Channel Generic Services (FS-GS) specification. -
Page 420: Ms-1009
MS-1009 MS-1009 Message <timestamp>, [MS-1009], <sequence-number>,, ERROR, <system-name>, RLIR event. Switch Port ID is <PID> (<PID (hex)>). Device Port Tag is <port tag>. <message text>. Probable Cause Indicates a registered link incident record (RLIR) has been generated for one of the actions indicated by the <message>. -
Page 421: Ms-1023
MS-1023 MS-1023 Message <timestamp>, [MS-1023], <sequence-number>,, INFO, <system-name>, Management Server Topology Discovery Service <Enabled or Disabled>. Probable Cause Indicates 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. - Page 422 MS-1024 Fabric OS Message Reference 53-1001157-01...
-
Page 423: 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 a duplicate E_Port State Change Number was reported. The neighbor finite state machine (NBFSM) states are as follows: •... -
Page 424: 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 the database transmit set flag was not set for the specified input state on the specified port. -
Page 425: 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 the response payload exceeds the maximum frame size the remote switch can handle. Recommended Run the firmwareDownload command to upgrade the remote switch with firmware v4.3 or higher, Action... -
Page 426: Ns-1004
NS-1004 Reduce the local device count to follow the capability of the lowest version of firmware. Severity INFO NS-1004 Message <timestamp>, [NS-1004], <sequence-number>,, INFO, <system-name>, Number of local devices <Current local device count>, exceeds the standby can support <Local device count that standby can support>, can't sync. Probable Cause Indicates the name server on the standby CP has lower supported capability than the active CP because of different firmware versions running on the active and standby CPs. -
Page 427: 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 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 428: Pdm-1004
PDM-1004 PDM-1004 Message <timestamp>, [PDM-1004], <sequence-number>,, WARNING, <system-name>, PDM memory shortage. Probable Cause Indicates 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 429: 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 430: 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 the parity data manager (PDM) process could not read data from the specified file. Recommended Run the firmwareDownload command to reinstall the firmware. -
Page 431: 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 432: Pdm-1022
PDM-1022 Probable Cause Indicates 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. Severity WARNING PDM-1022... - Page 433 PDM-1024 Fabric OS Message Reference 53-1001157-01...
- Page 434 PDM-1024 Fabric OS Message Reference 53-1001157-01...
-
Page 435: Pdtr-1001
Chapter PDTR System Messages PDTR-1001 Message <timestamp>, [PDTR-1001], <sequence-number>,, INFO, <system-name>, <informational message>. Probable Cause Indicates 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 436 PDTR-1002 Fabric OS Message Reference 53-1001157-01...
-
Page 437: 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 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 438: 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 a PCI bus hang was detected. Recommended The FRU must be replaced. -
Page 439: Pmgr-1001
Chapter PMGR System Messages PMGR-1001 Message <timestamp>, [PMGR-1001], <sequence-number>, INFO, <system-name>, Switch <FID> was successfully created. Probable Cause Indicates the switch with the specified FID was successfully created. Recommended No action is required. Action Severity INFO PMGR-1002 Message <timestamp>, [PMGR-1002], <sequence-number>, WARNING, <system-name>, Switch <FID> failed to create. -
Page 440: Pmgr-1005
PMGR-1005 Recommended No action is required. Action Severity WARNING PMGR-1005 Message <timestamp>, [PMGR-1005], <sequence-number>, INFO, <system-name>, Ports <Ports> on slot <Slot> to switch <FID> were moved successfully. Probable Cause Indicates the successful attempt to move the ports to the specified switch. Recommended No action is required. -
Page 441: Pmgr-1009
PMGR-1009 Recommended No action is required. Action Severity WARNING PMGR-1009 Message <timestamp>, [PMGR-1009], <sequence-number>, INFO, <system-name>, The base switch was successfully changed to switch <FID>. Probable Cause Indicates the successful change of the base switch. Recommended No action is required. Action Severity INFO... - Page 442 PMGR-1010 Fabric OS Message Reference 53-1001157-01...
-
Page 443: 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 the specified port is now disabled because the link on this port had multiple failures that exceeded 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 444 PORT-1005 Recommended Invoke the portCfgLport to clear the L_port configuration. Action Severity WARNING Fabric OS Message Reference 53-1001157-01...
-
Page 445: 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 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. If it does not, reboot or power cycle the switch to Action reinitiate the firmware. -
Page 446: 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 447: 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 448 PSWP-1003 Fabric OS Message Reference 53-1001157-01...
-
Page 449: 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 450: 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 451: 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 452 RAS-3004 Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1001157-01...
-
Page 453: 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 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 454: 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 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 455: 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 a domain cannot handle the zone database being committed. Recommended Reduce the zone database size. - Page 456 RCS-1008 Fabric OS Message Reference 53-1001157-01...
-
Page 457: Rkd-1001
Chapter RKD System Messages RKD-1001 Message <timestamp>, [RKD-1001], <sequence-number>,, INFO, <system-name>, <Re-key type (First time encryption/Rekey/Write Metadata)> operation <Re-key action (started/completed/cancelled)>.\nTarget: <Target physial WWN>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>.\n SessionId:<Session ID>/<Session MN> Probable Cause Indicates that a First time encryption/re-key/Write Metadata was started/completed/cancelled. Recommended No action is required. - Page 458 RKD-1003 Fabric OS Message Reference 53-1001157-01...
-
Page 459: 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 an authentication error was reported. The specified client IP address has faulty credentials. -
Page 460: 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 the SSL certificate file has been corrupted. Recommended To enable RPCD in Secure mode, install a valid SSL certificate the switch. Action Severity WARNING RPCD-1005... -
Page 461: 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 462: 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 463: 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 464 SAS-1001 Fabric OS Message Reference 53-1001157-01...
-
Page 465: Scn-1001
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 the system being busy. - Page 466 SCN-1001 Fabric OS Message Reference 53-1001157-01...
-
Page 467: 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 failed 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 468: 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 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 469: 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 a security violation was reported. The IP address of the unauthorized host is displayed in the message. -
Page 470: 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 the fabric failed to generate or validate either the public or private key pair or the certificate signing request (CSR). -
Page 471: 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 a corruption occurred during the distribution of the security database. This can occur only when the primary fabric configuration server (FCS) distributes the security database to the other switches in the fabric, then local validation finds the error in the security database. -
Page 472: Sec-1030
SEC-1030 SEC-1030 Message <timestamp>, [SEC-1030], <sequence-number>, ERROR, <system-name>, The length of the name invalid. Probable Cause Indicates a corruption occurred during the distribution of the security database. This can occur only when the primary fabric configuration server (FCS) distributes the security database to the other switches in the fabric, then local validation finds the error in the security database. -
Page 473: Sec-1034
SEC-1034 Probable Cause Indicates 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 474: Sec-1037
SEC-1037 SEC-1037 Message <timestamp>, [SEC-1037], <sequence-number>,, ERROR, <system-name>, Invalid WWN <invalid WWN> format Probable Cause Indicates 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 475: 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 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 476: 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 477: 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 there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configuration 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 478: Sec-1054
SEC-1054 SEC-1054 Message <timestamp>, [SEC-1054], <sequence-number>,, ERROR, <system-name>, Invalid FCS <list length> list length Probable Cause Indicates there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configuration 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 479: 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 there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configuration 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 480: Sec-1064
SEC-1064 Severity ERROR SEC-1064 Message <timestamp>, [SEC-1064], <sequence-number>,, ERROR, <system-name>, Failed to sign message. Probable Cause Indicates 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 481: 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 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 482: Sec-1076
SEC-1076 Probable Cause Indicates there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configuration 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. This is a rare occurrence. -
Page 483: Sec-1079
SEC-1079 SEC-1079 Message <timestamp>, [SEC-1079], <sequence-number>,, ERROR, <system-name>, The policy name <policy name> is invalid. Probable Cause Indicates 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 Message... -
Page 484: 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 485: Sec-1087
SEC-1087 Probable Cause Indicates 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 database is larger than the data distribution limit of fabric <fabric data distribution limit>... -
Page 486: 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 there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configuration 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 487: Sec-1094
SEC-1094 Probable Cause Indicates the new fabric configuration 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 488: 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 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 489: Sec-1101
SEC-1101 Probable Cause Indicates there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configuration 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. This is a rare occurrence. -
Page 490: Sec-1105
SEC-1105 Severity ERROR SEC-1105 Message <timestamp>, [SEC-1105], <sequence-number>,, ERROR, <system-name>, Fail to disable secure mode on all switches. Probable Cause Indicates the switch failed to disable security in the fabric. This could happen if the switch cannot get the required resources to complete the command, and sending to a remote domain fails or the remote domain returns an error. -
Page 491: Sec-1110
SEC-1110 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. Recommended Verify that the security event was planned. -
Page 492: Sec-1113
SEC-1113 Recommended Make sure that the new FCS policy is the same as the current FCS policy on the switch. Action Severity ERROR SEC-1113 Message <timestamp>, [SEC-1113], <sequence-number>,, WARNING, <system-name>, <Key> [ <Feature> license ] going to expire in <Expiry_days> days. Probable Cause Indicates the license period will expire soon. -
Page 493: Sec-1117
SEC-1117 Probable Cause Indicates there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configuration 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. This is a rare occurrence. -
Page 494: Sec-1121
SEC-1121 SEC-1121 Message <timestamp>, [SEC-1121], <sequence-number>,, ERROR, <system-name>, Time is out of <text> range when Probable Cause Indicates the time on the switch is not synchronized with the primary fabric configuration server (FCS), the data packet is corrupted, or a replay attack is launched on the switch. Recommended Verify the security event was planned. -
Page 495: Sec-1126
SEC-1126 Severity INFO SEC-1126 Message <timestamp>, [SEC-1126], <sequence-number>,, INFO, <system-name>, Secure mode has been disabled. Probable Cause Indicates that a secure mode disable operation completed successfully. Recommended Verify the security event was planned. If the security event was planned, no action is required. If the Action security event was not planned, take appropriate action as defined by your enterprise security policy. -
Page 496: Sec-1137
SEC-1137 Probable Cause Indicates the receiving switch fails to validate the security database sent from the primary fabric configuration 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 497: Sec-1142
SEC-1142 Probable Cause Indicates that the receiving switch failed to validate the security database sent from the primary fabric configuration 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 498: Sec-1153
SEC-1153 Probable Cause Indicates 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. The values wrap around after 128. If a DCC policy contains an index/area of 127 before changing to extended-edge PID, then the new index/area is 15, because of the wraparound. -
Page 499: Sec-1156
SEC-1156 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. Recommended Reduce the size of the specified policy database. -
Page 500: Sec-1159
SEC-1159 SEC-1159 Message <timestamp>, [SEC-1159], <sequence-number>,, INFO, <system-name>, Non_Reachable domain <Domain ID>. Probable Cause Indicates there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configuration 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 501: Sec-1165
SEC-1165 Severity ERROR SEC-1165 Message <timestamp>, [SEC-1165], <sequence-number>,, ERROR, <system-name>, Low memory, failed to enable security on all switches. Probable Cause Indicates the system is low on memory. Recommended Wait a few minutes and try the command again. Action Severity ERROR SEC-1166 Message... -
Page 502: Sec-1170
SEC-1170 Probable Cause Indicates 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 503: Sec-1173
SEC-1173 Recommended Verify all switches in the fabric are in time synchronization with the primary and that no external Action entity is trying to access the fabric. When verification is complete, retry the operation. Severity ERROR SEC-1173 Message <timestamp>, [SEC-1173], <sequence-number>,, ERROR, <system-name>, Lost contact with Primary FCS switch. -
Page 504: Sec-1180
SEC-1180 Recommended Verify all switches in the fabric are in time synchronization with the primary and that no external Action entity is trying to access the fabric. When verification is complete, retry the operation. Severity ERROR SEC-1180 Message <timestamp>, [SEC-1180], <sequence-number>,, INFO, <system-name>, Added account <user name>... -
Page 505: Sec-1184
SEC-1184 Recommended Retry the command with a valid value. 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-1184 Message <timestamp>, [SEC-1184], <sequence-number>,, INFO, <system-name>, <server> configuration change, action <action>, server ID <server>. -
Page 506: Sec-1187
SEC-1187 SEC-1187 Message <timestamp>, [SEC-1187], <sequence-number>,, INFO, <system-name>, Security <switch WWN> violation: Unauthorized switch tries to join fabric. Probable Cause Indicates a switch connection control (SCC) security violation was reported. The specified unauthorized switch attempts to join the fabric. Recommended Check the switch connection control policy (SCC) policy to verify the switches allowed in the fabric. -
Page 507: Sec-1190
SEC-1190 SEC-1190 Message <timestamp>, [SEC-1190], <sequence-number>,, INFO, <system-name>, Security <IP address> violation: Unauthorized host with IP address tries to do SNMP read operation. Probable Cause Indicates an SNMP security violation was reported. The specified unauthorized host attempted to perform a read SNMP operation. Recommended Check the RSNMP policy to verify the hosts allowed access to the fabric through SNMP read Action... -
Page 508: Sec-1194
SEC-1194 Probable Cause Indicates a specified login security violation was reported. The incorrect password was used while trying to log in through the specified connection method; the login failed. Recommended The error message lists the violating IP address. Verify that this IP address is being used by a valid Action switch admin. -
Page 509: Sec-1197
SEC-1197 Severity WARNING SEC-1197 Message <timestamp>, [SEC-1197], <sequence-number>,, INFO, <system-name>, Changed account <user name>. Probable Cause Indicates the specified account has changed. Recommended No action is required. Action Severity INFO SEC-1198 Message <timestamp>, [SEC-1198], <sequence-number>,, INFO, <system-name>, Security <IP address> violation: Unauthorized host with IP address tries to establish API connection. -
Page 510: Sec-1201
SEC-1201 Probable Cause Indicates a management server (MS) forward security violation was reported. A management server command was forwarded from a non-primary fabric configuration server (FCS) switch. Recommended Check the MS policy and verify that the connection is allowed. If the connection is allowed but not Action specified, enable the connection in the MS policy. -
Page 511: Sec-1250
SEC-1250 Severity INFO SEC-1250 Message <timestamp>, [SEC-1250], <sequence-number>,, WARNING, <system-name>, DCC enforcement API failed: <failed action> err=<status>, key=<data> Probable Cause Indicates an internal error caused the DCC policy enforcement to fail. 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. -
Page 512: Sec-1301
SEC-1301 Probable Cause Indicates the switch is set up with VC-encoded mode. Recommended Turn off VC-encoded mode before enabling security. Action Severity INFO SEC-1301 Message <timestamp>, [SEC-1301], <sequence-number>,, INFO, <system-name>, This switch is in interop mode. Security is not supported. Probable Cause Indicates the switch is interop-mode enabled. -
Page 513: Sec-1304
SEC-1304 SEC-1304 Message <timestamp>, [SEC-1304], <sequence-number>,, INFO, <system-name>, This switch has no security license. Probable Cause Indicates there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configuration 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 514: Sec-1307
SEC-1307 SEC-1307 Message Got response <timestamp>, [SEC-1307], <sequence-number>,, INFO, <system-name>, from <Radius/LDAP server identity> server <Radius/LDAP server identity>. Probable Cause Indicates that after some servers timed out, the specified remote authentication dial-in user service (RADIUS/LDAP) server responded to a switch request. Recommended If the message appears frequently, move the responding server to the top of the RADIUS/LDAP Action... -
Page 515: Sec-1311
SEC-1311 Severity INFO SEC-1311 Message <timestamp>, [SEC-1311], <sequence-number>,, ERROR, <system-name>, Security mode cannot be enabled because one or more of the password policies is not set to default value. Probable Cause Indicates the security enable failed on the fabric because one or more switches in the fabric have password policies that are not set to the default value. -
Page 516: Sec-1315
SEC-1315 Probable Cause Indicates the call to the EM module to retrieve the IP address failed. Recommended Reboot the system to fix this error. If the problem persists contact your switch service provider. Action Severity ERROR SEC-1315 Message <timestamp>, [SEC-1315], <sequence-number>,, ERROR, <system-name>, <Name of command >... -
Page 517: Sec-1318
SEC-1318 SEC-1318 Message <timestamp>, [SEC-1318], <sequence-number>,, INFO, <system-name>, Transaction rejected due to inconsistent fabric Probable Cause Indicates that some domains detected an inconsistent fabric. Recommended Resolve the policy conflict, if there is one, then wait for the fabric to stabilize. Retry the distribution. Action Severity INFO... -
Page 518: Sec-1322
SEC-1322 Severity ERROR SEC-1322 Message <timestamp>, [SEC-1322], <sequence-number>,, WARNING, <system-name>, Some DCC policy is too large, distribution cancelled Probable Cause Indicates this fabric is not able to support a device connection control (DCC) policy with more than 256 ports. Recommended Reconfigure any policy that includes more than 256 ports in its member list, then save the policy Action configuration changes. -
Page 519: Sec-1326
SEC-1326 Recommended No action is required unless the switch must remain in the fabric. If the switch must remain in the Action fabric, add the switch world wide name (WWN) to the SCC policy, then attempt to join the switch with the fabric. -
Page 520: Sec-1329
SEC-1329 SEC-1329 Message <timestamp>, [SEC-1329], <sequence-number>,, ERROR, <system-name>, IPFilter enforcement: Failed to enforce ipfilter policy of <policy Type> type because of <Error code>. Probable Cause Indicates the IP filter policy enforcement failed due to internal system failure. Recommended Run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command Action and contact your switch service provider. -
Page 521: Sec-1333
SEC-1333 Recommended Remove either the FCS from the fabric-wide policy, or remove 5.3 and 5.2 switches from the fabric, Action or set the fabric-wide mode for FCS as Strict. Severity ERROR SEC-1333 Message <timestamp>, [SEC-1333], <sequence-number>,, ERROR, <system-name>, <Name of command>... -
Page 522: Sec-3037
SEC-3037 SEC-3037 Message <timestamp>, [SEC-3037], <sequence-number>, AUDIT, INFO, <system-name>, Event: ipfilter, Status: success, Info: <IP Filter Policy> ipfilter policy activated. Probable Cause Indicates that that the specified IP filter policy has been activated. 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 523: Sec-3051
SEC-3051 Recommended Verify the security event was planned. If the security event was planned, no action is required. If the Action security event was not planned, take appropriate action as defined by your enterprise security policy. Severity INFO SEC-3051 Message <timestamp>, [SEC-3051], <sequence-number>, AUDIT, INFO, <system-name>, The license key <key>... - Page 524 SEC-3051 Fabric OS Message Reference 53-1001157-01...
-
Page 525: Snmp-1001
Chapter SNMP System Messages SNMP-1001 Message <timestamp>, [SNMP-1001], <sequence-number>,, ERROR, <system-name>, SNMP service is not available <Reason>. Probable Cause Indicates 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 the IP address for the Ethernet and Fibre Channel interface is set correctly. -
Page 526: Snmp-1004
SNMP-1004 SNMP-1004 Message <timestamp>, [SNMP-1004], <sequence-number>, FFDC, ERROR, <system-name>, Incorrect SNMP configuration. Probable Cause Indicates 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 527: Snmp-1008
SNMP-1008 Severity INFO SNMP-1008 Message <timestamp>, [SNMP-1008], <sequence-number>,, INFO, <system-name>, The last device change happened at: <string>. Probable Cause Indicates the last device change time. Recommended Execute the nsshow to view the current device status. Action Severity INFO Fabric OS Message Reference 53-1001157-01... - Page 528 SNMP-1008 Fabric OS Message Reference 53-1001157-01...
-
Page 529: Spc-1001
Chapter SPC System Messages SPC-1001 Message <timestamp>, [SPC-1001], <sequence-number>,, INFO, <system-name>, <slot number containing Encryption Engine>, Cryptographic operation enabled. Probable Cause Indicates the cryptographic operation is enabled on an encryption engine. Recommended No action is required. Action Severity INFO SPC-1002 Message <timestamp>, [SPC-1002], <sequence-number>,, INFO, <system-name>, <slot number containing Encryption Engine>, Cryptographic operation disabled. -
Page 530: Spc-2001
SPC-2001 SPC-2001 Message <timestamp>, [SPC-2001], <sequence-number>,, ERROR, <system-name>, <slot number containing Encryption Engine>, <module name>: Crypto error asserted by Vader/OB1 0x%x. Probable Cause Indicates the Crypto error asserted by FPGA. Recommended No action is required. Action Severity INFO SPC-2002 Message <timestamp>, [SPC-2002], <sequence-number>,, CRITICAL, <system-name>, <slot number containing Encryption Engine>, <module name>: Tamper Event: Crypto subsystem cover tampered. -
Page 531: Spc-2005
SPC-2005 SPC-2005 Message <timestamp>, [SPC-2005], <sequence-number>,, INFO, <system-name>, <slot number containing Encryption Engine>, <module name>: FPGA firmware download success: 0x%x. Probable Cause Indicates the FPGA download was successful. Recommended No action is required. Action Severity INFO SPC-2006 Message <timestamp>, [SPC-2006], <sequence-number>,, ERROR, <system-name>, <slot number containing Encryption Engine>, <module name>: Crypto post tests failed: 0x%x. -
Page 532: Spc-2009
SPC-2009 SPC-2009 Message <timestamp>, [SPC-2009], <sequence-number>,, CRITICAL, <system-name>, <slot number containing Encryption Engine>, <module name>: Tamper event: User zeroization. Probable Cause Indicates the Tamper event triggered due to a user zeroize request. Recommended EE is zeroized. User needs to run initEE and regEE. Action Severity CRITICAL... -
Page 533: Spc-3001
SPC-3001 SPC-3001 Message <timestamp>, [SPC-3001], <sequence-number>,, ERROR, <system-name>, <slot number containing Encryption Engine>, <module name>: No input KEK for DEK inject, DEK: <DEK octet 1> <DEK octet 2> <DEK octet 3> <DEK octet 4>, KEK: <KEK octet 1> <KEK octet 2> <KEK octet 3> <KEK octet 4>. Probable Cause Indicates the wrapping KEK for the DEK to be injected does not exist within the EE Crypto Module. -
Page 534: Spc-3005
SPC-3005 Probable Cause Indicates the output wrapping KEK for the DEK to be created does not exist within the EE Crypto Module. Recommended For opaque key vaults such as RKM, recover the missing Master Key to current or alternate Action position. -
Page 535: Spc-3007
SPC-3007 SPC-3007 Message <timestamp>, [SPC-3007], <sequence-number>,, ERROR, <system-name>, <slot number containing Encryption Engine>, <module name>: DEK create error: <SP status code>, info: <other info>. Probable Cause Indicates the cause depends on the SP status code: • 2 - Invalid input DEK specification •... -
Page 536: Spc-3010
SPC-3010 SPC-3010 Message <timestamp>, [SPC-3010], <sequence-number>,, WARNING, <system-name>, <slot number containing Encryption Engine>, <module name>: SEK integrity failure during initialization. Probable Cause Indicates the Crypto Module internal Secret Encryption Key has been corrupted or has not been initialized. Recommended Run initEE and regEE. Action Severity ERROR... -
Page 537: Spc-3014
SPC-3014 Recommended Contact technical support. Action Severity ERROR SPC-3014 Message <timestamp>, [SPC-3014], <sequence-number>,, ERROR, <system-name>, <slot number containing Encryption Engine>, <module name>: RNG compare failure: successive values match. Probable Cause Indicates the Crypto Module internal random number generator failed. Recommended Contact technical support. - Page 538 SPC-3015 Fabric OS Message Reference 53-1001157-01...
-
Page 539: Spm-1001
Chapter SPM System Messages SPM-1001 Message <timestamp>, [SPM-1001], <sequence-number>,, ERROR, <system-name>, Init fails: <Reason>. Probable Cause Indicates SPM failed to initialize. Recommended Check system resources and reboot switch. Action Severity ERROR SPM-1002 Message <timestamp>, [SPM-1002], <sequence-number>,, WARNING, <system-name>, Generic SPM Warning: <Reason>. -
Page 540: Spm-1005
SPM-1005 Recommended No action is required. Action Severity INFO SPM-1005 Message <timestamp>, [SPM-1005], <sequence-number>,, INFO, <system-name>, Set EE Control slot <slot> action <action>. Probable Cause User configured. Recommended No action is required. Action Severity INFO SPM-1006 Message <timestamp>, [SPM-1006], <sequence-number>,, INFO, <system-name>, Registered Certificate of type <cert_type>. -
Page 541: Spm-1009
SPM-1009 Recommended No action is required. Action Severity INFO SPM-1009 Message <timestamp>, [SPM-1009], <sequence-number>,, ERROR, <system-name>, <cert> Certificate is missing. Probable Cause User configured. Recommended Run cryptocfg --initnode. Action Severity ERROR SPM-1010 Message <timestamp>, [SPM-1010], <sequence-number>,, ERROR, <system-name>, <cert> Key Vault Certificate is missing. - Page 542 SPM-1010 Fabric OS Message Reference 53-1001157-01...
-
Page 543: 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 the supportSave command was used to transfer support information to a remote location. Recommended No action is required. -
Page 544: 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 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 545: 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 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 546: Sulb-1004
SULB-1004 SULB-1004 Message <timestamp>, [SULB-1004], INFO, FIRMWARE, <event-initiator-details>, <event-location>, , Firmwarecommit has completed. Probable Cause Indicates 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 547: 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 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 548 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 549 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 550 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 551 SULB-1009 TABLE 7 Error Messages and Error Codes Error Message Error Code “firmwareDownload timed out.” 0x23 "Our of disk space." 0x24 “Primary filesystem is inconsistent. Run firmwareRestore to restore the original firmware, or 0x25 contact your service provider for recovery.” "The post-install script failed."...
- Page 552 SULB-1009 0x24 - out of disk space. This error may occur because some coredump files have not been removed from the filesystem and are using up disk space. Remove these coredump files using the supportSave command before proceeding. 0x29 - The pre-install script failed. This error may be caused by an unsupported blade type in the chassis.
-
Page 553: Sulb-1010
SULB-1010 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. In that case, run firmwareDownload single mode (-s) to upgrade the firmware on the standby CP to the same version as the active CP. -
Page 554: Sulb-1018
SULB-1018 Severity ERROR SULB-1018 Message <timestamp>, [SULB-1018], <sequence-number>, AUDIT, ERROR, <system-name>, Firmwaredownload timed out in slot <Slot number>. Probable Cause Indicates there may be an error caused by the blade initialization issue after the new firmware is downloaded and the blade is rebooted. The error may also be caused by the internal Ethernet issue or by the persistent storage failure. -
Page 555: Sulb-1022
SULB-1022 SULB-1022 Message <timestamp>, [SULB-1022], <sequence-number>,, WARNING, <system-name>, The blade in slot <Slot number> has rebooted successfully with new firmware. Probable Cause Indicates that the blade in the specified slot has rebooted with new firmware. This is a normal step in the firmwareDownload process. -
Page 556: Sulb-1025
SULB-1025 SULB-1025 Message <timestamp>, [SULB-1025], <sequence-number>,, WARNING, <system-name>, The blade in slot <Slot number> will reboot with the new firmware. Probable Cause Indicates new firmware has been downloaded to the specified AP blade and that the AP blade will reboot to activate it. Recommended Wait for the blade to reboot. -
Page 557: Sulb-1032
SULB-1032 Recommended Wait for the operation to complete. Action Severity WARNING SULB-1032 Message <timestamp>, [SULB-1032], <sequence-number>, AUDIT, WARNING, <system-name>, Relocating an internal firmware image on the CP. Probable Cause Indicates the switch has started a firmware download to the co-CPU. Recommended Wait for the operation to complete. -
Page 558: Sulb-1036
SULB-1036 Probable Cause Indicates an error has occurred during the relocation of the internal image. The error may be caused by inconsistent internal firmware image. It may also be caused by the internal Ethernet or persistent storage hardware failure. Recommended Reset the switch. -
Page 559: 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 the switch is enabled before it is ready. Recommended If the message persists, run supportFtp (as needed) to set up automatic FTP transfers;... -
Page 560: 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 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 561: 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 562: 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 563: 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 564: 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 565: Sysm-1001
Chapter SYSM System Messages SYSM-1001 Message <timestamp>, [SYSM-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, No memory. Probable Cause Indicates 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 566: Sysm-1004
SYSM-1004 SYSM-1004 Message <timestamp>, [SYSM-1004], <sequence-number>,, ERROR, <system-name>, Failed to retrieve current chassis configuration option, ret=<Unknown> Probable Cause Indicates 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 567: Tape-1001
Chapter TAPE System Messages TAPE-1001 Message <timestamp>, [TAPE-1001], <sequence-number>, FFDC, INFO, <system-name>, Key acquisition for <Pool or Container><Begins or Complete>. Probable Cause Indicates that the key acquisition for the pool or the container has begun or is complete. Recommended No action is required. Action Severity INFO... - Page 568 TAPE-1001 Fabric OS Message Reference 53-1001157-01...
-
Page 569: 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 570: 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 571: 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 572: 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 573: Trck-1001
Chapter TRCK System Messages TRCK-1001 Message <timestamp>, [TRCK-1001], <sequence-number>,, INFO, <system-name>, Successful login by user <User>. Probable Cause Indicates 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 login by user <User>. -
Page 574: Trck-1005
TRCK-1005 Probable Cause Indicates 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 575: Ts-1001
Chapter TS System Messages TS-1001 Message <timestamp>, [TS-1001], <sequence-number>,, WARNING, <system-name>, NTP Query failed: <error code>. Probable Cause Indicates 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 576: Ts-1006
TS-1006 TS-1006 Message <timestamp>, [TS-1006], <sequence-number>,, INFO, <system-name>, <message>. Probable Cause Indicates 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 577 TS-1008 Fabric OS Message Reference 53-1001157-01...
- Page 578 TS-1008 Fabric OS Message Reference 53-1001157-01...
-
Page 579: 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 580: Ucst-1025
UCST-1025 UCST-1025 Message <timestamp>, [UCST-1025], <sequence-number>,, INFO, <system-name>, In-order delivery option has been enabled with Lossless-DLS option. Probable Cause Indicates the IOD option has been enabled for the switch. This option guarantees in-order delivery of frames during topology changes. Recommended No action is required. -
Page 581: 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 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 582 UPTH-1001 Fabric OS Message Reference 53-1001157-01...
-
Page 583: 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 the SSL certificate file is either invalid or absent. Recommended Install a valid key file. Action Severity WARNING... -
Page 584: 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 the size of the HTTP log file exceeded the maximum limit. Recommended No action is required. Action Severity INFO... -
Page 585: Zolb-1001
Chapter ZOLB System Messages ZOLB-1001 Message <timestamp>, [ZOLB-1001], <sequence-number>,, ERROR, <system-name>, ZONELIB <error message> Probable Cause Indicates 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 586 ZOLB-1001 Fabric OS Message Reference 53-1001157-01...
-
Page 587: 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 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 588: 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 589: 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 590: 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 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 591: Zone-1018
ZONE-1018 Probable Cause Indicates 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 592: 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 the effective zone configuration has changed to the name displayed. Recommended Verify this zone configuration change was done on purpose. If the new effective zone configuration Action is correct, no action is necessary. -
Page 593: 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 the zoning transaction was aborted due to a variety of potential errors. The error reason variable can be one of the following: •... -
Page 594: 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 the current zone database could not be converted to reflect the PID format change. -
Page 595: Zone-1034
ZONE-1034 Probable Cause Indicates 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 596: 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 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 597: Zone-1041
ZONE-1041 Severity INFO ZONE-1041 Message <timestamp>, [ZONE-1041], <sequence-number>,, WARNING, <system-name>, Unstable link detected during merge at port (<Port number>). 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 598: 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 599: Zone-1049
ZONE-1049 ZONE-1049 Message <timestamp>, [ZONE-1049], <sequence-number>,, ERROR, <system-name>, ZONE AD-DefZone conflict detected while system initialization. Probable Cause Indicates that there is an AD-DefZone conflict. Recommended Check and resolve the default zone mismatch issue. Action Severity ERROR ZONE-1050 Message <timestamp>, [ZONE-1050], <sequence-number>,, INFO, <system-name>, The Interop Safe Zoning mode is set to Enabled. -
Page 600: Zone-1053
ZONE-1053 ZONE-1053 Message <timestamp>, [ZONE-1053], <sequence-number>,, INFO, <system-name>, The Default Zone state is set to Disabled. Probable Cause Indicates the Interop Default Zone attribute state is disabled. Recommended Verify if the Interop Default Zone attribute state change was done on purpose. Action Severity INFO... - Page 601 Section Audit Log Messages This section provides the Audit messages, including: • AUDIT AG System Messages ........545 •...
-
Page 603: Ag-1029
Chapter AUDIT AG System Messages AG-1029 Message AUDIT, <timestamp>, [AG-1029], INFO, CFG, <event-initiator-details>, <event-location>, , F_Port to N_Port mapping has been updated for N_Port <n_port>. Probable Cause Indicates that the F_Ports mapped to an N_Port have changed and the config file has been updated. - Page 604 AG-1029 Fabric OS Message Reference 53-1001157-01...
-
Page 605: 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 606: 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 607: 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 608 AUTH-3008 Fabric OS Message Reference 53-1001157-01...
-
Page 609: Conf-1020
Chapter AUDIT CONF System Messages CONF-1000 Message AUDIT, <timestamp>, [CONF-1000], INFO, CFG, <event-initiator-details>, <event-location>, , configDownload completed successfully. <Info about the 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 610 CONF-1022 Fabric OS Message Reference 53-1001157-01...
-
Page 611: Fcip-1002
Chapter AUDIT FCIP System Messages FCIP-1002 Message AUDIT, <timestamp>, [FCIP-1002], INFO, CFG, <event-initiator-details>, <event-location>, , An IPsec/IKE policy was added. Probable Cause Indicates that an IPsec/IKE policy was added and the config file was updated. Recommended No action is required. Action Severity INFO... - Page 612 FCIP-1003 Fabric OS Message Reference 53-1001157-01...
-
Page 613: Ficu-1011
Chapter AUDIT FICU System Messages FICU-1011 Message AUDIT, <timestamp>, [FICU-1011], INFO, CFG, <event-initiator-details>, <event-location>, , FMS mode has been enabled. Probable Cause Indicates the FICON Management server mode has been enabled. Recommended No action is required. Action Severity INFO FICU-1012 Message AUDIT, <timestamp>, [FICU-1012], INFO, CFG, <event-initiator-details>, <event-location>, , FMS mode has been disabled. - Page 614 FICU-1012 Fabric OS Message Reference 53-1001157-01...
-
Page 615: 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-1001157-01... - Page 616 FW-3001 Fabric OS Message Reference 53-1001157-01...
-
Page 617: 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 618 HTTP-1003 Fabric OS Message Reference 53-1001157-01...
-
Page 619: Ipad-1002
Chapter AUDIT IPAD System Messages IPAD-1002 Message AUDIT, <timestamp>, [IPAD-1002], INFO, CFG, <event-initiator-details>, <event-location>, , Switchname has been successfully changed to <Switch name>. Probable Cause Indicates that a change with the switch name has occured. Recommended No action is required. Action Severity INFO... - Page 620 IPAD-1002 Fabric OS Message Reference 53-1001157-01...
-
Page 621: Port-1006
Chapter AUDIT PORT System Messages PORT-1006 Message AUDIT, <timestamp>, [PORT-1006], INFO, CFG, <event-initiator-details>, <event-location>, , Configuration changed for port (ID: <port number>) in No_Module or No_Light state. Probable Cause Indicates the configuration changes were made to an offline port in No_Module or No_Light state. Recommended No action is required. - Page 622 PORT-1009 Probable Cause Indicates a GigE port has been disabled. Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1001157-01...
-
Page 623: 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 the security mode of the fabric was either enabled or disabled. Recommended Verify the security mode change was planned. -
Page 624: Sec-3004
SEC-3004 Recommended Verify the new policy creation was planned. If the new policy creation was planned, no action is Action required. If the new policy creation was not planned, take appropriate action as defined by your enterprise security policy. Severity INFO SEC-3004 Message... -
Page 625: Sec-3007
SEC-3007 Recommended Verify the removal of members to the policy was planned. If the removal of members was planned, Action no action is required. If the removal of members was not planned, take appropriate action as defined by your enterprise security policy. Severity INFO SEC-3007... -
Page 626: Sec-3010
SEC-3010 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 a user has reset all the security statistics. Recommended Verify the security statistics were intentionally reset. If the security statistics were intentionally Action reset, no action is required. -
Page 627: Sec-3014
SEC-3014 Recommended Verify 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. Severity INFO SEC-3014... -
Page 628: Sec-3017
SEC-3017 Severity INFO SEC-3017 Message AUDIT, <timestamp>, [SEC-3017], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: <Event Related Info>. Probable Cause Indicates a user has changed the remote authentication dial-in user service (RADIUS) configuration. Recommended Verify the RADIUS configuration was intentionally changed. If the RADIUS configuration was Action intentionally changed, no action is required. -
Page 629: Sec-3021
SEC-3021 Probable Cause Indicates a successful login occurred. An IP address is displayed when the login occurs over a remote connection. Recommended Verify the security event was planned. If the security event was planned, no action is required. If the Action security event was not planned, take appropriate action as defined by your enterprise security policy. -
Page 630: Sec-3024
SEC-3024 SEC-3024 Message AUDIT, <timestamp>, [SEC-3024], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: User account [<User Name>], password changed. Probable Cause Indicates the user's password was changed. Recommended Verify the security event was planned. If the security event was planned, no action is required. If the Action security event was not planned, take appropriate action as defined by your enterprise security policy. -
Page 631: Sec-3028
SEC-3028 Recommended Verify the security event was planned. If the security event was planned, no action is required. If the Action security event was not planned, take appropriate action as defined by your enterprise security policy. Severity INFO SEC-3028 Message AUDIT, <timestamp>, [SEC-3028], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: User account [<User Name>] deleted. -
Page 632: Sec-3031
SEC-3031 SEC-3031 Message AUDIT, <timestamp>, [SEC-3031], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Distributed<List of Databases> db(s) to <Number of domains> domains, dom-id(s)<List of Domains>. Probable Cause Indicates that the specified event has occurred. Recommended Verify the event was planned. If the event was planned, no action is required. If the event was not Action planned, take appropriate action as defined by your enterprise security policy. -
Page 633: Sec-3035
SEC-3035 Severity INFO SEC-3035 Message AUDIT, <timestamp>, [SEC-3035], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: ipfilter, Status: success, Info: <IP Filter Policy> IP filter policy(ies) saved. Probable Cause Indicates the specified IP filter policies have been saved. Recommended Verify the security event was planned. If the security event was planned, no action is required. If the Action security event was not planned, take appropriate action as defined by your enterprise security policy. -
Page 634: Sec-3039
SEC-3039 Probable Cause Indicates the specified IP filter policy failed to activate. Recommended Verify the security event was planned. If the security event was planned, no action is required. If the Action security event was not planned, take appropriate action as defined by your enterprise security policy. -
Page 635: Sec-3044
SEC-3044 SEC-3044 Message AUDIT, <timestamp>, [SEC-3044], INFO, SECURITY, <event-initiator-details>, <event-location>, FIPS mode has been changed to <Fips Mode>. Probable Cause Indicates there was a change in the FIPS mode. Recommended Verify the security event was planned. If the security event was planned, no action is required. If the Action security event was not planned, take appropriate action as defined by your enterprise security policy. -
Page 636: Sec-3048
SEC-3048 SEC-3048 Message AUDIT, <timestamp>, [SEC-3048], INFO, SECURITY, <event-initiator-details>, <event-location>, FIPS mode has been enabled in the system using force option. Probable Cause Indicates the system has been forced to FIPS mode. Recommended Verify the security event was planned. If the security event was planned, no action is required. If the Action security event was not planned, take appropriate action as defined by your enterprise security policy. -
Page 637: 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 638 SNMP-1006 Fabric OS Message Reference 53-1001157-01...
-
Page 639: 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 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 640: Sulb-1009
SULB-1004 SULB-1004 Message AUDIT, <timestamp>, [SULB-1004], INFO, FIRMWARE, <event-initiator-details>, <event-location>, , Firmwarecommit has completed. Probable Cause Indicates 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 641 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 642 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 643 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 644 SULB-1009 TABLE 10 Error Messages and Error Codes Error Message Error Code “firmwareDownload timed out.” 0x23 "Our of disk space." 0x24 “Primary filesystem is inconsistent. Run firmwareRestore to restore the original firmware, or 0x25 contact your service provider for recovery.” "The post-install script failed."...
- Page 645 SULB-1009 0x24 - out of disk space. This error may occur because some coredump files have not been removed from the filesystem and are using up disk space. Remove these coredump files using the supportSave command before proceeding. 0x29 - The pre-install script failed. This error may be caused by an unsupported blade type in the chassis.
-
Page 646: Sulb-1017
SULB-1010 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. In that case, run firmwareDownload single mode (-s) to upgrade the firmware on the standby CP to the same version as the active CP. -
Page 647: Sulb-1020
SULB-1020 Recommended Run the slotShow command. If the blade is in a FAULTY state, run the slotPowerOff and Action slotPowerOn commands to trigger another firmwareDownload. If the blade is stuck in LOADING state, remove and re-insert the blade to trigger another firmwareDownload. If the problem persists, contact your switch service provider. -
Page 648: Sulb-1024
SULB-1024 Recommended The firmwareCommit command will be started automatically after the blade boots up to repair the Action secondary 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. -
Page 649: Sulb-1031
SULB-1031 Recommended The firmwareDownload command will continue after the switch has rebooted. Run the Action firmwareDownloadStatus 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 the switch has rebooted with the new firmware and is relocating the AP firmware. -
Page 650: Sulb-1035
SULB-1035 Recommended Reboot the switch. This will cause the internal image to be relocated again. Use the Action firmwareDownloadStatus command 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 651: Swch-1012
Chapter AUDIT SWCH System Messages SWCH-1012 Message AUDIT, <timestamp>, [SWCH-1012], INFO, CFG, <event-initiator-details>, <event-location>, , Trunk Area (<trunk area>) has been enabled for one or more ports. Probable Cause Indicates a Trunk Area has been enabled for one or more ports and the config file has been updated. - Page 652 SWCH-1014 Fabric OS Message Reference 53-1001157-01...
-
Page 653: Ucst-1021
Chapter AUDIT UCST System Messages UCST-1021 Message AUDIT, <timestamp>, [UCST-1021], INFO, CFG, <event-initiator-details>, <event-location>, , In-order delivery option has been enabled. Probable Cause Indicates the IOD option has been enabled for the switch. This option guarantees in-order delivery of frames during topology changes. Recommended No action is required. -
Page 654: Ucst-1024
UCST-1024 UCST-1024 Message AUDIT, <timestamp>, [UCST-1024], INFO, CFG, <event-initiator-details>, <event-location>, , Dynamic Load Sharing option has been disabled. Probable Cause Indicates the DLS option has been disabled for the switch. Recommended No action is required. Action Severity INFO UCST-1025 Message AUDIT, <timestamp>, [UCST-1025], INFO, CFG, <event-initiator-details>, <event-location>, , In-order delivery option has been enabled with Lossless-DLS option. - Page 655 UCST-1027 Severity INFO Fabric OS Message Reference 53-1001157-01...
- Page 656 UCST-1027 Fabric OS Message Reference 53-1001157-01...
-
Page 657: 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 658: 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 the event was planned. If the event was planned, no action is required. If the event was not Action planned, take appropriate action as defined by your enterprise security policy. -
Page 659: 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 the specified zone configuration has been enabled. Recommended Verify the event was planned. If the event was planned, no action is required. If the event was not Action planned, take appropriate action as defined by your enterprise security policy. -
Page 660: 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 the specified zone object has been expunged. Recommended Verify the event was planned. If the event was planned, no action is required. If the event was not Action planned, take appropriate action as defined by your enterprise security policy. -
Page 661: 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 the event was planned. If the event was planned, no action is required. If the event was not Action planned, take appropriate action as defined by your enterprise security policy. -
Page 662: 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 the specified admin domain (AD) object has been deactivated. Recommended Verify the event was planned. If the event was planned, no action is required. If the event was not Action planned, take appropriate action as defined by your enterprise security policy. -
Page 663: 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 the current admin domain (AD) configuration has been saved to flash. Recommended Verify the event was planned. - Page 664 ZONE-3025 Severity INFO Fabric OS Message Reference 53-1001157-01...
Need help?
Do you have a question about the A7533A - Brocade 4Gb SAN Switch Base and is the answer not in the manual?
Questions and answers