Brocade Communications Systems AA979A - StorageWorks SAN Switch 2/8V Reference Manual
Brocade Communications Systems AA979A - StorageWorks SAN Switch 2/8V Reference Manual

Brocade Communications Systems AA979A - StorageWorks SAN Switch 2/8V Reference Manual

Brocade fabric os message reference guide (53-1000242-01, november 2006)
Hide thumbs Also See for AA979A - StorageWorks SAN Switch 2/8V:

Advertisement

Fabric OS
Message Reference
Supporting Fabric OS v5.2.0
Publication Number: 53-1000242-01
Publication Date: 09/29/06

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the AA979A - StorageWorks SAN Switch 2/8V and is the answer not in the manual?

Questions and answers

Summary of Contents for Brocade Communications Systems AA979A - StorageWorks SAN Switch 2/8V

  • Page 1 Fabric OS Message Reference Supporting Fabric OS v5.2.0 Publication Number: 53-1000242-01 Publication Date: 09/29/06...
  • Page 2 Copyright © 2006, Brocade Communications Systems, Incorporated. ALL RIGHTS RESERVED. Publication Number: 53-1000242-01 Brocade, the Brocade B weave logo, Secure Fabric OS, and SilkWorm are registered trademarks and Tapestry is a trademark of Brocade Communications Systems, Inc., in the United States and/or in other countries. FICON, IBM BladeCenter are registered trademarks of IBM Corporation in the U.S.
  • Page 3 Document History The following table lists all versions of the Brocade Fabric OS Message Reference. Document Title Publication Summary of Changes Publication Number Date Diagnostic and System Error 53-0000210-02 First release March 2002 Message Reference v3.0, v4.0 Diagnostic and System Error 53-0000511-04 Major content reorganization June 2003...
  • Page 5: Table Of Contents

    Contents About This Document How This Document Is Organized ....... . xlvii Supported Hardware and Software .
  • Page 6 Responding to a System Message........1-12 Looking Up a System Message ....... . 1-12 Gathering Information About the Problem .
  • Page 7 AUTH-1028 ..........AUTH-1029 .
  • Page 8 BL-1020 ........... . . BL-1021 .
  • Page 9 BM-1056 ........... . . BM-1058 .
  • Page 10 EM-1015 ........... . . EM-1016 .
  • Page 11 EM-1062 ........... . . 2-17 EM-1063 .
  • Page 12 FABR-1029 ........... 2-10 FABR-1030 .
  • Page 13 FCPD-1003 ........... Chapter 17 FCPH System Messages FCPH-1001 .
  • Page 14 FCR-1029 ........... . 2-10 FCR-1030 .
  • Page 15 FCR-1067 ........... . 2-20 FCR-1068 .
  • Page 16 FSPF-1002 ........... FSPF-1003 .
  • Page 17 FW-1033 ........... . . FW-1034 .
  • Page 18 FW-1124 ........... . . 2-16 FW-1125 .
  • Page 19 FW-1174 ........... . . 2-28 FW-1175 .
  • Page 20 FW-1245 ........... . . 2-39 FW-1246 .
  • Page 21 FW-1316 ........... . . 2-51 FW-1317 .
  • Page 22 FW-1347 ........... . . 2-63 FW-1348 .
  • Page 23 FW-1378 ........... . . 2-75 FW-1379 .
  • Page 24 Chapter 26 HAM System Messages HAM-1001 ........... HAM-1002 .
  • Page 25 HIL-1305 ........... . HIL-1306 .
  • Page 26 Chapter 31 HTTP System Messages HTTP-1001 ........... HTTP-1002 .
  • Page 27 Chapter 36 ISNS System Messages ISNS-1001 ........... ISNS-1002 .
  • Page 28 LSDB-1004 ........... Chapter 41 MFIC System Messages MFIC-1001 .
  • Page 29 Chapter 46 NS System Messages NS-1001 ........... . . NS-1002 .
  • Page 30 PLAT-1001 ........... Chapter 50 PORT System Messages PORT-1003 .
  • Page 31 RCS-1005 ........... . RCS-1006 .
  • Page 32 SEC-1022 ........... . SEC-1024 .
  • Page 33 SEC-1059 ........... . 3-15 SEC-1062 .
  • Page 34 SEC-1096 ........... . 3-25 SEC-1097 .
  • Page 35 SEC-1142 ........... . 3-35 SEC-1145 .
  • Page 36 SEC-1187 ........... . 3-46 SEC-1188 .
  • Page 37 SEC-1311 ........... . 3-57 SEC-1312 .
  • Page 38 SULB-1006 ........... SULB-1007 .
  • Page 39 SYSM-1004 ..........SYSM-1005 .
  • Page 40 Chapter 68 UCST System Messages UCST-1003 ........... UCST-1007 .
  • Page 41 ZONE-1010 ..........ZONE-1012 .
  • Page 42 ZONE-1046 ..........3-15 Section II Audit Log Messages Chapter 74...
  • Page 43 SEC-3014 ........... . SEC-3015 .
  • Page 44 SULB-1017 ........... SULB-1018 .
  • Page 45 ZONE-3022 ..........ZONE-3023 .
  • Page 46 xlvi Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 47: About This Document

    About This Document This document is a command reference manual written to help system administrators and technicians operate, maintain, and troubleshoot SAN products. “About This Document” contains the following sections: • “How This Document Is Organized,” next • “Supported Hardware and Software” on page xlvii •...
  • Page 48: What's New In This Document

    • Brocade SilkWorm 7500 switch • Brocade SilkWorm 24000 director • Brocade SilkWorm 48000 director In those instances in which procedures or parts of procedures documented here apply to some switches but not to others, this guide identifies exactly which switches are supported and which are not. Although many different software and hardware configurations are tested and supported by Brocade Communications Systems, Inc.
  • Page 49: Document Conventions

    Document Conventions This section describes text formatting conventions and important notices formats. Text Formatting The narrative-text formatting conventions that are used in this document are as follows: bold text Identifies command and method names Identifies GUI elements Identifies keywords and operands Identifies text to enter at the GUI or CLI italic text Provides emphasis...
  • Page 50: Additional Information

    Additional Information This section lists additional Brocade and industry-specific documentation that you might find helpful. Brocade Resources The following related documentation is provided on the Brocade Documentation CD-ROM and on the Brocade Web site, through Brocade Connect. Note Go to http://www.brocade.com and click Brocade Connect to register at no cost for a user ID and password.
  • Page 51 • Cable Management Tray and Guide Replacement Procedure • Chassis Door Replacement Procedure • WWN Bezel and Card Replacement Procedure • Power Supply and Filler Panel Replacement Procedure • SilkWorm Director Migration Guide • 14U Rack Mount Kit Installation Procedure •...
  • Page 52: Optional Brocade Features

    For additional Brocade documentation, visit the Brocade SAN Info Center and click the Resource Library location: http://www.brocade.com Release notes are available on the Brocade Connect Web site and are also bundled with the Fabric OS firmware. Optional Brocade Features Optional Brocade features include: Advanced Performance Monitoring Enables more effective end-to-end SAN performance analysis to enhance performance tuning, increase productivity, optimize resource utilization, and...
  • Page 53: Other Industry Resources

    Other Industry Resources For additional resource information, visit the Technical Committee T11 Web site. This Web site provides interface standards for high-performance and mass storage applications for Fibre Channel, storage management, and other applications: http://www.t11.org For information about the Fibre Channel industry, visit the Fibre Channel Industry Association Web site: http://www.fibrechannel.org Getting Technical Help...
  • Page 54: Document Feedback

    Document Feedback Because quality is our first concern at Brocade, we have made every effort to ensure the accuracy and completeness of this document. However, if you find an error or an omission, or you think that a topic needs further development, we want to hear from you. Forward your feedback to: documentation@brocade.com Provide the title and version number and as much detail as possible about your issue, including the topic heading and page number and your suggestions for improvement.
  • Page 55: Introduction To System Messages

    Chapter Introduction to System Messages This guide supports Fabric OS v5.2.0 and documents system messages that you can use to diagnose and fix problems with the switch or fabric. The messages are organized first by event type, AUDIT or RASLog, then alphabetically by module name. A module is a subsystem in the Fabric OS. Each module generates a set of numbered messages.
  • Page 56: System Logging Daemon (Syslogd)

    Overview of System Messages • Messages are numbered sequentially from 1 to 2,147,483,647 (0x7ffffff). The sequence number will continue to increase beyond the storage limit of 1024 messages. The sequence number can be reset to 1 using the errClear command. The sequence number is persistent across power cycles and switch reboots.
  • Page 57: System Console

    Overview of System Messages Fabric OS can be configured to use a UNIX-style syslogd process to forward system events and error messages to log files on a remote host system. The host system can be running UNIX, Linux, or any other operating system that supports the standard syslogd functionality.
  • Page 58: Viewing And Configuring System Message Logs

    Viewing and Configuring System Message Logs Viewing and Configuring System Message Logs This section provides information on viewing and configuring system message logs, including: • “Viewing System Messages from Web Tools” on page 1-6 • “Dumping System Messages” on page 1-6 •...
  • Page 59 Viewing and Configuring System Message Logs Table 1-1 Commands Used to View or Configure the System Logs (Continued) Command Description portLogShowPort Displays the port log of specified port, with page breaks. portLogTypeDisable Disables an event from reporting to the port log. Port log events are described by the portLogEventShow command.
  • Page 60: Viewing System Messages From Web Tools

    Viewing and Configuring System Message Logs Viewing System Messages from Web Tools This procedure is valid for the SilkWorm 200E, 3016, 3250, 3850, 3900, 4100, 24000, and 48000. To view the system message log for a switch from Web Tools: Launch Web Tools.
  • Page 61: Viewing The System Messages With Page Breaks

    Viewing and Configuring System Message Logs Viewing the System Messages with Page Breaks This procedure is valid for the SilkWorm 200E, 3250, 3850, 3900, 4100, 24000, and 48000 products. To display the system message log, with page breaks: Log in to the switch as admin. At the command line, enter the errShow command: switch:admin>...
  • Page 62: Reading A Ras System Message

    Reading a RAS System Message Reading a RAS System Message This section provides information about reading system messages. The following example shows the sample format of the RAS system error message: <timestamp>, [<Event ID>], <Sequence Number>, <Flags>,<Severity>,<Switch name>, <Event-specific information> The following example shows a sample message from the error log: 2004/07/22-10:12:33, [EM-1031], 4,, ERROR, switchname, Slot 7 ejector not closed...
  • Page 63: Audit Event Messages

    Reading a RAS System Message Table 1-2 System Message Field Description (Continued) Example Variable Name Description Audit and/or For most messages, this field contains a space <NULL> FFDC Flags character (null value) indicating that the message (blank) is neither an AUDIT or FFDC message. Messages may contain the following values: •...
  • Page 64 Reading a RAS System Message The following is an sample audit event message: AUDIT, 2005/12/10-09:54:03, [SEC-1000], WARNING, SECURITY, JohnSmith/root/ 192.168.132.10/Telnet/CLI, Domain A/JohnsSwitch, , Incorrect password during login attempt. The fields in the error message are described in table below. Table 1-3 Audit Message Field Description Example Variable Name...
  • Page 65 Reading a RAS System Message Table 1-3 Audit Message Field Description (Continued) Example Variable Name Description Switch name or This field displays the defined switch name or switchname chassis name, the chassis name of the switch. This value is depending on the truncated if it is over 16 characters in length.
  • Page 66: Message Severity Levels

    Responding to a System Message Message Severity Levels There are four levels of severity for messages, ranging from Critical (1) to Info (4). In general, the definitions are wide ranging and are to be used as general guidelines for troubleshooting. For all cases, you should look at each specific error message description thoroughly before taking action.
  • Page 67: Gathering Information About The Problem

    Responding to a System Message • Recommended action • Message severity Gathering Information About the Problem Common steps and questions to ask yourself when troubleshooting a system message are as follows: What is the current Fabric OS level? What is the switch hardware version? Is the switch operational? Assess impact and urgency: Is the switch down?
  • Page 68: Panic Dump And Core Dump Files

    Responding to a System Message Panic Dump and Core Dump Files The Fabric OS creates panic dump files and core files when there are problems in the Fabric OS kernel. You can view panic dump files using the pdShow command. These files can build up in the kernel partition (typically because of failovers) and might need to be periodically deleted or downloaded using the saveCore command.
  • Page 69: System Module Descriptions

    System Module Descriptions System Module Descriptions Table 1-4 provides a summary of the system modules for which messages are documented in this reference guide; the system modules are listed alphabetically by name. Table 1-4 System Module Descriptions System Description Module AUTH Authentication error messages indicate problems with the authentication module of the Fabric OS.
  • Page 70: Hamk

    System Module Descriptions Table 1-4 System Module Descriptions (Continued) System Description Module Fibre Channel router related traffic and activity on the fabric or backend fabric. FICU The FICON-CUP daemon handles communication with FICON on IBM FICON storage devices. Errors to this module are usually initiation errors or indications that FICON-CUP prerequisites have not been met, such as a license key, core PID, and secure mode on the fabric.
  • Page 71 System Module Descriptions Table 1-4 System Module Descriptions (Continued) System Description Module ICPD ICPD stands for iSCSI gateway daemon on CP. It manages iSCSI configurations such as CHAP, VT/LUN, DD/DDSet and portal configurations, and statistics such as iSCSI session/connection information. Moreover, ICPD distributes iSCSI configurations not only switch wide, but also fabric wide.
  • Page 72 System Module Descriptions Table 1-4 System Module Descriptions (Continued) System Description Module LSDB The link state database is a part of the FSPF protocol that maintains records on the status of port links. This database is used to route frames. MFIC MS-FICON messages relate to FICON installations.
  • Page 73 System Module Descriptions Table 1-4 System Module Descriptions (Continued) System Description Module The reliable commit service daemon generates log entries when it receives a request from the zoning, security, or management server for passing data messages to switches in the fabric.
  • Page 74 System Module Descriptions Table 1-4 System Module Descriptions (Continued) System Description Module TRCK The track change feature tracks the following events: • Turning on or off the track change feature • CONFIG_CHANGE • LOGIN • LOGOUT • FAILED_LOGIN If any of these events occurs, a message is sent to the system message log. Additionally, if the SNMP trap option is enabled, an SNMP trap is also sent.
  • Page 75 Section RASLog Messages This section provides the RASLog messages, including: • AUTH System Messages • BL System Messages • BLL System Messages • BM System Messages • CDR System Messages • CER System Messages • CONF System Messages • EM System Messages •...
  • Page 76 • IBPD System Messages • ICPD System Messages • IPS System Messages • ISCS System Messages • ISNS System Messages • KSWD System Messages • KTRC System Messages • LOG System Messages • LSDB System Messages • MFIC System Messages •...
  • Page 77 • WEBD System Messages • ZOLB System Messages • ZONE System Messages Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 78 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 79 Chapter AUTH System Messages AUTH-1001 Message <timestamp>, [AUTH-1001], <sequence-number>,, INFO, <system-name>, <Operation type> has been successfully done. Probable Indicates that the secret database operation has been updated using the secAuthSecret command. The Cause values for Operation type can be "set" or "remove". Recommended No action is required.
  • Page 80 AUTH-1004 Probable Indicates an authentication configuration value was set to the specified value. The data type is either Cause "authentication type" or "DH group type". Recommended No action is required. Action Severity INFO AUTH-1004 Message <timestamp>, [AUTH-1004], <sequence-number>,, ERROR, <system-name>, Failed to set <data type>...
  • Page 81 AUTH-1007 Probable Indicates an internal problem with the Secure Fabric OS. Cause Recommended Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and Action switchEnable commands. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
  • Page 82 AUTH-1011 Probable Indicates an internal problem with the Secure Fabric OS. Cause Recommended Reboot or power cycle the switch. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity ERROR AUTH-1011...
  • Page 83 AUTH-1013 AUTH-1013 Message <timestamp>, [AUTH-1013], <sequence-number>,, WARNING, <system- name>, Can not perform authentication request message: port <port number>, message code <message code> Probable Indicates that the system is running low on resources when receiving an authentication request. Cause 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 84 AUTH-1018 Recommended Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and Action switchEnable commands. If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity ERROR AUTH-1018...
  • Page 85 AUTH-1022 AUTH-1022 Message <timestamp>, [AUTH-1022], <sequence-number>,, ERROR, <system-name>, Failed to extract <data type> from <message> payload: port <port number>. Probable Indicates the authentication process failed to extract a particular value from the receiving payload. Cause 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 86 AUTH-1025 AUTH-1025 Message <timestamp>, [AUTH-1025], <sequence-number>,, ERROR, <system-name>, Failed to get <data type> during <authentication phase>: port <port number> Probable Indicates the authentication process failed to get the expected information during the specified Cause 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 87 AUTH-1029 Probable Indicates that the authentication process failed because the system is low on memory. Cause Data type is the payload or structure that failed to get memory. Operation phase specifies which operation of a particular authentication phase failed. Recommended Usually this problem is transient.
  • Page 88 AUTH-1031 If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity ERROR AUTH-1031 Message <timestamp>, [AUTH-1031], <sequence-number>,, ERROR, <system-name>, Failed to retrieve secret value: port <port number> Probable Indicates that the secret value was not set properly for the authenticated entity.
  • Page 89 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 Indicates that an entity was not configured in the SCC policy and tried to connect to the port. Cause Recommended Add the entity's WWN to the SCC policy and reinitialize authentication by using the portDisable and Action portEnable commands or the switchDisable and switchEnable commands.
  • Page 90 AUTH-1036 If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity ERROR AUTH-1036 Message <timestamp>, [AUTH-1036], <sequence-number>,, ERROR, <system-name>, Invalid state <state value> for <authentication phase>: port <port number>...
  • Page 91 AUTH-1038 AUTH-1038 Message <timestamp>, [AUTH-1038], <sequence-number>,, ERROR, <system-name>, Failed to retrieve certificate during <authentication phase>: port <port number> Probable Indicates that the PKI certificate is not installed properly. Cause Recommended Reinstall the PKI certificate, using the pkiCreate command. Action Reinitialize authentication using the portDisable and portEnable commands or the switchDisable and switchEnable commands.
  • Page 92 AUTH-1038 2-14 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 93 Chapter BL System Messages BL-1000 Message <timestamp>, [BL-1000], <sequence-number>,, INFO, <system-name>, Initializing Ports... Probable Indicates that the switch has started initializing the ports. Cause Recommended No action is required. Action Severity INFO BL-1001 Message <timestamp>, [BL-1001], <sequence-number>,, INFO, <system-name>, Port Initialization Completed. Probable Indicates that the switch has completed initializing the ports.
  • Page 94 BL-1003 Probable Indicates that the blade initiation failed because one or more of the internal ports was not online. The Cause blade is faulted. Recommended Make sure that the blade is seated correctly. If the blade is seated correctly, reboot or power cycle the Action blade.
  • Page 95 BL-1006 BL-1006 Message <timestamp>, [BL-1006], <sequence-number>,, INFO, <system-name>, Blade <slot number> NOT faulted. Peer blade <slot number> experienced abrupt failure. Probable Indicates that the errors (mostly synchronization errors) on this blade are harmless. Probably, the Cause standby CP blade connected to the active CP blade has experienced transitory problems. Recommended Verify that the standby CP is healthy.
  • Page 96 BL-1009 If the message persists, replace the blade. Severity CRITICAL BL-1009 Message <timestamp>, [BL-1009], <sequence-number>, FFDC, CRITICAL, <system- name>, Blade in slot <slot number> timed out initializing the chips. Probable Indicates that the blade has failed to initialize the ASIC chips. Cause Recommended Make sure that the blade is seated correctly.
  • Page 97 BL-1012 Probable Indicates that too many interrupts in the embedded port caused the specified chip to be disabled. The Cause probable cause is too many abnormal frames; the chip is disabled to prevent the CP from becoming too busy. Recommended Make sure to capture the console output during this process.
  • Page 98 BL-1014 Recommended Make sure to capture the console output during this process. Action Check for a faulty cable, SFP, or device attached to the specified port. On a bladed switch, run the slotPowerOff and slotPowerOn commands. On a nonbladed switch, reboot or power cycle the switch. If the message persists, replace the blade.
  • Page 99 BL-1016 On a bladed switch, run the slotPowerOff and slotPowerOn commands. On a nonbladed switch, reboot the switch. Run the systemVerification command to determine if there is a hardware error. If there is a hardware error, if the slotPowerOff or slotPowerOn fails on the bladed switch or if errors are encountered again: •...
  • Page 100 BL-1018 BL-1018 Message <timestamp>, [BL-1018], <sequence-number>,, INFO, <system-name>, Slot <slot number> Initialization Completed Probable Indicates that the slot has completed initializing the ports. Cause Recommended No action is required. Action Severity INFO BL-1019 Message <timestamp>, [BL-1019], <sequence-number>,, INFO, <system-name>, Slot <Slot number>, retry <Retry Number>, internal port retry initialization, <List of internal ports retrying initialization>...
  • Page 101 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 Indicates that the switch had internal ports not online and that the system is retrying to bring the ports Cause that failed back online.
  • Page 102 BL-1024 Recommended Reboot or power cycle the blade. Action If the message persists, replace the blade. Severity CRITICAL 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 Indicates that a recent firmware upgrade caused the blade's firmware to be upgraded and resulted in the Cause...
  • Page 103 BL-1027 Recommended Collect supportSave information, then reboot switch and run POST. If problem persists, replace switch. Action Severity CRITICAL BL-1027 Message <timestamp>, [BL-1027], <sequence-number>,, CRITICAL, <system- name>, Blade in slot <slot number> faulted, boot failed; status 0x<boot status> 0x<1250 0 boot status> 0x<1250 1 boot status>. Probable Indicates that the blade failed to boot properly.
  • Page 104 BL-1030 Recommended No action is required. Action Severity INFO BL-1030 Message <timestamp>, [BL-1030], <sequence-number>,, INFO, <system-name>, All GigE/FCIP ports on the switch will be reset as part of the firmware upgrade. Probable Indicates that a recent firmware upgrade caused the switch's internal processor firmware to be upgraded Cause and resulted in the cold upgrade.
  • Page 105 BL-1033 Probable Indicates that BE/BI ports have not come ONLINE within time limit. Cause Recommended Reboot or power cycle the blade. Run the systemVerification command to verify that the blade does Action not have hardware problems. If the message persists, replace the blade. Refer to the Fabric OS Command Reference for more information on the systemVerification command.
  • Page 106 BL-1035 BL-1035 Message <timestamp>, [BL-1035], <sequence-number>,, INFO, <system-name>, Slot <slot number> iSCSI port <iscsi port number> Initialization Completed Probable Indicates that the indicated slot has completed initializing specified iSCSI port. Cause Recommended No action is required. Action Severity INFO 3-14 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 107 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 Indicates that a blade regulation problem was reported on the specified slot number. The blade is Cause faulted.
  • Page 108 BLL-1000 • 21 = RAM parity error • 22 = BISR or RAMINIT error Recommended Make sure that the blade is seated correctly. Action If the blade is seated correctly, reboot or power cycle the blade. Run the systemVerification command to verify that the blade does not have hardware problems. Refer to the Fabric OS Command Reference for more information on this command.
  • Page 109 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 Indicates that the software running on the CP cannot communicate with the AP blade in the indicated Cause slot, in order to determine AP blade's firmware version. This can be due to one of the following: •...
  • Page 110 BM-1003 BM-1003 Message <timestamp>, [BM-1003], <sequence-number>,, WARNING, <system-name>, Failed to establish connection between CP and blade in slot <Slot number>. Faulting blade. Probable The CP could not establish a connection to the BP to communicate. Cause Recommended Reseat the blade. If the problem persists, power-cycle the blade using the slotPowerOff and Action slotPowerOn commands.
  • Page 111 BM-1006 Severity WARNING BM-1006 Message <timestamp>, [BM-1006], <sequence-number>,, INFO, <system-name>, Blade is not configured. Persistently disabling all ports for blade in slot <Slot number> Probable The policy of the specified blade is to persistently disable all ports the first time the blade is detected, so Cause either: •...
  • Page 112 BM-1009 Severity WARNING BM-1009 Message <timestamp>, [BM-1009], <sequence-number>,, WARNING, <system-name>, Firmwaredownload timed-out for application processor. Faulting switch. Probable FirmwareDownload of the application processor failed. Cause Recommended Power-cycle the switch. Action Severity WARNING BM-1054 Message <timestamp>, [BM-1054], <sequence-number>,, INFO, <system-name>, AP firmware <Blade firmware>...
  • Page 113 BM-1056 Severity WARNING BM-1056 Message <timestamp>, [BM-1056], <sequence-number>,, INFO, <system-name>, AP is not configured. Persistently disabling all ports on the switch. Probable The policy of the specified switch is to persistently disable all ports the first time the AP is detected, and Cause either the: •...
  • Page 114 BM-1058 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 115 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 Indicates a deteriorated SFP, an incompatible SFP pair, a faulty cable between peer ports, or the port Cause speed configuration does not match the capability of the SFP.
  • Page 116 CDR-1002 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 117 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 Indicates that the HA synchronization between the active and standby CPs is broken because there is Cause downlevel firmware loaded on the standby CP.
  • Page 118 CER-1001 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 119 Chapter CONF System Messages CONF-1000 Message <timestamp>, [CONF-1000], <sequence-number>, AUDIT, INFO, <system- name>, configDownload completed successfully <Info about the parameters and AD>. Probable Indicates that the configDownload operation was initiated and completed successfully. The message Cause string that follows is a description of the class of configuration parameters that were downloaded. If AD is enabled, the AD number is specified in the description.
  • Page 120 CONF-1020 CONF-1020 Message <timestamp>, [CONF-1021], <sequence-number>,, INFO, <system-name>, configDownload not permitted <AD Number if AD is configured on the system>. Probable There are many possible causes. Cause Recommended Check the error log for a possible cause. Please correct the error and download the configuration again. Action Severity INFO...
  • Page 121 Chapter EM System Messages EM-1001 Message <timestamp>, [EM-1001], <sequence-number>, FFDC, CRITICAL, <system- name>, <FRU ID> is over heating: Shutting down Probable Indicates that a field replaceable unit (FRU) is shutting down due to overheating. This is typically due to Cause a faulty fan but can also be caused by the switch environment.
  • Page 122 EM-1003 EM-1003 Message <timestamp>, [EM-1003], <sequence-number>, FFDC, CRITICAL, <system- name>, <FRU ID> has unknown hardware identifier: FRU faulted. Probable Indicates that a fan FRU header could not be read or is not valid. The FRU is faulted. Cause Recommended On SilkWorm 24000 and 48000, try reseating the specified FRU. Action Reboot or power cycle the switch.
  • Page 123 EM-1005 EM-1005 Message <timestamp>, [EM-1005], <sequence-number>, FFDC, CRITICAL, <system- name>, <FRU Id> has faulted. Sensor(s) above maximum limits Probable Indicates that a blade in the specified slot or the switch (for nonbladed switches) is being shut down for Cause environmental reasons; its temperature or voltage is out of range. Recommended Check the environment and make sure the room temperature is within the operational range of the Action...
  • Page 124 EM-1008 For the SilkWorm 200E, 3016, 3250, 3850, 4100, and 4900 replace the switch. Severity CRITICAL EM-1008 Message <timestamp>, [EM-1008], <sequence-number>, FFDC, CRITICAL, <system- name>, Unit in <FRU Id> faulted, incompatible with chassis option <chassis configuration option> Probable Indicates that a blade inserted in the specified slot is not compatible with the switch chassisConfig Cause option.
  • Page 125 EM-1011 Severity CRITICAL EM-1011 Message <timestamp>, [EM-1011], <sequence-number>, FFDC, CRITICAL, <system- name>, Received unexpected power down for <FRU Id>, but cannot determine if it has power Probable Indicates that the environmental monitor (EM) received an unexpected power-down notification from Cause the FRU specified;...
  • Page 126 EM-1014 Recommended If the fruInfoSet command was being run, try the command again; otherwise, the update is Action automatically reattempted. If it continues to fail, try reseating the FRU. If the message persists, replace the FRU. Severity ERROR EM-1014 Message <timestamp>, [EM-1014], <sequence-number>,, ERROR, <system-name>, Unable to read sensor on <FRU Id>...
  • Page 127 EM-1017 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 EM-1017 Message <timestamp>, [EM-1017], <sequence-number>,, WARNING, <system-name>, Uncommitted WWN change detected. Cold reboot required. Probable Indicates that a user did not commit a changed WWN value prior executing a reboot, power cycle, or Cause...
  • Page 128 EM-1028 Recommended Either change the chassisConfig option to 1 with the chassisConfig command, or upgrade the firmware Action on the standby to the version running on the active CP. Severity WARNING EM-1028 Message <timestamp>, [EM-1028], <sequence-number>, FFDC, CRITICAL, <system- name>, HIL Error: <function> failed to access history log for FRU: <FRU Id>...
  • Page 129 EM-1031 EM-1031 Message <timestamp>, [EM-1031], <sequence-number>,, ERROR, <system-name>, <FRU Id> ejector not closed Probable Indicates that the environmental monitor (EM) has found a switch blade that is inserted, but the ejector Cause switch is not closed. The blade in the specified slot is treated as not inserted. Recommended Close the ejector switch (raise the slider in most blades, or completely screw in the upper thumbscrew Action...
  • Page 130 EM-1035 Run the systemVerification command to verify that the switch does not have hardware problems. Refer to the Fabric OS Command Reference for more information on this command. If the message persists, replace the FRU. Severity ERROR EM-1035 Message <timestamp>, [EM-1035], <sequence-number>,, ERROR, <system-name>, 2 circuit paired Power Supplies are faulty, please check the <Switch side>...
  • Page 131 EM-1037 EM-1037 Message <timestamp>, [EM-1037], <sequence-number>,, INFO, <system-name>, <FRU Id> is no longer faulted. Probable Indicates that the specified Power Supply has been marked as no longer being faulty. Probably because Cause its AC power supply has been turned on. Recommended No action is required.
  • Page 132 EM-1043 Severity WARNING EM-1043 Message <timestamp>, [EM-1043], <sequence-number>,, WARNING, <system-name>, Can't power <FRU Id> <state (on or off)>. Probable Indicates that the specified FRU cannot be powered on or off. Cause Recommended The specified FRU is not responding to commands and should be replaced. Action Severity WARNING...
  • Page 133 EM-1046 Recommended The SilkWorm 24000 (CP2) requires only a single power supply for a fully populated chassis; however, Action you should always operate the system with at least two power supplies for redundancy. For the SilkWorm 48000 (CP4), when there are no intelligent (AP) port blades installed, two power supplies are sufficient for redundancy;...
  • Page 134 EM-1049 Recommended The EM-1029 error can be a transitory error; if the problem resolves, the EM-1048 message is Action displayed. Severity INFO EM-1049 Message <timestamp>, [EM-1049], <sequence-number>,, INFO, <system-name>, FRU <FRU Id> insertion detected. Probable Indicates that a FRU of the type and location specified by the FRU ID was detected as having been Cause inserted into the chassis.
  • Page 135 EM-1055 EM-1055 Message <timestamp>, [EM-1055], <sequence-number>,, WARNING, <system-name>, <FRU Id>: Port media incompatible. Reason: <Reason for incompatibility> Probable Indicates that an incompatible port media is detected. Cause The possible causes are: • The port media is not capable of running at the configured port speed. •...
  • Page 136 EM-1058 EM-1058 Message <timestamp>, [EM-1058], <sequence-number>,, WARNING, <system-name>, Switch gets reset:<Fault reason> Probable The switch is automatically reset due to known resetable transient errors, such as bloom parity. error. Cause Recommended No action is required if the switch does not reach the reset threshold for the switch/blade. If the reset Action threshold is reached on the switch/blade, the switch/blade will be faulted and should be replaced.
  • Page 137 EM-1061 EM-1061 Message <timestamp>, [EM-1061], <sequence-number>,, WARNING, <system-name>, Synchronization halted. Remove all blades of type <Blade Type Id> or upgrade your standby CP, then reboot or run haSyncStart. Probable A blade in the system is not supported by the release on the standby CP. Cause Recommended Please remove all blades of this type or upgrade your standby CP.
  • Page 138 EM-2003 Severity CRITICAL EM-2003 Message <timestamp>, [EM-2003], <sequence-number>,, ERROR, <system-name>, Slot <Slot Id> has failed the POST tests. FRU is being faulted. Probable Indicates that a FRU did not pass the Power On Self Tests. Please see the /tmp/post[1/2].slot#.log file Cause for more information on fault.
  • Page 139 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 The event could not be sent to the remote proxy because the remote proxy switch cannot be reached Cause through in-band.
  • Page 140 EVMD-1001 10-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 141 Chapter FABR System Messages FABR-1001 Message <timestamp>, [FABR-1001], <sequence-number>,, WARNING, <system- name>, port <port number>, <segmentation reason> Probable Indicates that the specified switch port is isolated because of a segmentation due to mismatched Cause 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 142 FABR-1003 FABR-1003 Message <timestamp>, [FABR-1003], <sequence-number>,, WARNING, <system- name>, port <port number>: ILS <command> bad size <payload size>, wanted <expected payload size> Probable Indicates that an internal link service (ILS) information unit of invalid size has been received. The Cause neighbor switch has sent an invalid sized payload.
  • Page 143 FABR-1005 FABR-1005 Message <timestamp>, [FABR-1005], <sequence-number>,, WARNING, <system- name>, <command sent>: port <port number>: status 0x<reason for failure> (<description of failure reason>) xid = 0x<exchange ID of command> Probable Indicates that the application failed to send an async command for the specified port. The message Cause provides additional details regarding the reason for the failure and the exchange ID of the command.
  • Page 144 FABR-1008 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-1008 Message <timestamp>, [FABR-1008], <sequence-number>,, WARNING, <system- name>, <error description> Probable Indicates that errors occurred during the request domain ID state; the information unit cannot be Cause allocated or sent.
  • Page 145 FABR-1011 Probable Indicates that the errors occurred while cleaning up the RDI (request domain ID). The error description Cause provides further details. This message is rare and usually indicates a problem with the Fabric OS. Recommended If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the Action supportSave command and contact your switch service provider.
  • Page 146 FABR-1014 Probable Indicates that there is not enough memory in the switch for the fabric module to allocate. This message Cause is rare and usually indicates a problem with the Fabric OS. Recommended The system will recover by failing over to the standby CP. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers;...
  • Page 147 FABR-1016 FABR-1016 Message <timestamp>, [FABR-1016], <sequence-number>,, WARNING, <system- name>, ficonMode is enabled. Probable Indicates that FICON mode is enabled on the switch through a user interface command. Cause Recommended No action is required. Action Severity WARNING FABR-1017 Message <timestamp>, [FABR-1017], <sequence-number>,, WARNING, <system- name>, ficonMode is disabled.
  • Page 148 FABR-1019 Severity WARNING FABR-1019 Message <timestamp>, [FABR-1019], <sequence-number>, FFDC, CRITICAL, <system-name>, Critical fabric size (<current domains>) exceeds supported configuration (<supported domains>) Probable Indicates that this switch is a value-line switch and has exceeded the limited fabric size: that is, a Cause specified limit to the number of domains.
  • Page 149 FABR-1022 Probable Indicates that this switch has a value-line license and has a limited number of domains. If more than the Cause specified number of domains are in the fabric, a counter is started to disable Web Tools. This grace period has expired and Web Tools has been disabled.
  • Page 150 FABR-1024 FABR-1024 Message <timestamp>, [FABR-1024], <sequence-number>,, INFO, <system-name>, Initializing fabric size limit timer <grace period> Probable Indicates that the fabric size has exceeded the limit set by your value-line switches. Value-line switches Cause have a limited fabric size: a specified limit to the number of domains. This value is defined by your specific value-line license key.
  • Page 151 FABR-1031 Probable Indicates that the domain ID has changed as specified. Cause Recommended No action is required. Action Severity INFO FABR-1031 Message <timestamp>, [FABR-1031], <sequence-number>, FFDC, WARNING, <system-name>, Maximum number of retries sending ILS from port <port number> exceeded. Probable Indicates that fabric exhausted the maximum number of retries sending ILSes to iswitchd on the logical Cause E-port.
  • Page 152 FABR-1031 11-12 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 153 Chapter FABS System Messages FABS-1001 Message <timestamp>, [FABS-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, <Function name> <Description of memory need> Probable Indicates that the system is low on memory and cannot allocate more memory for new operations. This Cause is usually an internal Fabric OS problem or file corruption. Description of memory need indicates how much memory was being requested.
  • Page 154 FABS-1005 Probable Indicates that an operation has been interrupted by a signal. This is usually an internal Fabric OS Cause problem or file corruption. Recommended Reboot or power cycle the switch. Action Severity WARNING FABS-1005 Message <timestamp>, [FABS-1005], <sequence-number>,, WARNING, <system- name>, <Function name and description of problem>...
  • Page 155 FABS-1007 If the message persists, run the firmwareDownload command to update the firmware. Severity WARNING FABS-1007 Message <timestamp>, [FABS-1007], <sequence-number>,, WARNING, <system- name>, <Function name>: Media state is invalid - status=<Status value> Probable Indicates that the Fabric OS has detected an invalid value in an object's status field. This is usually an Cause internal Fabric OS problem or file corruption.
  • Page 156 FABS-1010 FABS-1010 Message <timestamp>, [FABS-1010], <sequence-number>,, WARNING, <system- name>, <Function name>: Wrong media_event <Event number> Probable Indicates that the Fabric OS detected an unknown event type. This is usually an internal Fabric OS Cause problem or file corruption. Recommended Reboot or power cycle the switch. Action If the message persists, run the firmwareDownload command to update the firmware.
  • Page 157 FABS-1013 FABS-1013 Message <timestamp>, [FABS-1013], <sequence-number>,, ERROR, <system-name>, <Method name>[<Method tag number>]:Unknown blade type 0x<Blade type> Probable An unrecognized type of blade has been discovered in the system. Cause This may be caused by an incorrect FRU header, inability to read the FRU header, or the blade may not be supported by this platform or Fabric OS version.
  • Page 158 FABS-1015 Probable Indicates the specified FRU could not be enabled. This is usually an internal Fabric OS problem. Cause Recommended Try removing and reinserting the FRU. Action Reboot or power-cycle the CP or system. If the message persists, run the firmwareDownload command to update the firmware. Severity ERROR 12-6...
  • Page 159 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 The CP determined that the version of firmware running on the AP blade is not compatible with the Cause version of firmware running on the CP.
  • Page 160 FBC-1001 13-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 161 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 Indicates that the hardware is not responding to a command request; possibly because it is busy. Cause Recommended Retry the command.
  • Page 162 FCIP-1000 14-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 163 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 Indicates that the switch is low on memory and failed to allocate new memory for an information unit Cause (IU).
  • Page 164 FCMC-1001 15-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 165 Chapter FCPD System Messages FCPD-1001 Message <timestamp>, [FCPD-1001], <sequence-number>,, WARNING, <system- name>, Probing failed on <error string> Probable Indicates that an FCP switch probed devices on a loop port, and the probing failed on the either the Cause L_Port, AL_PA address, or the F_Port. For the AL_PA, the valid range is 00 through FF. The error sting can be either: •...
  • Page 166 FCPD-1003 FCPD-1003 Message <timestamp>, [FCPD-1003], <sequence-number>,, INFO, <system-name>, Probing failed on <error string> which is possibly a private device which is not supported in this port type Probable Private devices will not respond to the switch PLOGI during probing. Cause Recommended Refer to the switch vendor for a list of other port types that support private devices for inclusion into the Action...
  • Page 167 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 Indicates that the switch is low on memory and failed to allocate new memory for a Fibre Channel Cause driver instance.
  • Page 168 FCPH-1001 17-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 169 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 Indicates that a proxy device in the edge fabric has been imported at the specified port. Cause Recommended No action is required.
  • Page 170 FCR-1004 Recommended No action is required. Action Severity INFO FCR-1004 Message <timestamp>, [FCR-1004], <sequence-number>,, INFO, <system-name>, FC router physical device offline at port <port number>. Probable Indicates that a physical device connected to the specified port has gone offline. Cause Recommended Verify that the device was intended to be taken offline.
  • Page 171 FCR-1007 Severity INFO FCR-1007 Message <timestamp>, [FCR-1007], <sequence-number>,, INFO, <system-name>, FC router LSAN zone removed at port <port number>. Probable Indicates that an LSAN zone attached to the specified port was removed from the edge fabric. Cause Recommended No action is required. Action Severity INFO...
  • Page 172 FCR-1010 FCR-1010 Message <timestamp>, [FCR-1010], <sequence-number>,, INFO, <system-name>, FC router LSAN zone disabled at port <port number>. Probable Indicates that an LSAN zone is disabled in the edge fabric. Cause Recommended No action is required. Action Severity INFO FCR-1011 Message <timestamp>, [FCR-1011], <sequence-number>,, INFO, <system-name>, Remote LSAN zone updated in domain <domain ID>.
  • Page 173 FCR-1013 FCR-1013 Message <timestamp>, [FCR-1013], <sequence-number>,, INFO, <system-name>, Phantom FSPF database exchange completed on port <port number>. Probable Indicates that the specified EX port has completed FSPF database exchange. Cause Recommended No action is required. Action Severity INFO FCR-1015 Message <timestamp>, [FCR-1015], <sequence-number>,, INFO, <system-name>, New EX or VEX port added on port <port number>...
  • Page 174 FCR-1018 FCR-1018 Message <timestamp>, [FCR-1018], <sequence-number>,, ERROR, <system-name>, FC router proxy device entries exhausted on port <port number>. Probable Indicates that the number of proxy devices is greater than allowed by the port resource. Cause Recommended Remove excess LSAN zones or devices until the number of proxy devices exported is within the range Action allowed by the port resource.
  • Page 175 FCR-1021 Recommended Remove excess LSAN zones so that the number of LSAN zones created is within the range of the local Action database limitations. Severity WARNING FCR-1021 Message <timestamp>, [FCR-1021], <sequence-number>,, WARNING, <system- name>, Local LSAN device entries exhausted. Probable Indicates that the number of devices created through LSAN zones within the MetaSAN is greater than Cause the local LSAN zone database limitations.
  • Page 176 FCR-1024 Recommended You might need to limit the number of port WWNs required by limiting the remote edge fabric Action connectivity (which limits the number of translate domains). You can also limit the number of proxy devices for a translate domain (which limits the number of translate domain ports required) by limiting the devices specified in LSAN zones.
  • Page 177 FCR-1027 Recommended It is unlikely that WWN conflicts will occur as a result of pool rollover unless the switch is deployed in Action a very large MetaSAN environment with large number of LSAN devices and fabrics, or there are highly dynamic changes to EX port connectivity.
  • Page 178 FCR-1029 FCR-1029 Message <timestamp>, [FCR-1029], <sequence-number>,, INFO, <system-name>, Port WWN pool 95 percent allocated. Probable Indicates that the Port WWN pool has rolled over and WWN entries detected to not be in use are reused Cause as needed. Recommended It is unlikely that WWN conflicts will occur as a result of pool rollover unless the switch is deployed in Action a very large MetaSAN environment with large number of LSAN devices and fabrics, or there are highly dynamic changes to EX port connectivity.
  • Page 179 FCR-1032 FCR-1032 Message <timestamp>, [FCR-1032], <sequence-number>,, INFO, <system-name>, Edge fabric enabled security on port <port number> in fabric <fabric ID>. Probable Indicates that Secure mode was turned on in the edge fabric. Cause Recommended No action is required. Action Severity INFO FCR-1033 Message...
  • Page 180 FCR-1035 FCR-1035 Message <timestamp>, [FCR-1035], <sequence-number>,, INFO, <system-name>, LSAN zone device added in the backbone fabric. Probable Indicates that a new device was added to an LSAN zone in the backbone fabric. Cause Recommended No action is required. Action Severity INFO FCR-1036 Message...
  • Page 181 FCR-1038 FCR-1038 Message <timestamp>, [FCR-1038], <sequence-number>,, WARNING, <system- name>, Total zone entries exceeded local fabric limits by <overflow> entries, in zone: <zone name>, zone limit: <LSAN zone limit>. Probable Indicates that the number of cfg/zone/alias entries created in a local fabric is greater than the local Cause switch's zone database limitations.
  • Page 182 FCR-1041 FCR-1041 Message <timestamp>, [FCR-1041], <sequence-number>,, INFO, <system-name>, LSAN zone device removed in the backbone fabric. Probable Indicates that an LSAN zone device within the backbone fabric was removed. Cause Recommended No action is required. Action Severity INFO FCR-1042 Message <timestamp>, [FCR-1042], <sequence-number>,, INFO, <system-name>, LSAN zone removed in the backbone fabric.
  • Page 183 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 Indicates the specified credit type was not set. Cause Recommended Setting port credits failed. Run the portEnable command. Action If the problem persists try rebooting the switch. If the message persists, collect switch information using the supportShow command, and contact your switch service provider.
  • Page 184 FCR-1054 FCR-1054 Message <timestamp>, [FCR-1054], <sequence-number>,, WARNING, <system- name>, Port <port number> received ILS <command> of incorrect size (<actual payload size>); valid ILS size is <expected payload size>. Probable Indicates that an internal link service (ILS) IU of invalid size was received from the switch on the other Cause end of the link.
  • Page 185 FCR-1057 Recommended No action is required if backbone to edge routing is not needed. Otherwise replace the switch with one Action that supports backbone to edge routing. Severity INFO FCR-1057 Message <timestamp>, [FCR-1057], <sequence-number>,, ERROR, <system-name>, EX port(<port number>) incompatible long distance parameters on link.
  • Page 186 FCR-1060 Probable Indicates that the DH-CHAP authentication failed on the EX port. Cause Recommended Verify that the shared secrets on both sides of the link match. Action Disable and enable the ports using the portDisable then portEnable commands to restart authentication.
  • Page 187 FCR-1062 FCR-1062 Message <timestamp>, [FCR-1062], <sequence-number>,, INFO, <system-name>, Port <port number> disabled, system only supports <maximum ports> ports. Probable Indicates that the maximum number of supported ports was exceeded. To enable this port, disable any Cause other operational port then re-enable the port. Recommended No action is required.
  • Page 188 FCR-1065 FCR-1065 Message <timestamp>, [FCR-1065], <sequence-number>,, ERROR, <system-name>, Fabric on port <port number> was assigned two different fabric IDs. Probable Indicates that another port on the switch is connected to the same edge fabric with a different fabric ID Cause assignment.
  • Page 189 FCR-1068 FCR-1068 Message <timestamp>, [FCR-1068], <sequence-number>,, INFO, <system-name>, The FC Routing service is disabled. Probable Indicates that the FC Routing service is disabled. This is caused by fcrDisable, configDefault, or a Cause configDownload with the fcrState set to 2 (disabled). Note that the FC Routing service is disabled by the factory.
  • Page 190 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 Indicates that the port became an EX or VEX port. Cause Recommended No action is required. Action Severity INFO FCR-1072 Message <timestamp>, [FCR-1072], <sequence-number>,, INFO, <system-name>,...
  • Page 191 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 Indicates that one of the configuration management functions failed. The key variable is part of the Cause Fabric OS configuration database and is for support use only. The error variable is an internal error number.
  • Page 192 FICU-1003 FICU-1003 Message <timestamp>, [FICU-1003], <sequence-number>,, WARNING, <system- name>, <function name>: <message> FICON-CUP License Not Installed (<error>) Probable Indicates that the FICON-CUP license is not installed on the switch. Cause Recommended Run the licenseShow command to check the installed licenses on the switch. The switch cannot be Action managed using FICON-CUP commands until the FICON-CUP license is installed.
  • Page 193 FICU-1005 FICU-1005 Message <timestamp>, [FICU-1005], <sequence-number>,, ERROR, <system-name>, Failed to initialize <module> rc = <error> Probable Indicates that the initialization of a module within the FICON-CUP daemon failed. Cause Recommended Download a new firmware version using the firmwareDownload command. Refer to the Fabric OS Action Command Reference for more information on this command.
  • Page 194 FICU-1008 FICU-1008 Message <timestamp>, [FICU-1008], <sequence-number>,, WARNING, <system- name>, FMS mode has been enabled. Port(s):<port number(s)> have been disabled due to port address conflict. Probable Indicates that the specified port(s) were disabled when FICON Management Server mode (fmsMode) Cause was enabled. This is due to port address conflict or port address being reserved for CUP management port Recommended No action is required.
  • Page 195 Chapter FKLB System Messages FKLB-1001 Message <timestamp>, [FKLB-1001], <sequence-number>,, WARNING, <system- name>, exchange <xid> overlapped, pid=<pid> Probable Indicates that the FC kernel driver has timed out the exchange while the application is still active. When Cause the FC kernel driver reuses the exchange, the application will overlap. This happens on a timed-out exchange;...
  • Page 196 FKLB-1001 20-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 197 Chapter FLOD System Messages FLOD-1001 Message <timestamp>, [FLOD-1001], <sequence-number>, FFDC, WARNING, <system-name>, Unknown LSR type: port <port number>, type <LSR header type> Probable Indicates that the link state record (LSR) type is unknown. 1-Unicast and 3-Multicast are the only two Cause LSR header types.
  • Page 198 FLOD-1005 Probable Indicates that the LSU size exceeds what the system can support. Cause Recommended Reduce the number of switches in the fabric or reduce the number of redundant ISLs between two Action switches. Severity ERROR FLOD-1005 Message <timestamp>, [FLOD-1005], <sequence-number>,, WARNING, <system- name>, Invalid received domain ID: <domain number>...
  • Page 199 Chapter FSPF System Messages FSPF-1001 Message <timestamp>, [FSPF-1001], <sequence-number>,, ERROR, <system-name>, Input Port <port number> out of range Probable Indicates that the specified input port number is out of range; it does not exist on the switch. Cause Recommended No action is required. Action Severity ERROR...
  • Page 200 FSPF-1005 Probable Indicates that the specified remote domain ID is out of range. Cause Recommended No action is required; the frame is discarded. Action Severity ERROR FSPF-1005 Message <timestamp>, [FSPF-1005], <sequence-number>,, ERROR, <system-name>, Wrong Section Id <section number>, should be <section number>, input port = <port number>...
  • Page 201 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 Indicates that an application has dropped a high availability (HA) data update. Cause Recommended Run the haSyncStart command if this is a dual-CP system, or reboot the switch if it is a nonbladed Action system.
  • Page 202 FSS-1003 FSS-1003 Message <timestamp>, [FSS-1003], <sequence-number>,, WARNING, <system- name>, Component (<component name>) misused the update transaction (<transaction ID>) without marking the transaction beginning Probable Indicates that the FSS has dropped the update because an application has not set the transaction flag Cause correctly.
  • Page 203 FSS-1006 Recommended If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the Action supportSave command and contact your switch service provider. Severity WARNING FSS-1006 Message <timestamp>, [FSS-1006], <sequence-number>,, WARNING, <system- name>, No FSS message available Probable Indicates that data is not available on the FSS device.
  • Page 204 FSS-1007 23-4 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 205 Chapter FSSM System Messages FSSM-1002 Message <timestamp>, [FSSM-1002], <sequence-number>,, INFO, <system-name>, HA State is in sync Probable Indicates that the HA state for the active CP is in synchronization with the HA state of the standby CP. Cause If the standby CP is healthy, then a failover is nondisruptive. For more information on the haFailover command, refer to the Fabric OS Command Reference.
  • Page 206 FSSM-1004 FSSM-1004 Message <timestamp>, [FSSM-1004], <sequence-number>,, INFO, <system-name>, Incompatible software version in HA synchronization. Probable Indicates that the active CP and the standby CP in a dual CP system are running firmware that are Cause incompatible with each other. If the active CP fails, the failover will be disruptive. In a non-bladed system, this message is logged when the firmware upgrade/downgrade was invoked.
  • Page 207 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 Indicates that the internal temperature of the switch has changed. Cause Recommended No action is required. Respond to this message as is appropriate to the particular policy of the end-user Action installation.
  • Page 208 FW-1003 FW-1003 Message <timestamp>, [FW-1003], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the internal temperature of the switch has risen above the high boundary to a value that Cause might damage the switch.
  • Page 209 FW-1006 FW-1006 Message <timestamp>, [FW-1006], <sequence-number>,, WARNING, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the speed of the fan has fallen below the low boundary. Fan problems typically contribute Cause to temperature problems.
  • Page 210 FW-1009 FW-1009 Message <timestamp>, [FW-1009], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the state of the power supply has changed from faulty to functional, or from functional to Cause faulty.
  • Page 211 FW-1012 Severity INFO FW-1012 Message <timestamp>, [FW-1012], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the power supply counter changed from a value outside of the acceptable range to a value Cause within the acceptable range.
  • Page 212 FW-1035 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>. Probable Indicates that the temperature of the SFP has risen above the high boundary. Frequent fluctuations in Cause temperature might indicate a deteriorating SFP.
  • Page 213 FW-1038 Recommended Incoming laser fluctuations usually indicate a deteriorating SFP. If this message occurs repeatedly, Action replace the SFP. Severity INFO FW-1038 Message <timestamp>, [FW-1038], <sequence-number>,, WARNING, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the receive power value of the SFP has fallen below the low boundary.
  • Page 214 FW-1041 Probable Indicates that the receive power value of the SFP has changed from a value outside of the acceptable Cause range to a value within the acceptable range. The receive performance area measures the amount of incoming laser to help you determine if the SFP is in good working condition or not. If the counter often exceeds the threshold, the SFP is deteriorating.
  • Page 215 FW-1043 FW-1043 Message <timestamp>, [FW-1043], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the transmit power value of the SFP has risen above the high boundary. The transmit Cause performance area measures the amount of outgoing laser to help you determine if the SFP is in good working condition or not.
  • Page 216 FW-1046 Severity INFO FW-1046 Message <timestamp>, [FW-1046], <sequence-number>,, WARNING, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the value of the SFP voltage has fallen below the low boundary. Cause Recommended Verify that your optical components are clean and function properly.
  • Page 217 FW-1049 Severity INFO FW-1049 Message <timestamp>, [FW-1049], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the value of the SFP voltage has changed. Frequent voltage fluctuations are an indication Cause that the SFP is deteriorating.
  • Page 218 FW-1052 Severity WARNING FW-1052 Message <timestamp>, [FW-1052], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the value of the SFP voltage has changed from a value outside of the acceptable range to a Cause value within the acceptable range.
  • Page 219 FW-1115 Recommended No action is required. Respond to this message as is appropriate to the particular policy of the end-user Action installation. Severity INFO 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 Indicates that the number of times E_Ports have gone down has risen above the high boundary.
  • Page 220 FW-1118 Probable Indicates that the number of fabric reconfigures has changed. The following actions can cause a fabric Cause reconfiguration: • two switches with the same domain ID have connected to one another. • two fabrics have joined. • an E_Port has gone offline. •...
  • Page 221 FW-1120 • An E_Port has gone offline. • A principal link has segmented from the fabric. Recommended Verify that all ISL cables are properly connected at both ends. Verify that the SFP has not become faulty. Action An inexplicable fabric reconfiguration might be a transient error and might not require troubleshooting. Severity INFO FW-1120...
  • Page 222 FW-1122 FW-1122 Message <timestamp>, [FW-1122], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of domain ID changes has fallen below the low boundary. Domain ID changes Cause occur when there is a conflict of domain IDs in a single fabric and the principal switch has to assign another domain ID to the switch.
  • Page 223 FW-1125 Severity INFO FW-1125 Message <timestamp>, [FW-1125], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of segmentations has changed. Segmentation changes might occur due to: Cause • Zone conflicts. •...
  • Page 224 FW-1127 FW-1127 Message <timestamp>, [FW-1127], <sequence-number>,, INFO, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of segmentations has risen above the high boundary. Segmentation changes Cause might occur due to: •...
  • Page 225 FW-1129 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 Indicates that the number of zone changes has changed. Zone changes occur when there is a change to Cause the effective zone configuration.
  • Page 226 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 Indicates that the number of zone changes has changed from a value outside of the acceptable range to a Cause value within the acceptable range.
  • Page 227 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 Indicates that the number of fabric logins has risen above the high boundary. Fabric logins occur when a Cause port or device initializes with the fabric.
  • Page 228 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 Indicates that the number of SFP state changes has fallen below the low boundary. SFP state changes Cause occur when the SFP is inserted or removed.
  • Page 229 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 Indicates that the number of link failures that the port experiences has changed. Link loss errors occur Cause when a link experiences a loss of signal and fails.
  • Page 230 FW-1163 Probable Indicates that the number of link failures that the port experiences has risen above the high boundary. Cause Link loss errors occur when a link experiences a loss of signal and fails. Both physical and hardware problems can cause link loss errors. Link loss errors frequently occur due to a loss of synchronization. Check for concurrent loss of synchronization errors and, if applicable, troubleshoot them.
  • Page 231 FW-1165 FW-1165 Message <timestamp>, [FW-1165], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of synchronization losses that the port experiences has fallen below the low Cause boundary.
  • Page 232 FW-1168 Recommended No action is required. Respond to this message as is appropriate to the particular policy of the end-user Action installation. Severity INFO FW-1168 Message <timestamp>, [FW-1168], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of signal losses that the port experiences has changed.
  • Page 233 FW-1171 Recommended Check both ends of your cable connection. Verify that the cable is not faulty. Action Severity WARNING FW-1171 Message <timestamp>, [FW-1171], <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 Indicates that the number of signal losses that the port experiences has changed from a value outside of Cause...
  • Page 234 FW-1174 Probable Indicates that the number of protocol errors that the port experiences has fallen below the low boundary. Cause Occasional protocol errors occur due to software glitches. Persistent protocol errors occur due to hardware problems. A low number of protocol errors means that the switch is functioning normally. Recommended No action is required.
  • Page 235 FW-1176 FW-1176 Message <timestamp>, [FW-1176], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of invalid words that the port experiences has changed. Invalid words usually Cause indicate a hardware problem with an SFP or cable.
  • Page 236 FW-1179 FW-1179 Message <timestamp>, [FW-1179], <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 Indicates that the number of invalid words that the port experiences has changed from a value outside of Cause the acceptable range to a value within the acceptable range.
  • Page 237 FW-1182 FW-1182 Message <timestamp>, [FW-1182], <sequence-number>,, WARNING, <system-name>, <Port Name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of invalid CRCs that the port experiences has risen above the high boundary. Cause Recommended This error generally indicates an deteriorating fabric hardware.
  • Page 238 FW-1185 FW-1185 Message <timestamp>, [FW-1185], <sequence-number>,, INFO, <system-name>, <Port Name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the percentage of incoming traffic that the port experiences has fallen below the low Cause boundary.
  • Page 239 FW-1188 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> <Unit>. Probable Indicates that the percentage of outgoing traffic that the port experiences has changed. Cause Recommended No action is required. Respond to this message as is appropriate to the particular policy of the end-user Action installation.
  • Page 240 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 Indicates that the percentage of outgoing traffic that the port experiences has changed from a value Cause outside of the acceptable range to a value within the acceptable range.
  • Page 241 FW-1194 Recommended No action is required. Respond to this message as is appropriate to the particular policy of the end-user Action installation. Severity INFO FW-1194 Message <timestamp>, [FW-1194], <sequence-number>,, WARNING, <system-name>, <Port Name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of state changes that the port experiences has risen above the high boundary.
  • Page 242 FW-1217 Probable Indicates that the number of AL_PA CRC errors has changed. This indicates that errors have been Cause detected in the FC frame. Invalid CRC messages occur when the number of CRC errors in Fibre Channel frames for specific source ID (S_ID) and destination ID (D_ID) pairs change. These messages might also be caused by dirty equipment, temperature fluctuations, and aging equipment.
  • Page 243 FW-1219 Severity WARNING FW-1219 Message <timestamp>, [FW-1219], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of CRC errors has changed from a value outside of the acceptable range to a Cause value within the acceptable range.
  • Page 244 FW-1242 Probable Indicates that the number of EE CRC errors has fallen below the low boundary. Invalid CRC messages Cause occur when the number of CRC errors in Fibre Channel frames for specific source ID (S_ID) and destination ID (D_ID) pairs change. These messages might also be caused by dirty equipment, temperature fluctuations, and aging equipment.
  • Page 245 FW-1244 FW-1244 Message <timestamp>, [FW-1244], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of EE word frames that the switch receives has changed. Receive performance Cause messages appear due to the number of word frames that travel from the configured S_ID to the D_ID pair.
  • Page 246 FW-1247 Severity INFO FW-1247 Message <timestamp>, [FW-1247], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of EE word frames that the switch receives has changed from a value outside Cause of the acceptable range to a value within the acceptable range.
  • Page 247 FW-1250 Recommended No action is required. Respond to this message as is appropriate to the particular policy of the end-user Action installation. Severity INFO FW-1250 Message <timestamp>, [FW-1250], <sequence-number>,, INFO, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of EE word frames that the switch transmits has risen above the high Cause...
  • Page 248 FW-1273 Probable Indicates that the number of frame types or commands that the port receives has changed. The port has Cause received SCSI Read, SCSI Write, SCSI Read and Write, SCSI Traffic, or IP commands in a frame. Recommended No action is required. Respond to this message as is appropriate to the particular policy of the end-user Action installation.
  • Page 249 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 Indicates that the number of frame types or commands that the port receives has changed from a value Cause outside of the acceptable range to a value within the acceptable range.
  • Page 250 FW-1298 Recommended No action is required. Action Severity INFO 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 Indicates that the number of telnet violations has risen above the high boundary. Telnet violations Cause indicate that a telnet connection request has been received from an unauthorized IP address.
  • Page 251 FW-1300 FW-1300 Message <timestamp>, [FW-1300], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of HTTP violations has changed. HTTP violations indicate that a browser Cause connection request has been received from an unauthorized IP address. The HTTP_POLICY contains a list of TCP/IP addresses that are authorized to establish browser connections to the switches in the fabric.
  • Page 252 FW-1303 Probable Indicates that the number of HTTP violations has risen above the high boundary. HTTP violations Cause indicate that a browser connection request has been received from an unauthorized IP address. The HTTP_POLICY contains a list of TCP/IP addresses that are authorized to establish browser connections to the switches in the fabric.
  • Page 253 FW-1305 FW-1305 Message <timestamp>, [FW-1305], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of API violations has fallen below the low boundary. API violations indicate Cause that an API connection request has been received from an unauthorized IP address. The SNMP_POLICY contains a list of TCP/IP addresses that are authorized to establish API connections to switches in the fabric.
  • Page 254 FW-1308 Probable Indicates that the number of API violations has changed from a value outside of the acceptable range to Cause a value within the acceptable range. API violations indicate that an API connection request has been received from an unauthorized IP address. The SNMP_POLICY contains a list of TCP/IP addresses that are authorized to establish API connections to switches in the fabric.
  • Page 255 FW-1310 FW-1310 Message <timestamp>, [FW-1310], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of RSNMP violations has risen above the high boundary. RSNMP violations Cause indicate that an SNMP "get" operation request has been received from an unauthorized IP address. Recommended Run the errShow command to determine the IP address that sent the request.
  • Page 256 FW-1313 Severity INFO FW-1313 Message <timestamp>, [FW-1313], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of WSNMP violations has fallen below the low boundary. WSNMP violations Cause indicate that an SNMP "get/set"...
  • Page 257 FW-1316 Recommended No action is required. Action Severity INFO FW-1316 Message <timestamp>, [FW-1316], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of SES violations has changed. SES violations indicate that an SCSI Cause Enclosure Services (SES) request has been received from an unauthorized WWN.
  • Page 258 FW-1319 Probable Indicates that the number of SES violations has risen above the high boundary. SES violations indicate Cause that an SCSI Enclosure Services (SES) request has been received from an unauthorized WWN. The SES_POLICY contains a list of WWNs of device ports that are allowed to access the SES Server functionality.
  • Page 259 FW-1321 FW-1321 Message <timestamp>, [FW-1321], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of MS violations has fallen below the low boundary. MS violations indicate Cause that a Management Server (MS) access request has been received from an unauthorized WWN. The MS_POLICY contains a list of WWNs of device ports that are allowed to access the Management Server functionality.
  • Page 260 FW-1324 Recommended No action is required. Action Severity INFO FW-1324 Message <timestamp>, [FW-1324], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of serial violations has changed. Serial violations indicate that an Cause unauthorized serial port request has been received.
  • Page 261 FW-1327 Probable Indicates that the number of serial violations has risen above the high boundary. Serial violations Cause indicate that an unauthorized serial port request has been received. The SERIAL_POLICY contains a list of switch WWNs for which serial port access is enabled. Recommended Run the errShow command to determine the WWN of the device that sent the request.
  • Page 262 FW-1329 FW-1329 Message <timestamp>, [FW-1329], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of front panel violations has fallen below the low boundary. Front panel Cause violations indicate that an unauthorized front panel request has been received. The FRONTPANEL_POLICY contains a list of switch WWNs for which front panel access is enabled.
  • Page 263 FW-1332 Recommended No action is required. Action Severity INFO FW-1332 Message <timestamp>, [FW-1332], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of SCC violations has changed. SCC violations indicate that an unauthorized Cause switch tried to join the fabric.
  • Page 264 FW-1335 Probable Indicates that the number of SCC violations has risen above the high boundary. SCC violations indicate Cause that an unauthorized switch tried to join the fabric. The SCC_POLICY contains a list of switches by WWN that are allowed to be members of a fabric. Recommended Run the errShow command to determine the WWN of the device that sent the request.
  • Page 265 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 Indicates that the number of DCC violations has fallen below the low boundary. DCC violations Cause indicate that an unauthorized device tried to join the fabric. The DCC_POLICY allows for the specification of rules for binding device ports (typically HBA ports) to specific switch ports.
  • Page 266 FW-1340 Probable Indicates that the number of DCC violations has changed from a value outside of the acceptable range Cause to a value within the acceptable range. DCC violations indicate that an unauthorized device tried to join the fabric. The DCC_POLICY allows for the specification of rules for binding device ports (typically HBA ports) to specific switch ports.
  • Page 267 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 Indicates that the number of login violations has risen above the high boundary. Login violations Cause indicate that a login failure has been detected. Recommended Run the errShow command to determine the IP location of the login attempt.
  • Page 268 FW-1345 Recommended Responses to security-class messages depend on user policies. Consult your security administrator for Action response strategies and policies. Severity INFO FW-1345 Message <timestamp>, [FW-1345], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of invalid timestamps has fallen below the low boundary.
  • Page 269 FW-1347 FW-1347 Message <timestamp>, [FW-1347], <sequence-number>,, INFO, <system-name>, <Label>, is between high and low boundaries(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of invalid timestamps has changed from a value outside of the acceptable Cause range to a value within the acceptable range.
  • Page 270 FW-1350 Probable Indicates that the number of invalid signatures has fallen below the low boundary. Invalid-signature Cause violations indicate that a packet with an invalid signature has been received from the primary FCS. When the primary fabric configuration server (FCS) downloads a new configuration to the other switches in the fabric, the packet is signed using the private key of the primary FCS.
  • Page 271 FW-1352 Severity INFO FW-1352 Message <timestamp>, [FW-1352], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of invalid certificates has changed. This violation indicates that a packet with Cause an invalid certificate has been received from the primary FCS.
  • Page 272 FW-1354 FW-1354 Message <timestamp>, [FW-1354], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of invalid certificates has risen above the high boundary. This violation Cause indicates that a packet with an invalid certificate has been received from the primary FCS. Before a new primary FCS switch sends any configuration data to any switch in the fabric, it first sends its certificate to all the switches in the fabric.
  • Page 273 FW-1357 Probable Indicates that the number of authentication failures has changed. Authentication failures can occur for Cause 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. The port where authentication fails is segmented. This counter keeps track of the number of authentication failures.
  • Page 274 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 Indicates that the number of authentication failures has changed from a value outside of the acceptable Cause range to a value within the acceptable range.
  • Page 275 FW-1362 Severity INFO FW-1362 Message <timestamp>, [FW-1362], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of SLAP faulty packets has risen above the high boundary. This counter keeps Cause track of the number of unexpected SLAP packets and SLAP packets with faulty transmission IDs.
  • Page 276 FW-1365 Severity INFO FW-1365 Message <timestamp>, [FW-1365], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of time service out-of-sync violations has fallen below the low boundary. Cause Recommended No action is required.
  • Page 277 FW-1368 Severity INFO FW-1368 Message <timestamp>, [FW-1368], <sequence-number>,, INFO, <system-name>, <Label>, value has changed(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of no-FCS violations has changed. This counter records how often the switch Cause loses contact with the primary FCS switch.
  • Page 278 FW-1371 Probable Indicates that the number of no-FCS violations has risen above the high boundary. This counter records Cause how often the switch loses contact with the primary FCS switch. When the primary FCS switch in the fabric sends its certificate to a switch, the receiving switch saves the WWN of that primary FCS switch. If a secure switch finds that there are no FCSs in the fabric, but it still has the WWN of the last primary FCS switch, it increments this counter and resets the WWN of the primary FCS to all zeroes.
  • Page 279 FW-1373 FW-1373 Message <timestamp>, [FW-1373], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of incompatible security database violations has fallen below the low Cause boundary. This violation indicates the number of secure switches with different version stamps have been detected.
  • Page 280 FW-1376 Probable Indicates that the number of incompatible security database violations has changed from a value outside Cause of the acceptable range to a value within the acceptable range. This violation indicates the number of secure switches with different version stamps have been detected. When a switch is in secure mode, it connects only to another switch that is in secure mode and has a compatible security database.
  • Page 281 FW-1378 FW-1378 Message <timestamp>, [FW-1378], <sequence-number>,, WARNING, <system-name>, <Label>, is above high boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the number of illegal commands has risen above the high boundary. This counter tracks Cause how many times commands allowed only on the primary FCS switch have been executed on a non- primary FCS switch.
  • Page 282 FW-1401 Recommended No action is required. Respond to this message as is appropriate to the particular policy of the end-user Action installation. Severity INFO FW-1401 Message <timestamp>, [FW-1401], <sequence-number>,, INFO, <system-name>, <Label>, is below low boundary(High=<High value>, Low=<Low value>). Current value is <Value> <Unit>. Probable Indicates that the flash usage percentage has fallen below the low boundary.
  • Page 283 FW-1424 Probable Indicates that the flash usage percentage has changed from a value outside of the acceptable range to a Cause value within the acceptable range. Flash increases and decreases slightly with normal operation of the switch. Excessive permanent increases can lead to future problems. Recommended No action is required.
  • Page 284 FW-1427 Probable Indicates that the switch status is not in a healthy state. This occurred because the number of faulty or Cause missing power supplies is greater than or equal to the policy set by the switchStatusPolicySet command. Recommended Replace the faulty or missing power supply. Action Severity WARNING...
  • Page 285 FW-1430 Probable Indicates that the switch status is not in a healthy state. This occurred because the power supplies are not Cause in the correct slots for redundancy. Recommended Rearrange the power supplies so that one is in an odd slot and other in an even slot to make them Action redundant.
  • Page 286 FW-1433 Recommended Replace the faulty WWN card. Action Severity WARNING FW-1433 Message <timestamp>, [FW-1433], <sequence-number>,, WARNING, <system-name>, Switch status change contributing factor CP: CP non-redundant. Probable Indicates that the switch status is not in a healthy state. This occurred because the number of faulty CPs Cause is greater than or equal to the policy set by the switchStatusPolicySet command.
  • Page 287 FW-1435 FW-1435 Message <timestamp>, [FW-1435], <sequence-number>,, WARNING, <system-name>, Switch status change contributing factor Flash: usage out of range. Probable Indicates that the switch status is not in a healthy state. This occurred because the flash usage is out of Cause range.
  • Page 288 FW-1438 Severity WARNING FW-1438 Message <timestamp>, [FW-1438], <sequence-number>,, WARNING, <system-name>, Switch status change contributing factor Missing SFPs: <Num of missing SFPs> missing SFPs. Probable Indicates that the switch status is not in a healthy state. This occurred because the number of missing Cause SFPs is greater than or equal to the policy set by the switchStatusPolicySet command.
  • Page 289 FW-1441 FW-1441 Message <timestamp>, [FW-1441], <sequence-number>,, INFO, <system-name>, <FRU label> state has changed to <FRU state>. Probable Indicates that specified FRU's state has changed to "inserted". This means that a FRU is inserted but not Cause powered on. Recommended No action is required. Verify that the event was planned. Action Severity INFO...
  • Page 290 FW-1444 FW-1444 Message <timestamp>, [FW-1444], <sequence-number>,, WARNING, <system-name>, <FRU label> state has changed to <FRU state>. Probable Indicates that the specified FRU's state has changed to "faulty". Cause Recommended Replace the FRU. Action Severity WARNING 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.
  • Page 291 FW-1500 Recommended To maintain full (2X) redundancy and proper monitoring by Fabric Watch, 4 active power supplies Action should be supplied and the default values associated with the presence of an AP blade should be entered with switchstatuspolicyset. Severity WARNING FW-1500 Message <timestamp>, [FW-1500], <sequence-number>,, WARNING, <system-name>,...
  • Page 292 FW-1501 25-86 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 293 Chapter HAM System Messages HAM-1001 Message <timestamp>, [HAM-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, Standby CP is not Healthy, device <device name> status BAD, Severity = <Log="YES" Class="NONE" Severity> Probable Indicates that a standby CP device error is reported by the high-availability manager (HAM) Health Cause Monitor, with a specific device and Log="YES"...
  • Page 294 HAM-1004 HAM-1004 Message <timestamp>, [HAM-1004], <sequence-number>,, INFO, <system-name>, Processor rebooted - <Reboot Reason> Probable This message records switch processor reboot reasons that were initiated by the user or the switch Cause errors. The switch reboots can be initiated by the firmwareDownload, fastBoot, haFailover, and reboot commands.
  • Page 295 Chapter HAMK System Messages HAMK-1001 Message <timestamp>, [HAMK-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, Warm Recovery Failed Probable The switch failed in the warm recovery. Cause Recommended This message triggers a switch reboot automatically and attempts a cold recovery. Contact your switch Action service provider with the supportSave and haDump information.
  • Page 296 HAMK-1003 HAMK-1003 Message <timestamp>, [HAMK-1003], <sequence-number>,, INFO, <system-name>, Heartbeat up Probable Indicates that the active CP blade detects the standby CP blade. This message indicates that the standby Cause CP blade is available to take over in case a failure happens on the active CP blade. This message is typically seen when the standby CP blade reboots.
  • Page 297 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 Indicates that the blade voltage is above the threshold. Cause Recommended Replace the faulty blade or switch (for nonbladed switches). Action Severity ERROR...
  • Page 298 HIL-1103 HIL-1103 Message <timestamp>, [HIL-1103], <sequence-number>,, ERROR, <system-name>, Blower <blower number> faulted, <nominal voltage> (<measured voltage>) is above threshold. Probable Indicates that the fan voltage is above threshold. Cause Recommended Run the psShow command to verify the power supply status. Action Try to reseat the faulty fan FRU and power supply FRU to verify that they are seated properly.
  • Page 299 HIL-1106 For the SilkWorm 3900, replace the motherboard FRU. For the SilkWorm 4100, if the 12 volt level is faulty, replace one or both power supplies; if any other voltage is faulty, replace the entire switch. Severity ERROR HIL-1106 Message <timestamp>, [HIL-1106], <sequence-number>,, ERROR, <system-name>, Switch error, <nominal voltage>...
  • Page 300 HIL-1108 HIL-1108 Message <timestamp>, [HIL-1108], <sequence-number>, FFDC, CRITICAL, <system-name>, Switch faulted, <nominal voltage> (<measured voltage>) below threshold. System preparing for reset. Probable Indicates that the switch voltage is below threshold. This message is specific to nonbladed switches and Cause is not applicable to the SilkWorm 12000, 24000, or 48000. Recommended For the SilkWorm 200E, 3250 and 3850, the entire switch must be replaced, because these switches do Action...
  • Page 301 HIL-1202 HIL-1202 Message <timestamp>, [HIL-1202], <sequence-number>,, ERROR, <system-name>, Blower <blower number> faulted, speed (<measured speed> RPM) below threshold. Probable Indicates that the specified fan speed (in RPM) has fallen below the minimum threshold. Cause Recommended Replace the fan FRU. Action Severity ERROR HIL-1203...
  • Page 302 HIL-1206 Recommended For the SilkWorm 3900 replace the fan FRU. Action For the SilkWorm 3016, 3250 and 3850, the entire switch must be replaced, because these switches do not have FRUs. Severity ERROR HIL-1206 Message <timestamp>, [HIL-1206], <sequence-number>,, ERROR, <system-name>, Fan <fan number>...
  • Page 303 HIL-1208 HIL-1208 Message <timestamp>, [HIL-1208], <sequence-number>,, INFO, <system-name>, Fan <fan number> is not faulty. Probable Indicates that the fan is not faulty. Cause Recommended This can only occur on switches with non-removable fans. It follows a previous indication of faultiness. Action If the fan continues to generate this message, it indicates oscillation between faulty and non-faulty behavior.
  • Page 304 HIL-1303 HIL-1303 Message <timestamp>, [HIL-1303], <sequence-number>,, ERROR, <system-name>, One fan failed. Replace failed fan FRU immediately. Probable Indicates that a fan FRU has failed. This message is often preceded by a low fan speed message. Cause Recommended Replace the faulty fan FRU immediately. Action Severity ERROR...
  • Page 305 HIL-1306 HIL-1306 Message <timestamp>, [HIL-1306], <sequence-number>,, ERROR, <system-name>, Three fans failed. Replace failed fan FRUs immediately. Probable Indicates that three fan FRUs have failed. This message is often preceded by a low fan speed message. Cause Recommended Replace the faulty fan FRUs immediately. Action Severity ERROR...
  • Page 306 HIL-1309 HIL-1309 Message <timestamp>, [HIL-1309], <sequence-number>,, ERROR, <system-name>, <count> fan FRU(s) failed. Replace failed fan FRU(s) immediately. Probable Indicates that multiple fans have failed. This message is often preceded by a low fan speed message. Cause Recommended Replace the faulty fan FRUs immediately. Action Severity ERROR...
  • Page 307 HIL-1401 HIL-1401 Message <timestamp>, [HIL-1401], <sequence-number>,, WARNING, <system- name>, One fan FRU missing. Install fan FRU immediately. Probable Indicates that one fan FRU has been removed. Cause Recommended Install the missing fan FRU. Action Severity WARNING HIL-1402 Message <timestamp>, [HIL-1402], <sequence-number>,, WARNING, <system- name>, Two fan FRUs missing.
  • Page 308 HIL-1404 HIL-1404 Message <timestamp>, [HIL-1404], <sequence-number>,, WARNING, <system- name>, <count> fan FRU(s) missing. Install fan FRU(s) immediately. Probable Indicates that one or more fan FRUs have been removed. Cause 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...
  • Page 309 HIL-1503 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 blade. Severity CRITICAL HIL-1503...
  • Page 310 HIL-1505 HIL-1505 Message <timestamp>, [HIL-1505], <sequence-number>,, WARNING, <system- name>, High temperature (<measured temperature> C) exceeds environmental specifications. Probable Indicates that temperatures in the system have risen above the warning threshold. Cause Recommended Run the fanShow command to verify all the fans are working properly. Action Make sure that the area is well ventilated and that the room temperature is within operational range of your switch.
  • Page 311 HIL-1508 Recommended In order 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. Make sure that the area is well ventilated and that the room temperature is within operational range of your switch.
  • Page 312 HIL-1510 HIL-1510 Message <timestamp>, [HIL-1510], <sequence-number>,, WARNING, <system- name>, Current temperature (<measured temperature> C) is below shutdown threshold. System shutdown cancelled. Probable Indicates that temperatures in the system have dropped below the critical threshold, so that the system Cause can continue operation. Recommended To help prevent future problems, make sure that all the fans are working properly.
  • Page 313 HIL-1602 Run the tempShow command to verify temperature values. If any sensor is too high, monitor the switch. Try rebooting or power cycling the switch. Severity CRITICAL Fabric OS Message Reference 28-17 Publication Number: 53-1000242-01...
  • Page 314 HIL-1602 28-18 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 315 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 Indicates that the HLO message was incompatible with the value specified in the FSPF protocol. The Cause Brocade switch will not accept FSPF frames from the remote switch.
  • Page 316 HLO-1003 HLO-1003 Message <timestamp>, [HLO-1003], <sequence-number>,, ERROR, <system-name>, Invalid Hello received from port <port number>, Domain = <domain ID>, Remote Port = <remote port ID> Probable Indicates that the HLO message received was invalid and the frame was dropped. The Brocade switch Cause will not accept FSPF frames from the remote switch.
  • Page 317 Chapter HMON System Messages HMON-1001 Message <timestamp>, [HMON-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, <Failure description> Probable Indicates that there was a problem reading an essential file containing configuration information from Cause 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 318 HMON-1001 30-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 319 Chapter HTTP System Messages HTTP-1001 Message <timestamp>, [HTTP-1001], <sequence-number>,, INFO, <system-name>, Switch PIDformat has changed to <current PID format>. Probable Indicates that the PID format was changed by the administrator. Cause Recommended No action is required. For more information on PID, format refer to the Fabric OS Administrator’s Action Guide.
  • Page 320 HTTP-1003 Probable Indicates an error in completing the zoning transaction. Cause Recommended Verify that 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 31-2...
  • Page 321 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 Indicates that the initiator name length exceeds the supported limit of characters. Cause Recommended Change the initiator name, keeping the number of characters within the supported limit.
  • Page 322 IBPD-1003 IBPD-1003 Message <timestamp>, [IBPD-1003], <sequence-number>,, WARNING, <system- name>, iSCSI login sessions exceed the maximum limit at slot <Slot number> port ge<Port number> Probable Indicates that the iSCSI login sessions exceed the supported limit per port. Cause Recommended Use another port to login. Action Severity WARNING...
  • Page 323 Chapter ICPD System Messages ICPD-1001 Message <timestamp>, [ICPD-1001], <sequence-number>,, ERROR, <system-name>, Failed to allocate memory: (<function name>). Probable Indicates that the specified function failed to allocate memory. Cause Recommended Check memory usage on the switch using the memShow command. Action Reboot or power cycle the switch.
  • Page 324 ICPD-1004 Recommended No action is required. Action Severity INFO ICPD-1004 Message <timestamp>, [ICPD-1004], <sequence-number>,, WARNING, <system- name>, iSNS Client service is detected on multiple switches in fabric. Probable Indicates that iSNS Client service is enabled on multiple switches in fabric. Cause Recommended Enable the iSNS Client service on a single switch in the fabric using the fosConfig command.
  • Page 325 ICPD-1007 Recommended No action is required. Action Severity INFO ICPD-1007 Message <timestamp>, [ICPD-1007], <sequence-number>,, INFO, <system-name>, iSNSC service is <status> on the switch. Probable Indicates that the iSNSC service is enabled or disabled on the switch. Cause Recommended No action is required. Action Severity INFO...
  • Page 326 ICPD-1008 33-4 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 327 Chapter IPS System Messages IPS-1001 Message <timestamp>, [IPS-1001], <sequence-number>,, WARNING, <system- name>, <message> FCIP License Not Installed (<error>) Probable Indicates that the FCIP license is not installed on the switch. Cause Recommended Run the licenseShow command to check the installed licenses on the switch. Contact your switch Action supplier for a FCIP license.
  • Page 328 IPS-1004 Probable Indicates that memory resources are low. This might be a transient problem. Cause Recommended If the message persists, check the memory usage on the switch, using the memShow 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 329 IPS-1006 Probable Indicates that tunnel setup failed due to a configuration mismatch between the two ends. Reasons for Cause such a mismatch could be the Compression, SACK, FastWrite, and TapePipelining setting. Recommended Change the tunnel configuration on one side of the tunnel to match that of the other side to setup tunnel. Action Severity WARNING...
  • Page 330 IPS-1006 34-4 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 331 Chapter ISCS System Messages ISCS-1000 Message <timestamp>, [ISCS-1000], <sequence-number>,, ERROR, <system-name>, Slot <slot number> Port GE<port number> crashed unexpectedly. Probable Indicates that specified port has crashed. Cause Recommended No action is required; the port will restart automatically. Action Severity ERROR Fabric OS Message Reference 35-1 Publication Number: 53-1000242-01...
  • Page 332 ISCS-1000 35-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 333 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>/<New config port number> (current <Current iSNS server IP address> <Current slot number>/<Current port number>). Probable Indicates that the user has issued the isnsCCfg command.
  • Page 334 ISNS-1003 ISNS-1003 Message <timestamp>, [ISNS-1003], <sequence-number>,, INFO, <system-name>, Peering with external iSNS server is disabled. Probable Indicates that the IP address of iSNS server is set to zero, so peering is disabled. Cause Recommended If you want to enable the iSNS server to a different value, use the isnscCfg command; otherwise, no Action action is required.
  • Page 335 ISNS-1006 ISNS-1006 Message <timestamp>, [ISNS-1006], <sequence-number>,, INFO, <system-name>, Start re-register with external iSNS server <iSNS server IP address> slot/port <Slot number>/<Port number>. Probable Indicates that the re-register with the specified external iSNS server has started. Cause Recommended No action is required. Action Severity INFO...
  • Page 336 ISNS-1010 ISNS-1010 Message <timestamp>, [ISNS-1010], <sequence-number>,, WARNING, <system- name>, Slot/port <Slot>/<Port> is out of range. Probable Indicates that the slot or port is out of range. Cause Recommended Retry with a valid slot/port. Refer to the appropriate hardware reference manual for valid slot and port Action ranges.
  • Page 337 Chapter KSWD System Messages KSWD-1003 Message <timestamp>, [KSWD-1003], <sequence-number>, FFDC, WARNING, <system-name>, kSWD: <Warning message> Probable Indicates a warning state within the system. Cause A critical application error was reported in the watchdog subsystem. Refer to the string at the end of the error message for specific information.
  • Page 338 KSWD-1003 37-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 339 Chapter KTRC System Messages KTRC-1001 Message <timestamp>, [KTRC-1001], <sequence-number>,, WARNING, <system- name>, Dump memory size exceeds dump file size Probable Indicates that the dump memory size has exceeded the dump file size. Cause Recommended No action is required. Action Severity WARNING KTRC-1002 Message...
  • Page 340 KTRC-1004 Probable Indicates that the ATA dump driver is not initialized properly. Cause Recommended No action is required. Action Severity ERROR KTRC-1004 Message <timestamp>, [KTRC-1004], <sequence-number>,, ERROR, <system-name>, Cannot write to ATA dump device Probable Indicates that the write boundry in the ATA dump device has been exceeded. Cause Recommended No action is required.
  • Page 341 Chapter LOG System Messages LOG-1000 Message <timestamp>, [LOG-1000], <sequence-number>,, INFO, <system-name>, Previous message repeated <repeat count> time(s) Probable Indicates that the previous message repeated the specified number of times. Cause Recommended No action is required. Action Severity INFO LOG-1001 Message <timestamp>, [LOG-1001], <sequence-number>, FFDC, WARNING, <system- name>, A log message was dropped Probable...
  • Page 342 LOG-1002 LOG-1002 Message <timestamp>, [LOG-1002], <sequence-number>, FFDC, WARNING, <system- name>, A log message was dropped Probable Indicates that a message was not recorded by the error logging system. A trace dump file is created. The Cause message might still be visible through SNMP or other management tools. Recommended Run the reboot command for nonbladed switches or the haFailover command on bladed switches.
  • Page 343 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 Indicates that the specified link state database ID is out of the acceptable range. The valid link state ID Cause is the same as the valid domain ID, whose range is from 1 through 239.
  • Page 344 LSDB-1003 LSDB-1003 Message <timestamp>, [LSDB-1003], <sequence-number>, FFDC, CRITICAL, <system-name>, No database entry for local Link State Record, domain <local domain> Probable Indicates that there is no local link state record entry in the link state database. The switch should Cause always generate its own local entry when starting up.
  • Page 345 Chapter MFIC System Messages MFIC-1001 Message <timestamp>, [MFIC-1001], <sequence-number>,, ERROR, <system-name>, failure at sysmod_scn registry rc= <failure reason> Probable Indicates that the system is temporarily out of resources. Cause Recommended No action is required; this message is often transitory. Action If the message persists, run a switch reboot or an haFailover (if applicable).
  • Page 346 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 Indicates that one or more switches joined the fabric with a different insistent domain ID (IDID) mode Cause setting than the current effective IDID mode for the fabric.
  • Page 347 Chapter MPTH System Messages MPTH-1001 Message <timestamp>, [MPTH-1001], <sequence-number>, FFDC, ERROR, <system- name>, Null parent, lsId = <number> Probable Indicates that a null parent was reported. MPATH uses a tree structure in which the parent is used to Cause connect to the root of the tree. Recommended No action is required.
  • Page 348 MPTH-1003 Recommended No action is required. Action Severity WARNING 42-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 349 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 Indicates that an unexpected message has been received in the specified message queue. The queue Cause name is always fspf_q.
  • Page 350 MQ-1004 43-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 351 Chapter MS System Messages MS-1001 Message <timestamp>, [MS-1001], <sequence-number>,, WARNING, <system-name>, MS Platform Segmented port=<port number>(<reason for segmentation> <domain>) Probable Indicates that the management server (MS) has segmented from another switch domain at the specified Cause port number due to errors or inconsistencies defined in the MS platform service. Recommended Reboot or power cycle the switch.
  • Page 352 MS-1003 Recommended The recommended actions are as follows: Action • <No Resp for GCAP from> No action is required. • <GCAP sup but not PL by> Set the flag for the MS Platform Service. • <GCAP Rejected (reason =BUSY) by> Run the firmwareDownload command to upgrade the firmware level on the switch to a level that supports RCS.
  • Page 353 MS-1005 Recommended This message is often transitory. Action The fabric might be reconfiguring, forming, or merging. Wait a few minutes and try the operation again. Run the fabricShow command or the secFabricShow command to verify that the number of domains matches the Management Server known domains.
  • Page 354 MS-1021 Probable MS failed while initializing the specified action. Cause The following actions might be displayed: • <while writing to ms_els_q> MS is unable to write a message to the MS Extended Link Service Queue. • <while inserting timer to timer list> MS is unable to add a timer to a resource.
  • Page 355 MS-1023 MS-1023 Message <timestamp>, [MS-1023], <sequence-number>,, INFO, <system-name>, Management Server Topology Discovery Service <Enabled or Disabled> Probable Indicates that Management Server Topology Discovery Service is being enabled or disabled. Cause Recommended No action is required. Action Severity INFO MS-1024 Message <timestamp>, [MS-1024], <sequence-number>,, INFO, <system-name>, Management Server Access Control List is Updated Probable...
  • Page 356 MS-1024 44-6 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 357 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 Indicates that a duplicate E_Port State Change Number was reported. The neighbor finite state machine Cause (NBFSM) states are as follows: •...
  • Page 358 NBFS-1003 • 4 - Database Wait • 5 - Full If this error occurs repeatedly, it means the protocol implementation between two connected switches has problems. Recommended Run the nbrStateShow command to check the neighbor state of the port listed in the message. If it is Action FULL, then this message can safely be ignored.
  • Page 359 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 Indicates that the response payload exceeds the maximum frame size that the remote switch can handle. Cause Recommended Run the firmwareDownload command to upgrade the remote switch with firmware v4.3 or higher, or...
  • Page 360 NS-1003 NS-1003 Message <timestamp>, [NS-1003], <sequence-number>,, INFO, <system-name>, Number of local devices <Current local device count>, exceeds the standby can support <Local device count that standby can support>, can't send update. Probable Indicates that the name server on the standby CP has lower supported capability than the active CP due Cause to different firmware versions running on the active and standby CPs.
  • Page 361 Chapter PDM System Messages PDM-1001 Message <timestamp>, [PDM-1001], <sequence-number>,, WARNING, <system- name>, Failed to parse the pdm config Probable Indicates that the PDM process could not parse the configuration file. This might be caused by a Cause missing configuration file during the installation. Recommended Run the firmwareDownload command to reinstall the firmware.
  • Page 362 PDM-1004 Probable Indicates that a syntax error occurred when trying to launch the PDM process. Cause Recommended Run the firmwareDownload command to reinstall the firmware. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
  • Page 363 PDM-1007 Probable Indicates that the configuration file sync.conf contains too many entries. Cause Recommended Run the firmwareDownload command to reinstall the firmware. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
  • Page 364 PDM-1010 Probable Indicates that the PDM system call to setCfg failed. Cause Recommended Run the firmwareDownload command to reinstall the firmware. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING PDM-1010...
  • Page 365 PDM-1013 Probable Indicates that the PDM process could not write data to the specified file name. Cause Recommended Run the firmwareDownload command to reinstall the firmware. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider.
  • Page 366 PDM-1019 Probable Indicates that a system call failed. Cause Recommended Run the firmwareDownload command to reinstall the firmware. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity CRITICAL PDM-1019...
  • Page 367 PDM-1021 Probable Indicates that a system call failed. Cause Recommended Run the firmwareDownload command to reinstall the firmware. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING Fabric OS Message Reference...
  • Page 368 PDM-1021 47-8 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 369 Chapter PDTR System Messages PDTR-1001 Message <timestamp>, [PDTR-1001], <sequence-number>,, INFO, <system-name>, < informational message > Probable Indicates that information has been written to the panic dump files. The watchdog register codes are as Cause follows: • 0x10000000 bit set means that the watch dog timer (WDT) forced a core reset. •...
  • Page 370 PDTR-1002 48-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 371 Chapter PLAT System Messages PLAT-1000 Message <timestamp>, [PLAT-1000], <sequence-number>, FFDC, CRITICAL, <system-name>, <Function name> <Error string> Probable Indicates that nonrecoverable PCI errors have been detected. Cause Recommended The system will be faulted and might automatically reboot. Action If the system does not reboot, then try issuing the reboot command from a command-line prompt. Run supportFtp (as needed) to set up automatic FTP transfers;...
  • Page 372 PLAT-1001 49-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 373 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 Indicates that the specified port is now disabled because the link on this port had multiple failures that Cause exceed an internally set threshold on the port.
  • Page 374 PORT-1005 PORT-1005 Message <timestamp>, [PORT-1005], <sequence-number>,, WARNING, <system- name>, Slot <slot number> port <port on slot> does not support configured L_port. Issue portCfgLport to clear configuration. Probable Indicates that the specified port is configured to be an L_port, but that port does not support L_port. If Cause an L_port is connected, then the port will be disabled because it does not support L_port.
  • Page 375 Chapter PS System Messages PS-1000 Message <timestamp>, [PS-1000], <sequence-number>, FFDC, CRITICAL, <system- name>, Failed to initialize Advanced Performance Monitoring. Probable Indicates that an unexpected software error has occurred in Advanced Performance Monitoring. The Cause Performance Monitor has failed to initialize. Recommended The CP should reboot (or fail over) automatically.
  • Page 376 PS-1003 Probable Indicates that an unexpected software error has occurred in Advanced Performance Monitoring. The Cause Performance Monitor tracing system has failed to initialize. Recommended Tracing will not be available for Advanced Performance Monitoring, but other functions should Action function normally. To retry activating tracing, reboot (or fail over) the CP. Severity INFO PS-1003...
  • Page 377 PS-1005 Recommended To resume counting, delete some end-to-end monitors sharing the same hardware resource pool. Action Severity WARNING Fabric OS Message Reference 51-3 Publication Number: 53-1000242-01...
  • Page 378 PS-1005 51-4 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 379 Chapter PSWP System Messages PSWP-1001 Message <timestamp>, [PSWP-1001], <sequence-number>,, INFO, <system-name>, Areas for port <wwn name corresponding to source port> and port <wwn name corresponding to destination port> are swapped. New area for port <wwn name corresponding to source port> is <wwn name corresponding to destination port>...
  • Page 380 PSWP-1003 PSWP-1003 Message <timestamp>, [PSWP-1003], <sequence-number>,, INFO, <system-name>, Port Swap feature disabled Probable Indicates that the portSwap feature has been disabled in the switch. Cause Recommended No action is required. Action Severity INFO 52-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 381 Chapter RAS System Messages RAS-1001 Message <timestamp>, [RAS-1001], <sequence-number>,, INFO, <system-name>, First failure data capture (FFDC) event occurred. Probable Indicates that a failure happened and the failure data was captured. Cause Recommended Run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command Action and contact your switch service provider.
  • Page 382 RAS-1004 Probable Indicates the current state of the audit message log. Cause Recommended No action is required. Action Severity WARNING RAS-1004 Message <timestamp>, [RAS-1004], <sequence-number>, FFDC, WARNING, <system- name>, Software 'verify' error detected. Probable Indicates a internal software error. Cause Recommended Run the supportSave command and contact your switch service provider.
  • Page 383 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 Indicates that the RCS feature has been disabled on the local switch because not all switches in the Cause fabric support RCS or the switch is in nonnative mode.
  • Page 384 RCS-1003 RCS-1003 Message <timestamp>, [RCS-1003], <sequence-number>,, ERROR, <system-name>, Failed to allocate memory: (<function name>) Probable Indicates that the specified RCS function failed to allocate memory. Cause Recommended This message is usually transitory. Wait a few minutes and retry the command. Action Check memory usage on the switch using the memShow command.
  • Page 385 RCS-1006 Recommended If the reject is in ACA phase, wait several minutes and then retry the operation from the sender switch. Action If the reject is in the SFC phase, check if the application license exists for the local domain and if the application data is compatible.
  • Page 386 RCS-1008 RCS-1008 Message <timestamp>, [RCS-1008], <sequence-number>,, ERROR, <system-name>, Domain <domain number> Lowest Max Zone DB size Probable Indicates that the specified domain has the lowest maximum Zone database size. Cause Recommended Reduce the zone database size. Action Severity ERROR 54-4 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 387 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 Indicates that an authentication error was reported. The specified client IP address has faulty Cause credentials.
  • Page 388 RPCD-1004 Probable Indicates that the SSL certificate file configured on the switch could not be accessed because root did Cause not have read-level access. Recommended Change the file system access level for the certificate file to have root read-level access. Action Severity WARNING...
  • Page 389 RPCD-1007 Recommended Change the file system access level for the private key file and make sure that root has read-level access. Action Severity WARNING RPCD-1007 Message <timestamp>, [RPCD-1007], <sequence-number>,, WARNING, <system- name>, Invalid private file. Secure RPCd is disabled. Probable Indicates that the private key file has been corrupted.
  • Page 390 RPCD-1007 55-4 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 391 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 Indicates that an error occurred in the RTWR. The message provides the name of the routine having the Cause error, and more specific error information.
  • Page 392 RTWR-1003 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 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>...
  • Page 393 Chapter SCN System Messages SCN-1001 Message <timestamp>, [SCN-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, SCN queue overflow for process <daemon name> Probable Indicates that an attempt to write an SCN (state change notification) message to a specific queue has Cause failed because the SCN queue for the specified daemon name is full. This might be caused by the daemon hanging or if the system is busy.
  • Page 394 SCN-1001 57-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 395 Chapter SEC System Messages SEC-1001 Message <timestamp>, [SEC-1001], <sequence-number>,, ERROR, <system-name>, RCS process fails: <reason code> Probable Indicates that the RCS (reliable commit service) process fails to complete. RCS is a reliable mechanism Cause to transfer data from one switch to other switches within the fabric. This mechanism guarantees that either all switches commit to the new database or none of them update to the new database.
  • Page 396 SEC-1003 Severity ERROR 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 Indicates that the specified domain number failed to download security data after the specified number Cause of attempts.
  • Page 397 SEC-1007 Recommended If the message is the result of a user command, retry the statistic command. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command and contact your switch service provider. Severity WARNING SEC-1007...
  • Page 398 SEC-1016 Recommended Check for unauthorized access to the switch through the telnet connection. Action Severity INFO 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 Indicates that a security violation was reported.
  • Page 399 SEC-1025 Severity INFO SEC-1025 Message <timestamp>, [SEC-1025], <sequence-number>,, ERROR, <system-name>, Invalid IP address (<IP address>) detected. Probable Indicates that a corruption occurred during the distribution of the security database. This can occur only Cause when the primary FCS distributes the security database to the other switches in the fabric, then local validation finds the error in the security database.
  • Page 400 SEC-1029 Recommended Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be Action in the ready state. If a switch is in the error state, the database might not be correctly updated for that specific switch.
  • Page 401 SEC-1032 Probable Indicates that the security database size is not supported by the standby CP. Cause Recommended Reduce the security database size by reducing the number of entries within each policy. Action Severity WARNING SEC-1032 Message <timestamp>, [SEC-1032], <sequence-number>,, ERROR, <system-name>, Empty FCS list is not allowed.
  • Page 402 SEC-1034 SEC-1034 Message <timestamp>, [SEC-1034], <sequence-number>,, ERROR, <system-name>, Invalid member <policy member>. Probable Indicates that the input list has an invalid member. Cause Recommended Verify the member names, and input the correct information. Action Severity ERROR SEC-1035 Message <timestamp>, [SEC-1035], <sequence-number>,, ERROR, <system-name>, Invalid device WWN <device WWN>.
  • Page 403 SEC-1037 SEC-1037 Message <timestamp>, [SEC-1037], <sequence-number>,, ERROR, <system-name>, Invalid WWN format <invalid WWN>. Probable Indicates that the WWN entered in the policy member list had an invalid format. Cause Recommended Run the command again using the standard WWN format, 16 hexadecimal digits grouped as eight colon Action separated pairs.
  • Page 404 SEC-1041 SEC-1041 Message <timestamp>, [SEC-1041], <sequence-number>,, ERROR, <system-name>, Invalid port member <port member> in portlist (<port list>). <Reason>. Probable Indicates that the port member is invalid for one of the following reasons: Cause • The value is not a number. •...
  • Page 405 SEC-1044 SEC-1044 Message <timestamp>, [SEC-1044], <sequence-number>,, ERROR, <system-name>, Duplicate member <member ID> in (<List>). Probable Indicates that the specified member is a duplicate in the input list. The list can be a policy list or a switch Cause member list. Recommended Do not specify any duplicates.
  • Page 406 SEC-1049 SEC-1049 Message <timestamp>, [SEC-1049], <sequence-number>,, ERROR, <system-name>, Invalid switch name <switch name>. Probable Indicates that there has been a corruption during the distribution of the security database. This can only Cause occur when the primary 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 407 SEC-1052 Severity ERROR SEC-1052 Message <timestamp>, [SEC-1052], <sequence-number>,, ERROR, <system-name>, Invalid input. Probable Indicates that there has been a corruption during the distribution of the security database. This can only Cause occur when the primary 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 408 SEC-1055 Recommended Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be Action in the ready state. If a switch is in the error state, the database might not be correctly updated for that specific switch.
  • Page 409 SEC-1059 Probable Indicates that there has been a corruption during the distribution of the security database. This can only Cause occur when the primary FCS is distributing the security database to the other switches in the fabric and local validation finds that there is an error in the security database. This is a rare occurrence. Recommended Run the secFabricShow command to verify that the fabric is still consistent.
  • Page 410 SEC-1064 Probable Indicates that either the type or domains specified are invalid. Cause Recommended Enter valid input. Action Severity ERROR SEC-1064 Message <timestamp>, [SEC-1064], <sequence-number>,, ERROR, <system-name>, Failed to sign message. Probable Indicates that the PKI objects on the switch are not in a valid state and the signature operation failed. Cause Recommended Run the pkiShow command to verify that all PKI objects are valid.
  • Page 411 SEC-1071 Recommended Run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command Action and contact your switch service provider. Severity ERROR SEC-1071 Message <timestamp>, [SEC-1071], <sequence-number>,, ERROR, <system-name>, No new security policy data to apply. Probable Indicates that no changes in the defined security policy database need to be activated at this time.
  • Page 412 SEC-1074 SEC-1074 Message <timestamp>, [SEC-1074], <sequence-number>,, ERROR, <system-name>, Cannot execute the command on this switch. Please check the secure mode and FCS status. Probable Indicates that a security command was run on a switch that is not allowed to run it either because it is in Cause non-secure mode or because it does not have required FCS privilege.
  • Page 413 SEC-1077 SEC-1077 Message <timestamp>, [SEC-1077], <sequence-number>,, ERROR, <system-name>, Failed to activate new policy set on all switches. Probable Indicates that the policy could not be activated. Possible reasons that the policy could not be activate Cause include not enough memory or a busy switch. Recommended Run the secFabricShow command to verify that all switches in the fabric are in the ready state.
  • Page 414 SEC-1080 SEC-1080 Message <timestamp>, [SEC-1080], <sequence-number>,, ERROR, <system-name>, Operation denied. Please, use secModeEnable command. Probable Indicates that there has been a corruption during the distribution of the security database. This can only Cause occur when the primary 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 415 SEC-1083 SEC-1083 Message <timestamp>, [SEC-1083], <sequence-number>,, ERROR, <system-name>, Name already exists. Probable Indicates that there has been a corruption during the distribution of the security database. This can only Cause occur when the primary 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 416 SEC-1086 SEC-1086 Message <timestamp>, [SEC-1086], <sequence-number>,, ERROR, <system-name>, The security database is too large to fit in flash. Probable Indicates that the security database has more data than the flash can accommodate. Cause Recommended Reduce the number of entries in some policies to decrease the security database size. Action Severity ERROR...
  • Page 417 SEC-1089 SEC-1089 Message <timestamp>, [SEC-1089], <sequence-number>,, ERROR, <system-name>, Policy name <policy name> was not found. Probable Indicates that the security policy name in the secPolicyAdd command does not exist. Cause Recommended Create the appropriate security policy first, then use its name in the secPolicyAdd command to add new Action members.
  • Page 418 SEC-1092 SEC-1092 Message <timestamp>, [SEC-1092], <sequence-number>,, ERROR, <system-name>, <Policy name> Name not found. Probable Indicates that there has been a corruption during the distribution of the security database. This can only Cause occur when the primary 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 419 SEC-1095 SEC-1095 Message <timestamp>, [SEC-1095], <sequence-number>,, ERROR, <system-name>, Deleting FCS policy is not allowed. Probable Indicates that there has been a corruption during the distribution of the security database. This can only Cause occur when the primary 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 420 SEC-1098 SEC-1098 Message <timestamp>, [SEC-1098], <sequence-number>,, ERROR, <system-name>, No <active or defined> FCS list. Probable Indicates that the specified policy could not be found. Cause Recommended Run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command Action and contact your switch service provider.
  • Page 421 SEC-1101 SEC-1101 Message <timestamp>, [SEC-1101], <sequence-number>,, ERROR, <system-name>, Failed to enable security on all switches. Please retry later. Probable Indicates that the security enable failed on the fabric because one or more switches in the fabric are Cause busy. Recommended Verify that the security event was planned.
  • Page 422 SEC-1105 SEC-1105 Message <timestamp>, [SEC-1105], <sequence-number>,, ERROR, <system-name>, Fail to disable secure mode on all switches. Probable Indicates that the switch failed to disable security in the fabric. This could happen if the switch cannot Cause get the required resources to complete the command, and sending to a remote domain fails or the remote domain returns an error.
  • Page 423 SEC-1108 SEC-1108 Message <timestamp>, [SEC-1108], <sequence-number>,, ERROR, <system-name>, Fail to reset stamp on all switches. Probable Indicates that a version reset operation failed either because the switch could not get all the required Cause resources to perform the operation or because it failed to send the message to all switches in the fabric. Recommended Verify that the security event was planned.
  • Page 424 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 Indicates that either a security policy download is attempted with an active policy that does not have the Cause FCS policy as the first policy or the FCS policy is not same as the current FCS policy on the switch.
  • Page 425 SEC-1117 SEC-1117 Message <timestamp>, [SEC-1117], <sequence-number>,, INFO, <system-name>, Fail to set <data>. Probable Indicates that the switch failed to save the data received by the primary FCS switch. This data can be an Cause FCS password, a non-FCS password, SNMP data, or multiple user authentication data. Recommended Run the secFabricShow command to verify that all switches in fabric are in the ready state.
  • Page 426 SEC-1121 SEC-1121 Message <timestamp>, [SEC-1121], <sequence-number>,, ERROR, <system-name>, Time is out of range when <text>. Probable Indicates that the time on the switch is not synchronized with the primary FCS, the data packet is Cause corrupted, or a replay attack is launched on the switch. Recommended Verify that the security event was planned.
  • Page 427 SEC-1124 SEC-1124 Message <timestamp>, [SEC-1124], <sequence-number>,, INFO, <system-name>, Secure Mode is off. Probable Indicates that a secure mode disable is attempted in a non-secure fabric. Cause Recommended No action is required. Action Severity INFO SEC-1126 Message <timestamp>, [SEC-1126], <sequence-number>,, INFO, <system-name>, Secure mode has been disabled.
  • Page 428 SEC-1135 SEC-1135 Message <timestamp>, [SEC-1135], <sequence-number>,, INFO, <system-name>, Secure fabric version stamp has been reset. Probable Indicates that the version stamp of the secure fabric is reset. Cause Recommended Verify that 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 429 SEC-1138 Recommended Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be Action in the ready state. If a switch is in the error state, the database might not be correctly updated for that switch.
  • Page 430 SEC-1145 Probable Indicates that the new polices are rejected due to the reason specified. Cause Recommended Use proper syntax when entering policy information. Action Severity INFO SEC-1145 Message <timestamp>, [SEC-1145], <sequence-number>,, INFO, <system-name>, A security admin event has occurred. This message is for information purpose only.
  • Page 431 SEC-1153 SEC-1153 Message <timestamp>, [SEC-1153], <sequence-number>,, INFO, <system-name>, Error in RCA: RCS is not supported Probable Indicates that RCS is not supported. Cause Recommended Run the rcsInfoShow command to view RCS capability on the fabric. RCS must be capable on all Action switches in the fabric to be enabled.
  • Page 432 SEC-1156 Recommended Reduce the size of the specified policy database. Action Severity INFO SEC-1156 Message <timestamp>, [SEC-1156], <sequence-number>,, INFO, <system-name>, Change failed: <Reason> <defined status> <active status>. Probable Indicates that the security daemon is busy. The status values can be either defined, active, or both. A Cause negative value means that a policy set was failed by the daemon.
  • Page 433 SEC-1159 Recommended Enter a valid name. Action Severity INFO SEC-1159 Message <timestamp>, [SEC-1159], <sequence-number>,, INFO, <system-name>, Non_Reachable domain <Domain ID>. Probable Indicates that there has been a corruption during the distribution of the security database. This can only Cause occur when the primary 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 434 SEC-1164 Severity ERROR SEC-1164 Message <timestamp>, [SEC-1164], <sequence-number>,, ERROR, <system-name>, Lockdown option cannot be applied on a non-FCS switch. Probable Indicates that the attempt to enable security is made on a switch that is not present in the FCS list. Cause Recommended Add the switch into the FCS policy list when using the lockdown option to enable security.
  • Page 435 SEC-1167 SEC-1167 Message <timestamp>, [SEC-1167], <sequence-number>,, ERROR, <system-name>, Another FCS failover is in process. Command terminated. Probable Indicates that because another failover is already in progress, this failover attempt cannot proceed. Cause Recommended Verify that the security event was planned. If the security event was planned, retry FCS failover after Action current failover has completed, if this switch should become primary FCS.
  • Page 436 SEC-1171 Severity INFO SEC-1171 Message <timestamp>, [SEC-1171], <sequence-number>,, ERROR, <system-name>, Disabled secure mode due to invalid security object. Probable Indicates that the switch is segmented, and secure mode is disabled on the switch because there was no Cause license present or no PKI objects. Recommended Run the pkiShow command to check if all PKI objects exist.
  • Page 437 SEC-1174 SEC-1174 Message <timestamp>, [SEC-1174], <sequence-number>,, ERROR, <system-name>, Failed to set <FCS or non-FCS> password. Probable Indicates that the FCS or non-FCS password could not be set. Cause Recommended Verify that all switches in the fabric are in time synchronization with the primary and that no external Action entity is trying to access the fabric.
  • Page 438 SEC-1180 SEC-1180 Message <timestamp>, [SEC-1180], <sequence-number>,, INFO, <system-name>, Added account <user name> with <role name> authorization. Probable Indicates that the specified new account has been created. Cause Recommended No action is required. Action Severity INFO SEC-1181 Message <timestamp>, [SEC-1181], <sequence-number>,, INFO, <system-name>, Deleted account <user name>...
  • Page 439 SEC-1183 SEC-1183 Message <timestamp>, [SEC-1183], <sequence-number>,, ERROR, <system-name>, Policy to binary conversion error: Port <port number> is out range. Probable Indicates that a security database conversion has failed because of an invalid value. Cause Recommended Retry the command with a valid value. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers;...
  • Page 440 SEC-1186 SEC-1186 Message <timestamp>, [SEC-1186], <sequence-number>,, INFO, <system-name>, <action> Radius Configuration. Probable Indicates that the RADIUS configuration was enabled or disabled as the primary AAA mechanism. Cause Recommended No action is required. Action Severity INFO SEC-1187 Message <timestamp>, [SEC-1187], <sequence-number>,, INFO, <system-name>, Security violation: Unauthorized switch <switch WWN>...
  • Page 441 SEC-1189 Severity INFO SEC-1189 Message <timestamp>, [SEC-1189], <sequence-number>,, INFO, <system-name>, Security violation: Unauthorized host with IP address <IP address> tries to do SNMP write operation. Probable Indicates that an SNMP security violation was reported. The specified unauthorized host attempted to Cause perform a write SNMP operation.
  • Page 442 SEC-1192 Recommended Check if the host IP address specified in the message can be used to manage the fabric through an HTTP Action connection. If so, add the host IP address to the HTTP policy of the fabric. If the host is not allowed access to the fabric, this is a valid violation message and an unauthorized entity is trying to access your fabric.
  • Page 443 SEC-1195 Recommended Run the secFabricShow command to verify that the fabric is still consistent. All the switches should be Action in the ready state. If a switch is in the error state, the database might not be correctly updated for that specific switch.
  • Page 444 SEC-1198 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. Probable Indicates that an API security violation was reported. The specified unauthorized host attempted to Cause establish an API connection.
  • Page 445 SEC-1201 Probable Indicates that an MS forward security violation was reported. A management server command was Cause forwarded from a non-primary FCS switch. Recommended Check the MS policy and verify that the connection is allowed. If the connection is allowed but not Action specified, enable the connection in the MS policy.
  • Page 446 SEC-1203 SEC-1203 Message <timestamp>, [SEC-1203], <sequence-number>,, INFO, <system-name>, Login information: Login successful via TELNET/SSH/RSH. IP Addr: <IP address> Probable Indicates the IP address of the remote station logging in. Cause Recommended No action is required. Action Severity INFO SEC-1250 Message <timestamp>, [SEC-1250], <sequence-number>,, WARNING, <system- name>, DCC enforcement API failed: <failed action>...
  • Page 447 SEC-1253 SEC-1253 Message <timestamp>, [SEC-1253], <sequence-number>,, ERROR, <system-name>, Bad DCC interface state during <Phase>, state=<state>. Probable Indicates that an internal error has caused the DCC policy update to fail in the provision, commit, or Cause cancel phases. Recommended Retry the failed security command. Action If the message persists, run supportFtp (as needed) to set up automatic FTP transfers;...
  • Page 448 SEC-1302 SEC-1302 Message <timestamp>, [SEC-1302], <sequence-number>,, INFO, <system-name>, This switch does not have all the required PKI objects correctly installed. Probable Indicates that there has been a corruption during the distribution of the security database. This can only Cause occur when the primary 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 449 SEC-1305 SEC-1305 Message <timestamp>, [SEC-1305], <sequence-number>,, INFO, <system-name>, This switch has no zoning license. Probable Indicates that there has been a corruption during the distribution of the security database. This can only Cause occur when the primary 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 450 SEC-1308 SEC-1308 Message <timestamp>, [SEC-1308], <sequence-number>,, INFO, <system-name>, All Radius servers have failed to respond. Probable Indicates that all servers in the RADIUS configuration have failed to respond to a switch request within Cause the specified timeout. Recommended Verify that the switch has proper network connectivity to the specified RADIUS servers, and the servers Action are correctly configured.
  • Page 451 SEC-1311 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 Indicates that the security enable failed on the fabric because one or more switches in the fabric have Cause password policies that are not set to the default value.
  • Page 452 SEC-1314 SEC-1314 Message <timestamp>, [SEC-1314], <sequence-number>,, ERROR, <system-name>, Reading <IP Address Description > IP address from EM failed. Probable Indicates that the call to the EM module to retrieve the IP address failed. Cause Recommended Please reboot the system to fix this error. If the problem persists contact your switch service provider. Action Severity ERROR...
  • Page 453 SEC-1317 SEC-1317 Message <timestamp>, [SEC-1317], <sequence-number>,, INFO, <system-name>, Inconsistent fabric, rejecting transaction Probable Indicates that either this domain is performing an FDD merge or matched domains are not the same as Cause what the CM sees. Recommended If a policy conflict exists, resolve it, then wait for the fabric to become stable. Retry the distribution. Action Severity INFO...
  • Page 454 SEC-1320 SEC-1320 Message <timestamp>, [SEC-1320], <sequence-number>,, WARNING, <system- name>, Non-acl domain <Domain Number> tries to join a fabric with strict fabric wide policy Probable Indicates that a domain not supporting ACL tried to join a fabric with a strict fabricwide policy. Cause Recommended No action is required.
  • Page 455 SEC-1323 SEC-1323 Message <timestamp>, [SEC-1323], <sequence-number>,, INFO, <system-name>, Key(s) \"<Key Name>\" ignored during configdownload Probable Indicates that the specified key is ignored during configdownload. Cause Recommended Verify that 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 456 SEC-1326 SEC-1326 Message <timestamp>, [SEC-1326], <sequence-number>,, INFO, <system-name>, Event: fddcfg --fabwideset, Status: success, Info: Fabric wide configuration set to <Fabric-wide configuration set by user>. Probable Indicates that the specified event has occurred. Cause Recommended Verify that 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 457 Chapter SNMP System Messages SNMP-1001 Message <timestamp>, [SNMP-1001], <sequence-number>,, ERROR, <system-name>, SNMP service is not available <Reason>. Probable Indicates that the SNMP service could not be started because of the specified Reason. You will not be Cause able to query the switch through SNMP. Recommended Verify that the IP address for the Ethernet and Fibre Channel interface is set correctly.
  • Page 458 SNMP-1004 Recommended Retry changing the SNMP community strings from the primary switch. Action Severity ERROR SNMP-1004 Message <timestamp>, [SNMP-1004], <sequence-number>, FFDC, ERROR, <system- name>, Incorrect SNMP configuration. Probable Indicates that the SNMP configuration is incorrect and the SNMP service will not work correctly. Cause Recommended Change the SNMP configuration back to the default.
  • Page 459 SNMP-1006 Severity INFO Fabric OS Message Reference 59-3 Publication Number: 53-1000242-01...
  • Page 460 SNMP-1006 59-4 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 461 Chapter SS System Messages SS-1000 Message <timestamp>, [SS-1000], <sequence-number>,, INFO, <system-name>, supportSave has ftp'ed support information to the host with IP address <host ip>. Probable Indicates that the supportSave command was used to transfer support information to a remote FTP Cause location.
  • Page 462 SS-1001 60-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 463 Chapter SULB System Messages SULB-1005 Message <timestamp>, [SULB-1005], <sequence-number>,, INFO, <system-name>, Current Active CP is preparing to failover. Probable Indicates that the active CP is about to reboot. The standby CP is taking over as the active CP. Cause Recommended No action is required.
  • Page 464 SULB-1008 Probable Indicates that the standby CP is rebooting with new firmware. Cause Recommended No action is required. The firmwareDownload command is progressing as expected. Action Run the firmwareDownloadStatus command for more information. Severity INFO SULB-1008 Message <timestamp>, [SULB-1008], <sequence-number>,, INFO, <system-name>, Standby CP booted successfully with new firmware.
  • Page 465 SULB-1025 Probable Indicates that the blade in the indicated slot has rebooted with new firmware. This is a normal step in the Cause firmwareDownload process. Recommended Run the firmwareDownloadStatus command to monitor the firmwareDownload progress. Action Severity WARNING SULB-1025 Message <timestamp>, [SULB-1025], <sequence-number>,, WARNING, <system- name>, The blade in slot <Slot number>...
  • Page 466 SULB-1035 Recommended Run the firmwareShow command to verify the firmware versions. Also run the switchShow command Action to make sure the switch is enabled. Severity WARNING SULB-1035 Message <timestamp>, [SULB-1035], <sequence-number>,, ERROR, <system-name>, An error has occurred during firmwaredownload. Probable Indicates that an error has occurred during the firmwareDownload.
  • Page 467 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 Indicates that the switch is enabled before it is ready. Cause Recommended If the message persists, run supportFtp (as needed) to set up automatic FTP transfers;...
  • Page 468 SWCH-1003 SWCH-1003 Message <timestamp>, [SWCH-1003], <sequence-number>,, ERROR, <system-name>, Slot ENABLED but Not Ready during recovery, disabling slot = <slot number>(<return value>) Probable Indicates that the slot state has been detected as inconsistent during failover or recovery. Cause Recommended On a SilkWorm 12000, 24000, or 48000 switch, run first the slotPowerOff and then the slotPowerOn Action commands.
  • Page 469 SWCH-1006 SWCH-1006 Message <timestamp>, [SWCH-1006], <sequence-number>,, WARNING, <system- name>, HA state out of sync: Standby CP (ver = <standby SWC version>) does not support NPIV functionality. (active ver = <active SWC version>, NPIV devices = <'1' if NPIV devices exist; Otherwise '0'.
  • Page 470 SWCH-1008 Recommended Replace the blade with ports that support port swap. Then port swap the ports back to ports default area. Action Refer to the Fabric OS Administrator’s Guide for more information on port swapping. Severity WARNING 62-4 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 471 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 Indicates that during the boot sequence, one of the programs would not run on the system. Cause Recommended If the message is reported during a reboot after new firmware has been loaded, try reloading the...
  • Page 472 SYSC-1003 SYSC-1003 Message <timestamp>, [SYSC-1003], <sequence-number>, FFDC, CRITICAL, <system-name>, Chassis config option <Option number read from the chassis option storage device> is not supported by CP Blade with ID <Blade ID (platform) number from the Active CP>. Change the chassis configuration <Steps to change chassis configuration>...
  • Page 473 SYSC-1005 Recommended Use the supportSave command to gather troubleshooting data. Issue a hardboot or hafailover to recover Action the system and limit the traffic disruption. Severity WARNING Fabric OS Message Reference 63-3 Publication Number: 53-1000242-01...
  • Page 474 SYSC-1005 63-4 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 475 Chapter SYSM System Messages SYSM-1001 Message <timestamp>, [SYSM-1001], <sequence-number>, FFDC, CRITICAL, <system-name>, No memory Probable Indicates that the switch has run out of system memory. Cause Recommended Run the memShow command to view the switch memory usage. Action Reboot or power cycle the switch. Run supportFtp and traceFtp (as needed) to set up automatic FTP transfers;...
  • Page 476 SYSM-1003 SYSM-1003 Message <timestamp>, [SYSM-1003], <sequence-number>,, INFO, <system-name>, <number>, Switch: <start reason> Probable Indicates that the user executed the switchStart or switchReboot command. This indicates that all Cause services are brought back up after a temporary shutdown of that logical switch. Recommended No action is required if the switchStart command was executed intentionally.
  • Page 477 SYSM-1006 SYSM-1006 Message <timestamp>, [SYSM-1006], <sequence-number>, FFDC, CRITICAL, <system-name>, CP blade in slot <Slot number> is incompatible with the chassis type. Probable Indicates that this chassis type is not compatible with the CP blade. Cause Recommended Use the CP blade on a compatible chassis. Action Severity CRITICAL...
  • Page 478 SYSM-1007 64-4 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 479 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 Indicates that trace dump files have been generated on the switch or the indicated slot.
  • Page 480 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 Indicates that a trace dump has been created on the switch or the indicated slot but is not automatically Cause transferred from the switch due to an FTP error, such as a wrong FTP address, FTP site down, or network down.
  • Page 481 TRCE-1006 TRCE-1006 Message <timestamp>, [TRCE-1006], <sequence-number>,, INFO, <system-name>, FTP Connectivity Test succeeded to FTP site ' <FTP target configured by users.> '. Probable Indicates that a connectivity test to the FTP host has succeeded. This feature is enabled by the Cause supportFtp -t command.
  • Page 482 TRCE-1009 Severity CRITICAL TRCE-1009 Message <timestamp>, [TRCE-1009], <sequence-number>,, ERROR, <system-name>, Unable to alert active CP that a dump has occurred. Probable Indicates that the standby CP is unable to communicate trace information to active CP. This message is Cause only applicable to the SilkWorm 12000, 24000, and 48000. Recommended Run the haShow command to verify that the current CP is standby and the active CP is active.
  • Page 483 TRCE-1012 Recommended No action is required. Action Severity INFO TRCE-1012 Message <timestamp>, [TRCE-1012], <sequence-number>,, WARNING, <system- name>, The system was unable to retrieve trace information from slot <Slot number of the blade the attempt was made on>. Probable Indicates that communication between the main system and the indicated slot is unavailable. Cause Recommended Check that the AP blade is enabled and retry the command.
  • Page 484 TRCE-1012 65-6 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 485 Chapter TRCK System Messages TRCK-1001 Message <timestamp>, [TRCK-1001], <sequence-number>,, INFO, <system-name>, Successful login by user <User>. Probable Indicates that the track change feature recorded a successful login. Cause 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 486 TRCK-1004 Probable Indicates that the track change feature recorded a successful logout. Cause Recommended No action is required. Action Severity INFO TRCK-1004 Message <timestamp>, [TRCK-1004], <sequence-number>,, INFO, <system-name>, Config file change from task:<task> Probable Indicates that the track change feature recorded a configuration change for the switch. The track change Cause feature records any change to the configuration file in nonvolatile memory, including a configDownload.
  • Page 487 TRCK-1006 Recommended No action is required. Run the trackChangesSet 1 command to enable the track changes feature. Action Severity INFO Fabric OS Message Reference 66-3 Publication Number: 53-1000242-01...
  • Page 488 TRCK-1006 66-4 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 489 Chapter TS System Messages TS-1001 Message <timestamp>, [TS-1001], <sequence-number>,, WARNING, <system-name>, NTP Query failed: <error code> Probable Indicates that a network time protocol (NTP) query to the configured external clock server failed. Local Cause clock time on the principal or primary FCS switch is used for fabric synchronization. This might be logged during temporary operational issues such as IP network connection issues to the external clock server.
  • Page 490 TS-1006 Recommended Run the tsClockServer command to verify that the principal or primary FCS switch has the clock Action server IP configured correctly. Verify that this clock server is accessible to the switch and functional. If the principal or primary FCS does not support the feature, either choose a different switch for the role or reset the clock server to LOCL.
  • Page 491 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 Indicates that duplicate paths were reported to the specified domain from the specified output port. The Cause path database (PDB) pointer is the address of the path database and provides debugging information.
  • Page 492 UCST-1020 UCST-1020 Message <timestamp>, [UCST-1020], <sequence-number>,, WARNING, <system- name>, Static route (input-area: <port number>, domain: <domain ID> output-area: <port number>) has been ignored due to platform limitation. Probable Indicates that the configured static route cannot be applied to the routing database due to a platform Cause limitation.
  • Page 493 Chapter UPTH System Messages UPTH-1001 Message <timestamp>, [UPTH-1001], <sequence-number>,, WARNING, <system- name>, No minimum cost path in candidate list Probable Indicates that the specified switch is unreachable because no minimum cost path (FSPF UPATH) exists Cause in the candidate list (domain ID list). Recommended No action is required.
  • Page 494 UPTH-1001 69-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 495 Chapter USWD System Messages USWD-1006 Message <timestamp>, [USWD-1006], <sequence-number>,, WARNING, <system- name>, uSWD: <Warning message> Probable Indicates a warning state in the system. This is an internal use only message. Cause Recommended No action is required. Action Severity WARNING Fabric OS Message Reference 70-1 Publication Number: 53-1000242-01...
  • Page 496 USWD-1006 70-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 497 Chapter WEBD System Messages WEBD-1001 Message <timestamp>, [WEBD-1001], <sequence-number>,, WARNING, <system- name>, Missing or Invalid Certificate file -- HTTPS is configured to be enabled but could not be started. Probable Indicates that the SSL certificate file is either invalid or absent. Cause Recommended Run the configure command to disable HTTPS.
  • Page 498 WEBD-1004 Probable Indicates that the HTTP/HTTPS interface is disabled. This is logged when HTTP/HTTPS is disabled Cause through the configure command. Recommended Run the configure command to enable HTTP/HTTPS. For more information on the configure Action command, refer to the Fabric OS Command Reference. Severity INFO WEBD-1004...
  • Page 499 WEBD-1007 Recommended No action is required. Action Severity INFO WEBD-1007 Message <timestamp>, [WEBD-1007], <sequence-number>, FFDC, INFO, <system- name>, HTTP server will be restarted due to change of IP Address Probable Indicates that the IP address of the switch changed and the HTTP server is restarted. Cause Recommended No action is required.
  • Page 500 WEBD-1008 71-4 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 501 Chapter ZOLB System Messages ZOLB-1001 Message <timestamp>, [ZOLB-1001], <sequence-number>,, ERROR, <system-name>, ZONELIB <error message> Probable Indicates that there was an internal timeout on the IPC between the name server (NS) and the zoning Cause modules. This usually indicates that the system was busy. Recommended This message generates core dump files of the related modules (zoned, nsd, rcsd).
  • Page 502 ZOLB-1001 72-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 503 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 Indicates that a zone filter or zone group check failure occurred. The frame filter logic reported a failure Cause when creating or adding zone groups during PLOGI trap processing.
  • Page 504 ZONE-1004 ZONE-1004 Message <timestamp>, [ZONE-1004], <sequence-number>,, INFO, <system-name>, port <port number> enforcement changed to Session Based HARD Zoning. Probable Indicates that the zoning enforcement changed to session-based hard zoning. When a device is zoned Cause using both WWN in one zone and <domain, portarea> in another, this will cause that port to go session based hard zoning.
  • Page 505 ZONE-1006 ZONE-1006 Message <timestamp>, [ZONE-1006], <sequence-number>,, WARNING, <system- name>, WARNING - WWN(<WWN number>) in HARD PORT zone <zone_name>. Probable Indicates that one or more devices are zoned as WWN devices and also zoned as <domain, portarea> Cause devices. The device(s) are used to specify zone members over separate zones. Recommended If hardware zoning enforcement is preferred, edit the zoning database to have the device zoned using Action...
  • Page 506 ZONE-1010 ZONE-1010 Message <timestamp>, [ZONE-1010], <sequence-number>,, WARNING, <system- name>, WARNING - Duplicate entries in zone(<zone name>) specification. Probable Indicates that there are duplicate entries in a zone object. A zone object member is specified twice in a Cause given zone object. This message occurs only when enabling a zone configuration. Recommended Check the members of the zone and delete the duplicate member.
  • Page 507 ZONE-1014 ZONE-1014 Message <timestamp>, [ZONE-1014], <sequence-number>,, ERROR, <system-name>, Missing required license - <license name>. Probable Indicates that the required zoning license is missing. Cause Recommended Install the zoning license using the licenseAdd command. Refer to your switch supplier to obtain a Action Zoning license if you do not have one.
  • Page 508 ZONE-1018 ZONE-1018 Message <timestamp>, [ZONE-1018], <sequence-number>,, ERROR, <system-name>, Incorrect zoning enforcement type(<zone type>) at port(<port number>) Probable Indicates that an incorrect zoning enforcement type was reported on the specified port. This is a Cause software error. A QuickLoop zone type (value = 4) or an uninitialized type (value = 0) are invalid. The valid zone type values are: •...
  • Page 509 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 Indicates that the effective zone configuration has changed to the name displayed. Cause Recommended Verify that this zone configuration change was done on purpose. If the new effective zone configuration Action is correct, no action is necessary.
  • Page 510 ZONE-1026 ZONE-1026 Message <timestamp>, [ZONE-1026], <sequence-number>,, INFO, <system-name>, port <port number> Out of CAM entries Probable Indicates that the total number of S_ID entries while creating or adding a zone group exceeds the limit. Cause Recommended If hardware zoning enforcement is preferred, edit the zoning database to have zoned PIDs for that port. Action Severity INFO...
  • Page 511 ZONE-1029 Probable Indicates that the zone database size is greater than the limit allowed by the fabric. The limit of the zone Cause database size depends on the lowest level switch in the fabric. Older switches have less memory and force a smaller zone database for the entire fabric.
  • Page 512 ZONE-1031 ZONE-1031 Message <timestamp>, [ZONE-1031], <sequence-number>,, ERROR, <system-name>, Switch is in interop mode. (switch, port) members not supported. Probable The switch is set to interop mode using the interopMode command. Interop mode does not allow Cause <domain, portarea> members in the active zone database. Recommended Remove all <domain, portarea>...
  • Page 513 ZONE-1034 ZONE-1034 Message <timestamp>, [ZONE-1034], <sequence-number>,, WARNING, <system- name>, Zoning file doesn't exist or Corrupted Zoning files detected before reboot, currently the file is saved at <config file name> Probable Indicates that the zone database is corrupt or zone database is not found. Cause Recommended Use the firmwareDownload command to reinstall the firmware.
  • Page 514 ZONE-1037 ZONE-1037 Message <timestamp>, [ZONE-1037], <sequence-number>,, ERROR, <system-name>, Unable to examine <config file name>: error message <System Error Message> Probable Indicates that the Fabric OS cannot examine the zone configuration file. Typically the zone Cause configuration is too large for the memory available on the switch. Recommended Reduce the size of the zone database and retry the operation.
  • Page 515 ZONE-1040 ZONE-1040 Message <timestamp>, [ZONE-1040], <sequence-number>,, INFO, <system-name>, Merged zone database exceeds limit. Probable Indicates that the Fabric OS cannot read the merged zone configuration file. Typically the zone Cause configuration is too large for the memory available on the switch. Recommended Reduce the size of the zone database and retry the operation.
  • Page 516 ZONE-1043 ZONE-1043 Message <timestamp>, [ZONE-1043], <sequence-number>,, INFO, <system-name>, The Default Zone access mode is set to No Access Probable Indicates that the Default Zone access mode is set to No Access. Cause Recommended Verify that this Default Zone access mode change was done intentionally. Action Severity INFO...
  • Page 517 ZONE-1046 ZONE-1046 Message <timestamp>, [ZONE-1046], <sequence-number>,, INFO, <system-name>, The Default Zone access mode is already set to All Access Probable Indicates that the Default Zone access mode is already set to All Access. Cause Recommended No action is required. Action Severity INFO Fabric OS Message Reference...
  • Page 518 ZONE-1046 73-16 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 519 Section Audit Log Messages This section provides the Audit messages, including: • AUDIT AUTH System Messages • AUDIT CONF System Messages • AUDIT HTTP System Messages • AUDIT SEC System Messages • AUDIT SNMP System Messages • AUDIT SULB System Messages •...
  • Page 520 II-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 521 Chapter AUDIT AUTH System Messages AUTH-3001 Message AUDIT, <timestamp>, [AUTH-3001], INFO, SECURITY, <event-initiator- details>, <event-location>, , Event: <Event Name>, Status: success, Info: <Data type> type has been changed from [<Old value>] to [<New value>]. Probable Indicates that an authentication configuration value was set to a specified value. The data type is Cause "authentication type", "DH group type"...
  • Page 522 AUTH-3003 AUTH-3003 Message AUDIT, <timestamp>, [AUTH-3003], INFO, SECURITY, <event-initiator- details>, <event-location>, , Event: <Event Name>, Status: success, Info: <Operation type> the PKI objects. Probable Indicates that the pki Objects were created using the pkiCreate command, or that the pki objects were Cause removed using the pkiRemove command.
  • Page 523 Chapter AUDIT CONF System Messages CONF-1000 Message AUDIT, <timestamp>, [CONF-1000], INFO, CFG, <event-initiator- details>, <event-location>, , configDownload completed successfully <Info about the parameters and AD>. Probable The configDownload process was initiated and completed successfully. The message string describes Cause the class of configuration parameters that were downloaded. If AD is enabled, the AD number is specified in the description.
  • Page 524 CONF-1022 CONF-1022 Message AUDIT, <timestamp>, [CONF-1022], WARNING, CFG, <event-initiator- details>, <event-location>, , Downloading configuration without disabling the switch was unsuccessful. Probable The system attempted to download a configuration without disabling the switch was unsuccessful Cause because there are one or more parameters that require the switch to be disabled. Recommended Disable the switch using the switchDisable command and download the configuration.
  • Page 525 Chapter AUDIT HTTP System Messages HTTP-1002 Message AUDIT, <timestamp>, [HTTP-1002], INFO, ZONE, <event-initiator- details>, <event-location>, , Zoning transaction initiated by User: <User Name>, Role: <User Role> completed successfully. Probable Indicates that the zoning database has been changed. Cause Recommended Verify that 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 526 HTTP-1003 76-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 527 Chapter AUDIT SEC System Messages SEC-3001 Message AUDIT, <timestamp>, [SEC-3001], INFO, SECURITY, <event-initiator- details>, <event-location>, , Event: <Event Name>, Status: success, Info: Security mode <State change: Enabled or Disabled> on the fabric. Probable Indicates that the security mode of the fabric was either enabled or disabled. Cause Recommended Verify that the security mode change was planned.
  • Page 528 SEC-3003 SEC-3003 Message AUDIT, <timestamp>, [SEC-3003], INFO, SECURITY, <event-initiator- details>, <event-location>, , Event: <Event Name>, Status: success, Info: Created <Policy Name> policy, with member(s) <Member List> . Probable Indicates that a new security policy was created with entries. Cause Note: If you use a wildcard (for example, an asterisk) in creating a policy, the audit report displays the wildcard in the event info field.
  • Page 529 SEC-3006 Recommended Verify that the addition of members to the policy was planned. If the addition of members was planned, Action no action is required. If the addition of members was not planned, take appropriate action as defined by your enterprise security policy. Severity INFO SEC-3006...
  • Page 530 SEC-3008 SEC-3008 Message AUDIT, <timestamp>, [SEC-3008], INFO, SECURITY, <event-initiator- details>, <event-location>, , Event: <Event Name>, Status: success, Info: FCS member moved from position <Old FCS position> to <New FCS position>. Probable Indicates that the FCS list has been modified. One of the members of the list has been moved to a new Cause position in the list, as identified in the message.
  • Page 531 SEC-3011 Severity INFO SEC-3011 Message AUDIT, <timestamp>, [SEC-3011], INFO, SECURITY, <event-initiator- details>, <event-location>, , Event: <Event Name>, Status: success, Info: Reset [<Stat name>] statistics on domain(s) [<Domain IDs>]. Probable Indicates that a user has reset a security statistic on the specified domains. Cause Recommended Verify that the security statistic was intentionally reset.
  • Page 532 SEC-3014 Recommended Verify that the security version stamp was intentionally reset. If the security event was planned, no Action action is required. If the security version stamp was not intentionally reset, take appropriate action as defined by your enterprise security policy. Severity INFO SEC-3014...
  • Page 533 SEC-3017 Probable Indicates that a user has changed the specified attribute of the RADIUS server. Cause Recommended Verify that the RADIUS attribute was intentionally changed. If the RADIUS attribute was intentionally Action changed, no action is required. If the RADIUS attribute was not intentionally changed, take appropriate action as defined by your enterprise security policy.
  • Page 534 SEC-3019 SEC-3019 Message AUDIT, <timestamp>, [SEC-3019], INFO, SECURITY, <event-initiator- details>, <event-location>, , Event: <Event Name>, Status: success, Info: Passwdcfg parameters set to default values. Probable Indicates that the passwdCfg parameters are set to default values. Cause Recommended Verify that 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 535 SEC-3022 SEC-3022 Message AUDIT, <timestamp>, [SEC-3022], INFO, SECURITY, <event-initiator- details>, <event-location>, , Event: <Event Name>, Status: success, Info: Successful logout by user [<User>]. Probable Indicates that the specified user has successfully logged out. Cause Recommended No Action is Required. Action Severity INFO SEC-3023...
  • Page 536 SEC-3025 SEC-3025 Message AUDIT, <timestamp>, [SEC-3025], INFO, SECURITY, <event-initiator- details>, <event-location>, , Event: <Event Name>, Status: success, Info: User account [<User Name>] added. Role: [<Role Type>], Password [<Password Expired or not>], Home AD [<Home AD>], AD list [<AD membership List>]. Probable Indicates a new user account was created.
  • Page 537 SEC-3028 Severity INFO SEC-3028 Message AUDIT, <timestamp>, [SEC-3028], INFO, SECURITY, <event-initiator- details>, <event-location>, , Event: <Event Name>, Status: success, Info: User account [<User Name>] deleted. Probable Indicates that the specified user account was deleted. Cause Recommended Verify that 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 538 SEC-3031 Severity INFO SEC-3031 Message AUDIT, <timestamp>, [SEC-3031], INFO, SECURITY, <event-initiator- details>, <event-location>, , Event: <Event Name>, Status: success, Info: Distributed<List of Databases> db(s) to <Number of domains> domain(s), dom-id(s)<List of Domains>. Probable Indicates that the specified event has occurred. Cause Recommended Verify that the event was planned.
  • Page 539 SEC-3034 Recommended Verify that 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-3034 Message AUDIT, <timestamp>, [SEC-3034], INFO, SECURITY, <event-initiator- details>, <event-location>, , Event: aaaconfig, Status: success, Info: Authentication configuration changed from <Previous Mode>...
  • Page 540 SEC-3034 77-14 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 541 Chapter AUDIT SNMP System Messages SNMP-1005 Message AUDIT, <timestamp>, [SNMP-1005], INFO, CONFIGURATION, <event- initiator-details>, <event-location>, , SNMP configuration attribute, <Changed attribute>, has changed from <Old Value> to <New Value> Probable Indicates that the SNMP configuration has changed as indicated. Cause Recommended Use the snmpConfig --show command to display the new configuration.
  • Page 542 SNMP-1006 78-2 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 543 Chapter AUDIT SULB System Messages SULB-1001 Message AUDIT, <timestamp>, [SULB-1001], WARNING, FIRMWARE, <event- initiator-details>, <event-location>, , Firmwaredownload command has started. Probable Indicates that the firmwareDownload command has been entered. This process can take some time. Cause Recommended No action is required. Allow the firmwareDownload command to continue without disruption. Do not Action fail over or power down the system during firmware upgrade.
  • Page 544 SULB-1003 SULB-1003 Message AUDIT, <timestamp>, [SULB-1003], INFO, FIRMWARE, <event-initiator- details>, <event-location>, , Firmwarecommit has started. Probable Indicates that the firmwareCommit command has been entered. Cause Recommended No action is required. Run the firmwareDownloadStatus command for more information. Action Severity INFO SULB-1009 Message AUDIT, <timestamp>, [SULB-1009], INFO, FIRMWARE, <event-initiator-...
  • Page 545 SULB-1009 Status Message Status Code "firmwareDownload failed due to IPC error." 0x50 "Unable to check the firmware version on Standby CP due to IPC error." 0x51 "firmwareDownload failed due to IPC error." 0x52 "firmwareDownload failed due to IPC error." 0x53 "Standby CP failed to reboot due to IPC error."...
  • Page 546 SULB-1009 Status Message Status Code "firmwareCommit has started on Standby CP." 0x77 "firmwareCommit has completed successfully on Standby CP." 0x78 "Standby CP booted up with new firmware." 0x79 "Standby CP failed to boot up with new firmware." 0x7a "firmwareCommit has started on both Active and Standby CPs." 0x7b "firmwareCommit has completed successfully on both CPs."...
  • Page 547 SULB-1009 Status Message Status Code "The secondary partition has been restored successfully." 0x95 "Firmware is being downloaded to the blade. This step may take up to 10 0xa0 minutes." "firmwareDownload timed out." 0xa1 "Reboot occurred during firmwareDownload. firmwareCommit will be started 0xa2 to recover the blade."...
  • Page 548 SULB-1009 Table 79-2 lists additional firmwareDownload error messages and error codes. They provide more details on why firmwareDownload failed. Table 79-2 Error Messages and Error Codes Error Message Error Code "Image is up-to-date. No need to download the same version of firmware." "Upgrade is inconsistent.
  • Page 549 SULB-1009 Error Message Error Code "The pre-install script failed." 0x29 "The platform option is not supported. Run chassisConfig to reset the option first 0x2a and then try firmwareDownload." "Failed to install RPM package." 0x2b "Cannot downgrade directly to this version. Downgrade to an intermediate version 0x2c first and then download the desired version."...
  • Page 550 SULB-1009 0x18 - Error in getting lock device for firmwaredownload. This error can occur because another firmwareDownload is already in progress. Run firmwareDownloadStatus command to verify that is the case. Wait until the current session to finish before proceeding. 0x23 - firmwareDownload timed out. This error can occur because firmwareDownload has not been completed within the predefined timeout period.
  • Page 551 SULB-1010 Upgrade State Code SUS_PEER_FWC_BEGIN 0x32 SUS_PEER_FS_CHECK1 0x33 SUS_FINISH 0x34 SUS_COMMIT 0x35 Recommended Run the firmwareDownloadStatus command for more information. Action In a director, when firmwareDownload fails, the command will synchronize the firmware on the two partitions of each CP by starting a firmware commit operation. Wait until this operation completes (about 10 minutes) before attempting another firmwareDownload.
  • Page 552 SULB-1018 Recommended Run the slotShow command. If the blade is in a Faulty state, run the slotPowerOff and slotPowerOn Action commands to that blade to trigger another firmwareDownload. If the blade is stuck in LOADING state, you need to remove and re-insert the blade to trigger another firmwareDownload. If the problem persists, contact your switch service provider.
  • Page 553 SULB-1021 SULB-1021 Message AUDIT, <timestamp>, [SULB-1021], WARNING, FIRMWARE, <event- initiator-details>, <event-location>, , Firmware is being downloaded to the blade in slot <Slot number>. Probable Indicates that the firmware is being loaded to the indicated blade. Cause Recommended Run the firmwareDownloadStatus command to monitor the firmwareDownload progress. After it Action finishes, run the firmwareShow command to verify the firmware versions.
  • Page 554 SULB-1026 Recommended Since the operation may have been started to repair the secondary partition, run the firmwareShow Action command to verify the versions. If the blade firmware version is still inconsistent with the active CP firmware, firmwareDownload will be started automatically to the blade again. If the blade firmware is the same as the active CP firmware, firmwareDownload has completed successfully on the blade.
  • Page 555 SULB-1034 Probable The error can be caused by unexpected disruption of the firmwareDownload command, for example, Cause power the switch on an off in the middle of a firmwareDownload. This error can also be caused by the persistent storage failure, or other hardware failures. Recommended Retry the firmwareDownload operation.
  • Page 556 SULB-1034 79-14 Fabric OS Message Reference Publication Number: 53-1000242-01...
  • Page 557 Chapter AUDIT ZONE System Messages ZONE-3001 Message AUDIT, <timestamp>, [ZONE-3001], INFO, ZONE, <event-initiator- details>, <event-location>, , Event: <Event Name>, Status: success, Info: <Zone object type> \"<Zone object member list>\" added to <Zone object set type> \"<Zone object set name>\". Probable Indicates that a new zone object member or members have been added to a zone object set.
  • Page 558 ZONE-3003 ZONE-3003 Message AUDIT, <timestamp>, [ZONE-3003], INFO, ZONE, <event-initiator- details>, <event-location>, , Event: <Event Name>, Status: success, Info: <Zone object type> \"<Zone object name>\" deleted. Probable Indicates that the specified zone object has been deleted. Cause The zone object type can be "alias", "zone member", "zone" or "zone configuration". The string "..." appears at the end of the zone object member list if the list was truncated in the message.
  • Page 559 ZONE-3006 Recommended Verify that 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 ZONE-3006 Message AUDIT, <timestamp>, [ZONE-3006], INFO, ZONE, <event-initiator- details>, <event-location>, , Event: <Event Name>, Status: success, Info: Current zone configuration disabled.
  • Page 560 ZONE-3009 Recommended Verify that 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 ZONE-3009 Message AUDIT, <timestamp>, [ZONE-3009], INFO, ZONE, <event-initiator- details>, <event-location>, , Event: <Event Name>, Status: success, Info: <Event Description>...
  • Page 561 ZONE-3012 Recommended Verify that 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 ZONE-3012 Message AUDIT, <timestamp>, [ZONE-3012], INFO, ZONE, <event-initiator- details>, <event-location>, , Event: <Event Name>, Status: success, Info: Zone object \"<Zone object name>\"...
  • Page 562 ZONE-3015 Probable Indicates that the specified new AD object member or members have been added to the specified AD Cause object set. An AD object set type is "AD member". The string "..." appears at the end of the AD object member list if the list was truncated in the message.
  • Page 563 ZONE-3017 ZONE-3017 Message 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 Indicates that the specified admin domain has been created. Cause An AD object set type is "AD member".
  • Page 564 ZONE-3020 Severity INFO ZONE-3020 Message AUDIT, <timestamp>, [ZONE-3020], INFO, FABRIC, <event-initiator- details>, <event-location>, , Event: <Event Name>, Status: success, Info: \"<AD object member list>\" removed from <AD object set type> \"<AD object set name>\". Probable Indicates that the specified AD member or members have been removed from an AD. Cause Recommended Verify that the event was planned.
  • Page 565 ZONE-3023 Severity INFO ZONE-3023 Message AUDIT, <timestamp>, [ZONE-3023], INFO, FABRIC, <event-initiator- details>, <event-location>, , Event: <Event Name>, Status: Failure, Info: AD Apply operation failed due to transaction conflict. Probable Indicates that the AD apply operation failed due to a transaction conflict. Cause Recommended Verify that the event was planned.
  • Page 566 ZONE-3025 80-10 Fabric OS Message Reference Publication Number: 53-1000242-01...

Table of Contents