Page 1 53-1002448-01 ® 15 December 2011 Fabric OS Message Reference Supporting Fabric OS v7.0.1...
Page 2 Copyright © 2002-2011 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, NetIron, SAN Health, ServerIron, and TurboIron are registered trademarks, and Brocade Assurance, Brocade NET Health, Brocade One, CloudPlex, MLX, VCS, VDX, and When the Mission Is Critical, the Network Is Brocade 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 Fabric OS System Error Message 53-0000515-09 Updated for v4.4.0, August 2004 Reference Manual First RASLog release Fabric OS System Error Message 53-0000515-10 Added 22 ZONE messages April 2005 Reference Manual Fabric OS System Error Message 53-0000515-11 Added FICU-1010, HAMK-1004, and July 2005...
Page 4 Title Publication Summary of changes Date number Fabric OS Message Reference 53-1001157-01 Updated for Fabric OS v6.2.0: November 2008 -Revised and added new messages to FSS, KSWD, CTAP, CNM, CVLM, EM, FABR, FCIP, FW, HIL, FCR, SEC, SWCH, UCST, ZONE. -Added new chapters: CHASSIS, LFM, PMGR, TAPE.
Page 5 Title Publication Summary of changes Date number Fabric OS Message Reference 53-1002149-01 Updated for Fabric OS v7.0.0: April 2011 -Added new chapters: C3, CAL, MCAST_SS, RTE, and VS. -Added new messages: AG, AN, ANV, BL, C2, CDR, CCFG, ECC, EM, ESS, FABR, FCOE, FCPH, FICN, FICU, FSPF, FW, HIL, IPAD, IPS, KAC, L2SYS, LACP, LOG, MS, NS, NSM, ONM, PDM, PS, RAS, RCS,...
Page 7: Table Of Contents
Contents About This Document In this chapter ........... lxxix How this document is organized .
Page 8 Configuring the SNMP server hosts ........7 Configuring the SNMPv1 trap recipient .
Page 9 AG-1011 ............38 AG-1012 .
Page 10 AN-1005............48 AN-1010 .
Page 11 AUTH-1023 ............60 AUTH-1025 .
Page 12 BL-1009 ............73 BL-1010 .
Page 13 BL-1050 ............85 BL-1051 .
Page 14 C2-1009............99 C2-1010 .
Page 15 CCFG-1003 ........... . .111 CCFG-1004 .
Page 16 CHS-1005 ............124 Chapter 18 CNM System Messages CNM-1001 .
Page 17 CNM-1035 ............133 CNM-1036 .
Page 18 CNM-3010 ............143 CNM-3011 .
Page 19 CVLC-1015 ............155 CVLC-1016 .
Page 20 CVLM-3001 ........... . .166 CVLM-3002 .
Page 21 DOT1-1008 ........... . . 176 DOT1-1009 .
Page 22 EM-1043 ............190 EM-1044 .
Page 23 Chapter 27 ESWCH System Messages ESW-1001 ............203 ESW-1002 .
Page 24 FABR-1024............216 FABR-1029.
Page 25 FABS-1013 ............228 FABS-1014 .
Page 26 FCOE-1024............242 FCOE-1025 .
Page 27 FCR-1002............253 FCR-1003.
Page 28 FCR-1041 ............264 FCR-1042.
Page 29 FCR-1085............275 FCR-1086.
Page 30 FICN-1029 ............288 FICN-1030 .
Page 31 FICN-1066 ............299 FICN-1067 .
Page 32 FICN-1103 ............311 FICN-1104 .
Page 33 FICU-1006 ............322 FICU-1007 .
Page 34 Chapter 43 FSS System Messages FSS-1001 ............335 FSS-1002.
Page 35 FW-1043 ............346 FW-1044 .
Page 36 FW-1138 ............359 FW-1139 .
Page 37 FW-1194 ............371 FW-1195 .
Page 38 FW-1334 ............383 FW-1335 .
Page 39 FW-1401 ............396 FW-1402 .
Page 40 FW-1511 ............407 FW-1512 .
Page 41 FW-3022 ............419 Chapter 46 HAM System Messages HAM-1001 .
Page 42 HIL-1208 ............433 HIL-1301 .
Page 43 Chapter 49 HLO System Messages HLO-1001............445 HLO-1002 .
Page 44 ICPD-1007 ............460 ICPD-1008 .
Page 45 KAC-1008............474 KAC-1009.
Page 46 Chapter 65 LANCE System Messages LANCE-1000 ........... .489 Chapter 66 LFM System Messages LFM-1001 .
Page 47 MCAST_SS-1012 ..........499 MCAST_SS-1013 .
Page 48 MS-1025 ............513 MS-1026 .
Page 49 NSM-1002 ............525 NSM-1003 .
Page 50 PDM-1009 ............535 PDM-1010 .
Page 51 PMGR-1011 ........... . .547 Chapter 83 PORT System Messages PORT-1003 .
Page 52 RAS-1006............560 RAS-1007.
Page 53 RPCD-1002 ........... . . 571 RPCD-1003 .
Page 54 SEC-1032............585 SEC-1033.
Page 55 SEC-1079............595 SEC-1080.
Page 56 SEC-1118............606 SEC-1119.
Page 57 SEC-1180............617 SEC-1181.
Page 58 SEC-1310............628 SEC-1311.
Page 59 SEC-3063 ............639 SEC-3064 .
Page 60 SPC-2007............651 SPC-2008 .
Page 61 SPM-1008 ............662 SPM-1009 .
Page 62 SPM-3029 ............672 Chapter 99 SS System Messages SS-1000.
Page 63 SSMD-1214 ........... . .683 SSMD-1215 .
Page 64 SULB-1018............700 SULB-1020 .
Page 65 SWCH-1013 ........... . . 710 SWCH-1014 .
Page 66 TRCE-1008............723 TRCE-1009.
Page 67 Chapter 111 VS System Messages VS-1001 ............735 VS-1002 .
Page 68 XTUN-2007 ........... . . 745 XTUN-2008 .
Page 69 ZONE-1022 ........... . .758 ZONE-1023 .
Page 70 ZONE-1060 ........... . .768 Section II Audit Log Messages Chapter 116...
Page 71 Chapter 120 AUDIT CCFG System Messages CCFG-1002 ........... . .783 CCFG-1003 .
Page 72 CVLM-3012 ........... . .794 CVLM-3013 .
Page 73 FW-1404 ............808 FW-1405 .
Page 74 SEC-3005 ............825 SEC-3006 .
Page 75 SEC-3046 ............836 SEC-3047.
Page 76 SPM-3016 ............847 SPM-3017 .
Page 77 SULB-1039 ........... . .865 SULB-1040 .
Page 78 ZONE-3019 ........... . .878 ZONE-3020 .
Page 79: About This Document
About This Document In this chapter • How this document is organized ....... . . lxxix •...
Page 80 • Brocade 5410 • Brocade 5424 • Brocade 5450 • Brocade 5460 • Brocade 5470 • Brocade 5480 • Brocade 6505 • Brocade 6510 • Brocade 7800 • Brocade 8000 • Brocade Encryption Switch • Brocade DCX Backbone and Brocade DCX-4S Backbone FC8-16 port blade FC8-32 port blade FC8-48 port blade...
Page 81: What's New In This Document
The following blades are not supported in any chassis operating with Fabric OS v7.0.1: • FA4-18 • FC4-16IP • FC4-16 • FC4-32 • FC4-48 What’s new in this document The following changes have been made since this document was last released: •...
Page 82: Document Conventions
Document conventions This section describes text formatting conventions and important notice formats used in this document. 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...
Page 83: Notes, Cautions, And Warnings
Notes, cautions, and warnings The following notices and statements are used in this manual. They are listed below in order of increasing severity of potential hazards. NOTE A note provides a tip, guidance, or advice, emphasizes important information, or provides a reference to related information.
Page 84: Additional Information
Additional information This section lists additional Brocade and industry-specific documentation that you might find helpful. Brocade resources To get up-to-the-minute information, go to http://my.brocade.com to register at no cost for a user ID and password. White papers, online demonstrations, and data sheets are available through the Brocade website http://www.brocade.com/products-solutions/products/index.page For additional Brocade documentation, visit the Brocade website: http://www.brocade.com...
Page 85: Document Feedback
• syslog message logs 2. Switch Serial Number The switch serial number and corresponding bar code are provided on the serial number label, as illustrated below. The serial number label is located as follows: • Brocade 300, 5100, 5300, 6505, 6510, 7800, 8000, VA-40FC, and Brocade Encryption Switch—On the switch ID pull-out tab located inside the chassis on the port side on the left •...
Page 86 lxxxvi Fabric OS Message Reference 53-1002448-01...
Page 87: In This Chapter
Chapter Introduction to System Messages In this chapter • Overview of system messages ........1 •...
Page 88: Audit Log Messages
Overview of system messages For information on displaying and clearing the RASLog messages, refer to “Displaying and clearing system message logs” on page 15. Audit log messages Event auditing is designed to support post-event audits and problem determination based on high-frequency events of certain types such as security violations, zoning configuration changes, firmware downloads, and certain types of fabric events.
Page 89: Message Severity Levels
Overview of system messages Event auditing is a configurable feature, set to off by default. You must enable event auditing using the auditCfg enable command to send the events to a configured remote host. Syslogd must be configured for logging audit messages. You can set up filters to screen out particular classes of events using the auditCfg command.
Page 90: System Error Message Logging
Configuring the syslog message destinations System error message logging The RASLog service generates and stores messages related to abnormal or erroneous system behavior. It includes the following features: • All RASLog error messages are saved to nonvolatile storage by default. •...
Page 91: System Console
Configuring the syslog message destinations For the Brocade DCX family of switches, any security violations that occur through Telnet, HTTP, or serial connections are not propagated between CPs. Security violations on the active CP are not propagated to the standby CP counters in the event of a failover, nor do security violations on the standby CP get propagated to the active CP counters.
Page 92: Snmp Management Station
Configuring the syslog message destinations 3. Execute the errFilterSet command to verify the configured filter settings. switch:admin> errfilterset console: filter severity = ERROR SNMP management station When an unusual event, error, or a status change occurs on the device, an event notification is sent to the SNMP management station.
Page 93: Port Logs
Configuring the SNMP server hosts SNMP informs An SNMP inform is similar to the SNMP trap except that the management station that receives an SNMP inform acknowledges the system message with an SNMP response packet data unit (PDU). If the sender does not receive the SNMP response PDU, the inform request can be sent again. An SNMP inform request is saved in the switch memory until a response is received or the request times out.
Page 94: Configuring The Snmpv3 Trap Recipient
Configuring the SNMP server hosts 3. Execute the snmpConfig show snmpv1 command to verify the SNMPv1 agent configuration. switch:admin> snmpconfig --show snmpv1 SNMPv1 community and trap recipient configuration: Community 1: Secret C0de (rw) Trap recipient: 10.24.32.122 Trap port: 162 Trap recipient Severity level: 5 Community 2: OrigEquipMfr (rw) Trap recipient: fec0:60:69bc:200:213:72ff:fe64:47b9 Trap port: 162...
Page 95 Configuring the SNMP server hosts Priv Protocol [DES(1)/noPriv(2)/3DES(3)/AES128(4)/AES192(5)/AES256(6)]): (2..2) [2] User (ro): [snmpuser2] Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3] Priv Protocol [DES(1)/noPriv(2)/3DES(3)/AES128(4)/AES192(5)/AES256(6)]): (2..2) [2] User (ro): [snmpuser3] Auth Protocol [MD5(1)/SHA(2)/noAuth(3)]: (1..3) [3] Priv Protocol [DES(1)/noPriv(2)/3DES(3)/AES128(4)/AES192(5)/AES256(6)]): (2..2) [2] SNMPv3 trap recipient configuration: Trap Recipient's IP address : [172.26.4.52] UserIndex: (1..6) [1] Trap recipient Severity level : (0..5) [1]...
Page 96: Configuring The Snmpv3 Inform Recipient
Configuring the SNMP server hosts Configuring the SNMPv3 inform recipient To configure the SNMPv3 host to receive the SNMP informs, perform the following steps. 1. Log in to the switch as admin. 2. Execute the snmpConfig set snmpv3 command to configure the inform recipient. When prompted to enable the SNMP informs, enter true or t.
Page 97: Changing The Severity Level Of Sweventtrap
Changing the severity level of swEventTrap Trap Recipient's IP address : [0.0.0.0] Trap Recipient's IP address : [0.0.0.0] Committing configuration..done. NOTE To receive the SNMP informs, the username, the authentication protocol, the privacy protocol, and the engine ID must match between the switch and the management station. 3.
Page 98 Changing the severity level of swEventTrap To change the severity level of swEventTrap, perform the following steps. 1. Log in to the switch as admin. 2. Execute the snmpConfig set mibCapability command to configure MIBs interactively. All the supported MIBs and associated traps are displayed. You can change the DesiredSeverity for swEventTrap to 1 (Critical), 2 (Error), 3 (Warning), or 4 (Informational).
Page 99: Commands For Displaying And Configuring The System Message Logs
Commands for displaying and configuring the system message logs bdClearTrap: YES FE-MIB (yes, y, no, n): [yes] SW-MIB (yes, y, no, n): [yes] FA-MIB (yes, y, no, n): [yes] FICON-MIB (yes, y, no, n): [yes] HA-MIB (yes, y, no, n): [yes] FCIP-MIB (yes, y, no, n): [yes] ISCSI-MIB (yes, y, no, n): [yes] IF-MIB (yes, y, no, n): [yes]...
Page 100 Commands for displaying and configuring the system message logs TABLE 3 Commands for viewing or configuring the system parameters and message logs Command Description auditCfg Configures the audit message log. auditDump Displays or clears the audit log. errClear Clears all error log messages for all switch instances on this control processor (CP). errDelimiterSet Sets the error log start and end delimiter for messages pushed to the console.
Page 101: Displaying And Clearing System Message Logs
Displaying and clearing system message logs TABLE 3 Commands for viewing or configuring the system parameters and message logs (Continued) Command Description syslogdFacility Changes the syslogd facility. syslogdIpAdd Adds an IP address as a recipient of system messages. syslogdIpRemove Removes an IP address as a recipient of system messages. syslogdIpShow Views the currently configured IP addresses that are recipients of system messages.
Page 102: Displaying Raslog Messages One Message At A Time
Displaying, clearing, and configuring Audit messages Displaying RASLog messages one message at a time To display the system message log one message at a time, perform the following steps. 1. Log in to the switch as admin. 2. Enter the errShow command at the command line. switch:admin>...
Page 103: Clearing The Audit Message Log
Displaying, clearing, and configuring Audit messages 0 AUDIT, 2011/01/14-06:06:49 (UTC), [RAS-2001], INFO, SYSTEM, admin/admin/10.70.4.102/telnet/CLI, ad_0/switch/FID 128, , Audit message log is enabled. 2 AUDIT, 2011/01/14-06:07:03 (UTC), [SEC-3020], INFO, SECURITY, admin/admin/10.70.4.102/telnet/CLI ad_0/switch, , Event: login, Status: success, Info: Successful login attempt via SERIAL. 3 AUDIT, 2011/01/14-06:07:33 (UTC), [SULB-1003], INFO, FIRMWARE, admin/admin/10.70.4.102/telnet/CLI ad_0/switch, , Firmwarecommit has started.
Page 104: Reading The System Messages
Reading the system messages You must configure the syslog daemon to send the Audit events to a configured remote host using the syslogdIpAdd command. For more information on configuring the syslog server, refer to “Configuring a syslog server” on page 5. Reading the system messages This section provides information about reading the RASLog and Audit messages.
Page 105: Reading An Audit Message
Reading the system messages TABLE 4 System message field description (Continued) Variable name Description Flags For most messages, this field contains a space character (null value) indicating that the message is neither an AUDIT or FFDC message. Messages may contain the following values: •...
Page 106 Reading the system messages TABLE 5 Audit message field description (Continued) Variable name Description Time Stamp The system time (UTC) when the message was generated on the switch. The RASLog subsystem will support an internationalized time stamp format based on the “LOCAL” setting. Event ID The message module and number.
Page 107: Responding To A System Message
Responding to a system message Responding to a system message This section provides procedures on gathering information on system messages. Looking up a system message Error messages in this manual are arranged alphabetically. To look up an error message, copy down the module (see Table 6 on page 23) and the error code and compare this with the Table of...
Page 108: Support
Responding to a system message Common steps to be followed when troubleshooting a system message are as follows. • Execute the errDump command on each logical switch. • Execute the supportFtp command (as needed) to set up automatic FTP transfers, and then execute the supportSave command.
Page 109: System Module Descriptions
System module descriptions System module descriptions Table 6 provides a summary of the system modules for which messages are documented in this guide; the system modules are listed alphabetically by name. TABLE 6 System module descriptions System Description module Access Gateway (AG) 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 110 System module descriptions TABLE 6 System module descriptions (Continued) System Description module DAUTH DAUTH error messages indicate problems with the 802.1x authentication module of the Fabric OS. Error Checking and Correction (ECC) error messages indicate single-bit and multiple-bit errors in the Dynamic Random Access Memory (DRAM) devices.
Page 111 System module descriptions TABLE 6 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 112 System module descriptions TABLE 6 System module descriptions (Continued) System Description module • KSWD Authentication daemon (authd) • (continued) Blade Manager daemon (bmd) • Common Access Layer daemon (cald) • Cluster Node Manager daemon (cnmd) • DAUTH daemon (dauthd) • Diagnostics daemon (diagd) •...
Page 113 System module descriptions TABLE 6 System module descriptions (Continued) System Description module • KSWD VS daemon (vsd) • (continued) Web linker daemon (weblinkerd) • Web Tools daemon (webd) • ZONE daemon (zoned) KTRC Kernel RAS trace module. L2SYS L2SYS error messages indicate problems with the Layer 2 System manager that controls the Layer 2 forwarding engine and controls the learning/aging/forwarding functionality.
Page 114 System module descriptions TABLE 6 System module descriptions (Continued) System Description module ONMD ONMD error messages indicate problems with the Operation, Administration and Maintenance module of the Fabric OS. Parity data manager (PDM) is a user-space daemon responsible for the replication of persistent configuration files from the primary partition to the secondary partition and from the active CP blade to the standby CP blade.
Page 115 System module descriptions TABLE 6 System module descriptions (Continued) System Description module SNMP Simple Network Management Protocol (SNMP) is a universally supported low-level protocol that allows simple get, get next, and set requests to go to the switch (acting as an SNMP agent). It also allows the switch to send traps to the defined and configured management station.
Page 116 System module descriptions TABLE 6 System module descriptions (Continued) System Description module XTUN XTUN messages are generated by the 7800/FX8-24 FCIP Tunnel implementation. These messages indicate status of FCIP tunnels, FCIP emulation events for FCP traffic, or FCIP debug information (FTRACE buffer status changes).
Page 117 Section RASLog Messages This section provides the RASLog messages, including: • AG System Messages ......... . . 35 •...
Page 118 • FCPD System Messages ........249 •...
Page 119 • MSTP System Messages ........515 •...
Page 120 • XTUN System Messages ........741 •...
Page 121: Ag-1001
Chapter AG System Messages AG-1001 Message <timestamp>, [AG-1001], <sequence-number>,, ERROR, <system-name>, N_Port ID virtualization (NPIV) is not supported by fabric port connected to port <port>. Probable Cause Indicates that the N_Port ID virtualization (NPIV) capability is not supported by the fabric port to which the Access Gateway is connected.
Page 122: Ag-1004
AG-1004 Recommended Configure two or more N_Ports to connect to the same fabric; then execute the ag --failoverenable Action command to enable failover on these N_Ports. 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 123: Ag-1007
AG-1007 AG-1007 Message <timestamp>, [AG-1007], <sequence-number>,, WARNING, <system-name>, FLOGI response not received for the N_Port <port> connected to the fabric. Probable Cause Indicates the N_Port connected to the fabric switch is not online. The specified N_Port has been disabled. Recommended Check the connectivity between the Access Gateway N_Port and the fabric switch port.
Page 124: Ag-1011
AG-1011 Recommended Check the configuration of the fabric switch connected to the Access Gateway. Action If the message persists, execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the supportSave command and contact your switch service provider. Severity WARNING AG-1011...
Page 125: Ag-1014
AG-1014 AG-1014 Message <timestamp>, [AG-1014], <sequence-number>,, INFO, <system-name>, Failing back F_Ports mapped to N_Port <port>. Probable Cause Indicates the specified N_Port is failing back F_Ports mapped to the specified N_Port. Recommended Execute the ag mapShow command to display updated F_Port- to-N_Port mapping. Action Severity INFO...
Page 126: Ag-1018
AG-1018 Recommended Execute the switchShow command to display the status of all ports in the system. Execute the Action portCfgShow command to display the list of ports currently configured as N_Ports. Severity WARNING AG-1018 Message <timestamp>, [AG-1018], <sequence-number>,, ERROR, <system-name>, Host port should not be connected to port <port>, which is configured as N_Port.
Page 127: Ag-1021
AG-1021 AG-1021 Message <timestamp>, [AG-1021], <sequence-number>,, WARNING, <system-name>, Unable to do Preferred-Failover of F_Port <port>. Failover across different fabric is not supported. Probable Cause Indicates that failover across N_Ports connected to different fabrics is not supported. Recommended Change the preferred N_Port settings for this F_Port using the ag prefset command.
Page 128: Ag-1025
AG-1025 Recommended Execute the ag mapShow command to display the updated F_Port-to-N_Port mapping. Action Severity INFO AG-1025 Message <timestamp>, [AG-1025], <sequence-number>,, ERROR, <system-name>, Port group of Slave N_Port <port> is different than its Master N_Port <m_port>. Probable Cause Indicates that the port groups of the Master and Slave N_Ports are different while the Trunk Area assigned to the attached F_Ports on the edge switch is the same.
Page 129: Ag-1028
AG-1028 AG-1028 Message <timestamp>, [AG-1028], <sequence-number>,, WARNING, <system-name>, Device with Port WWN <port_name> tried to perform fabric login through port <fport>, without having access permission. Probable Cause Indicates the device does not have login access for that port, as per Advanced Device Security (ADS) policy set by the user.
Page 130: Ag-1032
AG-1032 Recommended Check the device configuration. Action Severity WARNING AG-1032 Message <timestamp>, [AG-1032], <sequence-number>,, INFO, <system-name>, N_Port (ID: <port>) has recovered from an unreliable state. Probable Cause Indicates that the port state has been stable for the last five minutes. Recommended No action is required.
Page 131: Ag-1036
AG-1036 Recommended No action is required. Action Severity INFO AG-1036 Message <timestamp>, [AG-1036], <sequence-number>,, WARNING, <system-name>,Port <port> is connected to a Non-Brocade fabric with Persistent ALPA enabled. Check the admin guide for supported configuration. Probable Cause Indicates that one of the ports is connected to a non-Brocade fabric. Recommended No action is required.
Page 132: Ag-1039
AG-1039 AG-1039 Message <timestamp>, [AG-1039], <sequence-number>,, INFO, <system-name>, F_Port <Port that was reset> was reset because a WWN mapped device using it, through N_Port <Port who's state change caused the reset>, went offline. Probable Cause Indicates that a port needed to be reset because an N_Port went offline and the changes need to be propagated to all involved devices.
Page 133: An-1001
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 134: An-1004
AN-1004 AN-1004 Message <timestamp>, [AN-1004], <sequence-number>,, WARNING, <system-name>, Congestion bottleneck on port <slot number>/<port number within slot number>. <percentage of seconds affected by congestion bottlenecking> pct. of <observation period over which the percentage of affected seconds is reported> secs. affected. Probable Cause Indicates that the volume of outgoing traffic at this port is too high for the capacity of the link.
Page 135: An-1012
AN-1012 Recommended Contact your vendor's customer support for assistance. Action Severity WARNING AN-1012 Message <timestamp>, [AN-1012], <sequence-number>,, WARNING, <system-name>, Credits did not return from other end. Complete loss of credits on a VC on slot <slot number> port <port number within slot number>. Probable Cause Indicates a credit loss.
Page 136 AN-1013 Fabric OS Message Reference 53-1002448-01...
Page 137: Anv-1001
Chapter ANV System Messages ANV-1001 Message <timestamp>, [ANV-1001], <sequence-number>,, ERROR, <switch-name>, Port <port number> port fault. Change the SFP or check the cable. Probable Cause Indicates a deteriorated small form-factor pluggable (SFP), an incompatible SFP pair, or a faulty cable between the peer ports. Recommended Verify that compatible SFPs are used on the peer ports, the SFPs have not deteriorated, and the Action...
Page 138: Anv-1004
ANV-1004 ANV-1004 Message <timestamp>, [ANV-1004], <sequence-number>,, ERROR, <switch-name>, S<slot number>,C<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 ASIC hardware that may degrade the data traffic. Recommended Restart the system at the next maintenance window. If the problem persists, replace the faulted Action blade.
Page 139: Anv-1008
ANV-1008 ANV-1008 Message <timestamp>, [ANV-1008], <sequence-number>,, ERROR, <switch-name>, S<slot number>, C<chip index>: MAC-VID classifier table is full. No space for new entry. Probable Cause Indicates that the Media Access Control (MAC) VLAN ID (VID) classifier table is full and no more entries can be added.
Page 140 ANV-1016 Fabric OS Message Reference 53-1002448-01...
Page 141: Auth-1001
Chapter AUTH System Messages AUTH-1001 Message <timestamp>, [AUTH-1001], <sequence-number>,, INFO, <system-name>, <Operation type> has been successfully completed. Probable Cause Indicates that the secret database operation has been updated using the secAuthSecret command. The values for Operation type can be “set” or “remove”. Recommended No action is required.
Page 142: Auth-1004
AUTH-1004 AUTH-1004 Message <timestamp>, [AUTH-1004], <sequence-number>,, ERROR, <system-name>, Failed to set <data type> type to <setting value>. Probable Cause Indicates that the authUtil command has failed to set the authentication configuration value. The data type is either authentication type, DH group type, or policy type. Recommended Retry the authUtil command.
Page 143: Auth-1008
AUTH-1008 Recommended Run the authUtil command to make sure the local switch supports the specified protocols: Fibre Action channel authentication protocol (FCAP) or Diffie Hellman - challenge handshake authentication protocol (DH-CHAP). Severity ERROR AUTH-1008 Message <timestamp>, [AUTH-1008], <sequence-number>,, ERROR, <system-name>, No security license, operation failed.
Page 144: Auth-1012
AUTH-1012 AUTH-1012 Message <timestamp>, [AUTH-1012], <sequence-number>,, WARNING, <system-name>, Authentication <code> is rejected: port <port number> explain <explain code> reason <reason code>. Probable Cause Indicates that an authentication is rejected because the remote entity does not support authentication. Recommended Make sure the entity at the other end of the link supports authentication. Action Severity WARNING...
Page 145: Auth-1016
AUTH-1016 AUTH-1016 Message <timestamp>, [AUTH-1016], <sequence-number>,, ERROR, <system-name>, Invalid value to start HBA authentication port: <port number>, <pid>. 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.
Page 146: Auth-1022
AUTH-1022 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 147: Auth-1025
AUTH-1025 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-1025 Message <timestamp>, [AUTH-1025], <sequence-number>,, ERROR, <system-name>, Failed to get <data type>...
Page 148: Auth-1028
AUTH-1028 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; then run the supportSave command and contact your switch service provider. Severity ERROR AUTH-1028...
Page 149: Auth-1030
AUTH-1030 AUTH-1030 Message <timestamp>, [AUTH-1030], <sequence-number>,, ERROR, <system-name>, Invalid message code for <message phase> message: port <port number>. Probable Cause Indicates the receiving payload does not have valid message code for a particular authentication phase. Recommended Usually this problem is transient. The authentication might fail. Action Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands.
Page 150: Auth-1033
AUTH-1033 AUTH-1033 Message <timestamp>, [AUTH-1033], <sequence-number>,, ERROR, <system-name>, Disable port <port number> due to unauthorized switch <switch WWN value>. Probable Cause Indicates that an entity was not configured in the switch connection control (SCC) policy and tried to connect to the port. Recommended Add the entity's world wide name (WWN) to the SCC policy and reinitialize authentication by using Action...
Page 151: Auth-1036
AUTH-1036 AUTH-1036 Message <timestamp>, [AUTH-1036], <sequence-number>,, ERROR, <system-name>, Invalid state <state value> for <authentication phase>: port <port number>. Probable Cause Indicates that the switch received an unexpected authentication message. Recommended Usually this problem is transient. The authentication might fail. Action Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands.
Page 152: Auth-1039
AUTH-1039 AUTH-1039 Message <timestamp>, [AUTH-1039], <sequence-number>,, ERROR, <system-name>, Neighboring switch has conflicting authentication policy: Port <Port Number> disabled. Probable Cause Indicates that the neighboring switch has a conflicting authentication policy enabled. The_E-Port has been disabled, because the neighboring switch rejected the authentication negotiation, and the local switch has a strict switch authentication policy.
Page 153: Auth-1042
AUTH-1042 AUTH-1042 Message <timestamp>, [AUTH-1042], <sequence-number>,, ERROR, <system-name>, Port <port number> has been disabled, because authentication failed with code '<Reason String>' and explanation '<Explanation String>'. Probable Cause The specified port has been disabled, because the connecting switch/device failed to authenticate. The error might indicate that an invalid entity attempted to connect to the switch.
Page 154: Auth-1045
AUTH-1045 AUTH-1045 Message <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. Install the certificate and reinitialize Action authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands.
Page 155: Bksw-1003
Chapter BKSW System Messages BKSW-1003 Message <timestamp>, [BKSW-1003], <sequence-number>, FFDC, WARNING, <system-name>, kSWD: <Warning message>. Probable Cause Indicates a warning state within the system. A critical application error was reported in the watchdog subsystem. This message is used to convey information regarding the state of the system. Refer to the Warning message variable for specific information.
Page 156 BKSW-1003 Fabric OS Message Reference 53-1002448-01...
Page 157: Bl-1000
Chapter BL System Messages BL-1000 Message <timestamp>, [BL-1000], <sequence-number>,, INFO, <system-name>, Initializing ports... Probable Cause Indicates that the switch has started initializing the ports. Recommended No action is required. Action Severity INFO BL-1001 Message <timestamp>, [BL-1001], <sequence-number>,, INFO, <system-name>, Port initialization completed.
Page 158: Bl-1003
BL-1003 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 159: Bl-1007
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 160: Bl-1010
BL-1010 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). Recommended No action is required.
Page 161: Bl-1013
BL-1013 If the message persists, replace the blade or the (nonbladed) switch. Severity ERROR BL-1013 Message <timestamp>, [BL-1013], <sequence-number>,, ERROR, <system-name>, bport <port number> port is faulted. status=0x<interrupt status> Port <port number> will be re-enabled in 1 minute. Probable Cause Indicates that the port generated an excessive number of interrupts that might prove fatal to the switch operation.
Page 162: Bl-1015
BL-1015 BL-1015 Message <timestamp>, [BL-1015], <sequence-number>,, ERROR, <system-name>, bport <port number> port is faulted. status=0x<interrupt status>. Probable Cause Indicates that the port generated an excessive number of interrupts that might prove fatal to the switch operation. The port is disabled to prevent the CP from becoming too busy. The bport is the blade port;...
Page 163: Bl-1018
BL-1018 Recommended No action is required. Action Severity INFO BL-1018 Message <slot <timestamp>, [BL-1018], <sequence-number>,, INFO, <system-name>, Slot number> Initialization completed. Probable Cause Indicates that the slot has completed initializing the ports. Recommended No action is required. Action Severity INFO BL-1019 Message <timestamp>, [BL-1019], <sequence-number>,, INFO, <system-name>, Slot <Slot...
Page 164: Bl-1021
BL-1021 BL-1021 Message <timestamp>, [BL-1021], <sequence-number>,, INFO, <system-name>, Retry <Retry Number>, internal port retry initialization, <List of internal ports retrying initialization>. Probable Cause Indicates that the switch had internal ports not online and that the system is retrying to bring the ports that failed back online.
Page 165: Bl-1024
BL-1024 BL-1024 Message <timestamp>, [BL-1024], <sequence-number>,, INFO, <system-name>, All ports on the blade in slot <slot number> will be reset as part of the firmware upgrade. Probable Cause Indicates that a recent firmware upgrade caused the blade's firmware to be upgraded and resulted in the cold upgrade.
Page 166: Bl-1028
BL-1028 Recommended Restart or power cycle the blade. Action If the message persists, replace the blade. Severity CRITICAL BL-1028 Message <timestamp>, [BL-1028], <sequence-number>,, CRITICAL, <system-name>, Switch faulted; internal processor was reset before switch init completed. Probable Cause Indicates that the switch's internal processor was reset before the initialization completed. Recommended Restart or power cycle the switch.
Page 167: Bl-1031
BL-1031 BL-1031 Message <timestamp>, [BL-1031], <sequence-number>,, CRITICAL, <system-name>, Link timeout in internal port (slot <Slot number>, port <Port number>) resulted in blade fault. Use slotpoweroff/slotpoweron to recover the blade. Probable Cause Indicates that link timeout occurred in one of the backend internal ports. Recommended Power cycle the blade or run the slotPowerOff and slotPowerOn commands.
Page 168: Bl-1035
BL-1035 Recommended No action is required. Action Severity INFO BL-1035 Message <timestamp>, [BL-1035], <sequence-number>,, INFO, <system-name>, Slot <slot number> iSCSI port <iscsi port number> Initialization completed. Probable Cause Indicates that the slot has completed initializing the specified iSCSI port. Recommended No action is required.
Page 169: Bl-1039
BL-1039 Recommended Restart the switch. If the message persists, replace the switch. Action Severity CRITICAL BL-1039 Message <timestamp>, [BL-1039], <sequence-number>,, CRITICAL, <system-name>, Inconsistent FPGA image version detected, faulting the blade in slot <slot number>. Probable Cause Indicates that the FPGA image version is incompatible with the software version. Recommended Power cycle the blade.
Page 170: Bl-1046
BL-1046 BL-1046 Message <timestamp>, [BL-1046], <sequence-number>,, ERROR, <system-name>, <Slot number of blade that has the SFP> error on SFP in Slot <Port number into which the SFP is inserted>/Port <The type of error "checksum" or "data access" for general problems accessing the i2c accessible data>...
Page 171: Bl-1050
BL-1050 Recommended No action is required. Action Severity INFO BL-1050 Message <timestamp>, [BL-1050], <sequence-number>,, WARNING, <system-name>, Incompatible Blade Processor FPGA version with FOS7.0 firmware in slot=<slot number> on FX8-24. Contact support for upgrade instructions. Probable Cause Indicates that the blade processor FPGA version with Fabric OS v7.0.0 firmware in the specified slot is incompatible on FX8-24 blade.
Page 172 BL-1051 Fabric OS Message Reference 53-1002448-01...
Page 173: Bll-1000
Chapter BLL System Messages BLL-1000 Message <timestamp>, [BLL-1000], <sequence-number>, FFDC, CRITICAL, <system-name>, ASIC driver detected Slot <slot number> port <port number> as faulty (reason: <reason>). Probable Cause Indicates that a blade regulation problem was reported on the specified slot. The blade is faulted. The possible reason codes are as follows: •...
Page 174 BLL-1000 Execute the diagPost command to make sure that Power-On Self-Test (POST) is enabled; then power cycle the blade using the slotPowerOff and slotPowerOn commands or have the blade's ejector switch cycled to run POST and verify that the blade does not have any hardware problems. Severity CRITICAL Fabric OS Message Reference...
Page 175: Bls-1000
Chapter BLS System Messages BLS-1000 Message <timestamp>, [BLS-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 176: Bls-1003
BLS-1003 BLS-1003 Message <timestamp>, [BLS-1003], <sequence-number>, INFO, <system-name>, An IPsec/IKE policy was deleted. 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 177: Bm-1001
Chapter BM System Messages BM-1001 Message <timestamp>, [BM-1001], <sequence-number>,, ERROR, <system-name>, BM protocol version <Protocol version> in slot <Slot number>. Probable Cause Indicates that the 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 178: Bm-1004
BM-1004 Recommended Use the slotPowerOff and slotPowerOn commands or reseat the affected blade. Action Severity WARNING BM-1004 Message <timestamp>, [BM-1004], <sequence-number>,, INFO, <system-name>, Blade firmware <Blade firmware> on slot <Slot> is not consistent with system firmware <System firmware>. Auto-leveling blade firmware to match system firmware. Probable Cause Indicates the policy of the specified blade is to auto-level the blade firmware to the system firmware.
Page 179: Bm-1007
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 180: Bm-1053
BM-1053 Recommended No action is required. The blade ports are cleared automatically. Action Severity INFO BM-1053 Message <timestamp>, [BM-1053], <sequence-number>, FFDC, 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.
Page 181: Bm-1056
BM-1056 BM-1056 Message <timestamp>, [BM-1056], <sequence-number>,, INFO, <system-name>, AP is not configured. Persistently disabling all ports on the switch. Probable Cause Indicates the policy of the specified switch is to persistently disable all ports the first time the AP is detected.
Page 182 BM-1058 Fabric OS Message Reference 53-1002448-01...
Page 183: 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 184: C2-1006
C2-1006 C2-1006 Message Message <timestamp>, [C2-1006], <sequence-number>,, WARNING, <system-name>, S<slot number>,C<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 185: C2-1009
C2-1009 C2-1009 Message Message <timestamp>, [C2-1009], <sequence-number>,, WARNING, <system-name>, S<slot number>,P<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 186: C2-1013
C2-1013 C2-1013 Message Message <timestamp>, [C2-1013], <sequence-number>,, WARNING, <system-name>, S<slot number>,P<port number>(<blade port number>): Duplicate rte_tbl_select detected! Probable Cause Indicates that the selected table is corrupted. Recommended This message must have a matching message for the other duplicate. Reset both the specified Action ports.
Page 187: C2-1017
C2-1017 Recommended Whenever this error is observed persistently, power cycle the specified blade. If the problem Action persists, replace the blade. Severity ERROR C2-1017 Message Message <timestamp>, [C2-1017], <sequence-number>,, ERROR, <system-name>, Blade in Slot <slot number> failed due to unavailability of ports in the internal trunk. Probable Cause Indicates that the blade failed due to unavailability of the ports in the internal trunk.
Page 188 C2-1019 Fabric OS Message Reference 53-1002448-01...
Page 189: C3-1001
Chapter C3 System Messages C3-1001 Message <timestamp>, [C3-1001], <sequence-number>,, ERROR, <system-name>, Port <port number> failed due to SFP validation failure. Check if the SFP is valid for the configuration. Probable Cause Indicates a deteriorated small form-factor pluggable (SFP), an incompatible SFP pair, or a faulty cable between the peer ports.
Page 190: C3-1006
C3-1006 C3-1006 Message <timestamp>, [C3-1006], <sequence-number>,, WARNING, <system-name>, S<slot number>,C<chip index>: Various non critical hardware errors were observed: fault1:0x<fault1_cnt>, fault2:0x<fault2_cnt> thresh1:0x<threshold_used>. Probable Cause Indicates some errors found in hardware that may or may not impact data traffic. Recommended No action is required. Action Severity WARNING...
Page 191: C3-1010
C3-1010 Recommended No action is required. Action Severity WARNING C3-1010 Message <timestamp>, [C3-1010], <sequence-number>,, CRITICAL, <system-name>, S<slot number>,C<chip index>: Above normal hardware errors were observed: fault1:<fault1_cnt>, fault2:<fault2_cnt> thresh2:0x<threshold_used>. Probable Cause Indicates above normal errors observed in hardware that may or may not impact data traffic. Recommended Whenever this error is observed persistently, power cycle the specified blade.
Page 192: C3-1013
C3-1013 C3-1013 Message <timestamp>, [C3-1013], <sequence-number>,, INFO, <system-name>, Maximum wait cycles to recover the lost frame or credit is exceeded on the internal Port Slot <slot number>,P<port number>(<blade port number>) m_rdy(0x<Multiple Credit(s) Lost>)/m_frame(0x<Multiple Frame(s) Lost>). Probable Cause Indicates that wait cycles to recover the lost frame or credit is exceeded on the specified port. Recommended Turn on the back-end credit recovery to reset the link and recover the lost credits.
Page 193: C3-1017
C3-1017 Recommended Whenever this error is observed persistently, power cycle the specified blade. If the problem Action persists, replace the blade. Severity ERROR C3-1017 Message <timestamp>, [C3-1017], <sequence-number>,, ERROR, <system-name>, Blade in Slot <slot number> failed due to unavailability of ports in the internal trunk. Probable Cause Indicates that the blade failed due to unavailability of the ports in the internal trunk.
Page 194: C3-1021
C3-1021 Recommended No action is required. Action Severity WARNING C3-1021 Message <timestamp>, [C3-1021], <sequence-number>,, WARNING, <system-name>, S<slot number>,P<port number>(<blade port number>): Port offline due to Encryption Compression Block error. Probable Cause Indicates that an internal error is observed in the ASIC hardware that may degrade the data traffic. Recommended Whenever this error occurs, software recovers from the error.
Page 195: Cal-1001
Chapter CAL System Messages CAL-1001 Message <timestamp>, [CAL-1001], <sequence-number>,, INFO, <system-name>, Switch offline requested by remote domain <domain number>. Probable Cause Indicates a remote domain has requested the local domain to be disabled. Recommended See remote domain raslogs for the reason. Action Severity INFO...
Page 196 CAL-1001 Fabric OS Message Reference 53-1002448-01...
Page 197: Ccfg-1001
Chapter CCFG System Messages CCFG-1001 Message <timestamp>, [CCFG-1001], <sequence-number>,, ERROR, <system-name>, Failed to initialize <module>, rc = <error>. Probable Cause Indicates that the 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. Action Severity ERROR...
Page 198: Ccfg-1004
CCFG-1004 CCFG-1004 Message <timestamp>, [CCFG-1004], <sequence-number>,, ERROR, <system-name>, Configuration replay failed due to missing system startup configuration file. Probable Cause Indicates that the startup configuration file has been moved or deleted and therefore replaying the system configuration has failed. Recommended Execute the copy file startup-config command to restore the startup configuration from any backup Action retrieved on the server.
Page 199: Ccfg-1008
CCFG-1008 CCFG-1008 Message <timestamp>, [CCFG-1008], <sequence-number>,, ERROR, <system-name>, CMSH init failed: <msg>. Probable Cause Indicates that CEE Management Shell (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 a configuration file has been copied to the specified destination.
Page 200: Ccfg-1012
CCFG-1012 CCFG-1012 Message <timestamp>, [CCFG-1012], <sequence-number>,, ERROR, <system-name>, Blade in slot <slot> failed to reach ONLINE state within <timeout> seconds after receiving system ready. Probable Cause Indicates that the blade in the specified slot has failed to come online within the specified timeout interval after receiving the system ready event.
Page 201: Cdr-1001
Chapter CDR System Messages CDR-1001 Message <timestamp>, [CDR-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, 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 202: Cdr-1004
CDR-1004 CDR-1004 Message <timestamp>, [CDR-1004], <sequence-number>, ERROR, <system-name>, S<slot number>, C<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 Whenever this error occurs, restart the system at the next maintenance window.
Page 203: Cdr-1008
CDR-1008 Recommended No action is required. Action Severity WARNING CDR-1008 Message <timestamp>, [CDR-1008], <sequence-number>,, WARNING, <system-name>, S<slot number>,C<chip index>: HW ASIC Chip warning Level 1 type = 0x<chip error type>. Probable Cause Indicates an internal error in the ASIC hardware that may or may not degrade data traffic. Recommended Whenever this error occurs, restart the system at the next maintenance window.
Page 204: Cdr-1011
CDR-1011 CDR-1011 Message <timestamp>, [CDR-1011], <sequence-number>,, WARNING, <system-name>, S<slot number>,P<port number>(<blade port number>): Link Timeout on internal port ftx=<frame transmitted> tov=<real timeout value>(><expected timeout value>) vc_no=<vc number> crd(s)lost=<Credit(s) lost> complete_loss:<complete credit loss>. Probable Cause Indicates that one or more credits have been lost on a back-end port, and there is no traffic on that port for two seconds.
Page 205: Cdr-1016
CDR-1016 Recommended Whenever this error is observed persistently, power cycle the specified blade. If the problem Action persists, replace the blade. Severity WARNING CDR-1016 Message <timestamp>, [CDR-1016], <sequence-number>,, ERROR, <system-name>, Port is faulted due to port re-initialization failure on internal Port S<slot number>,P<port number>(<blade port number>) with reason <port fault reason>.
Page 206 CDR-1019 Recommended Whenever this error occurs, restart the system at the next maintenance window. Action Severity WARNING Fabric OS Message Reference 53-1002448-01...
Page 207: Cer-1001
Chapter CER System Messages CER-1001 Message <timestamp>, [CER-1001], <sequence-number>,, ERROR, <system-name>, HA Sync broken, since standby Advanced Performance Tuning module does not support FICON Management Server (FMS). Probable Cause Indicates that the high-availability (HA) synchronization between the active and standby control processors (CPs) is broken, because there is downlevel firmware loaded on the standby CP.
Page 208 CER-1001 Fabric OS Message Reference 53-1002448-01...
Page 209: Chs-1002
Chapter CHS System Messages CHS-1002 Message <timestamp>, [CHS-1002], <sequence-number>, FFDC, 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 210: Chs-1005
CHS-1005 CHS-1005 Message <timestamp>, [CHS-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 211: Cnm-1001
Chapter CNM System Messages CNM-1001 Message <timestamp>, [CNM-1001], <sequence-number>,, ERROR, <system-name>, Failed to allocate memory: (<function name>). Probable Cause Indicates that the specified function failed to allocate memory. Recommended Check memory usage on the switch using the memShow command. Restart or power cycle the Action switch.
Page 212: Cnm-1004
CNM-1004 CNM-1004 Message <timestamp>, [CNM-1004], <sequence-number>,, INFO, <system-name>, iSCSI service is <status> on the switch. 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>].
Page 213: Cnm-1008
CNM-1008 CNM-1008 Message <timestamp>, [CNM-1008], <sequence-number>,, INFO, <system-name>, Posting event CNM_EVT_NODE_EJECT nodeName [<nodeName>], wwn [<wwn>]. Probable Cause Indicates that the node is ejected from the Encryption Group (EG). 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.
Page 214: Cnm-1012
CNM-1012 CNM-1012 Message <timestamp>, [CNM-1012], <sequence-number>,, INFO, <system-name>, Posting event CNM_EVT_EG_DELETED. Probable Cause Indicates that the Encryption Group (EG) is deleted. 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.
Page 215: Cnm-1016
CNM-1016 CNM-1016 Message <timestamp>, [CNM-1016], <sequence-number>,, INFO, <system-name>,Posting event Detected a EG degrade condition. Probable Cause Indicates an Encryption Group (EG) degrade condition. 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>].
Page 216: Cnm-1020
CNM-1020 CNM-1020 Message <timestamp>, [CNM-1020], <sequence-number>,, INFO, <system-name>, Node Admission Control failed, due to mismatch in certificates, rejecting node [<nodename>]. 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.
Page 217: Cnm-1024
CNM-1024 CNM-1024 Message <timestamp>, [CNM-1024], <sequence-number>,, INFO, <system-name>, Operation not required on GL node. 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.
Page 218: Cnm-1028
CNM-1028 CNM-1028 Message <timestamp>, [CNM-1028], <sequence-number>,, INFO, <system-name>, Certfile <cfname> already exists. No need to sync up. 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>...
Page 219: Cnm-1032
CNM-1032 CNM-1032 Message <timestamp>, [CNM-1032], <sequence-number>,, WARNING, <system-name>, Certfile <cfname> size <fsize> does not match cert file size <len> sent by GL Probable Cause Indicates that there is a size mismatch between a node's certificate file and the certificate file received from the group leader.
Page 220: Cnm-1036
CNM-1036 CNM-1036 Message <timestamp>, [CNM-1036], <sequence-number>,, INFO, <system-name>, All the active nodes of the cluster are in ONLINE state. Posting converged event. Probable Cause Indicates an event is being posted to indicate that the cluster is in a converged state. Recommended No action is required.
Page 221: Cnm-1040
CNM-1040 CNM-1040 Message <timestamp>, [CNM-1040], <sequence-number>,, INFO, <system-name>, Split-Brain Arbitration won, Majority WWN/GL Node, remote_wwn:local_wwn <wwn>. Probable Cause Indicates that split arbitration is won. 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.
Page 222: Cnm-1044
CNM-1044 CNM-1044 Message <timestamp>, [CNM-1044], <sequence-number>,, ERROR, <system-name>, Cluster Create Failed as the Certificate files not found, Please do the initnode. Probable Cause Indicates that the initnode is not invoked. 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.
Page 223: Cnm-1048
CNM-1048 CNM-1048 Message <timestamp>, [CNM-1048], <sequence-number>,, INFO, <system-name>, Posting <string>. Probable Cause Indicates the event that is posted. 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.
Page 224: Cnm-1052
CNM-1052 CNM-1052 Message <timestamp>, [CNM-1052], <sequence-number>,, ERROR, <system-name>, Member node registered with another Encryption Group. To proceed eject the member node <nodename> from other EG. Probable Cause Indicates that the member node is registered with another Encryption Group (EG). Recommended No action is required.
Page 225: Cnm-1056
CNM-1056 CNM-1056 Message <timestamp>, [CNM-1056], <sequence-number>,, INFO, <system-name>, Posting event CNM_EVT_EE_INITIALIZING Slot [<slot>], Wwn [<wwn>], IP [<ip>], flags [<flags>]. Probable Cause Indicates that the Encryption Engine (EE) is added into the Encryption Group (EG). Recommended No action is required. Action Severity INFO CNM-1057...
Page 226: Cnm-1060
CNM-1060 CNM-1060 Message <timestamp>, [CNM-1060], <sequence-number>,, INFO, <system-name>, Local Node CP certificate pair mismatch detected. Probable Cause Indicates that the certificate pair is matched. 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>].
Page 227: Cnm-3002
CNM-3002 CNM-3002 Message <timestamp>, [CNM-3002], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: encryption group deleted. Probable Cause Indicates an encryption group was deleted. 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.
Page 228: Cnm-3006
CNM-3006 CNM-3006 Message <timestamp>, [CNM-3006], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: Heartbeat miss count set to <hbmisses>. Probable Cause Indicates that the heartbeat miss value was set. 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>.
Page 229: Cnm-3010
CNM-3010 CNM-3010 Message <timestamp>, [CNM-3010],<sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: Membernode <membernodeWWN> unregistered. Probable Cause Indicates a membernode was unregistered. 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.
Page 230 CNM-3012 Fabric OS Message Reference 53-1002448-01...
Page 231: Conf-1000
Chapter CONF System Messages CONF-1000 Message <timestamp>, [CONF-1000], <sequence-number>, , 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 Info about the parameters and AD variable is the description of the classes of configuration parameters that were downloaded.
Page 232: Conf-1021
CONF-1021 CONF-1021 Message <timestamp>, [CONF-1021], <sequence-number>,, INFO, <system-name>, configUpload not permitted <AD Number if AD is configured on the system>. Probable Cause Indicates a configUpload operation is not permitted. There are many possible causes. Recommended Execute the errShow command to view the error log. Correct the error and execute the Action configUpload command again.
Page 233: Conf-1030
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 234: Conf-1041
CONF-1041 CONF-1041 Message <timestamp>, [CONF-1041], <sequence-number>,, INFO, <system-name>, configRemove failed. <Message>. Probable Cause Indicates that an error occurred while executing the configRemove command. Recommended Execute the errShow command to view the error log. Correct the error and execute the Action configRemove command again.
Page 235: Ctap-1001
Chapter CTAP System Messages CTAP-1001 Message <timestamp>, [CTAP-1001], <sequence-number>,, INFO, <system-name>, Key acquisition for <Pool or Container> <Begins or Complete>. Probable Cause Indicates that a change in the tape pool database has triggered the key acquisition process for each pool. Recommended Do not start tape backup or restore operations involving tape pools until the process is complete.
Page 236 CTAP-1001 Fabric OS Message Reference 53-1002448-01...
Page 237: Cvlc-1001
Chapter CVLC System Messages CVLC-1001 Message <timestamp>, [CVLC-1001], <sequence-number>,, INFO, <system-name>, <Re-key type (First time encryption/Key expired/Manual)> re-key <Re-key action (started/completed/failed/cancelled)>, LUN SN: <LUN serial number>. Container: <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.
Page 238: Cvlc-1004
CVLC-1004 CVLC-1004 Message <timestamp>, [CVLC-1004], <sequence-number>,, INFO, <system-name>, Forceful encryption LUN removal while re-key session is still active. Container: <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 239: Cvlc-1008
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 240: Cvlc-1011
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. Container: <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 241: Cvlc-1014
CVLC-1014 CVLC-1014 Message <timestamp>, [CVLC-1014], <sequence-number>,, ERROR, <system-name>, Missing Key ID from user input. Container: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Probable Cause Indicates that the data state in the LUN configuration is in the encrypted state without a key ID and there is no metadata found on the LUN.
Page 242: Cvlc-1018
CVLC-1018 Recommended No action is required. Action Severity ERROR CVLC-1018 Message <timestamp>, [CVLC-1018], <sequence-number>,, INFO, <system-name>, Event: <Description of the event>. Container: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Probable Cause Indicates an informational event. Recommended No action is required.
Page 243: Cvlc-1021
CVLC-1021 CVLC-1021 Message <timestamp>, [CVLC-1021], <sequence-number>,, INFO, <system-name>, User provided key ID <Key ID provided by the user> is ignored while metadata <Key ID from metadata> exists. Container: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Probable Cause Indicates that the key ID provided is ignored because metadata exists on the LUN.
Page 244: Cvlc-1025
CVLC-1025 Recommended No action is required. Action Severity INFO CVLC-1025 Message <timestamp>, [CVLC-1025], <sequence-number>,, ERROR, <system-name>, Secondary Metadata exists for encrypted LUN not configured with -newLUN option . Container: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Probable Cause Indicates that the secondary metadata exists on the LUN that is not configured with newLUN...
Page 245: Cvlc-1028
CVLC-1028 CVLC-1028 Message <timestamp>, [CVLC-1028], <sequence-number>,, WARNING, <system-name>, Not starting auto rekey on LUN with uncompressible blocks 1-16. Container: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Probable Cause Indicates a warning event. Recommended Perform a manual rekey on this LUN. Action Severity WARNING...
Page 246: Cvlc-1031
CVLC-1031 CVLC-1031 Message <timestamp>, [CVLC-1031], <sequence-number>,, WARNING, <system-name>, Primary LUN is restored from mirror LUN. LUN in read-only mode. Container: <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Probable Cause Indicates a rekeyed primary LUN may have been restored from mirror LUN without synchronizing. Recommended 1.
Page 247: Cvlc-1035
CVLC-1035 Recommended No action is required. Action Severity INFO CVLC-1035 Message <timestamp>, [CVLC-1035], <sequence-number>,, ERROR, <system-name>, A decommissioned LUN has been added back as encrypted LUN. Container <Target container name>, Initiator: <Initiator physical WWN>, LUN ID: <LUN ID>. Probable Cause Indicates that decommissioned LUN has been added back as encrypted LUN.
Page 248 CVLC-1041 Fabric OS Message Reference 53-1002448-01...
Page 249: Cvlm-1001
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 250: Cvlm-1004
CVLM-1004 CVLM-1004 Message <timestamp>, [CVLM-1004], <sequence-number>,, WARNING, <system-name>, Crypto device configuration between local switch (<local switch WWN>) and peer (<peer switch WWN>) is out of sync. New encryption session is not allowed. 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.
Page 251: Cvlm-1008
CVLM-1008 CVLM-1008 Message <timestamp>, [CVLM-1008], <sequence-number>,, WARNING, <system-name>, The member (<EE node WWN><EE slot num>) of HAC (<HAC name>) is not in the fabric. Probable Cause Indicates that the member of HAC is not in the fabric. Recommended Check the ISL port connected to the fabric. Action Severity WARNING...
Page 252: Cvlm-1012
CVLM-1012 CVLM-1012 Message <timestamp>, [CVLM-1012], <sequence-number>,, INFO, <system-name>, The HAC failback occurs at EE (<EE node WWN> <EE slot num>). Probable Cause Indicates that the HAC failback occurs at the EE. 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>.
Page 253: Cvlm-3004
CVLM-3004 CVLM-3004 Message <timestamp>, [CVLM-3004], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: Cluster member added to HA cluster <HAClusterName>. Probable Cause Indicates an HA cluster member was added to an HA cluster. Recommended No action is required. Action Severity INFO CVLM-3005 Message...
Page 254: Cvlm-3008
CVLM-3008 Recommended No action is required. Action Severity INFO CVLM-3008 Message <timestamp>, [CVLM-3008],<sequence-number>,, INFO, <system-name>, 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 <timestamp>, [CVLM-3009], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: Manual failback from EE...
Page 255: Cvlm-3012
CVLM-3012 Recommended No action is required. Action Severity INFO CVLM-3012 Message <timestamp>, [CVLM-3012],<sequence-number>,, INFO, <system-name>, 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 256: Cvlm-3015
CVLM-3015 CVLM-3015 Message <timestamp>, [CVLM-3015], <sequence-number>,, INFO, <system-name>, 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. Action Severity INFO...
Page 257: Cvlm-3019
CVLM-3019 CVLM-3019 Message <timestamp>, [CVLM-3019], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: Tape pool \<tapepoolLabelOrNum>\ modified. Probable Cause Indicates a tapepool was modified. Recommended No action is required. Action Severity INFO CVLM-3020 Message <timestamp>, [CVLM-3020], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: Manual rekey of LUN <LUNSpec>...
Page 258: Cvlm-3023
CVLM-3023 CVLM-3023 Message <timestamp>, [CVLM-3023], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: Transaction committed. Probable Cause Indicates a transaction commit operation was performed. Recommended No action is required. Action Severity INFO CVLM-3024 Message <timestamp>, [CVLM-3024], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: Transaction <transactionID>...
Page 259: Cvlm-3027
CVLM-3027 CVLM-3027 Message <timestamp>, [CVLM-3027], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: Decommission of device (container <cryptoTargetContainer> initiator <Initiator>, LUN <Lun>). Probable Cause Indicates that the decommission operation has been completed for the device. Recommended No action is required. Action Severity INFO...
Page 260 CVLM-3028 Fabric OS Message Reference 53-1002448-01...
Page 261: Dot1-1001
Chapter DAUTH System Messages DOT1-1001 Message <timestamp>, [DOT1-1001], <sequence-number>,, INFO, 802.1X is enabled globally. Probable Cause Indicates that 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 802.1X is disabled globally.
Page 262: Dot1-1005
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 authentication has succeeded on the specified port. Recommended No action is required. Action Severity INFO DOT1-1006 Message...
Page 263: Dot1-1009
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 802.1X is disabled for a specified port. Recommended No action is required. Action Severity INFO DOT1-1010 Message <timestamp>, [DOT1-1010], <sequence-number>,, INFO, Port <port_name>...
Page 264 DOT1-1010 Fabric OS Message Reference 53-1002448-01...
Page 265: Ecc-1000
Chapter ECC System Messages ECC-1000 Message <timestamp>, [ECC-1000], <sequence-number>,, ERROR, <system-name>, ECC Error <Multiple or single occurrence of errors of a given type detected> occurrence of <Automatic calibration error detected> <Multiple bit error detected> <Single bit error detected><Memory select error detected>. Probable Cause Indicates that the processor memory controller has detected one of several types of DDR memory errors.
Page 266 ECC-1001 Fabric OS Message Reference 53-1002448-01...
Page 267: Em-1001
Chapter EM System Messages EM-1001 Message <timestamp>, [EM-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, <FRU ID> is overheating: Shutting down. Probable Cause Indicates that the specified field-replaceable unit (FRU) is shutting down due to overheating. This event is typically due to a faulty fan and can also be caused by the switch environment. Recommended Verify that the location temperature is within the operational range of the switch.
Page 268: Em-1004
EM-1004 Execute the diagPost command to make sure that Power-On Self-Test (POST) is enabled; then power cycle the blade using the slotPowerOff and slotPowerOn commands or have the blade's ejector switch cycled to run POST and verify that the blade does not have any hardware problems. On the Brocade 24000 and 48000, replace the specified FRU.
Page 269: Em-1006
EM-1006 EM-1006 Message <timestamp>, [EM-1006], <sequence-number>, FFDC, CRITICAL, <system-name>, <FRU 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 270: Em-1009
EM-1009 EM-1009 Message <timestamp>, [EM-1009], <sequence-number>, FFDC, CRITICAL, <system-name>, <FRU 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 may indicate a hardware malfunction in the FRU.
Page 271: Em-1013
EM-1013 Recommended Reseat the specified field-replaceable unit (FRU). Action If the problem persists, restart or power cycle the switch. Execute the diagPost command to make sure that Power-On Self-Test (POST) is enabled; then power cycle the blade using the slotPowerOff and slotPowerOn commands or have the blade's ejector switch cycled to run POST and verify that the blade does not have any hardware problems.
Page 272: Em-1016
EM-1016 EM-1016 Message <timestamp>, [EM-1016], <sequence-number>,, WARNING, <system-name>, Cold recovery failed (<Return code>). Probable Cause Indicates that a problem was discovered when performing consistency checks during a cold boot. Recommended Monitor the switch. Action If the problem persists, execute the supportFtp command (as needed) to set up automatic FTP transfers;...
Page 273: Em-1028
EM-1028 Recommended Execute the fosconfig enable ethsw command to allow the blade to be up. Note that this is a Action disruptive command, which requires the system to be restarted. Otherwise, remove the blade. Severity ERROR EM-1028 Message <timestamp>, [EM-1028], <sequence-number>, FFDC, WARNING, <system-name>, HIL Error: <function>...
Page 274: Em-1033
EM-1033 Recommended Close the ejector switch (raise the slider in most blades, or completely screw in the upper Action thumbscrew for the FC4-48 port blade) if the field-replaceable unit (FRU) is intended for use. Refer to the appropriate Hardware Refernce Manual for instructions on inserting the switch blades. Severity ERROR EM-1033...
Page 275: Em-1035
EM-1035 EM-1035 Message <timestamp>, [EM-1035], <sequence-number>,, ERROR, <system-name>, 2 circuit paired Power Supplies are faulty, please check the <Switch side> AC main switch/circuit to see if it has power. Probable Cause Indicates that both power supplies associated with one of the two main circuits are present but faulty, may be the circuit's switch has been turned off, or the AC power source has been interrupted for that circuit.
Page 276: Em-1042
EM-1042 Recommended No action is required. Action Severity INFO EM-1042 Message <timestamp>, [EM-1042], <sequence-number>,, WARNING, <system-name>, Important FRU header data for <FRU Id> is not valid). Probable Cause Indicates that the specified field-replaceable unit (FRU) has an incorrect number of sensors in its FRU header-derived information.
Page 277: Em-1045
EM-1045 EM-1045 Message <timestamp>, [EM-1045], <sequence-number>,, WARNING, <system-name>, <FRU Id> is being powered <new state>. Probable Cause Indicates that an automatic power adjustment is being made because of the (predicted) failure of a power supply or the insertion or removal of a port blade. The new state value can be one of the following: •...
Page 278: Em-1048
EM-1048 Recommended No action is required. Action Severity INFO EM-1048 Message <timestamp>, [EM-1048], <sequence-number>,, INFO, <system-name>, <FRU Id> I2C access recovered: state <current state> Probable Cause Indicates that the Inter-Integrated Circuit (I2C) bus problems have been resolved and I2C access to the field-replaceable unit (FRU) has become available again.
Page 279: Em-1051
EM-1051 EM-1051 Message <timestamp>, [EM-1051], <sequence-number>,, INFO, <system-name>, <FRU Id>: Inconsistency detected, FRU reinitialized. 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 the traffic may have been disrupted.
Page 280: Em-1059
EM-1059 EM-1059 Message <timestamp>, [EM-1059], <sequence-number>, FFDC, ERROR, <system-name>, <Slot number or Switch> with ID <Blade Id> may not be supported on this platform, check FOS firmware version as a possible cause. Probable Cause Indicates that a blade inserted in the specified slot or the switch (for nonbladed switches) is incompatible with the switch configuration software.
Page 281: Em-1062
EM-1062 EM-1062 Message <timestamp>, [EM-1062], <sequence-number>,, CRITICAL, <system-name>, Blade in slot <Slot Id> faulted as it exceeds the maximum support limit of <Limit> blades with Blade ID <Blade Type Id> in the chassis. Probable Cause Indicates that too many blades of a particular type are in the system. Recommended Remove the faulted blade.
Page 282: Em-1066
EM-1066 Recommended Upgrade the Fabric OS firmware or the SAS firmware using the firmwareDownload command. Refer Action to the release notes for a compatible version of firmware. Severity WARNING EM-1066 Message <timestamp>, [EM-1066], <sequence-number>,, INFO, <system-name>, SAS Virtualization Services are now available <Slot number or blank for single board systems>.
Page 283: Em-1069
EM-1069 Recommended Restart or power cycle the switch. Action If the problem persists, execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the supportSave command and contact your switch service provider. Severity ERROR EM-1069 Message <timestamp>, [EM-1069], <sequence-number>,, INFO, <system-name>, Slot <FRU slot number>...
Page 284: Em-2003
EM-2003 EM-2003 Message <timestamp>, [EM-2003], <sequence-number>,, ERROR, <system-name>, <Slot Id or Switch for pizza boxes> has failed the POST tests. FRU is being faulted. Probable Cause Indicates that a field-replaceable unit (FRU) has failed the Power-On Self-Test (POST). Refer to the /tmp/post[1/2].slot#.log file for more information on the faults.
Page 285: Ess-1001
Chapter ESS System Messages ESS-1001 Message <timestamp>, [ESS-1001], <sequence-number>,, WARNING, <system-name>, A few switches in the fabric do not support the Coordinated HotCode protocol. Probable Cause Indicates one or more switches in the fabric do not support the Coordinated HotCode protocol. Continuing with the firmware download may cause data traffic disruption.
Page 286: Ess-1004
ESS-1004 ESS-1004 Message <timestamp>, [ESS-1004], <sequence-number>,, WARNING, <system-name>, The resume message is rejected by the domain <domain id>. Probable Cause Indicates that during the Coordinated HotCode protocol, a switch in the fabric has rejected the resume message which prevented the protocol from completing. Any data traffic disruption observed during the firmware download may have been due to the rejected resume message.
Page 287: Ess-1010
ESS-1010 Recommended Select an appropriate fabric name and set it again from any switch. Action Severity WARNING ESS-1010 Message <timestamp>, [ESS-1010], <sequence-number>,, WARNING, <system-name>, Duplicate Fabric Name - <fabric_name> matching with FID <Fabric ID>. Probable Cause Indicates that the configured fabric name is already used for another partition. Recommended Select a different fabric name and reconfigure.
Page 288 ESS-1010 Fabric OS Message Reference 53-1002448-01...
Page 289: Esw-1001
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 290: Esw-1004
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 291: Esw-1008
ESW-1008 Recommended Based on the disable reason displayed, take appropriate action to restore the port. Insufficient Action 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 292 ESW-1008 Fabric OS Message Reference 53-1002448-01...
Page 293: Evmd-1001
Chapter EVMD System Messages EVMD-1001 Message <timestamp>, [EVMD-1001], <sequence-number>,, WARNING, <system-name>, Event could not be sent to remote proxy. = <Remote proxy switch id> 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 294 EVMD-1001 Fabric OS Message Reference 53-1002448-01...
Page 295: Fabr-1001
Chapter FABR System Messages FABR-1001 Message <timestamp>, [FABR-1001], <sequence-number>,, WARNING, <system-name>, port <port number>, <segmentation reason>. Probable Cause Indicates that the specified switch port is isolated because of a segmentation resulting from mismatched configuration parameters. Recommended Based on the segmentation reason displayed within the message, look for a possible mismatch of Action relevant configuration parameters in the switches at both ends of the link.
Page 296: Fabr-1004
FABR-1004 Run the fabStateShow command on both the receiving and transmitting switches. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING FABR-1004 Message <timestamp>, [FABR-1004], <sequence-number>,, WARNING, <system-name>, port: <port number>, req iu: 0x<address of IU request sent>, state: 0x<command sent>, resp iu:...
Page 297: Fabr-1007
FABR-1007 Recommended In case of severe memory corruption, the system might recover by performing an automatic Action failover. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING FABR-1007...
Page 298: Fabr-1010
FABR-1010 Recommended The fabric daemon will discard the EFP. The system will recover through the EFP retrial process. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING FABR-1010...
Page 299: Fabr-1013
FABR-1013 FABR-1013 Message <timestamp>, [FABR-1013], <sequence-number>, FFDC, CRITICAL, <system-name>, No Memory: pid=<fabric process id> file=<source file name> line=<line number within the source file>. Probable Cause Indicates that there is not enough memory in the switch for the fabric module to allocate. This message is rare and usually indicates a problem with the Fabric OS.
Page 300: Fabr-1016
FABR-1016 FABR-1016 Message <timestamp>, [FABR-1016], <sequence-number>,, WARNING, <system-name>, ficonMode is enabled. Probable Cause Indicates that FICON mode is enabled on the switch through a user interface command. Recommended No action is required. Action Severity WARNING FABR-1017 Message <timestamp>, [FABR-1017], <sequence-number>,, WARNING, <system-name>, ficonMode is disabled.
Page 301: Fabr-1019
FABR-1019 FABR-1019 Message <timestamp>, [FABR-1019], <sequence-number>, FFDC, CRITICAL, <system-name>, Critical fabric size (<current domains>) exceeds supported configuration (<supported domains>). 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.
Page 302: Fabr-1022
FABR-1022 FABR-1022 Message <timestamp>, [FABR-1022], <sequence-number>, FFDC, CRITICAL, <system-name>, Fabric size (<actual domains>) exceeds supported configuration (<supported domains>). Fabric limit timer (<type>) started from <grace period in seconds>. Probable Cause Indicates that the fabric size has exceeded the value-line limit, and the grace period counter has started.
Page 303: Fabr-1029
FABR-1029 FABR-1029 Message <timestamp>, [FABR-1029], <sequence-number>,, INFO, <system-name>, Port <port number> negotiated <flow control mode description> (mode = <received flow control mode>). Probable Cause Indicates that a different flow control mode, as described in the message, is negotiated with the port at the other end of the link.
Page 304: Fabr-1032
FABR-1032 FABR-1032 Message <timestamp>, [FABR-1032], <sequence-number>, WARNING, <system-name>, Remote switch with domain ID <domain ID> and switchname <switchname>running an unsupported FOS version v2.x has joined the fabric. Probable Cause Indicates that a switch with an unsupported Fabric OS version 2.x has joined the fabric. Recommended Remove the switch with the unsupported Fabric OS version 2.x from the fabric.
Page 305: Fabr-1037
FABR-1037 Recommended Move the cable to a port that does not have Trunk Area enabled. Action Severity INFO FABR-1037 Message <timestamp>, [FABR-1037], <sequence-number>, INFO, <system-name>, Port configuration incompatible with Trunk Area enabled port. Persistently disabling port <Port that is being disabled>. Probable Cause 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,...
Page 306: Fabr-1040
FABR-1040 FABR-1040 Message <timestamp>, [FABR-1040], <sequence-number>, INFO, <system-name>, Speed is not 2g,4g or 8g with F_port trunking enabled. Persistently disabling port <Port that is being disabled>. Probable Cause Indicates that the speed is not compatible for F_port trunks. Recommended Change the speed for the port or disable F_port trunking on the port. Action Severity INFO...
Page 307: Fabr-1044
FABR-1044 FABR-1044 Message <timestamp>, [FABR-1044], <sequence-number>, ERROR, <system-name>, Detected Fabric ID 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 a Fabric ID conflict with the local switch. All E_ports directly connected to the conflicting switch are disabled.
Page 308: Fabr-1047
FABR-1047 FABR-1047 Message <timestamp>, [FABR-1047], <sequence-number>, INFO, <system-name>, Area unavailable to assign to the port. Persistently disabling port <Port that is being disabled>. Probable Cause Indicates that there are no areas available to assign to the port during port creation. Recommended Move some ports out of the default switch to make areas available.
Page 309: Fabr-1051
FABR-1051 Recommended Install the required license. Action Severity INFO FABR-1051 Message <timestamp>, [FABR-1051], <sequence-number>,, ERROR, <system-name>, D-Port <Testname> loopback test failed for slot <Slot> and port <Port>. Probable Cause Indicates that the D-Port test failed for the given slot and port due to one of the following reasons: •...
Page 310: Fabr-1054
FABR-1054 FABR-1054 Message <timestamp>, [FABR-1054], <sequence-number>, FFDC, INFO, <system-name>, Rebooting the standby as it received an update before port [<Port Number>] is expanded. Probable Cause Indicates that the standby CP did not have the port because the port expand operation is still in progress and the standby CP has received a port update.
Page 311: Fabs-1001
Chapter FABS System Messages FABS-1001 Message <timestamp>, [FABS-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, <Function name> <Description of memory need> Probable Cause Indicates that the system is low on memory and cannot allocate more memory for new operations. This is usually an internal Fabric OS problem or file corruption. Description of memory need indicates how much memory was being requested.
Page 312: Fabs-1005
FABS-1005 FABS-1005 Message <timestamp>, [FABS-1005], <sequence-number>,, WARNING, <system-name>, <Function name and description of problem> (<ID type>= <ID number>) Probable Cause Indicates that an unsupported operation has been requested. This is usually an internal Fabric OS problem or file corruption. The possible value for function name and description of problem is: fabsys_write: Unsupported write operation: process xxx where xxx is the process ID (PID), which could be any whole number.
Page 313: Fabs-1008
FABS-1008 If the message persists, run the firmwareDownload command to update the firmware. Severity WARNING FABS-1008 Message <timestamp>, [FABS-1008], <sequence-number>,, WARNING, <system-name>, <Function 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.
Page 314: Fabs-1013
FABS-1013 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-1013 Message <timestamp>, [FABS-1013], <sequence-number>,, ERROR, <system-name>, <Method name>[<Method tag number>]:Unknown blade type 0x<Blade type> Probable Cause Indicates an unrecognized type of blade has been discovered in the system.
Page 315 FABS-1015 If the message persists, run the firmwareDownload command to update the firmware. Severity ERROR Fabric OS Message Reference 53-1002448-01...
Page 316 FABS-1015 Fabric OS Message Reference 53-1002448-01...
Page 317: Fbc-1001
Chapter FBC System Messages FBC-1001 Message <timestamp>, [FBC-1001], <sequence-number>,, ERROR, <system-name>, Firmware version on AP blade is incompatible with that on the CP. Probable Cause The CP determined that the version of firmware running on the AP blade is not compatible with the version of firmware running on the CP.
Page 318 FBC-1001 Fabric OS Message Reference 53-1002448-01...
Page 319: Fcip-1000
Chapter FCIP System Messages FCIP-1000 Message <timestamp>, [FCIP-1000], <sequence-number>, FFDC, ERROR, <system-name>, <command name> of GE <port number> failed. Please retry the command. Data: inst=<ASIC instance> st=<ASIC initializing state> rsn=<reason code> fn=<message function> oid=<ASIC ID> Probable Cause Indicates that the hardware is not responding to a command request, possibly because it is busy. Recommended Retry the command.
Page 320: Fcip-1003
FCIP-1003 FCIP-1003 Message <timestamp>, [FCIP-1003], <sequence-number>, INFO, <system-name>, An IPsec/IKE policy was deleted. 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, <system-name>, Tape Read Pipelining is being disabled slot (<slot number>) port (<user port index>) tunnel (<The configured tunnel ID (0-7)>).
Page 321: Fcmc-1001
Chapter FCMC System Messages FCMC-1001 Message <timestamp>, [FCMC-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, System is low on memory and has failed to allocate new memory. Probable Cause Indicates that the switch is low on memory and failed to allocate new memory for an information unit (IU).
Page 322 FCMC-1001 Fabric OS Message Reference 53-1002448-01...
Page 323: Fcoe-1001
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 logingroup limit reached at <limit>. Probable Cause Indicates that too many logingroups have been added.
Page 324: Fcoe-1005
FCOE-1005 Recommended Remove the failed member from the logingroup. Action Severity ERROR FCOE-1005 Message <timestamp>, [FCOE-1005], <sequence-number>,, ERROR, <system-name>, <device>: membership check failed in logingroup: <lg> Probable Cause Indicates that the Membership check for the device has failed. Recommended Check the device for failed Membership. Action Severity ERROR...
Page 325: Fcoe-1010
FCOE-1010 Recommended Remove unwanted nport mappings and try adding nport mapping. Action Severity INFO FCOE-1010 Message <timestamp>, [FCOE-1010], <sequence-number>,, ERROR, <system-name>, Cleanup of login failed for port:<port>. Probable Cause Indicates an invalid port number. Recommended Use the supportsave command and restart the system. Action Severity ERROR...
Page 326: Fcoe-1015
FCOE-1015 Recommended Request to add ports to VLAN failed. Action Severity ERROR FCOE-1015 Message <timestamp>, [FCOE-1015], <sequence-number>,, ERROR, <system-name>, Request to add MACs to Layer 2 for ifindex 0x<ifindex>x failed, rc:<rc>. Probable Cause Indicates that an add request to Layer 2 for slot or port has failed. Recommended Request to add MACs to Layer 2 for slot or port failed.
Page 327: Fcoe-1019
FCOE-1019 Recommended Request to delete MACs from Layer 2 for slot or port failed. Action Severity ERROR FCOE-1019 Message <timestamp>, [FCOE-1019], <sequence-number>,, WARNING, <system-name>, FLOGI ignored as FC-MAP not configured on FCOE VLAN. Probable Cause Indicates that the FC-MAP has not been configured on FCOE VLAN. Recommended Configure FC-MAP on FCOE VLAN.
Page 328: Fcoe-1024
FCOE-1024 Recommended No action is required. Action Severity WARNING FCOE-1024 Message <timestamp>, [FCOE-1024], <sequence-number>,, WARNING, <system-name>, FDISC received from Enode without prior FLOGI. Probable Cause Indicates that no root Nport has logged in. Recommended No action is required. Action Severity WARNING FCOE-1025 Message...
Page 329: Fcoe-1028
FCOE-1028 Recommended No action is required. Action Severity ERROR FCOE-1028 Message <timestamp>, [FCOE-1028], <sequence-number>,, ERROR, <system-name>, <msg>: <wwn1> <wwn2> <wwn3> <wwn4> <wwn5> <wwn6> <wwn7> <wwn8>. Probable Cause Indicates the FCoE device with following WWN is not a member of the login group: WWN will be printed.
Page 330: Fcoe-1032
FCOE-1032 Recommended No action is required. Action Severity WARNING FCOE-1032 Message <timestamp>, [FCOE-1032], <sequence-number>,, WARNING, <system-name>, We are in WARM RECOVERING state. Probable Cause Indicates that a HA failover or reboot may be in progress. Recommended No action is required. Action Severity WARNING...
Page 331: Fcoe-1038
FCOE-1038 Recommended Create a logingroup for the switch WWN with another name that will not lead to a name conflict. Action Severity WARNING FCOE-1038 Message <timestamp>, [FCOE-1038], <sequence-number>,, INFO, <system-name>, logingroup# <logingroup number> (<logingroup name>)created. Probable Cause Indicates that the logingroup is added in the switch logingroup table. Recommended No action is required.
Page 332: Fcoe-1042
FCOE-1042 Recommended No action is required. Action Severity INFO FCOE-1042 Message <timestamp>, [FCOE-1042], <sequence-number>,, INFO, <system-name>, FCoE login configuration transaction saved fabric-wide. Probable Cause Indicates that the FCoE login configuration transaction is saved fabric-wide. Recommended No action is required. Action Severity INFO FCOE-1043...
Page 333: Fcoe-1046
FCOE-1046 Recommended No action is required. Action Severity INFO FCOE-1046 Message <timestamp>, [FCOE-1046], <sequence-number>,, INFO, <system-name>, fcoed.conf file is truncated. Please reconfigure FCoE ports. Probable Cause Indicates the magic number in the fcoed.conf file does not match. The fcoed.conf file is truncated and updated with a new magic number.
Page 334 FCOE-1048 Fabric OS Message Reference 53-1002448-01...
Page 335: Fcpd-1001
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 336 FCPD-1003 Fabric OS Message Reference 53-1002448-01...
Page 337: Fcph-1001
Chapter FCPH System Messages FCPH-1001 Message <timestamp>, [FCPH-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, <function>: <failed function call> failed, out of memory condition Probable Cause Indicates that the switch is low on memory and failed to allocate new memory for a Fibre Channel driver instance.
Page 338: Fcph-1004
FCPH-1004 Recommended No action is required. Action Severity WARNING FCPH-1004 Message <timestamp>, [FCPH-1004], <sequence-number>,, WARNING, <system-name>, NPIV port <Port Number> has same Port WWN with old port <Port Number> with pid 0x<Port PID> as part of duplicate Port WWN detection policy. Probable Cause Indicates that this port is older port of same port name of NPV device.
Page 339: Fcr-1001
Chapter FCR System Messages FCR-1001 Message <timestamp>, [FCR-1001], <sequence-number>,, INFO, <system-name>, FC router proxy device in edge created at port <port number>. Probable Cause Indicates that a proxy device at the port in the edge fabric has been imported at the specified port. Recommended No action is required.
Page 340: Fcr-1005
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 341: Fcr-1008
FCR-1008 FCR-1008 Message <timestamp>, [FCR-1008], <sequence-number>,, INFO, <system-name>, FC router LSAN zone created at port <port number>. 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...
Page 342: Fcr-1012
FCR-1012 Recommended No action is required. Action Severity INFO 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.
Page 343: Fcr-1016
FCR-1016 FCR-1016 Message <timestamp>, [FCR-1016], <sequence-number>,, INFO, <system-name>, FCR fabric no longer reachable at port id <port number> (<port number (hex)>) fabric ID <fabric ID>. Probable Cause Indicates that a fabric is no longer accessible through the backbone fabric. This may be caused by a link or switch failure.
Page 344: Fcr-1020
FCR-1020 FCR-1020 Message <timestamp>, [FCR-1020], <sequence-number>,, WARNING, <system-name>, Local LSAN zone entries for FC router exhausted; max limit: <LSAN zone limit>. Probable Cause Indicates that the number of logical storage area network (LSAN) zones created within a MetaSAN exceeds the local LSAN zone database limitations. Recommended Remove excess LSAN zones so that the number of LSAN zones created is within the range of local Action...
Page 345: Fcr-1023
FCR-1023 FCR-1023 Message <timestamp>, [FCR-1023], <sequence-number>,, WARNING, <system-name>, Local phantom port WWN entries exhausted. Probable Cause Indicates that the number of port world wide names (WWNs) in use exceeds the local port WWN resources. Recommended Limit the number of port WWNs required by limiting the remote edge fabric connectivity (which Action limits the number of translate domains).
Page 346: Fcr-1027
FCR-1027 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. WWN conflicts might cause unpredictable behavior in management applications.
Page 347: Fcr-1029
FCR-1029 FCR-1029 Message <timestamp>, [FCR-1029], <sequence-number>,, INFO, <system-name>, In slot <slot number> port WWN pool 95 percent allocated. Probable Cause Indicates that the Port world wide name (WWN) pool has rolled over in the specified slot, and WWN entries detected not 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...
Page 348: Fcr-1033
FCR-1033 Recommended No action is required. Action Severity INFO FCR-1033 Message <timestamp>, [FCR-1033], <sequence-number>,, INFO, <system-name>, Edge fabric disabled security on port <port number> in fabric <fabric ID>. Probable Cause Indicates that Secure mode was turned off in the edge fabric. Recommended No action is required.
Page 349: Fcr-1037
FCR-1037 Recommended No action is required. Action Severity INFO FCR-1037 Message <timestamp>, [FCR-1037], <sequence-number>,, INFO, <system-name>, LSAN zone disabled in the backbone fabric. Probable Cause Indicates that a logical storage area network (LSAN) zone is disabled in the backbone fabric. Recommended No action is required.
Page 350: Fcr-1040
FCR-1040 FCR-1040 Message <timestamp>, [FCR-1040], <sequence-number>,, INFO, <system-name>, Proxy device deleted in the backbone fabric. Probable Cause Indicates that a proxy device created in the backbone fabric was deleted. Recommended No action is required. Action Severity INFO FCR-1041 Message <timestamp>, [FCR-1041], <sequence-number>,, INFO, <system-name>, LSAN zone device removed in the backbone fabric.
Page 351: Fcr-1048
FCR-1048 FCR-1048 Message <timestamp>, [FCR-1048], <sequence-number>,, ERROR, <system-name>, On EX port (<port number>) setting port <credit type> credits failed. Probable Cause Indicates that the specified credit type was not set. Recommended Setting port credits failed. Execute the portEnable command. Action If the problem persists try restarting the switch.
Page 352: Fcr-1055
FCR-1055 Recommended Check the error message log on the other switch using the errShow command for additional Action messages. Check for a faulty cable or deteriorated small form-factor pluggable (SFP). Replace the cable or SFP if necessary. Run the portLogDumpPort command on both the receiving and transmitting port. Run the fabStateShow command on the transmitting switch.
Page 353: Fcr-1058
FCR-1058 Investigate the other switch for more details. Run the errShow command on the other switch to view the error log for additional messages. Severity ERROR FCR-1058 Message <timestamp>, [FCR-1058], <sequence-number>,, WARNING, <system-name>, Port <port number> isolated due to mismatched configuration parameter; <segmentation reason>.
Page 354: Fcr-1061
FCR-1061 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. Severity WARNING FCR-1061 Message <timestamp>, [FCR-1061], <sequence-number>,, INFO, <system-name>, Backbone fabric created on port <port number>.
Page 355: Fcr-1064
FCR-1064 FCR-1064 Message <timestamp>, [FCR-1064], <sequence-number>,, ERROR, <system-name>, Fabric ID of backbone FC-Routers mismatch or overlap. Probable Cause Indicates that either (1) a backbone fabric split and both are connected to common edge fabrics, or (2) the fabric IDs of two backbone fabrics connected to an edge fabric are the same. Recommended If the backbone fabric split, merge the fabrics.
Page 356: Fcr-1068
FCR-1068 The limit includes both active and configured information that is part of the zoning database in the edge fabric. Non-LSAN zones are not counted in the limit. Recommended Limit the logical storage area network (LSAN) zoning related zone configuration in the edge fabric Action connected to this port.
Page 357: Fcr-1071
FCR-1071 FCR-1071 Message <timestamp>, [FCR-1071], <sequence-number>,, INFO, <system-name>, Port <port number> is changed from non FCR port to FCR port. Probable Cause Indicates that the port became an EX_Port or VEX_Port. Recommended No action is required. Action Severity INFO FCR-1072 Message <timestamp>, [FCR-1072], <sequence-number>,, INFO, <system-name>, Port <port number>...
Page 358: Fcr-1075
FCR-1075 Recommended Keep the number of LSAN Zones to the lower limit of the two CPs or upgrade the remote CP. Action Severity ERROR FCR-1075 Message <timestamp>, [FCR-1075], <sequence-number>,, ERROR, <system-name>, Zone Name configuration is larger than <Zone Name Limit> characters in the edge fabric connected to port <port numer>.
Page 359: Fcr-1078
FCR-1078 Recommended Ensure that the M-Model switch has the same currently configured details such as front port Action domain ID and WWN of the EX_Port on which this operation was attempted. Severity WARNING FCR-1078 Message <timestamp>, [FCR-1078], <sequence-number>,, WARNING, <system-name>, LSAN name <LSAN name>...
Page 360: Fcr-1081
FCR-1081 FCR-1081 Message <timestamp>, [FCR-1081], <sequence-number>,, WARNING, <system-name>, The pause 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 pause message.
Page 361: Fcr-1085
FCR-1085 Recommended No action is required. Action Severity WARNING FCR-1085 Message <timestamp>, [FCR-1085], <sequence-number>,, ERROR, <system-name>, HA sync lost as remote CP does not support FCR based matrix. Probable Cause Indicates that the remote control processor (CP) has earlier firmware, which does not support the FCR- based matrix while the local CP has the feature enabled.
Page 362: Fcr-1088
FCR-1088 FCR-1088 Message <timestamp>, [FCR-1088], <sequence-number>,, INFO, <system-name>, LSAN <Enforce/Speed> tag <Tag Name> added. Probable Cause Indicates that the user has added a LSAN tag. Recommended No action is required. Action Severity INFO FCR-1089 Message <timestamp>, [FCR-1089], <sequence-number>,, INFO, <system-name>, LSAN <Enforce/Speed>...
Page 363: Fcr-1093
FCR-1093 FCR-1093 Message <timestamp>, [FCR-1093], <sequence-number>,, INFO, <system-name>, Slave EX-Port <Slave> interopmode conflicts with trunk master <Master>. Disabling the port. Probable Cause Indicates that the slave EX-Port is disabled due to interop conflict with trunk master. Recommended Configure slave EX-Port with the trunk master interopmode. Action Severity INFO...
Page 364 FCR-1094 Fabric OS Message Reference 53-1002448-01...
Page 365: Ficn-1003
Chapter FICON System Messages The FICON messages in this chapter include in many of the messages. The FICON <FICON Path> Path is a string that includes, where: VEHDHPDDDPLPCUDV • VE - VE Port Number: This number represents the FCIP Tunnel number through its VE Port number.
Page 366: Ficn-1004
FICN-1004 FICN-1004 Message <timestamp>, [FICN-1004], <sequence-number>,, WARNING, <system-name>, FICON XRC Emulation License Key is not installed. Probable Cause Indicates FICON eXtended Remote Copy (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 367: Ficn-1007
FICN-1007 FICN-1007 Message <timestamp>, [FICN-1007], <sequence-number>,, ERROR, <system-name>, DevDiskEgr:FICON Selective Reset:Path=<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR CUADDR DeviceAddr> State=0x<current Emulation State> stat_array=0x<the Last 4 Status values that were received from the device>. Probable Cause Indicates that a Selective Reset from the channel was received as normal part of path recovery or starting sequence in an error case.
Page 368: Ficn-1010
FICN-1010 FICN-1010 Message <timestamp>, [FICN-1010], <sequence-number>,, INFO, <system-name>, DevDiskEgr:Device level exception flag found for Path=<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR CUADDR DeviceAddr>: Oxid=0x<The OXID that was reported in the Device Level Exception Frame>. Probable Cause Indicates that a Device Level Exception frame was received from the FICON channel. Recommended If there was a job or IO failure associated with this event, contact your switch service provider.
Page 369: Ficn-1013
FICN-1013 FICN-1013 Message <timestamp>, [FICN-1013], <sequence-number>,, INFO, <system-name>, DevDiskIng:Status=0x<Status that was received from the DASD device in an odd state> received in odd state=0x<The current emulation state> from Path=0x<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR CUADDR DeviceAddr> sent LBY. Probable Cause Indicates that when the device sent the status in an incorrect state, the emulation processing rejected the status with an LBY frame.
Page 370: Ficn-1016
FICN-1016 FICN-1016 Message <timestamp>, [FICN-1016], <sequence-number>,, INFO, <system-name>, DevIng:Received Logical Path Removed response:Path=0x<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR> <CUADDR>. Probable Cause Indicates the FICON Control Unit sent an LPR frame to the FICON channel. Recommended No action is required. Action Severity INFO FICN-1017...
Page 371: Ficn-1020
FICN-1020 Recommended If there was a job failure associated with this event, contact your switch service provider. Action Severity ERROR FICN-1020 Message <timestamp>, [FICN-1020], <sequence-number>,, WARNING, <system-name>, DevTapeEgr:FICON Cancel received Path=<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR CUADDR DeviceAddr> state=0x<the current emulation state for the device>...
Page 372: Ficn-1023
FICN-1023 FICN-1023 Message <timestamp>, [FICN-1023], <sequence-number>,, ERROR, <system-name>, DevTapeEgr:FICON Selective Reset:Path=<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR CUADDR DeviceAddr> Elapsed Time=<the current SIO time in seconds for the device>.<the current SIO time in milliseconds for the device> seconds. Probable Cause Indicates that the FICON channel issued a Selective Reset sequence for a device. Recommended If there was an unexpected job failure associated with this event, contact your switch service Action...
Page 373: Ficn-1026
FICN-1027 Recommended If there was an unexpected job failure or IO Error associated with this event, contact your switch Action service provider. Severity INFO FICN-1027 Message <timestamp>, [FICN-1027], <sequence-number>,, ERROR, <system-name>, DevTapeIng:Device level exception found for Path=<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr>: Oxid=0x<The OXID of the frame that included the Device Level Exception>.
Page 374: Ficn-1030
FICN-1030 FICN-1030 Message <timestamp>, [FICN-1030], <sequence-number>,, ERROR, <system-name>, HostDiskIng:FICON Purge received:Path=<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR CUADDR DeviceAddr>. Probable Cause Indicates an active disk emulation device received a FICON Purge Path from the channel. Recommended If there was an unexpected job failure or IO Error associated with this event, contact your switch Action service provider.
Page 375: Ficn-1033
FICN-1034 Recommended No action is required. This is part of the FICON path initialization. Action Severity INFO FICN-1034 Message <timestamp>, [FICN-1034], <sequence-number>,, ERROR, <system-name>, HostEgr:Discarding Invalid LRCd Frame on Path=<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort> count=<The total number of frames that have been received with an invalid LRC>.
Page 376: Ficn-1036
FICN-1037 FICN-1037 Message <timestamp>, [FICN-1037], <sequence-number>,, INFO, <system-name>, HostIng:FICON ELP Request on Path=<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort> <LPAR> <CUADDR>. Probable Cause Indicates that a locally connected FICON Channel issued an Establish Logical Path sequence to the specified FICON Control Unit. Recommended No action is required.
Page 377: Ficn-1040
FICN-1040 FICN-1040 Message <timestamp>, [FICN-1040], <sequence-number>,, ERROR, <system-name>, HostTapeEgr:Tape:CmdReject Sense Data Rcvd:Path=<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR CUADDR DeviceAddr>LastCmds=0x<Last 4 commands received from the channel for this device> 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>.
Page 378: Ficn-1043
FICN-1043 FICN-1043 Message <timestamp>, [FICN-1043], <sequence-number>,, ERROR, <system-name>, HostTapeIng::FICON Selective Reset:Path=<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR CUADDR DeviceAddr> state=0x<the current emulation state for this device> LastCmds=0x<the last 4 commands received from the channel for this device> LastStatus=0x<the last 4 status values presented to the channel for this device>.
Page 379: Ficn-1046
FICN-1046 FICN-1046 Message <timestamp>, [FICN-1046], <sequence-number>,, WARNING, <system-name>, HostTapeIng:LRJ received on Path=<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR CUADDR DeviceAddr>lastCmds=0x<Last 4 commands received from the channel for this device> lastStatus=0x<Last 4 status values presented to the channel for this device> treating as system reset event. Probable Cause Indicates an LRJ from a FICON channel indicates that the channel believes that it no longer has a path established to the CU.
Page 380: Ficn-1049
FICN-1049 FICN-1049 Message <timestamp>, [FICN-1049], <sequence-number>,, WARNING, <system-name>, ProcessIngTirData:Lost Logical Path for Path=<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR CUADDR DeviceAddr> <CUADDR>Index=<Current processing index in the TIR data from the locally connected channel or control unit>. Probable Cause Indicates a TIR received from a FICON end point indicates that it no longer has an established path to its peer.
Page 381: Ficn-1052
FICN-1052 FICN-1052 Message <timestamp>, [FICN-1052], <sequence-number>,, INFO, <system-name>, XRC Session Terminated: SessID=<SDM Assigned Session ID>, Path=0x<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 382: Ficn-1056
FICN-1056 Recommended If this was an unexpected event, contact your vendor's customer support for assistance. Action Severity WARNING FICN-1056 Message <timestamp>, [FICN-1056], <sequence-number>,, ERROR, <system-name>, FICON Emulation Error Error Code=<The internal emulation error code value>, Path=<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR CUADDR DeviceAddr>...
Page 383: Ficn-1059
FICN-1059 FICN-1059 Message <timestamp>, [FICN-1059], <sequence-number>,, ERROR, <system-name>, Error return from frame generation for a FICON Image: Path=0x<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 384: Ficn-1062
FICN-1062 FICN-1062 Message <timestamp>, [FICN-1062], <sequence-number>,, ERROR, <system-name>, Ingress Abort:Oxid=0x<the OXID of the aborted exchange>:Path=0x<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR CUADDR DeviceAddr>:LastStates=0x<prior emulation state> <previous emulation state> <current emulation state>. Probable Cause Indicates an abort operation has been received from the local FC interface for an active emulation exchange.
Page 385: Ficn-1065
FICN-1065 FICN-1065 Message <timestamp>, [FICN-1065], <sequence-number>,, INFO, <system-name>, Egress Abort:Oxid=0x<the OXID of the aborted exchange>:Unknown Path on GEPort=<GEPort Number> VEPort=<VEPortNumber> from SID=0x<Source Domain><Source Port> to DID=0x<Destination Domain><Destination Port>. Probable Cause Indicates an abort operation has been received from a peer FC interface for an exchange. Recommended If there were associated IO errors at the same time as this event, contact your vendor's customer Action...
Page 386: Ficn-1069
FICN-1069 Recommended If there were associated IO errors at the same time as this event, contact your vendor's customer Action support for assistance. Severity ERROR FICN-1069 Message <timestamp>, [FICN-1069], <sequence-number>,, ERROR, <system-name>, Emulation Configuration Error on TunnelId <Tunnel ID>. Probable Cause Indicates an error has been noted in the FICON configuration.
Page 387: Ficn-1072
FICN-1072 FICN-1072 Message <timestamp>, [FICN-1072], <sequence-number>,, INFO, <system-name>, DevTapeEgr:Tape Loaded on Path=0x<VEPortNumber HostDomain HostPort DeviceDomain> <DevicePort LPAR CUADDR DeviceAddr>. Probable Cause Indicates the tape IOs are processed from a locally connected LPAR, which indicates that a tape is loaded on a device. Recommended No action is required.
Page 388: Ficn-1075
FICN-1075 FICN-1075 Message <timestamp>, [FICN-1075], <sequence-number>,, INFO, <system-name>, HostTapeIngr:ReadBlkReport: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 389: Ficn-1078
FICN-1078 Recommended No action is required. Action Severity INFO FICN-1078 Message <timestamp>, [FICN-1078], <sequence-number>,, INFO, <system-name>, DevTapeEgr:ReadBlkReport: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 write commands processed while this tape was loaded>:Chains=0x<the number of emulated host chains processed while this tape was loaded>:MBytes=<the number of emulated write megabytes processed while this tape was loaded>...
Page 390: Ficn-1080
FICN-1080 FICN-1080 Message <timestamp>, [FICN-1080], <sequence-number>,, INFO, <system-name>, DevTapeEgr:ReadCpReport:Path=0x<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 391: Ficn-1083
FICN-1083 FICN-1083 Message <timestamp>, [FICN-1083], <sequence-number>,, WARNING, <system-name>, EmulEls:SW_RSCN received on GEPort=<GEPortNumber> VEPort=<VEPortNumber> Domain=0x<Domain> Port=0x<Port Host/Device Side>. Probable Cause Indicates an attached port with the established FICON emulated path has logged out from the switch. Recommended This may be an unexpected event, contact your vendor's customer support for assistance. Action Severity WARNING...
Page 392: Ficn-1087
FICN-1087 FICN-1087 Message <timestamp>, [FICN-1087], <sequence-number>,, ERROR, <system-name>, DevTeraEgr:AS Link Level Reject (LRJ) from Chan on Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> LastCmd=0x<the Last 4 commands issued to the device> LastStatus=0x<the Last 4 status values received from the device>. Probable Cause Indicates the FICON channel indicated in the path issued an LRJ frame for a sequence from the device.
Page 393: Ficn-1090
FICN-1090 FICN-1090 Message <timestamp>, [FICN-1090], <sequence-number>,, ERROR, <system-name>, DevTeraEgr:FICON Selective Reset:Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> State=0x<the current state of the device that received the selective reset> statArray=0x<the last 4 status values received from the device> cmdArray=0x<the last 4 commands that were issued to the device>...
Page 394: Ficn-1093
FICN-1093 FICN-1093 Message <timestamp>, [FICN-1093], <sequence-number>,, WARNING, <system-name>, DevTeraEgr:Auto Sense Data received on Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> 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 the FICON tera write pipeline processed sense data from a FICON device.
Page 395: Ficn-1096
FICN-1096 FICN-1096 Message <timestamp>, [FICN-1096], <sequence-number>,, ERROR, <system-name>, HostTeraEgr:CmdReject Sense Data Rcvd: Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> LastCmds=0x<Last 4 commands received from the channel for this device> 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>.
Page 396: Ficn-1099
FICN-1099 FICN-1099 Message <timestamp>, [FICN-1099], <sequence-number>,, ERROR, <system-name>, HostTeraIng::FICON Selective Reset:Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> state=0x<the current emulation state for this device> LastCmds=0x<the last 4 commands received from the channel for this device> LastStatus=0x<the last 4 status values presented to the channel for this device>.
Page 397: Ficn-1102
FICN-1102 FICN-1102 Message <timestamp>, [FICN-1102], <sequence-number>,, WARNING, <system-name>, HostTeraIng:LRJ received on Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> lastCmds=0x<Last 4 commands received from the channel for this device> lastStatus=0x<Last 4 status values presented to the channel for this device> treating as system reset event. Probable Cause Indicates an LRJ from a FICON channel indicates that the channel believes that it no longer has a path established to the CU.
Page 398: Ficn-1105
FICN-1105 FICN-1105 Message <timestamp>, [FICN-1105], <sequence-number>,, WARNING, <system-name>, DevTeraIng:LRJ received on Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> lastCmds=0x<Last 4 commands received from the channel for this device> lastStatus=0x<Last 4 status values presented to the channel for this device> treating as system reset event. Probable Cause Indicates an LRJ from a FICON channel indicates that the channel does not have a path established to the CU.
Page 399: Ficn-1108
FICN-1108 FICN-1108 Message <timestamp>, [FICN-1108], <sequence-number>,, WARNING, <system-name>, DevPrintEgr:FICON Tera Cancel:Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> 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 400: Ficn-1111
FICN-1111 FICN-1111 Message <timestamp>, [FICN-1111], <sequence-number>,, ERROR, <system-name>, DevPrintEgr:FICON Purge received Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr>. Probable Cause Indicates the FICON channel issued a Purge Path command sequence for a device. Recommended If there was an unexpected job failure associated with this event, contact your vendor's customer Action support for assistance.
Page 401: Ficn-1114
FICN-1114 FICN-1114 Message <timestamp>, [FICN-1114], <sequence-number>,, ERROR, <system-name>, DevPrintIng:Device level exception found for Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr>: Oxid=0x<The OXID of the frame that included the Device Level Exception>. Probable Cause Indicates an active emulation device delivered a Device Level Exception frame to the emulation processing.
Page 402: Ficn-1117
FICN-1117 FICN-1117 Message <timestamp>, [FICN-1117], <sequence-number>,, WARNING, <system-name>, HostPrintIng:FICON Cancel received Path=0x<VEPortNumber HostDomain HostPort DeviceDomain><DevicePort LPAR CUADDR DeviceAddr> state=0x<the current emulation state for this device>. Probable Cause Indicates a job was cancelled during Print write pipelining. Recommended If this was an unexpected event (cancel is normally an operator event), contact your vendor's Action customer support for assistance.
Page 403: Ficn-1120
FICN-1120 FICN-1120 Message <timestamp>, [FICN-1120], <sequence-number>,, WARNING, <system-name>, HostPrintIng:FICON Purge received:Path=0x<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 FICON path recovery. Recommended If this was an unexpected event, contact your vendor's customer support for assistance. Action Severity WARNING...
Page 404: Ficn-2005
FICN-2005 FICN-2005 Message <timestamp>, [FICN-2005], <sequence-number>,, INFO, <system-name>, FICON VEPort <VE port number> Feature Change verified Xrc <1 or 0 - XRC Emulation Enabled or Disabled> TapeWrt <1 or 0 - Tape Write Emulation Enabled or Disabled> TapeRd <1 or 0 - FICON Tape Read Emulation Enabled or Disabled>...
Page 405: Ficn-2065
FICN-2065 FICN-2065 Message <timestamp>, [FICN-2065], <sequence-number>,, INFO, <system-name>, Egress Abort:Oxid=0x<the OXID of the aborted exchange>:Unknown Path on VEPort=<VEPortNumber> from SID=0x<Source Domain><Source Port> to DID=0x<Destination Domain><Destination Port>. Probable Cause Indicates an abort operation has been received from a peer FC interface for an exchange. Recommended If there were associated IO errors at the same time as this event, contact your vendor's customer Action...
Page 406: Ficn-2085
FICN-2085 Recommended This may be an unexpected event, contact your vendor's customer support for assistance. Action Severity WARNING FICN-2085 Message <timestamp>, [FICN-2085], <sequence-number>,, INFO, <system-name>, FICON or FCP Emulation Enabled FCIP Tunnel is Up on VEPort=<VEPortNumber>. Probable Cause Indicates a FICON or FCP Emulation Enabled FCIP tunnel has been established successfully to the peer switch.
Page 407: Ficu-1001
Chapter FICU System Messages FICU-1001 Message <timestamp>, [FICU-1001], <sequence-number>,, ERROR, <system-name>, <function name>: config<config Set(key)|Get(key)| Save> failed rc = <error>. Probable Cause Indicates that one of the configuration management functions have 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 408: Ficu-1004
FICU-1004 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 FICON-CUP.
Page 409: Ficu-1007
FICU-1007 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 may be a transient problem. Recommended Check the memory usage in the switch using the memShow command. Action If the problem persists, execute the supportFtp command (as needed) to set up automatic FTP transfers;...
Page 410: Ficu-1011
FICU-1011 Recommended Execute the portDisable command to disable ports with 0xFE or 0xFF areas. Action Severity WARNING FICU-1011 Message FMS mode has <timestamp>, [FICU-1011], <sequence-number>,, INFO, <system-name>, been enabled. Probable Cause Indicates that FMS mode has been enabled. Recommended No action is required. Action Severity INFO...
Page 411: Ficu-1018
FICU-1018 Recommended Execute the wwnaddress show command to display all the devices currently bound to areas. Action Execute wwnaddress unbind [WWN] command to release the reserved area from the device. Severity WARNING FICU-1018 Message FMSMODE <timestamp>, [FICU-1018], <sequence-number>,, WARNING, <system-name>, enable noticed swapped ports.
Page 412: Ficu-1022
FICU-1022 Recommended No action is required. Action Severity INFO FICU-1022 Message Detected <timestamp>, [FICU-1022], <sequence-number>,, ERROR, <system-name>, 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) in a Virtual Fabric disabled chassis.
Page 413: Fklb-1001
Chapter FKLB System Messages FKLB-1001 Message <timestamp>, [FKLB-1001], <sequence-number>,, WARNING, <system-name>, exchange <xid> overlapped, pid=<pid> Probable Cause Indicates that the FC kernel driver has timed out the exchange while the application is still active. When the FC kernel driver reuses the exchange, the application will overlap. This happens on a timed-out exchange;...
Page 414 FKLB-1001 Fabric OS Message Reference 53-1002448-01...
Page 415: Flod-1001
Chapter FLOD System Messages FLOD-1001 Message <timestamp>, [FLOD-1001], <sequence-number>,, 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 416: Flod-1005
FLOD-1005 FLOD-1005 Message <timestamp>, [FLOD-1005], <sequence-number>,, WARNING, <system-name>, Invalid received domain ID: <domain number>. 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>.
Page 417: Fspf-1001
Chapter FSPF System Messages FSPF-1001 Message <timestamp>, [FSPF-1001], <sequence-number>,, ERROR, <system-name>, Input Port <port number> out of range Probable Cause Indicates that the specified input port number is out of range as it does not exist on the switch. Recommended No action is required.
Page 418: Fspf-1005
FSPF-1005 FSPF-1005 Message <timestamp>, [FSPF-1005], <sequence-number>,, ERROR, <system-name>, Wrong Section Id <section number>, should be <section number>, input port = <port number> Probable Cause Indicates that an incorrect section ID was reported from the specified input port. The section ID is used to identify a set of switches that share an identical topology database.
Page 419: Fspf-1009
FSPF-1009 Recommended No action is required. Action Severity INFO FSPF-1009 Message <timestamp>, [FSPF-1009], <sequence-number>,, ERROR, <system-name>, ICL topology is invalid on local domain <domain number>. Probable Cause Indicates that there is a problem with the current ICL configuration. The ICL connectivity of one or more neighbor domains violates the requirement of symmetric ICL connections on both core blades.
Page 420 FSPF-1010 Fabric OS Message Reference 53-1002448-01...
Page 421: Fss-1001
Chapter FSS System Messages FSS-1001 Message <timestamp>, [FSS-1001], <sequence-number>,, WARNING, <system-name>, Component (<component name>) dropping HA data update (<update ID>). Probable Cause Indicates that an application has dropped a High Availability (HA) data update. Recommended For dual Control Processor (CP) system, enable the HA state synchronization using the haSyncStart Action command.
Page 422: Fss-1004
FSS-1004 If the problem persists, execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the supportSave command and contact your switch service provider. Severity WARNING FSS-1004 Message <timestamp>, [FSS-1004], <sequence-number>,, ERROR, <system-name>, Memory shortage. Probable Cause Indicates that the system ran out of memory.
Page 423: Fss-1007
FSS-1007 FSS-1007 Message <timestamp>, [FSS-1007], <sequence-number>,, CRITICAL, <system-name>, <component name>: Faulty Ethernet connection. Probable Cause Indicates that the Ethernet connection between the active CP and standby CP is not healthy. This error occurs when the standby CP does not respond to a request from the active CP within five seconds.
Page 424: Fss-1011
FSS-1011 Recommended Execute the supportSave command and contact your switch service provider. Action Severity WARNING FSS-1011 Message <timestamp>, [FSS-1011], <sequence-number>,, INFO, <system-name>, FSS Info: <Info Message>. Probable Cause Indicates an FSS-related informational message. Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1002448-01...
Page 425: Fssm-1002
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 of the active Control Processor (CP) is in synchronization with the HA state of the standby CP. If the standby CP is healthy, the failover will be nondisruptive.
Page 426 FSSM-1004 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. This causes a disruptive firmware upgrade or downgrade. Recommended For a dual CP system, execute the firmwareDownload command to load compatible firmware on the Action standby CP.
Page 427: Fw-1001
Chapter FW System Messages FW-1001 Message <timestamp>, [FW-1001], <sequence-number>,, INFO, <system-name>, <label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the internal temperature of the switch has changed. Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation.
Page 428: Fw-1004
FW-1004 Recommended This message generally appears when a fan fails. If so, a fan failure message accompanies this Action message. Replace the fan field-replaceable unit (FRU). Severity WARNING FW-1004 Message <timestamp>, [FW-1004], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value>...
Page 429: Fw-1011
FW-1011 FW-1011 Message <timestamp>, [FW-1011], <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 power supply is functioning properly. Recommended Set the high boundary above the normal operation range. Action Severity INFO...
Page 430: Fw-1035
FW-1035 Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation. Severity WARNING FW-1035 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>.
Page 431: Fw-1038
FW-1038 FW-1038 Message <timestamp>, [FW-1038], <sequence-number>,, WARNING, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the receive power value of the small form-factor pluggable (SFP) has fallen below the low boundary. The receive performance area measures the amount of incoming laser to help you determine if the SFP is in good working condition or not.
Page 432: Fw-1041
FW-1041 FW-1041 Message <timestamp>, [FW-1041], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the transmit power value of the small form-factor pluggable (SFP) has changed. The transmit performance area measures the amount of outgoing laser to help you determine if the SFP is in good working condition or not.
Page 433: Fw-1044
FW-1044 FW-1044 Message <timestamp>, [FW-1044], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the transmit power value of the small form-factor pluggable (SFP) has changed from a value outside of the acceptable range to a value within the acceptable range.
Page 434: Fw-1047
FW-1047 FW-1047 Message <timestamp>, [FW-1047], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the value of the small form-factor pluggable (SFP) voltage has risen above the high boundary. Recommended The supplied current of the SFP transceiver is outside of the normal range, indicating possible Action...
Page 435: Fw-1051
FW-1051 Recommended Configure the low threshold to 1 so that the threshold triggers an alarm when the value falls to 0 Action (Out_of_Range). If continuous or repeated alarms occur, replace the SFP before it deteriorates. Severity WARNING FW-1051 Message <timestamp>, [FW-1051], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>).
Page 436: Fw-1054
FW-1054 FW-1054 Message <timestamp>, [FW-1054], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the value of the small form-factor pluggable (SFP) Power on Hours has risen above the high boundary. High value indicate the SFP's maximum lifetime of use. Recommended Replace the SFP.
Page 437: Fw-1115
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 438: Fw-1118
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 439: Fw-1121
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 440: Fw-1124
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 441: Fw-1127
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 442: Fw-1129
FW-1129 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-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.
Page 443: Fw-1132
FW-1132 FW-1132 Message <timestamp>, [FW-1132], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. 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.
Page 444: Fw-1135
FW-1135 FW-1135 Message <timestamp>, [FW-1135], <sequence-number>,, INFO, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of fabric logins has risen above the high boundary. Fabric logins occur when a port or device initializes with the fabric. The event is called fabric login (FLOGI). Recommended No action is required.
Page 445: Fw-1138
FW-1138 FW-1138 Message <timestamp>, [FW-1138], <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 small form-factor pluggable (SFP) state changes has fallen below the low boundary. SFP state changes occur when the SFP is inserted or removed. A low number of SFP state changes means that the switch is functioning normally.
Page 446: Fw-1160
FW-1160 FW-1160 Message <timestamp>, [FW-1160], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of link failures that the port experiences has changed. Link loss errors occur when a link experiences a loss of signal and fails.
Page 447: Fw-1163
FW-1163 Losses of synchronization commonly cause link failures. If you receive concurrent loss of synchronization errors, troubleshoot the loss of synchronization. Severity WARNING FW-1163 Message <timestamp>, [FW-1163], <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 448: Fw-1166
FW-1166 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-1166 Message <timestamp>, [FW-1166], <sequence-number>,, WARNING, <system-name>, <Port Name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value>...
Page 449: Fw-1169
FW-1169 Recommended Check both ends of your cable connection. Verify that the cable and small form-factor pluggables Action (SFPs) are not faulty. Severity INFO FW-1169 Message <timestamp>, [FW-1169], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value>...
Page 450: Fw-1172
FW-1172 FW-1172 Message <timestamp>, [FW-1172], <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 protocol errors that the port experiences has changed. Occasional protocol errors occur due to software glitches. Persistent protocol errors occur due to hardware problems.
Page 451: Fw-1175
FW-1175 FW-1175 Message <timestamp>, [FW-1175], <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 protocol errors that the port experiences has changed from a value outside of the acceptable range to a value within the acceptable range.
Page 452: Fw-1178
FW-1178 FW-1178 Message <timestamp>, [FW-1178], <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 invalid words that the port experiences has risen above the high boundary.
Page 453: Fw-1181
FW-1181 FW-1181 Message <timestamp>, [FW-1181], <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 cyclic redundancy checks (CRC) that the port experiences has fallen below the low boundary.
Page 454: Fw-1184
FW-1184 FW-1184 Message <timestamp>, [FW-1184], <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 percentage of incoming traffic 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.
Page 455: Fw-1188
FW-1188 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-1188 Message <timestamp>, [FW-1188], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value>...
Page 456: Fw-1191
FW-1191 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> <Unit>. Probable Cause Indicates that the percentage of outgoing traffic that the port experiences has changed from a value outside of the acceptable range to a value within the acceptable range.
Page 457: Fw-1194
FW-1194 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 458: Fw-1197
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 459: Fw-1200
FW-1200 FW-1200 Message <timestamp>, [FW-1200], <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 C3 transmit time out frames has changed. Recommended Check the target device; it could be slow. Action Severity INFO...
Page 460: Fw-1204
FW-1204 Recommended Check the target device; it could be slow. Action Severity INFO 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.
Page 461: Fw-1207
FW-1207 FW-1207 Message <timestamp>, [FW-1207], <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 trunk utilization is between low and high thresholds. Recommended No action is required.
Page 462: Fw-1246
FW-1246 FW-1246 Message <timestamp>, [FW-1246], <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 end-to-end (EE) word frames that the switch receives has risen above the high boundary. Receive performance messages appear due to the number of word frames that travel from the configured S_ID to the D_ID pair.
Page 463: Fw-1249
FW-1249 FW-1249 Message <timestamp>, [FW-1249], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of end-to-end (EE) word frames that the switch transmits has fallen below the low boundary. Transmit performance messages appear due to the number of word frames that travel from the configured S_ID to the D_ID pair.
Page 464: Fw-1272
FW-1272 FW-1272 Message <timestamp>, [FW-1272], <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 frame types or commands that the port receives has changed. The port has received small computer system interface (SCSI) Read, SCSI Write, SCSI Read and Write, SCSI Traffic, or IP commands in a frame.
Page 465: Fw-1275
FW-1275 FW-1275 Message <timestamp>, [FW-1275], <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 frame types or commands that the port receives has changed from a value outside of the acceptable range to a value within the acceptable range.
Page 466: Fw-1298
FW-1298 FW-1298 Message <timestamp>, [FW-1298], <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 Telnet violations has risen above the high boundary. Telnet violations indicate that a Telnet connection request has been received from an unauthorized IP address. The TELNET_POLICY contains a list of internet protocol (IP) addresses that are authorized to establish Telnet connections to switches in the fabric.
Page 467: Fw-1301
FW-1301 FW-1301 Message <timestamp>, [FW-1301], <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 hypertext transfer protocol (HTTP) violations has fallen below the low boundary. HTTP violations indicate that a browser connection request has been received from an unauthorized IP address.
Page 468: Fw-1308
FW-1308 FW-1308 Message <timestamp>, [FW-1308], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of simple network management protocol read (RSNMP) violations has changed. RSNMP violations indicate that an SNMP get operation request has been received from an unauthorized IP address.
Page 469: Fw-1334
FW-1334 FW-1334 Message <timestamp>, [FW-1334], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of switch connection control policy (SCC) violations has risen above the high boundary. SCC violations indicate that an unauthorized switch tried to join the fabric. The SCC_POLICY contains a list of switches by World Wide Names (WWNs) that are allowed to be members of a fabric.
Page 470: Fw-1337
FW-1337 FW-1337 Message <timestamp>, [FW-1337], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of device cable connection (DCC) violations has fallen below the low boundary. DCC violations indicate that an unauthorized device tried to join the fabric. The DCC_POLICY allows for the specification of rules for binding device ports (typically host bus adaptor (HBA) ports) to specific switch ports.
Page 471: Fw-1339
FW-1339 FW-1339 Message <timestamp>, [FW-1339], <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 device cable connection (DCC) violations has changed from a value outside of the acceptable range to a value within the acceptable range.
Page 472: Fw-1342
FW-1342 FW-1342 Message <timestamp>, [FW-1342], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of login violations has risen above the high boundary. Login violations indicate that a login failure has been detected. Recommended Execute the errShow command to determine the IP location of the login attempt.
Page 473: Fw-1350
FW-1350 FW-1350 Message <timestamp>, [FW-1350], <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 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).
Page 474: Fw-1354
FW-1354 Recommended No action is required. Action Severity INFO 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 475: Fw-1356
FW-1356 FW-1356 Message <timestamp>, [FW-1356], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of authentication failures has changed. Authentication failures can occur for many reasons. The switch on the other side might not support the protocol, have an invalid certificate, not be signed properly, or send unexpected packets.
Page 476: Fw-1359
FW-1359 FW-1359 Message <timestamp>, [FW-1359], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of authentication failures has changed from a value outside of the acceptable range to a value within the acceptable range.
Page 477: Fw-1366
FW-1366 FW-1366 Message <timestamp>, [FW-1366], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of time service (TS) out-of-sync violations has risen above the high boundary. Recommended Responses to security-class messages depend on user policies.
Page 478: Fw-1369
FW-1369 FW-1369 Message <timestamp>, [FW-1369], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of no-FCS violations has fallen below the low boundary. This counter records how often the switch loses contact with the primary fabric configuration server (FCS) switch.
Page 479: Fw-1372
FW-1372 Recommended No action is required. Action Severity INFO FW-1372 Message <timestamp>, [FW-1372], <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 incompatible security database violations has changed. This violation indicates the number of secure switches with different version stamps have been detected.
Page 480: Fw-1375
FW-1375 Recommended Responses to security-class messages depend on user policies. Consult your security administrator Action for response strategies and policies. Severity WARNING FW-1375 Message <timestamp>, [FW-1375], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value>...
Page 481: Fw-1377
FW-1377 FW-1377 Message <timestamp>, [FW-1377], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of illegal commands has fallen below the low boundary. This counter tracks how many times commands allowed only on the primary fabric configuration server (FCS) switch have been executed on a non-primary FCS switch.
Page 482: Fw-1400
FW-1400 Recommended No action is required. Action Severity INFO FW-1400 Message <timestamp>, [FW-1400], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the flash usage percentage has changed. Flash increases and decreases slightly with normal operation of the switch.
Page 483: Fw-1403
FW-1403 FW-1403 Message <timestamp>, [FW-1403], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the CPU or memory usage is between the boundary limits. Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation.
Page 484: Fw-1407
FW-1407 Recommended No action is required. Action Severity CRITICAL FW-1407 Message <timestamp>, [FW-1407], <sequence-number>,, INFO, <system-name>, <Label>,is between high boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the memory usage is between high and middle thresholds. Recommended No action is required.
Page 485: Fw-1425
FW-1425 FW-1425 Message <timestamp>, [FW-1425], <sequence-number>,, INFO, <system-name>, Switch status changed from <Bad state> to HEALTHY. Probable Cause Indicates that the switch status has changed to a healthy state. This occurred because a policy is no longer violated. Recommended No action is required. Respond to this message as is appropriate to the particular policy of the Action end-user installation.
Page 486: Fw-1429
FW-1429 Recommended Replace the missing power supply. Action Severity WARNING FW-1429 Message <timestamp>, [FW-1429], <sequence-number>,, WARNING, <system-name>, Switch status change contributing factor: Power supplies are not redundant. Probable Cause Indicates that the switch status is not in a healthy state. This occurred because the power supplies are not in the correct slots for redundancy.
Page 487: Fw-1432
FW-1432 FW-1432 Message <timestamp>, [FW-1432], <sequence-number>,, WARNING, <system-name>, Switch status change contributing factor WWN: <Number Bad> 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 488: Fw-1435
FW-1435 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. The policy was set using the switchStatusPolicySet command. Recommended Execute the supportSave command to clear out the kernel flash.
Page 489: Fw-1438
FW-1438 FW-1438 Message <timestamp>, [FW-1438], <sequence-number>,, WARNING, <system-name>, Switch status change contributing factor Missing SFPs: <Number of missing SFPs> missing out of <Total number of SFPs> SFPs:config(<Percentage configured> percent,<Actual threshold limit>). (Port(s) <port list>). 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 490: Fw-1442
FW-1442 Recommended Verify that the event was planned. Action 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.
Page 491: Fw-1445
FW-1445 FW-1445 Message <timestamp>, [FW-1445], <sequence-number>,, INFO, <system-name>, Four power supplies are now required for 2X redundancy, Switch Status Policy values changed. Probable Cause Indicates that the switch now requires four power supplies and previous Switch Status Policy parameters will be overwritten to reflect this. The presence of an AP blade means that more than one power supply may be required to provide adequate power.
Page 492: Fw-1448
FW-1448 FW-1448 Message <timestamp>, [FW-1448], <sequence-number>,, WARNING, <system-name>, Switch status change contributing factor Error ports: <Number of Error ports> Error out of <Total number of ports> ports:config(<Percentage configured> percent,<actual threshold limit>). (Port(s) <port list>). Probable Cause Indicates that the switch is not in a healthy state. This occurred because the number of faulty ports are greater than or equal to the policy set by the switchStatusPolicySet command.
Page 493: Fw-1510
FW-1510 Recommended Reconfigure a valid e-mail address. Action Severity WARNING FW-1510 Message <timestamp>, [FW-1510], <sequence-number>,, WARNING, <system-name>, <Area string> threshold exceeded(High=<Threshold high>). Current value is <Current value>: Port <Port number> disabled. Probable Cause Indicates that the specified port is now disabled because the link on this port had multiple link failures that exceed Fabric Watch threshold on the port.
Page 494: Fw-1512
FW-1512 FW-1512 Message <timestamp>, [FW-1512], <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 link failures that the port experiences has changed and dropped below upper threshold boundary to a value within the acceptable range.
Page 495: Fw-1515
FW-1515 FW-1515 Message <timestamp>, [FW-1515], <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 number of signal losses that the port experiences has changed and crossed lower threshold boundary to a value within the acceptable range.
Page 496: Fw-1518
FW-1518 FW-1518 Message <timestamp>, [FW-1518], <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 protocol errors that the port experiences has changed and dropped below upper threshold boundary to a value within the acceptable range.
Page 497: Fw-1521
FW-1521 FW-1521 Message <timestamp>, [FW-1521], <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 number of invalid cyclic redundancy checks (CRC) that the port experiences crossed lower threshold boundary to a value within the acceptable range.
Page 498: Fw-1524
FW-1524 FW-1524 Message <timestamp>, [FW-1524], <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 percentage of incoming traffic that the port experiences has changed and dropped below upper threshold boundary to a value within the acceptable range.
Page 499: Fw-1527
FW-1527 FW-1527 Message <timestamp>, [FW-1527], <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 number of state changes that the port experiences has changed and crossed lower threshold boundary to a value within the acceptable range.
Page 500: Fw-1530
FW-1530 FW-1530 Message <timestamp>, [FW-1530], <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 link resets that the port experiences has changed and dropped below upper threshold boundary to a value within the acceptable range.
Page 501: Fw-1533
FW-1533 FW-1533 Message <timestamp>, [FW-1533], <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 trunk utilization crossed lower threshold boundary to in between low and high thresholds.
Page 502: Fw-3011
FW-3011 Recommended Respond to this message as it is appropriate to the particular policy of the end-user installation. Action Severity INFO FW-3011 Message <timestamp>, [FW-3011], <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 below threshold.
Page 503: Fw-3014
FW-3014 FW-3014 Message <timestamp>, [FW-3014], <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 the packet loss that the circuit experiences has changed. Recommended Respond to this message as is appropriate to the particular policy of the end-user installation. Action Severity INFO...
Page 504: Fw-3018
FW-3018 Recommended No action is required. Action Severity INFO FW-3018 Message <timestamp>, [FW-3018], <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 the number of state changes that the circuit experiences has changed. The state of the circuit has changed for either of the reason that if the circuit has gone offline or it has come online.
Page 505: Fw-3021
FW-3021 FW-3021 Message <timestamp>, [FW-3021], <sequence-number>,, WARNING, <system-name>, <Port Name>,<Label> is below low 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 is testing.
Page 506 FW-3022 Fabric OS Message Reference 53-1002448-01...
Page 507: Ham-1001
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 the specified device and Log="YES”...
Page 508: Ham-1005
HAM-1005 • 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 • Reboot:HAM •...
Page 509: Ham-1009
HAM-1007 Recommended The standby CP will take over and reset the active CP. The system will be non-redundant because Action the standby CP becomes the active CP. 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 510: Ham-1010
HAM-1010 Recommended Execute the reboot command to restart the switch manually. Action Severity CRITICAL HAM-1010 Message <timestamp>, [HAM-1010], <sequence-number>, SLOT cp-slot-number | CHASSIS, CRITICAL, <system-name>, Maunually trigger hareboot/reboot for recovery from OOM, when appropriate. Probable Cause Indicates that Out Of Memory (OOM) condition has been detected when the switch was not ready for warm recovery.
Page 511: Ham-1013
HAM-1013 HAM-1013 Message <timestamp>, [HAM-1013], <sequence-number>, SLOT cp-slot-number | CHASSIS, CRITICAL, <system-name>, <error message>. Probable Cause Indicates that the software watchdog detected termination of a restartable daemon, but could not restart the daemon. Recommended Manually initiate a restart or failover, if needed. Action Severity CRITICAL...
Page 512 HAM-1014 Fabric OS Message Reference 53-1002448-01...
Page 513: Hamk-1001
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 that the switch failed during the warm recovery. Recommended This event triggers a switch restart automatically and attempts a cold recovery. Execute the Action supportFtp command (as needed) to set up automatic FTP transfers;...
Page 514: Hamk-1004
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 CP is being reset due to a loss of heartbeat. Typically, this message is displayed when the standby CP has been restarted. Note that in certain circumstances a CP may experience a double reset and restart twice in a row.
Page 515: Hil-1101
Chapter HIL System Messages HIL-1101 Message <timestamp>, [HIL-1101], <sequence-number>,, ERROR, <system-name>, Slot <slot number> faulted, <nominal voltage> (<measured voltage>) is above threshold. Probable Cause Indicates that the blade voltage is above threshold. Recommended Replace the faulty blade or switch (for nonbladed switches). Action Severity ERROR...
Page 516: Hil-1104
HIL-1104 HIL-1104 Message <timestamp>, [HIL-1104], <sequence-number>,, ERROR, <system-name>, Blower <blower number> faulted, <nominal voltage> (<measured voltage>) is below threshold. Probable Cause Indicates that the fan voltage is below 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 517: Hil-1107
HIL-1107 HIL-1107 Message <timestamp>, [HIL-1107], <sequence-number>, FFDC, CRITICAL, <system-name>, Switch faulted, <nominal voltage> (<measured voltage>)above threshold. System preparing for reset. 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 518: Hil-1202
HIL-1202 If the fan continues to generate this message, replace the fan FRU. Severity WARNING HIL-1202 Message <timestamp>, [HIL-1202], <sequence-number>,, ERROR, <system-name>, Blower <blower number> faulted, speed (<measured speed> RPM) below threshold. Probable Cause Indicates that the specified fan speed (in RPMs) has fallen below the minimum threshold. Recommended Replace the fan FRU.
Page 519: Hil-1206
HIL-1206 HIL-1206 Message <timestamp>, [HIL-1206], <sequence-number>,, ERROR, <system-name>, Fan <fan number> sensor <sensor number>, speed (<measured speed> RPM) below threshold. Probable Cause Indicates that the specified fan speed (in RPMs) has fallen below the minimum threshold. This problem can quickly cause the switch to overheat. This message is specific to nonbladed switches and is not applicable to the Brocade 24000 or 48000.
Page 520: Hil-1301
HIL-1301 HIL-1301 Message <timestamp>, [HIL-1301], <sequence-number>,, WARNING, <system-name>, 1 blower failed or missing. Replace failed or missing blower assembly immediately. Probable Cause Indicates that a fan field-replaceable unit (FRU) has failed or has been removed. This message is often preceded by a low speed error message. This problem can cause the switch to overheat. Recommended Replace the affected fan FRU immediately.
Page 521: Hil-1305
HIL-1305 Recommended Replace the faulty fan FRUs immediately. Action 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.
Page 522: Hil-1308
HIL-1308 HIL-1308 Message <timestamp>, [HIL-1308], <sequence-number>,, ERROR, <system-name>, All fans failed. Replace failed fan FRUs immediately. Probable Cause Indicates that all fans have failed. This message is often preceded by a low fan speed message. Recommended Replace the faulty fan field-replaceable units (FRUs) immediately. Action Severity ERROR...
Page 523: Hil-1401
HIL-1401 If the fan continues to generate this message, it indicates oscillation between faulty and non-faulty behavior. Replace the switch because the fan is not field-replaceable. Severity INFO HIL-1401 Message <timestamp>, [HIL-1401], <sequence-number>,, WARNING, <system-name>, One fan FRU missing. Install fan FRU immediately. Probable Cause Indicates that one fan field-replaceable unit (FRU) has been removed.
Page 524: Hil-1501
HIL-1501 Recommended Install the missing fan FRUs immediately. Action Severity WARNING HIL-1501 Message <timestamp>, [HIL-1501], <sequence-number>,, WARNING, <system-name>, Slot <slot number>, high temperature (<measured temperature>). Probable Cause Indicates that the temperature of this blade has risen above the warning threshold. Recommended Run the fanShow command to verify all the fans are working properly.
Page 525: Hil-1504
HIL-1504 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. If the message persists, replace the faulty blade. Severity CRITICAL HIL-1504...
Page 526: Hil-1507
HIL-1507 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. Severity CRITICAL HIL-1507 Message <timestamp>, [HIL-1507], <sequence-number>, FFDC, CRITICAL, <system-name>, High temperature warning time expired.
Page 527: Hil-1510
HIL-1510 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. Severity CRITICAL HIL-1510 Message <timestamp>, [HIL-1510], <sequence-number>,, WARNING, <system-name>, Current temperature (<measured temperature>...
Page 528: Hil-1603
HIL-1603 HIL-1603 Message <timestamp>, [HIL-1603], <sequence-number>, FFDC, CRITICAL, <system-name>, <failure count> fans out of service. System is shutting down immediately. Probable Cause Indicates that the total fan failure count is greater than or equal to two. 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 529: Hil-1612
HIL-1612 Recommended Ensure fan units have same direction. Check fan directions with chassisshow command. Action Severity CRITICAL HIL-1612 Message <timestamp>, [HIL-1612], <sequence-number>,, CRITICAL, <system-name>, MISMATCH in PSU-FAN Air Flow direction.System shut down. Probable Cause Indicates that PSU FAN Air Flows are in reverse direction. System will be shut down. Applicable only to Brocade 6510.
Page 530 HIL-1650 Fabric OS Message Reference 53-1002448-01...
Page 531: Hlo-1001
Chapter HLO System Messages HLO-1001 Message <timestamp>, [HLO-1001], <sequence-number>, FFDC, ERROR, <system-name>, Incompatible Inactivity timeout <dead timeout> from port <port number>, correct value <value>. Probable Cause Indicates that the HLO message was incompatible with the value specified in the FSPF protocol. The Brocade switch will not accept FSPF frames from the remote switch.
Page 532 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 533: Hmon-1001
Chapter HMON System Messages HMON-1001 Message <timestamp>, [HMON-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, <Failure description> Probable Cause Indicates there was a problem reading an essential file containing configuration information from the nonvolatile storage device. This could be the result of a missing file or a corrupt file system. Recommended Run the firmwareDownload command to reinstall the firmware to your switch.
Page 534 HMON-1001 Fabric OS Message Reference 53-1002448-01...
Page 535: Hsl-1000
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 536: Hsl-1004
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 <InterfaceName> 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 537 HSL-1007 Recommended No action is required. Action Severity ERROR Fabric OS Message Reference 53-1002448-01...
Page 538 HSL-1007 Fabric OS Message Reference 53-1002448-01...
Page 539: Http-1001
Chapter HTTP System Messages HTTP-1001 Message <timestamp>, [HTTP-1001], <sequence-number>,, INFO, <system-name>, Switch PIDformat has changed to <current PID format>. Probable Cause Indicates that the PID format was changed by the administrator. Recommended No action is required. For more information on PID format, refer to the Fabric OS Administrator’s Action Guide.
Page 540 HTTP-1003 Fabric OS Message Reference 53-1002448-01...
Page 541: Ibd-1000
Chapter IBD System Messages IBD-1000 Message <timestamp>, [IBD-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 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 542 IBD-1000 Fabric OS Message Reference 53-1002448-01...
Page 543: Ibpd-1001
Chapter IBPD System Messages IBPD-1001 Message <timestamp>, [IBPD-1001], <sequence-number>,, WARNING, <system-name>, <Function name>:<Line number> initiator name length exceeds the <Max length limit> character limit [<Initiator name>] Probable Cause Indicates that the initiator name length exceeds the supported limit of characters. Recommended Change the initiator name, keeping the number of characters within the supported limit.
Page 544 IBPD-1003 Fabric OS Message Reference 53-1002448-01...
Page 545: Icpd-1001
Chapter ICPD System Messages ICPD-1001 Message <timestamp>, [ICPD-1001], <sequence-number>,, ERROR, <system-name>, Failed to allocate memory: (<function name>). Probable Cause Indicates that the specified function failed to allocate memory. Recommended Check memory usage on the switch using the memShow command. Action Reboot or power cycle the switch.
Page 546: Icpd-1005
ICPD-1005 Recommended Enable the iSNS Client service on a single switch in the fabric using the fosConfig command. Refer Action to the Fabric OS Command Reference for more information on this command. Severity WARNING ICPD-1005 Message <timestamp>, [ICPD-1005], <sequence-number>,, WARNING, <system-name>, iSCSI configuration between local switch (<local domain id>) and peer (<peer domain id>) is out of sync.
Page 547 ICPD-1008 Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1002448-01...
Page 548 ICPD-1008 Fabric OS Message Reference 53-1002448-01...
Page 549: Ipad-1000
Chapter IPAD System Messages IPAD-1000 Message <timestamp>, [IPAD-1000], <sequence-number>,, INFO, <system-name>, <Type of managed entity> <Instance number of managed entity> <Type of network interface> <Instance number of network interface> <Protocol address family> <Source of address change> <Value of address and prefix> <DHCP enabled or not>. Probable Cause Indicates that the local IP address has been changed.
Page 550: Ipad-1003
IPAD-1003 Recommended No action is required. Action Severity INFO IPAD-1003 Message <timestamp>, [IPAD-1003], <sequence-number>,, INFO, <system-name>, DNS parameters saved successfully. Probable Cause Indicates that the Domain Name System (DNS) parameters are saved successfully. Recommended No action is required. Action Severity INFO IPAD-1004 Message...
Page 551: Ips-1001
Chapter IPS System Messages IPS-1001 Message <timestamp>, [IPS-1001], <sequence-number>,, WARNING, <system-name>, <message> FCIP License Not Installed (<error>) Probable Cause Indicates that the FCIP license is not installed on the switch. Recommended Run the licenseShow command to check the installed licenses on the switch. Contact your switch Action supplier for a FCIP license.
Page 552: Ips-1004
IPS-1004 IPS-1004 Message <timestamp>, [IPS-1004], <sequence-number>,, WARNING, <system-name>, Port Config Mode Mismatch slot (<slot>) port(ge<port>): current mode is (<current mode>) 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.
Page 553 IPS-1007 Recommended Change the tunnel configuration to remove IPSec configurations or insert a GA2 revised FX8-24 Action blade. Severity WARNING Fabric OS Message Reference 53-1002448-01...
Page 554 IPS-1007 Fabric OS Message Reference 53-1002448-01...
Page 555: Isns-1001
Chapter ISNS System Messages ISNS-1001 Message <timestamp>, [ISNS-1001], <sequence-number>,, INFO, <system-name>, Configuration peering with external iSNS server <New config iSNS server IP address> slot/port <New config Slot number>/ge<New config port number> (current <Current iSNS server IP address> <Current slot number>/ge<Current port number>). Probable Cause Indicates that the user has issued the isnscCfg command.
Page 556: Isns-1004
ISNS-1004 ISNS-1004 Message <timestamp>, [ISNS-1004], <sequence-number>,, WARNING, <system-name>, Timeout refreshing iSNS database with iSNS server <iSNS server IP address> slot/port <Slot number>/ge<Port number> Reg-Period <Registration-Period in seconds>. Probable Cause Indicates that the internet storage name service (iSNS) client failed to receive a successful response for a DevAttrQry within the specified Registration-Period.
Page 557: Isns-1009
ISNS-1009 Recommended No action is required. You may change the configuration and retry the peering with the external Action iSNS server. Severity INFO ISNS-1009 Message <timestamp>, [ISNS-1009], <sequence-number>,, INFO, <system-name>, Peering with external iSNS server <iSNS server IP address> not started because no virtual targets found.
Page 558: Isns-1013
ISNS-1013 ISNS-1013 Message <timestamp>, [ISNS-1013], <sequence-number>,, WARNING, <system-name>, iSNS server connection failure. 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 559: Kac-1002
Chapter KAC System Messages KAC-1002 Message <timestamp>, [KAC-1002], <sequence-number>,, ERROR, <system-name>, KAC(<Key Vault Type>) communication Error: Error connecting to <Backup or Primary>. Probable Cause Indicates that the key archival client is unable to communicate with the primary or backup key vault.
Page 560: Kac-1007
KAC-1007 KAC-1007 Message <timestamp>, [KAC-1007], <sequence-number>,, WARNING, <system-name>, KAC put key to key vault failed, LUN=<LUN Number>, keyID=<Key ID Value>, errno=<Error Number>. 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...
Page 561: Kac-1011
KAC-1011 KAC-1011 Message <timestamp>, [KAC-1011], <sequence-number>,, WARNING, <system-name>, Putting the dummy DEK to the KV <Keyvault IP Address> failed. Dummy DEK: <Dummy Key Id>, KeyCount: <Key Count>. Error code=<Error code>, string=<Error string>. Probable Cause Indicates that putting the Dummy failed to keyvault. Recommended No action is required.
Page 562: Kac-1015
KAC-1015 Recommended No action is required. Action Severity WARNING KAC-1015 Message <timestamp>, [KAC-1015], <sequence-number>,, ERROR, <system-name>, KAC(<Key Vault Type>) communication Error: Error connecting to <Key Vault IP>. Error code=<Error code>, string=<Error string>. Probable Cause Indicates that key archival client is unable to communicate with the primary or backup key vault. Recommended Change the switch key vault settings and/or ensure that the configured key vault is operational.
Page 563: Kswd-1001
Chapter KSWD System Messages KSWD-1001 Message <timestamp>, [KSWD-1001], <sequence-number>, FFDC, WARNING, <system-name>, <Software component>:<Software component Process ID> failed to refresh (<Current time>:<Refresh time>). Probable Cause Indicates 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 564 KSWD-1002 Fabric OS Message Reference 53-1002448-01...
Page 565: Ktrc-1001
Chapter KTRC System Messages KTRC-1001 Message <timestamp>, [KTRC-1001], <sequence-number>,, WARNING, <system-name>, Dump memory size exceeds dump file size Probable Cause Indicates the dump memory size has exceeded the dump file size. Recommended No action is required. Action Severity WARNING KTRC-1002 Message <timestamp>, [KTRC-1002], <sequence-number>,, INFO, <system-name>, Concurrent trace dumping.
Page 566: Ktrc-1005
KTRC-1005 Recommended No action is required. Action Severity ERROR KTRC-1005 Message <timestamp>, [KTRC-1005], <sequence-number>,, ERROR, <system-name>, Trace initialization failed. <Reason initialization failed>. <Internal error code>. Probable Cause Indicates that a trace was unable to initialize. Recommended No action is required. Action Severity ERROR...
Page 567: L2Ss-1001
Chapter L2SYS System Messages L2SS-1001 Message <timestamp>, [L2SS-1001], <sequence-number>,, ERROR, <system-name>, Linux socket error - error reason: <reason>, socket name: <socketname>, error name: <errorname>. Probable Cause Indicates that an error has occurred in the Linux socket. Recommended Restart the Layer 2 system daemon (l2sysd). Action Severity ERROR...
Page 568: L2Ss-1004
L2SS-1004 L2SS-1004 Message <timestamp>, [L2SS-1004], <sequence-number>,, ERROR, <system-name>, FDB error: Error in creating AVL tree. Probable Cause Indicates that the l2sys has encountered an error while initializing the AVL tree. Recommended Restart the l2sys 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>...
Page 569: L2Ss-1008
L2SS-1008 L2SS-1008 Message <timestamp>, [L2SS-1008], <sequence-number>,, INFO, <system-name>, Hardware gid limit reached on chip <Chip_id>, gid limit at <Max_gid>. Probable Cause Indicates that all the dynamic Group IDs (GIDs) are allocated. Recommended Clear some of the ACL entries using the clear counters access-list mac command. Action Severity INFO...
Page 570 L2SS-1008 Fabric OS Message Reference 53-1002448-01...
Page 571: L3Ss-1004
Chapter L3SS System Messages L3SS-1004 Message <timestamp>, [L3SS-1004], <sequence-number>,, ERROR, <system-name>, <Function Name>, <Line No>: HW/Driver Error (possibly the CAM is full): <HW Error Message>, rc=<Error Code>. Probable Cause Indicates an error in the hardware or the driver of the Layer 3 subsystem (L3SS). The L3SS may have passed invalid parameters or the hardware content-addressable memory (CAM) may be full.
Page 572 L3SS-1004 Fabric OS Message Reference 53-1002448-01...
Page 573: Lacp-1001
Chapter LACP System Messages LACP-1001 Message <timestamp>, [LACP-1001], <sequence-number>,, ERROR, <system-name>, <module> Error opening socket (<error>). Probable Cause Indicates that initialization of the specified module within the Link Aggregation Control Protocol (LACP) daemon has failed. Recommended Download a new firmware using the firmwareDownload command. Action Severity ERROR...
Page 574 LACP-1002 Fabric OS Message Reference 53-1002448-01...
Page 575: Lance-1000
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 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 576 LANCE-1000 Fabric OS Message Reference 53-1002448-01...
Page 577: Lfm-1001
Chapter LFM System Messages LFM-1001 Message <timestamp>, [LFM-1001], <sequence-number>,, INFO, <system-name>, The Logical Fabric Manager service is disabled. Probable Cause Indicates that the Logical Fabric Manager service is disabled. Note that the Logical Fabric Manager service is enabled by the factory setting and it is not user configurable. Recommended No action is required.
Page 578: Lfm-1004
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...
Page 579: Log-1000
Chapter LOG System Messages LOG-1000 Message <timestamp>, [LOG-1000], <sequence-number>,, INFO, <system-name>, Previous message repeated <repeat count> 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.
Page 580: Log-1003
LOG-1003 LOG-1003 Message <timestamp>, [LOG-1003], <sequence-number>,, INFO, <system-name>, The log has been cleared. Probable Cause Indicates the persistent error log has been cleared. Recommended No action is required. Action Severity INFO LOG-1004 Message <timestamp>, [LOG-1004], <sequence-number>,, INFO, <system-name>, Log message <Log message that has been blocked>...
Page 581: Lsdb-1001
Chapter LSDB System Messages LSDB-1001 Message <timestamp>, [LSDB-1001], <sequence-number>,, ERROR, <system-name>, Link State ID <link state ID> out of range. Probable Cause Indicates the specified link state database ID is out of the acceptable range. The valid link state ID is the same as the valid domain ID, whose range is from 1 through 239.
Page 582: Lsdb-1004
LSDB-1004 Recommended Run the switchDisable and switchEnable commands. A new local link state record is generated Action during the switch enable. Severity CRITICAL LSDB-1004 Message <timestamp>, [LSDB-1004], <sequence-number>,, WARNING, <system-name>, No Link State Record for domain <local domain>. Probable Cause Indicates there is no link state record for the specified local domain.
Page 583: Mcast_Ss-1001
Chapter MCAST_SS System Messages MCAST_SS-1001 Message <timestamp>, [MCAST_SS-1001], <sequence-number>,, ERROR, <system-name>, Socket Error: <op> (<reason>) for socket <sockname> the error code<errorname>. Probable Cause Indicates error encountered in Linux socket. Recommended Try restarting the mcast_ssd daemon. Action Severity ERROR MCAST_SS-1002 Message <timestamp>, [MCAST_SS-1002], <sequence-number>,, ERROR, <system-name>, Socket Error: <op>...
Page 584: Mcast_Ss-1005
MCAST_SS-1005 Recommended Try restarting the mcast_ssd daemon. Action Severity ERROR MCAST_SS-1005 Message <timestamp>, [MCAST_SS-1005], <sequence-number>,, ERROR, <system-name>, Message error: Invalid message type <type> expecting <value1> or <value2> or <value3>. Probable Cause Indicates that type in the message recieved from driver is invalid. Recommended Try restarting the mcast_ssd daemon.
Page 585: Mcast_Ss-1009
MCAST_SS-1009 Recommended Try restarting the mcast_ssd daemon. Action Severity ERROR MCAST_SS-1009 Message <timestamp>, [MCAST_SS-1009], <sequence-number>,, ERROR, <system-name>, L2SS error : <op> (<reason>) vlan <vid> mac <macaddr>. Probable Cause Indicates that mcast_ss encountered L2SS related errors. Recommended Try restarting the mcast_ssd daemon. Action Severity ERROR...
Page 586: Mcast_Ss-1013
MCAST_SS-1013 Recommended Try restarting the mcast_ssd daemon. Action Severity ERROR MCAST_SS-1013 Message <timestamp>, [MCAST_SS-1013], <sequence-number>,, ERROR, <system-name>, Snooping DB error : <op> (<reason>) Group Not found - Vlan <vid> group <grpaddr>. Probable Cause Indicates that the group address lookup for a VLAN failed. Recommended Try restarting the mcast_ssd daemon.
Page 587: Mcast_Ss-1017
MCAST_SS-1017 Recommended Try restarting the mcast_ssd daemon. Action Severity ERROR MCAST_SS-1017 Message <timestamp>, [MCAST_SS-1017], <sequence-number>,, ERROR, <system-name>, Learning error: <op> (<reason>) Invalid number <port> for ifindex <ifindex>. Probable Cause Indicates that mcast_ss encountered an error while learning MAC addresses. Recommended Try restarting the mcast_ssd daemon.
Page 588 MCAST_SS-1020 Recommended Try restarting the mcast_ssd daemon. Action Severity ERROR Fabric OS Message Reference 53-1002448-01...
Page 589: Mfic-1001
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 that the system is temporarily out of resources. Recommended This error is often transitory. Action Execute the reBoot or haFailover commands (if applicable). If the problem persists, execute the supportFtp command (as needed) to set up automatic FTP transfers;...
Page 590: Mfic-1003
MFIC-1003 MFIC-1003 Message <timestamp>, [MFIC-1003], <sequence-number>,, WARNING, <system-name>, Effective Insistent domain ID for the fabric changed from <state> to <state>. Probable Cause Indicates that one or more switches joined the fabric with an insistent domain ID (IDID) mode setting that is different from the current effective IDID mode for the fabric. This message also occurs when the IDID for the fabric has been turned on or off.
Page 591: Mpth-1001
Chapter MPTH System Messages MPTH-1001 Message <timestamp>, [MPTH-1001], <sequence-number>, FFDC, ERROR, <system-name>, Null parent, lsId = <number>. 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 592 MPTH-1003 Fabric OS Message Reference 53-1002448-01...
Page 593: Mq-1004
Chapter MQ System Messages MQ-1004 Message <timestamp>, [MQ-1004], <sequence-number>,, ERROR, <system-name>, mqRead, queue = <queue name>, queue ID = <queue ID>, type = <message type> Probable Cause Indicates an unexpected message has been received in the specified message queue. The queue name is always fspf_q.
Page 594: Mq-1006
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-1002448-01...
Page 595: Ms-1001
Chapter MS System Messages MS-1001 Message <timestamp>, [MS-1001], <sequence-number>,, WARNING, <system-name>, MS Platform Segmented port=<port number> (0x<port number (hex)>) (<reason for segmentation> <domain> (0x<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 596: Ms-1003
MS-1003 • <GCAP Rejected (reason =BUSY) by> Run the firmwareDownload command to upgrade the firmware level on the switch to a level that supports RCS. RCS is supported in Fabric OS v2.6, v3.1 and greater, and v4.1 and greater. • <Reject EXGPLDB from>...
Page 597: Ms-1005
MS-1005 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 MS-1005 Message <timestamp>, [MS-1005], <sequence-number>,, ERROR, <system-name>, MS Invalid CT Response from d=<domain>. Probable Cause Indicates the management server (MS) received an invalid common transport (CT) response from the switch domain.
Page 598: Ms-1009
MS-1009 If the error persists, check the available memory on the switch using the memShow command. Severity ERROR 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>.
Page 599: Ms-1023
MS-1023 Recommended No action is required. Action Severity INFO 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...
Page 600: Ms-1026
MS-1026 MS-1026 Message <timestamp>, [MS-1026], <sequence-number>,, WARNING, <system-name>, MS Platform disabled port <port number> domain <domain> to block enabling Platform service through merge operation. Probable Cause Indicates the management server (MS) has disabled E-port port number connected to domain because implicit enable operation of platform service is blocked. Recommended Enable Platform service on the switch and renable the port to join the fabric.
Page 601: Mstp-1001
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 602: Mstp-2002
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 603: Mstp-2006
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 604 MSTP-2006 Fabric OS Message Reference 53-1002448-01...
Page 605: Nbfs-1001
Chapter NBFS System Messages NBFS-1001 Message <timestamp>, [NBFS-1001], <sequence-number>,, INFO, <system-name>, Duplicate E_Port SCN from port <portnumber> in state <state change name> (<state change number>) Probable Cause Indicates a duplicate E_Port State Change Number was reported. The neighbor finite state machine (NBFSM) states are as follows: •...
Page 606: Nbfs-1003
NBFS-1003 Recommended Run the nbrStateShow command to check the neighbor state of the port listed in the message. If it Action is FULL, then this message can safely be ignored. Otherwise, run the portDisable and portEnable commands to refresh the port. Severity ERROR NBFS-1003...
Page 607: Ns-1001
Chapter NS System Messages NS-1001 Message <timestamp>, [NS-1001], <sequence-number>,, WARNING, <system-name>, The response for request 0x<CT command code> from remote switch 0x<Domain Id> is larger than the max frame size the remote switch can support! Probable Cause Indicates the response payload exceeds the maximum frame size the remote switch can handle. Recommended Run the firmwareDownload command to upgrade the remote switch with firmware v4.3 or higher, Action...
Page 608: Ns-1004
NS-1004 Recommended To avoid disruption of traffic in the event of an unplanned failover, schedule a firmwareDownload so Action that the active and standby CPs have the same firmware version. Reduce the local device count to follow the capability of the lowest version of firmware. Severity INFO NS-1004...
Page 609: Ns-1007
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 610: Ns-1011
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 611: Nsm-1001
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 specified 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 612: Nsm-1003
NSM-1003 NSM-1003 Message <timestamp>, [NSM-1003], <sequence-number>,, INFO, <system-name>, Interface <Interface Name> is link down. Probable Cause Indicates that the specified interface is offline because the link is down. Recommended Check whether the connectivity between the peer ports is proper, and the remote link is up using Action the show interface command.
Page 613: Nsm-1007
NSM-1007 NSM-1007 Message <timestamp>, [NSM-1007], <sequence-number>,, INFO, <system-name>, Chassis is <status>. Probable Cause Indicates whether chassis is enabled or disabled. Recommended No action is required. Action Severity INFO NSM-1008 Message <timestamp>, [NSM-1008], <sequence-number>,, INFO, <system-name>, Blade is <status>. Probable Cause Indicates whether the specified blade is enabled or disabled.
Page 614: Nsm-1011
NSM-1011 NSM-1011 Message <timestamp>, [NSM-1011], <sequence-number>,, INFO, <system-name>, OperationalEndpointMode changed from <Mode_old> to <Mode_new> for interface <InterfaceName>. Probable Cause Indicates that the interface Operational Endpoint mode has been changed. Recommended No action is required. Action Severity INFO NSM-1012 Message <timestamp>, [NSM-1012], <sequence-number>,, INFO, <system-name>, VLAN classifier group <group_id>...
Page 615: Nsm-1015
NSM-1015 NSM-1015 Message <timestamp>, [NSM-1015], <sequence-number>,, INFO, <system-name>, VLAN classifier rule <rule_id> is deleted. Probable Cause Indicates that the specified VLAN classifier rule has been deleted. Recommended No action is required. Action Severity INFO NSM-1016 Message <timestamp>, [NSM-1016], <sequence-number>,, INFO, <system-name>, VLAN classifier rule <rule_id>...
Page 616: Nsm-1019
NSM-1019 NSM-1019 Message <timestamp>, [NSM-1019], <sequence-number>,, INFO, <system-name>, Interface <InterfaceName> is administratively up. Probable Cause Indicates that the administrative status of the specified interface has changed to up. Recommended No action is required. Action Severity INFO NSM-1020 Message <timestamp>, [NSM-1020], <sequence-number>,, INFO, <system-name>, Interface <InterfaceName>...
Page 617: Onmd-1000
Chapter ONMD System Messages ONMD-1000 Message <timestamp>, [ONMD-1000], <sequence-number>,, INFO, <system-name>, LLDP is enabled. Probable Cause Indicates that the Link Layer Discovery Protocol (LLDP) is enabled globally. Recommended No action is required. Action Severity INFO ONMD-1001 Message <timestamp>, [ONMD-1001], <sequence-number>,, INFO, <system-name>, LLDP is disabled.
Page 618: Onmd-1004
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 the specified interface. Recommended No action is required. Action Severity INFO ONMD-1005 Message...
Page 619: Pdm-1001
Chapter PDM System Messages PDM-1001 Message <timestamp>, [PDM-1001], <sequence-number>,, WARNING, <system-name>, Failed to parse the pdm config. Probable Cause Indicates the parity data manager (PDM) process could not parse the configuration file. This might be caused by a missing configuration file during the installation. Recommended Run the firmwareDownload command to reinstall the firmware.
Page 620: Pdm-1004
PDM-1004 PDM-1004 Message <timestamp>, [PDM-1004], <sequence-number>,, WARNING, <system-name>, PDM memory shortage. Probable Cause Indicates the parity data manager (PDM) process ran out of memory. Recommended Reboot or power cycle the switch. Action If the message persists, run the supportFtp command (as needed) to set up automatic FTP transfers;...
Page 621: Pdm-1008
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 622: Pdm-1011
PDM-1011 PDM-1011 Message <timestamp>, [PDM-1011], <sequence-number>,, WARNING, <system-name>, File read failed: <file name>, Length(read=<Number of character read>, expected=<Number of characters expected>), errno=<errno returned by read>. Probable Cause Indicates the parity data manager (PDM) process could not read data from the specified file. Recommended Run the firmwareDownload command to reinstall the firmware.
Page 623: Pdm-1017
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 624: Pdm-1021
PDM-1021 PDM-1021 Message <timestamp>, [PDM-1021], <sequence-number>,, WARNING, <system-name>, Failed to download area port map. 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;...
Page 625: Pdm-1025
PDM-1025 Recommended Configure DNS with IPv4 addresses. Action Severity WARNING PDM-1025 Message <timestamp>, [PDM-1025], <sequence-number>,, WARNING, <system-name>, IPv6 is configured for LDAP. Probable Cause Indicates that the parity data manager (PDM) cannot synchronize with its peer because the LDAP server is configured for IPv6 addresses. IPv6 is not supported by older firmware. Recommended Configure the LDAP server with IPv4 addresses.
Page 626 PDM-1026 Fabric OS Message Reference 53-1002448-01...
Page 627: Pdtr-1001
Chapter PDTR System Messages PDTR-1001 Message <timestamp>, [PDTR-1001], <sequence-number>,, INFO, <system-name>, <informational message>. Probable Cause Indicates information has been written to the panic dump files. The watchdog register codes are as follows: • 0x10000000 bit set means that the watch dog timer (WDT) forced a core reset. •...
Page 628 PDTR-1002 Fabric OS Message Reference 53-1002448-01...
Page 629: Plat-1000
Chapter PLAT System Messages PLAT-1000 Message <timestamp>, [PLAT-1000], <sequence-number>, FFDC, CRITICAL, <system-name>, <Function name> <Error string> Probable Cause Indicates nonrecoverable PCI errors have been detected. Recommended The system will be faulted and might automatically reboot. Action If the system does not reboot, then try issuing the reboot command from a command-line prompt. Run the supportFtp command (as needed) to set up automatic FTP transfers;...
Page 630: Plat-1003
PLAT-1003 Recommended Reboot the CP if it does not reboot itself. Reseat the CP if rebooting does not solve the problem. If Action the problem still persists, then replace the CP. Severity CRITICAL PLAT-1003 Message <timestamp>, [PLAT-1003], <sequence-number>, FFDC, CRITICAL, <system-name>, <Info message>...
Page 631: Pmgr-1001
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 632: Pmgr-1005
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) to switch <FID> succeeded. Probable Cause Indicates the successful attempt to move the ports to the specified switch. Recommended No action is required. Action Severity INFO...
Page 633: Pmgr-1009
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 634 PMGR-1011 Fabric OS Message Reference 53-1002448-01...
Page 635: Port-1003
Chapter PORT System Messages PORT-1003 Message <timestamp>, [PORT-1003], <sequence-number>,, WARNING, <system-name>, Port <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 636: Port-1006
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 637: Port-1010
PORT-1010 Recommended No action is required. Action Severity INFO PORT-1010 Message <timestamp>, [PORT-1010], <sequence-number>,, INFO, <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 638 PORT-1010 Fabric OS Message Reference 53-1002448-01...
Page 639: Ps-1000
Chapter PS System Messages PS-1000 Message <timestamp>, [PS-1000], <sequence-number>, FFDC, CRITICAL, <system-name>, Failed to initialize Advanced Performance Monitoring. Probable Cause Indicates an unexpected software error has occurred in Advanced Performance Monitoring (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 640: Ps-1003
PS-1003 PS-1003 Message <timestamp>, [PS-1003], <sequence-number>,, WARNING, <system-name>, Failed to set end-to-end monitoring mask on ISL ports. 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 641: Ps-1007
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 642 PS-1009 Fabric OS Message Reference 53-1002448-01...
Page 643: Pswp-1001
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 644: Pswp-1004
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 645: Ras-1001
Chapter RAS System Messages RAS-1001 Message <timestamp>, [RAS-1001], <sequence-number>,, INFO, <system-name>, First failure data capture (FFDC) event occurred. Probable Cause Indicates that a first failure data capture (FFDC) event occurred and the failure data has been captured. Recommended Execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the Action supportSave command and contact your switch service provider.
Page 646: Ras-1005
RAS-1005 RAS-1005 Message <timestamp>, [RAS-1005], <sequence-number>, FFDC, WARNING, <system-name>, Software 'assert' error detected. Probable Cause Indicates an internal software error. Recommended Execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the Action supportSave command and contact your switch service provider. Severity WARNING RAS-1006...
Page 647: Ras-2002
RAS-2002 RAS-2002 Message <timestamp>, [RAS-2002], <sequence-number>, INFO, <system-name>, Audit message log is disabled. Probable Cause Indicates that the audit message log has been disabled. Recommended No action is required. Action Severity INFO RAS-2003 Message <timestamp>, [RAS-2003], <sequence-number>, INFO, <system-name>, Audit message class configuration has been changed to <New audit class configuration>.
Page 648: Ras-3003
RAS-3003 RAS-3003 Message <timestamp>, [RAS-3003], <sequence-number>, WARNING, <system-name>, USB storage device was unplugged before it was disabled. Probable Cause Indicates that the USB storage device was unplugged before it was disabled. Recommended Disable the USB storage device using the usbstorage -d command before unplugged it from the Action system.
Page 649: Rcs-1001
Chapter RCS System Messages RCS-1001 Message <timestamp>, [RCS-1001], <sequence-number>,, INFO, <system-name>, RCS has been disabled. Some switches in the fabric do not support this feature. Probable Cause Indicates that the RCS feature has been disabled on the local switch because not all switches in the fabric support RCS or the switch is in nonnative mode.
Page 650: Rcs-1004
RCS-1004 RCS-1004 Message <timestamp>, [RCS-1004], <sequence-number>,, ERROR, <system-name>, Application(<application name>) not registered.(<error string>) Probable Cause Indicates that a specified application did not register with RCS. Recommended Run the haShow command to view the HA state. Action Run the haDisable and the haEnable commands. Run the rcsInfoShow command to view RCS capability on the fabric.
Page 651: Rcs-1007
RCS-1007 If the reject is in the SFC phase, check if the application license exists for the remote domain and if the application data is compatible. 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>.
Page 652: Rcs-1010
RCS-1010 RCS-1010 Message <timestamp>, [RCS-1010], <sequence-number>,, ERROR, <system-name>, Domain <domain number> is RCS incapable. Disabled <Number of E-ports disabled> E-port(s) connected to this domain. Probable Cause Indicates the remote domain is non-RCS and necessary action need to be taken to join RCS fabric. Recommended Configure the remote domain as RCS capable switch.
Page 653: Rkd-1001
Chapter RKD System Messages RKD-1001 Message <timestamp>, [RKD-1001], <sequence-number>,, INFO, <system-name>, <Re-key type (First time encryption/Rekey/Write Metadata)> operation <Re-key action (started/completed/cancelled)>. Target: <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 654: Rkd-1004
RKD-1004 Recommended Correct the error and resume. Action Severity CRITICAL 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>...
Page 655: Rmon-1001
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 the remote monitoring (RMON) alarm. Recommended Check the traffic on the interface using the show interface command. Action Note that you can use the show interface command to check the traffic on the interface, provided the statistics on the interface is not cleared using the clear counters command.
Page 656 RMON-1002 Fabric OS Message Reference 53-1002448-01...
Page 657: Rpcd-1001
Chapter RPCD System Messages RPCD-1001 Message <timestamp>, [RPCD-1001], <sequence-number>,, WARNING, <system-name>, Authentication Error: client \"<IP address>\" has bad credentials: <bad user name and password pair> Probable Cause Indicates an authentication error was reported. The specified client IP address has faulty credentials.
Page 658: Rpcd-1004
RPCD-1004 RPCD-1004 Message <timestamp>, [RPCD-1004], <sequence-number>,, WARNING, <system-name>, Invalid certificate file. Secure RPCd is disabled. Probable Cause Indicates the SSL certificate file has been corrupted. Recommended To enable RPCD in Secure mode, install a valid SSL certificate in the switch. Action Severity WARNING...
Page 659: Rte-1001
Chapter RTE System Messages RTE-1001 Message <timestamp>, [RTE-1001], <sequence-number>,, ERROR, <system-name>, Detected route inconsistency. If connectivity issues arise, all ISLs connected to this chassis need to be bounced to recover. Probable Cause Indicates that the constraints that are used to determine the paths for Dynamic Path Selection (DPS) are not synchronized from active control processor (CP) to standby CP during the failover.
Page 660 RTE-1001 Fabric OS Message Reference 53-1002448-01...
Page 661: Rtwr-1001
Chapter RTWR System Messages RTWR-1001 Message <timestamp>, [RTWR-1001], <sequence-number>,, ERROR, <system-name>, RTWR <routine: error message> 0x<detail 1>, 0x<detail 2>, 0x<detail 3>, 0x<detail 4>, 0x<detail 5> Probable Cause Indicates that an error has occurred in the RTWR. The message provides the name of the routine having the error, and more specific error information.
Page 662: Rtwr-1003
RTWR-1003 RTWR-1003 Message <timestamp>, [RTWR-1003], <sequence-number>,, INFO, <system-name>, <module name>: RTWR retry <number of times retried> to domain <domain ID>, iu_data <first word of iu_data> Probable Cause Indicates 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 663: Scn-1001
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 664: Scn-1002
SCN-1002 SCN-1002 Message <timestamp>, [SCN-1002], <sequence-number>, FFDC, ERROR, <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 665: Sec-1001
Chapter SEC System Messages SEC-1001 Message <timestamp>, [SEC-1001], <sequence-number>,, ERROR, <system-name>, RCS process fails: <reason code>. 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 666: Sec-1003
SEC-1003 SEC-1003 Message <timestamp>, [SEC-1003], <sequence-number>,, WARNING, <system-name>, Fail to download security data to domain <Domain number> after <Number of retires> retries. Probable Cause Indicates the specified domain 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 667: Sec-1007
SEC-1007 SEC-1007 Message <timestamp>, [SEC-1007], <sequence-number>,, INFO, <system-name>, Security violation: Unauthorized host with IP address <IP address of the violating 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 668: Sec-1016
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 violation: Unauthorized host with IP address <IP address of the violating host> tries to establish SSH connection. Probable Cause Indicates a security violation was reported.
Page 669: Sec-1025
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 670: Sec-1029
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 671: Sec-1032
SEC-1032 SEC-1032 Message <timestamp>, [SEC-1032], <sequence-number>,, ERROR, <system-name>, Empty FCS list is not allowed. 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 672: Sec-1035
SEC-1035 SEC-1035 Message <timestamp>, [SEC-1035], <sequence-number>,, ERROR, <system-name>, Invalid device WWN <device WWN>. Probable Cause Indicates the specified world wide name (WWN) is invalid. Recommended Enter the correct WWN value. Action Severity ERROR SEC-1036 Message <timestamp>, [SEC-1036], <sequence-number>,, ERROR, <system-name>, Device name <device name>...
Page 673: Sec-1040
SEC-1040 SEC-1040 Message <timestamp>, [SEC-1040], <sequence-number>,, ERROR, <system-name>, Invalid portlist (<port list>). Cannot combine * with port member in the same portlist. Probable Cause Indicates the port list contains the wildcard asterisk (*) character. You cannot use the asterisk in a port list.
Page 674: Sec-1044
SEC-1044 Recommended Use valid syntax when entering port ranges. Action Severity ERROR SEC-1044 Message <timestamp>, [SEC-1044], <sequence-number>,, ERROR, <system-name>, Duplicate member <member ID> in (<List>). 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.
Page 675: Sec-1049
SEC-1049 SEC-1049 Message <timestamp>, [SEC-1049], <sequence-number>,, ERROR, <system-name>, Invalid switch name <switch name>. 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 676: Sec-1052
SEC-1052 SEC-1052 Message <timestamp>, [SEC-1052], <sequence-number>,, ERROR, <system-name>, Invalid input. 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 677: Sec-1055
SEC-1055 SEC-1055 Message <timestamp>, [SEC-1055], <sequence-number>,, ERROR, <system-name>, Invalid FCS list <WWN 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 678: Sec-1059
SEC-1059 SEC-1059 Message <timestamp>, [SEC-1059], <sequence-number>,, ERROR, <system-name>, Fail to <operation, e.g., save, delete, etc.,> <named item> to flash. Probable Cause Indicates the operation failed when writing to flash. Recommended Run the supportFtp - e command to FTP files from the switch and remove them from the flash. Action Severity ERROR...
Page 679: Sec-1065
SEC-1065 SEC-1065 Message <timestamp>, [SEC-1065], <sequence-number>,, ERROR, <system-name>, Invalid character in list. Probable Cause Indicates the input list has an invalid character. Recommended Enter valid input. Action Severity ERROR SEC-1069 Message <timestamp>, [SEC-1069], <sequence-number>,, ERROR, <system-name>, Security Database is corrupted. Probable Cause Indicates the security database is corrupted for unknown reasons.
Page 680: Sec-1073
SEC-1073 SEC-1073 Message <timestamp>, [SEC-1073], <sequence-number>,, ERROR, <system-name>, No FCS policy in list! Probable Cause Indicates the specific policy type is empty. The security database is corrupted for unknown reasons. Recommended Run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command Action and contact your switch service provider.
Page 681: Sec-1076
SEC-1076 SEC-1076 Message <timestamp>, [SEC-1076], <sequence-number>,, ERROR, <system-name>, NoNodeWWNZoning option has been changed. Probable Cause Indicates the NoNodeWWNZoning option has been changed. If the option is turned on, a zone member can be added using node WWNs, but the member will not be able to communicate with others nodes in the zone.
Page 682: Sec-1080
SEC-1080 Recommended Run the command again using a valid policy name. Action Severity ERROR SEC-1080 Message <timestamp>, [SEC-1080], <sequence-number>,, ERROR, <system-name>, Operation denied. Please, use secModeEnable command. 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 683: Sec-1083
SEC-1083 SEC-1083 Message <timestamp>, [SEC-1083], <sequence-number>,, ERROR, <system-name>, Name already exists. 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 684: Sec-1087
SEC-1087 Recommended Reduce the number of entries in some policies to decrease the security database size. Action Severity ERROR SEC-1087 Message <timestamp>, [SEC-1087], <sequence-number>,, ERROR, <system-name>, The security database is larger than the data distribution limit of fabric <fabric data distribution limit>...
Page 685: Sec-1090
SEC-1090 SEC-1090 Message <timestamp>, [SEC-1090], <sequence-number>,, ERROR, <system-name>, SCC list contains FCS member. Please remove member from the FCS policy first. Probable Cause Indicates there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configuration server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.
Page 686: Sec-1093
SEC-1093 SEC-1093 Message <timestamp>, [SEC-1093], <sequence-number>,, ERROR, <system-name>, New FCS list must have at least one member in common with current FCS list. Probable Cause Indicates the new fabric configuration server (FCS) list does not have a common member with the existing FCS list.
Page 687: Sec-1096
SEC-1096 SEC-1096 Message <timestamp>, [SEC-1096], <sequence-number>,, ERROR, <system-name>, Failed to delete <policy name> because <reason text>. Probable Cause Indicates a policy cannot be removed because deleting it would result in invalid security policy configuration. Recommended Verify the security policy configuration requirements and remove any policies that require the policy Action you want to remove first.
Page 688: Sec-1100
SEC-1100 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-1100...
Page 689: Sec-1104
SEC-1104 SEC-1104 Message <timestamp>, [SEC-1104], <sequence-number>,, ERROR, <system-name>, Fail to get primary <Certificate or public key>. Probable Cause Indicates the switch failed to get either the primary certificate or a primary public key. Recommended Verify the primary switch has a valid certificate installed and retry the operation. If a valid Action certificate is not installed, install a certificate by following the procedure specified in the Secure Fabric OS Administrator's Guide.
Page 690: Sec-1108
SEC-1108 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 INFO SEC-1108...
Page 691: Sec-1112
SEC-1112 SEC-1112 Message <timestamp>, [SEC-1112], <sequence-number>,, ERROR, <system-name>, FCS list must be the first entry in the Active Security policies, and the same as the current active FCS list in the switch. Probable Cause Indicates that either a security policy download is attempted with an active policy that does not have the fabric configurations server (FCS) policy as the first policy or the FCS policy is not same as the current FCS policy on the switch.
Page 692: Sec-1116
SEC-1116 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. Severity ERROR SEC-1116 Message <timestamp>, [SEC-1116], <sequence-number>,, ERROR, <system-name>, Fail to commit failover.
Page 693: Sec-1119
SEC-1119 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 694: Sec-1124
SEC-1124 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. Action Severity INFO SEC-1126...
Page 695: Sec-1136
SEC-1136 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-1136 Message <timestamp>, [SEC-1136], <sequence-number>,, ERROR, <system-name>, Failed to verify signature <data type, MUA, policy, etc.,>.
Page 696: Sec-1139
SEC-1139 Recommended Verify that the security event was planned. If the security event was planned, no action is required. Action If the security event was not planned, take appropriate action as defined by your enterprise security policy. Severity INFO SEC-1139 Message <timestamp>, [SEC-1139], <sequence-number>,, ERROR, <system-name>, The RSNMP_POLICY cannot exist without the WSNMP_POLICY.
Page 697: Sec-1146
SEC-1146 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-1146 Message <timestamp>, [SEC-1146], <sequence-number>,, INFO, <system-name>, PID changed: <State>.
Page 698: Sec-1155
SEC-1155 Recommended Reduce the size of the policy database. Action Severity INFO SEC-1155 Message <timestamp>, [SEC-1155], <sequence-number>,, INFO, <system-name>, PID change failed: <Reason> <defined status> <active status>. Probable Cause Indicates that either the defined or active policy was too large after modifying the index/area ID. The status values can be either defined, active, or both.
Page 699: Sec-1158
SEC-1158 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. The name can be a policy name or a switch name. Recommended Enter a valid name. Action Severity INFO SEC-1159 Message...
Page 700: Sec-1164
SEC-1164 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. Probable Cause Indicates the attempt to enable security is made on a switch that is not present in the fabric configuration server (FCS) list.
Page 701: Sec-1167
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 702: Sec-1171
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 703: Sec-1175
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 704: Sec-1182
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 705: Sec-1185
SEC-1185 SEC-1185 Message <timestamp>, [SEC-1185], <sequence-number>,, INFO, <system-name>, <action> switch 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 706: Sec-1188
SEC-1188 SEC-1188 Message <timestamp>, [SEC-1188], <sequence-number>,, INFO, <system-name>, Security violation: Unauthorized device <device node name> tries to FLOGI to index/area <port number> of switch <switch WWN>. Probable Cause Indicates a device connection control (DCC) security violation was reported. The specified device attempted to login using fabric login (FLOGI) to an unauthorized port.
Page 707: Sec-1191
SEC-1191 SEC-1191 Message <timestamp>, [SEC-1191], <sequence-number>,, INFO, <system-name>, Security violation: Unauthorized host with IP address <Ip address> tries to establish HTTP connection. Probable Cause Indicates an HTTP security violation was reported. The specified unauthorized host attempted to establish an HTTP connection. Recommended Determine whether the host IP address specified in the message can be used to manage the fabric Action...
Page 708: Sec-1194
SEC-1194 SEC-1194 Message <timestamp>, [SEC-1194], <sequence-number>,, WARNING, <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 709: Sec-1197
SEC-1197 SEC-1197 Message <timestamp>, [SEC-1197], <sequence-number>,, INFO, <system-name>, Changed account <user name>. Probable Cause Indicates the specified account has changed. Recommended No action is required. Action Severity INFO SEC-1198 Message <timestamp>, [SEC-1198], <sequence-number>,, INFO, <system-name>, Security violation: Unauthorized host with IP address <IP address> tries to establish API connection.
Page 710: Sec-1201
SEC-1201 Recommended Check the MS policy and verify that the connection is allowed. If the connection is allowed but not Action specified, enable the connection in the MS policy. If the MS policy does not allow the connection, this is a valid violation message and an unauthorized entity is trying to access your fabric. Take appropriate action, as defined by your enterprise security policy.
Page 711: Sec-1250
SEC-1250 SEC-1250 Message <timestamp>, [SEC-1250], <sequence-number>,, WARNING, <system-name>, DCC enforcement API failed: <failed action> err=<status>, key=<data> Probable Cause Indicates an internal error caused the device connection control (DCC) policy enforcement to fail. Recommended Retry the failed security command. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
Page 712: Sec-1301
SEC-1301 Recommended Turn off VC-encoded mode before enabling security. Action Severity INFO SEC-1301 Message <timestamp>, [SEC-1301], <sequence-number>,, INFO, <system-name>, This switch is in interop mode. Security is not supported. Probable Cause Indicates the switch is interop-mode enabled. Recommended Disable interop-mode using the interopMode command before enabling the Secure Fabric OS Action feature.
Page 713: Sec-1304
SEC-1304 SEC-1304 Message <timestamp>, [SEC-1304], <sequence-number>,, INFO, <system-name>, This switch has no security license. Probable Cause Indicates there has been a corruption during the distribution of the security database. This can only occur when the primary fabric configuration server (FCS) is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database.
Page 714: Sec-1307
SEC-1307 SEC-1307 Message <timestamp>, [SEC-1307], <sequence-number>,, INFO, <system-name>, Got response from < Security server (RADIUS/LDAP) > server <Server name>. Probable Cause Indicates that after some servers timed out, the specified remote authentication dial-in user service (RADIUS/LDAP) server responded to a switch request. Recommended If the message appears frequently, move the responding server to the top of the RADIUS/LDAP Action...
Page 715: Sec-1311
SEC-1311 Recommended Retry the command when the fabric is stable. Action Severity INFO SEC-1311 Message <timestamp>, [SEC-1311], <sequence-number>,, ERROR, <system-name>, Security mode cannot be enabled because one or more of the password policies is not set to default value. Probable Cause Indicates the security enable failed on the fabric because one or more switches in the fabric have password policies that are not set to the default value.
Page 716: Sec-1314
SEC-1314 SEC-1314 Message <timestamp>, [SEC-1314], <sequence-number>,, ERROR, <system-name>, Reading <IP Address Description> IP address from EM failed. Probable Cause Indicates the call to the EM module to retrieve the IP address failed. Recommended Restart the system to fix this error. If the problem persists contact your switch service provider. Action Severity ERROR...
Page 717: Sec-1318
SEC-1318 Recommended If a policy conflict exists, resolve it, then wait for the fabric to become stable. Retry the distribution. Action Severity INFO SEC-1318 Message <timestamp>, [SEC-1318], <sequence-number>,, INFO, <system-name>, Transaction rejected due to inconsistent fabric. Probable Cause Indicates that some domains detected an inconsistent fabric. Recommended Resolve the policy conflict, if there is one, then wait for the fabric to stabilize.
Page 718: Sec-1322
SEC-1322 Recommended Verify the security event was planned. Action If the security event was planned, run the fddcfg --fabwideset “” command or ad --clear command to clear the fabric wide consistency configuration or AD configuration and retry the secModeEnable command. Severity ERROR SEC-1322...
Page 719: Sec-1325
SEC-1325 SEC-1325 Message <timestamp>, [SEC-1325], <sequence-number>,, ERROR, <system-name>, Security enforcement: Switch <switch WWN> connecting to port <Port number> is not authorized to stay in fabric. Probable Cause Indicates that because of a switch connection control (SCC) policy violation, the switch is being disabled on the specified port.
Page 720: Sec-1329
SEC-1329 Recommended Verify the security event was planned. If the security event was planned, run the authUtil --policy Action passive command to disable the Authentication Policy and retry the secModeEnable command. Severity ERROR SEC-1329 Message <timestamp>, [SEC-1329], <sequence-number>,, ERROR, <system-name>, IPFilter enforcement: Failed to enforce ipfilter policy of <policy Type>...
Page 721: Sec-1332
SEC-1332 SEC-1332 Message <timestamp>, [SEC-1332], <sequence-number>,, ERROR, <system-name>, Fabric wide policy is conflicting as <Policy Name> is present in the fabric wide policy and 5.3 or 5.2 switches present in the fabric. Probable Cause Indicates the fabric-wide policy is conflicting. Recommended Remove either the FCS from the fabric-wide policy, or remove 5.3 and 5.2 switches from the fabric, Action...
Page 722: Sec-1336
SEC-1336 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. Severity WARNING SEC-1336...
Page 723: Sec-3036
SEC-3036 SEC-3036 Message <timestamp>, [SEC-3036], <sequence-number>, INFO, <system-name>, Event: ipfilter, Status: failed, Info: Failed to save changes for <IP Filter Policy> ipfilter policies. Probable Cause Indicates that that the specified IP filter policy has not been saved. 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 724: Sec-3050
SEC-3050 Recommended Check for unauthorized access to the switch through the specified protocol connection. Action Severity INFO SEC-3050 Message <timestamp>, [SEC-3050], <sequence-number>, INFO, <system-name>, Event: <Event Name>, Status: success, Info: <Event Specific Info>. Probable Cause Indicates the specified sshutil operation was performed. Recommended Verify the security event was planned.
Page 725: Sec-3063
SEC-3063 Recommended No action is required. Action Severity INFO SEC-3063 Message <timestamp>, [SEC-3063], <sequence-number>, INFO, <system-name>, Role <role name> is copied from <source role>. Probable Cause Indicates that the specified role name has been copied from the source role. Recommended No action is required.
Page 726: Sec-3067
SEC-3067 Recommended No action is required. Action Severity INFO SEC-3067 Message <timestamp>, [SEC-3067], <sequence-number>, WARNING, <system-name>, Invalid Cipher list <Cipher List>. Probable Cause Indicates that the input cipher list is an invalid string. Recommended Invalid cipher list input, therefore reverted to previous cipher list. Action Severity WARNING...
Page 727: Sflo-1001
Chapter SFLO System Messages SFLO-1001 Message <timestamp>, [SFLO-1001], <sequence-number>,, INFO, <system-name>, sFlow is <state> globally. Probable Cause Indicates that sFlow is globally enabled or disabled. Recommended No action is required. Action Severity INFO SFLO-1002 Message <timestamp>, [SFLO-1002], <sequence-number>,, INFO, <system-name>, sFlow is <state>...
Page 728: Sflo-1005
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 sFlow sampling rate has been changed on the specified port. Recommended No action is required.
Page 729 SFLO-1008 Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1002448-01...
Page 730 SFLO-1008 Fabric OS Message Reference 53-1002448-01...
Page 731: Snmp-1001
Chapter SNMP System Messages SNMP-1001 Message <timestamp>, [SNMP-1001], <sequence-number>,, ERROR, <system-name>, SNMP service is not available <Reason>. Probable Cause Indicates that the Simple Network Management Protocol (SNMP) service could not be started because of the specified reason. Therefore, you will not be able to query the switch through SNMP. Recommended Verify that the IP address for the Ethernet and Fibre Channel interface is set correctly.
Page 732: Snmp-1004
SNMP-1004 SNMP-1004 Message <timestamp>, [SNMP-1004], <sequence-number>, FFDC, ERROR, <system-name>, Incorrect SNMP configuration. Probable Cause Indicates that the SNMP configuration is incorrect and therefore the SNMP service will not work correctly. Recommended Change the SNMP configuration to default using the snmpConfig default command.
Page 733: Snmp-1008
SNMP-1008 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 SNMP-1009 Message <timestamp>, [SNMP-1009], <sequence-number>,, INFO, <system-name>, Port traps are <blocked state>...
Page 734 SNMP-1009 Fabric OS Message Reference 53-1002448-01...
Page 735: Spc-1001
Chapter SPC System Messages SPC-1001 Message <timestamp>, [SPC-1001], <sequence-number>,, INFO, <system-name>, S<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>, S<slot number containing Encryption Engine>, Cryptographic operation disabled.
Page 736: Spc-2001
SPC-2001 SPC-2001 Message <timestamp>, [SPC-2001], <sequence-number>,, ERROR, <system-name>, S<slot number containing Encryption Engine>, <module name>: Crypto error asserted by Vader/OB1 0x<Reason>. Probable Cause Indicates the Crypto error is asserted by Field-Programmable Gate Array (FPGA). Recommended No action is required. Action Severity ERROR SPC-2002...
Page 737: Spc-2005
SPC-2005 Recommended No action is required. Action Severity ERROR SPC-2005 Message <timestamp>, [SPC-2005], <sequence-number>,, INFO, <system-name>, S<slot number containing Encryption Engine>, <module name>: FPGA firmware download success: 0x<Reason>. Probable Cause Indicates the FPGA download was successful. Recommended No action is required. Action Severity INFO...
Page 738: Spc-2009
SPC-2009 Recommended No action is required. Action Severity INFO SPC-2009 Message <timestamp>, [SPC-2009], <sequence-number>,, CRITICAL, <system-name>, S<slot number containing Encryption Engine>, <module name>: Tamper event: User zeroization. Probable Cause Indicates the Tamper event triggered due to a user zeroize request. The Encryption Engine (EE) is zeroized.
Page 739: Spc-2012
SPC-2012 SPC-2012 Message <timestamp>, [SPC-2012], <sequence-number>,, INFO, <system-name>, S<slot number containing Encryption Engine>, <module name>: User zeroization command completed successfully. Tamper INT status <Status>. Probable Cause Indicates the User zeroization command has completed successfully. The Encryption Engine (EE) is zeroized. Recommended Execute the cryptocfg initEE and cryptocfg...
Page 740: Spc-2041
SPC-2041 Recommended No action is required. Action Severity ERROR SPC-2041 Message <timestamp>, [SPC-2041], <sequence-number>,, ERROR, <system-name>, S<slot number containing Encryption Engine>, <module name>: Alloc freemsg block failed. Probable Cause Indicates an allocation failure for pool for switch board (SB) message. Recommended No action is required.
Page 741: Spc-3001
SPC-3001 Recommended No action is required. Action Severity WARNING SPC-3001 Message <timestamp>, [SPC-3001], <sequence-number>,, ERROR, <system-name>, S<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>...
Page 742: Spc-3004
SPC-3004 SPC-3004 Message <timestamp>, [SPC-3004], <sequence-number>,, ERROR, <system-name>, S<slot number containing Encryption Engine>, <module name>: No output KEK for DEK create, KEK: <KEK octet 1> <KEK octet 2> <KEK octet 3> <KEK octet 4>. Probable Cause Indicates the output wrapping KEK for the DEK to be created does not exist within the EE Crypto Module.
Page 743: Spc-3007
SPC-3007 Recommended For status code 14, complete primary KEK generation; otherwise, contact your switch service Action provider. Severity ERROR SPC-3007 Message <timestamp>, [SPC-3007], <sequence-number>,, ERROR, <system-name>, S<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: •...
Page 744: Spc-3010
SPC-3010 SPC-3010 Message <timestamp>, [SPC-3010], <sequence-number>,, WARNING, <system-name>, S<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 Execute the cryptocfg initEE and cryptocfg regEE commands.
Page 745: Spc-3014
SPC-3014 Recommended Contact your switch service provider for assistance. Action Severity ERROR SPC-3014 Message <timestamp>, [SPC-3014], <sequence-number>,, ERROR, <system-name>, S<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 your switch service provider for assistance.
Page 746 SPC-3015 Fabric OS Message Reference 53-1002448-01...
Page 747: Spm-1001
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 748: Spm-1005
SPM-1005 Recommended No action is required. Action Severity INFO SPM-1005 Message <timestamp>, [SPM-1005], <sequence-number>,, INFO, <system-name>, Set EE Control slot <slot> action <action>. Probable Cause 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 749: Spm-1009
SPM-1009 Recommended No action is required. Action Severity INFO SPM-1009 Message <timestamp>, [SPM-1009], <sequence-number>,, ERROR, <system-name>, <cert> Certificate is missing. Probable Cause 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 750: Spm-1013
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 751: Spm-1016
SPM-1016 SPM-1016 Message <timestamp>, [SPM-1016], <sequence-number>,, WARNING, <system-name>, Security database is out of sync. This warning can be ignored if the nodes in the EG are running different versions of FOS. Probable Cause Indicates a failure to distribute security database. Recommended Use the cryptocfg sync -securitydb command to manually sync security db.
Page 752: Spm-3004
SPM-3004 SPM-3004 Message <timestamp>, [SPM-3004], <sequence-number>,, INFO, <system-name>,Event: cryptocfg Status: success, Info: EE in slot <slot> enabled. Probable Cause Indicates an encryption engine was enabled. Recommended No action is required. Action Severity INFO SPM-3005 Message <timestamp>, [SPM-3005], <sequence-number>,, INFO, <system-name>,Event: cryptocfg Status: success, Info: EE in slot <slot>...
Page 753: Spm-3008
SPM-3008 SPM-3008 Message <timestamp>, [SPM-3008], <sequence-number>,, INFO, <system-name>,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 <timestamp>, [SPM-3009], <sequence-number>,, INFO, <system-name>,Event: cryptocfg Status: success, Info: DH response accepted.
Page 754: Spm-3012
SPM-3012 SPM-3012 Message <timestamp>, [SPM-3012], <sequence-number>,, INFO, <system-name>,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 Message...
Page 755: Spm-3016
SPM-3016 Recommended No action is required. Action Severity INFO SPM-3016 Message <timestamp>, [SPM-3016], <sequence-number>,, INFO, <system-name>,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 <timestamp>, [SPM-3017], <sequence-number>,, INFO, <system-name>,Event: cryptocfg Status: success, Info: Master key exported.
Page 756: Spm-3020
SPM-3020 Recommended No action is required. Action Severity INFO SPM-3020 Message <timestamp>, [SPM-3020], <sequence-number>,, INFO, <system-name>, Event: cryptocfg Status: success, Info: System card with certificate label \"<certLabel>\" deregistered. Probable Cause Indicates a system card was de-registered. Recommended No action is required. Action Severity INFO...
Page 757: Spm-3024
SPM-3024 Recommended No action is required. Action Severity INFO SPM-3024 Message <timestamp>, [SPM-3024], <sequence-number>,, INFO, <system-name>, 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 758: Spm-3028
SPM-3028 Recommended No action is required. Action Severity INFO SPM-3028 Message <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. Action Severity INFO SPM-3029 Message...
Page 759: Ss-1000
Chapter SS System Messages SS-1000 Message <timestamp>, [SS-1000], <sequence-number>,, INFO, <system-name>, supportSave has uploaded support information to the host with IP address <host ip>. Probable Cause Indicates that the supportSave command was used to transfer support information to a remote location.
Page 760: Ss-1003
SS-1003 SS-1003 Message <timestamp>, [SS-1003], <sequence-number>,, WARNING, <system-name>, supportSave's operation to USB storage device aborted. Probable Cause Indicates that a USB operation error has occurred during execution of the supportSave command. Complete error information cannot always be displayed in this message because of possible errors in subcommands being executed by the supportSave command.
Page 761: Ss-1007
SS-1007 Recommended Restart the switch using the reboot command and then execute the supportSave command. Action 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 specified slot for the given supportsave request.
Page 762 SS-1009 Fabric OS Message Reference 53-1002448-01...
Page 763: Ssmd-1001
Chapter SSMD 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 764: Ssmd-1004
SSMD-1004 SSMD-1004 Message <timestamp>, [SSMD-1004], <sequence-number>,, ERROR, <system-name>, Failed to unlock semaphore mutex: (<function name>). 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 start up failed.
Page 765: Ssmd-1008
SSMD-1008 Recommended Try again after sometime. If the problem persists, execute the supportSave command and then Action restart or power cycle the switch. Severity ERROR SSMD-1008 Message <timestamp>, [SSMD-1008], <sequence-number>,, ERROR, <system-name>, Apptype TCAM Table full for Slot:<slot number> chip:<Chip number in the slot>. Probable Cause Indicates that the application type TCAM table is full on the specified chip.
Page 766: Ssmd-1202
SSMD-1202 SSMD-1202 Message <timestamp>, [SSMD-1202], <sequence-number>,, WARNING, <system-name>, QoS failed programming interface 0x<Interface ID> 802.3x Pause flow control. Probable Cause Indicates that DCE SSM encountered an unexpected error in programming the dataplane ASIC for enforcing the interface 802.3x Pause flow control feature. Recommended Delete and reapply the QoS 802.3x Pause flow control policy using the qos flowcontrol command.
Page 767: Ssmd-1206
SSMD-1206 Recommended Delete and reapply the CEE Map ETS policy using the cee-map default command. Action If the problem persists, restart or power cycle the switch. 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 that DCE SSM encountered an unexpected error in programming the dataplane ASIC for enforcing the CEE Map Class of Service (CoS) to Priority Group ID (PGID) mapping feature.
Page 768: Ssmd-1209
SSMD-1209 SSMD-1209 Message <timestamp>, [SSMD-1209], <sequence-number>,, WARNING, <system-name>, QoS failed programming interface 0x<Interface ID> CoS Mutation map. Probable Cause Indicates that DCE SSM encountered an unexpected error in programming the dataplane ASIC for enforcing the interface CoS Mutation mapping feature. Recommended Delete and reapply the QoS interface CoS Mutation policy using the qos cos-mutation command.
Page 769: Ssmd-1212
SSMD-1212 SSMD-1212 Message <timestamp>, [SSMD-1212], <sequence-number>,, WARNING, <system-name>, QoS failed programming ASIC <ASIC slot number>/<ASIC chip number> Multicast Scheduler Control. Probable Cause Indicates that DCE SSM encountered an unexpected error in programming the dataplane ASIC for enforcing the multicast packet Scheduler Control feature. Recommended Delete and reapply the QoS multicast packet Scheduler Control policy using the qos queue Action...
Page 770: Ssmd-1216
SSMD-1216 Recommended Delete and reapply the QoS CoS Tail Drop Threshold policy using the qos rcv-queue command. Action If the problem persists, restart or power cycle the switch. Severity WARNING SSMD-1216 Message <timestamp>, [SSMD-1216], <sequence-number>,, WARNING, <system-name>,QoS failed programming interface 0x<Interface ID> Pause. Probable Cause Indicates that DCE SSM encountered an unexpected error in programming the dataplane ASIC for enforcing the interface Pause feature.
Page 771: Ssmd-1302
SSMD-1302 Recommended No action is required. Action Severity INFO SSMD-1302 Message <timestamp>, [SSMD-1302], <sequence-number>,, INFO, <system-name>, CEE Map <ceemap> priority table <pg_ids> is <action>. Probable Cause Indicate that the priority groups (PGs) have been added to or removed from the specified CEE Map. Recommended No action is required.
Page 772: Ssmd-1306
SSMD-1306 Recommended No action is required. Action Severity INFO SSMD-1306 Message <timestamp>, [SSMD-1306], <sequence-number>,, INFO, <system-name>, CEE Map <ceemap> priority group <pg_id> is PFC <pfc_status>. Probable Cause Indicates that the specified PG PFC status has been changed. Recommended No action is required. Action Severity INFO...
Page 773: Ssmd-1310
SSMD-1310 Recommended No action is required. Action Severity INFO SSMD-1310 Message <timestamp>, [SSMD-1310], <sequence-number>,, INFO, <system-name>, ACL <acl_name> configured on interface <InterfaceName>. Probable Cause Indicates that the specified access list has been configured on the interface. Recommended No action is required. Action Severity INFO...
Page 774: Ssmd-1314
SSMD-1314 Recommended No action is required. Action Severity INFO SSMD-1314 Message <timestamp>, [SSMD-1314], <sequence-number>,, INFO, <system-name>, CEE Map <ceemap> precedence changed from <precedence_old> to <precedence_new>. Probable Cause Indicates that precedence of the specified CEE Map has been changed.Recommended Action No action is required. Severity INFO SSMD-1315...
Page 775: Ssmd-1318
SSMD-1318 Recommended No action is required. Action Severity INFO SSMD-1318 Message <timestamp>, [SSMD-1318], <sequence-number>,, INFO, <system-name>, ACL <acl_name> is being removed from interface <InterfaceName>. This operation could take a long time. Probable Cause Indicates that the specified access list is being removed from the interface. Recommended No action is required.
Page 776 SSMD-1318 Fabric OS Message Reference 53-1002448-01...
Page 777: Sulb-1001
Chapter SULB System Messages SULB-1001 Message <timestamp>, [SULB-1001], <sequence-number>, 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 778: Sulb-1004
SULB-1004 SULB-1004 Message <timestamp>, [SULB-1004], <sequence-number>,, INFO, <system-name>, 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 779: Sulb-1008
SULB-1008 SULB-1008 Message <timestamp>, [SULB-1008], <sequence-number>,, INFO, <system-name>, Standby CP booted successfully with new firmware. Probable Cause Indicates the standby CP has rebooted successfully. Recommended No action is required. The firmwareDownload command is progressing as expected. Action Run the firmwareDownloadStatus command for more information. Severity INFO SULB-1009...
Page 780 SULB-1009 TABLE 7 Status messages and status codes (Continued) Status message Status code "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." 0x58 "Unable to check the firmware version on Standby CP due to IPC error."...
Page 781 SULB-1009 TABLE 7 Status messages and status codes (Continued) Status message Status code "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." 0x82 "Standby CP failed to boot up with new firmware."...
Page 782 SULB-1009 TABLE 7 Status messages and status codes (Continued) Status message Status code "Switch is relocating the AP image." 0xa9 "The AP image is relocated successfully." 0xaa "Switch reboots during relocating the AP image. The operation will be restarted." 0xab “Blade failed to reboot with the original image.
Page 783 SULB-1009 TABLE 8 Error messages and error codes (Continued) Error message Error code “Primary filesystem is inconsistent. Run firmwareRestore to restore the original firmware, or 0x25 contact your service provider for recovery.” "The post-install script failed." 0x26 "Unexpected reboot." 0x27 "Primary kernel partition is inconsistent.
Page 784 SULB-1009 0x29 - The pre-install script failed. This error may be caused by an unsupported blade type in the chassis. Remove or power off the unsupported blades before proceeding. Another possible cause may be an invalid chassisConfig option setting. In that case, reset the chassisConfig option before retrying firmwareDownload.
Page 785: Sulb-1010
SULB-1010 In a director-class switch, when firmwareDownload fails, the two CPs may end up with different versions of firmware and they may not gain high-availability (HA) sync. In that case, run firmwareDownload single mode (-s) to upgrade the firmware on the standby CP to the same version as the active CP.
Page 786: Sulb-1018
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 787: Sulb-1022
SULB-1022 SULB-1022 Message <timestamp>, [SULB-1022], <sequence-number>,, WARNING, <system-name>, The blade in slot <Slot number> has rebooted successfully with new firmware. Probable Cause Indicates that the blade in the specified slot has rebooted with new firmware. This is a normal step in the firmwareDownload process.
Page 788: Sulb-1025
SULB-1025 SULB-1025 Message <timestamp>, [SULB-1025], <sequence-number>,, WARNING, <system-name>, The blade in slot <Slot number> will reboot with the new firmware. Probable Cause Indicates new firmware has been downloaded to the specified AP blade and that the AP blade will reboot to activate it. Recommended Wait for the blade to reboot.
Page 789: Sulb-1032
SULB-1032 Recommended Wait for the operation to complete. Action Severity WARNING SULB-1032 Message <timestamp>, [SULB-1032], <sequence-number>, 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 790: Sulb-1036
SULB-1036 Probable Cause Indicates an error has occurred during the relocation of the internal image. The error may be caused by inconsistent internal firmware image. It may also be caused by the internal Ethernet or persistent storage hardware failure. Recommended Reset the switch.
Page 791: Sulb-1039
SULB-1039 SULB-1039 Message <timestamp>, [SULB-1039], <sequence-number>, INFO, <system-name>, 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 792: Sulb-1043
SULB-1043 Recommended No action is required. The firmwareActivate command has completed as expected. Action Run the firmwareShow command to verify the firmware versions. Severity INFO SULB-1043 Message <timestamp>, [SULB-1043], <sequence-number>, INFO, <system-name>, FirmwareActivation command failed. <error string>. Probable Cause Indicates the firmwareActivate command failed. The error string indicates why it failed. Recommended Run the firmwareShow command to verify the firmware versions.
Page 793: Swch-1001
Chapter SWCH System Messages SWCH-1001 Message <timestamp>, [SWCH-1001], <sequence-number>,, ERROR, <system-name>, Switch is not in ready state - Switch enable failed switch status= 0x<switch status>, c_flags = 0x<switch control flags>. Probable Cause Indicates the switch is enabled before it is ready. Recommended If the message persists, run the supportFtp command (as needed) to set up automatic FTP Action...
Page 794: Swch-1004
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 795: Swch-1008
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 796: Swch-1011
SWCH-1011 Refer to the Fabric OS Administrator’s Guide for more information. 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 797: Swch-1014
SWCH-1014 SWCH-1014 Message <timestamp>, [SWCH-1014], <sequence-number>,, INFO, <system-name>, All Trunk Areas have been disabled. Probable Cause Indicates that all Trunk Areas have been disabled and the configuration file has been updated. Recommended No action is required. Action Severity INFO SWCH-1015 Message <timestamp>, [SWCH-1015], <sequence-number>,, WARNING, <system-name>, <Function name>...
Page 798: Swch-1018
SWCH-1018 Recommended This is a LOOP device and peristent PID is set on it. This is not a supported configuration. Remove Action the WWN-PID binding and re-enable the port and then run the wwnaddress unbind wwn command. Severity INFO SWCH-1018 Message <timestamp>, [SWCH-1018], <sequence-number>,, INFO, <system-name>, Device <wwn name of device>...
Page 799: Swch-1021
SWCH-1021 SWCH-1021 Message <timestamp>, [SWCH-1021], <sequence-number>,, WARNING, <system-name>, HA state out of sync: Standby CP (ver = <standby SWC version>) does not support Dynamic area on default switch (Active CP version = <active SWC version>). Probable Cause Indicates the standby control processor (CP) does not support dynamic area on default switch. Recommended Load a firmware version on the standby CP that supports dynamic area on default switch, using the Action...
Page 800 SWCH-1022 Fabric OS Message Reference 53-1002448-01...
Page 801: Sysc-1001
Chapter SYSC System Messages SYSC-1001 Message <timestamp>, [SYSC-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, Failed to run <Name of program that could not be run (string)>:<System internal error message (string)>. Probable Cause Indicates that during the boot sequence, one of the programs 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 802: Sysc-1004
SYSC-1004 It could also indicate that the current option number could not be read from the chassis option storage device (the world wide name (WWN) card). This message occurs only on the Brocade 24000 and 48000. Recommended As indicated in the message, run the chassisConfig command to change to one that is valid on this Action platform running this firmware.
Page 803: Sysm-1001
Chapter SYSM System Messages SYSM-1001 Message <timestamp>, [SYSM-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, No memory. Probable Cause Indicates the switch has run out of system memory. Recommended Run the memShow command to view the switch memory usage. Action Restart or power cycle the switch. Run the supportFtp command to set up automatic FTP transfers;...
Page 804: Sysm-1004
SYSM-1004 SYSM-1004 Message <timestamp>, [SYSM-1004], <sequence-number>,, ERROR, <system-name>, Failed to retrieve current chassis configuration option, ret=<Unknown> Probable Cause Indicates there was a failure to read configuration data from the WWN card. Recommended Verify that the world wide name (WWN) card is present and operational and that the affected Action control processor (CP) is properly seated in its slot.
Page 805: Tape-1001
Chapter TAPE System Messages TAPE-1001 Message <timestamp>, [TAPE-1001], <sequence-number>, FFDC, INFO, <system-name>, Key acquisition for <Pool or Container><Begins or Complete>. Probable Cause Indicates that the key acquisition for the pool or the container has begun or is complete. Recommended No action is required. Action Severity INFO...
Page 806 TAPE-1001 Fabric OS Message Reference 53-1002448-01...
Page 807: Trce-1001
Chapter TRCE System Messages TRCE-1001 Message <timestamp>, [TRCE-1001], <sequence-number>,, WARNING, <system-name>, Trace dump available< optional slot indicating on which slot the dump occurs >! (reason: <Text explanation of what triggered the dump. (PANIC DUMP, WATCHDOG EXPIRED, MANUAL, TRIGGER)>) Probable Cause Indicates that trace dump files have been generated on the switch or the indicated slot.
Page 808: Trce-1003
TRCE-1003 TRCE-1003 Message <timestamp>, [TRCE-1003], <sequence-number>,, ERROR, <system-name>, Trace dump <optional slot indicating on which slot the dump occurs> was not transferred due to FTP error. 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.
Page 809: Trce-1007
TRCE-1007 Recommended No action is required. Action Severity INFO TRCE-1007 Message <timestamp>, [TRCE-1007], <sequence-number>,, INFO, <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 810: Trce-1010
TRCE-1010 TRCE-1010 Message <timestamp>, [TRCE-1010], <sequence-number>,, ERROR, <system-name>, Traced fails to start 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.
Page 811: Trck-1001
Chapter TRCK System Messages TRCK-1001 Message <timestamp>, [TRCK-1001], <sequence-number>,, INFO, <system-name>, Successful login by user <User>. Probable Cause Indicates the track change feature 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 812: Trck-1004
TRCK-1004 TRCK-1004 Message <timestamp>, [TRCK-1004], <sequence-number>,, INFO, <system-name>, Config file change from task:<task>. 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.
Page 813: Ts-1001
Chapter TS System Messages TS-1001 Message <timestamp>, [TS-1001], <sequence-number>,, WARNING, <system-name>, NTP Query failed: <error code>. Probable Cause Indicates a network time protocol (NTP) query to the configured external clock server failed. Local clock time on the principal or primary fabric configuration server (FCS) switch is used for fabric synchronization.
Page 814: Ts-1006
TS-1006 TS-1006 Message <timestamp>, [TS-1006], <sequence-number>,, INFO, <system-name>, <message>. Probable Cause Indicates a time service event is occurring or has failed. The message might be one of the following: • Init failed. Time Service exiting Probable Cause: Initialization error, Time Server exits. •...
Page 815: Ucst-1003
Chapter UCST System Messages UCST-1003 Message <timestamp>, [UCST-1003], <sequence-number>,, INFO, <system-name>, Duplicate Path to Domain <domain ID>, Output Port = <port number>, PDB pointer = 0x<value> Probable Cause Indicates 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 816: Ucst-1021
UCST-1021 UCST-1021 Message <timestamp>, [UCST-1021], <sequence-number>,, INFO, <system-name>, 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. Action Severity INFO...
Page 817: Ucst-1025
UCST-1025 UCST-1025 Message <timestamp>, [UCST-1025], <sequence-number>,, INFO, <system-name>, In-order delivery option has been enabled with Lossless-DLS option. Probable Cause Indicates the IOD option has been enabled for the switch. This option guarantees in-order delivery of frames during topology changes. Recommended No action is required.
Page 818 UCST-1027 Fabric OS Message Reference 53-1002448-01...
Page 819: Upth-1001
Chapter UPTH System Messages UPTH-1001 Message <timestamp>, [UPTH-1001], <sequence-number>,, WARNING, <system-name>, No minimum cost path in candidate list. Probable Cause Indicates the specified switch is unreachable because no minimum cost path (FSPF UPATH) exists in the candidate list (domain ID list). Recommended No action is required.
Page 820 UPTH-1002 Fabric OS Message Reference 53-1002448-01...
Page 821: Vs-1001
Chapter VS System Messages VS-1001 Message <timestamp>, [VS-1001], <sequence-number>,, INFO, <system-name>, No virtual PWWN assignment for the device <Login device PWWN>, port <Switch port> or (AG <AG NWWN> port <AG port>). Probable Cause Indicates that the device with virtual Port World Wide Name (PWWN) feature enabled, tried to login but there is no mapping for the device, port, or Access Gateway (AG) port.
Page 822: Vs-1004
VS-1004 VS-1004 Message <timestamp>, [VS-1004], <sequence-number>,, INFO, <system-name>, Could not find Virtual PWWN config file for the switch. Probable Cause Indicates that the virtual Port World Wide Name (PWWN) feature has been enabled for the first time on the switch or the configuration file was corrupted or accidently removed. Recommended Creating a new default configuration file.
Page 823: Vs-1008
VS-1008 VS-1008 Message <timestamp>, [VS-1008], <sequence-number>,, INFO, <system-name>, Virtualization services failed to create timer. Probable Cause Indicates failure in virtualization service daemon (vsd) start up because vsd has failed to create a timer. Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1002448-01...
Page 824 VS-1008 Fabric OS Message Reference 53-1002448-01...
Page 825: Webd-1001
Chapter WEBD System Messages WEBD-1001 Message <timestamp>, [WEBD-1001], <sequence-number>,, WARNING, <system-name>, Missing or Invalid Certificate file -- HTTPS is configured but could not be started. Probable Cause Indicates the SSL certificate file is either invalid or absent. Recommended Install a valid key file. Action Severity WARNING...
Page 826: Webd-1006
WEBD-1006 Recommended No action is required. Action Severity WARNING WEBD-1006 Message <timestamp>, [WEBD-1006], <sequence-number>,, INFO, <system-name>, HTTP server 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 827: Xtun-1000
Chapter XTUN System Messages XTUN-1000 Message <timestamp>, [XTUN-1000], <sequence-number>,, ERROR, <system-name>, FCIP Tunnel <VE Port (Tunnel) Number> 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 828: Xtun-1003
XTUN-1003 XTUN-1003 Message <timestamp>, [XTUN-1003], <sequence-number>,, ERROR, <system-name>, FCIP Tunnel <VE Port (Tunnel) Number> Message Transmission failed:I/T/L/E:<FC Initiator ID>/<FC Target ID>/<FCP Logical Unit Number>/<Error return value>. 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.
Page 829: Xtun-1997
XTUN-1997 Recommended No action is required. Action Severity INFO XTUN-1997 Message <timestamp>, [XTUN-1997], <sequence-number>,, WARNING, <system-name>, FTRACE buffer <FTRACE Trace Buffer Number> on slot <FX8-24 Slot Number> dp <FX8-24 DP Number> has been triggered. Probable Cause Indicates that a programmed trigger event has been detected. Recommended If there was an unexpected job failure associated with this event, contact your vendor's customer Action...
Page 830: Xtun-2001
XTUN-2001 Recommended No action is required. Action Severity INFO XTUN-2001 Message <timestamp>, [XTUN-2001], <sequence-number>,, ERROR, <system-name>, FCIP Tunnel <VE Port (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 831: Xtun-2005
XTUN-2005 Recommended No action is required. Action Severity INFO XTUN-2005 Message <timestamp>, [XTUN-2005], <sequence-number>,, ERROR, <system-name>, FCIP Tunnel <VE Port (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 832: Xtun-2009
XTUN-2009 Recommended No action is required. Action Severity INFO XTUN-2009 Message <timestamp>, [XTUN-2009], <sequence-number>,, INFO, <system-name>, IPsec: <Reason>. Probable Cause Indicates that the status of an IPsec Security Association has changed. Recommended No action is required. Action Severity INFO XTUN-2010 Message <timestamp>, [XTUN-2010], <sequence-number>,, INFO, <system-name>, SPD: <Reason>.
Page 833: Xtun-2021
XTUN-2021 Recommended No action is required. Action Severity INFO XTUN-2021 Message <timestamp>, [XTUN-2021], <sequence-number>,, INFO, <system-name>, FCIP Tunnel <VE Port (Tunnel) Number> Circuit <Circuit Number> DELETED (<Originator>). Probable Cause Indicates that the specified circuit has been administratively deleted. Recommended No action is required. Action Severity INFO...
Page 834: Xtun-2024
XTUN-2024 XTUN-2024 Message <timestamp>, [XTUN-2024], <sequence-number>,, INFO, <system-name>, FCIP Tunnel <VE Port (Tunnel) Number> Circuit <Circuit Number> MODIFIED (<Attribute change description>). Probable Cause Indicates that the attribute is modified. In most cases, the attribute value is modified within the specified circuit. Recommended No action is required.
Page 835: Zeus-1001
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 836: Zeus-1004
ZEUS-1004 ZEUS-1004 Message <timestamp>, [ZEUS-1004], <sequence-number>, , ERROR, <system-name>, S<slot number>,C<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 837 ZEUS-1016 Recommended Whenever this error is observed persistently, power cycle the faulted blade. If the problem persists, Action replace the blade. Severity WARNING Fabric OS Message Reference 53-1002448-01...
Page 838 ZEUS-1016 Fabric OS Message Reference 53-1002448-01...
Page 839: Zone-1002
Chapter ZONE System Messages ZONE-1002 Message <timestamp>, [ZONE-1002], <sequence-number>,, WARNING, <system-name>, WWN zoneTypeCheck or zoneGroupCheck warning(<warning string>) at port(<port number>). Probable Cause Indicates that a zone filter or zone group check failure occurred. The frame filter logic reported a failure when creating or adding the zone groups during port login (PLOGI) trap processing. This message usually indicates problems when adding the content-addressable memory (CAM) entries before the filter setup.
Page 840: Zone-1005
ZONE-1005 Recommended No action is required. Action Severity INFO ZONE-1005 Message <timestamp>, [ZONE-1005], <sequence-number>,, INFO, <system-name>, HARD and SOFT zones(<Zone name>, <Zone name>) definitions overlap. Probable Cause Indicates that a port is zoned with mixed devices (WWN and D,I). During zoning database cross checking, either of the following is detected: •...
Page 841: Zone-1008
ZONE-1008 Recommended The following are the ways to avoid this problem: Action • Avoid having too many hosts zoned with a set of target devices at a single port. • Avoid having too many zones directed at a single port group on the switch. Severity INFO ZONE-1008...
Page 842: Zone-1013
ZONE-1013 ZONE-1013 Message <timestamp>, [ZONE-1013], <sequence-number>,, WARNING, <system-name>, QuickLoop not supported. Probable Cause Indicates that the QuickLoop feature is not supported in the current version of Fabric OS. QuickLoop zones are not supported in Fabric OS version 4.x or later. Even if the QuickLoop zoning configuration is enabled on the switch, it will not be supported.
Page 843: Zone-1018
ZONE-1018 Recommended Edit the zone database to make sure that only one initiator is set for each FA zone configuration. Action Severity ERROR ZONE-1018 Message <timestamp>, [ZONE-1018], <sequence-number>,, ERROR, <system-name>, Incorrect zoning enforcement type(<zone type>) at port(<port number>). Probable Cause Indicates that an incorrect zoning enforcement type was reported on the specified port.
Page 844: Zone-1022
ZONE-1022 ZONE-1022 Message <timestamp>, [ZONE-1022], <sequence-number>,, INFO, <system-name>, The effective configuration has changed to <Effective configuration name>. <AD Id> Probable Cause Indicates that the effective zone configuration has changed to the specified zone name. 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 845: Zone-1027
ZONE-1027 ZONE-1027 Message <timestamp>, [ZONE-1027], <sequence-number>,, INFO, <system-name>, Zoning transaction aborted <error reason>. <AD Id>. Probable Cause Indicates the zoning transaction was aborted because of one of the following conditions: • Zone Merge Received: The fabric is in the process of merging two zone databases. •...
Page 846: Zone-1030
ZONE-1030 Recommended If the problem persists, execute the supportFtp command (as needed) to set up automatic FTP Action transfers; then execute 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.
Page 847: Zone-1033
ZONE-1033 ZONE-1033 Message <timestamp>, [ZONE-1033], <sequence-number>,, ERROR, <system-name>, Domain <domain number> Lowest Max Zone DB size. Probable Cause Indicates that the specified domain has the lowest memory available for the zone database in the fabric. The zone database must be smaller than the memory available on this domain. Recommended Reduce the size of the zone database and retry the operation.
Page 848: Zone-1037
ZONE-1037 Recommended Reduce the size of the zone database and retry the operation. Action Severity ERROR ZONE-1037 Message <timestamp>, [ZONE-1037], <sequence-number>,, ERROR, <system-name>, Unable to examine <config file name>: error message <System Error Message>. Probable Cause Indicates that the Fabric OS cannot examine the zone configuration file. Typically, the zone configuration is too large for the memory available on the switch.
Page 849: Zone-1040
ZONE-1040 ZONE-1040 Message <timestamp>, [ZONE-1040], <sequence-number>,, INFO, <system-name>, Merged zone database exceeds limit. Probable Cause Indicates that the Fabric OS cannot read the merged 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 850: Zone-1044
ZONE-1044 ZONE-1044 Message <timestamp>, [ZONE-1044], <sequence-number>,, INFO, <system-name>, The Default Zone access mode is set to All Access. Probable Cause Indicates that the Default Zone access mode is set to All Access. 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 851: Zone-1048
ZONE-1048 ZONE-1048 Message <timestamp>, [ZONE-1048], <sequence-number>,, WARNING, <system-name>, ZONE ACA is rejected on the standby. Probable Cause Indicates that the standby zoning component did not receive a syncdump command from the primary side. Recommended Synchronize the standby control processor (CP) using the haSyncStart command. Action Severity WARNING...
Page 852: Zone-1052
ZONE-1052 ZONE-1052 Message <timestamp>, [ZONE-1052], <sequence-number>,, INFO, <system-name>, The Interop Default Zone state is set to enabled. Probable Cause Indicates that the Interop Default Zone attribute state is 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 853: Zone-1056
ZONE-1056 ZONE-1056 Message <timestamp>, [ZONE-1056], <sequence-number>,, WARNING, <system-name>, Non-ETIZ-Capable Switch (dom <domainID>) in fabric w/ETIZ Configured. Probable Cause Indicates that the cfgSave, cfgEnable, or cfgDisable commands will not work on the Fabric OS switch earlier than v6.4.0 in Interop Mode 2 (IM2) fabric when Enhanced/Overlapping TI zones (ETIZs) are configured.
Page 854: Zone-1059
ZONE-1059 ZONE-1059 Message <timestamp>, [ZONE-1059], <sequence-number>,, WARNING, <system-name>, Unexpected TI routing behavior or a potentially unroutable TI configuration has been detected on local domain <Domain ID of the local Logical Switch where the error was detected>. Probable Cause Indicates that the current fabric topology and TI zone configuration may result in an unroutable condition or unexpected routing behavior.
Page 855 Section Audit Log Messages This section provides the Audit messages, including: • AUDIT AG System Messages ........771 •...
Page 856 Fabric OS Message Reference 53-1002448-01...
Page 857: Ag-1033
Chapter AUDIT AG System Messages AG-1033 Message <Sequence Number> AUDIT, <timestamp>, [AG-1033], INFO, CFG, <event-initiator-details>, <event-location>, , F_Port to N_Port mapping has been updated for N_Port (<n_port>). Probable Cause Indicates that the F_Ports mapped to an N_Port have changed and the configuration file has been updated.
Page 858: Ag-1037
AG-1036 AG-1036 Message <Sequence Number> AUDIT, <timestamp>, [AG-1036], WARNING, CFG, <event-initiator-details>, <event-location>, , Port <port> is connected to a Non-Brocade fabric with Persistent ALPA enabled. Check the admin guide for supported configuration . Probable Cause Indicates that one of the ports is connected to a non-Brocade fabric. Recommended No action is required.
Page 859: An-1003
Chapter AUDIT AN System Messages AN-1003 Message <Sequence Number> AUDIT, <timestamp>, [AN-1003], WARNING, FABRIC, <event-initiator-details>, <event-location>, , Latency bottleneck on port <slot number>/<port number within slot number>. <percentage of seconds affected by latency bottlenecking> pct. of <observation period over which the percentage of affected seconds is reported>...
Page 860: An-1006
AN-1006 Recommended No action is required. Action Severity INFO AN-1006 Message <Sequence Number> AUDIT, <timestamp>, [AN-1006], INFO, FABRIC, <event-initiator-details>, <event-location>, , Bottleneck detection configuration is successfully changed. Probable Cause Indicates that the bottleneck detection configuration was changed by a user. Recommended No action is required.
Page 861: An-1013
AN-1012 AN-1012 Message <Sequence Number> AUDIT, <timestamp>, [AN-1012], WARNING, FABRIC, <event-initiator-details>, <event-location>, , Credits did not return from other end. Complete loss of credits on a VC on slot <slot number> port <port number within slot number>. Probable Cause Indicates a credit loss. Recommended If this message is not followed by an AN-1013 message, please contact your vendor's customer Action...
Page 862 AN-1013 Fabric OS Message Reference 53-1002448-01...
Page 863: Auth-1046
Chapter AUDIT AUTH System Messages AUTH-1045 Message <Sequence Number> AUDIT, <timestamp>, [AUTH-1045], ERROR, SECURITY, <event-initiator-details>, <event-location>, , 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 864: Auth-3001
AUTH-3001 Run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity ERROR AUTH-3001 Message <Sequence Number> AUDIT, <timestamp>, [AUTH-3001], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: <Data type>...
Page 865: Auth-3004
AUTH-3004 AUTH-3004 Message <Sequence Number> AUDIT, <timestamp>, [AUTH-3004], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: failed, Info: Neighboring switch has a conflicting authentication policy; Port <Port Number> disabled. Probable Cause The specified E_Port was disabled because the neighboring switch rejected the authentication negotiation, and the local switch has a strict switch authentication policy.
Page 866: Auth-3007
AUTH-3007 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-3007 Message <Sequence Number> AUDIT, <timestamp>, [AUTH-3007], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: failed, Info: Port <port number>...
Page 867: Bls-1002
Chapter AUDIT BLS System Messages BLS-1002 Message <Sequence Number> AUDIT, <timestamp>, [BLS-1002], INFO, CFG, <event-initiator-details>, <event-location>, , An IPsec/IKE policy was added. Probable Cause Indicates that an Internet Protocol Security (IPSec) or Internet Key Exchange (IKE) policy was added and the configuration file has been updated. Recommended No action is required.
Page 868 BLS-1003 Fabric OS Message Reference 53-1002448-01...
Page 869: Ccfg-1002
Chapter AUDIT CCFG System Messages CCFG-1002 Message <Sequence Number> AUDIT, <timestamp>, [CCFG-1002], INFO, CFG, <event-initiator-details>, <event-location>, , Started loading CEE system configuration. Probable Cause Indicates that the CEE system configuration has started loading. Recommended No action is required. Action Severity INFO CCFG-1003 Message...
Page 870 CCFG-1013 Fabric OS Message Reference 53-1002448-01...
Page 871: Cnm-3001
Chapter AUDIT CNM System Messages CNM-3001 Message <Sequence Number> AUDIT, <timestamp>, [CNM-3001], INFO, SECURITY, <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...
Page 872: Cnm-3004
CNM-3004 CNM-3004 Message <Sequence Number> AUDIT, <timestamp>, [CNM-3004], INFO, SECURITY, <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...
Page 873: Cnm-3008
CNM-3008 Recommended No action is required. Action Severity INFO CNM-3008 Message <Sequence Number> AUDIT, <timestamp>, [CNM-3008], INFO, SECURITY, <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 874: Cnm-3011
CNM-3011 CNM-3011 Message <Sequence Number> AUDIT, <timestamp>, [CNM-3011], INFO, SECURITY, <event-initiator-details>, <event-location>, , 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 <Sequence Number> AUDIT, <timestamp>, [CNM-3012], INFO, SECURITY, <event-initiator-details>, <event-location>, , Deleteing an EG with luns setup for encryption can lead to luns being disabled if Encryption Group name is not preserved (<egname>).
Page 875: Conf-1020
Chapter AUDIT CONF System Messages CONF-1000 Message <Sequence Number> 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 Info about the parameters and AD variable is the description of the classes of configuration parameters that were downloaded.
Page 876: Conf-1042
CONF-1042 CONF-1042 Message <Sequence Number> AUDIT, <timestamp>, [CONF-1042], INFO, CFG, <event-initiator-details>, <event-location>, , Fabric Configuration Parameter <parameter> changed to <value>. Probable Cause Indicates that the fabric configuration parameter value has been changed. Recommended No action is required. Action Severity INFO CONF-1043 Message <timestamp>, [CONF-1043], INFO, CFG, <event-initiator-details>, <event-location>,...
Page 877: Cvlm-3001
Chapter AUDIT CVLM System Messages CVLM-3001 Message <Sequence Number> AUDIT, <timestamp>, [CVLM-3001], INFO, SECURITY, <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...
Page 878: Cvlm-3005
CVLM-3004 CVLM-3004 Message <Sequence Number> AUDIT, <timestamp>, [CVLM-3004], INFO, SECURITY, <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 879: Cvlm-3009
CVLM-3008 Recommended No action is required. Action Severity INFO CVLM-3008 Message <Sequence Number> AUDIT, <timestamp>, [CVLM-3008], INFO, SECURITY, <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...
Page 880: Cvlm-3011
CVLM-3011 CVLM-3011 Message <Sequence Number> AUDIT, <timestamp>, [CVLM-3011], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: cryptocfg Status: success, Info: Initiator PWWN \<initiatorPWWN>\ Initiator NWWN \<initiatorNWWN>\ added to crypto target container \<cryptoTargetContainer>\. Probable Cause Indicates an initiator was added to a cryptotarget container. Recommended No action is required.
Page 881: Cvlm-3016
CVLM-3015 Recommended No action is required. Action Severity INFO CVLM-3015 Message <Sequence Number> AUDIT, <timestamp>, [CVLM-3015], INFO, SECURITY, <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.
Page 882: Cvlm-3018
CVLM-3018 CVLM-3018 Message <Sequence Number> AUDIT, <timestamp>, [CVLM-3018], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: cryptocfg Status: success, Info: Tape pool \<tapepoolLabelOrNum>\ deleted. Probable Cause Indicates a tapepool was deleted. Recommended No action is required. Action Severity INFO CVLM-3019 Message <Sequence Number> AUDIT, <timestamp>, [CVLM-3019], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: cryptocfg Status: success, Info: Tape pool \<tapepoolLabelOrNum>\ modified.
Page 883: Cvlm-3022
CVLM-3022 Recommended No action is required. Action Severity INFO CVLM-3022 Message <Sequence Number> AUDIT, <timestamp>, [CVLM-3022], INFO, SECURITY, <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.
Page 884: Cvlm-3025
CVLM-3025 CVLM-3025 Message <Sequence Number> AUDIT, <timestamp>, [CVLM-3025], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: cryptocfg Status: started, Info: Decommission of device (container <cryptoTargetContainer> initiator <Initiator>, LUN <Lun>). Probable Cause Indicates that the decommission operation has started. Recommended No action is required. Action Severity INFO...
Page 885 CVLM-3028 Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1002448-01...
Page 886 CVLM-3028 Fabric OS Message Reference 53-1002448-01...
Page 887: Ess-1008
Chapter AUDIT ESS System Messages ESS-1008 Message <Sequence Number> AUDIT, <timestamp>, [ESS-1008], INFO, FABRIC, <event-initiator-details>, <event-location>, , Fabric Name - <fabric_name> configured (received from domain <domain id>). Probable Cause Indicates that the fabric name is configured or renamed. Recommended No action is required. Action Severity INFO...
Page 888 ESS-1010 Fabric OS Message Reference 53-1002448-01...
Page 889: Fcip-1002
Chapter AUDIT FCIP System Messages FCIP-1002 Message <Sequence Number> 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 890 FCIP-1003 Fabric OS Message Reference 53-1002448-01...
Page 891: Ficu-1012
Chapter AUDIT FICU System Messages FICU-1011 Message <Sequence Number> AUDIT, <timestamp>, [FICU-1011], INFO, CFG, <event-initiator-details>, <event-location>,, FMS mode has been enabled. Probable Cause Indicates that FMS mode has been enabled. Recommended No action is required. Action Severity INFO FICU-1012 Message <Sequence Number>...
Page 892: Ficu-1020
FICU-1020 FICU-1020 Message <Sequence Number> AUDIT, <timestamp>, [FICU-1020], INFO, CFG, <event-initiator-details>, <event-location>, , Port Addrs (<port mask>) have been Blocked by <source>. Probable Cause Indicates that FMS has blocked the specified ports. Recommended No action is required. Action Severity INFO FICU-1021 Message <Sequence Number>...
Page 893: Fw-1202
Chapter AUDIT FW System Messages FW-1202 Message <Sequence Number> AUDIT, <timestamp>, [FW-1202], WARNING, FW, <event-initiator-details>, <event-location>, , <Port Name>, <Label>, is above high boundaries (High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the number of C3 transmit time out frames is above high threshold. Recommended Check the target device;...
Page 894: Fw-1404
FW-1404 FW-1404 Message <Sequence Number> AUDIT, <timestamp>, [FW-1404], WARNING, FW, <event-initiator-details>, <event-location>, , <Label>,is above high boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Cause Indicates that the CPU or memory usage is above its threshold. If this RASLOG is pertaining to memory usage then the usage is above middle memory threshold.
Page 895 FW-3001 Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1002448-01...
Page 896 FW-3001 Fabric OS Message Reference 53-1002448-01...
Page 897: Http-1002
Chapter AUDIT HTTP System Messages HTTP-1002 Message <Sequence Number> 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.
Page 898 HTTP-1003 Fabric OS Message Reference 53-1002448-01...
Page 899: Ipad-1002
Chapter AUDIT IPAD System Messages IPAD-1002 Message <Sequence Number> 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 900 IPAD-1002 Fabric OS Message Reference 53-1002448-01...
Page 901: Ms-1027
Chapter AUDIT MS System Messages MS-1027 Message <Sequence Number> AUDIT, <timestamp>, [MS-1027], INFO, FABRIC, <event-initiator-details>, <event-location>, , Fabric Name - <fabric_name> configured. Probable Cause Indicates that the fabric name is configured or renamed. Recommended This is an informational message and does not require any action. Action Severity INFO...
Page 902 MS-1029 Fabric OS Message Reference 53-1002448-01...
Page 903: Pmgr-1003
Chapter AUDIT PMGR System Messages PMGR-1001 Message <Sequence Number> AUDIT, <timestamp>, [PMGR-1001], INFO, LS, <event-initiator-details>, <event-location>, , 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...
Page 904 PMGR-1003 Fabric OS Message Reference 53-1002448-01...
Page 905: Port-1007
Chapter AUDIT PORT System Messages PORT-1006 Message <Sequence Number> 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 906: Port-1009
PORT-1009 PORT-1009 Message <Sequence Number> AUDIT, <timestamp>, [PORT-1009], INFO, CFG, <event-initiator-details>, <event-location>, , GigE Port (ID: <port number>) has been disabled. Probable Cause Indicates a GigE port has been disabled. Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1002448-01...
Page 907: Ras-2001
Chapter AUDIT RAS System Messages RAS-2001 Message <Sequence Number> AUDIT, <timestamp>, [RAS-2001], INFO, SYSTEM, <event-initiator-details>, <event-location>, , <system-name>, Audit message log is enabled. Probable Cause Indicates that the audit message log has been enabled. Recommended No action is required. Action Severity INFO RAS-2002...
Page 908 RAS-2003 Fabric OS Message Reference 53-1002448-01...
Page 909: Sec-1113
Chapter AUDIT SEC System Messages SEC-1113 Message <Sequence Number> AUDIT, <timestamp>, [SEC-1113], WARNING, SECURITY, <event-initiator-details>, <event-location>, , <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 910: Sec-3002
SEC-3002 SEC-3002 Message <Sequence Number> 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: •...
Page 911: Sec-3005
SEC-3005 SEC-3005 Message <Sequence Number> AUDIT, <timestamp>, [SEC-3005], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Added member(s) <Members added> to policy <Policy name>. Probable Cause Indicates new members have been added to the specified 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.
Page 912: Sec-3008
SEC-3008 SEC-3008 Message <Sequence Number> 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 913: Sec-3012
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 914: Sec-3015
SEC-3015 SEC-3015 Message <Sequence Number> AUDIT, <timestamp>, [SEC-3015], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Moved 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 or LDAP) server.
Page 915: Sec-3018
SEC-3018 SEC-3018 Message <Sequence Number> 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 916: Sec-3021
SEC-3021 SEC-3021 Message <Sequence Number> AUDIT, <timestamp>, [SEC-3021], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: failed, Info: Failed login attempt via <connection method and IP Address>. Probable Cause Indicates a failed login attempt occurred. 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 917: Sec-3025
SEC-3025 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-3025 Message <Sequence Number>...
Page 918: Sec-3028
SEC-3028 SEC-3028 Message <Sequence Number> AUDIT, <timestamp>, [SEC-3028], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: User account [<User Name>] deleted. Probable Cause Indicates the specified user account was deleted. 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 919: Sec-3032
SEC-3032 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-3032 Message <Sequence Number> AUDIT, <timestamp>, [SEC-3032], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Switch is configured to <accept or reject>...
Page 920: Sec-3035
SEC-3035 SEC-3035 Message <Sequence Number> AUDIT, <timestamp>, [SEC-3035], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: ipfilter, Status: success, Info: <IP Filter Policy> IP filter policy(ies) saved. Probable Cause Indicates the specified IP filter policies have been saved. Recommended Verify the security event was planned. If the security event was planned, no action is required. If the Action security event was not planned, take appropriate action as defined by your enterprise security policy.
Page 921: Sec-3039
SEC-3039 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-3039 Message <Sequence Number>...
Page 922: Sec-3046
SEC-3046 SEC-3046 Message <Sequence Number> AUDIT, <timestamp>, [SEC-3046], INFO, SECURITY, <event-initiator-details>, <event-location>, The FIPS Self Tests mode has been set to <Self Test Mode>. Probable Cause Indicates there was a change in the FIPS Self Test mode. Recommended Verify the security event was planned. If the security event was planned, no action is required. If the Action security event was not planned, take appropriate action as defined by your enterprise security policy.
Page 923: Sec-3051
SEC-3050 Recommended No action is required. Action Severity INFO SEC-3050 Message <Sequence Number> AUDIT, <timestamp>, [SEC-3050], INFO, SECURITY, Event: <Event Name>, Status: success, Info: <Event Specific Info>. 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 924: Sec-3064
SEC-3063 Recommended No action is required. Action Severity INFO SEC-3063 Message <Sequence Number> AUDIT, <timestamp>, [SEC-3063], INFO, SECURITY, <event-initiator-details>, <event-location>, , Role ‘<Role Name>’ is copied from ‘<Source Role>’. Probable Cause Indicates that the specified role name has been copied from the source role. Recommended No action is required.
Page 925: Sec-3066
SEC-3066 SEC-3066 Message <Sequence Number> AUDIT, <timestamp>, [SEC-3066], INFO, SECURITY, <event-initiator-details>, <event-location>, , Configuration of user-defined roles is downloaded. Probable Cause Indicates the configuration of user-defined roles have been downloaded. Recommended No action is required. Action Severity INFO SEC-3067 Message <Sequence Number>...
Page 926 SEC-4001 Fabric OS Message Reference 53-1002448-01...
Page 927: Snmp-1005
Chapter AUDIT SNMP System Messages SNMP-1004 Message <Sequence Number> AUDIT, <timestamp>, [SNMP-1004], ERROR, CFG, <event-initiator-details>, <event-location>, , Incorrect SNMP configuration. Probable Cause Indicates that the SNMP configuration is incorrect and therefore the SNMP service will not work correctly. Recommended Change the SNMP configuration to default using the snmpConfig default command.
Page 928: Snmp-1009
SNMP-1009 SNMP-1009 Message <Sequence Number> AUDIT, <timestamp>, [SNMP-1009], INFO, CFG, <event-initiator-details>, <event-location>, , Port traps are <blocked state> on port <port>. Probable Cause Indicates the blocked or unblocked status of the port traps on the specified port. Recommended Execute the snmpTraps show command to view the current status of the port.
Page 929: Spm-3001
Chapter AUDIT SPM System Messages SPM-3001 Message <Sequence Number> AUDIT, <timestamp>, [SPM-3001], INFO, SECURITY, <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 <Sequence Number>...
Page 930: Spm-3005
SPM-3004 SPM-3004 Message <Sequence Number> AUDIT, <timestamp>, [SPM-3004], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: cryptocfg Status: success, Info: EE in slot <slot> enabled. Probable Cause Indicates an encryption engine was enabled. Recommended No action is required. Action Severity INFO SPM-3005 Message <Sequence Number>...
Page 931: Spm-3009
SPM-3008 Recommended No action is required. Action Severity INFO SPM-3008 Message <Sequence Number> AUDIT, <timestamp>, [SPM-3008], INFO, SECURITY, <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.
Page 932: Spm-3011
SPM-3011 SPM-3011 Message <Sequence Number> AUDIT, <timestamp>, [SPM-3011], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: cryptocfg Status: success, Info: Local file \"<filename>\" deleted. Probable Cause Indicates a locally stored file was deleted. Recommended No action is required. Action Severity INFO SPM-3012 Message <Sequence Number>...
Page 933: Spm-3015
SPM-3015 Recommended No action is required. Action Severity INFO SPM-3015 Message <Sequence Number> AUDIT, <timestamp>, [SPM-3015], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: cryptocfg Status: success, Info: Key vault type set to <keyVaultType>. Probable Cause Indicates the key vault type was set. Recommended No action is required.
Page 934: Spm-3018
SPM-3018 SPM-3018 Message <Sequence Number> AUDIT, <timestamp>, [SPM-3018], INFO, SECURITY, <event-initiator-details>, <event-location>,, 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 <Sequence Number> AUDIT, <timestamp>, [SPM-3019], INFO, SECURITY, <event-initiator-details>, <event-location>,, Event: cryptocfg Status: success, Info: System card registered.
Page 935: Spm-3022
SPM-3022 Recommended No action is required. Action Severity INFO SPM-3022 Message <Sequence Number> AUDIT, <timestamp>, [SPM-3022], INFO, SECURITY, <event-initiator-details>, <event-location>,,Event: cryptocfg Status: success, Info: Authentication card with certificate label \"<certLabel>\" deregistered. Probable Cause Indicates an authentication card was deregistered. Recommended No action is required.
Page 936: Spm-3025
SPM-3025 SPM-3025 Message <Sequence Number> AUDIT, <timestamp>, [SPM-3025], INFO, SECURITY, <event-initiator-details>, <event-location>, , Event: cryptocfg Status: success, Info: File imported via usb: Source: <sourcePath> Destination: <destinationFilename>. Probable Cause Indicates a file was imported via USB device. Recommended No action is required. Action Severity INFO...
Page 937: Spm-3029
SPM-3029 Recommended No action is required. Action Severity INFO SPM-3029 Message <Sequence Number> AUDIT, <timestamp>, [SPM-3029], INFO, <event-initiator-details>, <event-location>, , Event: KeyVault Connection Status: <status>, Info:KAC_Connect: <kac status>. Probable Cause Indicates the status of key vault. Recommended No action is required. Action Severity INFO...
Page 938 SPM-3029 Fabric OS Message Reference 53-1002448-01...
Page 939: Sulb-1002
Chapter AUDIT SULB System Messages SULB-1001 Message <Sequence Number> 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 940: Sulb-1009
SULB-1004 SULB-1004 Message <Sequence Number> 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 <Sequence Number>...
Page 941 SULB-1009 TABLE 10 Status messages and status codes (Continued) 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 942 SULB-1009 TABLE 10 Status messages and status codes (Continued) 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 943 SULB-1009 TABLE 10 Status messages and status codes (Continued) 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 944 SULB-1009 TABLE 11 Error messages and error codes (Continued) Error message Error code "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." 0x26 "Unexpected reboot."...
Page 945 SULB-1009 0x29 - The pre-install script failed. This error may be caused by an unsupported blade type in the chassis. Remove or power off the unsupported blades before proceeding. Another possible cause may be an invalid chassisConfig option setting. In that case, reset the chassisConfig option before retrying firmwareDownload.
Page 946: Sulb-1017
SULB-1010 In a director-class switch, when firmwareDownload fails, the two CPs may end up with different versions of firmware and they may not gain high-availability (HA) sync. In that case, run firmwareDownload single mode (-s) to upgrade the firmware on the standby CP to the same version as the active CP.
Page 947: Sulb-1020
SULB-1020 Recommended Run the slotShow command. If the blade is in a FAULTY state, run the slotPowerOff and Action slotPowerOn commands to trigger another firmwareDownload. If the blade is stuck in LOADING state, remove and re-insert the blade to trigger another firmwareDownload. If the problem persists, contact your switch service provider.
Page 948: Sulb-1024
SULB-1024 Recommended The firmwareCommit command will be started automatically after the blade boots up to repair the Action secondary partition. If at the end of firmwareCommit, the blade firmware version is still inconsistent with the active CP firmware, firmwareDownload will automatically be restarted on the blade.
Page 949: Sulb-1031
SULB-1031 Recommended The firmwareDownload command will continue after the switch has rebooted. Run the Action firmwareDownloadStatus command to monitor progress. If the problem persists, contact your switch service provider. Severity WARNING SULB-1031 Message <Sequence Number> AUDIT, <timestamp>, [SULB-1031], WARNING, FIRMWARE, <event-initiator-details>, <event-location>, , The switch is relocating an internal firmware image.
Page 950: Sulb-1034
SULB-1034 SULB-1034 Message <Sequence Number> AUDIT, <timestamp>, [SULB-1034], ERROR, FIRMWARE, <event-initiator-details>, <event-location>, Relocation of internal image timed out. Probable Cause Indicates there may be an error caused by a switch initialization issue after the internal image is relocated. It may also be caused by an internal Ethernet issue or by persistent storage failure. Recommended Reboot the switch.
Page 951: Sulb-1038
SULB-1038 SULB-1038 Message <Sequence Number> AUDIT, <timestamp>, [SULB-1038], WARNING, FIRMWARE, Co-CPU has not booted up properly. Skip the firmwaredownload command on the co-CPU. Probable Cause Indicates that the Main CPU cannot access the co-CPU to update the firmware on the co-CPU or run any other firmwaredownload command on the co-CPU.
Page 952: Sulb-1041
SULB-1041 SULB-1041 Message <Sequence Number> AUDIT, <timestamp>, [SULB-1041], INFO, FIRMWARE, <event-initiator-details>, <event-location>, , Firmware has been activated successfully on standby CP. Probable Cause Indicates the firmwareActivate command has completed successfully on standby CP. Recommended No action is required. The firmwareActivate command has completed on standby CP as expected. Action Run the firmwareShow command to verify the firmware versions.
Page 953: Swch-1012
Chapter AUDIT SWCH System Messages SWCH-1012 Message <Sequence Number> 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 that a Trunk Area has been enabled for one or more ports and the config file has been updated.
Page 954 SWCH-1014 Fabric OS Message Reference 53-1002448-01...
Page 955: Ucst-1022
Chapter AUDIT UCST System Messages UCST-1021 Message <Sequence Number> 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.
Page 956: Ucst-1024
UCST-1024 UCST-1024 Message <Sequence Number> 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 <Sequence Number>...
Page 957 UCST-1027 Recommended No action is required. Action Severity INFO Fabric OS Message Reference 53-1002448-01...
Page 958 UCST-1027 Fabric OS Message Reference 53-1002448-01...
Page 959: Zone-3001
Chapter AUDIT ZONE System Messages ZONE-3001 Message <Sequence Number> 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 960: Zone-3004
ZONE-3004 The zone object type variable can be alias, zone member, zone, or zone configuration. Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was Action not planned, take appropriate action as defined by your enterprise security policy. Severity INFO ZONE-3004...
Page 961: Zone-3007
ZONE-3007 ZONE-3007 Message <Sequence Number> AUDIT, <timestamp>, [ZONE-3007], INFO, ZONE, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Zone configuration \"<Zone configuration>\" enabled. <AD Id>. Probable Cause Indicates that the specified zone configuration has been enabled. Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was Action not planned, take appropriate action as defined by your enterprise security policy.
Page 962: Zone-3011
ZONE-3011 Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was Action not planned, take appropriate action as defined by your enterprise security policy. Severity INFO ZONE-3011 Message <Sequence Number> AUDIT, <timestamp>, [ZONE-3011], INFO, ZONE, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: Zone object \"<Zone object name>\"...
Page 963: Zone-3014
ZONE-3014 ZONE-3014 Message <Sequence Number> AUDIT, <timestamp>, [ZONE-3014], INFO, FABRIC, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: \"<AD object member list>\" added to <AD object set type> \"<AD object set name>\". Probable Cause Indicates that the specified new AD object member or members have been added to the specified AD object set.
Page 964: Zone-3017
ZONE-3017 ZONE-3017 Message <Sequence Number> AUDIT, <timestamp>, [ZONE-3017], INFO, FABRIC, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: <AD object set type> \"<AD object set name>\" created with \"<AD object member list>\". Probable Cause Indicates that the specified AD has been created. The AD object set type variable can be an AD alias or AD member.
Page 965: Zone-3021
ZONE-3021 Recommended Verify that the event was planned. If the event was planned, no action is required. If the event was Action not planned, take appropriate action as defined by your enterprise security policy. Severity INFO ZONE-3021 Message <Sequence Number> AUDIT, <timestamp>, [ZONE-3021], INFO, FABRIC, <event-initiator-details>, <event-location>, , Event: <Event Name>, Status: success, Info: AD object \"<AD object name>\"...
Page 966: Zone-3024
ZONE-3024 ZONE-3024 Message <Sequence Number> AUDIT, <timestamp>, [ZONE-3024], INFO, FABRIC, <event-initiator-details>, <event-location>, , Command: <Command Name>, Status: success, Info: executed. <AD Id>. Probable Cause Indicates that the ad transabort command has completed successfully in the specified AD. 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.

This manual is also suitable for:

Brocade 8/12c Brocade 8/24c Fabric os v7.0.1

Brocade Communications Systems SN3000B Reference

Table of Contents

Introduction to System Messages

Chapter 1 Introduction to System Messages

Section I

Chapter 2 AG System Messages

Chapter 3 AN System Messages

Chapter 4 ANV System Messages

Chapter 5 AUTH System Messages

Chapter 6 BKSW System Messages

Chapter 7 BL System Messages

Chapter 8 BLL System Messages

Chapter 9 BLS System Messages

Chapter 10 BM System Messages

Chapter 11 C2 System Messages

Chapter 12 C3 System Messages

Chapter 13 CAL System Messages

Chapter 14 CCFG System Messages

Chapter 15 CDR System Messages

Chapter 16 CER System Messages

Chapter 17 CHS System Messages

Chapter 18 CNM System Messages

Chapter 19 CONF System Messages

Chapter 20 CTAP System Messages

Chapter 21 CVLC System Messages

Chapter 22 CVLM System Messages

Chapter 23 DAUTH System Messages

Chapter 24 ECC System Messages

Chapter 25 EM System Messages

Chapter 26 ESS System Messages

Chapter 27 ESWCH System Messages

Chapter 28 EVMD System Messages

Chapter 29 FABR System Messages

Chapter 30 FABS System Messages

Chapter 31 FBC System Messages

Chapter 32 FCIP System Messages

Chapter 33 FCMC System Messages

Chapter 34 FCOE System Messages

Chapter 35 FCPD System Messages

Chapter 36 FCPH System Messages

Chapter 37 FCR System Messages

Chapter 38 FICON System Messages

Chapter 39 FICU System Messages

Chapter 40 FKLB System Messages

Chapter 41 FLOD System Messages

Chapter 42 FSPF System Messages

Chapter 43 FSS System Messages

Chapter 44 FSSM System Messages

Chapter 45 FW System Messages

Chapter 46 HAM System Messages

Chapter 47 HAMK System Messages

Chapter 48 HIL System Messages

Chapter 49 HLO System Messages

Chapter 50 HMON System Messages

Chapter 51 HSL System Messages

Chapter 128 AUDIT HTTP System Messages

Chapter 52 HTTP System Messages

Chapter 53 IBD System Messages

Chapter 54 IBPD System Messages

Chapter 55 ICPD System Messages

Chapter 129 AUDIT IPAD System Messages

Chapter 56 IPAD System Messages

Chapter 57 IPS System Messages

Chapter 58 ISNS System Messages

Chapter 59 KAC System Messages

Chapter 60 KSWD System Messages

Chapter 61 KTRC System Messages

Chapter 62 L2SYS System Messages

Chapter 63 L3SS System Messages

Chapter 64 LACP System Messages

Chapter 65 LANCE System Messages

Chapter 66 LFM System Messages

Chapter 67 LOG System Messages

Chapter 68 LSDB System Messages

Chapter 69 MCAST_SS System Messages

Chapter 70 MFIC System Messages

Chapter 71 MPTH System Messages

Chapter 72 MQ System Messages

Chapter 73 MS System Messages

Chapter 130 AUDIT MS System Messages