Page 1 53-1001767-01 ® 30 March 2010 Fabric OS Message Reference Supporting Fabric OS v6.4.0...
Page 2: Document History
Copyright © 2006-2010 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, IronPoint, IronShield, IronView, IronWare, JetCore, NetIron, SecureIron, ServerIron, StorageX, and TurboIron are registered trademarks, and DCFM, Extraordinary Networks, and SAN Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.
Page 3 Title Publication Summary of changes Date number Diagnostic and System Error 53-0000515-08 Update software and hardware support March 2004 Message Reference v4.2.0 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...
Page 4 Title Publication Summary of changes Date number Fabric OS Message Reference 53-1001116-01 Updated for Fabric OS v6.1.1_enc: Aug 2008 -Revised and added new messages to AG -Added new chapters: CNM, CTAP, CVLC, CVLM, KAC, RKD, SPC, SPM -Added new Audit chapters: AG, FCIP, FICU, IPAD, PORT, SWCH, UCST -Updated Introductory chapters.
Page 5: Table Of Contents
Reading a RAS System Message ........
Page 6 Responding to a System Message........11 Looking Up a System Message .
Page 7 AG-1026............32 AG-1027 .
Page 8 AUTH-1016............42 AUTH-1017.
Page 9 ANV-1007............54 Chapter 6 BKSW System Messages BKSW-1003 .
Page 10 BL-1046 ............72 Chapter 8 BLL System Messages BLL-1000 .
Page 11 BM-1058 ............81 Chapter 11 C2 System Messages C2-1001 .
Page 12 Chapter 15 CHASSIS System Messages CHASSIS-1002........... . 95 CHASSIS-1003.
Page 13 CNM-1031 ............104 CNM-1032 .
Page 14 CNM-3006 ............113 CNM-3007 .
Page 15 CVLC-1011 ............126 CVLC-1012 .
Page 16 CVLM-1011 ........... . .135 CVLM-1012 .
Page 17 DOT1-1006 ........... . .146 DOT1-1007 .
Page 18 EM-1044 ............159 EM-1045 .
Page 19 ESW-1006 ............170 ESW-1007 .
Page 20 FABR-1035............184 FABR-1036.
Page 21 Chapter 30 FCIP System Messages FCIP-1000 ............199 FCIP-1001 .
Page 22 FCOE-1031............208 FCOE-1032 .
Page 23 FCR-1024............221 FCR-1025.
Page 24 FCR-1068............231 FCR-1069.
Page 25 FICN-1014 ............243 FICN-1015 .
Page 26 FICN-1051 ............253 FICN-1052 .
Page 27 Chapter 36 FICU System Messages FICU-1001 ............265 FICU-1002 .
Page 28 FSPF-1005............278 FSPF-1006.
Page 29 FW-1039 ............291 FW-1040 .
Page 30 FW-1136 ............303 FW-1137 .
Page 31 FW-1192 ............314 FW-1193 .
Page 32 FW-1332 ............325 FW-1333 .
Page 33 FW-1400 ............338 FW-1401 .
Page 34 FW-1512 ............348 FW-1513 .
Page 35 Chapter 43 HAM System Messages HAM-1001 ............361 HAM-1002 .
Page 36 HIL-1301 ............374 HIL-1302 .
Page 37 Chapter 47 HMON System Messages HMON-1001........... . .385 Chapter 48 HSL System Messages HSL-1000 .
Page 38 Chapter 53 IPAD System Messages IPAD-1000 ............401 IPAD-1001 .
Page 39 Chapter 58 KSWD System Messages KSWD-1001 ........... . .413 KSWD-1002.
Page 40 LOG-1003 ............426 Chapter 65 LSDB System Messages LSDB-1001 .
Page 41 Chapter 70 MSTP System Messages MSTP-1001 ........... . .441 MSTP-1002 .
Page 42 NSM-1009 ............453 NSM-1010 .
Page 43 PDM-1017 ............463 PDM-1019 .
Page 44 PORT-1009 ........... . . 474 PORT-1010.
Page 45 RCS-1002 ............487 RCS-1003 .
Page 46 Chapter 90 SEC System Messages SEC-1001............503 SEC-1002.
Page 47 SEC-1053............514 SEC-1054.
Page 48 SEC-1097............524 SEC-1098.
Page 49 SEC-1155............535 SEC-1156.
Page 50 SEC-1198............545 SEC-1199.
Page 51 SEC-1328............556 SEC-1329.
Page 52 SNMP-1005 ........... . .568 SNMP-1006 .
Page 53 Chapter 94 SPM System Messages SPM-1001 ............581 SPM-1002 .
Page 54 SPM-3022 ............590 SPM-3023 .
Page 55 SSMD-1211 ........... . .601 SSMD-1212 .
Page 56 SULB-1020 ........... . .616 SULB-1021 .
Page 57 SWCH-1019 ........... . .628 SWCH-1020 .
Page 58 Chapter 103 TRCK System Messages TRCK-1001 ........... . .639 TRCK-1002 .
Page 59 XTUN-1001 ........... . .649 XTUN-1002 .
Page 60 ZONE-1026 ........... . .662 ZONE-1027 .
Page 61: Cnm-3006
AG-1034............675 AG-1035.
Page 62: Cnm-3009
CNM-3009 ............687 CNM-3010 .
Page 63 CVLM-3024 ........... . .697 CVLM-3025 .
Page 64 SEC-3004 ............712 SEC-3005 .
Page 65 SEC-3045 ............723 SEC-3046 .
Page 66 SPM-3017 ............735 SPM-3018 .
Page 67 SULB-1040 ........... . .751 Chapter 129 AUDIT SWCH System Messages SWCH-1012 .
Page 68 ZONE-3022 ........... . .765 ZONE-3023 .
Page 69: About This Document
About This Document In this chapter • How this document is organized ....... . . lxix •...
Page 70: What's New In This Document
• Brocade 5000 • Brocade 5100 • Brocade 5300 • Brocade 5410 • Brocade 5424 • Brocade 5450 • Brocade 5460 • Brocade 5470 • Brocade 5480 • Brocade 7500 • Brocade 7500E • Brocade 7600 • Brocade 7800 • Brocade 8000 •...
Page 71: Document Conventions
“CNM System Messages” “AUDIT CNM System Messages” “CONF System Messages” “AUDIT CONF System Messages” “CVLC System Messages” “CVLM System Messages” “AUDIT CVLM System Messages” “FABR System Messages” “FICU System Messages” “AUDIT FICU System Messages” “FW System Messages” “HAM System Messages” “HIL System Messages”...
Page 72: Command Syntax Conventions
Text formatting The narrative-text formatting conventions that are used are as follows: bold text Identifies command names Identifies the names of user-manipulated GUI elements Identifies keywords and operands Identifies text to enter at the GUI or CLI italic text Provides emphasis Identifies variables Identifies paths and Internet addresses Identifies document titles...
Page 73: Notice To The Reader
CAUTION A Caution statement alerts you to situations that can be potentially hazardous to you or cause damage to hardware, firmware, software, or data. DANGER A Danger statement indicates conditions or situations that can be potentially lethal or extremely hazardous to you. Safety labels are also attached directly to products to warn of these conditions or situations.
Page 74: Getting Technical Help
For additional Brocade documentation, visit the Brocade website: http://www.brocade.com Release notes are available on the MyBrocade website and are also bundled with the Fabric OS firmware. Other industry resources For additional resource information, visit the Technical Committee T11 website. This website provides interface standards for high-performance and mass storage applications for Fibre Channel, storage management, and other applications: http://www.t11.org...
Page 75: Document Feedback
• Brocade 5000—On the switch ID pull-out tab located on the bottom of the port side of the switch • Brocade 7600—On the bottom of the chassis • Brocade 48000—Inside the chassis next to the power supply bays • Brocade DCX—On the bottom right on the port side of the chassis •...
Page 76 lxxvi Fabric OS Message Reference 53-1001767-01...
Page 77: In This Chapter
Reading a RAS System Message ........
Page 78: 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 79: System Logging Daemon (Syslogd)
Overview of System Messages defined set of Audit messages are sent to the configured remote host in the Audit message format, so that they are easily distinguishable from other syslog events that might occur in the network. For details on how to configure event auditing, see “Viewing and Configuring System Message Logs”...
Page 80: Viewing And Configuring System Message Logs
Viewing and Configuring System Message Logs Refer to the Fabric OS Administrator’s Guide for information on interpreting results of the portLogDump command. Port log functionality is completely separate from the system message log. Port logs are typically used to troubleshoot device connections. Viewing and Configuring System Message Logs This section provides information on viewing and configuring system message logs, including.
Page 81 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 82: 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 83: 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 84: 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 85 Reading a RAS System Message TABLE 3 System Message Field Description (Continued) Example Variable Name Description [EM-1031] Message Module The message module and number. These values uniquely identify and Message each message in the Fabric OS and reference the cause and Number actions recommended in this manual.
Page 86: Audit Event Messages
Reading a RAS System Message Audit Event Messages Compared to RASLog error messages, messages flagged as AUDIT provide additional user and system-related information of interest for post event auditing and problem determination. Audit event message format: AUDIT, <timestamp>, [<Event ID>], <Severity>, <Event Class>, <User ID>/<Role>/<IP address>/<Interface>/<app name>.
Page 87: Message Severity Levels
Responding to a System Message TABLE 4 Audit Message Field Description (Continued) Example Variable Name Description Switch name or chassis The defined switch name or the chassis name of the switchname name, depending on switch. This value is truncated if it is over 16 the action;...
Page 88: Looking Up A System Message
Is the problem repeatable? If so, what are the steps to produce the problem? What configuration was in place when the problem occurred? 8. Did a failover occur? 9. Was security enabled? 10. Was POST enabled? 11. Are serial port (console) logs available? 12.
Page 89: Support
System Module Descriptions Support Fabric OS creates a number of files that can help support personnel troubleshoot and diagnose a problem. This section describes those files and how to access and/or save the information for support personnel. Panic Dump and Core Dump Files The Fabric OS creates panic dump files and core files when there are problems in the Fabric OS kernel.
Page 90 System Module Descriptions Table 5 provides a summary of the system modules for which messages are documented in this reference guide; the system modules are listed alphabetically by name. TABLE 5 System Module Descriptions System Description Module Access Gateway allows multiple hosts (or HBAs) to access the fabric using fewer physical ports. Access Gateway mode transforms the Brocade switches as well as embedded switches into a device management tool that is compatible with different types of fabrics, including Brocade-, Cisco-, and McDATA-based fabrics.
Page 91 System Module Descriptions TABLE 5 System Module Descriptions (Continued) System Description Module The environmental monitor (EM) manages and monitors the various field replaceable units (FRUs), including the port cards, control processor (CP) blades, blower assemblies, power supplies, and world wide name (WWN) cards. EM controls the state of the FRUs during system startup, hot-plug sequences, and fault recovery.
Page 92 System Module Descriptions TABLE 5 System Module Descriptions (Continued) System Description Module The Fabric OS state synchronization framework provides facilities by which the active control processor (CP) can synchronize with the standby CP, enabling the standby CP to take control of the switch nondisruptively during failures and software upgrades.
Page 93 System Module Descriptions TABLE 5 System Module Descriptions (Continued) System Description Module KSWD The kernel software watchdog (KSWD) watches daemons for unexpected terminations and “hang” conditions and informs the HAM module to take corrective actions such as failover or reboot. The following daemons are monitored by KSWD: •...
Page 94 System Module Descriptions TABLE 5 System Module Descriptions (Continued) System Description Module MFIC MS-FICON messages relate to Fibre Connection (FICON) installations. Fibre Connection control unit port (FICON-CUP) messages are displayed under the FICU module. MPTH Multicast path uses the shortest path first (SPF) algorithm to dynamically compute a broadcast tree. Message queues are used for interprocess communication.
Page 95 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 96 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 97 Section RASLog Messages This section provides the RASLog messages, including: • AG System Messages ......... . . 25 •...
Page 98 • FICON System Messages ........239 •...
Page 99 • PDM System Messages......... 459 •...
Page 100 Fabric OS Message Reference 53-1001767-01...
Page 101: Ag System Messages
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 102 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 103 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 104 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 the supportFtp command (as needed) to set up automatic FTP transfers;...
Page 105 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 the supportFtp command (as needed) to set up automatic FTP transfers;...
Page 106 AG-1019 Recommended Run the switchShow command to display the status of all ports in the system. Run the portCfgShow Action command to display a list of ports currently configured as N_Ports. Ensure that the host is connected to an F_port. Severity ERROR AG-1019...
Page 107 AG-1022 AG-1022 Message <timestamp>, [AG-1022], <sequence-number>,, INFO, <system-name>, F_Port <fport> is failed over to its preferred N_Port <nport>. Probable Cause Indicates the specified F_Port is failing over to its preferred N_Port. Recommended Run the ag --mapshow command to display the updated F_Port-to-N_Port mapping. Action Severity INFO...
Page 108 AG-1026 AG-1026 Message <timestamp>, [AG-1026], <sequence-number>,, WARNING, <system-name>, Unable to handle the login request on port <port> due to insufficient resources. Probable Cause 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 the supportFtp (as needed) to set up automatic FTP transfers;...
Page 109 AG-1030 Severity WARNING AG-1030 Message <timestamp>, [AG-1030], <sequence-number>,, WARNING, <system-name>, N_Port ID: <port> has been determined to be unreliable. Probable Cause Indicates that the port goes online and offline very often. Recommended No action is required. Action Severity WARNING AG-1031 Message <timestamp>, [AG-1031], <sequence-number>,, WARNING, <system-name>, Loop Detected for device with Port WWN <port>...
Page 110 AG-1034 Severity INFO AG-1034 Message <timestamp>, [AG-1034], <sequence-number>,, INFO, <system-name>,F_Port cannot accept any more logins (<fport>) . Probable Cause Indicates that the F_Port has already logged in the maximum number of devices. Recommended No action is required. Action Severity INFO AG-1035 Message <timestamp>, [AG-1035], <sequence-number>,, INFO, <system-name>,Device cannot...
Page 111 AG-1038 Recommended If the switchshow command on the connected fabric switch port displays 'Persistently disabled: Action Area has been acquired', then check the cabling on the AG. All trunked ports in a single trunk should belong to the same ASIC Port Group. Severity INFO AG-1038...
Page 112 AG-1039 Fabric OS Message Reference 53-1001767-01...
Page 113: An System Messages
Chapter AN System Messages AN-1001 Message <timestamp>, [AN-1001], <sequence-number>,, ERROR, <system-name>, Failed to allocate memory: <function name> Probable Cause Indicates that the specified function has failed to allocate memory. Recommended Check memory usage on the switch using the memShow command. Restart or power cycle the Action switch.
Page 114 AN-1004 AN-1004 Message <timestamp>, [AN-1004], <sequence-number>,, WARNING, <system-name>, Slot <slot number>, port <port number within slot number> is a congestion bottleneck. <percentage of seconds affected by congestion bottlenecking> percent of last <observation period over which the percentage of affected seconds is reported> seconds were affected by this condition.
Page 115: Auth System Messages
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 116 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 117 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 118 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 119 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 120 AUTH-1022 If the message persists, run the supportFtp command (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 121 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 122 AUTH-1028 If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity ERROR AUTH-1028 Message <timestamp>, [AUTH-1028], <sequence-number>,, ERROR, <system-name>, Failed to allocate <data type> for <operation phase>: port <port number>. Probable Cause Indicates that the authentication process failed because the system is low on memory.
Page 123 AUTH-1031 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. If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers;...
Page 124 AUTH-1034 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. Severity ERROR AUTH-1034 Message <timestamp>, [AUTH-1034], <sequence-number>,, ERROR, <system-name>, Failed to validate name <entity name>...
Page 125 AUTH-1037 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>. Probable Cause Indicates that a Diffie Hellman - challenge handshake authentication protocol (DH-CHAP) authentication operation failed on the specified port due to mismatched response values between two entities.
Page 126 AUTH-1040 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. Probable Cause Indicates that the local switch has rejected the authentication because the switch policy is turned off.
Page 127 AUTH-1043 If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity ERROR AUTH-1043 Message <timestamp>, [AUTH-1043], <sequence-number>,, ERROR, <system-name>, Failed to enforce device authentication mode:<Device Auth Policy>(error: <Reason Code>). Probable Cause Indicates that the Kernel mode setting for F_Port authentication failed.
Page 128 AUTH-1046 AUTH-1046 Message <timestamp>, [AUTH-1046], <sequence-number>,, INFO, <system-name>, <Operation type> has been successfully completed. Probable Cause Indicates that the certificate database operation has been updated using the secAuthCertificate command. The values for Operation type can be "set" or "remove". Recommended No action is required.
Page 129: Anv System Messages
Chapter ANV System Messages ANV-1001 Message <timestamp>, [ANV-1001], <sequence-number>,, ERROR, <system-name>, Port <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, or a faulty cable between peer ports. Recommended Verify if you are using compatible SFPs on the peer ports.
Page 130 ANV-1004 ANV-1004 Message <timestamp>, [ANV-1004], <sequence-number>,, 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. Recommended Restart the system at the next maintenance window.
Page 131 ANV-1007 Severity CRITICAL Fabric OS Message Reference 53-1001767-01...
Page 132 ANV-1007 Fabric OS Message Reference 53-1001767-01...
Page 133: Bksw System Messages
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 regarding the state of the system. Refer to the string at the end of the error message for specific information.
Page 134 BKSW-1003 Fabric OS Message Reference 53-1001767-01...
Page 135: Bl System Messages
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 136 BL-1003 Severity CRITICAL BL-1003 Message <timestamp>, [BL-1003], <sequence-number>, FFDC, CRITICAL, <system-name>, Faulting blade in slot <slot number> Probable Cause Indicates a faulty blade in the specified slot number. Recommended Make sure that the blade is seated correctly. If the blade is seated correctly, restart or power cycle Action the blade.
Page 137 BL-1007 BL-1007 Message <timestamp>, [BL-1007], <sequence-number>,, WARNING, <system-name>, blade #<blade number>: blade state is inconsistent with EM. bl_cflags 0x<blade control flags>, slot_on <slot_on flag>, slot_off <slot_off flag>, faulty <faulty flag>, status <blade status>. Probable Cause Indicates that a failover occurred while a blade was initializing on the previously active control processor (CP).
Page 138 BL-1010 If the message persists, replace the blade. Severity CRITICAL BL-1010 Message <timestamp>, [BL-1010], <sequence-number>,, WARNING, <system-name>, Blade in slot <slot number> inconsistent with the hardware settings. Probable Cause Indicates that a failover occurred while some hardware changes were being made on the previously active control processor (CP) (such as changing the domain ID).
Page 139 BL-1013 Probable Cause Indicates that the port generated an excessive number of interrupts that might prove unrecoverable to the switch operation. The port is disabled to prevent the control processor (CP) from becoming too busy. The bport is the blade port; this number might not correspond to a user port number.
Page 140 BL-1015 Run the diagPost command to ensure that Power-On Self-Test (POST) is enabled. If there is a hardware error, if the slotPowerOff or slotPowerOn fails on the bladed switch or if errors are encountered again: • On the Brocade 24000, and 48000, replace the blade field-replaceable unit (FRU). •...
Page 141 BL-1017 Run the systemVerification command to verify that the blade does not have hardware problems. To run this command root access is required. 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 142 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 Restart or power cycle the switch. Action Run the systemVerification command to verify that the switch does not have hardware problems. To run this command root access is required.
Page 143 BL-1023 Severity CRITICAL 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 Restart or power cycle the blade.
Page 144 BL-1027 Probable Cause Indicates that an internal port went offline during the warm recovery of the switch. The switch will reboot and start a cold recovery. Recommended Collect supportSave information, then restart the switch and run the diagPost command to ensure Action Power-On Self-Test (POST) is enabled.
Page 145 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 146 BL-1034 Probable Cause Indicates that the system has timed out while waiting for disable messages from the user ports after disabling the ports. Recommended Restart or power cycle the blade. Run the systemVerification command to verify that the blade does Action not have hardware problems.
Page 147 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 Indicates a fault on the chip and that all ports on the chip have been disabled. Recommended No action is required.
Page 148 BL-1045 BL-1045 Message <timestamp>, [BL-1045], <sequence-number>,, ERROR, <system-name>, mini SFP+ (SN: <mini SFP+ serial number>) is only supported in certain high port count blades, not blade in slot <slot number of blade that has the mini SFP+> w/ ID <Blade ID of blade that has the mini SFP+ that does not support it>.
Page 149: Bll System Messages
• 6 = Excessive RCC VC on E_Port • 7 = Excessive RCC VC on FL_Port • 8 = Fail detection buffer tag error • 9 = Fail detection TX parity error • 10 = EPI CMEM interrupt error •...
Page 150 BLL-1000 Severity CRITICAL Fabric OS Message Reference 53-1001767-01...
Page 151: Bls System Messages
Chapter BLS System Messages BLS-1000 Message <timestamp>, [BLS-1000], <sequence-number>,, 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 152 BLS-1004 Probable Cause Indicates that an IPsec or IKE policy was deleted and the configuration file was updated. Recommended No action is required. Action Severity INFO BLS-1004 Message <timestamp>, [BLS-1004], <sequence-number>,, INFO, <system-name>, Tape Read Pipelining is being disabled slot <slot number> port <user port index> tunnel <The configured tunnel ID (0-7)>.
Page 153: Bm System Messages
Chapter BM System Messages BM-1001 Message <timestamp>, [BM-1001], <sequence-number>,, ERROR, <system-name>, BM protocol version <Protocol version> in slot <Slot number>. Probable Cause Indicates that the 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 154 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 155 BM-1007 BM-1007 Message <timestamp>, [BM-1007], <sequence-number>,, INFO, <system-name>, If set, clear EX/VEX/FC Fastwrite configuration for all ports for blade in slot <Slot number> Probable Cause Indicates the specified blade was detected for the first time after an FR4-18i was previously configured in the same slot.
Page 156 BM-1053 Severity INFO BM-1053 Message <timestamp>, [BM-1053], <sequence-number>,, WARNING, <system-name>, Failed to establish connection between CP and Application Processor. Faulting switch. Probable Cause Indicates the control processor (CP) could not establish a connection with the application processor to communicate. Recommended On the Brocade 7500 or 7600, switch off and switch on all the primary power to power-cycle the Action unit.
Page 157 BM-1058 Probable Cause Indicates the policy of the specified switch is to persistently disable all ports the first time the AP is detected. This may be caused by one of the following: • The AP was detected for the first time on this switch. •...
Page 158 BM-1058 Fabric OS Message Reference 53-1001767-01...
Page 159: C2 System Messages
Chapter C2 System Messages C2-1001 Message <timestamp>, [C2-1001], <sequence-number>,, ERROR, <system-name>, Port <port number> port faulted due to SFP validation failure. Please check if the SFP is valid for the configuration. 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 160 C2-1006 C2-1006 Message Message <timestamp>, [C2-1006], <sequence-number>,, WARNING, <system-name>, <slot number>,<chip index>: Internal link errors reported, no hardware faults identified, continuing monitoring: fault1:<fault1_cnt>, fault2:<fault2_cnt> thresh1:0x<threshold_used>. Probable Cause Indicates a warning that some internal link errors have been detected. These can be normal in an active running system.
Page 161 C2-1009 C2-1009 Message Message <timestamp>, [C2-1009], <sequence-number>,, WARNING, <system-name>, <slot number>, <port number><blade port number>: portcfglongdistance vc_translation_link_init = 1 overwrites fill word IDLE. ARB will be used on the link. Probable Cause Indicates portcfglongdistance vc_translation_link_init 1 overwrites fill word IDLE. ARB will be used on the link.
Page 162 C2-1011 Fabric OS Message Reference 53-1001767-01...
Page 163: Cdr System Messages
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 that the port speed configuration does not match the capability of the SFP. Recommended Ensure that you are using compatible SFPs on the peer ports.
Page 164 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 165: Cee Config System Messages
Chapter CEE CONFIG System Messages CCFG-1001 Message <timestamp>, [CCFG-1001], <sequence-number>,, ERROR, <system-name>, Failed to initialize <module>, rc = <error>. Probable Cause Indicates that initialization of a module within the Converged Enhanced Ethernet (CEE) configuration management daemon has failed. Recommended Download a new firmware version using the firmwareDownload command. Refer to the Fabric OS Action Command Reference Manual for more information on this command.
Page 166 CCFG-1005 Probable Cause Indicates that the startup configuration has been moved or deleted, hence replaying the system configuration has failed. Recommended Use the copy file startup-config command to restore the startup configuration from any backup Action retrieved on the server. Severity ERROR CCFG-1005...
Page 167 CCFG-1009 Probable Cause Indicates that the CMSH initialization has failed. Recommended No action is required. Action Severity ERROR CCFG-1009 Message <timestamp>, [CCFG-1009], <sequence-number>,, INFO, <system-name>, Successfully copied to <destination>. Probable Cause Indicates that the file has been successfully copied to the destination. Recommended No action is required.
Page 168 CCFG-1012 Probable Cause Indicates that the mentioned slot has failed to reach the Online state within the specified time after system ready event. Recommended Run the slotpoweroff command followed by the slotpoweron command on the slot to retry bringing Action the slot online.
Page 169: Cer System Messages
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 170 CER-1001 Fabric OS Message Reference 53-1001767-01...
Page 171: Chassis System Messages
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, execute the slotPowerOff command and slotPowerOn commands on the Action blade to recover the system. For a non-bladed system, execute the fastBoot command on the switch to recover the system.
Page 172 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 173: Cnm System Messages
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. Restart or power cycle the Action switch.
Page 174 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 (EG) leader is elected. Recommended No action is required.
Page 175 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 176 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 177 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 178 CNM-1021 Probable Cause Indicates that the Node Admission Control has 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 that the Node Admission Control has failed. Recommended No action is required.
Page 179 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 on a member node.
Page 180 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>,, WARNING, <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 181 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 WARNING CNM-1033 Message <timestamp>, [CNM-1033], <sequence-number>,, WARNING, <system-name>, Some of the defined nodes in the Encryption Group are not ONLINE.
Page 182 CNM-1037 Probable Cause Indicates an event is being posted to indicate that 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 183 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 184 CNM-1045 Recommended No action is required. Action Severity ERROR CNM-1045 Message <timestamp>, [CNM-1045], <sequence-number>,, ERROR, <system-name>, Member node <wwn> is having dual IP stack.Registering member node with dual IP in an EG with only IPV6 is not allowed. Probable Cause Indicates that the member node with a dual IP stack was registered with an IPV6 encryption group (EG).
Page 185 CNM-1049 Recommended No action is required. Action Severity INFO CNM-1049 Message <timestamp>, [CNM-1049], <sequence-number>,, ERROR, <system-name>, Failed to define node, Node Name <string>. Probable Cause Indicates the system failed to define the node object. Recommended No action is required. Action Severity ERROR CNM-1050...
Page 186 CNM-1053 Recommended No action is required. Action Severity ERROR CNM-1053 Message <timestamp>, [CNM-1053], <sequence-number>,, ERROR, <system-name>, Node is already a registered member of another EG. First eject the current node <nodename> from the existing EG and then try. Probable Cause Indicates that the node is already a registered member of another encryption group (EG).
Page 187 CNM-1057 Recommended No action is required. Action Severity INFO CNM-1057 Message <timestamp>, [CNM-1057], <sequence-number>,, INFO, <system-name>, Posting event CNM_EVT_ONLINE Slot <slot>, Wwn <wwn>, IP <ip>, flags <flags>. Probable Cause Indicates that the encryption engine (EE) is online in the encryption group (EG). Recommended No action is required.
Page 188 CNM-1061 Recommended No action is required. Action Severity INFO CNM-1061 Message <timestamp>, [CNM-1061], <sequence-number>,, INFO, <system-name>, IP of the switch changed from [<my_ip>] to [<new_ip>]. Probable Cause Indicates that the switch IP has changed. Recommended No action is required. Action Severity INFO CNM-1062...
Page 189 CNM-3003 Recommended No action is required. Action Severity INFO CNM-3003 Message <timestamp>, [CNM-3003],<sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: Membernode \<membernodeWWN>\ added to encryption group. Probable Cause Indicates a member node was added to an encryption group. Recommended No action is required. Action Severity INFO...
Page 190 CNM-3007 Recommended No action is required. Action Severity INFO CNM-3007 Message <timestamp>, [CNM-3007],<sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: Heartbeat timeout set to <hbtimeout>. Probable Cause Indicates that the heartbeat timeout value was set. Recommended No action is required. Action Severity INFO...
Page 191 CNM-3011 Recommended No action is required. Action Severity INFO CNM-3011 Message <timestamp>, [CNM-3011], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: Encryption group synchronized. Probable Cause Indicates an encryption group was synchronized. Recommended No action is required. Action Severity INFO CNM-3012 Message <timestamp>, [CNM-3012], <sequence-number>,, INFO, <system-name>, Deleteing an EG...
Page 192 CNM-3012 Fabric OS Message Reference 53-1001767-01...
Page 193: Conf System Messages
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 194 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 the configupload command. Action Severity INFO...
Page 195 CONF-1030 CONF-1030 Message <timestamp>, [CONF-1030], <sequence-number>,, WARNING, <system-name>, Configuration database full, data not committed (key:<Key of failed configuration data>. Probable Cause Indicates that the previous configuration commands have resulted in a database full condition. Configuration changes associated with the specified key have not been applied. Recommended Use the configure command and various other commands to erase configuration parameters that Action...
Page 196 CONF-1041 CONF-1041 Message <timestamp>, [CONF-1041], <sequence-number>,, INFO, <system-name>, configRemove failed. Probable Cause Indicates a configRemove error has occurred. Recommended Correct the error and try again. Action Severity INFO CONF-1042 Message <timestamp>, [CONF-1042], <sequence-number>,, INFO, <system-name>, Fabric Configuration Parameter <parameter> changed to <value>. Probable Cause Indicates that the parameter value has been changed.
Page 197: Ctap System Messages
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 198 CTAP-1001 Fabric OS Message Reference 53-1001767-01...
Page 199: Cvlc System Messages
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 200 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 201 CVLC-1008 Recommended If you want to preserve the user data, use cryptocfg --modLUNpolicy -cleartext to convert to clear Action text LUN. Use cryptocfg ---modLUNpolicy -disable_allowdecrypt to disable decryption of existing data. Then try the LUN deletion again. Severity ERROR CVLC-1008 Message <timestamp>, [CVLC-1008], <sequence-number>,, ERROR, <system-name>, LUN discovery failure: <Discovery state>, Container: <Target container name>, Initiator:...
Page 202 CVLC-1011 CVLC-1011 Message <timestamp>, [CVLC-1011], <sequence-number>,, ERROR, <system-name>, Third party license is required for encryption LUN in third party mode.\nContainer: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Probable Cause Indicates that the encryption LUN is configured with non-Brocade mode but there is no valid license.
Page 203 CVLC-1015 Recommended Use cryptocfg command to add the key ID, if available. Action Severity ERROR CVLC-1015 Message <timestamp>, [CVLC-1015], <sequence-number>,, ERROR, <system-name>, LUN is set to read only mode. Reason: <Reason for LUN is set to read only mode>.\nContainer: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Probable Cause Indicates that the LUN is set as read-only because there is a conflict in the configuration.
Page 204 CVLC-1019 Probable Cause Indicates an informational event. Recommended No action is required. Action Severity INFO CVLC-1019 Message <timestamp>, [CVLC-1019], <sequence-number>,, ERROR, <system-name>, Metadata exists while data state is clear text.\nContainer: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Probable Cause Indicates that the data state in the LUN configuration is in clear text state but metadata exists on the LUN.
Page 205 CVLC-1022 CVLC-1022 Message <timestamp>, [CVLC-1022], <sequence-number>,, INFO, <system-name>, User provided key ID <Key ID from metadata> is ignored while data state is clear text.\nContainer: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Probable Cause Indicates that the key ID provided is ignored because the data state is clear text. Recommended No action is required.
Page 206 CVLC-1026 Severity ERROR CVLC-1026 Message <timestamp>, [CVLC-1026], <sequence-number>,, INFO, <system-name>, Some secondary metadata missing for encrypted LUN configured with -newLUN option.\nContainer: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Probable Cause Indicates that the secondary metadata does not exist on all LBAs for a LUN that is configured with --newLUN option.
Page 207 CVLC-1030 Recommended Break the mirror and re-establish the mirror after rekey on primary LUN is complete. Action Severity WARNING CVLC-1030 Message <timestamp>, [CVLC-1030], <sequence-number>,, WARNING, <system-name>, Primary LUN may be out of sync with mirror LUN.\nContainer: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Probable Cause Indicates the manual rekey was completed on primary LUN.
Page 208 CVLC-1033 CVLC-1033 Message <timestamp>, [CVLC-1033], <sequence-number>,, INFO, <system-name>, Rebalance completed for EE: <EE name>\nDevice login in progress. Probable Cause Indicates a rebalance operation was performed. Recommended No action is required. Action Severity INFO CVLC-1034 Message <timestamp>, [CVLC-1034], <sequence-number>,, INFO, <system-name>, Rekey failed on Container: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>...
Page 209: Cvlm System Messages
Chapter CVLM System 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 has failed to allocate memory. Recommended Check the memory usage on the switch using the memShow command. Restart or power cycle the Action switch.
Page 210 CVLM-1005 Probable Cause Indicates that EE 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 211 CVLM-1009 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 found in the fabric. Recommended No action is required.
Page 212 CVLM-3001 Recommended No action is required. Action Severity INFO CVLM-3001 Message <timestamp>, [CVLM-3001], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: Failback mode set to <failbackmode>. Probable Cause Indicates the failback mode was set. Recommended No action is required. Action Severity INFO CVLM-3002...
Page 213 CVLM-3005 Recommended No action is required. Action Severity INFO CVLM-3005 Message <timestamp>, [CVLM-3005], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: Cluster member removed from HA cluster <HAClusterName>. Probable Cause Indicates an HA cluster member was removed from an HA cluster. Recommended No action is required.
Page 214 CVLM-3009 Recommended No action is required. Action Severity INFO CVLM-3009 Message <timestamp>, [CVLM-3009], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: Manual failback from EE <currentnodeWWN>/<currentSlot> to EE <newnodeWWN>/<newnodeSlot>. Probable Cause Indicates a manual failback was performed to an encryption engine. Recommended No action is required.
Page 215 CVLM-3013 Probable Cause Indicates an initiator was removed from a cryptotarget container. Recommended No action is required. Action Severity INFO CVLM-3013 Message <timestamp>, [CVLM-3013], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: LUN <LUNSpec>, attached through Initiator \<Initiator>\, added to crypto target container \<cryptoTargetContainer>\. Probable Cause Indicates a LUN was added to a cryptotarget container.
Page 216 CVLM-3016 CVLM-3016 Message <timestamp>, [CVLM-3016], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: Lun <LUNNumber>, attached through Initiator \<Initiator>\, in crypto target container \<cryptoTargetContainer>\ enabled. Probable Cause Indicates a LUN in a cryptotarget container was enabled. Recommended No action is required. Action Severity INFO...
Page 217 CVLM-3020 CVLM-3020 Message <timestamp>, [CVLM-3020], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: Manual rekey of LUN <LUNSpec> attached through Initiator \<Initiator>\ in crypto tgt container \<cryptoTargetContainer>\. Probable Cause Indicates a manual rekey of a LUN was performed. Recommended No action is required. Action Severity INFO...
Page 218 CVLM-3024 CVLM-3024 Message <timestamp>, [CVLM-3024], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: Transaction <transactionID> aborted. Probable Cause Indicates a transaction abort operation was performed. Recommended No action is required. Action Severity INFO CVLM-3025 Message <timestamp>, [CVLM-3025], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: started, Info: Decommission of device (container <cryptoTargetContainer>...
Page 219 CVLM-3028 CVLM-3028 Message <timestamp>, [CVLM-3028], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: SRDF mode set to <srdfmode>. Probable Cause Indicates that the SRDF mode was set. Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1001767-01...
Page 220 CVLM-3028 Fabric OS Message Reference 53-1001767-01...
Page 221: Dauth System Messages
Chapter DAUTH System Messages DOT1-1001 Message <timestamp>, [DOT1-1001], <sequence-number>,, INFO, 802.1X is enabled globally. Probable Cause Indicates that the 802.1X is enabled globally. Recommended No action is required. Action Severity INFO DOT1-1002 Message <timestamp>, [DOT1-1002], <sequence-number>,, INFO, 802.1X is disabled globally. Probable Cause Indicates that the 802.1X is disabled globally.
Page 222 DOT1-1005 Recommended No action is required. Action Severity INFO DOT1-1005 Message <timestamp>, [DOT1-1005], <sequence-number>,, INFO, 802.1X Authentication is successful on port <port_name>. Probable Cause Indicates that the authentication has succeeded on a particular port. Recommended No action is required. Action Severity INFO DOT1-1006...
Page 223 DOT1-1009 Recommended No action is required. Action Severity INFO DOT1-1009 Message <timestamp>, [DOT1-1009], <sequence-number>,, INFO, 802.1X is disabled for port <port_name>. Probable Cause Indicates that the 802.1X is disabled for a particular port. Recommended No action is required. Action Severity INFO DOT1-1010 Message...
Page 224 DOT1-1010 Fabric OS Message Reference 53-1001767-01...
Page 225: Em System Messages
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 226 EM-1004 Run the systemVerification command to verify that the switch does not have hardware problems. To run this command root access is required. 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.
Page 227 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 228 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 229 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 230 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 231 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 232 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 233 EM-1035 EM-1035 Message <timestamp>, [EM-1035], <sequence-number>,, ERROR, <system-name>, 2 circuit <Switch side> paired Power Supplies are faulty, please check the AC main switch/circuit to see if it has power. Fabric OS Message Reference 53-1001767-01...
Page 234 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 235 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 236 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 237 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 238 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 239 EM-1060 Recommended Replace the blade. Make sure the replacement is compatible with your switch type. Action Severity ERROR EM-1060 Message <timestamp>, [EM-1060], <sequence-number>,, WARNING, <system-name>, Stopping synchronization of the system due to blade incompatibility with software version on standby CP. Probable Cause Indicates a blade in the system is not supported by the release on the standby control processor (CP).
Page 240 EM-1063 EM-1063 Message <timestamp>, [EM-1063], <sequence-number>,, CRITICAL, <system-name>, Blade in slot <Slot Id> faulted because it exceeds the maximum support limit of <Limit> blades with Blade IDs <Applicable blade Type IDs> in the chassis. Probable Cause Indicates too many blades of a set of particular types are in the system. Recommended Remove the faulted blade.
Page 241 EM-1067 Probable Cause Indicates the previously incompatible Fabric OS or Storage Application Services (SAS) firmware has been upgraded and is now compatible. Recommended No action is required. Action Severity INFO EM-1067 Message <timestamp>, [EM-1067], <sequence-number>,, WARNING, <system-name>, Stopping synchronization of the system due to version incompatibility with standby CP. Probable Cause Indicates that the software version on the standby CP is not compatible with this software version.
Page 242 EM-1070 EM-1070 Message <timestamp>, [EM-1070], <sequence-number>,, INFO, <system-name>, Slot <FRU slot number> is being powered on. Probable Cause Indicates a blade is being intentionally powered on. Recommended No action is required. Action Severity INFO EM-2003 Message <timestamp>, [EM-2003], <sequence-number>,, ERROR, <system-name>, <Slot Id or Switch for pizza boxes>...
Page 243: Ess System Messages
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 244 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 245: Eswch System Messages
Chapter ESWCH System Messages ESW-1001 Message <timestamp>, [ESW-1001], <sequence-number>,, ERROR, <system-name>, Switch is not in ready state - Switch enable failed switch status= 0x<switch status>, c_flags = 0x<switch control flags>. Probable Cause Indicates that the switch enable has failed. Recommended If the message persists, run the supportFtp command (as needed) to set up automatic FTP Action transfers;...
Page 246 ESW-1004 ESW-1004 Message <timestamp>, [ESW-1004], <sequence-number>,, ERROR, <system-name>,Blade attach failed during recovery, disabling slot = <slot number>. Probable Cause Indicates that the blade has failed during failover or recovery. Recommended On a Brocade 8000 switch, restart or power cycle the switch. Action Severity ERROR...
Page 247 ESW-1008 Severity WARNING ESW-1008 Message <timestamp>, [ESW-1008], <sequence-number>,, WARNING, <system-name>,<area string> are port swapped on ports that do not support port swap. Slot <slot number> will be faulted. Probable Cause Indicates that the blade has area swapped ports on ports that do not support this feature. Recommended Replace the blade with ports that support port swap.
Page 248 ESW-1008 Fabric OS Message Reference 53-1001767-01...
Page 249: Evmd System Messages
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 250 EVMD-1001 Fabric OS Message Reference 53-1001767-01...
Page 251: Fabr System Messages
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 252 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 253 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 254 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 255 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 256 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 257 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 258 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 259 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 260 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 261 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 262 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 a link reset was received before the completion of the trunking protocol on the port. Recommended Enable the port by running the portEnable command.
Page 263 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 264 FABR-1049 FABR-1049 Message <timestamp>, [FABR-1049], <sequence-number>, ERROR, <system-name>, Detected Fabric ID (FID <InheritedFID> inherited) conflict with neighbor switch <Switchname> (domain <Domain ID>, FID <Fabric ID>). E-ports (<Number of E-ports disabled>) connected to the switch are disabled. Probable Cause Indicates that the neighbor switch has Fabric ID conflict with the inherited FID of the local switch. All E_ports directly connected to the conflicting switch are disabled.
Page 265: Fabs System Messages
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 266 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 267 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 268 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 269 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 270 FABS-1015 Fabric OS Message Reference 53-1001767-01...
Page 271: Fbc System Messages
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 272 FBC-1001 Fabric OS Message Reference 53-1001767-01...
Page 273: Fcmc System Messages
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 274 FCMC-1001 Fabric OS Message Reference 53-1001767-01...
Page 275: Fcip System Messages
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 276 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 277: Fcoe System Messages
Chapter FCOE System Messages FCOE-1001 Message <timestamp>, [FCOE-1001], <sequence-number>,, ERROR, <system-name>, calloc failed for <object>. Probable Cause Indicates a memory failure. Recommended Check the switch memory status. Action Severity ERROR FCOE-1002 Message <timestamp>, [FCOE-1002], <sequence-number>,, WARNING, <system-name>, Max login Group limit reached at <limit>. Probable Cause Indicates too many login groups (LGs) have been added.
Page 278 FCOE-1005 Recommended Remove the failed member from the login group. Action Severity ERROR FCOE-1005 Message <timestamp>, [FCOE-1005], <sequence-number>,, ERROR, <system-name>, <device>: membership check failed in lg: <lg> Probable Cause Indicates that the Membership check for the device has failed. Recommended Check the device for failed Membership.
Page 279 FCOE-1009 Recommended No action is required. Action Severity INFO FCOE-1009 Message <timestamp>, [FCOE-1009], <sequence-number>,, INFO, <system-name>, Addition of nport mapping failed. Max nport mapping limit reached: <maxnport>. Probable Cause Indicates that the N_port mapping has reached its maximum limit. Recommended Remove unwanted N_port mappings and try adding N_port mapping.
Page 280 FCOE-1013 Recommended Rerequest to delete port from VLAN. Action Severity ERROR FCOE-1013 Message <timestamp>, [FCOE-1013], <sequence-number>,, ERROR, <system-name>, Request to add VLAN <vid> failed. Probable Cause Indicates an add request to a VLAN has failed. Recommended Rerequest to add VLAN. Action Severity ERROR...
Page 281 FCOE-1017 Recommended The VLAN may be in use; disable the active FCoE login session and try deleting the VLAN again. Action Severity ERROR FCOE-1017 Message <timestamp>, [FCOE-1017], <sequence-number>,, ERROR, <system-name>, Request to add fcmap failed for vlan <vid>. Probable Cause Indicates an add request to VLAN has failed.
Page 282 FCOE-1022 Recommended No action is required. Action Severity INFO FCOE-1022 Message <timestamp>, [FCOE-1022], <sequence-number>,, WARNING, <system-name>, Max FCoE device login limit reached. Probable Cause Indicates that the switch has reached its maximum allowed FCoE device limit. Recommended Do not add any more FCoE devices to the switch. Action Severity WARNING...
Page 283 FCOE-1026 Recommended It is due to a CNA/target driver issue. No action is required. Action Severity WARNING FCOE-1026 Message <timestamp>, [FCOE-1026], <sequence-number>,, WARNING, <system-name>, FDISC/FLOGI mismatch. FDISC addressed to different FCF than base FLOGI. Probable Cause Indicates the base port has sent an FLOGI but the subsequent FDISC's that was received on the switch does not match the original FLOGI.
Page 284 FCOE-1030 Probable Cause Indicates a version mismatch between the FLOGI and the FDISCs. Recommended No action is required. Action Severity WARNING FCOE-1030 Message <timestamp>, [FCOE-1030], <sequence-number>,, WARNING, <system-name>, Version mismatch between FIP LOGO and root VN port. Probable Cause Indicates a version mismatch between the FIP logout and base FLOGI. Recommended No action is required.
Page 285 FCOE-1034 Recommended No action is required. Action Severity WARNING FCOE-1034 Message <timestamp>, [FCOE-1034], <sequence-number>,, WARNING, <system-name>, Discarded frame received on priority <pkt_ctrlp->pri_in> for which PFC / FCoE is disabled. Probable Cause Indicates the priority PFC/FCoE is not enabled. Recommended Configure as required. Action Severity WARNING...
Page 286 FCOE-1036 Fabric OS Message Reference 53-1001767-01...
Page 287: Fcpd System Messages
Chapter FCPD System Messages FCPD-1001 Message <timestamp>, [FCPD-1001], <sequence-number>,, WARNING, <system-name>, Probing failed on <error string> Probable Cause Indicates that a Fibre Channel Protocol (FCP) switch probed devices on a loop port, and probing failed on the L_Port, AL_PA address, or the F_Port. For the AL_PA, the valid range is 00 through FF. The error string can be either of the following: •...
Page 288 FCPD-1003 Fabric OS Message Reference 53-1001767-01...
Page 289: Fcph System Messages
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 290 FCPH-1002 Fabric OS Message Reference 53-1001767-01...
Page 291: Fcr System Messages
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 at the port in the edge fabric has been imported at the specified port. Recommended No action is required.
Page 292 FCR-1005 Recommended Verify that the devices were intended to be taken offline. If not, verify that the devices are Action 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. Severity INFO FCR-1005...
Page 293 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 294 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 295 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 296 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, and verify that this error is not reported again. Severity WARNING FCR-1021 Message <timestamp>, [FCR-1021], <sequence-number>,, WARNING, <system-name>, Local LSAN...
Page 297 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 298 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 299 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 300 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 301 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&apos zone database limitations.
Page 302 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 303 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 304 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 305 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 306 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 307 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 308 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 309 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 an earlier version of the switch in the backbone or edge that supports a different limit of logical storage area network (LSAN) zones was detected.
Page 310 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 311 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 Indicates that during the Coordinated HotCode protocol, a switch in the fabric has not responded to the pause message which prevented the protocol from completing.
Page 312 FCR-1083 FCR-1083 Message <timestamp>, [FCR-1083], <sequence-number>,, WARNING, <system-name>, The resume message is rejected by the domain <Domain>. Probable Cause Indicates that 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 313 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 314 FCR-1092 Recommended No action is required. Action Severity INFO FCR-1092 Message <timestamp>, [FCR-1089], <sequence-number>,, ERROR, <system-name>, FCR ELS trap entries exhausted. Probable Cause Indicates that the FCR ELS trap entries are exhausted. Recommended Collect supportsave data and send it to support. Action Severity ERROR...
Page 315: Ficon System Messages
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.
Page 316 FICN-1004 Severity WARNING FICN-1004 Message <timestamp>, [FICN-1004], <sequence-number>,, WARNING, <system-name>, FICON XRC Emulation License Key is not installed. Probable Cause Indicates FICON XRC Emulation requires a License Key. Recommended Use the appropriate License Key. Action Severity WARNING FICN-1005 Message <timestamp>, [FICN-1005], <sequence-number>,, INFO, <system-name>, FICON GEPort <GE port number>...
Page 317 LastCmds=<the Last 4 commands issued to the device> Sense Data:Bytes0-0xB=<bytes 0-3 of sense data from the device> <bytes 4-7 of sense data from the device> <bytes 8-0x0b of sense data from the device>. Probable Cause Indicates a Unit Check status was received from a device and a sense command was issued to read the sense data.
Page 318 FICN-1011 Probable Cause Indicates a Device Level Exception frame was received from the FICON Channel. Recommended If there was a job or IO failure associated with this event, please contact your vendor's customer Action support for assistance. Severity INFO FICN-1011 Message <timestamp>, [FICN-1011], <sequence-number>,, ERROR, <system-name>, DevDiskIng:XRC Incorrect RRS SeqNum Rcvd Path=0x<VEPortNumber HostDomain HostPort...
Page 319 FICN-1014 Severity INFO FICN-1014 Message <timestamp>, [FICN-1014], <sequence-number>,, INFO, <system-name>, DevEgr:Device level exception flag found for Path=0x<VEPortNumber HostDomain HostPort DeviceDomain>8X<DevicePort LPAR CUADDR DeviceAddr>8X: Oxid=0x<The OXID used to deliver the non-AS Device Level Exception>4X. Probable Cause Indicates a frame was received that indicated device level exception. Recommended If there was an IO failure associated with this event, please contact your vendor's customer support Action...
Page 320 FICN-1018 Probable Cause Indicates the FICON Control Unit sent an LPE frame to the FICON channel. Recommended This is an informational message and does not require any action. Action Severity INFO FICN-1018 Message <timestamp>, [FICN-1018], <sequence-number>,, ERROR, <system-name>, DevIng:FCUB Lookup failed for Path=0x<VEPortNumber HostDomain HostPort DeviceDomain>8x<DevicePort LPAR>2x.
Page 321 FICN-1021 FICN-1021 Message <timestamp>, [FICN-1021], <sequence-number>,, ERROR, <system-name>, DevTapeEgr:FICON Tape Cancel:Path=0x<VEPortNumber HostDomain HostPort DeviceDomain>8X<DevicePort LPAR CUADDR DeviceAddr>8X Elapsed Time=<the current SIO time in seconds for the device>.<the current SIO time in milliseconds for the device> seconds. Probable Cause Indicates the FICON channel issued a Cancel sequence for a device in emulation. Recommended If there was an unexpected job failure associated with this event, contact your vendor's customer Action...
Page 322 DeviceDomain>8X<DevicePort LPAR CUADDR DeviceAddr>8X Bytes0-0xB=0x<bytes 0-3 of sense data from the device>8X<bytes 4-7 of sense data from the device>8X<bytes 8-0x0b of sense data from the device>8X. Probable Cause Indicates the FICON tape write pipelining processed sense data from a FICON device.
Page 323 FICN-1028 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-1028 Message <timestamp>, [FICN-1028], <sequence-number>,, ERROR, <system-name>, HostDiskIng:FICON Cancel received Path=<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR CUADDR DeviceAddr>state=0x<The current emulation state of the device>.
Page 324 FICN-1031 FICN-1031 Message <timestamp>, [FICN-1031], <sequence-number>,, WARNING, <system-name>, HostDiskIng:FICON System Reset received on Path=<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR><CUADDR>. Probable Cause Indicates the FICON channel sent a System Reset to the disk control unit. Recommended No action is required. The MVS system was either set to IPL or performing error recovery. Action Severity WARNING...
Page 325 FICN-1035 Probable Cause Indicates the channel emulation processing received a frame with an invalid FICON LRC from the peer. This indicates that the channel side noted corruption from the device/CU side processing. Recommended Contact your vendor's customer support for assistance. Action Severity ERROR...
Page 326 SenseData:Bytes0-0xB=0x<Bytes 0-3 of sense data from the device> <Bytes 4-7 of sense data from the device> <Bytes 8-0x0b of sense data from the device>. Probable Cause Indicates an active disk emulation device received a FICON Purge Path from the channel.
Page 327 FICN-1042 Probable Cause Indicates an LRJ received from a device indicates that the CU has lost the logical path to the LPAR. Recommended If this was an unexpected event, contact your vendor's customer support for assistance. Action Severity ERROR FICN-1042 Message <timestamp>, [FICN-1042], <sequence-number>,, WARNING, <system-name>, HostTapeIng:FICON Cancel received Path=<VEPortNumber HostDomain HostPort...
Page 328 FICN-1045 FICN-1045 Message <timestamp>, [FICN-1045], <sequence-number>,, WARNING, <system-name>, HostTapeIng:FICON Purge received:Path=<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR CUADDR DeviceAddr>. Probable Cause Indicates a purge path was received from the locally connected FICON channel. This is performed during the path recovery. Recommended If this was an unexpected event, contact your vendor's customer support for assistance.
Page 329 FICN-1049 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 FICN-1049 Message <timestamp>, [FICN-1049], <sequence-number>,, WARNING, <system-name>, ProcessIngTirData:Lost Logical Path for Path=<VEPortNumber HostDomain HostPort DeviceDomain>...
Page 330 FICN-1052 Severity INFO FICN-1052 Message <timestamp>, [FICN-1052], <sequence-number>,, INFO, <system-name>, XRC Session Terminated: SessID=<SDM Assigned Session ID>, Path=<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR CUADDR DeviceAddr>. Probable Cause Indicates a PSF command has been received to break an XRC session with the extended DASD device.
Page 331 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 332 FICN-1059 FICN-1059 Message <timestamp>, [FICN-1059], <sequence-number>,, ERROR, <system-name>, Error return from frame generation for a FICON Image: Path=<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR >. Probable Cause Indicates an internal resource shortage caused an error such that an emulation frame could not be created and sent to an LPAR.
Page 333 FICN-1063 Probable Cause Indicates an abort operation has been received from the local FC interface for an active emulation exchange. Recommended This is an unexpected event, contact your vendor's customer support for assistance. Action Severity ERROR FICN-1063 Message <timestamp>, [FICN-1063], <sequence-number>,, ERROR, <system-name>, Egress Abort:Oxid=0x<the OXID of the aborted exchange>:Path=<VEPortNumber HostDomain HostPort DeviceDomain>...
Page 334 FICN-1066 FICN-1066 Message <timestamp>, [FICN-1066], <sequence-number>,, WARNING, <system-name>, MemAllocFailed for GEPort=<GE0 or GE1 Number> VEport=<VEPortNumber> could not create required structure. 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...
Page 335 FICN-1070 Recommended If resolution of the configuration issue cannot be completed, contact your vendor's customer Action support for assistance. Severity ERROR FICN-1070 Message <timestamp>, [FICN-1070], <sequence-number>,, INFO, <system-name>, DevTapeIngr:Exceptional Status rcvd on Path=<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR CUADDR DeviceAddr> state=0x<current emulation state>...
Page 336 FICN-1073 FICN-1073 Message <timestamp>, [FICN-1073], <sequence-number>,, INFO, <system-name>, HostTapeIngr:Unloaded:Path=<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR CUADDR DeviceAddr>:states=0x<4 prior emulation states>:cmds=0x<last 4 commands received from the channel for this device>:status=0x<last 4 status values sent to the channel for this device>:flags=0x<tape report bit flags (0x80-Tape Loaded,0x40-WriteEmul,0x20-RdBlkEmul,0x10-RdCpEmul)>.
Page 337 FICN-1076 Severity INFO FICN-1076 Message <timestamp>, [FICN-1076], <sequence-number>,, INFO, <system-name>, HostTapeIngr:ReadCpReport:Path=<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR CUADDR DeviceAddr>: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 megabytes processed while this tape was loaded>.
Page 338 FICN-1079 Recommended No action is required. Action Severity INFO FICN-1079 Message <timestamp>, [FICN-1079], <sequence-number>,, INFO, <system-name>, DevTapeEgr:WriteReport:Path=<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR CUADDR DeviceAddr>: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 339 FICN-1082 Recommended This is normally an unexpected event, contact your vendor's customer support for assistance. Action Severity WARNING FICN-1082 Message <timestamp>, [FICN-1082], <sequence-number>,, WARNING, <system-name>, EmulEls:CSWR_RSCN received on GEPort=<GEPortNumber> VEPort=<VEPortNumber> Domain=0x<Domain Port Host> Port=0x<Device Side>. Probable Cause Indicates an attached port which had a FICON emulated path established has logged out from the switch.
Page 340 FICN-1086 Probable Cause Indicates a FICON FCIP tunnel has been established successfully to the peer switch. Recommended No action is required. Action Severity INFO FICN-1086 Message <timestamp>, [FICN-1086], <sequence-number>,, ERROR, <system-name>, FICON FCIP Tunnel is Down on GE<Either GE0 or GE1>,tunnel Id=<The configured tunnel ID (0-7)>.
Page 341: Ficu System Messages
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 a part of the Fabric OS configuration database and is for support use only. The error variable is an internal error number.
Page 342 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 343 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 344 FICU-1010 FICU-1010 Message <timestamp>, [FICU-1010], <sequence-number>,, WARNING, <system-name>, FMS Mode enable failed due to address conflict with port <port number> 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 345 FICU-1014 FICU-1014 Message <timestamp>, [FICU-1014], <sequence-number>,, INFO, <system-name>, CUP SBTOV Timeout - %s, Type(%s). Probable Cause Indicates that the FICON Host failed to send an IU within the SBTOV. Recommended No Action is required. Action Severity INFO FICU-1015 Message CUP SB <timestamp>, [FICU-1015], <sequence-number>,, INFO, <system-name>, Recovery DIB - %s, DIB_Type(%s).
Page 346 FICU-1018 FICU-1018 Message <timestamp>, [FICU-1018], <sequence-number>,, WARNING, <system-name>, FMSMODE enable noticed swapped ports. Probable Cause Indicates some ports are swapped at the time of FMS Mode enable. Recommended Verify expected FICON Port Address / Port Number relationship. Action Severity WARNING FICU-1019 Message Switch has...
Page 347 FICU-1022 FICU-1022 Message <timestamp>, [FICU-1022], <sequence-number>,, ERROR, <system-name>, Detected FC8-48 and/or FC8-64 that are not manageable when FMS mode is enabled. Probable Cause Indicates presence of unmanageable ports such as 48 port blade ports in Virtual Fabric disabled chassis. Recommended No action is required.
Page 348 FICU-1022 Fabric OS Message Reference 53-1001767-01...
Page 349: Fklb System Messages
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 350 FKLB-1001 Fabric OS Message Reference 53-1001767-01...
Page 351: Flod System Messages
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 352 FLOD-1006 Probable Cause Indicates that the received LSR contained an invalid domain number. Recommended No action is required because the LSR is discarded. Action Severity WARNING FLOD-1006 Message <timestamp>, [FLOD-1006], <sequence-number>,, WARNING, <system-name>, Transmitting invalid domain ID: <domain number> Probable Cause Indicates that the transmit LSR contained an invalid domain number.
Page 353: Fspf System Messages
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 354 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 355 FSPF-1008 Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1001767-01...
Page 356 FSPF-1008 Fabric OS Message Reference 53-1001767-01...
Page 357: Fss System Messages
Chapter FSS System Messages FSS-1001 Message <timestamp>, [FSS-1001], <sequence-number>, SLOT cp-slot-number | CHASSIS, 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 358 FSS-1004 If the message persists, run the supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING FSS-1004 Message <timestamp>, [FSS-1004], <sequence-number>, SLOT cp-slot-number | CHASSIS, ERROR, <system-name>, Memory shortage Probable Cause Indicates that the system ran out of memory.
Page 359 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 360 FSS-1011 FSS-1011 Message <timestamp>, [FSS-1011], <sequence-number>, SLOT cp-slot-number | CHASSIS, INFO, <system-name>, FSS Info: <Info Message>. Probable Cause Indicates an informational message only. Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1001767-01...
Page 361: Fssm System Messages
Chapter FSSM System Messages FSSM-1002 Message <timestamp>, [FSSM-1002], <sequence-number>, SLOT cp-slot-number | CHASSIS, 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 362 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 or downgrade was invoked. The new firmware version is not compatiable with the current running version.
Page 363: Fw System Messages
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 364 FW-1004 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 365 FW-1012 Recommended Set the high boundary above the normal operation range. Action Severity INFO FW-1012 Message <timestamp>, [FW-1012], <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 power supply counter changed from a value outside of the acceptable range to a value within the acceptable range.
Page 366 FW-1035 FW-1035 Message <timestamp>, [FW-1035], <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 temperature of the small form-factor pluggable (SFP) has risen above the high boundary. Frequent fluctuations in temperature might indicate a deteriorating SFP. Recommended Replace the SFP.
Page 367 FW-1039 Probable Cause Indicates that the receive power value of the small form-factor pluggable (SFP) has fallen below the low boundary. The receive performance area measures the amount of incoming laser to help you determine if the SFP is in good working condition or not. If the counter often exceeds the threshold, the SFP is deteriorating.
Page 368 FW-1042 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. If the counter often exceeds the threshold, the SFP is deteriorating.
Page 369 FW-1045 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. 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 370 FW-1048 Severity WARNING FW-1048 Message <timestamp>, [FW-1048], <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 value of the small form-factor pluggable (SFP) voltage has changed from a value outside of the acceptable range to a value within the acceptable range.
Page 371 FW-1052 Recommended Frequent voltage fluctuations are an indication that the SFP is deteriorating. Replace the SFP. Action Severity WARNING FW-1052 Message <timestamp>, [FW-1052], <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 value of the small form-factor pluggable (SFP) voltage has changed from a value outside of the acceptable range to a value within the acceptable range.
Page 372 FW-1115 FW-1115 Message <timestamp>, [FW-1115], <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 times E_Ports have gone down has risen above the high 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.
Page 373 FW-1118 FW-1118 Message <timestamp>, [FW-1118], <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 fabric reconfigurations has fallen below the low boundary. The following occurrences can cause a fabric reconfiguration: •...
Page 374 FW-1121 • Two switches with the same domain ID have connected to one another. • Two fabrics have joined. • An E_Port has gone offline. • A principal link has segmented from the fabric. Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation.
Page 375 FW-1124 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-1124 Message <timestamp>, [FW-1124], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value>...
Page 376 FW-1127 • 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. A low number of segmentation errors means that the fabric is functioning normally. Recommended No action is required.
Page 377 FW-1129 Severity INFO FW-1129 Message <timestamp>, [FW-1129], <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 zone changes has changed. Zone changes occur when there is a change to the effective zone configuration.
Page 378 FW-1133 Probable Cause Indicates that the number of zone changes has changed from a value outside of the acceptable range to a value within the acceptable range. Zone changes occur when there is a change to the effective zone configuration. Recommended No action is required.
Page 379 FW-1136 FW-1136 Message <timestamp>, [FW-1136], <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 logins has changed from a value outside of the acceptable range to a value within the acceptable range.
Page 380 FW-1140 Probable Cause Indicates that the number of small form-factor pluggable (SFP) state changes has risen above the high boundary. SFP state changes occur when the SFP is inserted or removed. Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation.
Page 381 FW-1162 Probable Cause Indicates that the number of link failures that the port experiences has fallen below the low boundary. Link loss errors occur when a link experiences a loss of signal and fails. Both physical and hardware problems can cause link loss errors. Link loss errors frequently occur due to a loss of synchronization.
Page 382 FW-1164 FW-1164 Message <timestamp>, [FW-1164], <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 synchronization losses that the port experiences has changed. Loss of synchronization errors frequently occur due to a faulty small form-factor pluggable (SFP) or cable. Signal losses often create synchronization losses.
Page 383 FW-1167 FW-1167 Message <timestamp>, [FW-1167], <sequence-number>,, INFO, <system-name>, <Port 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 synchronization losses that the port experiences has changed from a value outside of the acceptable range to a value within the acceptable range.
Page 384 FW-1171 Probable Cause Indicates that the number of signal losses that the port experiences has risen above the high boundary. Loss of signal generally indicates a physical problem. Recommended Check both ends of your cable connection. Verify that the cable is not faulty. Action Severity WARNING...
Page 385 FW-1174 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-1174 Message <timestamp>, [FW-1174], <sequence-number>,, WARNING, <system-name>, <Port Name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value>...
Page 386 FW-1177 FW-1177 Message <timestamp>, [FW-1177], <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 invalid words that the port experiences has fallen below the low boundary.
Page 387 FW-1181 Probable Cause Indicates that the number of invalid cyclic redundancy checks (CRCs) that the port experiences has changed. Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation. Frequent fluctuations in CRC errors generally indicate an aging fabric. Check your small form-factor pluggables (SFPs), cables, and connections for faulty hardware.
Page 388 FW-1184 Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation. Frequent fluctuations in CRC errors generally indicate an aging fabric. Check your small form-factor pluggables (SFPs), cables, and connections for faulty hardware. Verify that all optical hardware is clean.
Page 389 FW-1187 FW-1187 Message <timestamp>, [FW-1187], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, is between high and low boundaries(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 changed from a value outside of the acceptable range to a value within the acceptable range.
Page 390 FW-1191 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-1191 Message <timestamp>, [FW-1191], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value>...
Page 391 FW-1194 Severity INFO FW-1194 Message <timestamp>, [FW-1194], <sequence-number>,, WARNING, <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 number of state changes that the port experiences has risen above the high boundary.
Page 392 FW-1197 FW-1197 Message <timestamp>, [FW-1197], <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 link resets that the port experiences has fallen below the low boundary.
Page 393 FW-1201 Probable Cause Indicates that the number of C3 transmit time out frames has changed. Recommended Check the target device; it could be slow. Action Severity INFO FW-1201 Message <timestamp>, [FW-1201], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, is below low boundaries (High=<High value>, Low=<Low value>). Current value is <Value>...
Page 394 FW-1204 FW-1204 Message <timestamp>, [FW-1204], <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 trunk utilization has changed. Recommended No action required. Action Severity INFO FW-1205 Message <timestamp>, [FW-1205], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, is below low boundaries (High=<High value>, Low=<Low value>).
Page 395 FW-1244 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. Receive performance messages appear due to the number of word frames that travel from the configured S_ID to the D_ID pair.
Page 396 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 397 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 398 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 399 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 400 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 401 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 402 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 403 FW-1337 FW-1337 Message <timestamp>, [FW-1337], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of device cable connection (DCC) violations has fallen below the low boundary. DCC violations indicate that an unauthorized device tried to join the fabric. The DCC_POLICY allows for the specification of rules for binding device ports (typically host bus adaptor (HBA) ports) to specific switch ports.
Page 404 FW-1340 Probable Cause Indicates that the number of device cable connection (DCC) violations has changed from a value outside of the acceptable range to a value within the acceptable range. DCC violations indicate that an unauthorized device tried to join the fabric. The DCC_POLICY allows for the specification of rules for binding device ports (typically host bus adaptor (HBA) ports) to specific switch ports.
Page 405 FW-1343 Recommended Run the errShow command to determine the IP location of the login attempt. Responses to Action security-class messages depend on user policies. Consult your security administrator for response strategies and policies. Severity WARNING FW-1343 Message <timestamp>, [FW-1343], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>).
Page 406 FW-1352 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 407 FW-1354 FW-1354 Message <timestamp>, [FW-1354], <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 invalid certificates has risen above the high boundary. This violation indicates that a packet with an invalid certificate has been received from the primary fabric configuration server (FCS).
Page 408 FW-1357 Severity INFO FW-1357 Message <timestamp>, [FW-1357], <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 authentication failures has fallen below the low boundary. Authentication failures can occur for many reasons. The switch on the other side might not support the protocol, have an invalid certificate, not be signed properly or send unexpected packets.
Page 409 FW-1364 Severity INFO FW-1364 Message <timestamp>, [FW-1364], <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 time service (TS) out-of-sync violations has changed. Recommended Responses to security-class messages depend on user policies. Consult your security administrator Action for response strategies and policies.
Page 410 FW-1368 Recommended No action is required. Action Severity INFO FW-1368 Message <timestamp>, [FW-1368], <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 no-FCS violations has changed. This counter records how often the switch loses contact with the primary fabric configuration server (FCS) fabric configuration server (FCS) switch.
Page 411 FW-1371 Probable Cause Indicates that the number of no-FCS violations has risen above the high boundary. 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 412 FW-1373 FW-1373 Message <timestamp>, [FW-1373], <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 incompatible security database violations has fallen below the low boundary. This violation indicates the number of secure switches with different version stamps have been detected.
Page 413 FW-1376 FW-1376 Message <timestamp>, [FW-1376], <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 illegal commands has changed. 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 414 FW-1379 Severity WARNING FW-1379 Message <timestamp>, [FW-1379], <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 illegal commands has changed from a value outside of the acceptable range to a value within the acceptable range.
Page 415 FW-1402 FW-1402 Message <timestamp>, [FW-1402], <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 flash usage percentage has risen above the high boundary. Flash increases and decreases slightly with normal operation of the switch. Excessive permanent increases can lead to future problems.
Page 416 FW-1406 Recommended No action is required. Action Severity INFO FW-1406 Message <timestamp>, [FW-1406], <sequence-number>,, CRITICAL, <system-name>, <Label>,is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause It means memory usage is above high memory threshold. Recommended No action is required.
Page 417 FW-1425 Recommended Run the switchStatusShow command to determine the policy violation. Action Severity WARNING FW-1425 Message <timestamp>, [FW-1425], <sequence-number>,, INFO, <system-name>, Switch status <Bad state> changed from to HEALTHY. Probable Cause Indicates that the switch status has changed to a healthy state. This occurred because a policy is no longer violated.
Page 418 FW-1428 FW-1428 Message <timestamp>, [FW-1428], <sequence-number>,, WARNING, <system-name>, Switch status <Number Missing> change contributing factor Power supply: absent. Probable Cause Indicates that the switch status is not in a healthy state. This occurred because the number of missing power supplies is greater than or equal to the policy set by the switchStatusPolicySet command.
Page 419 FW-1432 Recommended Replace the faulty or deteriorating fan field-replaceable units (FRUs). Action Severity WARNING FW-1432 Message <timestamp>, [FW-1432], <sequence-number>,, WARNING, <system-name>, Switch status <Number Bad> change contributing factor WWN: bad. Probable Cause Indicates that the switch status is not in a healthy state. This occurred because the number of faulty world wide name (WWN) cards is greater than or equal to the policy set by the switchStatusPolicySet command.
Page 420 FW-1435 Recommended Replace the faulty blade. Action Severity WARNING FW-1435 Message <timestamp>, [FW-1435], <sequence-number>,, WARNING, <system-name>, Switch status change contributing factor Flash: usage out of range. Probable Cause Indicates that the switch status is not in a healthy state. This occurred because the flash usage is out of range.
Page 421 FW-1438 FW-1438 Message <timestamp>, [FW-1438], <sequence-number>,, WARNING, <system-name>, Switch status <Num of missing SFPs> change contributing factor Missing SFPs: missing SFPs. Probable Cause Indicates that the switch status is not in a healthy state. This occurred because the number of missing small form-factor pluggables (SFPs) is greater than or equal to the policy set by the switchStatusPolicySet command.
Page 422 FW-1442 Severity INFO FW-1442 Message <timestamp>, [FW-1442], <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 “on”. Recommended No action is required. Verify that the event was planned. Action Severity INFO...
Page 423 FW-1446 Recommended No action required, unless there are fewer than 4 power supplies active in the chassis. If there are Action fewer than 4, insert additional power supplies so that there are 4 active. Severity INFO FW-1446 Message <timestamp>, [FW-1446], <sequence-number>,, WARNING, <system-name>, Four power supplies now required for 2X redundancy, not enforced by Fabric Watch due to Switch Status Policy overridden by User.
Page 424 FW-1501 FW-1501 Message <timestamp>, [FW-1501], <sequence-number>,, INFO, <system-name>, Mail overflow <Mails discarded> cleared - alerts discarded. Probable Cause Indicates that the mail overflow condition has cleared. Recommended No action is required. Action Severity INFO FW-1510 Message <timestamp>, [FW-1510], <sequence-number>,, INFO, <system-name>, <Area string> threshold exceeded: Port <Port number>...
Page 425 FW-1513 Probable Cause Indicates that the number of link failures that the port experiences has changed and dropped below upper threshold boundary 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 426 FW-1516 Probable Cause Indicates that the number of signal losses that the port experiences has changed and crossed lower threshold boundary to a value within the acceptable range. Loss of signal generally indicates a physical problem. Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation.
Page 427 FW-1519 Probable Cause Indicates that the number of protocol errors that the port experiences has changed and dropped below upper threshold boundary to a value within the acceptable range. Occasional protocol errors occur due to software glitches. Persistent protocol errors occur due to hardware problems. Recommended No action is required.
Page 428 FW-1522 Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation. Frequent fluctuations in CRC errors generally indicate an aging fabric. Check your small form-factor pluggables (SFPs), cables, and connections for faulty hardware. Verify that all optical hardware is clean.
Page 429 FW-1525 FW-1525 Message <timestamp>, [FW-1525], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, has crossed lower threshold boundary to in between(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the percentage of outgoing traffic that the port experiences has changed and crossed lower threshold boundary to a value within the acceptable range.
Page 430 FW-1529 Probable Cause Indicates that the number of state changes that the port experiences has changed and dropped below upper boundary to a value within the acceptable range. The state of the port has changed for one of the following reasons: the port has gone offline, has come online, is testing, is faulty, has become an E_Port, has become an F_Port, has segmented, or has become a trunk port.
Page 431 FW-1532 Recommended Check the target device. It could be slow. Action Severity INFO FW-1532 Message <timestamp>, [FW-1532], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, has dropped below upper threshold boundary to in between(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of C3 transmit time out frames has dropped below upper threshold boundary and is in between low and high thresholds.
Page 432 FW-1535 FW-1535 Message <timestamp>, [FW-1535], <sequence-number>,, INFO, <system-name>, Fabric Watch has stopped portfencing feature for <Area String> loss area in <Port Name> class since FOS6.3. Disabling port fencing feature for this. Probable Cause Indicates that in previous versions portfencing is configured for Link/Sync loss, but after upgrading to new version, in which portfencing is not suppoted, resets the above bit.
Page 433 FW-3013 Recommended No action is required. Action Severity WARNING FW-3013 Message <timestamp>, [FW-3013], <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 circuit utilization is in-between high and low threshold. Recommended No action required.
Page 434 FW-3017 Probable Cause Indicates the packet loss that the circuit experiences is above threshold. Recommended No action is required. Action Severity WARNING FW-3017 Message <timestamp>, [FW-3017], <sequence-number>,, INFO, <system-name>, <Port Name>,<Label> is between high and low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit> Probable Cause Indicates the packet loss that the circuit experiences is in-between the specified range.
Page 435 FW-3020 FW-3020 Message <timestamp>, [FW-3020], <sequence-number>,, WARNING, <system-name>, <Port Name>,<Label> is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit> Probable Cause Indicates the number of state changes that the circuit experiences has increased above the high boundary. The state of the circuit has changed for the reason that the circuit has gone offline, it has come online, or it is testing.
Page 436 FW-3021 Fabric OS Message Reference 53-1001767-01...
Page 437: Ham System Messages
Chapter HAM System Messages HAM-1001 Message <timestamp>, [HAM-1001], <sequence-number>, SLOT cp-slpt-number | FFDC | CHASSIS, 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 438 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 439 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. Run the supportSave command and contact your switch service provider. Severity CRITICAL HAM-1007 Message <timestamp>, [HAM-1007], <sequence-number>, SLOT cp-slpt-number | FFDC | CHASSIS, FFDC, CRITICAL, <system-name>,Need to reboot the system for recovery, reason: <reason name>.
Page 440 HAM-1010 HAM-1010 Message <timestamp>, [HAM-1010], <sequence-number>, SLOT cp-slot-number | CHASSIS, CRITICAL, <system-name>,Please maunually trigger hareboot/reboot for recovery from OOM when appropriate. Probable Cause Indicates OOM is detected when system is not ready for warm recovery. Recommended Manually trigger reboot for cold recovery if needed, or wait until system is ready and use Action hareboot/hafailover to trigger warm recovery.
Page 441 HAM-1014 Severity CRITICAL HAM-1014 Message <timestamp>, [HAM-1014], <sequence-number>, SLOT cp-slot-number | CHASSIS, CRITICAL, <system-name>. Probable Cause Indicates a software watchdog detected termination of a restartable daemon and needed to reboot/failover. Recommended If needed manually initiate a reboot/failover. Action Severity CRITICAL Fabric OS Message Reference 53-1001767-01...
Page 442 HAM-1014 Fabric OS Message Reference 53-1001767-01...
Page 443: Hamk System Messages
Chapter HAMK System Messages HAMK-1001 Message <timestamp>, [HAMK-1001], <sequence-number>, SLOT cp-slot-number | CHASSIS, 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 the Action supportFtp command (as needed) to set up automatic FTP transfers;...
Page 444 HAMK-1004 HAMK-1004 Message <timestamp>,[HAMK-1004], <sequence-number>, SLOT cp-slot-number | CHASSIS, 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 445: Hil System Messages
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 threshold. Recommended Replace the faulty blade or switch (for nonbladed switches). Action Severity ERROR...
Page 446 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 threshold. Recommended Run the psShow command to verify the power supply status. Action Try to reseat the faulty fan field-replaceable units (FRUs) and power supply FRU to verify that they are seated properly.
Page 447 HIL-1107 HIL-1107 Message <timestamp>, [HIL-1107], <sequence-number>, FFDC, 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 448 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 449 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 450 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 451 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 452 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 453 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 454 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 455 HIL-1505 Recommended No action is required. Action Severity INFO HIL-1505 Message <timestamp>, [HIL-1505], <sequence-number>,, WARNING, <system-name>, High temperature (<measured temperature> C) fan speed increasing per environmental specifications. Probable Cause Indicates that temperatures in the system have risen above the warning threshold and the fan speed is increased.
Page 456 HIL-1508 Severity CRITICAL 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 457 HIL-1601 HIL-1601 Message <timestamp>, [HIL-1601], <sequence-number>,, ERROR, <system-name>, Using backup temperature sensor. Attention needed. 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 458 HIL-1610 Recommended No action required. Action Severity INFO HIL-1610 Message <timestamp>, [HIL-1610], <sequence-number>, FFDC, WARNING, <system-name>, Fan/PS unit <Combo fan/power supply unit number> not supplying power, fan speeds not available. Please ensure that the unit has power and the switch is on. Probable Cause Indicates that the power supply is not connected to a power source or it is not switched on or the unit is faulty.
Page 459: Hlo System Messages
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 460 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 461: Hmon System Messages
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 462 HMON-1001 Fabric OS Message Reference 53-1001767-01...
Page 463: Hsl System Messages
Chapter HSL System Messages HSL-1000 Message <timestamp>, [HSL-1000], <sequence-number>,, CRITICAL, <system-name>, HSL initialization failed. Probable Cause Indicates an HSL initialization failure. Recommended No action is required. Action Severity CRITICAL HSL-1001 Message <timestamp>, [HSL-1001], <sequence-number>,, CRITICAL, <system-name>, Failed to acquire system mac address pool. Probable Cause Indicates the failure to acquire a system address.
Page 464 HSL-1004 Recommended No action is required. Action Severity INFO HSL-1004 Message <timestamp>, [HSL-1004], <sequence-number>,, ERROR, <system-name>, Incompatible SFP for interface <Interface name> is detected. Probable Cause Indicates an incompatible SFP for the interface has been inserted. Recommended Use the correct SFP for this interface. Action Severity ERROR...
Page 465 HSL-1007 Recommended Install more memory on board. Action Severity CRITICAL HSL-1007 Message <timestamp>, [HSL-1007], <sequence-number>,, ERROR, <system-name>, Failed to read SFP for interface <InterfaceName>. Probable Cause Indicates a failure to read an SFP. Recommended No action is required. Action Severity ERROR Fabric OS Message Reference 53-1001767-01...
Page 466 HSL-1007 Fabric OS Message Reference 53-1001767-01...
Page 467: Http System Messages
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 468 HTTP-1003 Fabric OS Message Reference 53-1001767-01...
Page 469: Ibd System Messages
Chapter IBD System Messages IBD-1001 Message <timestamp>, [IBD-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 470 IBD-1001 Fabric OS Message Reference 53-1001767-01...
Page 471: Ibpd System Messages
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 472 IBPD-1003 Fabric OS Message Reference 53-1001767-01...
Page 473: Icpd System Messages
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 474 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 475 ICPD-1008 Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1001767-01...
Page 476 ICPD-1008 Fabric OS Message Reference 53-1001767-01...
Page 477: Ipad System Messages
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 478 IPAD-1001 Fabric OS Message Reference 53-1001767-01...
Page 479: Ips System Messages
Chapter IPS System Messages IPS-1001 Message <timestamp>, [IPS-1001], <sequence-number>,, WARNING, <system-name>, <message> FCIP License Not Installed (<error>) Probable Cause Indicates that the FCIP license is not installed on the switch. Recommended Run the licenseShow command to check the installed licenses on the switch. Contact your switch Action supplier for a FCIP license.
Page 480 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 481: Iscs System Messages
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-1001767-01...
Page 482 ISCS-1000 Fabric OS Message Reference 53-1001767-01...
Page 483: Isns System Messages
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 484 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 485 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 486 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 or port. Use the isnscCfg command to display or Action correct the server IP address.
Page 487: Kac System Messages
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 488 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 or resolve the operational problem at the vault. Severity ERROR KAC-1008...
Page 489: Kswd System Messages
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 that 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 490 KSWD-1002 Fabric OS Message Reference 53-1001767-01...
Page 491: Ktrc System Messages
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 492 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 493: L2Sys System Messages
Chapter L2SYS System Messages L2SS-1001 Message <timestamp>, [L2SS-1001], <sequence-number>,, ERROR, <system-name>, Socket Error: <reason> for socket <sockname> the error code <errorname>. Probable Cause Indicates an error has occurred in the Linux socket. Recommended Restart the l2ssd daemon. Action Severity ERROR L2SS-1002 Message <timestamp>, [L2SS-1002], <sequence-number>,, ERROR, <system-name>,...
Page 494 L2SS-1005 Recommended Restart the l2sysd daemon. Action Severity ERROR L2SS-1005 Message <timestamp>, [L2SS-1005], <sequence-number>,, ERROR, <system-name>, Mac-address-table hash failed even after two attempts for slot <slot> chip <chip>. Probable Cause Indicates a mac-address-table hash failure happened even after two hash changes on the chip. Recommended Restart the l2sysd daemon.
Page 495: Lacp System Messages
Chapter LACP System Messages LACP-1001 Message <timestamp>, [LACP-1001], <sequence-number>,, ERROR, <system-name>, <module> Error opening socket (<error>). Probable Cause Indicates that the initialization of a module within the LACP daemon has failed. Recommended Download a new firmware version using the firmwareDownload command. Refer to the Fabric OS Action Command Reference Manual for more information on this command.
Page 496 LACP-1001 Fabric OS Message Reference 53-1001767-01...
Page 497 Chapter LANCE System Messages LANCE-1000 Message <timestamp>, [LANCE-1000], <sequence-number>,, ERROR, <system-name>, Slot <slot number> Port GE <port number>: Maximum attempts to restart failed. Disabling port. Probable Cause Indicates that the port is disabled. Recommended No action is required. Action Severity ERROR Fabric OS Message Reference 53-1001767-01...
Page 498 LANCE-1000 Fabric OS Message Reference 53-1001767-01...
Page 499: Lfm System Messages
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 500 LFM-1004 LFM-1004 Message <timestamp>, [LFM-1004], <sequence-number>,FFDC, 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 501: Log System Messages
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 502 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-1001767-01...
Page 503: Lsdb System Messages
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 504 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 505: Mfic System Messages
Chapter MFIC System Messages MFIC-1001 Message <timestamp>, [MFIC-1001], <sequence-number>,, ERROR, <system-name>, failure at sysmod_scn registry rc= <failure reason> 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 506 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 507: Mpth System Messages
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 508 MPTH-1003 Fabric OS Message Reference 53-1001767-01...
Page 509: Mq System Messages
2 - MSG_TX • 3 - MSG_INTR • 4 - MSG_STR • 6 - MSG_ASYNC_IU • 7 - MSG_LINIT_IU • 8 - MSG_RSCN • 9 - MSG_IOCTL • 10 - MSG_ACCEPT • 11 - MSG_IU_FREE • 12 - MSG_US •...
Page 510 MQ-1006 MQ-1006 Message <timestamp>, [MQ-1006], <sequence-number>,, WARNING, <system-name>, queue <queue name>: msg too long (<number of bytes>:<message queue size>) Probable Cause Indicates the incoming message size is larger than the message queue size. Recommended No action is required. Action Severity WARNING Fabric OS Message Reference 53-1001767-01...
Page 511: Ms System Messages
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 512 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 513 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 514 MS-1009 MS-1009 Message <timestamp>, [MS-1009], <sequence-number>,, ERROR, <system-name>, RLIR event. Switch Port ID is <port number> (<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 515 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 516 MS-1026 Fabric OS Message Reference 53-1001767-01...
Page 517: Mstp System Messages
Chapter MSTP System Messages MSTP-1001 Message <timestamp>, [MSTP-1001], <sequence-number>,, ERROR, <system-name>, <msg>:<msg>. Probable Cause Indicates that the system has failed to allocate memory. Recommended Check the memory usage on the switch using the memShow command. Action Restart or power cycle the switch. Severity ERROR MSTP-1002...
Page 518 MSTP-2002 Recommended No action is required Action Severity INFO MSTP-2002 Message <timestamp>, [MSTP-2002], <sequence-number>,, INFO, <system-name>, <Bridge mode information>. My Bridge ID: <Bridge ID> Old Root: <Old Root id> New Root: <New Root ID> Probable Cause Indicates that the MSTP bridge or bridge instance root has changed. Recommended No action is required.
Page 519 MSTP-2006 Recommended No action is required. Action Severity INFO MSTP-2006 Message <timestamp>, [MSTP-2006], <sequence-number>,, INFO, <system-name>, MSTP instance <instance> brigde priority is changed from <priority_old> to <priority_new>. Probable Cause Indicates that the MSTP instance priority has modified. Recommended No action is required. Action Severity INFO...
Page 520 MSTP-2006 Fabric OS Message Reference 53-1001767-01...
Page 521: Nbfs System Messages
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 522 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 523: Ns System Messages
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 524 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 525 NS-1007 NS-1007 Message <timestamp>, [NS-1007], <sequence-number>,, WARNING, <system-name>, NS has detected a logical ISL port <LISL port number> in TI zone <TI zone name> in fabric <Fabric ID>. Routing may not be setup correctly. Probable Cause Indicates that a logical ISL is detected in the TI zone. Recommended Remove the LISL port from the TI zone because the routing may not be set up correctly.
Page 526 NS-1011 NS-1011 Message <timestamp>, [NS-1011], <sequence-number>,, WARNING, <system-name>, NS has detected a failover flag disabled TI zone in a base switch <domain id> in fabric id <fabric id>. Probable Cause Indicates that a failover flag has disabled TI zone in a base switch fabric. Recommended Modify failover flag to enable or remove TI zone with failover flag disabled since the routing may not Action...
Page 527: Nsm System Messages
Chapter NSM System Messages NSM-1001 Message <timestamp>, [NSM-1001], <sequence-number>,, INFO, <system-name>, Interface <Interface Name> is online. Probable Cause Indicates that the interface is online after the protocol dependencies are resolved. Recommended No action is required. Action Severity INFO NSM-1002 Message <timestamp>, [NSM-1002], <sequence-number>,, INFO, <system-name>, Interface <Interface Name>...
Page 528 NSM-1005 Recommended No action is required. Action Severity INFO NSM-1005 Message <timestamp>, [NSM-1005], <sequence-number>,, INFO, <system-name>,The FCoE VLAN: <Vlan name> is in use. First remove all the FCoE sessions of its member ports and then try again to disable it. Probable Cause Indicates that the FCoE VLAN is used in FCoEd.
Page 529 NSM-1009 Recommended No action is required. Action Severity INFO NSM-1009 Message <timestamp>, [NSM-1009], <sequence-number>,, INFO, <system-name>, Interface <InterfaceName> is deleted. Probable Cause Indicates that the logical interface has been deleted. Recommended No action is required. Action Severity INFO NSM-1010 Message <timestamp>, [NSM-1010], <sequence-number>,, INFO, <system-name>, InterfaceMode changed from <Mode_old>...
Page 530 NSM-1013 Recommended No action is required. Action Severity INFO NSM-1013 Message <timestamp>, [NSM-1013], <sequence-number>,, INFO, <system-name>, Vlan classifier group <group_id> is deleted. Probable Cause Indicates that Vlan classifier group has been deleted. Recommended No action is required. Action Severity INFO NSM-1014 Message <timestamp>, [NSM-1014], <sequence-number>,, INFO, <system-name>, Vlan classifier...
Page 531 NSM-1017 Recommended No action is required. Action Severity INFO NSM-1017 Message <timestamp>, [NSM-1017], <sequence-number>,, INFO, <system-name>, Interface <InterfaceName> is <action> on interface <Logical_InterfaceName>. Probable Cause Indicates that logical interface member list has been changed. Recommended No action is required. Action Severity INFO NSM-1018...
Page 532 NSM-1021 Recommended No action is required. Action Severity INFO NSM-1021 Message <timestamp>, [NSM-1021], <sequence-number>,, INFO, <system-name>, DCE ports disabled due to non-availability of core blades. Probable Cause Indicates that the DCE ports were brought down due to non-availability of cores. Recommended Enable the DCE ports after bringing up the core blades.
Page 533: Onm System Messages
Chapter ONM System Messages ONMD-1000 Message <timestamp>, [ONMD-1000], <sequence-number>,, INFO, <system-name>, LLDP is enabled. Probable Cause Indicates that LLDP is globally enabled. Recommended No action is required. Action Severity INFO ONMD-1001 Message <timestamp>, [ONMD-1001], <sequence-number>,, INFO, <system-name>, LLDP is disabled. Probable Cause Indicates that LLDP is globally disabled.
Page 534 ONMD-1004 Recommended No action is required. Action Severity INFO ONMD-1004 Message <timestamp>, [ONMD-1004], <sequence-number>,, INFO, <system-name>, LLDP is disabled on interface <InterfaceName>. Probable Cause Indicates that LLDP is disabled on interface. Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1001767-01...
Page 535: Pdm System Messages
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 536 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 the supportFtp command (as needed) to set up automatic FTP transfers;...
Page 537 PDM-1008 Recommended Run the firmwareDownload command to reinstall the firmware. Action If the message persists, run the supportFtp command (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...
Page 538 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 539 PDM-1017 Recommended Run the firmwareDownload command to reinstall the firmware. Action If the message persists, run the supportFtp command (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...
Page 540 PDM-1022 Probable Cause Indicates a system call failed. Recommended Run the firmwareDownload command to reinstall the firmware. Action If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING PDM-1022...
Page 541: Pdtr System Messages
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 542 PDTR-1002 Fabric OS Message Reference 53-1001767-01...
Page 543: Plat System Messages
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 the supportFtp command (as needed) to set up automatic FTP transfers;...
Page 544 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 545: Pmgr System Messages
Chapter PMGR System Messages PMGR-1001 Message <timestamp>, [PMGR-1001], <sequence-number>, INFO, <system-name>, Attempt to create switch <FID> succeeded. Probable Cause Indicates that 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>, Attempt to create switch <FID>...
Page 546 PMGR-1005 Recommended No action is required. Action Severity WARNING PMGR-1005 Message <timestamp>, [PMGR-1005], <sequence-number>, INFO, <system-name>, Attempt to move port(s) <Ports> on slot <Slot> to switch <FID> succeeded. Probable Cause Indicates the successful attempt to move the ports to the specified switch. Recommended No action is required.
Page 547 PMGR-1009 Recommended No action is required. Action Severity WARNING PMGR-1009 Message <timestamp>, [PMGR-1009], <sequence-number>, INFO, <system-name>,Attempt to change the base switch to switch <FID> succeeded. Probable Cause Indicates the successful change of the base switch. Recommended No action is required. Action Severity INFO...
Page 548 PMGR-1011 Fabric OS Message Reference 53-1001767-01...
Page 549: Port System Messages
Chapter PORT System Messages PORT-1003 Message <port <timestamp>, [PORT-1003], <sequence-number>,, WARNING, <system-name>, Port number> Faulted because of many Link Failures Probable Cause Indicates that the specified port is now disabled because the link on this port had multiple failures that 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 550 PORT-1006 Recommended Invoke the portCfgLport command to clear the L_port configuration. Action Severity WARNING PORT-1006 Message <timestamp>, [PORT-1006], <sequence-number>,, INFO, <system-name>, 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 551 PORT-1010 Recommended No action is required. Action Severity INFO PORT-1010 Message <timestamp>, [PORT-1010], <sequence-number>,, WARNING, <system-name>, Port (ID: <port number>) QOS is disabled. Probable Cause The Port QOS is disabled because the port currently has Best Effort Setting that requires QOS to be disabled on a 4G or 8G long distance platform.
Page 552 PORT-1010 Fabric OS Message Reference 53-1001767-01...
Page 553: Ps System Messages
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 (APM). The performance monitor has failed to initialize. Recommended The control processor (CP) should restart (or fail over) automatically If this does not happen, restart Action or power cycle the switch to re-initiate the firmware.
Page 554 PS-1004 Probable Cause Indicates that the restoring configuration has failed 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 555 PS-1007 PS-1007 Message <timestamp>, [PS-1007], <sequence-number>,, WARNING, <system-name>, Failed to add fabricmode toptalker on domain=<domain id>. <function name>. Probable Cause Indicates that FCR or McData mode is enabled on this particular fabric. Recommended No action required. Top Talker cannot be installed on fabric with FC router or McData mode Action enabled.
Page 556 PS-1007 Fabric OS Message Reference 53-1001767-01...
Page 557: Pswp System Messages
Chapter PSWP System Messages PSWP-1001 Message <timestamp>, [PSWP-1001], <sequence-number>,, INFO, <system-name>, PID for port <wwn name corresponding to source port> and port <wwn name corresponding to destination port> are swapped. New PID for port <wwn name corresponding to source port> is <wwn name corresponding to destination port> and port <new area corresponding to source wwn>...
Page 558 PSWP-1004 PSWP-1004 Message <timestamp>, [PSWP-1004], <sequence-number>,, INFO, <system-name>, Blade Swap complete for slots <slot number corresponding to the source blade> and <slot number corresponding to the destination blade>. Probable Cause Indicates that the bladeSwap command has been issued. Recommended No action is required. Action Severity INFO...
Page 559: Ras System Messages
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 data event was captured. Recommended Run the supportFtp command (as needed) to set up automatic FTP transfers and run the Action supportSave command then contact your switch service provider.
Page 560 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 561 RAS-3001 Probable Cause Indicates that the configured classes of the audit feature have been changed. 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 562 RAS-3004 Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1001767-01...
Page 563: Rcs System Messages
Chapter RCS System Messages RCS-1001 Message <timestamp>, [RCS-1001], <sequence-number>,, INFO, <system-name>, RCS has been disabled. Some switches in the fabric do not support this feature. Probable Cause Indicates that the RCS feature has been disabled on the local switch because not all switches in the fabric support RCS or the switch is in nonnative mode.
Page 564 RCS-1004 RCS-1004 Message <timestamp>, [RCS-1004], <sequence-number>,, ERROR, <system-name>, Application(<application name>) not registered.(<error string>) Probable Cause Indicates that a specified application did not register with RCS. Recommended Run the haShow command to view the HA state. Action Run the haDisable and the haEnable commands. Run the rcsInfoShow command to view RCS capability on the fabric.
Page 565 RCS-1007 Severity INFO RCS-1007 Message <timestamp>, [RCS-1007], <sequence-number>,, ERROR, <system-name>, Zone DB size and propogation overhead exceeds domain <domain number>'s maximum supported Zone DB size <max zone db size>. Retry after reducing the Zone DB size. Probable Cause Indicates that a domain cannot handle the zone database being committed. Recommended Reduce the zone database size.
Page 566 RCS-1008 Fabric OS Message Reference 53-1001767-01...
Page 567: Rkd System Messages
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 568 RKD-1004 RKD-1004 Message <timestamp>, [RKD-1004], <sequence-number>,, INFO, <system-name>, Message: <Generic rekey message>. Probable Cause Indicates the generic rekey message. Recommended No action is required. Action Severity INFO RKD-1005 Message <timestamp>, [RKD-1005], <sequence-number>,, WARNING, <system-name>, LUN with LSN: <LUN LSN> does no have metadata. Please make note of key ID <Key ID for encrypt/decrypt>...
Page 569: Rmond System Messages
Chapter RMOND System Messages RMON-1001 Message <timestamp>, [RMON-1001], <sequence-number>,, INFO, <system-name>, RMON rising threshold alarm from SNMP OID <oid>. Probable Cause Indicates that the threshold level has exceeded for the sample type of RMON alarm. Recommended Check the traffic on the interface. Action Severity INFO...
Page 570 RMON-1002 Fabric OS Message Reference 53-1001767-01...
Page 571: Rpcd System Messages
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 572 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 in the switch. Action Severity WARNING...
Page 573: Rtwr System Messages
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 has occurred in the RTWR. The message provides the name of the routine having the error, and more specific error information.
Page 574 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 the number of times the RTWR has failed to get a response. Recommended Run the dom command to verify that the specified domain ID is reachable.
Page 575: Sas System Messages
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 576 SAS-1001 Fabric OS Message Reference 53-1001767-01...
Page 577: Scn System Messages
Chapter SCN System Messages SCN-1001 Message <timestamp>, [SCN-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, SCN < > queue overflow for process daemon name 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 578 SCN-1001 Fabric OS Message Reference 53-1001767-01...
Page 579: Sec System Messages
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 580 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 has 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 581 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 582 SEC-1016 Recommended Resolve the above specifed error by executing the command only from Primary FCS. Action Severity ERROR SEC-1016 Message <timestamp>, [SEC-1016], <sequence-number>,, INFO, <system-name>, Security <IP address of the violating host> violation: Unauthorized host with IP address tries to establish SSH connection. Probable Cause Indicates a security violation was reported.
Page 583 SEC-1025 SEC-1025 Message <timestamp>, [SEC-1025], <sequence-number>,, ERROR, <system-name>, Invalid IP address (<IP address>) detected. 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 584 SEC-1029 SEC-1029 Message <timestamp>, [SEC-1029], <sequence-number>,, ERROR, <system-name>, Invalid character in <policy name>. 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 585 SEC-1033 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 586 SEC-1036 Severity ERROR SEC-1036 Message <timestamp>, [SEC-1036], <sequence-number>,, ERROR, <system-name>, Device name <device name> is invalid due to a missing colon. Probable Cause Indicates one or more device names mentioned in the securePolicyCreate or securePolicyAdd command does not have the colon character (:) as required. Recommended Run the secPolicyCreate or secPolicyAdd command with a properly formatted device name Action...
Page 587 SEC-1041 Severity ERROR SEC-1041 Message <timestamp>, [SEC-1041], <sequence-number>,, ERROR, <system-name>, Invalid port member <port member> in portlist (<port list>). <Reason>. Probable Cause Indicates the port member is invalid for one of the following reasons: • The value is not a number. •...
Page 588 SEC-1045 Probable Cause Indicates the specified member is a duplicate in the input list. The list can be a policy list or a switch member list. Recommended Do not specify any duplicates. Action Severity ERROR SEC-1045 Message <timestamp>, [SEC-1045], <sequence-number>,, ERROR, <system-name>, Too many port members.
Page 589 SEC-1050 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-1050...
Page 590 SEC-1053 Severity ERROR SEC-1053 Message <timestamp>, [SEC-1053], <sequence-number>,, ERROR, <system-name>, Invalid pFCS list <pFCS 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 591 SEC-1056 SEC-1056 Message <timestamp>, [SEC-1056], <sequence-number>,, ERROR, <system-name>, Invalid position <New position>. Only <Number of members in FCS list> members in list. 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 592 SEC-1063 Probable Cause Indicates that either no domains or domains more than the maximum number supported are specified. Recommended Enter the correct number of domains. Action Severity ERROR SEC-1063 Message <timestamp>, [SEC-1063], <sequence-number>,, ERROR, <system-name>, Failed to reset statistics. Probable Cause Indicates that either the type or domains specified are invalid.
Page 593 SEC-1071 Probable Cause Indicates 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. Severity ERROR SEC-1071 Message <timestamp>, [SEC-1071], <sequence-number>,, ERROR, <system-name>, No new security policy data to apply.
Page 594 SEC-1075 Probable Cause Indicates a security command was run on a switch that is not allowed to run it either because it is in non-secure mode or because it does not have the required fabric configuration server (FCS) privilege. Recommended If a security operation that is not allowed in non-secure mode is attempted, do not perform the Action operation in non-secure mode.
Page 595 SEC-1078 Severity ERROR SEC-1078 Message <timestamp>, [SEC-1078], <sequence-number>,, ERROR, <system-name>, No new data to abort. Probable Cause Indicates there are no new changes in the defined security policy database that can be aborted. Recommended Verify the security event was planned. Verify if there were really any changes to the defined policy Action database that can be aborted.
Page 596 SEC-1082 Probable Cause Indicates the device connection control (DCC) policy name given in the secPolicyCreate command was the same as another DCC policy. Recommended Make sure that the DCC policy name has a unique alphanumeric string, and run the Action secPolicyCreate command again.
Page 597 SEC-1085 SEC-1085 Message <timestamp>, [SEC-1085], <sequence-number>,, ERROR, <system-name>, Failed to create <policy name>. Probable Cause Indicates that the security policy was not created. Recommended Check that the current policy configuration is valid. For example, the RSNMP policy cannot exist Action without the WSNMP policy.
Page 598 SEC-1089 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-1089...
Page 599 SEC-1092 SEC-1092 Message <timestamp>, [SEC-1092], <sequence-number>,, ERROR, <system-name>, <Policy name> Name not found. 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 600 SEC-1096 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 601 SEC-1099 SEC-1099 Message <timestamp>, [SEC-1099], <sequence-number>,, ERROR, <system-name>, Please enable your switch before running secModeEnable. 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 602 SEC-1104 Probable Cause Indicates the switch failed to download a certificate, security database, or policies. This can happen when the switch does not have enough resources to complete the operation, the fabric has not stabilized, or the policy database is an invalid format. Recommended Wait for fabric to become stable and then retry the operation.
Page 603 SEC-1107 SEC-1107 Message <timestamp>, [SEC-1107], <sequence-number>,, INFO, <system-name>, Stamp is 0. 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 604 SEC-1112 Probable Cause Indicates the defined and active fabric configuration server (FCS) policy list failed to have at least one member in common. Recommended A new FCS policy list must have at least one member in common with the previous FCS policy. Action Severity ERROR...
Page 605 SEC-1115 SEC-1115 Message <timestamp>, [SEC-1115], <sequence-number>,, ERROR, <system-name>, No primary FCS to failover. Probable Cause Indicates that during an attempted secFcsFailover, no primary fabric configurations server (FCS) is present in the fabric. Recommended Run the secFabricShow command to verify that all switches in fabric are in the ready state. When Action all switches are in the ready state, retry the operation.
Page 606 SEC-1119 Recommended Usually this problem is transient. Retry the command. Action Severity INFO SEC-1119 Message <timestamp>, [SEC-1119], <sequence-number>,, INFO, <system-name>, Secure mode has been enabled. Probable Cause Indicates the secure Fabric OS was enabled by the secModeEnable command. Recommended Verify the security event was planned. If the security event was planned, there is no action required. Action If the security event was not planned, take appropriate action as defined by your enterprise security policy.
Page 607 SEC-1124 Probable Cause Indicates the security database was successfully downloaded from the primary fabric configuration server (FCS). Recommended No action is required. Action Severity INFO SEC-1124 Message <timestamp>, [SEC-1124], <sequence-number>,, INFO, <system-name>, Secure Mode is off. Probable Cause Indicates that a secure mode disable is attempted in a non-secure fabric. Recommended No action is required.
Page 608 SEC-1135 SEC-1135 Message <timestamp>, [SEC-1135], <sequence-number>,, INFO, <system-name>, Secure fabric version stamp has been reset. Probable Cause Indicates the version stamp of the secure fabric is reset. 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 609 SEC-1138 SEC-1138 Message <timestamp>, [SEC-1138], <sequence-number>,, INFO, <system-name>, Security database download received from Primary FCS. Probable Cause Indicates that a non-primary fabric configuration server (FCS) switch received a security database download. 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 610 SEC-1146 Probable Cause Indicates one of the following has occurred: • The names for the specified policies have changed. • The passwords have changed for the specified accounts. • The SNMP community strings have been 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 611 SEC-1155 Probable Cause Indicates that either the defined or the active policy could not be updated. If the policy database is very large, it might not be able to change the index/area because the new policy database exceeds the maximum size. This message can also be caused when the switch is short of memory. The status values can be either defined, active, or both.
Page 612 SEC-1158 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 SEC-1158 Message <timestamp>, [SEC-1158], <sequence-number>,, INFO, <system-name>, Invalid name <Policy or Switch name>. Probable Cause Indicates the specified name is invalid.
Page 613 SEC-1164 Probable Cause Indicates the lockdown option was attempted while the fabric is already in secure mode. Recommended Do not use lockdown option with the secModeEnable command when a switch is already in secure Action mode. Severity ERROR SEC-1164 Message <timestamp>, [SEC-1164], <sequence-number>,, ERROR, <system-name>, Lockdown option cannot be applied on a non-FCS switch.
Page 614 SEC-1167 SEC-1167 Message <timestamp>, [SEC-1167], <sequence-number>,, ERROR, <system-name>, Another FCS failover is in process. Command terminated. Probable Cause Indicates that because another failover is already in progress, this failover attempt cannot proceed. Recommended Verify the security event was planned. If the security event was planned, retry fabric configurations Action server (FCS) failover after current failover has completed, if this switch should become primary FCS.
Page 615 SEC-1171 SEC-1171 Message <timestamp>, [SEC-1171], <sequence-number>,, ERROR, <system-name>, Disabled secure mode due to invalid security object. Probable Cause Indicates the switch is segmented, and secure mode is disabled on the switch because there was no license present or no public key infrastructure (PKI) objects. Recommended Run the pkiShow command to determine whether all PKI objects exist.
Page 616 SEC-1175 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-1175 Message <timestamp>, [SEC-1175], <sequence-number>,, ERROR, <system-name>, Failed to install zone data.
Page 617 SEC-1182 Recommended No action is required. Action Severity INFO SEC-1182 Message <timestamp>, [SEC-1182], <sequence-number>,, INFO, <system-name>, Recovered <number of> accounts. Probable Cause Indicates the specified number of accounts has been recovered from backup. Recommended No action is required. Action Severity INFO SEC-1183 Message...
Page 618 SEC-1186 Probable Cause Indicates the switch database was enabled or disabled as the secondary authentication, accounting, and authorization (AAA) mechanism when the Remote Authentication Dial-in User Service (RADIUS) / Lightweight Directory Access Protocol (LDAP) is the primary AAA mechanism Recommended No action is required.
Page 619 SEC-1189 Recommended Check the DCC policy and verify the specified device is allowed in the fabric and is included in the Action DCC policy. If the specified device is not included in the policy, add it to the policy. If the host is not allowed access to the fabric, this is a valid violation message and an unauthorized entity is trying to access your fabric.
Page 620 SEC-1192 Recommended Determine whether the host IP address specified in the message can be used to manage the fabric Action through an HTTP connection. If so, add the host IP address to the HTTP policy of the fabric. If the host is not allowed access to the fabric, this is a valid violation message and an unauthorized entity is trying to access your fabric.
Page 621 SEC-1195 SEC-1195 Message <timestamp>, [SEC-1195], <sequence-number>,, WARNING, <system-name>, This switch has no <component> 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 622 SEC-1199 Recommended Check to see if the host IP address specified in the message can be used to manage the fabric Action through an API connection. If so, add the host IP address to the API policy of the fabric. If the host is not allowed access to the fabric, this is a valid violation message and an unauthorized entity is trying to access your fabric.
Page 623 SEC-1202 Severity INFO SEC-1202 Message <timestamp>, [SEC-1202], <sequence-number>,, INFO, <system-name>, Security violation: Unauthorized access from MS device node name <device node name>, device port name <device port name>. Probable Cause Indicates a management server (MS) security violation was reported. The unauthorized device specified in the message attempted to establish a connection.
Page 624 SEC-1253 Probable Cause Indicates the security database conversion failed because of invalid values. The reason is specified in the text message variable and a faulty value is printed in the value variable. 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 625 SEC-1302 SEC-1302 Message <timestamp>, [SEC-1302], <sequence-number>,, INFO, <system-name>, This switch does not have all the required PKI objects correctly installed. 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 626 SEC-1306 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 627 SEC-1309 Severity INFO SEC-1309 Message <timestamp>, [SEC-1309], <sequence-number>,, INFO, <system-name>, Waiting for RCS <Wait time in seconds> transaction to complete: secs Probable Cause Indicates that Secure Fabric OS is still waiting for the reliable commit service (RCS) transaction to complete. Recommended Verify if there are any RCS or RTWR errors.
Page 628 SEC-1313 Probable Cause Indicates the passwdCfg parameters 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 629 SEC-1316 SEC-1316 Message <timestamp>, [SEC-1316], <sequence-number>,, WARNING, <system-name>, <Policy Name> policy is conflicting with domain <Domain Number> Probable Cause Indicates the newly added switches to the fabric, as specified by Domain Number, have a conflicting policy with the local switch. Recommended Check the conflicting policy and make the new swithces and the local switch policies the same.
Page 630 SEC-1320 SEC-1320 Message <timestamp>, [SEC-1320], <sequence-number>,, WARNING, <system-name>, Non-acl domain <Domain Number> tries to join a fabric with strict fabric wide policy Probable Cause Indicates that a domain not supporting an access control list (ACL) policy tried to join a fabric with a strict fabric-wide policy.
Page 631 SEC-1324 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. Severity INFO SEC-1324 Message <timestamp>, [SEC-1324], <sequence-number>,, INFO, <system-name>, Fabric <Error code>...
Page 632 SEC-1328 Probable Cause Indicates the policy is conflicting with the domain. Recommended No action is required. The domain is denied by disallowing all its E_ports connected to the fabric. If Action the domain should be allowed to merge with the fabric, then resolve the issue by making the conflicting policies the same.
Page 633 SEC-1331 SEC-1331 Message <timestamp>, [SEC-1331], <sequence-number>,, ERROR, <system-name>, Attempt to enable secure mode failed. Reason: <Reason>. Probable Cause Indicates the secModeEnable command failed on the fabric because default IP Filter policies are not active on the switch, or an active transaction exists on IP Filter policies. Recommended Verify the security event was planned.
Page 634 SEC-3035 Probable Cause Indicates new members have been added to a security policy. If you use a wildcard (for example, an asterisk) in adding members to a policy, the audit report displays the wildcard in the event info field. Recommended Verify the addition of members to the policy was planned.
Page 635 SEC-3038 SEC-3038 Message <timestamp>, [SEC-3038], <sequence-number>, AUDIT, INFO, <system-name>, Event: ipfilter, Status: failed, Info: Failed to activate <IP Filter Policy> ipfilter policy. Probable Cause Indicates that the specified IP filter policy failed to activate. Recommended Verify that the security event was planned. If the 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-3061 Recommended No action is required. Action Severity INFO SEC-3061 Message <timestamp>, [SEC-3061], <sequence-number>, AUDIT, INFO, <system-name>, Role <role name> is created. Probable Cause Indicates a role name was created. Recommended No action is required. Action Severity INFO SEC-3062 Message <timestamp>, [SEC-3062], <sequence-number>, AUDIT, INFO, <system-name>, Role <role name>...
Page 637 SEC-3065 Recommended No action is required. Action Severity INFO SEC-3065 Message <timestamp>, [SEC-3065], <sequence-number>, AUDIT, INFO, <system-name>, Configuration of user-defined roles is uploaded. Probable Cause Indicates the configuration of user-defined roles are uploaded. Recommended No action is required. Action Severity INFO SEC-3066 Message...
Page 638 SEC-4001 Fabric OS Message Reference 53-1001767-01...
Page 639: Sflow System Messages
Chapter SFLOW System Messages SFLO-1001 Message <timestamp>, [SFLO-1001], <sequence-number>,, INFO, <system-name>, sFlow is <state> globally. Probable Cause Indicates that the sFlow is enabled or disabled globally. Recommended No action is required. Action Severity INFO SFLO-1002 Message <timestamp>, [SFLO-1002], <sequence-number>,, INFO, <system-name>, sFlow is <state>...
Page 640 SFLO-1005 Recommended No action is required. Action Severity INFO SFLO-1005 Message <timestamp>, [SFLO-1005], <sequence-number>,, INFO, <system-name>, sFlow sampling rate on port <name> is changed to <sample_rate>. Probable Cause Indicates that the sampling rate has changed on the port. Recommended No action is required. Action Severity INFO...
Page 641 SFLO-1008 Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1001338-01...
Page 642 SFLO-1008 Fabric OS Message Reference 53-1001338-01...
Page 643: Snmp System Messages
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 644 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 645 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 command to view the current device status. Action Severity INFO Fabric OS Message Reference 53-1001767-01...
Page 646 SNMP-1008 Fabric OS Message Reference 53-1001767-01...
Page 647: Spc System Messages
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 648 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 is asserted by FPGA. Recommended No action is required. Action Severity ERROR SPC-2002 Message <timestamp>, [SPC-2002], <sequence-number>,, CRITICAL, <system-name>, <slot number containing Encryption Engine>, <module name>: Tamper Event: Crypto...
Page 649 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 650 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. Run the initEE and regEE commands. Action Severity CRITICAL...
Page 651 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 652 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 653 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 654 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 the initEE and regEE commands. Action Severity ERROR...
Page 655 SPC-3014 Recommended Contact your 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 has failed. Recommended Contact technical support.
Page 656 SPC-3015 Fabric OS Message Reference 53-1001767-01...
Page 657: Spm System Messages
Chapter SPM System Messages SPM-1001 Message <timestamp>, [SPM-1001], <sequence-number>,, ERROR, <system-name>, Init fails: <Reason>. Probable Cause Indicates the SPM has failed to initialize. Recommended Check the system resources and restart the switch. Action Severity ERROR SPM-1002 Message <timestamp>, [SPM-1002], <sequence-number>,, WARNING, <system-name>, Generic SPM Warning: <Reason>.
Page 658 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 Indicates encryption engine (EE) control slot configuration. Recommended No action is required. Action Severity INFO SPM-1006 Message <timestamp>, [SPM-1006], <sequence-number>,, INFO, <system-name>, Registered...
Page 659 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 Indicates that a certificate is missing. Recommended Run the cryptocfg --initnode command. Action Severity ERROR SPM-1010 Message <timestamp>, [SPM-1010], <sequence-number>,, ERROR, <system-name>, <cert> Key Vault Certificate is missing.
Page 660 SPM-1013 Recommended No action is required. Action Severity INFO SPM-1013 Message <timestamp>, [SPM-1013], <sequence-number>,, ERROR, <system-name>, Security database is out of sync. Probable Cause Indicates a failure to distribute security database. Recommended Use cryptocfg --sync -securitydb to manually sync security db. Action Severity ERROR...
Page 661 SPM-3002 Recommended No action is required. Action Severity INFO SPM-3002 Message <timestamp>, [SPM-3002], <sequence-number>,, INFO, <system-name>,Event: cryptocfg Status: success, Info: EE in slot <slot> initialized. Probable Cause Indicates an encryption engine was initialized. Recommended No action is required. Action Severity INFO SPM-3003 Message...
Page 662 SPM-3006 Recommended No action is required. Action Severity INFO SPM-3006 Message <timestamp>, [SPM-3006], <sequence-number>,, INFO, <system-name>,Event: cryptocfg Status: success, Info: <source file> file exported via scp: <hostUsername> [<hostIP>]:<hostPath>. Probable Cause Indicates a file was exported using SCP protocol. Recommended No action is required. Action Severity INFO...
Page 663 SPM-3010 Recommended No action is required. Action Severity INFO SPM-3010 Message <timestamp>, [SPM-3010], <sequence-number>,, INFO, <system-name>,Event: cryptocfg Status: success, Info: EE in slot <slot> zeroized. Probable Cause Indicates an encryption engine was zeroized. Recommended No action is required. Action Severity INFO SPM-3011 Message...
Page 664 SPM-3014 Recommended No action is required. Action Severity INFO SPM-3014 Message <timestamp>, [SPM-3014], <sequence-number>,, INFO, <system-name>,Event: cryptocfg Status: success, Info: Key archive client registered with certificate file \"<certFilename>\". Probable Cause Indicates a KAC certificate was registered. Recommended No action is required. Action Severity INFO...
Page 665 SPM-3018 Recommended No action is required. Action Severity INFO SPM-3018 Message <timestamp>, [SPM-3018], <sequence-number>,, INFO, <system-name>,Event: cryptocfg Status: success, Info: <currentOrAlternate>master key recovered. Probable Cause Indicates a master key was recovered. Recommended No action is required. Action Severity INFO SPM-3019 Message <timestamp>, [SPM-3019], <sequence-number>,, INFO, <system-name>,Event: cryptocfg Status: success, Info: System card registered.
Page 666 SPM-3022 Recommended No action is required. Action Severity INFO SPM-3022 Message <timestamp>, [SPM-3022], <sequence-number>,, INFO, <system-name>,Event: cryptocfg Status: success, Info: Authentication card with certificate label \"<certLabel>\" deregistered. Probable Cause Indicates an authentication card was de-registered. Recommended No action is required. Action Severity INFO...
Page 667 SPM-3026 Recommended No action is required. Action Severity INFO SPM-3026 Message <timestamp>, [SPM-3026], <sequence-number>,, INFO, <system-name>,Event: cryptocfg Status: success, Info: File exported via usb: Source: <sourcePath> Destination: <destinationFilename>. Probable Cause Indicates a file was exported through the USB device. Recommended No action is required.
Page 668 SPM-3029 Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1001767-01...
Page 669: Ss System Messages
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 670 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 has 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 671 SS-1007 Severity WARNING SS-1007 Message <timestamp>, [SS-1007], <sequence-number>,, WARNING, <system-name>, supportsave failed for the slot <Slot Number>. Reason: No response from the blade in the corresponding slot for the given ss request. Probable Cause Indicates no reponse from the blade in the corresponding slot for the given supportsave request. Recommended Reboot the switch and then run the supportsave command.
Page 672 SS-1008 Fabric OS Message Reference 53-1001767-01...
Page 673: Ssm System Messages
Chapter SSM System Messages SSMD-1001 Message <timestamp>, [SSMD-1001], <sequence-number>,, ERROR, <system-name>,Failed to allocate memory: <function name>. Probable Cause Indicates that the specified function has failed to allocate memory. Recommended Check the memory usage on the switch using the memShow command. Action Restart or power cycle the switch.
Page 674 SSMD-1005 Probable Cause Indicates that the specified function has failed to unlock the mutex (semaphore). Recommended Restart or power cycle the switch. Action Severity ERROR SSMD-1005 Message <timestamp>, [SSMD-1005], <sequence-number>,, ERROR, <system-name>,SSM startup failed. Probable Cause Indicates the DCE System Services Manager (SSM) encountered an unexpected, severe error during basic startup and initialization.
Page 675 SSMD-1202 SSMD-1202 Message <timestamp>, [SSMD-1202], <sequence-number>,, WARNING, <system-name>,QoS failed programming interface 0x<Interface ID> x 802.3x Pause flow control. Probable Cause Indicates the DCE System Services Manager (SSM) encountered an unexpected error in programming the dataplane ASIC for enforcing the interface 802.3x Pause flow control feature. Recommended Delete and reapply QoS 802.3x Pause flow control policy.
Page 676 SSMD-1206 Severity WARNING SSMD-1206 Message <timestamp>, [SSMD-1206], <sequence-number>,, WARNING, <system-name>,CEE failed programming CoS to PGID policy for CEE Map <CEE Map name>. Probable Cause Indicates the DCE System Services Manager (SSM) encountered an unexpected error in programming the dataplane ASIC for enforcing the CEE Map CoS to PGID mapping feature. Recommended Delete and reapply the CEE Map CoS to PGID policy.
Page 677 SSMD-1210 Recommended Delete and reapply the QoS interface CoS Mutation policy. Restart or power cycle the switch. Action Severity WARNING SSMD-1210 Message <timestamp>, [SSMD-1210], <sequence-number>,, WARNING, <system-name>,QoS failed programming interface 0x <Interface ID> x CoS to Traffic Class map. Probable Cause Indicates the DCE System Services Manager (SSM) encountered an unexpected error in programming the dataplane ASIC for enforcing the CoS to Traffic Class mapping feature.
Page 678 SSMD-1214 Probable Cause Indicates the DCE System Services Manager (SSM) encountered an unexpected error in programming the dataplane ASIC for enforcing the interface CoS Tail Drop Threshold feature. Recommended Delete and reapply the QoS CoS Tail Drop Threshold policy. Restart or power cycle the switch. Action Severity WARNING...
Page 679 Indicates the DCE System Services Manager (SSM) was unable to translate CEE Map and FCoE configuration into an ETS scheduler policy implementable by the dataplane ASIC. Recommended Redefine CEE Map and FCoE into a configuration that translates into into an ETS scheduler policy Action requiring 8 or fewer Traffic Class. Severity WARNING SSMD-1300 Message <timestamp>, [SSMD-1300], <sequence-number>,, INFO, <system-name>, CEEMap...
Page 680 SSMD-1303 SSMD-1303 Message <timestamp>, [SSMD-1303], <sequence-number>,, INFO, <system-name>, CEEMap <ceemap> priority group <pg_id> with weight <PGID_weight> is created with pfc <pfc>. Probable Cause Indicates that priority Group has been created. Recommended No action is required. Action Severity INFO SSMD-1304 Message <timestamp>, [SSMD-1304], <sequence-number>,, INFO, <system-name>, CEEMap <ceemap>...
Page 681 SSMD-1307 SSMD-1307 Message <timestamp>, [SSMD-1307], <sequence-number>,, INFO, <system-name>, <acl_type> access list <acl_name> is created. Probable Cause Indicates that Access List has been created. Recommended No action is required. Action Severity INFO SSMD-1308 Message <timestamp>, [SSMD-1308], <sequence-number>,, INFO, <system-name>, <acl_type> access list <acl_name> is deleted. Probable Cause Indicates that Access List has been deleted.
Page 682 SSMD-1311 SSMD-1311 Message <timestamp>, [SSMD-1311], <sequence-number>,, INFO, <system-name>, ACL <acl_name> is removed from interface <InterfaceName>. Probable Cause Indicates that Access List has been removed from an interface. Recommended No action is required. Action Severity INFO SSMD-1312 Message <timestamp>, [SSMD-1312], <sequence-number>,, INFO, <system-name>, <map_type> <map_name>...
Page 683: Sulb System Messages
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 started. 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 684 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 685 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 686 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 687 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 688 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 689 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 690 Please reload firmware packages on the file server, then retry firmwareDownload. If the problem persists, contact your system administrator. Table 8 lists the firmwareDownload state names and state values. They indicate where in the firmwareDownload process the error occurred.
Page 691 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 692 SULB-1018 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 693 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 694 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 695 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 696 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 697 SULB-1039 SULB-1039 Message <timestamp>, [SULB-1039], INFO, FIRMWARE, CP has completed relocating the internal firmware image. Probable Cause Indicates that the firmwareDownload command process has been completed normally on the CP. Recommended Run the firmwareShow command to verify the firmware versions. Action Severity INFO...
Page 698 SULB-1040 Fabric OS Message Reference 53-1001767-01...
Page 699: Swch System Messages
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 the supportFtp command (as needed) to set up automatic FTP Action...
Page 700 SWCH-1004 SWCH-1004 Message <timestamp>, [SWCH-1004], <sequence-number>,, ERROR, <system-name>, Blade attach failed during recovery, disabling slot = <slot number> 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 701 SWCH-1008 Recommended Based on the disable reason displayed, proper corrective action may to be required to restore the Action port. If the disable reason is due to insufficient frame buffers, 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 702 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 703 SWCH-1015 Recommended No action is required. Action Severity INFO SWCH-1015 Message <timestamp>, [SWCH-1015], <sequence-number>,, WARNING, <system-name>, <Function name> <Description of problem>. Probable Cause Indicates that an internal problem has been detected by the software. This is usually an internal Fabric OS problem or due to file corruption. Recommended Restart or power cycle the switch Action...
Page 704 SWCH-1019 SWCH-1019 Message <timestamp>, [SWCH-1019], <sequence-number>,, INFO, <system-name>, Device <wwn name of device> tries to flogi, reject FLOGI as persistent PID is set on device and port <port number> has user area <area> bound to it. Probable Cause Indicates a WWN-PID and PortAddress binding collision. Recommended The Peristent PID is set on the device and requested area cannot be assigned because it is user Action...
Page 705: Sysc System Messages
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 does not run on the system. Recommended If the message is reported during a restart after new firmware has been loaded, try reloading the Action...
Page 706 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 707: Sysm System Messages
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 Restart or power cycle the switch. Run the supportFtp command to set up automatic FTP transfers;...
Page 708 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 709: Tape System Messages
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 710 TAPE-1001 Fabric OS Message Reference 53-1001767-01...
Page 711: Trce System Messages
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 712 TRCE-1004 Probable Cause Indicates that a trace dump has been created on the switch or the indicated slot but is not automatically transferred from the switch due to an FTP error, such as a wrong FTP address, FTP site down, or network down. Recommended If the message persists, run the supportFtp command to set up automatic FTP transfers;...
Page 713 TRCE-1007 TRCE-1007 Message <timestamp>, [TRCE-1007], <sequence-number>,, ERROR, <system-name>, Notification of this CP has failed. Parameters temporarily out of sync 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 714 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, restart the CP (dual-CP system) or restart the switch.
Page 715: Trck System Messages
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 has 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 716 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 command. This message is not generated for a configUpload command. All configuration changes occur through the PDM server, so the PDMIPC is the only task possible.
Page 717: Ts System Messages
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 718 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 719: Ucst System Messages
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 the duplicate paths were reported to the specified domain from the specified output port. The path database (PDB) pointer is the address of the path database and provides debugging information.
Page 720 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 721: Upth System Messages
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 722 UPTH-1002 Fabric OS Message Reference 53-1001767-01...
Page 723: Webd System Messages
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 724 WEBD-1006 Recommended No action is required. Action Severity WARNING WEBD-1006 Message <timestamp>, [WEBD-1006], <sequence-number>,, INFO, <system-name>, HTTP server and weblinker restarted due to logfile truncation. Probable Cause Indicates the size of the HTTP log file exceeded the maximum limit. Recommended No action is required.
Page 725: Xtun System Messages
Chapter XTUN System Messages XTUN-1000 Message <timestamp>, [XTUN-1000], <sequence-number>,, ERROR, <system-name>, Missed Data frame:I/T/L:<FC Initiator ID> <FC Target ID> <FCP Logical Unit Number>. Probable Cause Indicates a missed frame with one or more FCP data information units during a SCSI write or read operation.
Page 726 XTUN-1004 Probable Cause Indicates a message transmission failure. Recommended If there was an unexpected job failure associated with this event, contact your customer support for Action assistance. Severity ERROR XTUN-1004 Message <timestamp>, [XTUN-1004], <sequence-number>,, ERROR, <system-name>, Exchange aborted:I/T/L:<FC Initiator ID> <FC Target ID> <FCP Logical Unit Number>. Probable Cause Indicates that the FCP exchange has been aborted by the Initiator.
Page 727 XTUN-2001 Recommended No action is required. Action Severity INFO XTUN-2001 Message <timestamp>, [XTUN-2001], <sequence-number>,, ERROR, <system-name>, FCIP Tunnel <Tunnel Number> DOWN <Reason>. Probable Cause Indicates that the specified tunnel has gone down. Recommended If the tunnel has not been administratively disabled or deleted, a possible network error or Action disruption has occurred.
Page 728 XTUN-2005 Recommended No action is required. Action Severity INFO XTUN-2005 Message <timestamp>, [XTUN-2005], <sequence-number>,, INFO, <system-name>, FCIP Tunnel <Tunnel Number> <Priority Class> Pri QoS DOWN <Reason>. Probable Cause Indicates that the specified quality of service has gone down. This applies to the data classes only. If the f-class goes down, the tunnel itself is marked as down.
Page 729: Zeus System Messages
Chapter ZEUS System Messages ZEUS-1001 Message <timestamp>, [ZEUS-1001], <sequence-number>,, ERROR, <system-name>, Port <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, or a faulty cable between peer ports. Recommended Verify if you are using a compatible SFPs on the peer ports.
Page 730 ZEUS-1001 Fabric OS Message Reference 53-1001767-01...
Page 731: Zolb System Messages
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 732 ZOLB-1001 Fabric OS Message Reference 53-1001767-01...
Page 733: Zone System Messages
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 734 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 735 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 736 ZONE-1013 Recommended Check the device connetion. 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 737 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 738 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 739 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 740 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 741 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 742 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 743 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 744 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 745 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 746 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 747 ZONE-1057 ZONE-1057 Message <timestamp>, [ZONE-1057], <sequence-number>,, WARNING, <system-name>, TI Zone <TI zone name> has domain <Domain ID of switch with version pre6.4.0> running pre FOS6.4.0 firmware. TI member (Domain <Domain ID of higher port index>, Index <Higher port index>) is not supported. Probable Cause Indicates that an unsupported port index(>...
Page 748 ZONE-1057 Fabric OS Message Reference 53-1001767-01...
Page 749 Section Audit Log Messages This section provides the Audit messages, including: • AUDIT AG System Messages ........675 •...
Page 750 Fabric OS Message Reference 53-1001767-01...
Page 751: Audit Ag System Messages
Chapter AUDIT AG System Messages AG-1033 Message AUDIT, <timestamp>, [AG-1033], <sequence-number>,, INFO, <system-name>,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 configuration file has been updated.
Page 752 AG-1037 Probable Cause Indicates that one of the ports is connected to a Non-Brocade Fabric. Recommended No action is required. Action Severity WARNING AG-1037 Message AUDIT, <timestamp>, [AG-1037], <sequence-number>,, INFO, <system-name>,Trunked N_Port (<nport>) going offline, if switchshow CLI for the connected fabric switch port displays Persistently disabled: Area has been acquired, then check cabling: all trunked ports should be in same ASIC Port Group .
Page 753: Audit An System Messages
Chapter AUDIT AN System Messages AN-1003 Message <timestamp>, [AN-1003], <sequence-number>,, WARNING, <system-name>, Slot <slot number>, port <port number within slot number> is a latency bottleneck. <percentage of seconds affected by latency bottlenecking> percent of last <observation period over which the percentage of affected seconds is reported> seconds were affected by this condition.
Page 754 AN-1006 AN-1006 Message <timestamp>, [AN-1006], <sequence-number>,, INFO, <system-name>, Bottleneck detection configuration is successfully changed. Probable Cause Indicates that the bottleneck detection configuration was changed by a user. Recommended No action is required. Action Severity INFO AN-1010 Message <timestamp>, [AN-1010], <sequence-number>,, WARNING, <system-name>, Severe latency bottleneck detected at Slot <slot number>...
Page 755: Audit Auth System Messages
Chapter AUDIT AUTH System Messages AUTH-1045 Message AUDIT, <timestamp>, [AUTH-1045], <sequence-number>,, ERROR, <system-name>, Certificate not present in this switch in <authentication phase> port <port number>. Probable Cause Indicates that the public key infrastructure (PKI) certificate is not installed in this switch. Recommended Check the certificate availability using the pkiShow command.
Page 756 AUTH-3001 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 can be either “authentication type”, “DH group type”, “Hash type”...
Page 757 AUTH-3005 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. Recommended Correct the switch policy configuration on either of the switches using the authUtil command, and Action then enable the specified port using the portEnable command.
Page 758 AUTH-3008 Probable Cause Indicates that the specified port was disabled due to receiving an authentication reject response from the connected switch/device. The error might indicate that an invalid entity attempted to connect to the switch. Recommended Check the connection port for a possible security attack. Action Check the shared secrets using the secAuthSecret command and reinitialize authentication using the portDisable and portEnable commands.
Page 759: Audit Bls System Messages
Chapter AUDIT BLS System Messages BLS-1002 Message <timestamp>, [BLS-1002], <sequence-number>,, INFO, <system-name>, An IPsec/IKE policy was added. Probable Cause Indicates that an IPsec or IKE policy was added and the configuration file was updated. Recommended No action is required. Action Severity INFO BLS-1003...
Page 760 BLS-1003 Fabric OS Message Reference 53-1001767-01...
Page 761: Audit Cnm System Messages
Chapter AUDIT CNM System Messages CNM-3001 Message AUDIT, <timestamp>, [CNM-3001], INFO, , <event-initiator-details>, <event-location>, , Event: cryptocfg Status: success, Info: encryption group \<encryptiongroupname>\ created. Probable Cause Indicates an encryption group was created. Recommended No action is required. Action Severity INFO CNM-3002 Message AUDIT, <timestamp>, [CNM-3002], INFO, , <event-initiator-details>,...
Page 762 CNM-3004 CNM-3004 Message AUDIT, <timestamp>, [CNM-3004], INFO, , <event-initiator-details>, <event-location>, , Event: cryptocfg Status: success, Info: Membernode \<membernodeWWN>\ ejected from encryption group. Probable Cause Indicates a membernode was ejected from an encryption group. Recommended No action is required. Action Severity INFO CNM-3005 Message...
Page 763 CNM-3008 Severity INFO CNM-3008 Message AUDIT, <timestamp>, [CNM-3008], INFO, , <event-initiator-details>, <event-location>, , Event: cryptocfg Status: success, Info: Routing mode of EE in slot <slot> set to <routingmode>. Probable Cause Indicates that the encryption engine (EE) routing mode was set. Recommended No action is required.
Page 764 CNM-3012 Recommended No action is required. Action Severity INFO CNM-3012 Message AUDIT, <timestamp>, [CNM-3012], <sequence-number>,, INFO, <system-name>, Deleteing an EG with luns setup for encryption can lead to luns being disabled if Encryption Group name is not preserved (<egname>). Probable Cause Indicates that the Encryption Group (EG) was deleted, recreate EG with the same name if luns are setup for encryption.
Page 765: Audit Conf System Messages
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 Indicates that the configDownload operation was initiated and completed successfully. The statement that follows, message string, is the description of the classes of configuration parameters that were downloaded.
Page 766 CONF-1022 Severity INFO CONF-1022 Message AUDIT, <timestamp>, [CONF-1022], WARNING, CFG, <event-initiator-details>, <event-location>, , Downloading configuration without disabling the switch was unsuccessful. Probable Cause Indicates an attempt to download the configuration without disabling the switch was unsuccessful because there are one or more parameters that require the switch to be disabled. Recommended Disable the switch using the switchDisable command and download the configuration.
Page 767: Audit Cvlm System Messages
Chapter AUDIT CVLM System Messages CVLM-3001 Message AUDIT, <timestamp>, [CVLM-3001], INFO, , <event-initiator-details>, <event-location>, , Event: cryptocfg Status: success, Info: Failback mode set to <failbackmode>. Probable Cause Indicates that the failback mode was set. Recommended No action is required. Action Severity INFO CVLM-3002...
Page 768 CVLM-3004 CVLM-3004 Message AUDIT, <timestamp>, [CVLM-3004], INFO, , <event-initiator-details>, <event-location>, , Event: cryptocfg Status: success, Info: Cluster member added to HA cluster <HAClusterName>. Probable Cause Indicates a HA cluster member was added to an HA cluster. Recommended No action is required. Action Severity INFO...
Page 769 CVLM-3008 Severity INFO CVLM-3008 Message AUDIT, <timestamp>, [CVLM-3008], INFO, , <event-initiator-details>, <event-location>, , Event: cryptocfg Status: success, Info: Container \<containerName>\ deleted. Probable Cause Indicates a cryptotarget container was deleted. Recommended No action is required. Action Severity INFO CVLM-3009 Message AUDIT, <timestamp>, [CVLM-3009], INFO, , <event-initiator-details>, <event-location>, , Event: cryptocfg Status: success, Info: Manual failback from EE <currentnodeWWN>/<currentSlot>...
Page 770 CVLM-3012 Recommended No action is required. Action Severity INFO CVLM-3012 Message AUDIT, <timestamp>, [CVLM-3012], INFO, , <event-initiator-details>, <event-location>, , Event: cryptocfg Status: success, Info: Initiator \<initiator>\ removed from crypto target container \<cryptoTargetContainer>\. Probable Cause Indicates an initiator was removed from a cryptotarget container. Recommended No action is required.
Page 771 CVLM-3015 CVLM-3015 Message AUDIT, <timestamp>, [CVLM-3015], INFO, , <event-initiator-details>, <event-location>, , Event: cryptocfg Status: success, Info: Lun <LUNNumber>, attached through Initiator \<Initiator>\, removed from crypto target container \<cryptoTargetContainer>\. Probable Cause Indicates a LUN was removed from a cryptotarget container. Recommended No action is required.
Page 772 CVLM-3019 Recommended No action is required. Action Severity INFO CVLM-3019 Message AUDIT, <timestamp>, [CVLM-3019], INFO, , <event-initiator-details>, <event-location>, , Event: cryptocfg Status: success, Info: Tape pool \<tapepoolLabelOrNum>\ modified. Probable Cause Indicates a tapepool was modified. Recommended No action is required. Action Severity INFO...
Page 773 CVLM-3022 CVLM-3022 Message AUDIT, <timestamp>, [CVLM-3022], INFO, , <event-initiator-details>, <event-location>, , Event: cryptocfg Status: success, Info: Resume rekey of LUN <LIUNSpec> attached through Initiator \<Initiator>\ in crypto tgt container \<cryptoTargetContainer>\. Probable Cause Indicates a resume rekey was performed. Recommended No action is required. Action Severity INFO...
Page 774 CVLM-3026 Severity INFO CVLM-3026 Message AUDIT, <timestamp>, [CVLM-3026], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: failed, Info: Decommission of device (container <cryptoTargetContainer> initiator <Initiator>, LUN <Lun>). Probable Cause Indicates that the decommission operation has failed for the device. Recommended Reissue the decommission command. Action Severity INFO...
Page 775: Audit Fcip System Messages
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 776 FCIP-1003 Fabric OS Message Reference 53-1001767-01...
Page 777: Audit Ficu System Messages
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 that 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>,...
Page 778 FICU-1021 Recommended No action is required. Action Severity INFO FICU-1021 Message Port AUDIT, <timestamp>, [FICU-1021], <sequence-number>,, INFO, <system-name>, Addrs (%s) have been UnBlocked by %s. Probable Cause Indicates the Fibre Connectivity (FICON) Management server has unblocked ports. Recommended No action is required. Action Severity INFO...
Page 779: Audit Fw System Messages
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-1001767-01...
Page 780 FW-3001 Fabric OS Message Reference 53-1001767-01...
Page 781: Audit Http System Messages
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 782 HTTP-1003 Fabric OS Message Reference 53-1001767-01...
Page 783: Audit Ipad System Messages
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 784 IPAD-1002 Fabric OS Message Reference 53-1001767-01...
Page 785: Audit Port System Messages
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 786 PORT-1009 Probable Cause Indicates a GigE port has been disabled. Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1001767-01...
Page 787: Audit Sec System Messages
Chapter AUDIT SEC System Messages 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. Recommended Get a new license for this feature. Action Severity WARNING...
Page 788 SEC-3002 SEC-3002 Message AUDIT, <timestamp>, [SEC-3002], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: <Event Related Info>. Probable Cause Indicates the specified security event has occurred. The Event Name can be one of the following: • There has been an fabric configurations server (FCS) failover. •...
Page 789 SEC-3005 Severity INFO SEC-3005 Message AUDIT, <timestamp>, [SEC-3005], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Added members <Members added> to policy <Policy name>. Probable Cause Indicates new members have been added to the specified security policy. Note: If you use a wildcard (for example, an asterisk) in adding members to a policy, the audit report displays the wildcard in the event info field.
Page 790 SEC-3008 SEC-3008 Message AUDIT, <timestamp>, [SEC-3008], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: FCS member moved from position <Old FCS position> to <New FCS position>. Probable Cause Indicates the fabric configuration server (FCS) list has been modified. One of the members of the list has been moved to a new position in the list, as identified in the message.
Page 791 SEC-3012 Recommended Verify that the security statistic was intentionally reset. If the security statistic were intentionally Action reset, no action is required. If the security statistic was not intentionally reset, take appropriate action as defined by your enterprise security policy. Severity INFO SEC-3012...
Page 792 SEC-3015 SEC-3015 Message AUDIT, <timestamp>, [SEC-3015], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Moved RADIUS server <Server name> to position <New position>. Probable Cause Indicates a user has changed the position of the remote authentication dial-in user service (RADIUS) server.
Page 793 SEC-3018 SEC-3018 Message AUDIT, <timestamp>, [SEC-3018], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Parameter [<Parameter Name>] changed from [<Old Value>] to [<New Value>]. Probable Cause Indicates the specified passwdCfg parameter is changed. Recommended Verify the passwdCfg parameter was intentionally changed. If the passwdCfg parameter was Action intentionally changed, no action is required.
Page 794 SEC-3022 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-3022 Message AUDIT, <timestamp>, [SEC-3022], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Successful logout by user [<User>].
Page 795 SEC-3025 SEC-3025 Message AUDIT, <timestamp>, [SEC-3025], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: User account [<User Name>] added. Role: [<Role Type>], Password [<Password Expired or not>], Home AD [<Home AD>], AD list [<AD membership List>]. Probable Cause Indicates a new user account was created.
Page 796 SEC-3029 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-3029 Message AUDIT, <timestamp>, [SEC-3029], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Backup user account \"<User Account Name>\"...
Page 797 SEC-3032 SEC-3032 Message AUDIT, <timestamp>, [SEC-3032], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Switch is configured to <accept or reject> <Database name> database. Probable Cause Indicates the specified event has occurred to accept or reject a certain database. Recommended Verify the event was planned.
Page 798 SEC-3036 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-3036 Message AUDIT, <timestamp>, [SEC-3036], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: ipfilter, Status: failed, Info: Failed to save changes for <IP Filter Policy>...
Page 799 SEC-3039 SEC-3039 Message AUDIT, <timestamp>, [SEC-3039], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: Securty Violation, Status: failed, Info: Unauthorized host with IP address <IP address of the violating host> tries to establish connection using <Protocol Connection Type>. Probable Cause Indicates a security violation was reported. The IP address of the unauthorized host is displayed in the message.
Page 800 SEC-3047 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-3047 Message AUDIT, <timestamp>, [SEC-3047], INFO, SECURITY, <event-initiator-details>, <event-location>, RBAC permission denied for CLI : <Cmd Name>.
Page 801 SEC-3051 Probable Cause Indicates the specified sshutil operation was performed.. 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 802 SEC-3064 Probable Cause Indicates a role name is copied from source role. Recommended No action is required. Action Severity INFO SEC-3064 Message <timestamp>, [SEC-3064], <sequence-number>, AUDIT, INFO, <system-name>, Permission to the RBAC class(es) <RBAC Class Names> is changed for the role <Role Name>.
Page 803 SEC-4001 Probable Cause Indicates the client has logged in. Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1001767-01...
Page 804 SEC-4001 Fabric OS Message Reference 53-1001767-01...
Page 805: Audit Snmp System Messages
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 806 SNMP-1006 Fabric OS Message Reference 53-1001767-01...
Page 807: Audit Spm System Messages
Chapter AUDIT SPM System Messages SPM-3001 Message AUDIT, <timestamp>, [SPM-3001], INFO, <event-initiator-details>, <event-location>,,Event: cryptocfg Status: success, Info: Node initialized. Probable Cause Indicates a node was initialized. Recommended No action is required. Action Severity INFO SPM-3002 Message AUDIT, <timestamp>, [SPM-3002], INFO, <event-initiator-details>, <event-location>,,Event: cryptocfg Status: success, Info: EE in slot <slot>...
Page 808 SPM-3005 Probable Cause Indicates an encryption engine was enabled. Recommended No action is required. Action Severity INFO SPM-3005 Message AUDIT, <timestamp>, [SPM-3005], INFO, <event-initiator-details>, <event-location>,,Event: cryptocfg Status: success, Info: EE in slot <slot> disabled. Probable Cause Indicates an encryption engine was disabled. Recommended No action is required.
Page 809 SPM-3008 SPM-3008 Message AUDIT, <timestamp>, [SPM-3008], INFO, <event-initiator-details>, <event-location>,,Event: cryptocfg Status: success, Info: DH challenge generated for vault IP <vaultIP>. Probable Cause Indicates a DH challenge was generated for a key vault. Recommended No action is required. Action Severity INFO SPM-3009 Message AUDIT, <timestamp>, [SPM-3009], INFO, <event-initiator-details>,...
Page 810 SPM-3012 SPM-3012 Message AUDIT, <timestamp>, [SPM-3012], INFO, <event-initiator-details>, <event-location>,,Event: cryptocfg Status: success, Info: <primaryOrSecondary> key vault registered. Certificate label: \"<certLabel>\" Certificate file: \"<certFilename>\" IP address: <IPAddress>. Probable Cause Indicates a key vault was registered. Recommended No action is required. Action Severity INFO SPM-3013...
Page 811 SPM-3016 Severity INFO SPM-3016 Message AUDIT, <timestamp>, [SPM-3016], INFO, <event-initiator-details>, <event-location>,,Event: cryptocfg Status: success, Info: Master key generated. Probable Cause Indicates a master key was generated. Recommended No action is required. Action Severity INFO SPM-3017 Message AUDIT, <timestamp>, [SPM-3017], INFO, <event-initiator-details>, <event-location>,,Event: cryptocfg Status: success, Info: Master key exported.
Page 812 SPM-3020 Severity INFO SPM-3020 Message AUDIT, <timestamp>, [SPM-3020], INFO, <event-initiator-details>, <event-location>,,Event: cryptocfg Status: success, Info: System card with certificate label \"<certLabel>\" deregistered. Probable Cause Indicates a system card was deregistered. Recommended No action is required. Action Severity INFO SPM-3021 Message AUDIT, <timestamp>, [SPM-3021], INFO, <event-initiator-details>, <event-location>,,Event: cryptocfg Status: success, Info: Authentication card registered.
Page 813 SPM-3024 Recommended No action is required. Action Severity INFO SPM-3024 Message AUDIT, <timestamp>, [SPM-3024], INFO, <event-initiator-details>, <event-location>,,Event: cryptocfg Status: success, Info: Quorum size set to <quorumsize>. Probable Cause Indicates the quorum size was set. Recommended No action is required. Action Severity INFO SPM-3025...
Page 814 SPM-3028 Probable Cause Indicates a recovery card was registered. Recommended No action is required. Action Severity INFO SPM-3028 Message AUDIT, <timestamp>, [SPM-3028], <sequence-number>,, INFO, <system-name>, Event: SPM-EE state changed, Info: EE State: <EE Status>. Probable Cause Indicates an EE state has changed. Recommended No action is required.
Page 815: Audit Sulb System Messages
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 started. This process should take approximately 17 minutes. The process is set to time out after 30 minutes. Recommended No action is required.
Page 816 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 817 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 818 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 819 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 820 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 821 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 822 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 823 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 824 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 825 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 826 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 during relocation of the internal image.
Page 827 SULB-1039 SULB-1039 Message AUDIT, <timestamp>, [SULB-1039], INFO, FIRMWARE, CP has completed relocating the internal firmware image. Probable Cause Indicates that the firmwareDownload command process has been completed normally on the CP. Recommended Run the firmwareShow command to verify the firmware versions. Action Severity INFO...
Page 828 SULB-1040 Fabric OS Message Reference 53-1001767-01...
Page 829: Audit Swch System Messages
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 830 SWCH-1014 Fabric OS Message Reference 53-1001767-01...
Page 831: Audit Ucst System Messages
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 832 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 833 UCST-1027 Severity INFO Fabric OS Message Reference 53-1001767-01...
Page 834 UCST-1027 Fabric OS Message Reference 53-1001767-01...
Page 835: Audit Zone System Messages
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 836 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 837 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 838 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 839 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 840 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 841 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 842 ZONE-3025 Severity INFO Fabric OS Message Reference 53-1001767-01...

This manual is also suitable for:

1606 8/24 8/40 8/8 Poweredge m1000e Poweredge m600 ... Show all

Brocade Communications Systems 8 Reference

Table of Contents

Table of Contents

Section I

Section II

Quick Links

Chapters

Related Manuals for Brocade Communications Systems 8

Summary of Contents for Brocade Communications Systems 8