Brocade, Fabric OS, File Lifecycle Manager, MyView, and StorageX are registered trademarks and the Brocade B-wing symbol, DCX, and SAN
Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. All other brands, products, or
service names are or may be trademarks or service marks of, and are used to identify, products or services of their respective owners.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any equipment,
equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document at any time,
without notice, and assumes no responsibility for its use. This informational document describes features that may not be currently available.
Contact a Brocade sales office for information on feature and product availability. Export of technical data contained in this document may
require an export license from the United States government.
The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any person or entity with respect to any loss,
cost, liability, or damages arising from the information contained in this book or the computer programs that accompany it.
The product described by this document may contain “open source” software covered by the GNU General Public License or other open source
license agreements. To find-out which open source software is included in Brocade products, view the licensing terms applicable to the open
source software, and obtain a copy of the programming source code, please visit
http://www.brocade.com/support/oscd.
Brocade Communications Systems, Incorporated
Corporate Headquarters
Brocade Communications Systems, Inc.
1745 Technology Drive
San Jose, CA 95110
Tel: 1-408-333-8000
Fax: 1-408-333-8101
Email: info@brocade.com
European and Latin American Headquarters
Brocade Communications Switzerland Sàrl
Centre Swissair
Tour A - 2ème étage
29, Route de l'Aéroport
Case Postale 105
CH-1215 Genève 15
Switzerland
Tel: +41 22 799 56 40
Fax: +41 22 799 56 41
Email: emea-info@brocade.com
Document History
TitlePublication
number
Diagnostic and System Error
Message Reference v3.0, v4.0
Diagnostic and System Error
Message Reference v3.1.0
Diagnostic and System Error
Message Reference v4.1.0
Diagnostic and System Error
Message Reference v4.1.2
Diagnostic and System Error
Message Reference v4.2.0
Diagnostic and System Error
Message Reference v4.2.0
53-0000210-02 First releaseMarch 2002
53-0000511-04 Major content reorganizationJune 2003
54-0000515-02 Major content reorganizationJune 2003
53-0000515-06 Minor editorial changesOctober 2003
53-0000515-07Add FW and PLATFORM messagesDecember 2003
53-0000515-08 Update software and hardware supportMarch 2004
This document is organized to help you find the information that you want as quickly and easily as
possible.
The document contains the following components:
• Chapter 1, “Introduction To System Messages” provides basic information on system
messages.
• Chapters 2 through 87 provide message syntax, probable cause, recommended action, and
severity for each of the system messages.
Supported hardware and software
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. for 6.1.0, documenting all possible configurations and
scenarios is beyond the scope of this document.
The following hardware platforms are supported by this release of Fabric OS:
• Brocade 4100, 4900, 5000, 7500, AP 7600 switches
• Brocade 24000 director
• Brocade 48000 director
• FA4-16 blade
• FC10-6 blade
What’s new in this document
The following changes have been made since this document was last released:
• Information that was modified:
• “AG System Messages”
• “BL System Messages”
• “C2 System Messages”
• “EM System Messages”
• “FABR System Messages”
• “FCR System Messages”
• “FCIP System Messages”
• “FW System Messages”
• “SEC System Messages”
• “NS System Messages”
• “PDM System Messages”
• “SULB System Messages”
• “SWCH System Messages”
• “ZONE System Messages”
• “WEBD System Messages”
• “AUDIT SEC System Messages”
• Information that was added:
• “AUDIT FW System Messages”
For further information about new features and documentation updates for this release, refer to
the release notes.
Document conventions
This section describes text formatting conventions and important notices formats used in this
document.
Text formatting
The narrative-text formatting conventions that are used are as follows:
xlviiiFabric OS Message Reference
53-1000640-02
bold textIdentifies command names
Identifies the names of user-manipulated GUI elements
Identifies keywords and operands
Identifies text to enter at the GUI or CLI
italic textProvides emphasis
Identifies variables
Identifies paths and Internet addresses
Identifies document titles
code textIdentifies CLI output
Identifies command syntax examples
For readability, command names in the narrative portions of this guide are presented in mixed
lettercase: for example, switchShow. In actual examples, command lettercase is often all
lowercase. Otherwise, this manual specifically notes those cases in which a command is case
sensitive.
Notes, cautions, and warnings
The following notices and statements are used in this manual. They are listed below in order of
increasing severity of potential hazards.
NOTE
A note provides a tip, guidance or advice, emphasizes important information, or provides a reference
to related information.
ATTENTION
An Attention statement indicates potential damage to hardware or data.
CAUTION
A Caution statement alerts you to situations that can be potentially hazardous to you.
DANGER
A Danger statement indicates conditions or situations that can be potentially lethal or extremely
hazardous to you. Safety labels are also attached directly to products to warn of these conditions
or situations.
Key terms
For definitions specific to Brocade and Fibre Channel, see the Brocade Glossary.
For definitions of SAN-specific terms, visit the Storage Networking Industry Association online
dictionary at:
http://www.snia.org/education/dictionary
Fabric OS Message Referencexlix
53-1000640-02
Additional information
This section lists additional Brocade and industry-specific documentation that you might find
helpful.
Brocade resources
To get up-to-the-minute information, join Brocade Connect. It’s free! Go to http://www.brocade.com
and click Brocade Connect to register at no cost for a user ID and password.
For practical discussions about SAN design, implementation, and maintenance, you can obtain
Building SANs with Brocade Fabric Switches through:
http://www.amazon.com
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.
Other industry resources
• White papers, online demos, and data sheets are available through the Brocade Web site at
http://www.brocade.com/products/software.jhtml.
• Best practice guides, white papers, data sheets, and other documentation is available through
the Brocade Partner Web site.
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
Contact your switch support supplier for hardware, firmware, and software support, including
product repairs and part ordering. To expedite your call, have the following information available:
1. General Information
• Switch model
• Switch operating system version
• Error numbers and messages received
• supportSave command output
lFabric OS Message Reference
53-1000640-02
• Detailed description of the problem, including the switch or fabric behavior immediately
following the problem, and specific questions
• Description of any troubleshooting steps already performed and the results
• Serial console and Telnet session logs
• syslog message logs
2. Switch Serial Number
The switch serial number and corresponding bar code are provided on the serial number label,
as illustrated below.:
*FT00X0054E9*
FT00X0054E9
The serial number label is located as follows:
• Brocade 200E—On the nonport side of the chassis
• Brocade 300, 4100, 4900, 5100, 5300, and 7500—On the switch ID pull-out tab located
inside the chassis on the port side on the left
• Brocade 5000—On the switch ID pull-out tab located on the bottom of the port side of the
switch
• Brocade 7600—On the bottom of the chassis
• Brocade 48000—Inside the chassis next to the power supply bays
• Brocade DCX—On the bottom right on the port side of the chassis
3. World Wide Name (WWN)
Use the wwn command to display the switch WWN.
• If you cannot use the wwn command because the switch is inoperable, you can get the
WWN from the same place as the serial number, except for the Brocade DCX. For the
Brocade DCX, access the numbers on the WWN cards by removing the Brocade logo plate
at the top of the nonport side of the chassis.
Document feedback
Quality is our first concern at Brocade and 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 of the document and as much detail as possible about your
comment, including the topic heading and page number and your suggestions for improvement.
Fabric OS Message Referenceli
53-1000640-02
liiFabric OS Message Reference
53-1000640-02
Chapter
Introduction To System Messages
This guide supports Fabric OS v6.1.0 and documents system messages that can help you diagnose
and fix problems with a switch or fabric. The messages are organized first by event type, reliability,
availability, and serviceability log (RASLog) or AUDIT, and then alphabetically by module name. A
module is a subsystem in the Fabric OS. Each module generates a set of numbered messages. For
each message, this guide provides message text, probable cause, recommended action, and
severity level. There may be more than one cause and more than one recommended action for any
given message. This guide discusses the most probable cause and typical action recommended.
This chapter provides an introduction to system messages. It includes the following topics:
The Fabric OS maintains an internal system message log of all messages. All messages are tagged
by type as either RASLog system error messages, Audit messages, or both. RASLog error messages
are primarily designed to indicate and log abnormal, error-related events, whereas Audit messages
record events such as login failures, zone, or configuration changes. Fabric OS supports a different
methodology for storing and accessing each type of message.
This section provides information on the various logs saved by the system and how to view the
information in the log files, including the following topics:
The RASLog service generates and stores messages related to abnormal or erroneous system
behavior. It includes the following features:
• All RASLog error messages are saved to nonvolatile storage by default.
• The system error message log can save a maximum of 1024 messages in random access
memory (RAM).
• The system message log is implemented as a circular buffer. When more than maximum
entries are added to the log file, old entries are overwritten by new entries.
Fabric OS Message Reference1
53-1000600-02
Overview of System Messages
1
• Messages are numbered sequentially from 1 to 2,147,483,647 (0x7ffffff). The sequence
• By default, the errDump and errShow commands display all of the system error messages.
• Trace dump, first-time failure detection capture (FFDC), and core dump files can be uploaded
• It is recommended to configure the syslogd facility as a management tool for error logs. This is
Event Auditing
Event auditing is designed to support post-event audits and problem determination based on
high-frequency events of certain types such as security violations, zoning configuration changes,
firmware downloads, and certain types of fabric events. Fabric OS versions earlier than v5.2.0
generated a subset of messages flagged as AUDIT in the RASLog to identify some of this type of
output in addition to error log messages. In Fabric OS v5.2.0 and later, messages flagged as AUDIT
are no longer saved in the switch’s error logs. Instead, the switch can be configured to stream Audit
messages to the switch console and to forward the messages to specified syslog servers. There is
no limit to the number of audit events.
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.
to the FTP server using the supportSave command.
particularly important for dual-domain switches because the syslogd facility saves messages
from two logical switches as a single file and in sequential order. See “System Logging Daemon
(syslogd)” on page 3 for more information.
For any given event, AUDIT messages capture the following information:
• User Name - The name of the user who triggered the action.
• User Role - The access level of the user, such as, root or admin.
• Event Name - The name of the event that occurred.
• Status - The status of the event that occurred: success or failure.
• Event Info - Information about the event.
The five event classes described in the following table can be audited.
TABLE 1
Operand Event ClassDescription
1ZoneYou can audit zone event configuration changes, but not the actual
values that were changed. For example, you may receive a message
that states “Zone configuration has changed,” but the message
does not display the actual values that were changed.
2SecurityYou can audit any user-initiated security event for all management
interfaces. For events that have an impact on the entire fabric, an
audit is only generated for the switch from which the event was
initiated.
3ConfigurationYou can audit configuration downloads of existing SNMP
configuration parameters. Configuration uploads are not audited.
4FirmwareYou can audit configuration downloads of existing SNMP
configuration parameters. Configuration uploads are not audited.
5FabricYou can audit Administration Domain related changes.
2Fabric OS Message Reference
53-1000600-02
Overview of System Messages
Fabric OS v6.1.0 generates the following component-specific Audit messages:
Event auditing is a configurable feature, set to off by default. You must enable event auditing by
configuring the syslog daemon to send the events to a configured remote host using the
syslogIpAdd command. You can set up filters to screen out particular classes of events using the
auditCfg command (the classes include zone, security, configuration, firmware, and fabric). The
defined set of Audit messages are sent to the configured remote host in the Audit message format,
so that they are easily distinguishable from other syslog events that might occur in the network. For
details on how to configure event auditing, see “Viewing and Configuring System Message Logs” on
page 4.
System Logging Daemon (syslogd)
The system logging daemon (syslogd) is a process on UNIX, Linux, and some Windows systems that
reads and logs messages as specified by the system administrator.
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. Configuring for syslogd
involves configuring the host, enabling syslogd on the Brocade model, and, optionally, setting the
facility level.
For the Brocade DCX, 24000 and 48000, each CP has a unique error log, depending on which CP
was active when that message was reported. To fully understand message logging on the Brocade 24000 and 48000 you should enable the system logging daemon, because the logs on the host
computer are maintained in a single merged file for both CPs and are in sequential order.
Otherwise, you must examine the error logs in both CPs, particularly for events such as
firmwareDownload or haFailover, for which the active CP changes.
For the Brocade DCX, 24000 and 48000, any security violations that occur through Telnet, HTTP, or
serial connections are not propagated between CPs. Security violations on the active CP are not
propagated to the standby CP counters in the event of a failover, nor do security violations on the
standby CP get propagated to the active CP counters.
For information on configuring syslogd functionality, refer to the Fabric OS Administrator’s Guide.
System Console
The system console displays messages only through the serial port. If you log in to a switch through
the Ethernet port or modem port, you will not receive system console messages.
Fabric OS Message Reference3
53-1000600-02
Viewing and Configuring System Message Logs
1
The system console displays system messages, Audit messages (if enabled) and panic dump
messages. These messages are mirrored to the system console; they are always saved in one of
the system logs.
You can filter messages that appear on the system console by severity using the errFilterSet
command. All messages are still sent to the system message log and syslog (if enabled).
Port Logs
The Fabric OS maintains an internal log of all port activity. Each switch or logical switch maintains a
log file for each port. Port logs are circular buffers that can save up to 8000 entries per logical
switch. When the log is full, the newest log entries overwrite the oldest log entries. Port logs capture
switch-to-device, device-to-switch, switch-to-switch, some device A-to-device B, and control
information. Port logs are not persistent and are lost over power cycles and reboots.
Run the portLogShow command to display the port logs for a particular port.
Run the portLogEventShow command to display the specific events reported for each port.
Refer to the Fabric OS Administrator’s Guide for information on interpreting results of the
portLogDump command.
Port log functionality is completely separate from the system message log. Port logs are typically
used to troubleshoot device connections.
Viewing and Configuring System Message Logs
This section provides information on viewing and configuring system message logs, including:
The procedures are valid for the Brocade DCX, 200E, 3016, 3250, 3850, 3900, 4012, 4016,
4018, 4020, 4024, 4100, 4900, 5000, 7500, AP 76000, 24000, and 48000.
Table 2 describes commands that you can use to view or configure the system message logs. Most
commands require admin access level. For detailed information on required access levels and
commands, refer to the Fabric OS Command Reference.
4Fabric OS Message Reference
53-1000600-02
Viewing and Configuring System Message Logs
TABLE 2Commands for Viewing or Configuring the System Parameters and Logs
Command Description
agtCfgDefaultResets the SNMP recipients to default values.
agtCfgSetModifies the SNMP agent configuration.
agtCfgShowDisplays the current SNMP agent configuration.
auditCfgConfigures the audit message log.
auditShowModifies and displays audit log filter configuration.
diagPostSets or displays diagnostic POST (Power-On Self-Test) configuration.
errClearClears all error log messages for all switch instances on this control
processor (CP).
errDelimterSetSets the error log start and end delimiter for messages pushed to the
console.
errDumpDisplays the entire error log, without page breaks. Use the -r option to
show the messages in reverse order, from newest to oldest.
errFilterSetSets an error severity filter for the system console.
1
errShowDisplays the entire error log, with page breaks. Use the -r option to show
the messages in reverse order, from newest to oldest.
pdShowDisplays the contents of the panic dump and core dump files.
portErrShowDisplays the port error summary.
portLogClearClears the port log. If the port log is disabled, this command enables it.
portLogDisableDisables the port log facility.
portLogDumpDisplays the port log, without page breaks.
portLogDumpPortDisplays the port log of the specified port, without page breaks.
portLogEventShowDisplays which port log events are currently being reported.
portLoginShowDisplays port logins.
portLogPdiscSets or clears the debug pdisc_flag.
portLogResetEnables the port log facility.
portLogResizeResizes the port log to the specified number of entries.
portLogShowDisplays the port log, with page breaks.
portLogShowPortDisplays the port log of specified port, with page breaks.
portLogTypeDisableDisables an event from reporting to the port log. Port log events are
described by the portLogEventShow command.
portLogTypeEnableEnables an event to report to the port log. Port log events are described
by the portLogEventShow command.
setVerboseSets the verbose level of a particular module within the Fabric OS.
supportFtpSets, clears, or displays support FTP parameters or a time interval to
check the FTP server.
Fabric OS Message Reference5
53-1000600-02
Viewing and Configuring System Message Logs
1
TABLE 2Commands for Viewing or Configuring the System Parameters and Logs (Continued)
Command Description
supportFfdcEnables and disables FFDC (first failure data capture).
supportSaveCollects RASLog, trace files, and supportShow (active CP only)
supportShowExecutes a list of diagnostic and error display commands. This output is
syslogDIpAddAdds an IP address as a recipient of system messages.
syslogDIpRemoveRemoves an IP address as a recipient of system messages.
syslogDIpShowViews the currently configured IP addresses that are recipients of system
syslogdFacilityChanges the syslogd facility.
systemVerificationUse this command to run a comprehensive system wide test of all
information for the local CP and then transfers the files to an FTP server.
The operation can take several minutes.
used by your switch service provider to diagnose and correct problems
with the switch. The output from this command is very long.
messages.
switches in a system. It will initiate a burnin run on all switches within the
current system. Note that any reference seen to slot 0 is a reference to
the blade within the switch platform, e.g.,Brocade 7500 and AP7600
contain FR4-18i and FA4-18 blades respectively.
traceDumpDisplays, initiates, or removes a Fabric OS module trace dump.
traceTrigSets, removes, or displays trace triggers.
Viewing System Messages from Web Tools
To view the system message log for a switch from Web Tools:
1. Launch Web Tools.
2. Select the desired switch from the Fabric Tree. The Switch View displays.
3. Click the Switch Events button. A Switch Events Report displays.
4. View the switch events and messages.
In dual-domain switches, an Event button exists for each logical switch. Only messages relating to
that switch (and chassis) will be displayed.
Dumping System Messages
To display the system message log, with no page breaks:
1. Log in to the switch as admin.
2. Enter the errDump command at the command line:
switch:admin> errDump
Version: 5.0.1
2004/07/28-17:04:59, [FSSM-1002], 1,, INFO, switch, HA State is in sync
2004/07/28-17:04:59, [FSSM-1003], 2,, WARNING, switch, HA State out of sync
6Fabric OS Message Reference
53-1000600-02
Viewing and Configuring System Message Logs
2004/07/28-17:04:51, [EM-1055], 3,, WARNING, switch, Media 27: Port media
incompatible. Reason: Configured port speed.
2004/07/28-17:04:54, [FABR-1001], 4,, WARNING, switch, port 4, ELP rejected by
the other switch
2004/07/28-17:05:06, [FW-1050], 5,, WARNING, switch, Sfp Supply Voltage 0, is
below low boundary(High=3600, Low=3150). Current value is 0 mV.
switch:admin>
Viewing System Messages One Message at a Time
To display the system message log one message at a time:
1. Log in to the switch as admin.
2. At the command line, enter the errShow command:
switch:admin> errShow
Version: 5.0.1
2004/07/28-17:04:59, [FSSM-1002], 1,, INFO, switch, HA State is in sync
1
Type <CR> to continue, Q<CR> to stop:
2004/07/28-17:04:59, [FSSM-1003], 2,, WARNING, switch, HA State out of sync
Type <CR> to continue, Q<CR> to stop:
2004/07/28-17:04:51, [EM-1055], 3,, WARNING, switch, Media 27: Port media
incompatible
e. Reason: Configured port speed.
Type <CR> to continue, Q<CR> to stop:
Clearing the System Message Log
To clear the system message log for a particular switch instance:
1. Log in to the switch as admin.
2. Use the errClear command to clear all messages from memory.
NOTE
For products that have a single processor, all error log messages are cleared. For products that have
multiple processors, this command only clears the error logs of the processor it is executed from.
Configuring Event Auditing
To configure event auditing:
1. Configure the event classes you wish to audit:
switch:admin> auditcfg --class 1,2,3,4,5
Audit filter is configured.
switch:admin> auditcfg --enable
Audit filter is enabled.
4. Configure up to six syslog servers to receive the audit events that will be generated through
syslog (procedure will vary depending on server type).
5. Configure syslog on the switch to point to the configured servers’ IP addresses.
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
The fields in the error message are described in Table 3.:
TABLE 3System Message Field Description
ExampleVariable NameDescription
2004/07/22-10:12:33 Date and Time
Stamp
[EM-1031]Message Module
and Message
Number
The system time (UTC) when the message was generated on the
switch. The RASLog subsystem supports an internationalized
timestamp format base on the “LOCAL” setting.
The message module and number. These values uniquely identify
each message in the Fabric OS and reference the cause and
actions recommended in this manual. Note that not all message
numbers are used; there can be gaps in the numeric message
sequence.
8Fabric OS Message Reference
53-1000600-02
Reading a RAS System Message
TABLE 3System Message Field Description (Continued)
ExampleVariable NameDescription
4Sequence NumberThe error message position in the log. When a new message is
added to the log, this number is incremented by 1. When this
message reaches the last position in the error log and becomes
the oldest message in the log, it is deleted when a new message is
added.
The message sequence number starts at 1 after a
firmwareDownload and will increase up to a value of
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.
<NULL>
(blank)
ERRORSeverity LevelThe severity of the error:
switchnameSwitch name or
Slot 7 ejector not
closed
Audit and/or
FFDC Flags
chassis name,
depending on the
action; for example,
high-availability
(HA) messages
typically show the
chassis name, and
login failures show
the logical switch
name.
Error DescriptionA text string explaining the error encountered and providing
For most messages, this field contains a space character (null
value) indicating that the message is neither an AUDIT or FFDC
message. Messages may contain the following values:
AUDIT indicates that this message is for a security issue.
FFDC indicates that additional first failure data capture
information has also been generated for this event.
AUDIT:FFDC indicates that the message is for a security issue and
additional FFDC information has been generated.
1 = Critical
2 = Error
3 = Warning
4 = Info
The defined switch name or the chassis name of the switch. This
value is truncated if it exceeds 16 characters in length. Run either
the chassisName command to name the chassis or the
switchName command to rename the logical switch.
parameters supplied by the software at runtime.
1
Audit Event Messages
Compared to RASLog error messages, messages flagged as AUDIT provide additional user and
system-related information of interest for post event auditing and problem determination.
The fields in the error message are described in Table 4.
TABLE 4Audit Message Field Description
ExampleVariable NameDescription
AUDITAudit flagIdentifies the message as an Audit message.
2005/12/10-09:54:03Date and Time StampThe system time (UTC) when the message was
[SEC-1000]Message Module and
WARNINGSeverity LevelThe severity of the error:
SECURITYEvent ClassThe event class:
JohnSmithUser IDThe user ID.
rootRoleThe role of the user ID.
192.168.132.10IP AddressThe IP address.
TelnetInterfaceThe interface being used.
CLIApplication NameThe application name being used on the interface.
Domain AAdmin DomainThe Admin Domain, if there is one.
switchnameSwitch name or chassis
, , NullReserved for future use.
Slot 7 ejector not
closed
generated on the switch. The RASLog subsystem will
support an internationalized timestamp format base
on the “LOCAL” setting.
The message module and number. These values
Message Number
name, depending on
the action; for example,
HA messages typically
show the chassis name
and login failures show
the logical switch
name.
Error DescriptionA text string explaining the error encountered and
uniquely identify each message in the Fabric OS and
reference the cause and actions recommended in this
manual. Note that not all message numbers are used;
there can be gaps in the numeric message sequence.
1 = Critical
2 = Error
3 = Warning
4 = Info
Zone
Security
Configuration
Firmware
Fabric
The defined switch name or the chassis name of the
switch. This value is truncated if it is over 16
characters in length. Run either the chassisName
command to name the chassis or the switchName
command to rename the logical switch.
providing parameters supplied by the software at
runtime.
10Fabric OS Message Reference
53-1000600-02
Responding to a System Message
1
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.
System messages have the following severity levels.
1 = CRITICALCritical-level messages indicate that the software has detected serious problems that will
cause a partial or complete failure of a subsystem if not corrected immediately; for example, a
power supply failure or rise in temperature must receive immediate attention.
2 = ERRORError-level messages represent an error condition that does not impact overall system
functionality significantly. For example, error-level messages might indicate time-outs on
certain operations, failures of certain operations after retries, invalid parameters, or failure to
perform a requested operation.
3 = WARNINGWarning-level messages highlight a current operating condition that should be checked or it
might lead to a failure in the future. For example, a power supply failure in a redundant system
relays a warning that the system is no longer operating in redundant mode unless the failed
power supply is replaced or fixed.
4 = INFOInfo-level messages report the current non-error status of the system components: for
example, detecting online and offline status of a fabric port.
Responding to a System Message
This section provides procedures on gathering information on system messages, including:
Error messages in this manual are arranged alphabetically. To look up an error message, copy
down the module (see Table 5 on page 13) and the error code and compare this with the Table of
Contents to determine the location of the information for that error message.
The following information is provided for each message:
• Module and code name for the error
• Message text
• Probable cause
• Recommended action
• Message severity
Fabric OS Message Reference11
53-1000600-02
Responding to a System Message
1
Gathering Information About the Problem
Common steps and questions to ask yourself when troubleshooting a system message are as
follows:
1. What is the current Fabric OS level?
2. What is the switch hardware version?
3. Is the switch operational?
4. Assess impact and urgency:
-Is the switch down?
-Is it a standalone switch?
-How large is the fabric?
-Is the fabric redundant?
5. Run the errDump command on each logical switch.
6. Run supportFtp (as needed) to set up automatic FTP transfers, and then run the supportSave
command.
7.Document the sequence of events by answering the following questions:
-What happened just prior to the problem?
-Is the problem repeatable?
-If so, what are the steps to produce the problem?
-What configuration was in place when the problem occurred?
8. Did a failover occur?
9. Was security enabled?
10. Was POST enabled?
11. Are serial port (console) logs available?
12. Which CP was master? (only applicable to the Brocade DCX, 12000, 24000, or 48000)
13. What and when were the last actions or changes made to the system?
Support
Fabric OS creates a number of files that can help support personnel troubleshoot and diagnose a
problem. This section describes those files and how to access and/or save the information for
support personnel.
Panic Dump and Core Dump Files
The Fabric OS creates panic dump files and core files when there are problems in the Fabric OS
kernel. 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 supportSave command.
12Fabric OS Message Reference
53-1000600-02
System Module Descriptions
The software watchdog process (SWD) is responsible for monitoring daemons critical to the
function of a healthy switch. The SWD holds a list of critical daemons that ping the SWD periodically
at a predetermined interval defined for each daemon. The ping interval is set at 133 seconds, with
the exception of the Fabric Watch daemon and the IP storage demon, which ping the SWD every
333 seconds. (For a complete listing of daemons, see the KSWD entry in Tab le 5.)
If a daemon fails to ping the SWD within the defined interval, or if the daemon terminates
unexpectedly, then the SWD dumps information to the panic dump files, which helps to diagnose
the root cause of the unexpected failure.
Run the pdShow command to view these files or the supportSave command to send them to a host
workstation using FTP. The panic dump files and core files are intended for support personnel use
only.
1
Trace Dumps
The Fabric OS produces trace dumps when problems are encountered within Fabric OS modules.
The Fabric OS trace dump files are intended for support personnel use only. You can use the
supportSave or supportFTP commands to collect trace dump files to a specified remote location to
provide to support when requested.
supportSave Command
The supportSave command can be used to send the output of the system messages (RASLog), the
trace files, and the output of the supportShow command to an off-switch storage location through
FTP. Prior to running the supportSave command, you can optionally set up the FTP parameters
using the supportFtp command. The supportShow command runs a large number of dump and
show commands to provide a global output of the status of the switch. Refer to the Fabric OS Command Reference for more information on these commands.
System Module Descriptions
Tab le 5 provides a summary of the system modules for which messages are documented in this
reference guide; the system modules are listed alphabetically by name.
TABLE 5System Module Descriptions
System
Module
AGAccess Gateway allows multiple hosts (or HBAs) to access the fabric using fewer physical ports.
AUTHAuthentication error messages indicate problems with the authentication module of the Fabric OS.
BKSWMessages generated by the Blade Fabric OS kernel software watch dog module.
BLBlade error messages are a result of faulty hardware, transient out-of-memory conditions, application
BLLBloom is the name of the application specific integrated circuit (ASIC) used as the building block for
Description
Access Gateway mode transforms the Brocade 200E as well as embedded switches into a device
management tool that is compatible with different types of fabrics, including Brocade-, Cisco-, and
McDATA-based fabrics.
specific integrated circuit (ASIC) errors, or inconsistencies in the software state between a blade and
the EM (environment monitor) module.
third-generation hardware platforms.
Fabric OS Message Reference13
53-1000600-02
System Module Descriptions
1
TABLE 5System Module Descriptions (Continued)
System
Description
Module
BMBlade management error messages are a result of autoleveling firmware upgrades performed by the
control processor (CP).
CDRCondor application specific integrated circuit (ASIC) driver error messages.
CERThis is the core edge routing module on the Brocade director platforms.
CONFStatus messages for configUpload and configDownload operations.
EMThe environmental monitor (EM) manages and monitors the various field replaceable units (FRUs),
including the port cards, control processor (CP) blades, blower assemblies, power supplies, and
world-wide name (WWN) cards. EM controls the state of the FRUs during system startup, hot-plug
sequences, and fault recovery.
EM provides access to and monitors the sensor and status data from the FRUs and maintains the
integrity of the system using the environmental and power policies. EM reflects system status by way
of CLI commands, system light emitting diodes (LEDs), and status and alarm messages. EM also
manages some component-related data.
EVMDThis is the event management module.
FABRFABRIC refers to a network of Fibre Channel switches. The FABRIC error messages come from the
fabric daemon. The fabric daemon follows the FC-SW-3 standard for the fabric initialization process,
such as determining the E_Ports, assigning unique domain IDs to switches, creating a spanning tree,
throttling the trunking process, and distributing the domain and alias lists to all switches in the fabric.
FABSFabric OS system driver module.
FBCFirmware blade compatibility errors with control processor (CP).
FCIPFibre Channel over IP port configuration messages.
FCMCFibre Channel miscellaneous messages relate to problems with the physical layer used to send Fibre
Channel traffic to and from the switch.
FCPDThe Fibre Channel Protocol daemon is responsible for probing the devices attached to the loop port.
Probing is a process the switch uses to find the devices attached to the loop ports and to update the
Name Server with the information.
FCPHFibre Channel Physical Layer is used to send Fibre Channel traffic to and from the switch.
FCRFibre Channel router-related traffic and activity on the fabric or backend fabric.
FICUThe FICON-CUP daemon handles communication with fibre connectivity (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 process ID (PID), and secure mode on
the fabric.
FKLBFabric OS I/O kernel library module.
FLODFLOD is a part of the fabric shortest path first (FSPF) protocol that handles synchronization of the link
state database (LSDB) and propagation of the link state records (LSRs).
FSPFFabric shortest path first (FSPF) is a link state routing protocol that is used to determine how frames
should be routed. These messages are about protocol errors.
FSSThe Fabric OS state synchronization framework provides facilities by which the active control
processor (CP) can synchronize with the standby CP, enabling the standby CP to take control of the
switch nondisruptively during failures and software upgrades. These facilities include version
negotiation, state information transfer, and internal synchronization functions, enabling the transition
from standby to active operation.
FSS is defined both as a component and a service. A component is a module in the Fabric OS,
implementing a related set of functionality. A service is a collection of components grouped together
to achieve a modular software architecture.
14Fabric OS Message Reference
53-1000600-02
System Module Descriptions
TABLE 5System Module Descriptions (Continued)
System
Module
FSSMThe Fabric OS state synchronization management module is defined both as a component and a
FWFW is the Fabric Watch module. This module monitors thresholds for many switch subsystems: for
HAMHAM is a user space daemon responsible for high availability management.
HAMKThis is the kernel module for the high availability management (HAM) daemon.
HILHardware independent layer.
HLOHLO is a part of the fabric shortest path first (FSPF) protocol that handles the HELLO protocol between
HMONHealth monitor.
HTTPHTTP error messages.
IBDThis raslog generates messages related to port restart failure.
IBPDIBPD stands for iSCSI gateway daemon on a blade processor (BP). It manages iSCSI initiator access
ICPDICPD stands for iSCSI gateway daemon on a control processor (CP). It manages iSCSI configurations
IPADSystem messages generated by the IP admin demon.
IPSFibre Channel over IP license, tunneling, and port-related messages.
ISCSThe ISCS module is the FabOS component that performs system-level control of the iSCSI Gateways.
ISNSISNS server and client status messages.
Description
service. A component is a module in Fabric OS implementing a related set of functionality. A service is
a collection of components grouped together to achieve a modular software architecture.
example, temperature, voltage, fan speed, and switch status. Any changes that cross a specified
threshold are reported to the system message log.
adjacent switches. The HELLO protocol is used to establish connectivity with a neighbor switch, to
establish the identity of the neighbor switch, and to exchange FSPF parameters and capabilities.
control, session authentication, and session/connection statistics.
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. It keeps track iSCSI VT status and updates VT status to BP.
Its functions include: initialization, message delivery from iSCSI protocol clients, system error
monitoring, and fault recovery.
1
Fabric OS Message Reference15
53-1000600-02
System Module Descriptions
1
TABLE 5System Module Descriptions (Continued)
System
Module
KSWDThe kernel software watchdog (KSWD) watches daemons for unexpected terminations and “hang”
Description
conditions and informs the HAM module to take corrective actions such as failover or reboot.
The following daemons are monitored by KSWD:
• Access Gateway daemon (agd)
• Alias Server (asd)
• ARR daemon (arrd)
• Authentication daemon (authd)
• Blade Manager (bmd)
• Common Access Layer (cald)
• Diagnostics daemon (diagd)
• Environment Monitor (emd)
• EVM daemon (evmd)
• Exchange Service Support daemon (essd)
• FA-API rpc daemon (rpcd)
• Fabric daemon (fabricd)
• Fabric Watch daemon (fwd)
• FCPD daemon (fcpd)
• FDMI daemon (fdmid)
• FICON CUP daemon (ficud)
• FSPF daemon (fspfd)
• Inter-fabric Routing daemon (iswitchd)
• IP Storage Daemon (ipsd)
• iSCSI daemon on CP (icpd)
• iSNS client daemon on CP (isnscd)
• Management Server daemon (msd)
• Name Server Daemon (nsd)
• PDM daemon (pdmd)
• PS daemon (psd)
• RASLOG daemon (raslogd)
• RSC daemon (rcsd)
• SAS CP Daemon (scpd)
• Security daemon (secd)
• SNMP daemon (snmpd)
• Time Service daemon (tsd)
• TRACE daemon (traced)
• Track Changes daemon (trackd)
• Web tools daemon (webd)
KTRCKernel RAS trace module.
LOGRASLog subsystem.
LSDBThe 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.
MFICMS-FICON messages relate to Fibre Connection (FICON) installations. Fibre Connection control unit
port (FICON-CUP) messages are displayed under the FICU module.
MPTHMulticast path uses the shortest path first (SPF) algorithm to dynamically compute a broadcast tree.
MQMessage queues are used for interprocess communication. Message queues allow many messages,
each of variable length, to be queued. Any process or interrupt service routine (ISR) can write
messages to a message queue. Any process can read messages from a message queue.
16Fabric OS Message Reference
53-1000600-02
System Module Descriptions
TABLE 5System Module Descriptions (Continued)
System
Module
MSThe Management Service enables the user to obtain information about the Fibre Channel fabric
NBFSNBFSM is a part of the fabric shortest path first (FSPF) protocol that handles a neighboring or
NSIndicates problems with the simple name server module.
PDMParity data manager is a user space daemon responsible for the replication of persistent
PDTRThese messages indicate panic dump trace files have been created.
PLATThis message indicates hardware problems.
PORTPORT error messages refer to the front-end user ports on the switch. Front-end user ports are directly
PSThe performance server daemon measures the amount of traffic between end points or traffic with
PSWPThe portswap feature and associated commands generate these error messages.
RASFirst failure data capture (FFDC), informational message when FFDC events are logged to the FFDC
RCSThe reliable commit service daemon generates log entries when it receives a request from the zoning,
RPCDThe remote procedure call daemon (RPCD) is used by Fabric Access for API-related tasks.
RTWRThe reliable transport write and read daemon helps deliver data messages either to specific switches
SCNThe internal state change notification daemon is used for state change notifications from the kernel
SECThe security daemon generates security errors, warnings, or information during security-related data
Description
topology and attributes by providing a single management access point. MS provides for both
monitoring and control of the following areas:
Fabric Configuration Server. Provides for the configuration management of the fabric.
Unzoned Name Server. Provides access to Name Server information that is not subject to zone
constraints.
Fabric Zone Server. Provides access to and control of zone information.
adjacent switch’s finite state machine (FSM).
Input to the FSM changes the local switch from one state to another, based on specific events. For
example, when two switches are connected to each other using an ISL (interswitch link) cable, they
are in the Init state. After both switches receive HELLO messages, they move to the Database
Exchange state, and so on.
NBFSM states are Down (0), Init (1), Database Exchange (2), Database Acknowledge Wait (3),
Database Wait (4), and Full (5).
configuration files from the primary partition to the secondary partition and from the active CP blade
to the standby CP blade.
accessible by users to connect end devices or connect to other switches.
particular frame formats, such as SCSI frames, IP frames, and customer-defined frames.
log and size/roll over warning.
security, or management server for passing data messages to switches in the fabric. RCS then
requests reliable transport write and read (RTWR) to deliver the message. RCS also acts as a
gatekeeper, limiting the number of outstanding requests for the Zoning, Security, or Management
Server modules.
in the fabric or to all of the switches in the fabric. For example, if some of the switches are not
reachable or are offline, RTWR returns an “unreachable” message to the caller, allowing the caller to
take the appropriate action. If a switch is not responding, RTWR retries 100 times.
to the daemons within Fabric OS
management or fabric merge operations. Administrators should watch for these messages, to
distinguish between internal switch and fabric operation errors, and external attack.
1
Fabric OS Message Reference17
53-1000600-02
System Module Descriptions
1
TABLE 5System Module Descriptions (Continued)
System
Description
Module
SNMPSimple Network Management Protocol is a universally supported low-level protocol that allows simple
get, get next, and set requests to go to the switch (acting as an SNMP agent). It also allows the switch
to send traps to the defined and configured management station. Brocade switches support six
management entities that can be configured to receive these traps.
SSThe supportSave command generates these error messages if problems are encountered.
SULBThe software upgrade library provides firmwareDownload command capability, which enables
firmware upgrades to both CP blades with a single command, as well as nondisruptive code load to all
4.x switches. These messages might display if there are any problems during the firmwareDownload
procedure. Most messages are informational only and are generated even during successful firmware
download. For additional information, refer to the Fabric OS Administrator’s Guide.
SWCHThese messages are generated by the switch driver module that manages a Fibre Channel switch
instance.
SYSCSystem controller is a daemon that starts up and shuts down all Fabric OS modules in the proper
sequence.
SYSMGeneral system messages.
TRCERAS TRACE error messages.
TRCKThe track change feature tracks the following events:
Turning on or off the track change feature
CONFIG_CHANGE
LOGIN
LOGOUT
FAILED_LOGIN
If any of these events occur, a message is sent to the system message log. Additionally, if the SNMP
trap option is enabled, an SNMP trap is also sent.
For information on configuring the track change feature, refer to the Fabric OS Command Reference
or the Fabric OS Administrator’s Guide.
TSTime Service provides fabric time-synchronization by synchronizing all clocks in the fabric to the clock
time on the principal switch.
UCSTUCAST is a part of the fabric shortest path first (FSPF) protocol that manages the Unicast routing
table.
UPTHUPATH is a part of the FSPF protocol that uses the SPF algorithm to dynamically compute a Unicast
tree.
WEBDIndicates problems with the Web Tools module.
ZOLBIndicates problems with the zone library module.
ZONEThe zone module messages indicate any problems associated with the zoning features, including
commands associated with aliases, zones, and configurations.
NOTE
Any reference seen in a system message to slot 0 is a reference to the blade within the switch
platform, for example: Brocade DCC contains FC8-48, FC9-32, and FC8-16 blades.
18Fabric OS Message Reference
53-1000600-02
Section
RASLog Messages
This section provides the RASLog messages, including:
Message<timestamp>, [AG-1001], <sequence-number>,, ERROR, <system-name>, N_Port ID
virtualization (NPIV) is not supported by fabric port connected to port <port>.
Probable CauseN_Port ID virtualization (NPIV) capability is not supported by the fabric port to which the Access
Gateway is connected.
Recommended
Action
• On switches running Fabric OS 6.0 or earlier versions, run the portCfgNpivPort command to
enable NPIV capability on the port connected to the Access Gateway. Refer to the Fabric OS Command Reference manual for more information on this command.
• Some blades and ports in a switch may not support NPIV. NPIV functionality cannot be enabled
on such ports and they will not respond to NPIV requests. Refer to the Access Gateway Administrator Guide, Appendix B for specific AG compatibility requirements.
• On non-Brocade switches, refer to the manufacture's documentation to determine whether the
switch supports NPIV and how to enable NPIV on these types of switches.
2
SeverityERROR
AG-1002
Message<timestamp>, [AG-1002], <sequence-number>,, WARNING, <system-name>, Unable to
find alternate N_Port during failover for N_Port
Probable CauseNo other N_Port is configured or the fabric was unstable during failover.
Recommended
Action
SeverityWARNING
Please check whether or not an alternate N_Port is configured.
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.
<port>.
AG-1003
Message<timestamp>, [AG-1003], <sequence-number>,, WARNING, <system-name>, Unable to
failover N_Port <port>. Failover across different fabrics is not supported.
Probable CauseFailover across N_Ports connected to different fabrics is not supported.
Recommended
Action
Please configure two or more N_Ports to connect to the same fabric; then execute
ag --failoverenable to enable failover on these N_Ports.
response to fabric login (FLOGI) request from the fabric for N_Port <port>.
Probable CauseIndicates that the fabric sent an invalid response to the FLOGI Extended Link Service (ELS) for the
specified N_Port.
Recommended
Action
SeverityERROR
Please check the configuration of the fabric switch.
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.
Probable CauseIndicates that the N_Port connected to the fabric switch is not online. The specified N_Port has
been disabled.
24Fabric OS Message Reference
<port> connected to the fabric.
53-1000600-02
AG-1008
2
Recommended
Action
SeverityWARNING
Check the connectivity between the Access Gateway N_Port and the fabric switch port.
AG-1008
Message<timestamp>, [AG-1008], <sequence-number>,, WARNING, <system-name>, Invalid port
login (PLOGI) response from the fabric on the N_Port <port>.
Probable CauseIndicates that the fabric switch management server did not accept the N_Port Login (PLOGI)
request sent by the Access Gateway.
Recommended
Action
SeverityWARNING
Please check the configuration of the fabric switch connected to the Access Gateway.
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.
Probable CauseFailure sending Fabric Login (FLOGI) request from the Access Gateway to the fabric switch.
Recommended
Action
SeverityWARNING
Please check the configuration of the fabric switch connected to the Access Gateway.
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.
Probable CauseFailure sending N_Port Login (PLOGI) request from the Access Gateway to the fabric switch.
Recommended
Action
SeverityWARNING
Please check the configuration of the fabric switch connected to the Access Gateway.
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.
Probable CauseIndicates failure of sending the discover F_Port service parameter request from the Access
Gateway to the fabric switch.
Recommended
Action
SeverityWARNING
Please check the configuration of the fabric switch connected to the Access Gateway.
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.
Probable CauseFailure sending N_Port logout request from the Access Gateway to the fabric switch.
Recommended
Action
SeverityWARNING
Please check the configuration of the fabric switch connected to the Access Gateway.
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.
Probable CauseIndicates that the specified N_Port is failing over to other N_Port(s) connected to the same fabric.
Recommended
Action
SeverityINFO
Run the ag --mapshow command to display updated F_Port to N_Port mapping.
AG-1014
Message<timestamp>, [AG-1014], <sequence-number>,, INFO, <system-name>, Failing back
F_Ports mapped to N_Port <port>.
Probable CauseIndicates that the specified N_Port is failing back F_Ports mapped to the specified N_Port.
Recommended
Action
26Fabric OS Message Reference
Run the ag --mapshow command to display updated F_Port to N_Port mapping.
53-1000600-02
SeverityINFO
AG-1015
Message<timestamp>, [AG-1015], <sequence-number>,, WARNING, <system-name>, Unable to
find online N_Ports to connect to the fabric.
Probable CauseEither no other N_Port is configured or all N_Ports are currently offline.
AG-1015
2
Recommended
Action
SeverityWARNING
Please check whether or not any other N_Port is configured.
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.
AG-1016
Message<timestamp>, [AG-1016], <sequence-number>,, INFO, <system-name>, Failing over
F_Ports mapped to N_Port <port> to other N_Port(s).
Probable CauseIndicates that the specified N_Port has failed to come online. All F_Port(s) mapped to this N_Port
are being failed over to other active N_Port(s).
Recommended
Action
SeverityINFO
Run the ag --mapshow command to display updated F_Port to N_Port mapping.
AG-1017
Message<timestamp>, [AG-1017], <sequence-number>,, WARNING, <system-name>, No N_Port(s)
are currently Online.
Probable CauseIndicates that no N_Port(s) are currently configured in the system or all configured N_Port(s) have
failed to come online.
Recommended
Action
SeverityWARNING
Run switchShow to display the status of all ports in the system. Run portCfgShow to display a list of
ports currently configured as N_Port(s).
AG-1018
Message<timestamp>, [AG-1018], <sequence-number>,, ERROR, <system-name>, Host port
should not be connected to port <port>, which is configured as N_Port.
Probable CauseIndicates that Initiator/Target is erroneously connected to a port configured for N_Port operation.
Fabric OS Message Reference27
53-1000600-02
2
AG-1019
Recommended
Action
SeverityERROR
Run switchShow to display the status of all ports in the system. Run portCfgShow to display a list of
ports currently configured as N_Port(s). Ensure that the host is connected to an F_port.
AG-1019
Message<timestamp>, [AG-1019], <sequence-number>,, WARNING, <system-name>, Unable to
failover N_Port <port>. No other N Port in port group:<pgid> is online.
Probable CauseFailover across port groups is not supported.
Recommended
Action
SeverityWARNING
Please check whether or not an alternate N_Port is configured in this port group.
AG-1020
Message<timestamp>, [AG-1020], <sequence-number>,, INFO, <system-name>, F_Ports to
N_Ports route/mapping has been changed.
Probable CauseIndicates that F_Ports to N_Ports mapping has been changed because the switch has come online
or some new N_Port/F_Port has come online.
Recommended
Action
SeverityINFO
Run the ag --mapshow command to display the updated F_Port to N_Port mapping.
AG-1021
Message<timestamp>, [AG-1021], <sequence-number>,, WARNING, <system-name>, Unable to do
Preferred-Failover of F_Port <port>. Failover across different fabric is not
supported.
Probable CauseFailover across N_Ports connected to different fabrics is not supported.
Recommended
Action
SeverityWARNING
Please change the preferred N_Port settings for this F_Port using ag --prefset.
Choose the preferred N_Port such that it is in the same fabric as the primary N_Port of this F_Port.
Use ag --show to check the fabric connectivity of N_Ports.
Probable CauseIndicates that the specified N_Port is failing back F_Ports, which are failed over to some other
N_Port.
Recommended
Action
SeverityINFO
Run the ag --mapshow command to display the updated F_Port to N_Port mapping.
AG-1025
Message<timestamp>, [AG-1025], <sequence-number>,, ERROR, <system-name>, Port group of
Slave N_Port <port> is different than its Master N_Port <m_port>.
Probable CauseIndicates that port group of Master and Slave N_Ports are different while the Trunk Area assigned
to the attached F_Ports on edge switch is the same.
Recommended
Action
SeverityERROR
Please run the porttrunkarea --show command on the attached switch to display that the TA is
assigned to all ports in the system and run porttrunkarea --enable to reconfigure the TA.
Fabric OS Message Reference29
53-1000600-02
AG-1026
2
AG-1026
Message<timestamp>, [AG-1026], <sequence-number>,, WARNING, <system-name>, Unable to
handle the login request on port <port> due to insufficient resources.
Probable CauseInsufficient resources.
Recommended
Action
SeverityWARNING
Run configure CLI on AG switch and increase the number of allowed logins on this port.
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.
AG-1027
Message<timestamp>, [AG-1027], <sequence-number>,, WARNING, <system-name>, Unable to
handle this login request on port <port> because NPIV capability is not enabled on
this port.
Probable CauseNPIV not enabled.
Recommended
Action
SeverityWARNING
Run portcfgnpivport CLI on AG switch and enable the NPIV capability on this port.
AG-1028
Message<timestamp>, [AG-1028], <sequence-number>,, WARNING, <system-name>, Device with
Port WWN <port_name> tried to perform fabric login through port <fport>, without
having access permission.
Probable CauseDevice does not have access to login as per ADS policy set by user for that port.
Recommended
Action
SeverityWARNING
30Fabric OS Message Reference
Add the device in to the ADS allow list for that port using ag --adsadd command.
Probable CauseIndicates an authentication file corruption.
Recommended
Action
SeverityERROR
Run the firmwareDownload command to reinstall the firmware.
Run supportFtp (as needed) to set up automatic FTP transfers; then run the supportSave command
and contact your switch service provider.
AUTH-1006
Message<timestamp>, [AUTH-1006], <sequence-number>,, WARNING, <system-name>, Failed to
open authentication configuration file.
<error code>.
Probable CauseIndicates an internal problem with the Secure Fabric OS.
Recommended
Action
SeverityWARNING
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable
and switchEnable commands.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
AUTH-1007
Message<timestamp>, [AUTH-1007], <sequence-number>,, ERROR, <system-name>, The proposed
authentication protocol(s) are not supported: port
Probable CauseIndicates that the proposed authentication protocol type or types are not supported by the local
specified port.
32Fabric OS Message Reference
<port number>.
53-1000600-02
AUTH-1008
3
Recommended
Action
SeverityERROR
Run the authUtil command to make sure the local switch supports the specified protocols: Fibre
channel authentication protocol (FCAP) or Diffie Hellman - challenge handshake authentication
protocol (DH-CHAP).
AUTH-1008
Message<timestamp>, [AUTH-1008], <sequence-number>,, ERROR, <system-name>, No security
license, operation failed.
Probable CauseIndicates that the switch does not have a security license.
Recommended
Action
SeverityERROR
Verify that the security license is installed using the licenseShow command. If necessary, reinstall
the license using the licenseAdd command.
AUTH-1010
Message<timestamp>, [AUTH-1010], <sequence-number>,, ERROR, <system-name>, Failed to
Probable CauseIndicates an internal problem with the Secure Fabric OS.
Recommended
Action
SeverityERROR
Reboot or power cycle the switch.
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.
AUTH-1011
Message<timestamp>, [AUTH-1011], <sequence-number>,, WARNING, <system-name>, Failed to
register for failover operation: switch <switch number> error <error code>.
Probable CauseIndicates an internal problem with the Secure Fabric OS.
Recommended
Action
SeverityWARNING
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable
and switchEnable commands.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
Probable CauseIndicates that the system is running low on resources when receiving an authentication request.
Recommended
Action
SeverityWARNING
Usually this problem is transient. The authentication might fail.
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable
and switchEnable commands.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
Probable CauseIndicates an internal problem with the Secure Fabric OS.
Recommended
Action
SeverityERROR
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable
and switchEnable commands.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
value to start HBA authentication port: <port number>, <pid>.
34Fabric OS Message Reference
53-1000600-02
Probable CauseThis may relate to an internal failure.
AUTH-1017
3
Recommended
Action
SeverityERROR
Copy the message, collect switch information using the supportShow command, and contact your
switch service provider.
AUTH-1017
Message<timestamp>, [AUTH-1017], <sequence-number>,, ERROR, <system-name>, Invalid value
to start authentication request: port <port number>, operation code <operation
code>.
Probable CauseIndicates an internal problem with the Secure Fabric OS.
Recommended
Action
SeverityERROR
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable
and switchEnable commands.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
AUTH-1018
Message<timestamp>, [AUTH-1018], <sequence-number>,, ERROR, <system-name>, Invalid value
to check protocol type: port
Probable CauseIndicates an internal problem with the Secure Fabric OS.
Recommended
Action
SeverityERROR
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable
and switchEnable commands.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
<port number>.
AUTH-1020
Message<timestamp>, [AUTH-1020], <sequence-number>,, INFO, <system-name>, Failed to
create timer for authentication: port
Probable CauseIndicates that an authentication message's timer was not created.
Recommended
Action
Usually this problem is transient. The authentication might fail.
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable
and switchEnable commands.
<port number>.
Fabric OS Message Reference35
53-1000600-02
AUTH-1022
3
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.
SeverityINFO
AUTH-1022
Message<timestamp>, [AUTH-1022], <sequence-number>,, ERROR, <system-name>, Failed to
extract <data type> from <message> payload: port <port number>.
Probable CauseIndicates that the authentication process failed to extract a particular value from the receiving
payload.
Recommended
Action
SeverityERROR
Usually this problem is transient. The authentication might fail.
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable
and switchEnable commands.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
AUTH-1023
Message<timestamp>, [AUTH-1023], <sequence-number>,, ERROR, <system-name>, Failed to
<operation type> during <authentication phase>: port <port number>.
Probable CauseIndicates an authentication operation failed for a certain authentication phase.
Operation type varies depending on authentication type:
• Some operations for switch link authentication protocol (SLAP): certificate retrieve, certificate
verification signature verification, or nonce signing.
• Some operations for fibre channel authentication protocol (FCAP): certificate retrieve,
certificate verification, signature verification, or nonce singing.
• Some operations for Diffie Hellman - challenge handshake authentication Protocol (DH-CHAP).
response calculation, challenge generation, or secret retrieve.
The authentication phase specifies which phase of a particular authentication protocol failed.
A nonce is a single-use, usually random value used in authentication protocols to prevent replay
attacks.
Recommended
Action
36Fabric OS Message Reference
The error might indicate that an invalid entity tried to connect to the switch. Check the connection
port for possible unauthorized access attack.
It might indicate that the public key infrastructure (PKI) object for SLAP or FCAP or secret value for
DH-CHAP on the local entity is not set up properly. Reinstall all PKI objects or reset the secret value
for DH-CHAP properly.
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.
53-1000600-02
AUTH-1025
SeverityERROR
AUTH-1025
Message<timestamp>, [AUTH-1025], <sequence-number>,, ERROR, <system-name>, Failed to get
<data type> during <authentication phase>: port <port number>.
Probable CauseIndicates that the authentication process failed to get the expected information during the
specified authentication phase.
3
Recommended
Action
SeverityERROR
Usually this problem is transient. The authentication might fail.
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable
and switchEnable commands.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
AUTH-1026
Message<timestamp>, [AUTH-1026], <sequence-number>,, WARNING, <system-name>, Failed to
get <Device information> during negotiation phase: port <port number>.
Probable CauseIndicates that the authentication failed to get device or host bus adaptor (HBA) information due to
an internal failure.
Recommended
Action
Usually this problem is transient. If the authentication failed, retry the login.
Reinitialize authentication using the switchDisable and switchEnable commands or the portDisable
and portEnable commands.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
SeverityWARNING
AUTH-1027
Message<timestamp>, [AUTH-1027], <sequence-number>,, ERROR, <system-name>, Failed to
select <authentication value> during <authentication phase>: value <value> port
<port number>.
Probable CauseIndicates that the authentication process failed to select an authentication value (that is, DH
Group, hash value, or protocol type) from a receiving payload for the specified authentication phase. This indicates that the local switch does not support the specified authentication value.
Recommended
Action
Fabric OS Message Reference37
53-1000600-02
Check the authentication configuration and reset the supported value if needed using the authUtil
command.
AUTH-1028
3
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable
and switchEnable commands.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
SeverityERROR
AUTH-1028
Message<timestamp>, [AUTH-1028], <sequence-number>,, ERROR, <system-name>, Failed to
allocate <data type> for <operation phase>: port <port number>.
Probable CauseIndicates that the authentication process failed because the system is low on memory.
Data type is the payload or structure that failed to get memory. Operation phase specifies which
operation of a particular authentication phase failed.
Recommended
Action
SeverityERROR
Usually this problem is transient. The authentication might fail.
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable
and switchEnable commands.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
AUTH-1029
Message<timestamp>, [AUTH-1029], <sequence-number>,, ERROR, <system-name>, Failed to get
<data type> for <message phase> message: port <port number>, retval <error code>.
Probable CauseIndicates that the authentication process failed to get a particular authentication value at certain
phase.
Data type is the payload or structure that failed to get memory.
Recommended
Action
Usually this problem is transient. The authentication might fail.
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable
and switchEnable commands.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
message code for <message phase> message: port <port number>.
38Fabric OS Message Reference
53-1000600-02
AUTH-1031
Probable CauseIndicates the receiving payload does not have valid message code for a particular authentication
phase.
3
Recommended
Action
SeverityERROR
Usually this problem is transient. The authentication might fail.
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable
and switchEnable commands.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
AUTH-1031
Message<timestamp>, [AUTH-1031], <sequence-number>,, ERROR, <system-name>, Failed to
retrieve secret value: port
Probable CauseIndicates that the secret value was not set properly for the authenticated entity.
Recommended
Action
SeverityERROR
Reset the secret value by using secAuthSecret command.
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable
and switchEnable commands.
<port number>.
AUTH-1032
Message<timestamp>, [AUTH-1032], <sequence-number>,, ERROR, <system-name>, Failed to
generate <data type> for <message payload> payload: length <data length>, error
code <error code>, port <port number>.
Probable CauseIndicates that the authentication process failed to generate specific data (that is, challenge, nonce,
or response data) for an authentication payload. This usually relates to internal failure.
A nonce is a single-use, usually random value used in authentication protocols to prevent replay
attacks.
Recommended
Action
SeverityERROR
Usually this problem is transient. The authentication might fail.
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable
and switchEnable commands.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
AUTH-1033
Message<timestamp>, [AUTH-1033], <sequence-number>,, ERROR, <system-name>, Disable port
<port number> due to unauthorized switch <switch WWN value>.
Fabric OS Message Reference39
53-1000600-02
AUTH-1034
3
Probable CauseIndicates that an entity was not configured in the switch connection control (SCC) policy and tried
to connect to the port.
Recommended
Action
SeverityERROR
Add the entity's world-wide name (WWN) to the SCC policy and reinitialize authentication by using
the portDisable and portEnable commands or the switchDisable and switchEnable commands.
AUTH-1034
Message<timestamp>, [AUTH-1034], <sequence-number>,, ERROR, <system-name>, Failed to
validate name <entity name> in <authentication message>: port <port number>.
Probable CauseIndicates that the specified entity name in the payload is not in the correct format.
Recommended
Action
SeverityERROR
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable
and switchEnable commands.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
type> length in <message phase> message: length <data length>, port <port number>.
Probable CauseIndicates that a particular data field in the authentication message has an invalid length field. This
error usually relates to internal failure.
Recommended
Action
SeverityERROR
Usually this problem is transient. The authentication might fail.
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable
and switchEnable commands.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
AUTH-1036
Message<timestamp>, [AUTH-1036], <sequence-number>,, ERROR, <system-name>, Invalid state
<state value> for <authentication phase>: port <port number>.
Probable CauseIndicates that the switch received an unexpected authentication message.
Recommended
Action
Usually this problem is transient. The authentication might fail.
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable
and switchEnable commands.
40Fabric OS Message Reference
53-1000600-02
AUTH-1037
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
SeverityERROR
AUTH-1037
Message<timestamp>, [AUTH-1037], <sequence-number>,, ERROR, <system-name>, Failed to
<operation type> response for <authentication message>: init_len <data length>,
resp_len <data length>, port <port number>.
Probable CauseIndicates that a Diffie Hellman - challenge handshake authentication protocol (DH-CHAP)
authentication operation failed on the specified port due to mismatched response values between
two entities.
3
Recommended
Action
SeverityERROR
The error might indicate that an invalid entity tried to connect to the switch. Check the connection
port for a possible security attack.
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable
and switchEnable commands.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
AUTH-1038
Message<timestamp>, [AUTH-1038], <sequence-number>,, ERROR, <system-name>, Failed to
retrieve certificate during <authentication phase>: port <port number>.
Probable CauseIndicates that the public key infrastructure (PKI) certificate is not installed properly.
Recommended
Action
Reinstall the PKI certificate, using the pkiCreate command.
Reinitialize authentication using the portDisable and portEnable commands or the switchDisable
and switchEnable commands.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
switch has conflicting authentication policy: Port <Port Number> disabled.
Probable CauseIndicates that the neighboring switch has a conflicting authentication policy enabled. The_E-Port
has been disabled, because the neighboring switch rejected the authentication negotiation, and
the local switch has a strict switch authentication policy.
Fabric OS Message Reference41
53-1000600-02
3
AUTH-1040
Recommended
Action
SeverityERROR
Correct the switch policy configuration on either of the switches using the authUtil command, and
then enable the port using the portEnable command.
authentication on port <Port Number>, because switch authentication policy is set
to OFF.
Probable CauseIndicates that the local switch has rejected the authentication because the switch policy is turned
off. If the neighboring switch has a strict (ON) switch policy, the light will go off due to conflicting
configuration settings. Otherwise E_Port will form without authentication.
Recommended
Action
SeverityINFO
If there is no light on the port, correct the switch policy configuration on either of the switches using
the authUtil command, and then enable the port on the neighboring switch using the portEnable
command. If the E_Port formed, no action is required.
AUTH-1041
Message<timestamp>, [AUTH-1041], <sequence-number>,, ERROR, <system-name>, Port <port
number> has been disabled, because an authentication-reject was received with code
'<Reason String>' and explanation '<Explanation String>'.
Probable CauseThe specified port had been disabled, because it received an authentication-reject response from
the connected switch/device. The error might indicate that an invalid entity attempted to connect to
the switch.
Recommended
Action
SeverityERROR
Check the connection port for a possible security attack.
Check the shared secrets using secAuthSecret and reinitialize authentication using the portDisable
and portEnable commands.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
AUTH-1042
Message<timestamp>, [AUTH-1042], <sequence-number>,, ERROR, <system-name>, Port <port
number> has been disabled, because authentication failed with code '<Reason
String>' and explanation '<Explanation String>'.
Probable CauseThe specified port has been disabled, because the connecting switch/device failed to authenticate.
The error might indicate that an invalid entity attempted to connect to the switch.
42Fabric OS Message Reference
53-1000600-02
AUTH-1043
3
Recommended
Action
SeverityERROR
Check the connection port for a possible security attack.
Check the shared secrets using secAuthSecret and reinitialize authentication using the portDisable
and portEnable commands.
If the message persists, run supportFtp (as needed) to set up automatic FTP transfers; then run the
supportSave command and contact your switch service provider.
AUTH-1043
Message<timestamp>, [AUTH-1043], <sequence-number>,, ERROR, <system-name>, Failed to
Probable CauseIndicates that the Kernel mode setting for F_Port authentication failed. Device authentication will
be defaulted to OFF, and switch will not participate in Diffie Hellman - challenge handshake
authentication protocol (DH-CHAP) authentication with devices.
Recommended
Action
SeverityERROR
Try setting the device authentication policy manually using the authUtil command.
Authentication <Reason for disabling the port>. Disabling port <port number>.
Probable CauseIndicates authentication has timed out after multiple retries. The specified port has been disabled
as a result. This problem may be transient due to the system’s central processing unit (CPU) load.
In addition, a defective small form-factor pluggable (SFP) or faulty cable may have caused the
failure.
Recommended
Action
SeverityERROR
Check the SFP and the cable. Then try to enable the port using the portEnable command.
Probable CauseIndicates a warning state within the system.
A critical application error was reported in the watchdog subsystem. This message is used to
convey information that might be of interest to the customer regarding the state of the system.
Refer to the string at the end of the error message for specific information. The switch will reboot
(on single-CP switches) or failover (on dual-CP switches).
The warning message might be any one of the following:
Probable Cause: One of the critical daemons ended unexpectedly.
• <<daemon name> failed to refresh SWD*** Sending SIGABRT to PID <process id number>>
Probable Cause: One of the critical daemons is found to be nonresponsive; sending signal
abort.
4
Recommended
Action
SeverityWARNING
Run the supportSave command to determine if any core files were created. If a core file is found,
run supportFtp to send all core files to a secure server location.
Copy the error message and any core file information, and contact your switch service provider.
Failed: slot <slot number> DISABLED because internal ports were not ONLINE, <list
of internal port number not ONLINE>.
Probable CauseIndicates that the blade initiation failed because one or more of the internal ports were not online.
The blade is faulted.
Recommended
Action
Make sure that the blade is seated correctly. 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.
Note that any reference seen to slot 0 is a reference to the blade within the switch platform,
e.g.,Brocade 7500 and AP7600 contain FR4-18i and FA4-18 blades respectively.
Run the diagPost command to ensure that Power-On Self-Test (POST) is enabled. Refer to the Fabric OS Command Reference for more information on these command.
Fabric OS Message Reference47
53-1000600-02
BL-1003
5
Run the diagPost command to ensure that Power-On Self-Test (POST) is enabled.
Additional blade fault messages precede and follow this error, providing more information. See
other error messages for recommended action.
Probable CauseIndicates a faulty blade in the specified slot number.
<slot number>.
Recommended
Action
SeverityCRITICAL
Make sure that the blade is seated correctly. If the blade is seated correctly, reboot or power cycle
the blade.
Run the systemVerification command to verify that blade does not have hardware problems. Run
the diagPost command to ensure that Power-On Self-Test (POST) is enabled. Refer to the Fabric OS Command Reference for more information on these commands.
Probable CauseIndicates that the specified blade experienced a failure but was not faulted due to a user setting.
Recommended
Action
Reboot or power cycle the blade, using the slotPowerOff and slotPowerOn commands.
Run the systemVerification command to verify that the blade does not have hardware problems.
Run the diagPost command to ensure that Power-On Self-Test (POST) is enabled. Refer to the Fabric OS Command Reference for more information on these commands.