FOR BROCADE AND PARTNER USE ONLY

DIAGNOSTIC GUIDE

Brocade portLogDump Reference Guide

Supporting Fabric OS 8.0.1

53-1004122-01
29 April 2016
 FOR BROCADE AND PARTNER USE ONLY

© 2016, Brocade Communications Systems, Inc. All Rights Reserved.

Brocade, Brocade Assurance, the B-wing symbol, ClearLink, DCX, Fabric OS, HyperEdge, ICX, MLX, MyBrocade, OpenScript, VCS, VDX, Vplane, and
Vyatta are registered trademarks, and Fabric Vision is a trademark of Brocade Communications Systems, Inc., in the United States and/or in other
countries. Other brands, products, or service names mentioned may be trademarks of others.

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. assume no liability or responsibility to any person or entity with respect to the accuracy of this
document or any loss, cost, liability, or damages arising from the information contained herein 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 portLogDump Reference Guide

2 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY

Contents
Preface...........................................................................................................................................................................................................................................................................................7
Document conventions..............................................................................................................................................................................................................................................7
Object Missing...................................................................................................................................................................................................................................................... 7
Command syntax conventions....................................................................................................................................................................................................................7
Notes, cautions, and warnings..................................................................................................................................................................................................................... 7
Brocade resources.......................................................................................................................................................................................................................................................8
Contacting Brocade Technical Support........................................................................................................................................................................................................... 8
Brocade customers........................................................................................................................................................................................................................................... 8
Brocade OEM customers..............................................................................................................................................................................................................................9
Document feedback....................................................................................................................................................................................................................................................9

About This Document.......................................................................................................................................................................................................................................................... 11

Supported hardware and software...................................................................................................................................................................................................................... 11
Brocade Gen 5 (16-Gbps) fixed-port switches...................................................................................................................................................................................11
Brocade Gen 5 (16-Gbps) DCX 8510 Directors................................................................................................................................................................................11
Brocade Gen 6 fixed-port switches..........................................................................................................................................................................................................11
Brocade Gen 6 Directors..............................................................................................................................................................................................................................12
What's new in this document................................................................................................................................................................................................................................12
Changes made for this release .................................................................................................................................................................................................................12

Understanding the Portlogdump Command........................................................................................................................................................................................................ 13

Portlogdump command..........................................................................................................................................................................................................................................13
Reading portlogdump output............................................................................................................................................................................................................................... 13
Time.......................................................................................................................................................................................................................................................................... 14
Task............................................................................................................................................................................................................................................................................14
Event.........................................................................................................................................................................................................................................................................14
Port............................................................................................................................................................................................................................................................................ 14
Cmd...........................................................................................................................................................................................................................................................................14
Args........................................................................................................................................................................................................................................................................... 15
Using and customizing the portlogdump output...................................................................................................................................................................................... 15
Portlogdump-related commands............................................................................................................................................................................................................15
Displaying and customizing the portlogdump output..................................................................................................................................................................16
Locating information by task.................................................................................................................................................................................................................................17
Example outputs for portlogdump........................................................................................................................................................................................................20

Troubleshooting Using the Port Logs......................................................................................................................................................................................................................23

Portlogdump fields................................................................................................................................................................................................................................................... 23
Task ........................................................................................................................................................................................................................................................................ 23
Event....................................................................................................................................................................................................................................................................... 24
Port.......................................................................................................................................................................................................................................................................... 25
Cmd.........................................................................................................................................................................................................................................................................26
Args......................................................................................................................................................................................................................................................................... 26
FC-PH frames............................................................................................................................................................................................................................................................. 27
FC-PH frames definitions........................................................................................................................................................................................................................... 27
State Change Notification (SCN)...................................................................................................................................................................................................................... 33
Reading an SCN Event................................................................................................................................................................................................................................ 33
State Change Notification codes............................................................................................................................................................................................................ 34
Internal SCN sub-types............................................................................................................................................................................................................................... 35

Brocade portLogDump Reference Guide

53-1004122-01 3
 FOR BROCADE AND PARTNER USE ONLY

Internal SCN RSCN sub-types................................................................................................................................................................................................................39

Internal SCN GBIC states........................................................................................................................................................................................................................... 39
Internal SCN update states........................................................................................................................................................................................................................ 39
Internal SCN fabric states........................................................................................................................................................................................................................... 39
Internal SCN Diag states.............................................................................................................................................................................................................................40
Internal SCN SEC states............................................................................................................................................................................................................................. 40
Internal SCN CER state............................................................................................................................................................................................................................... 40
Internal SCN MMI states.............................................................................................................................................................................................................................40
Internal SCN slot states............................................................................................................................................................................................................................... 40
Internal SCN env states................................................................................................................................................................................................................................. 41
Internal SCN switch states............................................................................................................................................................................................................................41
Internal SCN HA states.................................................................................................................................................................................................................................. 41
Internal SCN zone states.............................................................................................................................................................................................................................42
Internal SCN FCP states............................................................................................................................................................................................................................. 42
Internal SCN port states...............................................................................................................................................................................................................................42
Internal SCN LE port states.......................................................................................................................................................................................................................43
Internal SCN GE port states...................................................................................................................................................................................................................... 43
Internal SCN blade states............................................................................................................................................................................................................................44
Loop State Change Notification reason codes for LIP........................................................................................................................................................................44
Speed negotiation..................................................................................................................................................................................................................................................... 45
I/O control (IOCTL)........................................................................................................................................................................................................................................ 45
Extended Link Service (ELS)...............................................................................................................................................................................................................................55
ELS command codes................................................................................................................................................................................................................................... 55
ELS example 1....................................................................................................................................................................................................................................................57
ELS example 2..................................................................................................................................................................................................................................................57
Switch Fabric Internal Link Services (SW_ILS)..........................................................................................................................................................................................57
Brocade-specific SW_ILS command codes....................................................................................................................................................................................57
SW_ILS reject reason codes (SW_RJT)............................................................................................................................................................................................. 59
SW_ILS examples...........................................................................................................................................................................................................................................60
Fabric OS State Synchronization (FSS).............................................................................................................................................................................................. 67
FSS messages..................................................................................................................................................................................................................................................68
ISL values and parameters.....................................................................................................................................................................................................................................71
ISL flow control mode values..................................................................................................................................................................................................................... 71
ISL flow control parameters.........................................................................................................................................................................................................................71
Switch_Priority field values...........................................................................................................................................................................................................................71
Fibre Channel Common Transport protocol (FC-CT)...........................................................................................................................................................................72
Name Server (SNS)........................................................................................................................................................................................................................................ 72
Name Server commands and code descriptions..........................................................................................................................................................................72
Management Server.................................................................................................................................................................................................................................................78
Fabric Configuration Server ......................................................................................................................................................................................................................78
Fabric Configuration Server codes........................................................................................................................................................................................................ 78
Management Server response codes.................................................................................................................................................................................................. 78
Management Server command codes................................................................................................................................................................................................78
Management Server reason code and explanation..................................................................................................................................................................... 85
Fabric Zone Server (ZS)...............................................................................................................................................................................................................................88
Alias Service request code (FC-GS-1)................................................................................................................................................................................................. 95
Decoding a ctin event....................................................................................................................................................................................................................................95
Decoding a ctout event................................................................................................................................................................................................................................ 96
Fibre Channel Protocol information................................................................................................................................................................................................................ 97
Well-Known Ordered Sets..........................................................................................................................................................................................................................97

Brocade portLogDump Reference Guide

4 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY

Port State Machine Values (pstate)........................................................................................................................................................................................................99

Well-Known Addresses................................................................................................................................................................................................................................99
Valid AL_PA Addresses............................................................................................................................................................................................................................ 100

Brocade portLogDump Reference Guide

53-1004122-01 5
 FOR BROCADE AND PARTNER USE ONLY

Brocade portLogDump Reference Guide

6 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY

Preface
∙ Document conventions..................................................................................................................................................................................................... 7
∙ Brocade resources...............................................................................................................................................................................................................8
∙ Contacting Brocade Technical Support...................................................................................................................................................................8
∙ Document feedback........................................................................................................................................................................................................... 9

Document conventions
The document conventions describe text formatting conventions, command syntax conventions, and important notice formats used in
Brocade technical documentation.

Object Missing
This object is not available in the repository.

Command syntax conventions

Bold and italic text identify command syntax components. Delimiters and operators define groupings of parameters and their logical
relationships.

Convention Description
bold text Identifies command names, keywords, and command options.
italic text Identifies a variable.
value In Fibre Channel products, a fixed value provided as input to a command option is printed in plain text, for
example, --show WWN.
[] Syntax components displayed within square brackets are optional.

Default responses to system prompts are enclosed in square brackets.

{x|y|z} A choice of required parameters is enclosed in curly brackets separated by vertical bars. You must select
one of the options.

In Fibre Channel products, square brackets may be used instead for this purpose.
x|y A vertical bar separates mutually exclusive elements.
<> Nonprinting characters, for example, passwords, are enclosed in angle brackets.
... Repeat the previous element, for example, member[member...].
\ Indicates a “soft” line break in command examples. If a backslash separates two lines of a command
input, enter the entire command at the prompt without the backslash.

Notes, cautions, and warnings

Notes, cautions, and warning statements may be used in this document. They are listed in the 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.

Brocade portLogDump Reference Guide

53-1004122-01 7
 FOR BROCADE AND PARTNER USE ONLY
Preface

ATTENTION
An Attention statement indicates a stronger note, for example, to alert you when traffic might be interrupted or the device might
reboot.

CAUTION
A Caution statement alerts you to situations that can be potentially hazardous to you or cause damage to hardware, firmware,
software, or data.

DANGER
A Danger statement indicates conditions or situations that can be potentially lethal or extremely hazardous to you. Safety labels
are also attached directly to products to warn of these conditions or situations.

Brocade resources
Visit the Brocade website to locate related documentation for your product and additional Brocade resources.

You can download additional publications supporting your product at www.brocade.com. Select the Brocade Products tab to locate your
product, then click the Brocade product name or image to open the individual product page. The user manuals are available in the
resources module at the bottom of the page under the Documentation category.

To get up-to-the-minute information on Brocade products and resources, go to MyBrocade. You can register at no cost to obtain a user
ID and password.

Release notes are available on MyBrocade under Product Downloads.

White papers, online demonstrations, and data sheets are available through the Brocade website.

Contacting Brocade Technical Support

As a Brocade customer, you can contact Brocade Technical Support 24x7 online, by telephone, or by e-mail. Brocade OEM customers
contact their OEM/Solutions provider.

Brocade customers
For product support information and the latest information on contacting the Technical Assistance Center, go to http://
www.brocade.com/services-support/index.html.

If you have purchased Brocade product support directly from Brocade, use one of the following methods to contact the Brocade
Technical Assistance Center 24x7.

Online Telephone E-mail

Preferred method of contact for non-urgent Required for Sev 1-Critical and Sev 2-High support@brocade.com
issues: issues:
Please include:
∙ My Cases through MyBrocade ∙ Continental US: 1-800-752-8061
∙ Problem summary
∙ Software downloads and licensing ∙ Europe, Middle East, Africa, and Asia
∙ Serial number
tools Pacific: +800-AT FIBREE (+800 28
34 27 33) ∙ Installation details
∙ Knowledge Base
∙ For areas unable to access toll free ∙ Environment description
number: +1-408-333-6061

Brocade portLogDump Reference Guide

8 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Preface

Online Telephone E-mail

∙ Toll-free numbers are available in

many countries.

Brocade OEM customers

If you have purchased Brocade product support from a Brocade OEM/Solution Provider, contact your OEM/Solution Provider for all of
your product support needs.

∙ OEM/Solution Providers are trained and certified by Brocade to support Brocade® products.

∙ Brocade provides backline support for issues that cannot be resolved by the OEM/Solution Provider.

∙ Brocade Supplemental Support augments your existing OEM support contract, providing direct access to Brocade expertise.
For more information, contact Brocade or your OEM.

∙ For questions regarding service levels and response times, contact your OEM/Solution Provider.

Document feedback
To send feedback and report errors in the documentation you can use the feedback form posted with the document or you can e-mail
the documentation team.

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. You can
provide feedback in two ways:

∙ Through the online feedback form in the HTML documents posted on www.brocade.com.

∙ By sending your feedback to documentation@brocade.com.

Provide the publication title, part number, and as much detail as possible, including the topic heading and page number if applicable, as
well as your suggestions for improvement.

Brocade portLogDump Reference Guide

53-1004122-01 9
 FOR BROCADE AND PARTNER USE ONLY
Preface

Brocade portLogDump Reference Guide

10 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY

About This Document

∙ Supported hardware and software..............................................................................................................................................................................11
∙ What's new in this document........................................................................................................................................................................................12

Supported hardware and software

The following hardware platforms are supported by Fabric OS 8.0.1.

NOTE
Although many different software and hardware configurations are tested and supported by Brocade Communication Systems,
Inc for Fabric OS 8.0.1, documenting all possible configurations and scenarios is beyond the scope of this document.

Brocade Gen 5 (16-Gbps) fixed-port switches

∙ Brocade 6505 switch

∙ Brocade 6510 switch

∙ Brocade 6520 switch

∙ Brocade M6505 blade server SAN I/O module

∙ Brocade 6543 blade server SAN I/O module

∙ Brocade 6545 blade server SAN I/O module

∙ Brocade 6546 blade server SAN I/O module

∙ Brocade 6547 blade server SAN I/O module

∙ Brocade 6548 blade server SAN I/O module

∙ Brocade 6558 blade server SAN I/O module

∙ Brocade 7840 Extension Switch

Brocade Gen 5 (16-Gbps) DCX 8510 Directors

NOTE
For ease of reference, Brocade chassis-based storage systems are standardizing on the term “Director”. The legacy term
“Backbone” can be used interchangeably with the term “Director”.

∙ Brocade DCX 8510-4 Director

∙ Brocade DCX 8510-8 Director

Brocade Gen 6 fixed-port switches

∙ Brocade G620 switch

Brocade portLogDump Reference Guide

53-1004122-01 11
 FOR BROCADE AND PARTNER USE ONLY
About This Document

Brocade Gen 6 Directors

∙ Brocade X6-4 Director

∙ Brocade X6-8 Director

Fabric OS support for the Brocade Analytics Monitoring Platform (AMP) device depends on the specific version of the software running
on that platform. Refer to the AMP Release Notes and documentation for more information.

What's new in this document

This document includes new and modified information for the Fabric OS 8.0.1 release.

Changes made for this release

The following content is newly added or has been significantly revised for this release of this document:

Updated the Supported hardware and software on page 11.

Brocade portLogDump Reference Guide

12 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY

Understanding the Portlogdump

Command
∙ Portlogdump command..................................................................................................................................................................................................13
∙ Reading portlogdump output.......................................................................................................................................................................................13
∙ Using and customizing the portlogdump output..............................................................................................................................................15
∙ Locating information by task........................................................................................................................................................................................ 17

Portlogdump command
The portlogdump command output is a powerful tool that can be used to troubleshoot fabric issues. This chapter lists most of the Fibre
Channel codes that you need to decode your Fibre Channel portlogdump traces and Fibre Channel analyzer traces, and explains how to
decode the Fabric OS portlogdump traces.

Use the portlogdump output to read the actions and communications of a fabric. By understanding the processes that are taking place in
the fabric, you can locate areas that may be problematic.

This chapter assumes that you are familiar with the Fibre Channel Physical (FC-PH) frame and the portlogdump format, and also
understand types of frames.

ATTENTION

Information contained in this chapter is subject to change without notice. In addition, undocumented messages may appear in
the portlogdump output.

Reading portlogdump output

The portlogdump command displays the port log, showing a portion of the FC-PH header (refer to FC-PH frames on page 27) and the
payload.

NOTE
Some Brocade hardware can divide the physical switch into virtual switches. The portlogdump command does not recognize
virtual switches and reports the information for the entire switch.

Because the portlogdump output is long, a truncated example is presented.

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Oct 16 00:58:32 2009
00:58:46.432 PORT scn 8 6 00000000,00000000,00000001
00:58:46.513 PORT debug 64 00000000,abcddcba,00000002,00000401
00:58:45.933 PORT scn 0 22 00010002,43020001,00000001
00:58:56.132 PORT scn 64 0 c70e74e0,c7059410,00000800
00:31:50.510 SPEE sn 3 WS 00000000,00000000,00000000 * 2
<output truncated>

The primary example is broken down by line and defined by information unit in the following examples.

Brocade portLogDump Reference Guide

53-1004122-01 13
 FOR BROCADE AND PARTNER USE ONLY
Understanding the Portlogdump Command

Time
The time field displays the event date and time in a 24-hour clock format (to the millisecond level).

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Oct 16 00:58:32 2009
00:58:46.513 PORT debug 64 00000000,abcddcba,00000002,00000401

Task
The task field displays the task that was in progress when the event occurred. Refer to Task on page 23 for more information.

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Oct 16 00:58:32 2009
00:58:46.513 PORT debug 64 00000000,abcddcba,00000002,00000401

Event
The event field displays the specific action described in the output. Refer to Event on page 24 for more information.

NOTE
The debug event is suppressed from the port log by default. You must enable it with the configure command.

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Oct 16 00:58:32 2009
00:58:46.513 PORT debug 64 00000000,abcddcba,00000002,00000401

Port
The port field in the portlogdump output indicates a physical port number.

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Oct 16 00:58:32 2009
00:58:46.513 PORT debug 64 00000000,abcddcba,00000002,00000401

Cmd
The cmd field displays the commands associated with each event category. Refer to Cmd on page 26 for more information.

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Oct 16 00:58:32 2009
00:48:11.474 PORT scn 19 11 00000000,00000000,00010000

Brocade portLogDump Reference Guide

14 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Understanding the Portlogdump Command

Args
The args field indicates arguments associated with a task or event. Refer to Args on page 26 for more information.

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Dec 11 23:55:03 2009
00:58:46.513 PORT debug 64 00000000,abcddcba,00000002,00000401

Using and customizing the portlogdump output

There are several commands that can be used to view certain aspects of the portlogdump output (such as a list of possible events) and
customize the output of the portlogdump .

Refer to the Fabric OS Command Reference for more detailed command information.

Portlogdump-related commands
The following table displays commands related to portlogdump .

TABLE 1 Portlogdump-related commands

Command Action
portlogdump [count[, saved]] Displays the port log, listing all entries in the log without page breaks. This
command displays the same information as portlogshow, but portlogshow
prompts you to type a return between each page of the output.

The count option controls the number of entries that display.

The saved option (when set to 1) causes the command to display the port
log saved in flash memory (due to a previous switch fault).
portlogdumpport port_index Displays the port log of specified port by its port index number. The
command displays all entries in the log without any page breaks. It is
identical to portlogshowportid, except that portlogshow portid prompts the
user to type a return between each page of output.
portlogshow [count, [saved]] Displays the port log. This command displays one page at a time. The
portlogshow command displays the same information as portlogdump ,
but it prompts you to type a return between each page of the output.

The count option controls the number of entries that display.

The saved option (when set to 1) causes the command to display the port
log saved in flash memory (due to a previous switch fault)
portlogclear Clears the port log of all entries. You may want to clear the port log before
triggering an activity so that the log displays only the entries related to that
activity.
portlogeventshow Displays the ID associated with the event. You can use this ID to enable or
disable an event and prevent it from appearing in the portlogdump
program output.

Also, this command shows the current enabled state for each event.
portlogshowport [port_index] Displays the port log of a specified port, showing one page at a time. It is
identical to portlogdumpportid, except that portlogdumpportid does not
prompt you to type a return between each page of the output.
portlogtypedisable log_type_id Disables the port log for a specified port log type. Disabling the port log
type prevents it from appearing in the portlogdump output. This saves
space for significant events.

Brocade portLogDump Reference Guide

53-1004122-01 15
 FOR BROCADE AND PARTNER USE ONLY
Understanding the Portlogdump Command

TABLE 1 Portlogdump-related commands (continued)

Command Action
portlogtypeenable log_type_id Enables the port log for a specified port log type. Enabling the port log
type allows it to appear in the portlogdump output.
portlogconfigshow Displays the current port log configuration.
portlogresize num_entries Resizes the number of port log entries.

Displaying and customizing the portlogdump output

A port log event is the specific action that is being described by the output. For a complete list of possible events for your switch, refer to
Event on page 24.

Use the following procedure to list port log events, and to find their associated ID numbers.

1. Connect to the switch as the administrator.

2. Enter the portlogeventshow command.

The left column displays the ID associated with the event. The number can be used to enable or disable a particular event; this
keeps it from appearing in the portlogdump output.

The middle column displays the event names.

The right column displays the enabled or disabled status of the event (0 = Enabled, 1 = Disabled). A disabled event does not
appear in the portlogdump output.

NOTE
Brocade does not recommend that you customize the portlogdump output unless directed to by Brocade Technical
Support.
3. Enter one of the following commands:

∙ – portlogtypeenable ID - To enable the particular event in the portlogdump output. ID is the ID number gathered in the
previous step.
– portlogtypedisable ID - To disable the particular event in the portlogdump output.ID is the ID number gathered in the
previous step.

In the following example, the "start" event is disabled. It will not appear in the portlogdump output.

switch:admin> portlogeventshow
ID Event-Name Disabled
---------------------------------
1 start 1
2 disable 0
3 enable 0
4 ioctl 0
5 Tx 0
6 Tx1 0
7 Tx2 0
8 Tx3 0
9 Rx 0
10 Rx1 0
11 Rx2 0
12 Rx3 0
13 stats 0
14 scn 0
15 pstate 0
16 reject 0
17 busy 0

Brocade portLogDump Reference Guide

16 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Understanding the Portlogdump Command

18 ctin 0
19 ctout 0
20 errlog 0
21 loopscn 0
22 create 0
23 debug 1
24 nbrfsm 0
25 timer 0
26 sn 0
27 fcin 0
28 fcout 0
29 read 0
30 write 0
31 err 0
32 frame 0
33 msRemQ 0
34 msRemR 0
35 nsRemQ 0
36 nsRemR 0
37 rscn 0
38 state 0
39 xalloc 0
40 xfree 0
41 xerr 0
42 xstate 0
43 seq 0
44 seqst 0
45 iu 0
46 payload 0
47 zone 0
48 cmd 0
49 event 0
50 msg 0
51 switch 0
52 ficonq 0
53 routing 0
switch:admin> portlogtypedisable 1

Locating information by task

The following table is an information map, and displays where to locate specific portlogdump information.

TABLE 2 Portlogdump information mapping table

Task Event Port Command Argument Reference
PORT ioctl port# IOCTL Code Speed negotiation on
page 45

Refer to I/O control

(IOCTL) on page 45
for a complete listing
of the SCN codes.
scn port# SCN Code Refer to State Change
Notification codes on
page 34.
Tx( ) port# Size of payload in
bytes
Rx ( ) port# Size of payload in The args for these If the ELS is
bytes frames are word 0, R_CTL=0x22 or
word 1, word 4 of the 0x23, refer to I/O
frame header, and control (IOCTL) on
word 0 of the frame page 45.
payload.

Brocade portLogDump Reference Guide

53-1004122-01 17
 FOR BROCADE AND PARTNER USE ONLY
Understanding the Portlogdump Command

TABLE 2 Portlogdump information mapping table (continued)

Task Event Port Command Argument Reference

If the FC-CT is
R_CTL=0x02 or
0x03, refer to FC-CT
reason code
explanation (NS_RJT)
on page 75.

If the SW_ILS is
R_CTL=0x02 or
0x03, refer to Switch
Fabric Internal Link
Services (SW_ILS) on
page 57.
INTR PS (primitive port# State Machine Value Standard protocol
sequence) pstate format. Visit the http://
www.t11.org web site.
SPEED sn port# WS Speed negotiation Speed negotiation on
event, page 45
00000000,000000
Refer to Loop State
00
Change Notification
reason codes for LIP
on page 44 for a
complete listing of the
SCN codes.
LOOP loopscn port# Loopscan code - Brocade ASIC LOOP Loop State Change
Brocade ASIC LOOP Code Notification reason
Code cmd column codes for LIP on page
44
nsd ctin port# Last byte of Well- FC-CT’s payload Fibre Channel
Known Address (WKA) Common Transport
protocol (FC-CT) on
ctout port# Last byte of WKA FC-CT’s payload
page 72
rscn 0 Bytes 0-2 of Word 0 The arguments are: I/O control (IOCTL) on
of the header (the DID page 45
∙ Word 1 of
of the frame) which is
the frame Refer to Loop State
the domain controller
header (the Change Notification
SID will be a reason codes for LIP
domain on page 44 for a
controller) complete listing of the
SCN codes.
∙ The SW_ILS
Code
(0x1b0000
00 or 0x1f)

∙ The high
order nibble
of the
highest
order byte is
the RSCN
information,
the low
order nibble
of that byte
is the
address

Brocade portLogDump Reference Guide

18 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Understanding the Portlogdump Command

TABLE 2 Portlogdump information mapping table (continued)

Task Event Port Command Argument Reference

format, the
lower 3
bytes are the
24-bit
address

∙ The
detection
method
Rscn 0 Word 0 = 24-bit The arguments are:
address is the DID the
∙ Word 1 of
RSCN is accessing.
the frame
header (the
SID is the
Fabric
Controller,
fffffd)

∙ Word 0 of
the frame
payload with
the high
order byte
being 0x61
(ELS
RSCN). The
next byte is
the page
length and is
0x04. The
two low
order bytes
are the
payload
length (min
8, max
1024)

∙ Lowest
three bytes
are the 24-
bit address
of the
changed
device
nsRemQ 0: 1st nibble NS cmd Last 3 nibbles: Name D_ID, S_ID, For Name Fibre Channel
code Server Cmd code. For Server Port Type, refer Common Transport
Fabric internal FC-CT, to Name Server port protocol (FC-CT) on
refer to cmd codes on type on page 76 page 72
Fabric internal FC-CT
commands on page
75
nsRemR port# Refer to Name Server D_ID, S_ID, Additional
Cmd Code on Name information command
Server commands and code
code descriptions on
page 72

Brocade portLogDump Reference Guide

53-1004122-01 19
 FOR BROCADE AND PARTNER USE ONLY
Understanding the Portlogdump Command

TABLE 2 Portlogdump information mapping table (continued)

Task Event Port Command Argument Reference
msd ctin port# Last byte of WKA FC-CT payload Fibre Channel
Common Transport
ctout port# Last byte of WKA FC-CT payload
protocol (FC-CT) on
page 72
asd ctout port# Last byte of WKA FC-CT payload Fibre Channel
Common Transport
protocol (FC-CT) on
page 72
FSS msg N/A Service ID, FSS messages on
Component ID, Send page 68
receive data, optional
flags, Additional text
description
cmd N/A
event N/A

Example outputs for portlogdump

The following examples show outputs for the portlogdump command in different scenarios. Refer to the previous table (Portlogdump
information mapping table) to interpret the command output.

Port going offline

18:47:53.907 PORT scn 242 5 00000000,00000000 ,00000002
18:47:53.907 PORT scn 242 1 00010004,43820012,00000002
18:47:53.907 PORT scn 242 22 00010004,43820012,00000001

E_Port going online

19:12:26.104 INTR pstate 242 AC
19:12:26.109 PORT scn 242 11 00000000,00000000,00000002
19:12:26.238 PORT Rx 242 164 02fffffd,00fffffd,5388ffff,10000000
19:12:26.238 PORT Tx 242 0 c0fffffd,00fffffd,53882bf3,00000001
19:12:26.238 FCPH read 242 164 02fffffd,00fffffd,ed000000,00000000,53882bf3
19:12:26.238 FCPH seq 242 a4 22290000,53882bf3,00000b22,0000001c,00000000
19:12:26.240 PORT scn 242 1 00000000,00000000,00000001
19:12:26.240 PORT scn 242 22 00000000,00000000,00000010
19:12:26.248 FCPH write 242 164 00fffffd,00fffffd,00000000,00000000,00000000
19:12:26.248 FCPH seq 242 a4 00210000,00000000,00000ebb,00010182,00000000
19:12:26.248 PORT Tx 242 164 02fffffd,00fffffd,2bfaffff,10000000
19:12:26.249 FCPH write 242 8 03fffffd,00fffffd,ed000000,00000000,53882bf3
19:12:26.249 FCPH seq 242 8 22980000,53882bf3,00000ebb,0004019c,00000000
19:12:26.249 PORT Tx 242 8 03fffffd,00fffffd,53882bf3,01000000
19:12:26.250 PORT Rx 242 0 c0fffffd,00fffffd,2bfa5389,00000001
19:12:26.250 PORT Rx 242 0 c0fffffd,00fffffd,53882bf3,00000001
19:12:26.282 PORT Rx 242 164 03fffffd,00fffffd,2bfa5389,02000000
19:12:26.282 PORT Tx 242 0 c0fffffd,00fffffd,2bfa5389,00000001
19:12:26.282 FCPH read 242 164 03fffffd,00fffffd,ee000000,00000000,2bfa5389
19:12:26.282 FCPH seq 242 a4 22980000,2bfa5389,00000b22,0000001c,00000000
19:12:26.380 INTR pstate 242 LR1
19:12:26.380 INTR pstate 242 AC
19:12:26.386 PORT scn 242 11 00000000,00000000,00000001
19:12:26.386 FCPH write 242 48 00fffffd,00fffffd,00000000,00000000,00000000
19:12:26.386 FCPH seq 242 30 00210000,00000000,00000ebb,00010182,00000000
19:12:26.386 PORT Tx 242 48 02fffffd,00fffffd,2bfbffff,30010030
19:12:26.386 PORT Rx 242 0 c0fffffd,00fffffd,2bfb538a,00000001
19:12:26.387 PORT Rx 242 48 03fffffd,00fffffd,2bfb538a,02000030
19:12:26.387 PORT Tx 242 0 c0fffffd,00fffffd,2bfb538a,00000001
19:12:26.387 FCPH read 242 48 03fffffd,00fffffd,ef000000,00000000,2bfb538a
19:12:26.387 FCPH seq 242 30 22980000,2bfb538a,00000b22,0000001c,00000000

Brocade portLogDump Reference Guide

20 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Understanding the Portlogdump Command

19:12:26.388 FCPH write 242 48 00fffffd,00fffffd,00000000,00000000,00000000

19:12:26.388 FCPH seq 242 30 00210000,00000000,00000ebb,00010182,00000000
19:12:26.388 PORT Tx 242 48 02fffffd,00fffffd,2bf9ffff,11100030
19:12:26.390 PORT Rx 242 0 c0fffffd,00fffffd,2bf9538b,00000001
19:12:26.391 PORT Rx 242 48 02fffffd,00fffffd,538cffff,11100030
19:12:26.391 PORT Tx 242 0 c0fffffd,00fffffd,538c2bf8,00000001
19:12:26.391 FCPH read 242 48 02fffffd,00fffffd,f0000000,00000000,538c2bf8
19:12:26.391 FCPH seq 242 30 22290000,538c2bf8,00000b22,0000001c,00000000
19:12:26.391 PORT Rx 242 48 03fffffd,00fffffd,2bf9538b,02100030
19:12:26.391 PORT Tx 242 0 c0fffffd,00fffffd,2bf9538b,00000001
19:12:26.391 FCPH write 242 48 03fffffd,00fffffd,f0000000,00000000,538c2bf8
19:12:26.391 FCPH seq 242 30 22980000,538c2bf8,00000ebb,0004019c,00000000
19:12:26.391 PORT Tx 242 48 03fffffd,00fffffd,538c2bf8,02100030
19:12:26.392 PORT scn 242 1 00000000,00000000,00000010

F_Port going online

11:40:16.284 INTR pstate 10 AC
11:40:16.290 PORT scn 10 11 00000000,00000000,00000002
11:40:16.290 PORT Rx3 10 116 22fffffe,00000000,4ad3ffff,04000000
11:40:16.290 PORT scn 10 1 00000000,00000000,00000001
11:40:16.290 PORT scn 10 22 00000000,00000000,00000010
11:40:16.290 PORT scn 10 1 00000000,00000000,00000020
11:40:16.290 PORT scn 10 22 00000000,00000000,00000008
11:40:16.408 PORT Tx3 10 116 23030a00,00fffffe,4ad30bc6,02000000

Brocade portLogDump Reference Guide

53-1004122-01 21
 FOR BROCADE AND PARTNER USE ONLY
Understanding the Portlogdump Command

Brocade portLogDump Reference Guide

22 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY

Troubleshooting Using the Port Logs

∙ Portlogdump fields...........................................................................................................................................................................................................23
∙ FC-PH frames.....................................................................................................................................................................................................................27
∙ State Change Notification (SCN)..............................................................................................................................................................................33
∙ Loop State Change Notification reason codes for LIP................................................................................................................................44
∙ Speed negotiation............................................................................................................................................................................................................. 45
∙ Extended Link Service (ELS)...................................................................................................................................................................................... 55
∙ Switch Fabric Internal Link Services (SW_ILS)................................................................................................................................................. 57
∙ ISL values and parameters.............................................................................................................................................................................................71
∙ Fibre Channel Common Transport protocol (FC-CT).................................................................................................................................. 72
∙ Management Server........................................................................................................................................................................................................ 78
∙ Fibre Channel Protocol information........................................................................................................................................................................97

Portlogdump fields
Each field in the portlogdump output displays information about a single event. The portlogdump command output consists of six fields:

∙ Time

∙ Task

∙ Event

∙ Port

∙ Cmd

∙ Args

Task
The following table lists the task descriptions and functionalities.

TABLE 3 Task descriptions

Task Description Functionality
INTR Internal Events associated with this task:

Port State (PS) and debug

PORT Port kernel driver Events associated with task: debug, I/O control,
State Change Notification, Transmit and Receive
SPEED Speed ASIC speed negotiation function; speed
selection of either 1, 2, 4, 8, or 16 Gbps
FLTR Filtering ASIC frame filtering function; used in WWN
zoning (WWN)
LOOP Loop ASIC loop function; it has to do with loop port
initialization
nsd Name Server Daemon NS daemon
msd Management Server Daemon MS daemon
asd Alias Server Daemon AS daemon

Event associated with this task: ctin and ctout

Brocade portLogDump Reference Guide

53-1004122-01 23
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 3 Task descriptions (continued)

Task Description Functionality
fspfd Fibre Channel Shortest Path First Event associated with this task: Neighbor state
transition
zone Zoning Event associated with this task: debug
fcpd N/A No event is associated with this task.
FSSk Fabric OS State Synchronization The primary function of FSS is to deliver State
Update messages from ACTIVE components to
their peer STANDBY components. FSS
determines if fabric elements are synchronized
(and thus "FSS-compliant").

Associated events are: UPCONN,

DOWNCONN, COMP, INCOMP, DUMPRDY,
SYNCSUCC, FAILSYNC, START, STOP,
RECOVFAIL, TAKE, YIELD, MISCATCH,
UPDATE, ACTIVE, STANDBY, TXQHIGH,
RXQHIGH, MISSSVC, AVAILSVC, TRACE.

Event
An event is the specific action that is being described by the output. For a complete list of possible events for your switch, refer to the
following table.

TABLE 4 Events descriptions

Event Description
start Describes a switch start or re-start event.
disable Indicates a port is disabled.
enable Indicates a port is enabled.
ioctl Indicates a port I/O control is executed.
Tx Indicates a frame is transmitted.
Tx() Indicates a frame is transmitted, class 1 or 2.
Tx(3) Indicates class 3 frame.
Rx Indicates a frame is received.
Rx() Indicates a frame is received, class 1 or 2.
Rx(3) Indicates class 3 frame.
stats Indicates a port status or statistics.
scn Indicates a State Change Notification.
pstate Indicates a port changes physical state.
reject Indicates a frame is rejected.
busy Indicates a received frame is busied.
ctin Indicates a Common Transport (CT)-based request is received.
ctout Indicates a Common Transport (CT)-based response is transmitted.
errlog Indicates a message is added to the error log.
loopscn Indicates a loop state change notification.
create Indicates a task is created.
debug Indicates generic debugging information.
nbrfsm Indicates a neighbor state transition.

Brocade portLogDump Reference Guide

24 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 4 Events descriptions (continued)

Event Description
timer Indicates a timer.
sn Indicates a speed negotiation.
fcin Indicates FC input.
fcout Indicates FC output.
read Indicates an FC read event.
write Indicates an FC write event.
err Indicates an FC error.
frame Indicates an FC frame payload.
nsRemQ Indicates an interswitch NS query.
nsRemR Indicates an interswitch NS response.
rscn Indicates a Registered State Change Notification (RSCN).
state Indicates an FC state.
xalloc Indicates an alloc exchange event.
xfree Indicates a free exchange event.
xerr Indicates an exchange error.
xstate Indicates an exchange state event.
seq Indicates a sequence event.
seqst Indicates a sequence state event.
iu Indicates an IU event.
payload Indicates a frame payload event.
zone Indicates a zone request/response event.
cmd Indicates an FSS command log event.
event Indicates an FSS event log event.
msg Indicates an FSS message log event.
switch Indicates a switch driver log event.
ficonq Indicates a FICON queue and ELS measurements event.
routing Indicates a switch/blade drivers routing log event.
reconf Indicates a fabric reconfiguration.
ps Indicates a primitive sequence in a Fibre Channel protocol exchange.

The following example indicates an internal task (INTR), an associated event is the Port State Machine (pstate), and the cmd field
describes the event, which is a link failure (LF2).

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Oct 16 00:58:32 2009
00:48:11.473 INTR pstate 19 LF2

Port
The port field in the portlogdump output indicates a physical port number.

Brocade portLogDump Reference Guide

53-1004122-01 25
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Oct 16 00:58:32 2009
00:58:32.750 PORT debug 64 00000000,abcddcba,00000002,00000401
00:58:56.132 PORT scn 64 0 c70e74e0,c7059410,00000800
00:31:50.510 SPEE sn 3 WS 00000000,00000000,00000000

Cmd
The cmd field represents different values depending on the task and event.

A command (cmd) is associated with each event category. For example, in the following output, the cmd column represents the scn
event. If the task is PORT, the cmd is usually the size of the payload.

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Oct 16 00:58:32 2009
00:48:11.474 PORT scn 19 11 00000000,00000000,00010000

Commands associated with an event category are also referred to as State Events. The following table lists some of the possible
commands.

TABLE 5 List of possible commands (cmd)

Command Definition
AC Active State
FC Name Server (in MS)
LR1 Link Reset: LR Transmit State
LR2 Link Reset: LR Receive State
LR3 Link Reset: LRR Receive State
LF1 Link Failure: NOS Transmit State
LF2 Link Failure: NOS Receive State
OL1 Offline: OLS Transmit State
OL2 Offline: OLS Receive State
OL3 Offline: Wait for OLS State
LIP Loop Initialization Primitive received
LIM FL_Port became the Loop Initialization Master
OLP Offline or Non-Participating

Args
The args field represents different values depending on the task and event.

If there is an asterisk with a number after the args field, this means that there are multiple identical entries collapsed into one line. In the
following example, the last line represents three identical events.

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Dec 11 23:55:03 2009
23:55:11.439 PORT Tx3 1 12 22000000,00000000,ffffffff,11010000
23:55:11.439 PORT Rx3 1 12 22000000,00000000,ffffffff,11010000

Brocade portLogDump Reference Guide

26 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

23:55:11.439 PORT Tx3 1 20 22000000,00000000,ffffffff,11020000

23:55:11.439 PORT Rx3 1 20 22000000,00000000,ffffffff,11020000
23:55:11.439 PORT Tx3 1 20 22000000,00000000,ffffffff,11030000
23:55:11.439 PORT Rx3 1 20 22000000,00000000,ffffffff,11030000
23:55:11.439 PORT Tx3 1 20 22000000,00000000,ffffffff,11040000
23:55:11.439 PORT Rx3 1 20 22000000,00000000,ffffffff,11040000

FC-PH frames
FC_PH stands for Fibre Channel payload and header frames. The header contains control and addressing information associated with
the frame. The payload contains the information being transported by the frame and is determined by the higher-level service or FC-4
upper level protocol. There are many different payload formats based on the protocol.

∙ The routing control INFO bit (bit 27-24) determines how to interpret the payload.

∙ The TYPE field (word 2, bit 31-24) tells which information unit (IU) format to use.

The following table describes the entire FC-PH frame.

TABLE 6 FC-PH frame diagram

4 8 Up to 2112 bytes 4 4
S C E
HEADER PAYLOAD
O R O

F C F

The following table cross-references the sections in this guide that discuss specific sections of the FC-PH frame.

TABLE 7 FC-PH frame cross-references

Word Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0
HEADER 0 Routing Control Destination ID (D_ID) on page 29
(R_CTL) on page 28
1 Class-Specific Control Source ID (S_ID) on page 29
Field (CS_CTL) on
page 32
2 Type of protocol Frame Control (F_CTL) on page 29
service (such as FC-
CT, FCP, FCIP, and so
on) for the FC-PH
frame
3 Sequence ID (SEQ_ID) Data Field Control Sequence Count (SEQ_CNT) on page 30
on page 30 (DF_CTL) on page
32
4 Originator ID (OX_ID) on page 30 Responder ID (RX_ID) on page 30
5 Parameter
Data Payload - 6 to 528 words

FC-PH frames definitions

The following sections describe the FC-PH frame header fields.

Brocade portLogDump Reference Guide

53-1004122-01 27
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

Routing Control (R_CTL)

The Routing Control (R_CTL) is the high-order byte in word 0 of the frame header. It defines the type of the frame and its contents. The
first four high-order bits (word bits 31-28) identify the frame type. The next four bits (word bits 27-24) define the contents of the frame
or identify the function of the frame.

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Oct 16 00:58:32 2009
00:46:44.044 PORT Tx 8 40 02fffffd,00fffffd,027fffff,14000000

The following table diagrams the structure of the Routing Control bits.

TABLE 8 Routing Control bits - R_CTL diagram

R_CTL bits Information Description
FC-4 Device Data x'0' 0 Uncategorized Device Data
1 Solicited Device Data
2 Unsolicited Control Info (Request)
3 Solicited Control Info (Reply)
4 Unsolicited Device Data
5 Data Descriptor
6 Unsolicited Command
7 Command Status Information
Extended Link Service x'2' 2 Request
3 Reply
FC-4 Link Data x'3' 2 Request

Note : Same as FC-4 Device Data frames. 3 Reply

4 Video Data
Basic Link Service x'8' 0 No Operation (NOP)
1 Abort Sequence (ABTS)
2 Remove Connection (RMC)
3 Reserved
4 Basic_Accept (BA_ACC)
5 Basic_Reject (BA_RJT)
6 Preempted (PRMT)
Others Reserved
Link Control x'C' 0 ACK
1 ACK
2 N_Port Reject (P_RJT)
3 Fabric Reject (F_RJT)
4 N_Port Busy (P_BSY)
5 Fabric Busy to Data Frame (F_BSY)
6 Fabric Busy to Link Control Frame (F_BSY)
7 Link Credit Reset (LCR)
8 Notify (NTY)
9 End

Brocade portLogDump Reference Guide

28 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 8 Routing Control bits - R_CTL diagram (continued)

R_CTL bits Information Description
Others Reserved

Destination ID (D_ID)
The Destination ID ( D_ID) refers to the Native port address (24-bit address).

Example args

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Dec 11 23:55:03 2009
23:55:27.598 PORT Tx 1 40 02fffffd,00fffffd,8b4fffff,14000000

In the example arguments, the D_ID is the Well Known Address of a Fabric Controller. The underlined fffffd field is the D_ID.

Source ID (S_ID)
The Source ID (S_ID) refers to the Native port address (24-bit address).

Example args

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Dec 11 23:55:03 2009
23:55:27.598 PORT Tx 1 40 02fffffd,00fffffd,8b4fffff,14000000

In the example arguments, the S_ID is the Well Known Address of a Fabric Controller. The underlined fffffd field is the S_ID.

Frame Control (F_CTL)

The Frame Control (F_CTL) field contains miscellaneous control information regarding the frame.

TABLE 9 Frame Control (F_CTL) diagram

Hex Abbreviation Description
0xC00000 FCTL_XCHSEQ Exchange & Sequence Context bit mask
0x800000 FCTL_RESPXCH Responder of Exchange
0x400000 FCTL_RECSEQ Sequence Recipient
0x200000 FCTL_1STSEQ First sequence of Exchange
0x100000 FCTL_LASTSEQ Last sequence of Exchange
0x080000 FCTL_ENDSEQ Last data frame of sequence
0x040000 FCTL_ENDCONN End of Connection pending
0x020000 FCTL_CHAINEDSEQ Chained Sequence active
0x010000 FCTL_SEQINIT Transfer sequence initiative
0x800000 FCTL_NEWXID X_ID reassigned
0x004000 FCTL_INVXID Invalid X_ID
0x003000 FCTL_ACKFORM ACK form capability
0x000800 FCTL_COMPRESS Data compression
0x000400 FCTL_ENCRYPT Data encryption
0x000200 FCTL_RETXSEQ Sequence retransmission

Brocade portLogDump Reference Guide

53-1004122-01 29
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 9 Frame Control (F_CTL) diagram (continued)

Hex Abbreviation Description
0x000100 FCTL_UNIDIRECTX Unidirectional transmission
0x0000C0 FCTL_CSCMASK Mask to get Control Sequence Condition
0x0000C0 FCTL_SEQDLY Sequence to follow-delayed
0x000080 FCTL_SEQSOON Sequence to follow-soon
0x000040 FCTL_SEQIMM Sequence to follow-immediately
0x000000 FCTL_SEQNONE No information
0x000030 FCTL_ASCMASK Mask to get Abort Sequence Condition
0x000030 FCTL_SEQABTR Abort Sequence - do ABTR
0x000020 FCTL_SEQSTOP Stop sequence
0x000010 FCTL_SEQABTS Abort sequence - do ABTS
0x000000 FCTL_SEQCONT Continue sequence
0x000030 FCTL_POLICYMASK Mask to get sequence policy
0x000030 FCTL_DISCRETX Discard Multi Sequence Immed ReTx
0x000020 FCTL_PROCESS Process policy with Infinite Buf
0x000010 FCTL_DISC1ABT Discard single sequence, abort
0x000000 FCTL_DISCMABT Discard Multi sequence, Abort
0x000008 FCTL_RELOFF Relative Offset present
0x000004 FCTL_XCHREASS Exchange Reassembly - reserved
0x000003 FCTL_FILLMASK Mask to get the fill bits
0x060f00 FCTL_INVALID Class 1, compression, encryption
0xffff NULL_XID Unassigned ox_id or rx_id

Sequence ID (SEQ_ID)
The Sequence ID (SEQ_ID) is used to identify and track all of the frames within a sequence between a source and destination port pair.

Sequence Count (SEQ_CNT)

The Sequence Count (SEQ_CNT) is used to indicate the sequential order of frame transmission within a sequence or multiple
consecutive sequences within the same exchange.

Originator ID (OX_ID)
The Originator ID ( OX_ID) refers to the exchange ID assigned by the originator port.

Example args

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Dec 11 23:55:03 2009
23:55:27.598 PORT Tx 1 40 02fffffd,00fffffd,8b4fffff,14000000

In the example, 8b4f is the Originator ID. Refer to FC-PH frames on page 27.

Responder ID (RX_ID)
The Responder ID is assigned by the responder to the exchange.

Brocade portLogDump Reference Guide

30 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

Example args

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Dec 11 23:55:03 2009
23:55:27.598 PORT Tx 1 40 02fffffd,00fffffd,8b4fffff,14000000

In the example, ffff is the Responder ID. Refer to FC-PH frames on page 27.

Data Field/Payload
The FC-PH standard limits the maximum size to 2112 bytes. Refer to FC-PH frames on page 27 for more details.

Type Code
The Type Code provides the type of protocol service (such as FC-CT, FCP, FCIP, and so on) for the FC-PH frame.

TABLE 10 FC-4 Type Codes

Code Type of Service
1x F_BSY (Fabric Busy, "x" = R_CTL bits 27-24)
3x F_BSY (N_Port Busy, "x" = R_CTL bits 27-24)
00 Basic Link Service
01 Extended Link Service
04 ISO/IEC 8802-2 LLC (In order)
05 ISO/IEC 8802-2 LLC/SNAP
06-07 Reserved
08 SCSI-FCP
09 SCSI-GPP
0A-0F SCSI-Reserved
10 Reserved: IPI-3
11 IPI-3 Master
12 IPI-3 Slave
13 IPI-3 Peer
14 Reserved: IPI-3
15 CP IPI-3 Master
16 CP IPI-3 Slave
17 CP IPI-3 Peer
18 Reserved: SBCCS
19 SBCCS - Channel (obsolete)
1A SBCCS - Control Unit (obsolete)
1B SBCCS-2 - Channel (proposed)
1C SBCCS-2 - Control Unit (proposed)
1D-1F Reserved: SBCCS
20 Fibre Channel Services (FC-CT)
21 FC-FG (not used)
22 Internal Link Service (SW_ILS)
23 FC-AL (not used)

Brocade portLogDump Reference Guide

53-1004122-01 31
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 10 FC-4 Type Codes (continued)

Code Type of Service
24 FC-SNMP
25-27 Reserved: Fabric Services
28-2F Reclaimed: was Futurebus
30-33 Scalable Coherent Interface (SCI)
34-37 MessageWay (FC-PH2)
38-3F Reserved
40 HIPPI - FP
41-47 Reserved: HIPPI
48-57 Reserved
58 Virtual Interface (FC-VI)
59-DF Reserved
E0-FF Vendor Unique

Data Field Control (DF_CTL)

The Data Field Control (DF_CTL) field indicates the presence of one or more optional headers at the beginning of the data field of the
frame. Optional headers are used for information that may be required by some applications or protocol mappings.

TABLE 11 Data Field Control (DF_CTL) optional headers

DF_CTL code Description
0x40 SECURITY_HEADER
0x20 NETWORK_HEADER
0x10 ASSOCIATION_HEADER
0x03 DEVICE_HEADER
0x8c DF_RESERVED

Class-Specific Control Field (CS_CTL)

Different controls are necessary for different classes of service. The Class-Specific Control Field (CS_CTL) field should always be zero,
per the FC-PH standards. If it is something other than zero, then it is a Brocade internal code called an "IU_Status Value." The following
table shows the CS_CTL. These are Brocade internal constants; not standard FC descriptions.

TABLE 12 Class-Specific Control Field (CS_CTL) IU_Status Values

Internal Code CS_CTL IU_Status Value
0x02 IU_P_RJT Received P_RJT
0x03 IU_F_RJT Received F_RJT
0x04 IU_P_BSY Received P_BSY
0x05 IU_F_BSY Received F_BSY
0x06 IU_F_BSY_LC Received F_BSY_LC
0x10 IU_NO_EXCH Cannot allocate exchange
0x11 IU_OFFLINE Port is offline
0x12 IU_BAD_EXCH Exchange ID not valid
0x13 IU_NO_ACK ED_TOV expired

Brocade portLogDump Reference Guide

32 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 12 Class-Specific Control Field (CS_CTL) IU_Status Values (continued)

Internal Code CS_CTL IU_Status Value
0x14 IU_CORRUPT Corruption such as CRC error, encoding error,
and so on
0x15 IU_BAD_CLASS Class 1 frame
0x16 IU_BAD_S_ID Invalid S_ID
0x17 IU_BAD_D_ID Invalid D_ID, VC, or multicast address
0x18 IU_TIMED_OUT Frame timed out, generate F_BSY
0x19 IU_TX_UNAVAIL Tx unavailable, generate F_BSY
0x1a IU_LOGIN_RQRD Login required
0x1b IU_PROTOCOL Protocol error
0x1c IU_RX_FLUSHED Frame flushed by Rx port
0x20 IU_ALPA_TMPNA AL_PA temporarily not available
0x21 IU_ALPA_PMTNA AL_PA permanently not available
0x22 IU_LOGO_OFFLINE Logout received or port goes offline
0x23 IU_ZONE_CONFLT Zone conflict
0x24 IU_ABTS_RX Received an abort signal that flushed this IU
0x80 IU_ASYNC_RESP Async IU response payload received
0x81 IU_ASYNC_TO Async IU response timeout
0x82 IU_ASYNC_ABTS Async IU aborts
0x83 IU_ASYNC_LOGO Async IU killed due to port logout or offline
0x84 IU_ASYNC_ACKTO Async IU ACK timeout

State Change Notification (SCN)

There are three different State Change Notifications:

∙ Stage Change Registration (SCR)

The State Change Registration (SCR) Extended Link Service requests the Fabric Controller to add the N_Port or NL_Port to the list of
N_Ports and NL_Ports registered to receive the Registered State Change Notification (RSCN) Extended Link Service.

∙ Registered State Change Notification (RSCN)

The Fabric Controller only issues RSCN requests to N_Ports and NL_Ports that have registered to be notified of state changes in other
N_Ports and NL_Ports. This registration is performed by way of the State Change Registration (SCR) Extended Link Service. An N_Port
or NL_Port can issue an RSCN to the Fabric Controller without having completed SCR with the Fabric Controller.

∙ Internal State Change Notification (SCN)

The Internal State Change Notification is used for internal state change notifications, not external changes. This is the switch logging that
the port is online or is an Fx_port. This is not what is sent from the switch to the Nx_ports.

Reading an SCN Event

time task event port cmd args
--------------------------------------------------------------------
12:05:28.116 PORT scn 7 137 00000000, 00000000, 00000008

Brocade portLogDump Reference Guide

53-1004122-01 33
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

∙ The cmd represents the scn type. Refer to State Change Notification codes on page 34 to view the cmd description.

∙ Read the args columns

– Arg 1 is dependant on the scn type:

First 16-bits (Most Significant) = The mode that the port is in. Second 16-bits (Least Significant) = The error that causes the port to be
marked OFFLINE.

∙ – Arg 2 is dependent on the scn type; it is currently not used (00000000).

– Arg 3 is the scn sub-type.

∙ Combine the scn sub-type (the third arg) and the scn type (the cmd column) to uniquely identify a particular scn. The scn type
alone is not sufficient, and is not guaranteed to be unique across all scn types.

State Change Notification codes

From the following table through Internal SCN blade states on page 44 relate to the possible State Change Notification (SCN) results
returned by the portlogdump command.

TABLE 13 Internal State Change Notification type and state

SCN value SCN Type Description
0 SWITCH_SCN switch state change
1 PORT_SCN port state change
2 UPD_SCN update state change
3 REMOTE_SCN Remote state change
4 ZONE_SCN zone check
5 FCP_SCN fcp portFCPTrigger
6 GBIC_SCN GBIC module in/out scn
7 ENV_SCN environmental events
8 SLOT_SCN slot change events
9 HA_SCN HA change events
10 DIAG_SCN DIAG change events
11 FAB_SCN fabric application events
12 LI_SCN link incident SCN
13 SEC_SCN FLOGI device security violation
14 CER_SCN Core-Edge Routing state change
15 BLADE_SCN Blade state change
16 PIC_SCN Plug-In Card state change
17 MEDIA_SCN Port Media state change
18 MMI_SCN Management Module state change
19 GE_PORT_SCN GigE Port state change
20 EX_PORT_SCN EX_Port state change
21 LE_PORT_SCN Logical E_Port state change
22 TA_SCN Trunk area state change
23 FCOE_SCN FCoE state change
24 FCOE_PORT_STATE FCoE port state change
25 FCOE_FLOGI_SCN FCoE FLOGI state change

Brocade portLogDump Reference Guide

34 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 13 Internal State Change Notification type and state (continued)

SCN value SCN Type Description
26 FCOE_MAC_RANGE FCoE MAC range state change
27 AG_SCN AG mode state change
28 VE_PORT_SCN VE port state change
29 SOFT_ZONE_SCN NS zone turned soft
30 CONFIG_SCN config state change
31 VPWWN_SCN vpwwn events
32 NP_SCN Flow Vision state change

Internal SCN sub-types

The following table lists the SCN sub-types for the Brocade proprietary SCN types.

TABLE 14 Brocade proprietary SCN sub-types

SCN value SCN Type SCN sub-type Sub-type value Description
23 FCOE_SCN None - FCoE state change
information.
24 FCOE_PORT_STATE FCoE port state change
information.
FCOE_PORT_PRESENT 1 Indicates that the FCOE
port is present.
FCOE_PORT_REMOVED 2 Indicates that the FCOE
port is removed.
FCOE_PORT_LINK_UP 4 Indicates that the FCOE
port link is up.
FCOE_PORT_LINK_DOW 8 Indicates that the FCOE
N port link is down.
25 FCOE_FLOGI_SCN None - FCoE FLOGI state change
information.
26 FCOE_MAC_RANGE None - FCoE MAC range state
change information.
27 AG_SCN AG mode state change
information.

NOTE
This SCN is
specific to AG
mode and will
not be
observed
when there is a
change in the
switch state
(from Native
to AG mode).

AG_PLOGI_TRAP 1 Indicates that PLOGI has

been trapped.

Brocade portLogDump Reference Guide

53-1004122-01 35
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 14 Brocade proprietary SCN sub-types (continued)

SCN value SCN Type SCN sub-type Sub-type value Description
AG_NPORT_SCN 2 Indicates that the N-Port
has come online.
AG_FPORT_SCN 4 Indicates that the F-port
has come online.
28 VE_PORT_SCN VE port state change
information.
VE_PORT_READY 1 Indicates that the VE port is
registered with the switch
driver.
VE_TUNNEL_UPDATE 2 Indicates that the bandwidth
change has occurred on the
extension tunnel for the VE
port.
VE_CIRCUIT_UP 4 Indicates that the extension
circuit is up.
VE_CIRCUIT_DOWN 8 Indicates that the extension
circuit is down.
VE_CFG_MISMATCH 16 Indicates that the extension
tunnel for the VE port has a
configuration mismatch
with the peer.
29 SOFT_ZONE_SCN None - NS zone turned soft
information.

NOTE
This SCN is
obsoleted.

30 CONFIG_SCN Config state change

information.
CONFIG_DEFAULT_COM 1 Indicates that the config-
PLETE default command is
executed.
CONFIG_PORT_NAME 2 Indicates that the dynamic
port name feature is
enabled or disabled.
31 VPWWN_SCN VPWWN events
information.
FPORT_VPWWN_LOGGE 1 Indicates that the VPWWN
D_IN device has logged in.
PORT_VPWWN_LOGGED 2 Indicates that the VPWWN
_OUT device has logged out.
VPWWN_SWPT_MAPPIN 4 Indicates that switch port to
G_CREATED VPWWN mapping is
created.
VPWWN_SWPT_ENABLE 8 Indicates that the VPWWN
D_AND assigned to the switch port
_MAPPING_CREATED is enabled.
VPWWN_SWPT_MAPPIN 16 Indicates that switch port to
G_DELETED VPWWN mapping is
deleted.

Brocade portLogDump Reference Guide

36 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 14 Brocade proprietary SCN sub-types (continued)

SCN value SCN Type SCN sub-type Sub-type value Description
VPWWN_SWPT_DISABLE 32 Indicates that the VPWWN
D_AND assigned to the switch port
MAPPING_DELETED is deleted.
VPWWN_AGPT_MAPPIN 64 Indicates that AG port to
G_CREATED VPWWN mapping is
created.
VPWWN_AGPT_ENABLE 128 Indicates that the VPWWN
D_AND assigned to the AG port is
_MAPPING_CREATED enabled.
VPWWN_AGPT_MAPPIN 256 Indicates that AG port to
G_DELETED VPWWN mapping is
deleted.
VPWWN_AGPT_DISABLE 512 Indicates that the VPWWN
D_AND assigned to the AG port is
_MAPPING_DELETED deleted.
VPWWN_AG_VPWWN_L 1024 Indicates that the VPWWN
OGGED_IN device has logged in
through AG port.
VPWWN_AG_VPWWN_L 2048 Indicates that the VPWWN
OGGED_OUT device visible through AG
has logged out.
VPWWN_CHANGE_SCN 4096 Indicates that the VPWWN
database has changed.
VPWWN_AG_MASTER_C 8192 Indicates that the Master
HANGED port of AG switch has
changed.
32 NP_SCN Flow Vision state change
information.
NP_FLOW_CREATE 1 Indicates that the flow is
created.

NOTE

This SCN
sub-type is
obsoleted.

NP_FLOW_DELETE 2 Indicates that the flow is

deleted.

NOTE

This SCN
sub-type is
obsoleted.

NP_FLOW_ACTIVATE 4 Indicates that the flow is

activated.

Brocade portLogDump Reference Guide

53-1004122-01 37
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 14 Brocade proprietary SCN sub-types (continued)

SCN value SCN Type SCN sub-type Sub-type value Description

NOTE

This SCN
sub-type is
obsoleted.

NP_FLOW_DEACTIVATE 8 Indicates that the flow is

deactivated.

NOTE

This SCN
sub-type is
obsoleted.

NP_FLOW_UPDATE 16 Indicates that the flow

definition is updated.

NOTE

This SCN
sub-type is
obsoleted.

NP_FLOW_RESET 32 Indicates that the flow

statistics is reset.

NOTE

This SCN
sub-type is
obsoleted.

NP_SERVICE_READY 64 Indicates that the flow vision

is registered and ready.
NP_FLOW_CLEANUP 128 Indicates that all flows are
cleaned in flow vision
database.
NP_FLOW_CTRLCFG 256 Indicates that the flow
control configuration has
changed.

NOTE

This SCN
sub-type is
obsoleted.

Brocade portLogDump Reference Guide

38 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

Internal SCN RSCN sub-types

TABLE 15 Internal SCN RSCN sub-types
SCN value Sub-Type Description
00000001 DOM_RSCN Domain RSCN
00000002 LOC_DEV_EXT_RSCN Local Device External RSCN
00000004 REM_DEV_EXT_RSCN Remote Device External RSCN
00000008 PORT_DET_RSCN N_Port detected RSCN

Internal SCN GBIC states

TABLE 16 Internal SCN GBIC states
SCN value State Description
00000001 GBIC_ONLINE GBIC is ONLINE
00000002 GBIC_OFFLINE GBIC is OFFLINE

Internal SCN update states

TABLE 17 Internal SCN update states
SCN value State Description
00000001 UPDSCN_UPD_AREA Update area
00000002 UPDSCN_DEL_AREA Delete area
00000004 UPDSCN_UPD_SCR Update state change registration
00000008 UPDSCN_UPD_VAREA Update SCN for virtual device
00000010 UPDSCN_DEL_VAREA Delete area SCN for virtual device
00000020 UPDSCN_UPD_VSCR Update state change registration for virtual
device
00000040 UPDSCN_UPD_TA_AREA Update logical trunk area
00000080 UPDSCN_DEL_TA_AREA Delete logical trunk area
00000100 UPDSCN_UPD_TA_SCR Update state change registration for trunk area
00000200 UPDSCN_UPD_PROBE Update SCN for NPIV device

Internal SCN fabric states

TABLE 18 Internal SCN fabric states
SCN value State Description
00000001 AC_PORT Link reset completed for E_Port
00000002 LR_PORT Link reset completed for non-E_Port
00000004 SW_PERSISTENT_DISABLE Switch is disabled persistently
00000008 F_SLAVE_LR_PORT Link reset completed for Slave F-Port
00000010 PT_PERSISTENT_DISABLE Port is disabled persistently
00000020 PT_TA_DISABLE Trunk area disabled
00000040 AC2_PORT Link reset completed for encryption-enabled
port
00000080 FEC_ENABLE FEC enabled on port

Brocade portLogDump Reference Guide

53-1004122-01 39
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

Internal SCN Diag states

TABLE 19 Internal SCN Diag states
SCN value State Description
00000000 DIAG_UNKNOWN Unknown/Initial Diag status
00000001 DIAG_IDLE Diagnostics are not Running
00000002 DIAG_ABORT Abort Diagnostics Test

Internal SCN SEC states

TABLE 20 Internal SCN SEC states
SCN value State Description
00000001 REM_DOMAIN_SET Domain is reachable and confirmed
00000002 REM_DOMAIN_CLEAR Domain is not reachable or not confirmed
00000004 FLOGI_DCC Device is a FLOGI device

Internal SCN CER state

TABLE 21 Internal SCN CER states
SCN value State Description
00000001 DOM_ADDS_REQD FSPF needs to re-add routes to new ports
00000002 REBALANCE_ALL Shuffle Domain Routes
00000004 IS_DOMS_ADDS_DONE Check Whether Mass Reroute is Complete
00000008 TRAFFIC_DISRUPTION_EVENT Notify FICON of Mass Reroute Event

Internal SCN MMI states

TABLE 22 Internal SCN MMI states
SCN value State Description
00000001 MMI_CONTROL
00000002 MMI_AB_SWITCH

Internal SCN slot states

TABLE 23 Internal SCN slot states
SCN value State Description
00000000 UNKNOWN
00000001 SLOT_OUT Blade has been removed
00000002 SLOT_IN Blade has been inserted but not powered on
00000004 SLOT_READY Blade is IN and has been powered on
00000008 SLOT_UP Blade is READY and has passed POST1
00000010 SLOT_ON Blade is UP and has passed POST2
00000020 SLOT_OFF Blade is ON and has been Disabled
00000040 SLOT_FAULT Blade has been marked as Faulty

Brocade portLogDump Reference Guide

40 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

Internal SCN env states

TABLE 24 Internal SCN env states
SCN value State Description
00000000 UNKNOWN
00000001 ENV_OUT removed
00000002 ENV_IN environmental hardware unit (PS/blower)
inserted
00000004 ENV_READY ready for hardware validation
00000008 ENV_UP ready for operations
00000010 ENV_ON Up and passed POST2 (unless N/A)
00000020 ENV_OFF ON and Disabled
00000040 ENV_FAULT

Internal SCN switch states

TABLE 25 Internal SCN switch states
SCN value State Description
00000001 DOMAIN_VALID Switch gets a domain
00000002 DOMAIN_INVALID Switch loses its domain
00000004 DOMAIN_REACHABLE Domain is reachable
00000008 DOMAIN_UNREACHABLE Domain is not reachable
00000010 SW_ONLINE Switch is online
00000020 SW_OFFLINE switch is offline
00000040 CFG_CHANGED Effective ZoneSet has changed
00000080 PASSWD_CHANGED Password has changed
00000100 FWN_NOTIFY Firmware has changed
00000200 PID_CHANGED PID Format has changed
00000400 ZONE_CHANGED Zoning database has changed
00000800 ROUTE_CHANGE Route has changed
00001000 DOMAIN_CAP_AVAILABLE Domain Capabilities are available
00002000 SERVICESTAT_START Service Statistics Start
00004000 SERVICESTAT_START Service Statistics Stop
00008000 FAB_SIZE_LIMIT_VIOLATION Fabric Size Threshold Crossed

Internal SCN HA states

TABLE 26 Internal SCN HA states
SCN value State Description
00000001 GO_ACTIVE_SCN Make This CP ACTIVE
00000002 GO_STANDBY_SCN Make This CP STANDBY
00000004 DEBUG_SCN No Explanation
00000008 SWITCH_0_SCN No Explanation
00000010 SWITCH_1_SCN No Explanation
00000020 SWITCH_BOTH_SCN No Explanation

Brocade portLogDump Reference Guide

53-1004122-01 41
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 26 Internal SCN HA states (continued)

SCN value State Description
00000040 CP_0_SCN No Explanation
00000080 CP_1_SCN No Explanation
00000100 FC0_IP_SCN No Explanation
00000200 FC1_IP_SCN No Explanation
00000400 HTBT_UP_SCN CP HeartBeat Detected
00000800 HTBT_DOWN_SCN CP HeartBeat Not Detected
00001000 EVENT_SCN No Explanation
00002000 SWD_APP_NOT_RESPONDING Application has not updated the Software
Watchdog
00004000 SWD_SWDD_DATA_COLLECT Software Watchdog Daemon Data Collection
00008000 GO_REBOOT_SCN

Internal SCN zone states

TABLE 27 Internal SCN zone states
SCN value State Description
00000001 ZONE_CHECK_WWN
00000002 ZONE_CHECK_PORT
00000004 ZONE_CHECK_CLEAR

Internal SCN FCP states

TABLE 28 Internal SCN FCP states
SCN value State Description
00000001 FCPMSG_PROBE start probing
00000002 FCPMSG_FLUSH stop probing

Internal SCN port states

TABLE 29 Internal SCN port states
SCN value State Description
00000000 UNKNOWN port state UNKNOWN
00000001 ONLINE port is ONLINE
00000002 OFFLINE port is OFFLINE
00000004 TESTING port is running diagnostics
00000008 FAULTY port marked FAULTY
00000010 E_PORT port is an E_PORT
00000020 F_PORT port is an F_PORT
00000040 SEGMENTED port is SEGMENTED
00000080 T_PORT port is a TRUNK port, not trunk master
00000100 LIP_ONLINE LIP has occurred
00000200 FORCE_OFFLINE Force OFFLINE a port that is already OFFLINE
00000400 BUF_ONLINE port is ONLINE by acquiring free buffers

Brocade portLogDump Reference Guide

42 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 29 Internal SCN port states (continued)

SCN value State Description
00000800 BUF_OFFLINE port is OFFLINE due to lack of buffers
00001000 OFFLINE_NEW_REASON port is debounced and still OFFLINE with new
reason
00002000 BUF_DEGRADED port is degraded due to lack of buffers
00004000 BUF_UPDATE degraded bitmap needs to be cleared and
updated
00008000 EPORT_CHANGE Promote TRUNK_SLAVE to TRUNK_MASTER
00010000 PLOGI_RCVD Switch has received a PLOGI
00020000 LOGO_RCVD Switch has received a LOGO
00040000 XCHANGE_ABORT_NOTIFY Send SCN because the exchange has been
aborted
00800000 F_Port ELP start Start F_Port trunking
01000000 Trunked F_Port The port is trunked F_Port
02000000 Dynamic Area Update A dynamic area has been assigned or cleared
04000000 D_Port Test Status Change in D_Port test status
08000000 D_Port The port is D_Port
10000000 Auto D_Port Dynamic or on-demand D_Port

Internal SCN LE port states

TABLE 30 Internal SCN LE port states
SCN value State Description
00000001 LE_ONLINE Logical E_Port Online
00000002 LE_OFFLINE Logical E_Port Offline
00000004 LE_PORT Port is a Logical E_Port

Internal SCN GE port states

NOTE
The following table is also applicable for 10 GbE ports.

TABLE 31 Internal SCN GE port states

SCN value State Description
00000001 GE_TCP_CONN_UP GigE TCP Connection is UP
00000002 GE_TCP_CONN_DOWN GigE TCP Connection is DOWN
00000004 GE_NTP_SYNC_UP GigE NTP Sync is UP
00000008 GE_NTP_SYNC_DOWN GigE NTP Sync is DOWN
00000010 GE_AUTH_FAILURE GigE Authorization Failed
00000020 GE_PORT_READY GigE Port is Ready
00000040 GE_TUNNEL_UP GigE Tunnel is UP
00000080 GE_TUNNEL_UP GigE Tunnel is DOWN
00000100 GE_TUNNEL_CFG_MISMATCH GigE Tunnel Configuration Mismatch

Brocade portLogDump Reference Guide

53-1004122-01 43
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

Internal SCN blade states

TABLE 32 Internal SCN blade states
SCN value State Description
00000001 BLADE_UNKNOWN Blade type is not known
00000002 BLADE_POWER_ON Blade is powered on
00000004 BLADE_INIT_DONE Blade is initialized
00000008 BLADE_OPERATIONAL Blade is operational
00000010 BLADE_BOOT_SUCCESS Blade boot is successful
00000020 BLADE_BOOT_FAILURE Blade boot failed
00000040 BLADE_UN_INST Blade uninstantiated
00000080 BLADE_POWER_OFF Blade power off

Loop State Change Notification reason codes for LIP

TABLE 33 Loop SCN reason codes (LIP)
LIP SCN value Description
8001 retry loop init
8002 start loop after gaining sync
8003 restart loop after port reset
8004 lip the loop after loop time-out
8005 retransmitting LIP in ARBF0
8006 lip the loop if OPN(x,y) returns
8007 start loop when transit out of G_Port
8008 start loop if self loopback
8009 per N_Port's FLA LINIT ELS
800a per N_Port's FLA LPC ELS
800b per QL's LOOP_LIP ioctl
800c per QL's LOOP_INIT ioctl
800d lip due to loop rx buffer overflow
800e start loop because of loop diag
8010 per new Phantoms being added (IPO)
8011 bloomInitRetry - loop init timed out
8012 bloomInitRetry - stuck at init state
8013 bloomInitRetry - no RSVD mini-buf for LISM
8014 bloomInitRetry - not pt-to-pt capable
8015 bloomInitRetry - no LISM rx in 2 AL_TIME
8016 bloomInitRetry - RXFIFO during loopinit
8017 bloomInitRetry - Retry LIP - Lock Lport lock is set
8019 bloomLismcleanup - tx q is not empty
801a lip due to loop rx buffer underflow
801b lip due to loop rx buffer overflow
801c lip due to XMITTED_CLOSE state timeout
801d lip due to TRANSFER state timeout

Brocade portLogDump Reference Guide

44 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 33 Loop SCN reason codes (LIP) (continued)

LIP SCN value Description
801e In Loop Init, Retry needed
801f LIP received from remote port
f7f7 No valid AL_PA
f8f7 loop port failure, requesting initialization

Speed negotiation
TABLE 34 Speed negotiation code command
Code Value (hex) Description
NC 0x01 Negotiation complete with speed 1 Gbps
NC 0x02 Negotiation complete with speed 2 Gbps
NC 0x04 Negotiation complete with speed 4 Gbps
NC 0x08 Negotiation complete with speed 8 Gbps
NC 0x1a Negotiation complete with speed 10 Gbps
NC 0x10 Negotiation complete with speed 16 Gbps
NM N/A Negotiate master
NF N/A Negotiate follow
WS N/A Signal is okay and actual start of SN - "trigger
for start"

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Dec 11 23:55:03 2009
23:55:11.133 SPEE sn 1 WS 00000000,00000000,00000000
23:55:11.429 SPEE sn 1 NM 00000000,00000000,00000000
23:55:11.429 SPEE sn 1 NF 00000000,00000000,00000000
23:55:11.429 SPEE sn 1 NC 00000004,00000000,00000000

I/O control (IOCTL)

An I/O control (IOCTL) event is an internal message that gives information about the port and the stage of bring-up or take down of the
ports. The following table provides a complete listing of the IOCTL codes.

TABLE 35 I/O FOS control codes

Ioctl Code Description
01010001 E_Port flow control mode
01010002 Set diag flag
01010003 Clear diag flag
01010004 Get E_Port VCs credits
01010005 set E_Port VCs credits
01010006 Set line loopback port
01010007 Get port topology
01010008 Set port topology
01010009 LED control

Brocade portLogDump Reference Guide

53-1004122-01 45
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 35 I/O FOS control codes (continued)

Ioctl Code Description
0101000a Port is an E_Port
0101000b Port is an F_Port
0101000c Port is segmented
0101000d Take port offline
0101000e Take port into LR
0101000f Take port down then up
01010010 Is a port disabled?
01010011 Get port type
01010012 Get mode of operation
01010013 Set RNID related info
01010014 reload Back-end port VC credit
01010015 Port is true EPORT?
01010016 load Back-end port credit
01010017 activate the port
01010018 update led mgmt ctrl
01010019 HA recovery check
0101001a Upper layer faulted port
0101001b set inter-frame gap
0101001c get inter-frame gap
0101001d Unset line loopback port
0101001e Unset frame loopback port
0101001f Check consistency bet
01010020 Get E_Port credits recov
02010001 Get physical state
02010002 Set physical state
02010003 Get GBIC type
02010004 Module val result
02010005 Set or clear bypass mode
03010005 set auto sn mode to arg1 value
03010006 get pt spd ala admin.h defines
03010007 get pt spd cap ala admin.h
03010008 get pt spd led color
03010009 set pt spd led color
04010008 Get Loop Bitmap
04010009 get blm_my_alpa table
0401000a get blm_plt_cam table
0401000b get blm_plt_alpa table
0401000c Loop port (or looplet) bypass
0401000d FLA Loop INITializing
0401000e FLA Loop Port Control
0401000f FLA Loop Status

Brocade portLogDump Reference Guide

46 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 35 I/O FOS control codes (continued)

Ioctl Code Description
04010010 LPORT ALPA bitmap
04010011 LIP the loop, TX_UNAVAIL on/off
04010012 send MRK primitive signal
04010013 Undo the FPORT ioctl
04010014 Set alpa in blm_alpa_avail[]
04010015 Clr alpa in blm_alpa_avail[]
05010001 continue link init/reset
06010002 Send MARK prim onto wire
06010003 Get MARK timestamps
06010004 Add port to the trunk
06010005 Get all trunk masters in Quad
06010006 Update MARK timestamp with RMT
06010007 Check whether port is trunkable
06010008 Enable trunking if possible
06010009 Get trunking group info
0601000a Find the master port
0601000b Get the master port
0601000c Get ports within a quad
0601000d Check whether port has a master
0601000e Get the bandwidth of an ISL
07010001 processing filter stage 1
07010002 processing filter stage 2
07010003 s/w frame filtering
07010004 enable hardware zoning
07010005 disable hardware zoning
07010006 add members to port's zone
07010007 del member from port's zone
07010008 add a zone type (new)
07010009 add zone group (new)
0701000a enable all pt zoning (new)
0701000b reset all pt zoning (new)
0701000c disable all pt zoning (new)
0701000d free zoning token (new)
0701000e setup PLOGI cmd trap (new)
0701000f setup report lun trap (new)
07010010 clear port zoning (new)
07010011 get rcv/orig id (new)
07010012 apply lun info (new)
07010013 exclude pt from zoning (new)
07010014 reset zone for port
07010015 propogate rscn info to flt

Brocade portLogDump Reference Guide

53-1004122-01 47
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 35 I/O FOS control codes (continued)

Ioctl Code Description
07010016 set filtering features
07010017 get filtering features
07010018 reset all port zoning (new)
07010019 get zone type data
0701001a get zone group data
0701001b check zone group data
0701001c load sidcam (diag)
0701001d load didcam (diag)
0701001e load lun offset (diag)
0701001f load zone grp ram (diag)
07010020 ld zone horizontally diag)
07010021 load flt sel (diag)
07010022 load field def (diag)
07010023 load action regs (diag)
07010024 get flt stats (diag)
07010025 clr all filtering hw (diag)
07010026 enable frame flt (diag)
07010027 disable frame flt (diag)
07010028 Reg frozen process hndl
07010029 Load Group control
0701002a portCamShow support and more
0701002b portCamShow
0701002c Add a filter counter
0701002d Delete a filter counter
0701002e number of filter hit count
0701002f ADD get perf filter references
07010030 clear all filter monitors
07010031 clear all filter status
07010032 get perf filter descriptions
07010033 Get all Fltr data
07010034 Add a filter for FICON/CUP
07010035 Delete a filter for FICON/CUP
07010036 Check whether an SID/DID pair are zoned together
07010037 Add a filter for port mirror
07010038 Delete a filter for port mirror
07010039 Get fltr desc for port mirror
0701003a Verify fltr desc for port mirror
0701003b Verify fltr desc port mirror
0701003c Add/delete discard fltr
0701003d Process offline port
0701003e del zone group

Brocade portLogDump Reference Guide

48 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 35 I/O FOS control codes (continued)

Ioctl Code Description
0701003f FCACC ingress filter config
07010040 FCACC egress filter config
07010041 Zone FCACC Add Flow
07010042 Zone FCACC Remove Flow
07010043 Zone FCACC Remove PID
07010044 Zone FCACC Soft
07010045 FCACC cleanup
07010046 Filter FCACC HA egress cfg
07010047 Enable FISOFT Zoning
07010048 Zoning RSCN New
07010049 Zone Enable All
0701004a Zone Disable All
0701004b Zone Soft All
08010001 add unicast route
08010002 delete unicast route
08010003 add multicast route
08010004 delete multicast route
08010005 unicast routing table done
08010006 add area route
08010007 del area route
08010008 get domain dest port (diag)
0801000a add next hop
0801000b add multiple routes
0801000c add path
0801000d delete path
0801000e add route
0801000f delete route
08010010 clear route
08010011 config virtual link
08010012 config. route policy
08010013 config vc mode
08010014 config vc setting
08010015 config chip tables
08010016 config port tables
08010017 verify add route
08010018 verify delete routes
08010019 configure if
0801001a verify nexthop
0801001b verify routing config
0801001c add loopback area rt
0801001d configure STAG

Brocade portLogDump Reference Guide

53-1004122-01 49
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 35 I/O FOS control codes (continued)

Ioctl Code Description
08010021 add portion of route
08010022 remove portion of route
08010023 read routing table, assuming port-based routing
08010024 set blm_port2vc value
08010025 FCACC Cfg Setup
08010026 FCACC Cfg Cleanup
12010000 Set Ex_Port Edge ID
12010001 Get Ex_Port Edge ID
12010002 FCR Set SFID
12010003 FCR Clear SFID
12010004 Create Backbone Translate Domain
12010005 Add edge domain
12010006 Delete Edge domain
12010007 Purge Edge Domain
12010008 Add Fabric Route
12010009 Delete Fabric Route
1201000a Purge Fabric Route
1201000b Add Proxy Device
1201000c Delete Proxy Device
1201000d Purge Proxy Device
1201000e Configure ELS Trap
1201000f Configure FCR Mode
12010010 Configure Routing Policy
12010011 Set Backcone Fabric ID
12010012 FCR Get DFAB EGIDS
12010013 Get Backbone Fabric ID
12010014 Get Fabric Info
12010015 Get Fabric Routing Info
12010016 Get Proxy Device Info
12010017 FCR Set Local EGID
12010018 FCR LE XD Reachable
12010019 FCR LE XD Unreachable
09010001 get buffer and port
09010002 set avail buf intr
09010003 return buffer
09010004 return Tx buffer
09010005 get available BB_Credit
09010006 get bb credit for the Fx_PORT
09010007 diag return buffer
09010008 get long distance calculations
09010009 Enable MARK retransmission

Brocade portLogDump Reference Guide

50 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 35 I/O FOS control codes (continued)

Ioctl Code Description
09010010 apply rate limit
09010011 return an RRDY before the poll
0901000a Disable MARK retransmission
0901000b Send MARK primitive with LRTT (link round trip timer) enabled
0901000c Save link round trip timer from ASIC
0901000d Save the credits from link round trip timer from other switch
0901000e Check if port config should be allowed
0901000f get port buffer allocations
0a010001 Get F_Port Error Status
0a010002 Get Fl_Port Error Status
0a010003 port admin stuff
0a010004 clr hw stat SRAM
0a010005 get common hw stats
0a010006 get loop hw stats
0a010007 get hw frame stats
0a010008 get hw error stats
0a010009 get intr stats
0a01000a pt perf calculation
0a01000b port perf calculation
0a01000c Add a SID-DID pair
0a01000d Del a SID-DID pair
0a01000e Get list of EE keys
0a01000f Get current EE mask
0a010010 Set the SID-DID pair
0a010011 Clr CRC cnt for ALPA
0a010012 Get CRC cnt for ALPA
0a010013 Snt wd cnt SID-DID
0a010014 Rcv wd cnt SID-DID
0a010015 CRC err cnt SID-DID
0a010016 clear all EE monitors
0a010017 clear all EE status
0a010018 get ticks when BB credit == 0
0a010019 get STATSET
0a010020 Replace all SID-DID pairs
0a010021 Clear CRC cntrs for multiple AL_PAs
0a010022 Get CRC cntrs for multiple AL_PAs
0a010023 Clear the TX and/or Rx word counts
0a010024 Get all EE data
0a010025 Trigger the Perf Poll
0a010026 get chip stat
0a010027 clear chip stats

Brocade portLogDump Reference Guide

53-1004122-01 51
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 35 I/O FOS control codes (continued)

Ioctl Code Description
0a010028 are any virtual ports online
0a010029 FC Acceleration allowed
0a01002a FC Accel ports
0a01002b Switch port cap
0a01002c 1250 FC Accel Add Flow
0a01002d 1250 FC Accel Remove Flow
0a01002e 1250 FC Accel Remove PID
0a01002f 1250 FC Accel Port Offline
0a01002c add sid-did PM monitor
0a01002d delete sid-did PM monitor
0a01002e start PM monitor polling
0a01002f stop PM monitor polling
0a010030 get sid-did PM statistics
0a010031 clear sid-did PM statistics
0a010032 get all PM statistics
0a010033 clear all PM statistics
0a010034 get PM indices/references
0a010035 get link table size
0b010001 cleanup dma
0b010002 send msg
0b010003 control frame reception
0c010001 bring port online
0c010002 Reset ASIC happened
0c010003 Initialize the chip
0c010004 Mark chip and ports initialized
0c010005 fault port due to excessive int.
0c010006 init hold time registers for every chip in the group
0c010007 initialize XCP connection
0c010008 tear down XCP connection
0c010009 initialize PCI config params for chip
0c01000a fwdl 2 iscsi chip
0c01000b BP warm start
0c01000c Poll in case of excessive chip interrupts
0c01000d Start the polling between cpsas and 1250
0d010001 No longer used
0d010002 enable port intr
0d010003 disable pt intr
0d010004 check if pt intr pending
0d010005 enable chip intr
0d010006 disable chip intr
0d010007 check if chip intr pending

Brocade portLogDump Reference Guide

52 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 35 I/O FOS control codes (continued)

Ioctl Code Description
0d010008 halt chip called by blade fault
0e010001 clr ASIC offline bit
0e010002 chk ASIC blade rdy bit
0e010003 set ASIC blade rdy bit
0e010004 clr ASIC blade rdy bit
0e010005 check ASIC PIC-ready bit
0e010006 set ASIC PIC-ready bit
0e010007 clear ASIC PIC-ready bit
10010001 set the bloom status
10010002 Execute I2C GBIC cmd
10010003 disable SID/DID chk
10010004 Verify ASIC can be accessed
10010005 modify proc entries for asic
10010006 get ASIC Register Map
10010007 get ASIC Registers
10010008 domain name is known
10010009 mcast routing table done
1001000a update property of the port
1001000b add the ASIC driver msg to appropriate queue
1001000c set area ASIC PORT ID ADDR Reg
1001000d log LLI and swc data
1001000e agmode
1001000f Set Condor cfg
10010010 Additional proc entry link
10010011 For AG trunked ports, set route to logically online
11010001 get fail detect lgc stat
11010002 set fail detect ctrl bit
11010003 clr fail detect ctrl bit
11010004 set Rx-to-Tx parity ctrl
11010005 get Rx-to-Tx parity err status
11010006 enable fail detect intr
11010007 disable fail detection interrupt
11010008 check for fail detection interrupt
11010009 doing BZIO polling
1101000a Get Device Info
1101000b set up pt loop diag mode
1101000c loop port bypass the ALPD
1101000d loop port enable the ALPD
1101000e diag message output
1101000f Chk if FL_Port diag hooked-up
11010010 chk if FL_Port a lb slave

Brocade portLogDump Reference Guide

53-1004122-01 53
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 35 I/O FOS control codes (continued)

Ioctl Code Description
11010011 set AL_PA for FL lb test
11010012 Disable FC-AL tx front-end
11010013 Enable FC-AL tx front-end
11010014 Set Flow Control Mode
11010015 ptXxxShow
11010016 rm all phantom nodes pt
11010017 add phantom dev (loop only)
11010018 xlate phantom sid and did
11010019 add phantom node for remote did
1101001a test phantom for (S_ID, D_ID)
1101001b add a phantom device (loop only)
1101001c remove a phantom device
1101001d get phantom AL_PA by address ID
1101001e get address ID by phantom AL_PA
1101001f Looplet init (send LIPs)
11010020 Looplet init sequence
11010021 Looplet init AL_PA bitmaps
11010022 Looplet unicast routes
11010023 get pub/pri/phantom cnts
11010024 F_Port disable port tx before ACC
14010800 get debug data
14010801 asic swc unit tests, not used yet
14010900 test recovery
15010800 get debug data
15010801 asic swc unit tests, not used yet
15010900 test recovery
13010000 IPSd ioctl
13010001 Normal FC Frames TX to 1250
13010002 dump BI regs per ptRegShow <BI>
13010003 dump BI regs per ptRegShow <BI>
13010004 Trigger 1250 to dump error stats
13010005 destined for BI per VE LINK_UP
13010006 destined for GigE port tunnel
13010007 dump GE stats
13010008 dump GE stats
13010009 dump GE stats and CP wont block
13010099 1250 HeartBeat Message
16010001 Copy regs to 1250 shared mem
16010002 Copy stats to 1250 shared mem
16010003 Clear Anzio/Sflipper port stats
16010004 1250 heartbeat message

Brocade portLogDump Reference Guide

54 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 35 I/O FOS control codes (continued)

Ioctl Code Description
16010005 Send message to SAS Driver
16010006 Pass the BP config
16010007 Enable the GE port - only for Diag
16010008 Disable the GE port - only for Diag
16010009 run BIST test

Extended Link Service (ELS)

An Extended Link Service (ELS) request is sent to the destination N_Port to perform the requested function or service.

∙ The R_CTL field of an Extended Link Service request is set to 0x22.

∙ The R_CTL field of the Extended Link Service reply is set to 0x23.

∙ The Type field for both requests and replies is 0x01 (portlogdump trace does not provide the TYPE information).

The command code for an ELS is always the first word of the payload (word 6) for both the request and reply.

There are 2148 bytes in a frame, and the portlogdump command captures a portion of the frame.

For Tx and Rx events, the first Arg field obtains the portion of the header and one word of the payload, word 6. Arg 1, 2, and 3 belong to
the FC-PH header (word 0, 1, 4 = R_CTL, D_ID, S_ID, OX_ID, RX_ID). The last argument (fourth argument) belongs to the payload.
Refer to ELS example 1 on page 57.

ELS command codes

The following table provides a complete reference of the ELS command code values.

TABLE 36 ELS command codes

ELS Command Abbreviation Description
01000000 RJT Reject
02000000 ACC Accept
03000000 PLOGI N_Port Login
04000000 FLOGI F_Port Login
05000000 LOGO Logout
06000000 ABTX Abort Exchange
07000000 RCS Read Connection Status
08000000 RES Read Exchange Status Block
09000000 RSS Read Sequence Status Block
0A000000 RSI Request Sequence Initiative
0B000000 ESTS Establish Streaming
0C000000 ESTC Estimate Credit
0D000000 ADVC Advise Credit
0E000000 RTV Read Timeout Value
0F000000 RLS Read Link Status
10000000 ECHO ECHO

Brocade portLogDump Reference Guide

53-1004122-01 55
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 36 ELS command codes (continued)

ELS Command Abbreviation Description
11000000 TEST Test
11010000 LISM Select Master
11020000 LIFA Fabric Assigned
11030000 LIPA Previously Acquired
11040000 LIHA Hard Assigned
11050000 LISA0 Soft Assigned (old)
11050100 LISA1 Soft Assigned (new)
11060000 LIRP Report Position
11070000 LILP Loop Position
12000000 RRQ Reinstate Recovery Qualifier
20100000 PRLI Process Login
21100000 PRLO Process Logout
22000000 SCN State Change Notification
23000000 TPLS Test Process Login State
24000000 TPRLO Third Party Process Logout
30000000 GAID Get Alias ID
31000000 FACT Fabric Activate Alias ID
32000000 FDACT Fabric Deactivate Alias ID
33000000 NACT N_Port Activate Alias ID
34000000 NDACT N_Port Deactivate Alias ID
40000000 QoSR Quality of Service Request
41000000 RVCS Read Virtual Circuit Status
50000000 PDISC Discover N_Port Service Parameters
51000000 FDISC Discover F_Port Service Parameters
52000000 ADISC Discover Address
53000000 RNC Report Node Capability
54000000 FARP FC Address Resolution Protocol
55000000 FARP_REPLY FC Address Resolution Protocol Reply
60000000 FAN Fabric Address Notification
61xxxxxx RSCN Registered State Change Notification
62000000 SCR State Change Registration
70000000 LINIT Loop Initialize
71000000 LPC Loop Port Control
72000000 LSTS Loop Status
77000000 RTIN Request Topology Information
78000000 RNID Request Node Identification Data
79000000 RLIR Registered Link Incident Record
7A000000 LIRR Link Incident Record Registration
7B000000 SLR Scan Loop Remote
7D000000 RPSC Report Port Speed Capabilities
7E000000 QSA Query Security Attributes

Brocade portLogDump Reference Guide

56 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 36 ELS command codes (continued)

ELS Command Abbreviation Description
7F000000 GCAP Get FICON Capabilities

ELS example 1
This example shows a FLOGI frame to the fabric F_port (R_CTL=0x22, ELS Request; D_ID=0xfffffe, fabric F_port; S_ID=0x000000).
S_ID = 0 indicates that the attaching device does not yet have a fabric address.

args

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Dec 11 23:55:03 2009
23:55:11.507 PORT Rx3 128 116 22fffffe,00000000,2018ffff,04000000

ELS example 2
This example shows how the FLOGI frame from the switch to the device (R_CTL=0x23, Extended Link Services Reply;
D_ID=0x638000, fabric F_port; S_ID=0xfffffe) is accepted. D_ID=0xd638000 is the assignment of the fabric address.

args

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Dec 11 23:55:03 2009
23:55:11.507 PORT scn 128 1 00000000,00000000,00000001
23:55:11.507 PORT scn 128 22 00000000,00000000,00000010
23:55:11.507 PORT scn 128 1 00000000,00000000,00000020
23:55:11.507 PORT scn 128 22 00000000,00000000,00000008
23:55:11.548 PORT Tx3 128 116 23638000,00fffffe,20188306,02000000

Switch Fabric Internal Link Services (SW_ILS)

Internal Link Services refers to the service that allows a switch to communicate with itself. A Domain Controller (or embedded port)
communicates to receive updated information.

When portlogdump shows a Well Known Address communicating to another Well Know Address, such as FFFD to FFFD, or FFFCxx to
FFFCxx (xx being the domain ID), refer to ILS for information about that communication. Refer to SW_ILS examples on page 60.

Brocade-specific SW_ILS command codes

TABLE 37 Switch Fabric Internal Link Services command codes
Value Code Description
0x 14000000 IE_HLO Routing: Hello
0x 15000000 IE_LSU Routing: Link State Update
0x 16000000 IE_LSA Routing: Link State Ack
0x 19000000 IE_GAID Get Alias ID
0x 1a000000 IE_RAID Return Alias ID
0x 1b000000 IE_RSCN Inter-switch RSCN
0x 1c000000 IE_INQ Inquiry

Brocade portLogDump Reference Guide

53-1004122-01 57
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 37 Switch Fabric Internal Link Services command codes (continued)

Value Code Description
0x 1d000000 IE_RTE Interswitch Routing Information
0x 1e000000 DRLIR Distribute Registered Link Incident Records
0x 1f000000 CSW_RSCN Consolidated Switch RSCN (Vendor-Specific)
0x 20000000 DSCN Disconnect Class 1 Connection
0x 21000000 LOOPD Detect Queued Class 1 ConnectionRequest
Deadlock
0x 22000000 MR Merge Request
0x 23000000 ACA Acquire Change Authorization
0x 24000000 RCA Release Change Authorization
0x 25000000 SFC Stage Fabric Configuration
0x 26000000 UFC Update Fabric Configuration
0x 3000xxxx ESC Exchange Switch Capabilities
0x 31000000 ESS Exchange Switch Support
0x70000000 IE_ZONE Inter Exchange Zone Update (Vendor-Specific)
0x71000000 IE_SGROUP Inter Exchange Groupwise Commands
0x72000000 IE_SEC Inter Exchange Security Entry
0x73000000 IE_SLAPRequest Inter Exchange SLAP Request
0x74000000 IE_SLAPAcknowledge Inter Exchange SLAP Acknowledge
0x75000000 IE_SLAPConfirm Inter Exchange SLAP Confirm
0x76000000 IE_SLAPDone Inter Exchange SLAP Done
0x77000000 IE_SLAPReject Inter Exchange SLAP Reject
0x78000000 IE_RCS_INFO Inter Exchange Reliable Commit Service Info
0x79000000 IE_RCS_ACA Inter Exchange RCS Acquire Change
Authorization
0x7a000000 IE_RCS_SFC Inter Exchange RCS Stage Fabric Config
0x7b000000 IE_RCS_UFC Inter Exchange RCS Update Fabric Config
0x7c000000 IE_RCS_RCA Inter Exchange RCS Release Change
Authorization
0x7d000000 IE_RCS_TCO Inter Exchange RCS Transfer Commit
Ownership
0x7e000000 IE_RDTS Inter Exchange RDTS Request
0x7f00000 IE_ECP Inter Exchange Exchange Credit Parameters
Request
Trunking Support Code
0x90000000 IE_EMT Inter Exchange Read MARK Timestamp (VU)
0x91000000 IE_ETP Inter Exchange Exchange Trunking Parameter
External Link Services
0x81000000 SW_RJT Reject
0x82000000 SW_ACC Accept
0x83000000 SW_CFN Change Fabric Name
0x84000000 SW_WTV Write Timeout Value
0x850000 SW_ON Offline Notification

Brocade portLogDump Reference Guide

58 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

SW_ILS reject reason codes (SW_RJT)

TABLE 38 FC_SW: Reject Reason Codes (SW_RJT)
Code Abbreviation Description
0x01 SW_INVALID_COMMAND Invalid ELS Command Code - The command
code is not recognized by the recipient.
0x02 SW_INVALID_VERSION Invalid revision level. The recipient does not
support the specified revision level.
0x03 SW_LOGICAL_ERROR Logical Error - The request identified by the
command code and the payload content is
invalid or logically inconsistent for the conditions
present.
0x04 SW_INVALID_IU_SIZE Invalid payload size - The size of the payload is
inconsistent with the command code and/or any
length fields in the payload.
0x05 SW_LOGICAL_BUSY Logical Busy - The port is unable to perform the
request at this time. Busy reason explanation
code:

01 - PHYSICAL_N_PORT_BUSY

03 - N_PORT_RESOURCE_BUSY
0x07 SW_PROTOCOL_ERROR Protocol Error - An error has been detected that
violates FC-2 protocols and is not covered by
another reason code.
0x09 SW_CANT_PERFORM_REQ Unable to perform command request - The
recipient is unable to perform the request at this
time.
0x0b SW_NOT_SUPPORTED Command not supported - The recipient does
not support the ELS command.
Other value Reserved
0xff SW_VENDOR_UNIQUE Vendor-unique field indicates an error condition.

TABLE 39 FC-SW (SW-RJT): Reject Reason Explanation Codes

Code Abbreviation Explanation
0x00 SW_NO_EXPLANATION No additional explanation
0x01 SW_CLASS_F_ERROR Class F Service Parameter error
0x03 SW_CLASS_N_ERROR Class N Service Parameter error
0x04 SW_UNKNOWN_CTL_MODE Unknown Flow Control code
0x05 SW_UNKNOWN_CTL_PARAMS Invalid Flow Control Parameters
0x0d SW_INVALID_PORT_NAME Invalid port name
0x0e SW_INVALID_SWITCH_NAME Invalid switch name
0x0f SW_TOV_MISMATCH R_A_TOV or E_D_TOV mismatch
0x10 SW_INVALID_DLIST Invalid Domain_ID_List
0x19 SW_COMMAND_IN_PROGRESS Command already in progress
0x29 SW_NO_MORE_RESOURCES Insufficient resources available
0x2a SW_NO_DOMAIN_ID Domain_ID not available
0x2b SW_INVALID_DOMAIN_ID Invalid Domain_ID
0x2c SW_NON_SUPPORTED_REQ Request not supported

Brocade portLogDump Reference Guide

53-1004122-01 59
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 39 FC-SW (SW-RJT): Reject Reason Explanation Codes (continued)

Code Abbreviation Explanation
0x2d SW_NO_LINK_PARAMETERS Link Parameters not yet established
0x2e SW_NO_CONT_DOMAIN_IDS Requested Domain_IDs not available
0x2f SW_EPORT_ISOLATED E_Port is Isolated
0x30 SW_CANT_TRUNK Cannot trunk
0x3a SW_EPORT_DISABLED E_Port disabled
0x3b SW_SLAP_NOTDONE Slap not done
0x3c SW_RDTS_NOTDONE Zoning is not done
0x3d SW_RDTS_NOTDONE RDTS not done

SW_ILS examples
The following ILS examples are explained in the following ways:

∙ The first section (labeled "Example" ) shows the entire example, and the subsequent sections are broken up line by line.

∙ For a text description of the events displayed in this example, refer to "Example summary" at the end of the section.

Hello frame example

Frame information

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Dec 11 23:55:03 2009
23:55:08.063 PORT Tx 1 40 02fffffd,00fffffd,8b3effff,14000000
23:55:08.064 PORT Rx 1 0 c0fffffd,00fffffd,8b3e0b1a,00000001

Args for output line 1

02fffffd,00fffffd,8b3effff,14000000

TABLE 40 Argument breakdown for example (line 1)

Arg1 02fffffd Arg2 00fffffd Arg3 8b3effff Arg4 14000000
02 = RC_CTL (request) 00 = Identifier 8b3e = OX_ID 14000000 = SW_ILS command
code (Hello). Refer to Brocade-
fffffd = D_ID (Fabric controller) ffffd = S_ID (Fabric controller) ffff = RX_ID
specific SW_ILS command codes
on page 57.

Args for output line 2

c0fffffd,00fffffd,8b3e0b1a,00000001

TABLE 41 Argument breakdown for example (line 2)

Arg1 c0fffffd Arg2 00fffffd Arg3 8b3e0b1a Arg4 00000001
CO = 00 = Identifier 8b3e = One frame acknowledged using
standardized code.
RC_CTL (Link control OX_ID
acknowledged)
fffffd = ffffd = 0b1a =

D_ID (Fabric controller) S_ID (Fabric controller) RX_ID

Brocade portLogDump Reference Guide

60 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

Example summary
The Fabric Controller from one switch sends a handshake "hello" to the other Fabric Controller on the switch. The handshake is
acknowledged.

Trunking frame example

Frame information

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Dec 11 23:55:03 2009
01:18:48.281 PORT Tx 0 24 02fffffd,00fffffd,0c93ffff,90000014
01:18:48.282 PORT Rx 0 0 c0fffffd,00fffffd,0c9308f5,00000001
01:18:48.288 PORT Rx 0 24 03fffffd,00fffffd,0c9308f5,02000014
01:18:48.288 PORT Tx 0 0 c0fffffd,00fffffd,0c9308f5,00000001
Output line 1
01:18:48.281 PORT Tx 0 24 02fffffd,00fffffd,0c93ffff,90000014

Args for output line 1

02fffffd,00fffffd,0c93ffff,90000014

TABLE 42 Argument breakdown for example (line 1)

Arg1 02fffffd Arg2 00fffffd Arg3 0c93ffff Arg4 9000014
02 = RC_CTL (request) 00 = Identifier 0c93 = OX_ID 9000014 = Trunking IU Preamble
fffffd = D_ID fffffd = S_ID ffff = RX_ID

Args for output line 2

c0fffffd,00fffffd,0c9308f5,00000001

TABLE 43 Argument breakdown for example (line 2)

Arg1 c0fffffd Arg2 00fffffd Arg3 0c9308f5 Arg4 00000001
cO = RC_CTL (Link control 00 = Identifier 0c93 = OX_ID One frame acknowledged using
acknowledged) standardized code.
fffffd = D_ID fffffd = S_ID 08f5 = RX_ID

Args for output line 3

03fffffd,00fffffd,0c9308f5,02000014

TABLE 44 Argument breakdown for example (line 3)

Arg1 03fffffd Arg2 00fffffd Arg3 0c9308f5 Arg4 02000014
03 = RC_CTL (reply) 00 = Identifier 0c93 = OX_ID 02 = (Accept)
fffffd = D_ID(Fabric controller) fffffd = S_ID (Fabric controller) 08f5 = RX_ID 000014

Args for output line 4

c0fffffd,00fffffd,0c9308f5,00000001

TABLE 45 Argument breakdown for example (line 4)

Arg1 c0fffffd Arg2 00fffffd Arg3 0c9308f5 Arg4 00000001
c0 = RC_CTL (Link control 00 = Identifier 0c93 = OX_ID One frame acknowledged using
acknowledge) standardized code.

Brocade portLogDump Reference Guide

53-1004122-01 61
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 45 Argument breakdown for example (line 4) (continued)

Arg1 c0fffffd Arg2 00fffffd Arg3 0c9308f5 Arg4 00000001
fffffd = D_ID (Fabric controller) fffffd = S_ID (Fabric controller) 08f5 = RX_ID

Example summary
The Fabric Controller on one switch sends a trunking stamp to the Fabric Controller on the other switch. The request is acknowledged
and accepted.

NSD example
The following example shows the S_ID domain controller (fffc0a) talking to the D_ID domain controller (fffc09).

If they are communicating using Brocade-specific Interswitch RSCN code, refer to Brocade-specific SW_ILS command codes on page
57 for descriptions.

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Oct 16 16:58:32 2009
16:09:52.553 nsd rscn 0fffc09 00fffc0a,1b000000,500a1f00,000000001

Zoning codes (NZ)

The SW_ILS command codes in the following table also correlate to zone exchange messaging.

TABLE 46 Zoning request codes for zoning exchange

Value Code Description
0x22000000 IE_NZ_MR N/A
0x23000000 IE_NZ_ACA N/A
0x24000000 IE_NZ_RCA N/A
0x25000000 IE_NZ_SFC N/A
0x26000000 IE_NZ_UFC N/A
0x70000000 IE_ZONE Zone Update (Vendor-Specific)
0x71000000 IE_SGROUP Group-wise commands
0x72000000 IE_SEC Security entry
0x73000000 IE_SLAPRequest SLAP Request
0x74000000 IE_SLAPAcknowledge SLAP Acknowledge
0x75000000 IE_SLAPConfirm SLAP Confirm
0x76000000 IE_SLAPDone SLAP Done
0x77000000 IE_SLAPReject SLAP Reject
0x78000000 IE_RCS_INFO Reliable commit service information
0x79000000 IE_RCS_ACA RCS Acquire Change Authorization
0x7a000000 IE_RCS_SFC RCS Stage Fabric Config
0x7b000000 IE_RCS_UFC RCS Update Fabric Config
0x7c000000 IE_RCS_RCA RCS Release Change Authorization
0x7d000000 IE_RCS_TCO RCS Transfer Commit Ownership
0x7e000000 IE_RDTS RDTS Request
0x7f000000 IE_ECP Exchange credit parameters request

Brocade portLogDump Reference Guide

62 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 47 Zoning request response codes

Value Code
0x00 NZ_SUCCESSFUL
0x01 NZ_FABRIC_BUSY
0x02 NZ_FAILED
(0 - 100) NZ_ERROR_BASE

TABLE 48 Zoning reason codes

Value Code
0x00 NZ_NO_REASON
0x01 NZ_INVALID_DATA_LEN
0x02 NZ_UNSUPPORTED_CMD
0x04 NZ_NOT_AUTHORIZED
0x05 NZ_INVALID_REQUEST
0x06 NZ_FABRIC_CHANGING
0x07 NZ_UPDATE_NOT_STAGED
0x09 NZ_INVALID_DATA
0x0a NZ_CANNOT_MERGE
0x0b ZONING_NO_LICENSE

TABLE 49 Zoning command codes

Code Abbreviation Description
1 ZONE_MERGE_REMOTE_RESPONSE Response sent to remote zoneDB update/
merge
2 ZONE_MERGE_my_RESPONSE Response received for my zone update/merge
3 ZONE_MERGE_INTEROP_RESPONSE Interop-mode Response sent to remote zone
update/merge
4 ZONE_CHECK_RESPONSE Zone Check response returned to kernel
9 ZONE_RCS_PROCESS_CM_RESPONSE
81 ZONE_MERGE_REMOTE_REQUEST Remote zoneDB update/merge request
82 ZONE_MERGE_my_REQUEST My initiated zone update/merge request
83 ZONE_MERGE_INTEROP_REQUEST Interop-mode Remote zone update/merge
request
84 ZONE_CHECK_REQUEST Zone Check request from kernel
89 ZONE_RCS_PROCESS_CM_REQUEST
90 ZONE_EFF_CFG_CHANGED

TABLE 50 Zoning status codes

Code Description
0100 REJECT
0200 ACCEPT
0300 INFO

Brocade portLogDump Reference Guide

53-1004122-01 63
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 51 Zoning detail codes

Code Abbreviation
0001 NO_EFFECTIVE_CFG
0002 switchGetWwnIds_FAILED
0003 TARGET_PORT_OFFLINE
0004 my_ORIG_PORT_OFFLINE
0005 SPOOFING_CHECK_FAILED
0006 ZONE_TYPE_SETUP_FAILED_ID1
0007 ZONE_GROUP_SETUP_FAILED_ID1
0008 ZONE_TYPE_SETUP_FAILED_ID2
0009 ZONE_GROUP_SETUP_FAILED_ID2
000a ZONED_OUT
000b GET_ID_TO_WWN_FAILED
000c ZONED_OUT_PDCM
0001 NO_EFFECTIVE_CFG
0002 switchGetWwnIds_FAILED
0003 TARGET_PORT_OFFLINE
0004 my_ORIG_PORT_OFFLINE

TABLE 52 TZone - New zoning SFC request's operation request values

Zoning Request Value Code Description
0x03 NZ_ACTIVATE_ZONESET
0x04 NZ_DEACTIVATE_ZONESET
0xF0 NZ_SAVE_FULLZONESET Vendor-specific fabric configuration server
(FCS) request operation code used for saving
configuration without activating or deactivating.

TABLE 53 Zoning transaction abort reason codes

Value Code
0xa0 ERR_ZONE_MERGE_RECEIVED
0xa1 ERR_ZONE_CONFIG_CHANGE
0xa2 ERR_ZONE_BAD_CONFIG
0xa3 ERR_ZONE_OP_FAILED
0xa4 ERR_ZONE_CANNOT_START_TRANSACTION
0xa5 ERR_ZONE_SHELL_EXITED
0xa6 ERR_ZONE_NOT_OWNER
0xa7 ERR_ZONE_VALIDATION_FAILED

Zoning-specific opcodes
SW_ILS (0x7f) ENT_MEMBER - Type of Zoning Members

TABLE 54 Specific opcode for 0x7f

SW_ILS (0x7f) ENT_MEMBER Type Description
0x01 PORT Entry describes physical port

Brocade portLogDump Reference Guide

64 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 54 Specific opcode for 0x7f (continued)

SW_ILS (0x7f) ENT_MEMBER Type Description
0x02 ENT_WWN Entry describes WWN
0x04 ENT_BMAP Entry describes AL_PA bitmap
0x08 ENT_NAME Entry describes a name

TABLE 55 Specific opcode for 0x80

SW_ILS (0x80) ENT_LUN LUN information in entry_t valid
0x01 ENT_TARGET e_devType is TARGET
0x02 ENT_INITIATOR e_devType is INITIATOR

TABLE 56 Zone configuration operations codes

Code (hex) Operation Description
00000001 CREATE Create an object
00000002 DELETE Delete an object
00000003 ADD Add a member to an object
00000004 REMOVE Remove a member from an object
00000005 CLEAR Clear all objects
00000006 DISABLE Disable configuration
00000007 ENABLE Enable configuration
00000008 SAVE Save in flash memory
00000009 MERGE Merge two configurations
0000000A REMOTE Look up ID on remote switch
0000000B CHECK Checksum configuration
00000015 TRANS_DISABLE N/A
00000016 TRANS_ENABLE N/A
00000017 TRANS_SAVE N/A
00000064 ZONE_VERSION N/A

TABLE 57 Zone object types code

Code hex value Description
00 Name Zoning
01 Zone set (Cfg)
02 Zone
03 Zone Alias
04 QLP
05 Cfg_end
06 IPO
08 Enable_cfg
09 Active_cfg

Brocade portLogDump Reference Guide

53-1004122-01 65
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 58 Zone error (TZone-reject) code

Decimal code Abbreviation Description
0 NOERROR Generic - no error
1 NOMEMORY Generic malloc failure
2 ZONE RULE CHECK No zoning rule violation

ERROR CODE EZACCEPT

3 EZBADPORT Non-existent port number
4 FCTYPEMIX Specific FC type and wildcard mix
5 ERSINGLEDEV More than one device when LUN presents
6 EZLUNMIX Mixture of devices with and without LUN at the
same port
7 EZMENMIX Mix of port and WWN zone members
8 EZHARDSOFTMIX Mix of hard and soft zones
9 EZFAQLMIX Mixing hard zoning with FA or QL zone
A EZLUNMENMIX Mix of QQQ
B ZONE TYPE Soft zoning - no need for ZT

MANAGEMENT ERROR

CODE ZT_SOFTZONE
C ZT_FABASSIST FA zone - no need for ZT
E ZT_DRIVERERR Driver returns error
F ZG_NO_MORE_CAM No more CAM entry in port driver
10 ZCHECKBADWWN Zone check bad WWN authentication
11 WWN_IN_PORTZONE WWN device in hard PORT zone
12 OFFSET_MASK_FULL No offset register available
13 PORT_EPORT Port is an E_Port

Zone example
FC-4 Type Device Data - Zoning Request

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Dec 11 23:55:03 2009
01:36:36.403 PORT Tx 29 48 02fffc07,00fffc04,09cfffff,7c000028
01:36:36.404 PORT Rx 29 0 c0fffc04,00fffc07,09cf0d69,00000001
01:36:36.409 PORT Rx 29 20 03fffc04,00fffc07,09cf0d69,02000000
01:36:36.409 PORT Tx 29 0 c0fffc07,00fffc04,09cf0d69,00000001

Output line 1

22:48:10.633 PORT Rx 8 4 02fffc07,00fffc04,09cfffff,7c000028

TABLE 59 Breakdown of args fields in output (line 1)

Arg1 02fffc0b Arg2 00fffc04 Arg3 09cfffff Arg4 7c000028
02 = RC_CTL (request) 00 = Identifier 09cf = OX_ID Zoning IU Preamble:
fffc07 = D_ID fffc04 = S_ID ffff = RX_ID 7c = IE_ELS Code (zoning)

00 = Zone Object Type (Name

zoning)

Brocade portLogDump Reference Guide

66 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

Output line 2

01:36:36.404 PORT Rx 29 0 c0fffc04,00fffc07,09cf0d69,00000001

TABLE 60 Breakdown of args fields in output (line 2)

Arg1 c0fffc04 Arg2 00fffc07 Arg3 09cf0d69 Arg4 null
c0 = RC_CTL (Link control 00 = Identifier 09cf = OX_ID One frame acknowledged using
acknowledge) standardized code.
fffc04 = D_ID fffc07 = S_ID 0d69 = RX_ID

Output line 3

01:36:36.409 PORT Rx 29 20 03fffc04,00fffc07,09cf0d69,02000000

TABLE 61 Breakdown of args fields in output (line 3)

Arg1 03fffc04 Arg2 00fffc07 Arg3 09cf0d69 Arg4 02000000
03 = RC_CTL (reply) 00 = Identifier 09cf = OX_ID 02 = Zoning IU preamble (accept)
fffc04 = D_ID fffc07 = S_ID 0d69 = RX_ID

Output line 4

01:36:36.409 PORT Tx 29 0 c0fffc07,00fffc04,09cf0d69,00000001

TABLE 62 Breakdown of args fields in output (line 4)

Arg1 c0fffc07 Arg2 00fffc04 Arg3 09cf0d69 Arg4 00000001
c0 = RC_CTL (Link control 00 = Identifier 09cf = OX_ID One frame acknowledged using
acknowledge) standardized code.
fffc07 = D_ID fffc04 = S_ID 0d69 = RX_ID

Example summary
Embedded port fffc04 sends a zoning code 70 request to the other embedded port fffc07. Embedded port fffc07 sends a link control
acknowledgment.

Fabric OS State Synchronization (FSS)

The primary function of FSS is to deliver State Update messages from ACTIVE components to their peer STANDBY components. FSS
determines if fabric elements are synchronized (and thus "FSS-compliant").

A Fabric OS switch service is composed of a set of components, which is either a user-space service daemon or kernel-space driver
with a symbolic name to identify its function inside the switch service and the instance number of the switch on which that the
component is operating.

FSS monitors the Fabric OS elements (asic driver, ns, zone, web, fabric, fspf, ms, ps, and so on) and reports them as either FSS-
compliant or not FSS-compliant. A Fabric Service is deemed fault-resilient (or FSS-compliant) if a set of its components is operating in
an active standby mode, and the state replication is carried out from the active components to their corresponding standbys.

The following table outlines each line of FSS output in portlogdump .

Brocade portLogDump Reference Guide

53-1004122-01 67
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 63 FSS field descriptions

Time Task Event Port Cmd Arg
Displays time of event Always FSSk Can be msg, event, or Always "0" (FSS is 0 = Sent, or Arg1 = service ID and
cmd. Refer to FSS related to CPs, not Transmitted (TX). component ID. Refer
messages on page ports). to FSSk service
1 = Received (RX).
68 identification on page
69.

Arg2 = send/receive
operation data.

Arg3 = Optional Flags

Arg4 = a text
description. Refer to
FSS messages on
page 68.

FSS messages
This section refers to the relationship between the event column and the final entry of the arg column. Refer to the following table to
decode a specific event and arg entry.

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Oct 16 21:58:32 2009
21:54:04.763 FSSK event 0 0 00000000,00000000,00000005,TRAC

TABLE 64 FSS messages

Event type Code/ 4th Arg Description
msg EXCH Broadcast message exchange well-know
address
msg UPDA Message state update
msg ACK Message - state acknowledgment
msg STAR Message - sync started
msg STOP Message - sync stopped
msg RECO Message - recover
msg YIEL Message - yield
msg NONE Message - no message
msg TAKE Message - Standby take control
msg TEST Message - Test Point
event STAR Sync start event
event UPCO Up connection event
event DOWN Down connection event
event COMP Image complete event
event INCO Incomplete event
event DUMP A dump is ready
event NONE No event occurred
event SYNC Sync success event
event FAIL Sync failure event

Brocade portLogDump Reference Guide

68 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 64 FSS messages (continued)

Event type Code/ 4th Arg Description
event STOP Sync stopped
event RECO The recovery failed
event TAKE A take control event occurred
event YIEL A yield control event occurred
event MISM A mismatch event occurred
event UPDA A state update event occurred
event ACTI Event reported. The active CP is ready
event STAN Event reported. The standby CP is ready
event TXQH Event reported. Transmissions are high
event RXQH Event reported. Receptions are high
event MISS Event reported. A service is missing
event AVAI Event reported. Service is available
event TRAC A trace of events was run
cmd NONE No command
cmd STAR The sync started
cmd STOP The sync stopped
cmd YIEL Yield control
cmd TAKE Take control
cmd RESE Reset
cmd FREE Freeze
cmd UNFR Unfreeze
cmd UPDA State update
cmd CONN Connect

FSSk service identification

The Service ID is displayed in the high-order half-word of Arg1.

21:54:04.882 FSSK event 0 0 00020000,00000000,00000000,UPCO

The Service ID can be viewed by running the hadump command.

The following is the output from the hadump command

=== FSS Service Dump : fcsw0 ===

== State ==
fcsw0(2): ACTIVE(0), Required ------------------------> **service ID 2
local = IMG_COMP, prev = IMG_NONE, peer = IMG_NONE
Name Local Remote
fcsw0(M) IMG_COMP IMG_INCOMP ---------------> component id 0
swc(M) IMG_COMP IMG_INCOMP ---------------> component id 1
fcp(M) IMG_COMP IMG_INCOMP ---------------> component id 2
rt(M) IMG_COMP IMG_INCOMP

FSSk component identification

A list of possible components can be found by using the hadump command. The following table lists the component name and its
associated ID.

Brocade portLogDump Reference Guide

53-1004122-01 69
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

The Component ID appears in the low-order half-word of Arg1. Use this number to determine the component that is being referenced.

22:15:51.430 FSSK msg 0 1 00020001,00000000,00000014,UPDA

TABLE 65 FSSk component identification

Component ID Component name
0x0 fcsw
0x1 swc
0x2 fcp
0x3 rt
0x4 fc
0x5 fabric
0x6 zone
0x7 fspf
0x8 ns
0x9 ms
0xA ps
0xB rcs
0xC evm
0xD track
0xE ts
0xF slap
0x10 security
0x11 web
0x12 snmp
0x13 fw
0x14 diagfss

Reading FSSk output in the portlogdump output

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Oct 16 18:58:32 2009
18:13:37.979 FSSK msg 0 0 0002000e,0000012c,00000000,UPDA
18:13:56.584 FSSK cmd 0 0 00000000,00000000,00000000,STOP
18:13:56.584 FSSK event 0 0 00000000,00000000,00000000,STOP
18:13:56.584 FSSK msg 0 0 00000000,00000005,00000000,UPDA
18:13:56.861 FSSK cmd 0 0 00020000,00000000,00000000,STOP
18:13:56.862 FSSK event 0 0 00020000,00000000,00000000,STOP
18:13:56.862 FSSK msg 0 0 00020000,00000005,00000000,UPDA
18:13:56.874 FSSK cmd 0 0 00040000,00000000,00000000,STOP
18:13:56.875 FSSK event 0 0 00040000,00000000,00000000,STOP

The following steps indicate how to read the example (from left to right).

1. The task column should display FSSK.

2. Look at the event column. All events (such as msg, cmd, event, and so on) are described in FSS messages on page 68.
3. Bypass the port column; it is always "0" because FSS is not a port-related service.
4. Look at the cmd column.

∙ 0 indicates Sent or Transmitted (TX).

Brocade portLogDump Reference Guide

70 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

∙ 1 indicates Received (RX).

5. Begin reading the Args column.

∙ Arg1 (the first 8 characters) displays the Service ID and the Component ID. Refer to FSSk component identification on
page 69.

∙ Arg2 (the second 8 characters) displays send or receive operation data.

∙ Arg3 (the third 8 characters) displays optional flags (send or receive data).

∙ Arg4 (the fourth entry in the args column) displays text that helps clarify the output.
– Note the displayed text (for example, UPDA).
– Look back at the event column (for example, msg)
– Use FSS messages on page 68 to find the message description.

ISL values and parameters

This section lists the ISL values and parameters for the portlogdump command.

ISL flow control mode values

TABLE 66 ISL flow control mode values
Value Description
hex‘0001’ Vendor-specific
hex‘0002’ R_RDY Flow Control
hex’0003 - hex’FFFE’ Vendor-specific
Other values Reserved

ISL flow control parameters

TABLE 67 ISL flow control parameters
Size Item
4 BB_Credit
16 Compatibility Parameters

Switch_Priority field values

TABLE 68 Switch_Priority field values
Hexadecimal value Description
00 Reserved
01 Highest priority value 1 .
02 The switch was the principal switch prior to sending or receiving BF 2 .
03 to FE Higher to lower priority values 3 .
FF The switch is not capable of acting as a principal switch.
1. This value allows the system administrator to establish which switch becomes the principal switch.

2. This allows the same switch to become the principal switch if it is still part of the fabric after sending or receiving the Build Fabric SW_ILS.

3. The Switch_Priority value for a given switch is established by means not defined by this standard.

Brocade portLogDump Reference Guide

53-1004122-01 71
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

Fibre Channel Common Transport protocol (FC-CT)

This section covers the variations to the Fibre Channel Common Transport (FC-CT) protocol that are unique to Brocade.

Name Server (SNS)

The Name Server (also referred to as the Simple Name Server) is a switch service that stores names, addresses, and attributes, and
provides them as required to other devices in the fabric. SNS is defined by fibre channel standards and exists at the Well-Known
Address for the Name Server (fffffc).

NOTE
Name Server can also be referred to as "directory service".

∙ Name Server commands and code descriptions on page 72

∙ FC-CT response commands on page 74

∙ FC-CT reject reason code (RJT) on page 74

∙ FC-CT reason code explanation (NS_RJT) on page 75

∙ Fabric internal FC-CT commands on page 75

∙ Name Server request types on page 76

∙ Name Server objects on page 76

∙ Name Server port type on page 76

Name Server commands and code descriptions

TABLE 69 Name Server command codes
Code Mnemonic Description Objects in request CT_IU Objects in accept CT_IU
Query with port ID
0100 GA_NXT Get all next Port Identifier All
0101 GID_A Get identifiers A list of Domain_IDsor A list of Domain_IDsor
Domain_ID/Area_IDs Domain_ID/Area_IDs
0112 GPN_ID Get Port Name Port Identifier is hex (Note - Port Name (Note - The null
The null value for the Port value for the Port or Node
or Node Name object is hex Name object is hex ‘00 00
‘00 00 00 00 00 00 00 00 00 00 00 00 00’)
00’)
0113 GNN_ID Get Node Name Port Identifier Node Name
0114 GCS_ID Get Class of Service Port Identifier Class of Service
0117 GFT_ID Get FC-4 Types Port Identifier FC-4 Types
0118 GSPN_ID Get Symbolic Port Name Port Identifier Symbolic Port Name
011A GPT_ID Get Port Type Port Identifier Port Type
011B GIPP_ID Get IP Address (Port) Port Identifier IP Address (Port)
011C GFPN_ID Get Fabric Port Name Port Identifier Fabric Port Name
011D GHA_ID Get Hard Address Port Identifier Hard Address
011E GFD_ID Get FC-4 Descriptors Port Identifier List of FC-4 Descriptors
011F GFF_ID Get FC-4 Features Port Identifier FC-4 Features

Brocade portLogDump Reference Guide

72 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 69 Name Server command codes (continued)

Code Mnemonic Description Objects in request CT_IU Objects in accept CT_IU
Query with Port name
0121 GID_PN Get Port Identifiers Port Name Port Identifier
012B GIPP_PN Get IP Address (Port) Port Name IP Address (Port)
Query with Node Name
0131 GID_NN Get Port Node Name Node Identifiers List of Port Identifiers
0132 GPN_NN Get Port Node Names Node Name List of Port Identifiers and
Port Names
0135 GIP_NN Get IP Address (Node) Node Name IP Address (Node)
0136 GIPA_NN Get Initial Process Node Name Initial Process Associator
Associator
0139 GSNN_NN Get Symbolic Node Name Node Name Symbolic Node
Query with IP
0153 GNN_IP Get Node Name IP Address (Node) Node Name
0156 GIPA_IP Get Initial Process IP Address (Node) Initial Process Associator
Associator
0171 GID_FT Get Port Identifiers None. because FC-4 type is List of Port Identifiers
specified as an encoded
value, not as an object.
0172 GPN_FT Get FC4-Type Port Name None, because FC-4 type is List of Port Identifiers and
specified as an encoded Port Names.
value, not as an object.
0173 GNN_FT Get FC-4 Type Node List of Port Identifiers and
Names Port Names.
Query with Port Type
01A1 GID_PT Get Port Identifiers Port Type (refer to Name List of Port Identifiers
Server port type on page
76)
Query with IP Port
01B1 GID_IPP Get Port Identifiers for IP IP Address (Port) List of Port Identifiers
Address (Port)
01B2 GPN_IPP Get Port Name IP Address (Port) Port Name
Query with FC-4 Features
01F1 GID_FF Get Port Identifiers FC-4 Features List of Port Identifiers
Registration
0212 RPN_ID Register Port Name Port Identifier, Port Name None
0213 RNN_ID Register Node Name Port Identifier, Node Name None
0214 RCS_ID Register Class of Service Port Identifier, Class None
0217 RFT_ID Register FC-4 Types Port Identifier, FC-4 None

Types
0218 RSPN_ID Register Symbolic Port Port Identifier, Symbolic None
Name for this Port ID Port Name
021A RPT_ID Register Port Type for this Port Identifier, IP Address None
Port ID (Port)
021B RIPP_ID Register IP Address (Port) Port Identifier, IP Address None
(Port)

Brocade portLogDump Reference Guide

53-1004122-01 73
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 69 Name Server command codes (continued)

Code Mnemonic Description Objects in request CT_IU Objects in accept CT_IU
021C RFPN_ID Register Fabric Port Name Port Identifier, Fabric Port None
Name
021D RHA_ID Register Hard Address Port Identifier, Hard None
Address
021E RFD_ID Register FC-4 Descriptors Port Identifier, FC-4 Types None
and FC-4 Descriptors
021F RFF_ID Register FC-4 Features Port Identifier, FC-4 None
Features
0235 RIP_NN Register IP Address for this Node Name, IP Address None
Node WWN (Node)
0236 RIPA_NN Register IP Address for this Node Name, Initial Process None
Node WWN Associator
0239 RSNN_NN Register Node Symbolic Node Name, Symbolic None
Name for this Node WWN Node Name
Deregistration
0300 DA_ID Deregister all Port Identifier None
FC-CT Command Restrictions

The following command codes are not used by any well-known server for the FC-GS-x client/server interface: Command codes 0400-04FF and
E000-EFFF: Fabric internal FC-CT commandsCommand codes F000-FFFF: Vendor-specific FC-CT commands.

FC-CT response commands

TABLE 70 FC-CT response commands
Value Response
0001-7FFF Request CT_IU. (These codes are used by all CT applications; for an
example, refer to Name Server commands and code descriptions on page
72.)
8001 Reject Response CT_IU. (These codes are used by all CT applications; for
an example, refer to FC-CT reject reason code (RJT) on page 74.).
8002 Accept Response CT_IU (hex ‘0000’: All available information was
returned in the Accept CT_IU.)
Other values Reserved

FC-CT reject reason code (RJT)

TABLE 71 FC-CT reject reason code
Code Description
01 Invalid command code
02 Invalid version level
03 Logical error
04 Invalid information unit size
05 Logical busy
07 Protocol error
09 Unable to perform command request
0B Command not supported
FF Vendor-specific error (see Vendor Unique field)

Brocade portLogDump Reference Guide

74 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 71 FC-CT reject reason code (continued)

Code Description
Others Reserved

FC-CT reason code explanation (NS_RJT)

TABLE 72 FC-CT reject reason code explanation
Encoded value(Bits 15-8) Description
00 No additional explanation
01 Port Identifier not registered
02 Port Name not registered
03 Node Name not registered
04 Class of Service not registered
05 IP Address (node) not registered
06 Initial Process Associator not registered
07 FC-4 TYPEs not registered
08 Symbolic Port Name not registered
09 Symbolic Node Name not registered
0A Port Type not registered
0B IP Address (port) not registered
0C Fabric Port Name not registered
0D Hard Address not registered
0E FC-4 Descriptor not registered
0F FC-4 Features not registered
10 Access denied
11 Unacceptable Port Identifier
12 Data base empty
13 No object registered in the specified scope
Others Reserved

Fabric internal FC-CT commands

TABLE 73 Fabric internal FC-CT commands
Code Mnemonic Description
0410 GE_ID Get entry, based on port identifier
0420 GE_PN Get entry, based on port name
0430 GE_NN Get entries, based on node name
0450 GE_IP Get entries, based on IP address
04A0 GE_PT Get entries, based on port type
04B0 GE_ZM Get entries, based on zone member
04C0 GE_ZN Get entries, based on zone name
04D0 GE_IPP Get entries, based on port IP address
04E0 GE_FF Get entries based on FC-4 features

Brocade portLogDump Reference Guide

53-1004122-01 75
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

Name Server request types

TABLE 74 Name Server request types
Hexadecimal code Description
01xx Get Objects (Query)
02xx Register Object
03xx Deregister Objects
0400-04FF and E000-EFFF Fabric internal FC-CT commands
F000- FFFF Vendor-specific FC-CT commands

Name Server objects

TABLE 75 Name Server objects
Object mnemonic Object name Description
A Aggregated objects Contains objects 1 through D
ID Port Identifier 3-byte address identifier
PN Port Name 8-byte Name_Identifier
NN Node Name 8-byte Name_Identifier
CS Class of Service 32-bit or 128-bit Internet Protocol address
IPA Initial Process Associator 8-byte Process_Associator
FT FC-4 TYPEs 32-byte field (8 words), one bit per TYPE
supported
SPN Symbolic Port Name Variable length (0 to 255-byte) field
SNN Symbolic Node Name Variable length (0 to 255-byte) field
PT Port Type 1-byte encoded Port Type
IPP IP Address (Port) 32-bit or 128-bit Internet Protocol address
FPN Fabric Port Name 8-byte Name_Identifier
HA Hard Address 3-byte address identifier
FD FC-4 Descriptor Variable length (0 to 255-byte) field
FF FC-4 Features 128-byte array, four bits per TYPE

Name Server port type

TABLE 76 Name Server port type
Code Description
0 NSPT_UNKNOWN
1 N_PORT
2 NL_PORT
3 NFL_PORT
0x04-0x80 Reserved
0x7F special value for all of the above ports Nx_PORT
0x81 F_PORT
0x82 FL_PORT
0x83 LT_PORT
0x84 E_PORT

Brocade portLogDump Reference Guide

76 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

FC-4 Type codes

The FC-4 Type Code provides the type of protocol service (such as FC-CT, FCP, FCIP, and so on).

TABLE 77 FC-4 Type codes

Code Service
0x04 ISO/IEC 8802-2 LLC/SNAP (in order)
0x05 FCIP
0x08 SCSI_FCP
0x09 SCSI-GPP
0x20 FC-CT used by Fibre Channel Services, such as NS, MS, AS, and so on
0x21 FC-FG
0x22 FC-SW
0x23 FC-AL
0x24 FC-SNMP
0x25-0x27 Fabric Services
0x30-0x33 Scalable Coherent Interface
0x40 HIPPI-FP
0x58 Virtual Interface
0x5b Fabric
0xDF RNID General Topology Discover (from FC-SW-5)
0xe0-0xff Vendor-specific

Server-to-Server protocol Data Unit Command/Response code

TABLE 78 Server-to-server protocol Data Unit Command/Response code
Brocade-specific code Response
0x0001 NSS_REQUEST
0x0002 NSS_RESPONSE
0x0003 NSS_INFORM
0x0004 NSS_DELETE

NSS_CT Command/Response code

The following table contains the CT_VU_NSS (Brocade, 0x0c) vendor-specific Name Server protocol Data Unit Command/Response
codes.

TABLE 79 NSS_CT Command/Response code

Code Response
0x0001 NSS_REQUEST
0x0002 NSS_RESPONSE
0x0003 NSS_INFORM
0x0004 NSS_DELETE
0x0410 NSS_GE_ID
0x041d NSS_GQP_PAIR
0x041e NSS_GQP_ID
0x041f NSS_GIDX

Brocade portLogDump Reference Guide

53-1004122-01 77
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 79 NSS_CT Command/Response code (continued)

Code Response
0x0420 NSS_GE_PN
0x0430 NSS_GE_NN
0x0450 NSS_GE_IP
0x0470 NSS_GE_FT
0x04A0 NSS_GE_PT

Management Server
The Management Server (MS) provides a single management access point within the Fibre Channel fabric.

The Management Server (MS) Well Known Address is FFFFFA.

Management Server covers the following areas:

∙ The Fabric Configuration Server provides for the configuration management of the fabric (refer to Fabric Configuration Server
on page 78).

∙ The Unzoned Name Server provides access to Name Server information that is not subject to zone constraints (refer to Name
Server (SNS) on page 72.)

∙ The Fabric Zone Server provides access to, and control of, zone information (refer to Fabric Zone Server (ZS) on page 88).

Fabric Configuration Server

The Fabric Configuration Server (FCS) provides a way for management applications to discover Fibre Channel Fabric topology and
attributes. Requests for the Fabric Configuration Server are carried over the Common Transport. The Fabric Configuration Server is
intended to be distributed among fabric elements, making the Fabric Configuration Server immediately available to an N_Port once it
has successfully completed Fabric Login. However, the Fabric Configuration Server is not restricted or required to be part of a fabric, and
may be located in any N_Port or NL_Port.

Fabric Configuration Server codes

Fabric Configuration Server registration, deregistration, and queries are managed through protocols containing a set of Request CT_IUs
and Response CT_IUs supported by the Fabric Configuration Server. Refer to FC-CT response commands on page 74.

Management Server response codes

Refer to FC-CT response commands on page 74 for all FC_CT response codes.

Management Server command codes

The primary management switch (FCS switch) can also be used as an access point for Management Server access, access by SNMP
software that polls for fabric status, a focal point for fabric-related SNMP traps, and as an access point for SAN management software.
For example, a client Nx_Port communicates its Management Server request (as defined in FC-GS-4) to a switch via the well-known
address FFFFFA. An example of a management application that uses the Management Server is the Brocade API.

Brocade portLogDump Reference Guide

78 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 80 Management Server command codes

Code Mnemonic Description Objects in request CT_IU Objects in accept CT_IU
0x0100 MS_GTIN Get Topology Information The Request CT_IU for The Accept CT_IU for GTIN
GTIN contains the request contains the ACC payload
payload defined for the defined for the Request
Request Topology Topology Information
InformationExtended Link ExtendedLink Service.
Service.
0x0101 MS_GIEL Get interconnect element List of Interconnect
list Element

Names and Types

0x0111 MS_GIET Get interconnect element Interconnect element name Interconnect element type
type
0x0112 MS_GDID Get domain ID Interconnect element name Domain identifier
0x0113 MS_GMID Get Mgmt Identifier Interconnect element name Management Identifier
0x0114 MS_GFN Get Fabric Name Interconnect element name Fabric Name 0x0115
0x0115 MS_GLIEN Get logical IE Name Interconnect element name Interconnect element logical
name
0x0116 MS_GMAL Get Mgmt Address list Interconnect element name Interconnect element
management address list
0x0117 MS_GIEIL Get IE Information list Interconnect element name Interconnect element
information list
0x0118 MS_GPL Get switch port list Interconnect element name List of Port Names, Port
Types, Port TX Types, and
Port Module Types
0x0121 MS_GPT Get switch port type Port Name Port type
0x0122 MS_GPPN Get switch physical port Port WWN Port number
number
0x0124 MS_GAPNL Get attached port name list Port WWN List of attached port names
0x0126 MS_GPS Get switch port state Port WWN Port state (See Port State
table)
0x0128 MS_GATIN Get attached topology Port WWN Attached topology
information information (4 bytes format)

Get Platform-Related Information

0x0191 MS_GPLNL Get platform node name list Platform name List of platform node
names
0x0192 MS_GPLT Get platform type Platform name See Platform type table
0x0194 MS_GPLA Get platform attributes Platform name Platform Mgmt address list
0x01A1 MS_GNPL Get platform name-node Platform Node name Platform Name
name
0x01A2 MS_GPNL Get platform name list None List of platform names
0x01B1 MS_GNID Get node identification data Platform node name None.

Brocade portLogDump Reference Guide

53-1004122-01 79
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 80 Management Server command codes (continued)

Code Mnemonic Description Objects in request CT_IU Objects in accept CT_IU

NOTE
The Accept
CT_IU for
GNID contains
the ACC
payload
defined for the
Request Node
Identification
Data Extended
Link Service.

0x0215 MS_RIELN Register IE logic name Interconnect element None

Name, Interconnect
Element Logical Name
Register Platform-Related Information
0x0280 MS_RPL Register platform Platform Name, Platform None
Type, Platform Mgmt
Address list, Platform Node
Name List
0x0291 MS_RPLN Register platform node Platform name, Platform None
name Node Name
0x0292 MS_RPLT Register platform type Platform Name, Platform None
Type
0x0293 MS_RPLM Register platform Mgmt Platform Name, Platform None
address Mgmt Address
Deregister Platform-Related Information
0x0380 MS_DPl Deregister platform Platform Name None
0x0391 MS_DPLN Deregister platform node Platform Node Name None
name
0x0392 MS_DPLM Deregister Platform Mgmt None
Addr
0x0393 MS_DPLML Deregister platform mgmt Platform Name None
address list
Port Performance Information
0x0400 MS_GPST Get port statistics
0x0401 MS_GPERR Get port errors
0x0402 MS_PCLST Clear port stats
0x0403 MS_PENAB Port enable
0x0404 MS_PDISA Port disable
Routing Information
0x0405 MS_GROUT Get a route between two
end ports
0x0406 MS_GLROUT Nexthop info from remote
switch
0x0407 MS_GPATH Output ports to reach a
domain

Brocade portLogDump Reference Guide

80 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 80 Management Server command codes (continued)

Code Mnemonic Description Objects in request CT_IU Objects in accept CT_IU
0x0408 MS_GROUT Set static route
0x0750 MS_DELROUT Delete static route
Fabric Hierarchy
0x0501 MS_GFABRIC Return all switch and port
WWNs
0x502 MS_GSW Return switch and port
WWNs
Switch Information
0x0505 MS_GSWITCH Get switch information
0x0506 MS_SSWITCH Set switch information
0x0507 MS_GSWITCH2 Get switch information
0x0508 MS_SSWITCH2 Set switch information 2.0+
API Version Information
0x0509 MS_GAPIVERSION Get API version
0x050a MS_GSSWITCH_NG Get switch info ng
0x050b MS_SSWITCH_NG Set switch info ng
0x05010 MS_GPORTLOG Get port log
0x05011 MS_GERRLOG Get error log
0x05012 MS_GFRULOG Get FRU history log
0x05013 MS_GPORTNVLOG Get port flash log
Port Information
0x0605 MS_GPORT Get port information
0x0606 MS_SPORT Set port information
0x0607 MS_GPSTATS Get port stats information
0x0608 MS_SPSTATS Set port stats information
0x0609 MS_GDEVICE Get device information
0x060a MS_GDEVICE2 Get device, string len = 256
0x060b MS_GPERRS Get port err information
0x060c MS_SPERRS Set port err information
0x060d MS_GENVATTR Asset management
0x060e MS_GFLPORT Get fl port info
0x060f MS_GMODULE Get PortModule info
0x0610 MS_SMODULE Set PortModule info
0x0611 MS_GPORT2 Get port info 2
0x0612 MS_SPORT2 Set port info 2
0x0613 MS_GPLATINFO Get platform state info
0x0614 MS_GPLATALL Get all platform database
0x0615 MS_GCP Get cp info
0x0616 MS_SFRU Set FRU Attributes
0x0617 MS_GENVATTR2 Switch Enclosure Attributes
2
0x0618 MS_GPORT_NG Get port info ng

Brocade portLogDump Reference Guide

53-1004122-01 81
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 80 Management Server command codes (continued)

Code Mnemonic Description Objects in request CT_IU Objects in accept CT_IU
0x0619 MS_SPORT_NG Set port info ng
0x0620 MS_START_PORT_DIAG Start port diag
0x0621 MS_STOP_PORT_DIAG Stop port diag
0x0622 MS_GET_PORT_DIAG_PF Get port diag profile
0x0623 MS_GET_PORT_DIAG_ST Get port diag status
0x0624 MS_GET_PORT_NAME Get port name
0x0625 MS_SET_PORT_NAME Set port name
0x0626 MS_GNPERRS Get the node port err stats
0x0627 MS_SNPERRS Get the node port err stats
0x0630 MS_GTCT Telnet Command Tunneling
RCOM
0x0701 MS_RCOM Get group commands
0X0705 MS_FW_LICENSE
0x0706 MS_FW_GET_CA
0x0707 MS_FW_GET_TH Fabric Watch. Get
Threshold.
0x0708 MS_FW_APPLY_ALARM Fabric Watch. Apply alarm.
0x0709 MS_FW_APPLY_BOUNDA Fabric Watch. Apply
RY boundary.
0x070a MS_FW_CANCEL_ALAR Fabric Watch. Cancel alarm.
M
0x070b MS_FW_CANCEL_BOUN Fabric Watch. Cancel
DARY boundary.
0x070c MS_FW_SET_ALARM_LE Fabric Watch. Set alarm
VEL level.
0x070d MS_FW_SET_ALARM Fabric Watch. Set Alarm.
0x070e MS_FW_SET_BN_LEVEL Fabric Watch. Set Boundary
Level.
0x070f MS_FW_SET_BN_BS Fabric Watch. Set
Boundary.
0x0710 MS_FW_SET_BN_HIGH Fabric Watch. Set Boundary
High level.
0x0711 MS_FW_SET_BN_LOW Fabric Watch. Set Boundary
Low Level.
0x0712 MS_FW_SET_BN_TB Fabric Watch. Set
Boundary.
0x0713 MS_FW_SET_BN_UNIT Fabric Watch. Set Boundary
Unit.
0x0714 MS_FW_SET_TH_STATUS Fabric Watch. Set Threshold
Status.
0x0715 MS_FW_SET_TH_BI Fabric Watch. Set
Threshold.
0x0716 MS_FW_SET_TH_BT Fabric Watch. Set
Threshold.
0x0717 MS_FW_INIT_CONFIG Fabric Watch. Initial
Configuration.

Brocade portLogDump Reference Guide

82 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 80 Management Server command codes (continued)

Code Mnemonic Description Objects in request CT_IU Objects in accept CT_IU
0x0718 MS_FW_INSERT_CONFIG Fabric Watch. Insert
Configuration.
0x0719 MS_FW_UPDATE_CONFI Fabric Watch. Update
G Configuration.
0x071a MS_FW_LOAD_CONFIG Fabric Watch. Load
Configuration.
0x071d MS_EVENT Management Server event.
0x071e MS_EVENT_ENABLE_FW Management Server event -
enable Fabric Watch.
0x071f MS_EVENT_DISABLE_F Management Server event -
W disable Fabric Watch.
0x0720 MS_LICENSE_ADD Management Server -
license addition reported.
0x0721 MS_LICENSE_RM Management Server -
license removal reported.
0x0722 MS_LICENSE_GET Management Server - get
license.
0x0723 MS_LICENSE_GETALL Management Server - get
all licenses.
0x0726 MS_PRODUCT_GET Management Server - get
product.
0x0727 MS_PRODUCT_GETALL Management Server - get
all products.
0x0728 MS_DOWNLOAD_START Management Server -
download start reported.
0x0729 MS_DOWNLOAD_PACKE Management Server -
T download packet reported.
0x072a MS_DOWNLOAD_ABORT Management Server -
download aborted.
0x072b MS_DOWNLOAD_END Management Server -
download ended.
0x072c MS_UPLOAD_START Management Server -
upload started.
0x072d MS_UPLOAD_PACKET Management Server -
packet upload reported.
0x072e MS_UPLOAD_ABORT Management Server -
upload aborted.
0x072f MS_UPLOAD_END Management Server -
upload ended.
0x0730 MS_EVENT_ENABLE_TC Management Server -
Enable Track Changes.
0x0731 MS_EVENT_DISABLE_TC Management Server -
Disable Track Changes.
0x0732 MS_DOWNLOAD_SELF_ Management Server - self
START start download reported.
0x0733 MS_DOWNLOAD_SELF_ Management Server - self
ABORT start download aborted.
In-Band SGroup Command

Brocade portLogDump Reference Guide

53-1004122-01 83
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 80 Management Server command codes (continued)

Code Mnemonic Description Objects in request CT_IU Objects in accept CT_IU
0x0801 MS_SG_GET Management Server - get
0x0802 MS_SG_SET Management Server - set
0x0803 MS_SG_DEL Management Server -
delete
0x0801 - 0x804 Does not appear in v4.2.0.
0x0810 MS_SEC_GET_CSR Management Server -
Security.
0x0811 MS_SEC_SET_CERT Management Server -
Security - set certificate.
0x0812 MS_SEC_SET_KEY_CERT Management Server -
Security - set key certificate.
0x0813 MS_SEC_COUNTER Management Server -
Security Counters.
0x0814 MS_SEC_GEN_CSR Management Server -
Security.
0x0815 MS_SEC_COUNTER2 Management Server -
Security Counter 2.
0x0816 MS_SEC_GET_BANNER Management Server -
Security - get banner.
0x0817 MS_SEC_SET_BANNER Management Server -
Security - set banner.
0x1000 MS_FC_API Management Server -
Forward-compatible API.
FC-SW-2 MS Command Codes
0xE000 MS_EXGPLDB Exchange Platform
Database
0xE001 MS_MRGPLDB Merge Platform Database
0xE010 MS_PLCOMIT Commit the previous Reg/
Dereg Plat Cmd
0xE020 MS_GCAP Get Management Server
Capabilities
Brocade Vendor-specific Platform-Related Information
0xF000 MS_PLACTV Activate Platform
Management Services
0xF001 MS_PLDACTV Deactivate Platform
Management Services
0xF002 MS_TDMGMT Enable or disable TD
Management Services

NOTE
All MSVU frames are non-FC-GS commands.

0xF003 MSVU_RPL Registers platform name of

AG
0xF004 MSVU_RPLN Registers platform node
name of AG
0xF005 MSVU_RPLM Register platform
management address

Brocade portLogDump Reference Guide

84 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 80 Management Server command codes (continued)

Code Mnemonic Description Objects in request CT_IU Objects in accept CT_IU
0xF006 MSVU_RPAB Registers platform attribute
block of data from AG
0xF007 MSVU_GAGINFO Get AG info command
0xF008 MSVU_DPL De-register platform
0xF009 MSVU_DPLN De-register platform node
0xF00A MSVU_DPLM De-register platform
management address
0xF00B MSVU_DPLML De-register platform
management address list
0xF00C MSVU_DPAB De-register platform
attribute block
0xF00D MSVU_DBSHOW Displays the AG database
0xF00E MSVU_GAGINFO_V2 Get AG information version
2
0xF00F MSVU_AG_ADD_DEV Register AG device details
0xF010 MSVU_AG_DEL_DEV De-register AG device
details
0xF011 MSVU_RPAB_V2 Register platform attribute
block version 2
0xF012 MSVU_GAGINFO_V3 Get AG info with larger
RPAB
Switch Default Zoning Behavior
0x0805 MS_GSWITCHDZB Get Switch Default Zoning
Behavior
0x0806 MS_SSWITCHDZB Set Switch Default Zoning
Behavior

Management Server reason code and explanation

If a Fabric Configuration Server request is rejected with a reason code of "Unable to perform command request," then it is because of
one of the reason codes explained in the following table.

TABLE 81 Management Server reason code and explanation

Code Reason
00 No additional explanation
01 Invalid Name_Identifier for Interconnect Element or Port
10 Interconnect Element List not available
11 Interconnect Element Type not available
12 Domain Identifier not available
13 Management Identifier not available
14 Fabric Name not available
15 Interconnect Element Logical Name not available
16 Management Address List not available
17 Interconnect Element Information List not available
0x18-2F Reserved for IE

Brocade portLogDump Reference Guide

53-1004122-01 85
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 81 Management Server reason code and explanation (continued)

Code Reason
30 Port List not available
31 Port Type not available
32 Physical Port Number not available
33 Reserved
34 Attached Port Name List not available
35 Reserved
36 Port State not available
50 Unable to register Interconnect Element Logical Name
60 Platform Name does not exist
61 Platform Name already exists
62 Platform Node Name does not exist
63 Platform Node Name already exists
64 EXPL_PLATFORM_DATABASE_CONFLICT
65 EXPL_PLATFORM_FUNC_UNABLE_TO_ACTIVATE
66 M_E_P_UNABLE_TO_ACTIVATE

MSRJT_EXPL_PLATFORM_FUNC_UNABLE_TO_ACTIVATE

MSRJT_EXPL_PLATFORM_FUNC_SEC_CONFLICT
67 MSRJT_EXPL_NO_PLATFORM_MGMTADDR
F0 EXPL_AUTHORIZATION_EXCEPTION
F1 EXPL_AUTHEN_EXCEPTION
F2 EXPL_DATABASE_FULL
0x01 MSRJT_EXPL_WWN_INVALID
0x91 MSRJT_EXPL_NO_PORT_STAT
0x92 MSRJT_EXPL_NO_PORT_ERRS
0x93 MSRJT_EXPL_PORT_CLR_FAIL
0x94 MSRJT_EXPL_PORT_ENABLE_FAIL
0x95 MSRJT_EXPL_PORT_DISABLE_FAIL
0x96 MSRJT_EXPL_NO_ROUT_INFO
0x97 MSRJT_EXPL_NO_LOCAL_ROUTE
0x98 MSRJT_EXPL_NO_PATH_INFO
0x99 MSRJT_EXPL_SET_STATIC_ROUTE_FAILED
0xa1 MSRJT_EXPL_DELETE_STATIC_ROUTE_FAILED
0xa5 MSRJT_EXPL_NO_SUCH_SWITCH
Definitions for port info access
0xb5 MSRJT_EXPL_NO_SUCH_PORT
0xc5 MSRJT_EXPL_INVALID_ARG
0xc6 MSRJT_EXPL_FW_INVALID_CLASS_AREA
0xc7 MSRJT_EXPL_FW_INVALID_INDEX
0xc8 MSRJT_EXPL_FW_INVALID_LEVEL_INDICATOR
0xc9 MSRJT_EXPL_FW_INVALID_EVENT_TYPE
0xca MSRJT_EXPL_FW_INVALID_ALARM_MATRIX

Brocade portLogDump Reference Guide

86 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 81 Management Server reason code and explanation (continued)

Code Reason
0xcb MSRJT_EXPL_FW_INVALID_BUFFER_SIZE
0xcc MSRJT_EXPL_FW_INVALID_LOW
0xcd MSRJT_EXPL_FW_INVALID_HIGH
0xce MSRJT_EXPL_FW_INVALID_TB
0xcf MSRJT_EXPL_FW_INVALID_UNIT_STRING
0xd0 MSRJT_EXPL_FW_INVALID_STATUS
0xd1 MSRJT_EXPL_FW_INVALID_BT
0xd2 MSRJT_EXPL_FW_INVALID_WWN
0xd3 MSRJT_EXPL_FW_DOWNLOAD_FAILED
0xd4 MSRJT_EXPL_FW_INVALID_PROFILE
0xd5 MSRJT_EXPL_FW_LOAD_FAILED
0xd6 MSRJT_EXPL_FW_INSERT_FAILED
0xd7 MSRJT_EXPL_FW_DOWNLOAD_INIT_FAILED
0xd8 MSRJT_EXPL_FW_TOO_MANY_PROXY
0xd9 MSRJT_EXPL_FW_PROXY_NOT_FOUND
0xda MSRJT_EXPL_FW_NO_LICENSE
SecureSAN PKI installation support
0xdb MSRJT_EXPL_CERT_ALREADY_INSTALLED
0xdc MSRJT_EXPL_CERT_REQ_FAILED
Firmware download errors
0xdd MSRJT_EXPL_CORRUPT_FLASH
0xde MSRJI_EXPL_RLS_SERVICE_DISABLE
Port configuration errors
0xe1 MSRJT_EXPL_PORTCFG_FAILED
0xe2 MSRJT_EXPL_PORTCFG_BADPORT
0xe3 MSRJT_EXPL_PORTCFG_BADARG
0xe4 MSRJT_EXPL_PORTCFG_BADNUMARG
0xe5 MSRJT_EXPL_PORTCFG_CFGABT
0xe6 MSRJT_EXPL_PORTCFG_NOLICENSE
0xe7 MSRJT_EXPL_PORTCFG_BADSWTYPE
0xe8 MSRJT_EXPL_PORTCFG_ISQLPORT
0xe9 MSRJT_EXPL_PORTCFG_ISLPORT
0xea MSRJT_EXPL_PORTCFG_ISGPORT
0xeb MSRJT_EXPL_PORTCFG_MCASTLB_LBEXIST
0xec MSRJT_EXPL_PORTCFG_LONGDIST_MCASTON
0xed MSRJT_EXPL_PORTCFG_LONGDIST_NOLDFAB
0xee MSRJT_EXPL_PORTCFG_BADPTTYPE
0xef MSRJT_EXPL_PORTCFG_BADSTRING

Brocade portLogDump Reference Guide

53-1004122-01 87
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

Fabric Zone Server (ZS)

The Fabric Zone Server (ZS) adds and removes, activations, and queries are managed through protocols containing a set of Request
CT_IUs and Response CT_IUs supported by the Fabric Zone Server. For a Fabric Zone Server request, the payload is transported from
the requestor to the Fabric Zone Server using a Request CT_IU. The corresponding Fabric Zone Server response is transported from the
Fabric Zone Server to the requestor, in the exchange established by the requestor, using a Response CT_IU.

The request codes described in Fabric Zone Server (ZS) codes on page 88 are based on Section 6.4.6.3 (Basic Zoning Management
Commands) of FC-GS-7 REV 10.2 dated July 21, 2014. Only those codes that are associated with Target Driven Peer Zone are
supported. Refer to Target Driven Peer Zone request codes on page 92 for more information.

Fabric Zone Server (ZS) codes

TABLE 82 Fabric Zone Server request command codes
Hexadecimal Code Mnemonic and description Attributes in request CT_IU Attributes in accept CT_IU
0x0100 GZC None Capabilities

Get Capabilities
0x0111 GEST None Enforcement state

Get Enforcement State

0x0112 GZSN None List of Zone Set Name and Number
of Zones
Get Zone Set List
0x0113 GZD Zone Set Name List of Zone Names and Number of
Zone Members
Get Zone List
0x0114 GZM Zone Name List of Zone Member Identifier
Types and Zone Member Identifiers
Get Zone Member List
0x0115 GAZS None Zone Set Name, Number of Zones,
List of Zone Names, Number of
Get Active Zone Set Zone Members, List of Zone
Member Identifier Types, and Zone
Member Identifiers
0x0116 GZS Zone Set Name None

Get Zone Set

0x0200 ADZS Zone Set Name, Number of Zones, None
List of Zone Names, Number of
Add Zone Set Zone Members, List of Zone
Member Identifier Types, and Zone
Member Identifiers
0x0201 AZSD Zone Set Name, Number of Zones, None
List of Zone Names, Number of
Activate Zone Set Direct Zone Members, List of Zone
Member Identifier Types, and Zone
Member Identifiers
0x0202 AZS Zone Set Name None

Activate Zone Set

0x0203 DZS None None

Deactivate Zone Set

0x0204 AZM Zone Name, List of Zone Member None
Identifier Types, and ZoneMember
Add Zone Members Identifiers

Brocade portLogDump Reference Guide

88 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 82 Fabric Zone Server request command codes (continued)

Hexadecimal Code Mnemonic and description Attributes in request CT_IU Attributes in accept CT_IU
0x0205 AZD Zone Set Name, Zone Name None

Add Zone
0x0300 RZM Zone Name, List of Zone Member None
Identifier Types, and Zone Member
Remove Zone Members Identifiers
0x0301 RZD Zone Set Name, Zone Name None

Remove Zone
0x0302 RZS Zone Set Name None

Remove Zone Set

The following definitions are based on the Section 6.4.7.7 (Enhanced Zoning Management Commands) of FC-GS-7 REV 10.2 dated July 21, 2014.
0x0117 ZS_GAR None CT_IU Preamble, Number of
Interconnect Element entries,
Get Activation Results Interconnect Element Name, Type,
and Reason code
0x0120 ZS_GZA Zone Name Zone Attribute Object Name

Get Zone Attribute Oject Name

0x0122 ZS_GZSE Null List of Zone Set Names

Get Zone Set List-Enhanced

0x0123 ZS_GZDE Zone Set Name List of Zone Names

Get zone List-Enhanced

0x0124 ZS_GZME Zone Name Zone Member List

Get Zone Member List-Enhanced

0x0128 ZS_GAL Null Alias List

Get Alias List

0x0129 ZS_GAM Alias Name Alias Member List

Get Alias Member List

0x0142 ZS_GFEZ None Fabric Enhanced Zoning support
flags, List of Switch Enhanced
Get Fabric Enhanced Zoning Zoning support flags
Support
0x012A ZS_GAPZ Zone Name Zone Name, Zone Attribute Block,
and Zone Member List
Get Active Peer Zone
0x0220 ZS_CZS Zone Set Name, Zone Name List Null

Create Zone Set

0x0224 ZS_AZME Zone Name, Zone Member List Null

Add Zone Members Enhanced

0x0225 ZS_CZ Zone Name, Zone Member List Null

Create Zone
0x0227 ZS_SZA Zone Name, Zone Attribute Object Null
Name
Set Zone Attributes
0x0229 ZS_CA Alias Name, Alias Member List Null

Create Alias

Brocade portLogDump Reference Guide

53-1004122-01 89
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 82 Fabric Zone Server request command codes (continued)

Hexadecimal Code Mnemonic and description Attributes in request CT_IU Attributes in accept CT_IU
0x022A ZS_AAM Alias Name, Alias Member List Null

Add Alias Members

0x022B ZS_AAPZ Zone Name, Zone Attribute Block, Null
Zone Member List
Add/Replace Active Peer Zone
0x0321 ZS_RZ Zone Set Name, Zone Name List Null

Remove Zones
0x0324 ZS_RZME Zone Name, Zone Member List Null

Remove Zone Members Enhanced

0x0325 ZS_RAPZ Zone Name Null

Remove Active Peer Zone

0x032A ZS_RAM Alias Name, Alias Member List Null

Remove Alias Members

0x032B ZS_DLZS Zone Set Name Null

Delete Zone Set

0x032c ZS_DLZ Zone Name Null

Delete zone
0x032d ZS_DLA Alias Name Null

Delete Alias
0x400 ZS_CMIT Zone Name Null

Commit zone change

TABLE 83 Zone Server Reject CT_IU GS4 reason codes

Hexadecimal Code Mnemonic
0x01 CT_INVALID_COMMAND
0x02 CT_INVALID_VERSION
0x03 CT_LOGICAL_ERROR
0x04 CT_INVALID_IU_SIZE
0x05 CT_LOGICAL_BUSY
0x07 CT_PROTOCOL_ERROR
0x09 CT_CANT_PERFORM_REQ
0x0b CT_NOT_SUPPORTED

TABLE 84 Zone Server Reject CT_IU GS4 reason code explanations

Hexadecimal Code Mnemonic
0x00 ZS_RJT_EXPL_NONE
0x01 ZS_RJT_EXPL_ZONES_NOT_SUPPORTED
0x10 ZS_RJT_EXPL_ZONESET_NAME_UNKNOWN
0x11 ZS_RJT_EXPL_NO_ZONESET_ACTIVE
0x12 ZS_RJT_EXPL_ZONE_NAME_UNKNOWN
0x13 ZS_RJT_EXPL_ZONE_STATE_UNKNOWN

Brocade portLogDump Reference Guide

90 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 84 Zone Server Reject CT_IU GS4 reason code explanations (continued)
Hexadecimal Code Mnemonic
0x14 ZS_RJT_EXPL_INCORRECT_PAYLOAD_LENGTH
0x15 ZS_RJT_EXPL_ZONESET_TOO_LARGE
0x16 ZS_RJT_EXPL_DEACTIVATE_FAILED
0x17 ZS_RJT_EXPL_REQUEST_NOT_SUPPORTED
0x18 ZS_RJT_EXPL_CAPABILITY_NOT_SUPPORTED
0x19 ZS_RJT_EXPL_MEMBER_TYPE_NOT_SUPPORTED
0x1A ZS_RJT_EXPL_INVALID_ZONESET

TABLE 85 Zone Server Reject CT_IU enhanced GS4 reason code explanations
Hexadecimal Code Mnemonic
0x20 ZS_RJT_EXPL_ENHANCED_CMDS_NOT_SUPPORTED
0x21 ZS_RJT_EXPL_ZONE_SET_ALREADY_EXISTS
0x22 ZS_RJT_EXPL_ZONE_ALREADY_EXISTS
0x23 ZS_RJT_EXPL_ALIAS_ALREADY_EXISTS
0x24 ZS_RJT_EXPL_ZONE_SET_UNKNOWN
0x25 ZS_RJT_EXPL_ZONE_UNKNOWN
0x26 ZS_RJT_EXPL_ALIAS_UNKNOWN
0x28 ZS_RJT_EXPL_UNKNOWN_ZONE_ATTRIBUTE
0x29 ZS_RJT_EXPL_FABRIC_UNABLE_TO_WORK_IN_ENH_MODE
0x30 ZS_RJT_EXPL_COMMIT_FAILED
0x33 ZS_RJT_EXPL_REQUEST_IN_PROCESS
0x34 RJT_EXPL_COMMIT_IN_PROCESS
0x37 ZS_RJT_EXPL_CONSISTENCY_CHECKS_FAILED
0x38 ZS_RJT_EXPL_PROVIDED_ZONE_NOT_PEER_ZONE
0x39 ZS_RJT_EXPL_ACTIVE_ZONE_NOT_PEER_ZONE

TABLE 86 Vendor Unique (VU) reason codes

Hexadecimal Code Mnemonic
0x00 ZS_RJT_VU_EXPL_NONE
0x01 ZS_RJT_VU_INV_MODE
0x02 ZS_RJT_VU_INV_AD
0x03 ZS_RJT_VU_ZS_ACT_NONE
0x04 ZS_RJT_VU_AD_INACTIVE
0x05 ZS_RJT_VU_INV_ZN_NAME_LEN
0x06 ZS_RJT_VU_INV_ZN_NAME
0x07 ZS_RJT_VU_INV_ATTR
0x08 ZS_RJT_VU_INV_MEM_CNT
0x09 ZS_RJT_VU_INV_ZN_MEMBER
0x0A ZS_RJT_VU_TRANS_IN_PROG
0x0B ZS_RJT_VU_FAB_UNSTABLE
0x0C ZS_RJT_VU_ZN_DUPLICATE

Brocade portLogDump Reference Guide

53-1004122-01 91
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 86 Vendor Unique (VU) reason codes (continued)

Hexadecimal Code Mnemonic
0x0D ZS_RJT_VU_PRZ_IN_REG_ZN
0x0E ZS_RJT_VU_INV_PRZ
0x0F ZS_RJT_VU_PRZ_IN_PROG
0x10 ZS_RJT_VU_INTRNAL_ERR
0x11 ZS_RJT_VU_INV_FC_SID
0x12 ZS_RJT_VU_DEV_UNAUTH
0x13 ZS_RJT_VU_DEV_NOT_IN_AD

Target Driven Peer Zone request codes

The following table describes the values for the Target Driven Peer Zone request codes.

TABLE 87 Target Driven Peer Zone request codes

Value Code Description
0x012A GAPZ Get Active Peer Zone
0x022B AAPZ Add/Replace Active Peer Zone
0x0325 RAPZ Remove Active Peer Zone
0x0142 GFEZ Get Fabric Enhanced Zoning Support

Decoding Target Driven Peer Zone request and response

The following examples describe decoding of various Target Driven Peer Zone requests and responses.

GFEZ incoming request and accept response

The following example shows the GFEZ incoming request and accept response.

sw0:admin> portlogdumpport 41
time task event port cmd args
-------------------------------------------------
Tue Dec 16 22:30:09 2014
22:30:09.305 PORT Rx3 41 16 02fffffa,00032900,10a8ffff,01000000
22:30:09.306 FCPH read 41 16 02fffffa,00032900,8f000000,00000000,10a89f23
22:30:09.306 FCPH seq 41 10 20290000,10a89f23,00000565,0000001c,00000000
22:30:09.306 zone ctin 41 fa 00000142
22:30:09.306 zone ctout 41 fa 00078002,00000001,00000002,00000003
22:30:09.307 FCPH write 41 48 03032900,00fffffa,8f000000,00000000,10a89f23
22:30:09.307 FCPH seq 41 30 20980000,10a89f23,00000701,00040000,00000000
22:30:09.307 PORT Tx3 41 48 03032900,00fffffa,10a89f23,01000000

Output line 4: GFEZ incoming request

22:30:09.306 zone ctin 41 fa 00000142

The argument breakdown for the sample argument “00000142” in output line 4 is as follows:

∙ 0000 = Bitmap for number of arguments

∙ 0142 = GFEZ request

Output line 5: GEFZ accept response

22:30:09.306 zone ctout 41 fa 00078002,00000001,00000002,00000003

Arguments breakdown for output line 5:

Brocade portLogDump Reference Guide

92 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

Arg1 00078002 Arg2 00000001 Arg3 00000002 Arg4 00000003

0007 = Bitmap for number of 00000001 = Fabric GFEZ flags 00000002 = Number of switches 00000003 = Local switch's GFEZ
arguments in the fabric flags
8002 = CT accept response

GAPZ incoming request and accept response

The following example shows the GAPZ incoming request and accept response.

sw0:admin> portlogdumpport 41
time task event port cmd args
-------------------------------------------------
Tue Dec 16 22:42:06 2014
22:42:06.616 PORT Rx3 41 88 02fffffa,00032900,10b0ffff,01000000
22:42:06.616 FCPH read 41 88 02fffffa,00032900,93000000,00000000,10b09fa7
22:42:06.616 FCPH seq 41 58 20290003,10b09fa7,00000565,0000001c,00000000
22:42:06.617 zone ctin 41 fa 000f012a,0000000c,74657374,5f7a6f6e,65000000
22:42:06.617 zone ctout 41 fa 00038002,00000001,00000001
22:42:06.617 FCPH write 41 64 03032900,00fffffa,93000000,00000000,10b09fa7
22:42:06.617 FCPH seq 41 40 20980003,10b09fa7,00000701,00040000,00000000
22:42:06.617 PORT Tx3 41 64 03032900,00fffffa,10b09fa7,01000000

Output line 4: GAPZ incoming request

22:42:06.617 zone ctin 41 fa 000f012a,0000000c,74657374,5f7a6f6e,65000000

Arguments breakdown for output line 4:

Arg1 000f012a Arg2 0000000c Arg3 74657374 Arg4 5f7a6f6e Arg5 65000000
000f = Bitmap for number 0000000c = Zone name 74657374 = Zone name 5f7a6f6e = Zone name 65000000 = Zone name
of arguments length
012a = GAPZ request

Output line 5: GAPZ accept response

22:42:06.617 zone ctout 41 fa 00038002,00000001,00000001

Arguments breakdown for output line 5:

Arg1 00038002 Arg2 00000001 Arg3 00000001

0003 = Bitmap for number of arguments 00000001 = Number of zone attribute entries 00000001 = Number of zone members
8002 = CT accept response

AAPZ incoming request and accept response

The following example shows the AAPZ incoming request and accept response.

sw0:admin> portlogdumpport 41
time task event port cmd args
-------------------------------------------------
Tue Dec 16 22:15:36 2014
22:15:36.090 PORT Rx3 41 64 02fffffa,00032900,10a1ffff,01000000
22:15:36.090 FCPH read 41 64 02fffffa,00032900,8c000000,00000000,10a19eb1
22:15:36.090 FCPH seq 41 40 20290000,10a19eb1,00000565,0000001c,00000000
22:15:36.094 zone ctin 41 fa 000f022b,302a0005,337e97e9,00000001,00000001
22:15:36.095 zone ctout 41 fa 00008002
22:15:36.096 FCPH write 41 16 03032900,00fffffa,8c000000,00000000,10a19eb1
22:15:36.096 FCPH seq 41 10 20980000,10a19eb1,00000701,0004001c,00000000
22:15:36.096 PORT Tx3 41 16 03032900,00fffffa,10a19eb1,01000000

Brocade portLogDump Reference Guide

53-1004122-01 93
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

Output line 4: AAPZ incoming request

22:15:36.094 zone ctin 41 fa 000f022b,302a0005,337e97e9,00000001,00000001

Arguments breakdown for output line 4:

Arg1 000f022b Arg2 302a0005 Arg3 337e97e9 Arg4 00000001 Arg5 00000001
000f = Bitmap for number 302a0005 = Upper 4 337e97e9 = Lower 4 bytes 00000001 - Number of 00000001 - Number of
of arguments bytes of initiator WWN of initiator WWN zone attributes zone members
022b = AAPZ request

Output line 5: AAPZ accept response

22:15:36.095 zone ctout 41 fa 00008002

The argument breakdown for the sample argument “00008002” in output line 5 is as follows:

∙ 0000 = Bitmap for number of arguments

∙ 8002 = CT accept response

RAPZ incoming request and accept response

The following example shows the RAPZ incoming request and accept response.

sw0:admin> portlogdumpport 41
time task event port cmd args
-------------------------------------------------
Tue Dec 16 22:45:40 2014
22:45:40.565 PORT Rx3 41 88 02fffffa,00032900,10b3ffff,01000000
22:45:40.565 FCPH read 41 88 02fffffa,00032900,94000000,00000000,10b39fc0
22:45:40.565 FCPH seq 41 58 20290003,10b39fc0,00000565,0000001c,00000000
22:45:40.567 zone ctin 41 fa 00030325,302a0005,337e97e9
22:45:40.568 zone ctout 41 fa 00008002
22:45:40.568 FCPH write 41 16 03032900,00fffffa,94000000,00000000,10b39fc0
22:45:40.568 FCPH seq 41 10 20980003,10b39fc0,00000701,0004001c,00000000
22:45:40.568 PORT Tx3 41 16 03032900,00fffffa,10b39fc0,01000000
22:45:50.798 nsd rscn 41 32900 00fffffd,61040014,00031900,00031901
22:45:50.798 FCPH write 41 20 00032900,00fffffd,00000000,00000000,00000000
22:45:50.798 FCPH seq 41 14 00210000,00000000,000044f3,00010180,00000000
22:45:50.798 PORT Tx3 41 20 22032900,00fffffd,9fcaffff,61040014

Output line 4: RAPZ incoming request

22:45:40.567 zone ctin 41 fa 00030325,302a0005,337e97e9

Arguments breakdown for output line 4:

Arg1 00030325 Arg2 302a0005 Arg3 337e97e9

0003 = Bitmap for number of arguments 302a0005 = Upper 4 bytes of initiator WWN 337e97e9 = Lower 4 bytes of initiator WWN
0325 = RAPZ request

Output line 5: RAPZ accept response

22:45:40.568 zone ctout 41 fa 00008002

The argument breakdown for the sample argument “00008002” in output line 5 is as follows:

∙ 0000 = Bitmap for number of arguments

∙ 8002 = CT accept response

Brocade portLogDump Reference Guide

94 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

CT Reject response

The following example shows the CT Reject response.

sw0:admin> portlogdumpport 41
time task event port cmd args
22:55:37.903 PORT Rx3 41 76 02fffffa,00032900,10bbffff,01000000
22:55:37.904 FCPH read 41 76 02fffffa,00032900,98000000,00000000,10bba012
22:55:37.904 FCPH seq 41 4c 20290000,10bba012,00000565,0000001c,00000000
22:55:37.907 zone ctin 41 fa 000f022b,302a0005,337e97e9,00000023,00000000
22:55:37.907 zone ctout 41 fa 00078001,00000009,0000001a,00000008
22:55:37.907 FCPH write 41 16 03032900,00fffffa,98000000,00000000,10bba012
22:55:37.907 FCPH seq 41 10 20980000,10bba012,00000701,0004001c,00000000
22:55:37.907 PORT Tx3 41 16 03032900,00fffffa,10bba012,01000000

Output line 5: Reject response

22:55:37.907 zone ctout 41 fa 00078001,00000009,0000001a,00000008

Arguments breakdown for output line 5:

Arg1 00078001 Arg2 00000009 Arg3 0000001a Arg4 00000008

0007 = Bitmap for number of 00000009 = CT reject reason 0000001a = CT reject explanation 00000008 = VU code
arguments
8001 = CT reject response

NOTE

Refer Fabric Zone Server (ZS) codes on page 88 for more information about CT reject reason codes, CT reject reason codes
explanation, and VU codes.

Alias Service request code (FC-GS-1)

The following table describes the values for the Alias Service request codes.

TABLE 88 Alias Service request code (FC-GS-1)

Value Code Description
0 ASRV_OK Alias Service OK
0 ASRV_ACC Alias Service Accepted
1 ASRV_REJ Alias ServiceRefer to FS_RJT reason code
explanation
2 ASRV_NOBUF Alias Service no buffer
3 ASRV_INVALID Alias Service - Invalid parameter
4 ASRV_BADPTR Alias Service - bad pointer
11 ASRV_DB_ENTRY_EXIST Related to database
12 ASRV_DB_NOENTRY Alias Service - No entry
19 ASRV_DB_CORRUPTED Alias Service - This is a critical message

Decoding a ctin event

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Dec 11 23:55:03 2009
23:55:28.843 nsd0 ctin 1 fc 00010173,00000008

Brocade portLogDump Reference Guide

53-1004122-01 95
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

Note the fc in the cmd field. FC = Name Server for NS entries.

TABLE 89 ctin event argument

Arg 1 00010173 Arg2 00000008
0001 means that only one additional argument follows after argument 0173 is the FC-CT command code. 0173 means "GNN_FT - Get FC-4
one (in this example, 00000008). Node Name." The FC-4 object defines by arg 2 as "00000008". Arg 2
belongs to word 4 of the GNN_FT frame. Refer to Decoding a ctout event
on page 96. Argument 2, "00000008", means SCSI- FCP.

NOTE
If the first 16-bit field is "0003", then the argument in positions 1 and 2 are sets, and you should have two arguments. In other
words, two arguments follow after arg 1.

TABLE 90 Get FC4-Type node name (0173 frame)

Word Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0
0 FC-CT Rev=01 IN_ID (S to zero by the Requesting_CT)
1 GS_TYPE GS_Subtype Options Reserved
2 Command Code=0173 Maximum/Residual Size
3 Reserved Reason Code Reason Code Explanation Vendor-specific
4 Reserved Domain ID scope Area_ID scope FC-4 Type Code=08

Decoding a ctout event

sw0:admin> portlogdump
time task event port cmd args
-------------------------------------------------
Fri Dec 11 23:55:03 2009
23:55:28.843 nsd0 ctout 1 fc 00018001,00090700

Note the fc in the cmd field. FC = Name Server for NS entries.

TABLE 91 ctout event argument

Arg 1 00018001 Arg2 00090700
0001 indicates whether subsequent args are valid. Arg 2 represents the FC-CT response code.

∙ A "0001" entry (1 = 0001 in binary) means that only one ∙ If the second 16-bit field is a reject ("8001"), then argument 2 is
additional argument follows after argument 1 (in this example, a reject, FC-CT reject reason code (RJT) on page 74
0001).
∙ If the second 16-bit field is an accept ("8002"), then arguments
∙ If the first 16-bit field is "0003", then the argument in position 1 2 and 3 are the IU response objects.
and 2 are sets, and you should have two arguments. In other
words, two arguments follow after argument 1.

TABLE 92 Accept get FC4-Type node name (0173 frame)

Word Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0
0 FC-CT Rev=01 IN_ID (S to zero by the Requesting_CT)
1 GS_TYPE GS_Subtype Options Reserved
2 Command Code=8001 Maximum/Residual Size
3 Reserved Reason Code=09 Reason Vendor-specific
CodeExplanation=07
4 Control Port Identifier #1
5 Reserved

Brocade portLogDump Reference Guide

96 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 92 Accept get FC4-Type node name (0173 frame) (continued)

Word Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0
6-7 Node Name #1

Fibre Channel Protocol information

The Fibre Channel Protocol information refers to the following:

Well-Known Ordered Sets

A transmission word that uses 8B/10B mapping and begins with the K28.5 character. Ordered sets occur outside of frames, and include
the following items:

∙ Primitive signals: Indicate events.

∙ Frame delimiters: Mark frame boundaries and describe frame contents.

∙ Primitive sequences: Indicate or initiate port states.

Ordered sets are used to differentiate Fibre Channel control information from data frames and to manage the transport of frames.

Types of Ordered Sets

There are two types of Ordered Sets:

∙ Point-to-Point Link

∙ Arbitrated Loop

Point-to-Point Link - Primitive Signals

The point-to-point link primitive signals in the following table indicate switch events.

TABLE 93 Point-to-Point Link - Primitive Signals

Abbreviation Primitive Signal Ordered Set
Idle Idle K28.5 - D21.4 - D21.5 - D21.5
R_RDY Receiver_Ready K28.5 - D21.4 - D10.2 - D10.2
VC_RDY Virtual Circuit Ready K28.5 - D21.7 - VC_ID - VC_ID
BB_SCs buffer-to-buffer State Change (SOF) K28.5 - D21.4 - D22.4 - D22.4
BB_SCr buffer-to-buffer State Change (R_RDY) K28.5 - D21.4 - D22.6 - D22.6
SYNx Clock Synchronization Word X K28.5 - D31.3 - CS_X - CS_X
SYNy Clock Synchronization Word Y K28.5 - D31.3 - CS_Y - CS_Y
SYNz Clock Synchronization Word Z K28.5 - D31.3 - CS_Z - CS_Z

Point-to-Point Link - Primitive Sequences

The point-to-point link primitive sequences in the following table indicate port states.

Brocade portLogDump Reference Guide

53-1004122-01 97
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 94 Point-to-Point Link - Primitive Sequences

Primitive Sequence Definition Ordered Set
Not_Operational (NOS) K28.5 D21.2 D31.5 D5.2
∙ Loss-of-Synchronization for more
than a timeout period (R_T_TOV)
while in the Word Synchronization
Acquired State

∙ Loss-of-Signal while in the Word

Synchronization Acquired State

∙ Timeout (R_T_TOV) during the Link

Reset Protocol
Offline (OLS) The FC_Port transmitting the Sequence K28.5 D21.1 D10.4 D21.2

∙ Initiates the Link Initialization Protocol

∙ Receives and recognizes NOS

∙ Enters the Offline State

Link_Reset (LR) Transmitted by an FC_Port to initiate the Link K28.5 D9.2 D31.5 D9.2
Reset Protocol, or to recover from a Link
Timeout.
Link_Reset_Response (LRR) Transmitted by an FC_Port to indicate that it is K28.5 D21.1 D31.5 D9.2
receiving and recognizes the LR Primitive
Sequence.

Arbitrated Loop - Primitive Signals

TABLE 95 Arbitrated Loop - Primitive Signals
Abbreviation Primitive Signal Ordered Set
ARByx Arbitrate K28.5 D20.4 y x
ARB(val) Arbitrate K28.5 D20.4 val val
CLS Close K28.5 D5.4 D21.5 D21.5
DHD Dynamic Half-Duplex K28.5 D10.4 D21.5 D21.5
MRKtx Mark K28.5 D31.2 MK_TP AL_PS
OPNyx Open full-duplex K28.5 D17.4 AL_PD AL_PS
OPNyy Open half-duplex K28.5 D17.4 AL_PD AL_PD
OPNyr Open selective replicate K28.5 D17.4 AL_PD D31.7
OPNfr Open broadcast replicate K28.5 D17.4 D31.7 D31.7

Arbitrated Loop - Primitive Sequence

TABLE 96 Arbitrated Loop - Primitive Sequence
Abbreviation Primitive Sequence Ordered Set
LIP(F7,F7) Loop Initialization--F7, F7 K28.5 D21.0 D23.7 D23.7
LIP(F8,F7) Loop Initialization--F8, F7 K28.5 D21.0 D24.7 D23.7
LIP(F7,x) Loop Initialization--F7, x K28.5 D21.0 D23.7 AL_PS
LIPyx Loop Initialization--reset K28.5 D21.0 AL_PD AL_PS
LIPfx Loop Initialization--reset all K28.5 D21.0 D31.7 AL_PS
LIPba Loop Initialization--reserved K28.5 D21.0 b a
LPByx Loop Port Bypass K28.5 D9.0 AL_PD AL_PS
LPBfx Loop Port Bypass all K28.5 D9.0 D31.7 AL_PS

Brocade portLogDump Reference Guide

98 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 96 Arbitrated Loop - Primitive Sequence (continued)

Abbreviation Primitive Sequence Ordered Set
LPEyx Loop Port Enable K28.5 D5.0 AL_PD AL_PS
LPEfx Loop Port Enable all K28.5 D5.0 D31.7 AL_PS

Port State Machine Values (pstate)

TABLE 97 Port State Machine Values
State Machine Values
0 AC Active state
ID LE Idle
1 LR1 Link Reset: LR transmit state
LR2 Link Reset: LR receive state
LR3 Link Reset: LRR receive state
LF1 Link Failure: NOS transmit state
LF2 Link Failure: NOS receive state
3 OL1 Offline: OLS transmit state
OL2 Offline: OLS receive state
OL3 Offline: wait for OLS state
4 NOS Not Operational

Well-Known Addresses
In the Fibre Channel protocol, a Well-Known Address is a logical address defined by the Fibre Channel standards as assigned to a
specific function, and stored on the switch.

TABLE 98 Well-Known Addresses

Well-Known Address Description
0xFFFFFF BROADCAST - Frames transmitted to this address are broadcast to all
operational N_Ports.
0xFFFFFE FABRIC_F_PORT- A Fabric is required to support this address to accept
Fabric login (FLOGI) requests from an F_Port or FL_Port associated with
an N_Port or group of NL_Ports on an arbitrated loop.
0xFFFFFD FABRIC_CONTROLLER - This address is responsible for managing the
Fabric. It initializes the Fabric, and routes frames to the well-known
address.
0xFFFFFC NAME_SERVER - This address provides a registration service allowing
an N_Port to register information in a database or initiate database queries
to retrieve information about other ports.
0xFFFFFB TIME_SERVER - An optional service that facilitates the maintenance of
system time between ports.
0xFFFFFA MANAGEMENT_SERVER - This is an optional service used to collect
and report management information such as link usage, error statistics,
and link quality.
0xFFFFF9 Quality of Service Facilitator (QoSF) for Class-4 Bandwidth and Latency
Management (FC_PH2).
0xFFFFF8 ALIAS_SERVER -An optional service to manage the assignment of alias
address identifiers.

Brocade portLogDump Reference Guide

53-1004122-01 99
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 98 Well-Known Addresses (continued)

Well-Known Address Description
0xFFFFF7 Security-Key Distribution Service - An optional service to manage the
distribution of encryption security keys to facilitate secure
communications between N_Ports.
0xFFFFF6 Clock Synchronization Server (FC-PH3)
0xFFFFF5 MULTICAST SERVER (FC-PH3) - An optional service that manages the
reliable multicast function in Class -6. ACK and RJT responses from
members of a multicast group and sending a single reply to the multicast
originator.
0xFFFFF4 - 0xFFFFF0 Reserved
S_ID and D_ID Assignments
0xFFFBxx Multicast (group in lower byte)
0xFFFCxx Embedded_Port (domain in lower byte)

Valid AL_PA Addresses

Arbitrated Loop Physical Address (AL_PA) and Loop IDs are listed in the following table. Up to 127 devices can be on a loop. AL_PA 00
is the Master AL_PA which is normally reserved for the FL_Port. The remaining 126 AL_PA values between x01 and xEF are available
for use by NL_Ports. The next AL_PA is EF, E8, E4 and so on from the lowest priority. There are only 127 values on a loop because the
other bits are used to preserve the running disparity on the link, and AL_PA values are restricted to those characters that result in neutral
disparity after encoding.

TABLE 99 Valid AL_PA Addresses

Word 0 Word 2 Word 3 Word 4
Bit AL_PA Bit AL_PA Bit AL_PA Bit AL_PA
31 L_bit 31 3C 31 73 31 B3
30 00 30 43 30 74 30 B4
29 01 29 45 29 75 29 B5
28 02 28 46 28 76 28 B6
27 04 27 47 27 79 27 B9
26 08 26 49 26 7A 26 BA
25 0F 25 4A 25 7C 25 BC
24 10 24 4B 24 80 24 C3
23 17 23 4C 23 81 23 C5
22 18 22 4D 22 82 22 C6
21 1B 21 4E 21 84 21 C7
20 1D 20 51 20 88 20 C9
19 1E 19 52 19 8F 19 CA
18 1F 18 53 18 90 18 CB
17 23 17 54 17 97 17 CC
16 25 16 55 16 98 16 CD
15 26 15 56 15 9B 15 CE
14 27 14 59 14 9D 14 D1
13 29 13 5A 13 9E 13 D2
12 2A 12 5C 12 9F 12 D3

Brocade portLogDump Reference Guide

100 53-1004122-01
 FOR BROCADE AND PARTNER USE ONLY
Troubleshooting Using the Port Logs

TABLE 99 Valid AL_PA Addresses (continued)

Word 0 Word 2 Word 3 Word 4
11 2B 11 63 11 A3 11 D4
10 2C 10 65 10 A5 10 D5
9 2D 9 66 9 A6 9 D6
8 2E 8 67 8 A7 8 D9
7 31 7 69 7 A9 7 DA
6 32 6 64 6 AA 6 DC
5 33 5 6B 5 AB 5 E0
4 34 4 6C 4 AC 4 E1
3 35 3 6D 3 AD 3 E2
2 36 2 6E 2 AE 2 E4
1 39 1 71 1 B1 1 E8
0 3A 0 72 0 B2 0 EF

Brocade portLogDump Reference Guide

53-1004122-01 101