447-01 Port Log Dump Reference

Brocade PortlogDump Reference Guide
Version 1.0
Publication Number: 53-0000447-01 Publication Date: May 5, 2004
Copyright 2004, Brocade Communications Systems, Incorporated. ALL RIGHTS RESERVED. Publication Number: 53-0000447-01
Brocade, the Brocade B weave logo, Secure Fabric OS, and SilkWorm are registered trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. FICON is a registered trademark of IBM Corporation in the U.S. and other countries. All other brands, products, or service names are or may be trademarks or service marks of, and are used to identify, products or services of their respective owners. Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be currently available. Contact a Brocade sales office for information on feature and product availability. The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any person or entity with respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that accompany it. Notice: 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. Export of technical data contained in this document may require an export license from the United States Government.
Brocade Communications Systems, Incorporated

Corporate Headquarters 1745 Technology Drive San Jose, CA 95110 T: (408) 487-8000 F: (408) 487-8101 Email: info@brocade.com
Document History
The table below lists all versions of the PortlogDump Reference Guide. Document version Initial Publication (Version 1.0) Publication Number Publication Date 53-0000447-01 5/5/2004
Table of Contents
Preface Chapter 1 Understanding the Port Log Dump

1-1 1-3 1-4 1-4 1-5 1-7
1.1. Reading Portlogdump Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2. Variations in Portlogdump Output by Fabric OS Version . . . . . . . . . . . . . . . . 1.3. Using and Customizing the portlogdump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.1. Portlogdump Related Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.2. Displaying and Customizing the Portlogdump Output. . . . . . . . . . . . . . . . . . . 1.4. Locating Information by Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2
Troubleshooting Using the Port Logs

2-1 2-1 2-4 2-5 2-5 2-6 2-7 2-7
2.1. About the Portlogdump Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.1. Task Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.2. Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.3. Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.4. Cmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.5. Args . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2. FC_PH Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.1. FC_PH Frames Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3. State Change Notification (SCN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13 2.3.1. Reading an SCN Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13 2.3.2. SCN Codes and Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14 2.3.3. SCN Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15 2.3.4. SCN Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15 2.3.5. SCN Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
2.4. Brocade Specific Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17 2.4.1. LoopSCN Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17 2.4.2. SilkWorm Port Physical State Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18 2.4.3. SilkWorm LED State Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18 2.4.4. SilkWorm Bypass Reason Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18 2.4.5. Switch Parameter Meanings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19 2.5. Speed Negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19 2.5.1. I/O Control (ioctl) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22 2.5.2. Reading a Routing Event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29 2.6. Extended Link Service (ELS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30 2.6.1. ELS Command Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30 2.6.2. FC-PH - Reject Reason Codes and Explanations . . . . . . . . . . . . . . . . . . . . . . . 2-32 2.6.3. ELS Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35 2.7. Switch Fabric Internal Link Services (SW_ILS) . . . . . . . . . . . . . . . . . . . . . . . . . 2-37 2.7.1. SW_ILS Command Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38 2.7.2. SW_ILS Reject Reason Codes (SW_RJT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40 2.7.3. SW_ILS Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41 2.7.4. Fabric OS State Synchronization (FSS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50 2.7.5. FSS Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50 2.8. Fabric Services Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54 2.9. ISL Flow Control and Switch Priority Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56 2.10. Fibre Channel Common Transport Protocol (FC-CT). . . . . . . . . . . . . . . . . . . 2-57 2.10.1. FC-CT Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58 2.10.2. About the Name Server (SNS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59 2.10.3. Name Server Commands and Code Descriptions . . . . . . . . . . . . . . . . . . . . . . 2-59 2.10.4. ctin and ctout Event Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68
ii
2.11. The Management Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-71 2.11.1. About the Fabric Configuration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-71 2.11.2. Fabric Configuration Server Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-71 2.11.3. Management Server Response Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-71 2.11.4. Management Server Command Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-71 2.11.5. Management Server Reason Code and Explanation . . . . . . . . . . . . . . . . . . . . 2-78 2.11.6. Fabric Zone Server (ZS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-82 2.11.7. Alias Service Request Code (FC_GS-1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-82 2.12. Link Control Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-83 2.12.1. Link Control Headers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-83 2.12.2. Link Control Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-84 2.12.3. Link Control Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-85 2.12.4. Link Control Abort Sequence (ABTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-87 2.13. Payload Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-87 2.13.1. SW_ELS Payload Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-87 2.13.2. SW_ILS Payload Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-90 2.13.3. FC-CT Payload Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-96 2.14. Fibre Channel Protocol Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-103 2.14.1. Well-Known Ordered Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-103 2.14.2. Port State Machine Values (pstate) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-105 2.14.3. Well-Known Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-106 2.14.4. Valid AL_PA Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-107
iii
iv
List Of Tables
Table 1-1 Fabric OS Variations ......................................................................................... 1-3 Table 1-2 portlogdump-Related Commands...................................................................... 1-4 Table 1-3 portlogdump Information Mapping Table......................................................... 1-7 Table 2-1 Fabric OS v2.x and v3.x Task Descriptions ...................................................... 2-1 Table 2-2 Fabric OS v4.x Task Descriptions..................................................................... 2-3 Table 2-3 Event Descriptions ............................................................................................ 2-4 Table 2-4 List of Commands (cmd)................................................................................... 2-5 Table 2-5 FC_PH Frame Diagram..................................................................................... 2-7 Table 2-6 FC_PH Frame Cross-References....................................................................... 2-7 Table 2-7 Routing Control Bits - R_CTL Diagram ........................................................... 2-8 Table 2-8 Frame Control (F_CTL) Diagram ..................................................................... 2-9 Table 2-9 FC-4 Type Codes............................................................................................. 2-11 Table 2-10 Data Field Control (DF_CTL) Optional Headers.......................................... 2-12 Table 2-11 Class Specific Control Field (CS_CTL) IU Status Values............................ 2-12 Table 2-12 Internal State Change Notification (SCN) Command Codes ........................ 2-14 Table 2-13 SCN Modes ................................................................................................... 2-15 Table 2-14 Types of SCNs............................................................................................... 2-15 Table 2-15 SCN Errors .................................................................................................... 2-16 Table 2-16 LoopSCN Code (loopscan code) ................................................................... 2-17 Table 2-17 Specific Physical State Values ...................................................................... 2-18 Table 2-18 SilkWorm Specific LED State Values .......................................................... 2-18 Table 2-19 Brocade Specific Bypass Reason Code......................................................... 2-18 Table 2-20 Specific Switch Parameter Meanings............................................................ 2-19 Table 2-21 Speed Negotiation ......................................................................................... 2-19 Table 2-22 Speed Negotiation Portlogs - Task, Event, and Port ..................................... 2-19 Table 2-23 Speed Negotiation Command (cmd) Code.................................................... 2-20 Table 2-24 Argument #1 Keys and Definitions............................................................... 2-20 Table 2-25 Argument #2 Branch Tags (not complete) .................................................... 2-21 Table 2-26 Argument #3 IUs ........................................................................................... 2-21
Table 2-27 IOCTL CTL Code ......................................................................................... 2-22 Table 2-28 ELS Command Code..................................................................................... 2-30 Table 2-29 FC-PH Reject Reason Code .......................................................................... 2-32 Table 2-30 FC-PH Reject Reason Explanation Codes .................................................... 2-33 Table 2-31 ELS Arg Explanation (Line 1) ...................................................................... 2-35 Table 2-32 ELS Arg Explanation (Line 2) ...................................................................... 2-35 Table 2-33 Switch Fabric Internal Link Services Command Codes ............................... 2-38 Table 2-34 FC_SW: Reject Reason Codes (SW_RJT).................................................... 2-40 Table 2-35 FC-SW (SW-RJT): Reject Reason Explanation Codes................................. 2-40 Table 2-36 Argument Break Down for Example (Line 1)............................................... 2-41 Table 2-37 Argument Breakdown for Example (Line 2)................................................. 2-42 Table 2-38 Argument Breakdown for Example (Line 1)................................................. 2-42 Table 2-39 Argument Breakdown for Example (Line 2)................................................. 2-42 Table 2-40 Argument Breakdown for Example (Line 3)................................................. 2-43 Table 2-41 Argument Breakdown for Example (Line 4)................................................. 2-43 Table 2-42 SW_ILS Reject Example Descriptions ......................................................... 2-44 Table 2-43 Breakdown of Arg Fields in Output (Line 1) ................................................ 2-45 Table 2-44 Breakdown of Arg Fields in Output (Line 2) ................................................ 2-45 Table 2-45 Breakdown of Arg Fields in Output (Line 3) ................................................ 2-45 Table 2-46 Breakdown of Arg Fields in Output (Line 4) ................................................ 2-46 Table 2-47 Zoning Request Codes for Zoning Exchange................................................ 2-46 Table 2-48 Zoning Operation Codes ............................................................................... 2-46 Table 2-49 Zoning Request Response Codes .................................................................. 2-47 Table 2-50 Zoning Reason Codes.................................................................................... 2-47 Table 2-51 TZone - New Zoning SFC Request's Operation Request Values.................. 2-47 Table 2-52 Zoning Transaction Abort Reason Codes ..................................................... 2-48 Table 2-53 Specific Opcode ............................................................................................ 2-48 Table 2-54 Configuration Operations .............................................................................. 2-48 Table 2-55 Zone Object Types ........................................................................................ 2-49 Table 2-56 Zone error (tzone- reject) Code ..................................................................... 2-49 Table 2-57 FSS Field Descriptions .................................................................................. 2-50
ii
Table 2-58 FSS Messages................................................................................................ 2-50 Table 2-59 FSSk Component Identification .................................................................... 2-52 Table 2-60 Fabric Services Response Command Codes ................................................. 2-54 Table 2-61 Fabric Services Reject Reason Codes ........................................................... 2-54 Table 2-62 Fabric Service Reject Reason Code Explanation .......................................... 2-54 Table 2-63 Fabric Segmentation Reason Details for Port ............................................... 2-55 Table 2-64 ISL Flow Control Mode Values .................................................................... 2-56 Table 2-65 ISL Flow Control Parameters........................................................................ 2-56 Table 2-66 Switch_Priority Field Values ........................................................................ 2-56 Table 2-67 FC-CT Frame ................................................................................................ 2-57 Table 2-68 Type of FC-CT Header Usage....................................................................... 2-57 Table 2-69 Basic CT_IU Preamble.................................................................................. 2-57 Table 2-70 GS_Type Values............................................................................................ 2-58 Table 2-71 Nx_port Name Server Examples (Most Common R_CTL) .......................... 2-59 Table 2-72 Name Server Command Codes ..................................................................... 2-59 Table 2-73 FC-CT Response Commands ........................................................................ 2-62 Table 2-74 FC-CT Reject Reason Code .......................................................................... 2-62 Table 2-75 Name Server Command Codes - Fabric Internal FC_CT Commands .......... 2-63 Table 2-76 Name Server Request Types ...................................................................... 2-63 Table 2-77 Name Server Objects.................................................................................. 2-64 Table 2-78 Name Server Port Type ................................................................................. 2-64 Table 2-79 Name Service GS_Subtype Code.................................................................. 2-65 Table 2-80 FC-4 Type Code ............................................................................................ 2-65 Table 2-81 Server-to-Server Protocol Data Unit Command/Response Code.................. 2-65 Table 2-82 NSS_CT Command/Response Code ............................................................. 2-66 Table 2-83 FC-CT Response Commands ........................................................................ 2-66 Table 2-84 FC-CT Reject Reason Code .......................................................................... 2-66 Table 2-85 Get FC4-Type Node Name, 0173 Frame ...................................................... 2-69 Table 2-86 Accept Get FC4-Type Node Name, 0173 Frame .......................................... 2-70 Table 2-87 Management Server Command Code............................................................ 2-71 Table 2-88 GS_Subtype Code ......................................................................................... 2-78
iii
Table 2-89 Management Server Reason Code and Explanation ..................................... 2-78 Table 2-90 Breakdown of Arg Fields in Output (Line 1) ................................................ 2-81 Table 2-91 Breakdown of Arg Fields in Output (Line 2) ................................................ 2-81 Table 2-92 Breakdown of Arg Fields in Output (Line 5) ................................................ 2-82 Table 2-93 Alias Service Request Code (FC_GS-1) ....................................................... 2-82 Table 2-94 F_BSY Reason Code..................................................................................... 2-85 Table 2-95 Point-to-Point Link - Primitive Signals....................................................... 2-103 Table 2-96 Point-to-Point Link - Primitive Sequences.................................................. 2-104 Table 2-97 Arbitrated Loop - Primitive Signals ............................................................ 2-104 Table 2-98 Arbitrated Loop - Primitive Sequence......................................................... 2-105 Table 2-99 Port State Machine Values .......................................................................... 2-105 Table 2-100 Well-Known Addresses............................................................................. 2-106 Table 2-101 Valid AL_PA Addresses ........................................................................... 2-107
iv
Preface
The Brocade PortlogDump Reference Guide is focused on providing information about portlogDump output (traces). This will help with utilizing portlogDump output for information gathering and troubleshooting. The Brocade PortlogDump Reference Guide is intended to be used in conjunction with existing Brocade manuals, release notes, and related Brocade publications.
Audience
The Brocade PortlogDump Reference Guide is targeted for use by storage administrators, SAN administrators, system administrators, systems engineers, and SAN operators that are involved with the information gathering and troubleshooting of SANs. The Brocade PortlogDump Reference Guide is an advanced document. Using the portlogdump Reference requires that the user be familiar with the Fibre Channel Physical (FC_PH) frame and the portlogdump format, and also understand types of frames. The reader is expected to have working experience with Brocade products. General computer system level troubleshooting skills are always important when troubleshooting sophisticated enterprise solutions. System administration or storage administration experience is also helpful in comprehending this document. This document is intended for use with SilkWorm switches running Fabric OS v 4.x. However, portlogdump information for Fabric OS 3.x and 2.x. is also provided for mixed fabric situations.
Guideline Conventions
The formatting and conventions used in this document are designed to help the reader locate and comprehend information quickly.
Formatting
The following table describes the formatting conventions that are used in this book: Convention bold text Purpose
italic text
code text
identifies GUI elements identifies keywords/operands identifies menu selections at the GUI or CLI provides emphasis identifies variables identifies paths and internet addresses identifies book titles and cross references identifies commands in line with text identifies CLI output
Notes and Guidelines

In addition to the information provided in standard text, there are Guidelines, Notes, and Cautions to help focus the reader on important information. Note: Notes emphasize important information.
Guideline: Guidelines are recommendations for consideration. The adoption of these guidelines is a function of the users ability to interpret and correlate relevant SAN information and make decisions based upon their organization and SAN requirements.
Warning:
Warnings alert you to potential damage to hardware, firmware, software, or data.
Chapter
Understanding the Port Log Dump
The portlogdump command output (trace) is a powerful tool which is used to troubleshoot fabric issues. The portlogdump output provides detailed information about the actions and communications within a fabric. By understanding the processes that are taking place in the fabric, issues can be identified and located. This document contains detailed lists of the Fibre Channel codes required to decode portlogdump traces and/or Fibre Channel analyzer traces, and explains how to decode the Fabric OS portlogdump traces. Guideline: Depending on the Port Log settings, undocumented messages may appear in the portlogdump output. To prevent this from occurring refer to section 1.3.2. Displaying and Customizing the Portlogdump Output on page 1-5.
1.1. Reading Portlogdump Output

The portlogdump command displays the port log, showing a portion of the FC-PH header (refer to section 2.2. FC_PH Frames on page 2-7) and the payload (refer to section 2.13. Payload Information on page 2-87). Since a portlogdump output is long, a truncated example is presented. Example: Primary Portlogdump Example
RSL_SWT134:admin> portlogdump time task event port cmd args ------------------------------------------------16:30:41.780 PORT Rx 9 40 02fffffd,00fffffd,0061ffff,14000000 16:30:41.780 PORT Tx 9 0 c0fffffd,00fffffd,0061030f 16:30:42.503 PORT Tx 9 40 02fffffd,00fffffd,0310ffff,14000000 16:30:42.505 PORT Rx 9 0 c0fffffd,00fffffd,03100062 16:31:00.464 PORT Rx 9 20 02fffc01,00fffca0,0063ffff,01000000 16:31:00.464 PORT Tx 9 0 c0fffca0,00fffc01,00630311 16:31:00.465 nsd ctin 9 fc 000104a0,0000007f 16:31:00.465 nsd ctout 9 fc 00038002,00000003,01fffc01 16:31:00.466 PORT Tx 9 356 03fffca0,00fffc01,00630311,01000000 16:31:00.474 PORT Rx 9 0 c0fffc01,00fffca0,00630311 16:31:01.844 PORT Tx 9 40 02fffffd,00fffffd,0312ffff,14000000 16:31:01.854 PORT Rx 9 0 c0fffffd,00fffffd,03120064 16:31:01.963 PORT Rx 9 40 02fffffd,00fffffd,0065ffff,14000000 16:31:01.963 PORT Tx 9 0 c0fffffd,00fffffd,00650313 16:31:14.726 INTR pstate 0 LF2 16:31:14.729 PORT scn 0 137 00000000,00000000,00000008 16:31:14.729 PORT scn 0 129 00000000,00000000,00000400 16:31:14.729 PORT scn 0 2 00010004,00000000,00000002 16:31:14.730 SPEE sn 0 ws 00000002,00000000,00000000 <output truncated>
1-1
The primary example is broken down by line and defined by information unit in the following examples. Example: Date: The date and time the event occurred.
time task event port cmd args ------------------------------------------------16:30:41.780 PORT Rx 9 40 02fffffd,00fffffd,0061ffff,14000000
Example: Task: The task that was in progress when the event occurred. Refer to section 2.1.1. Task Descriptions on page 2-1 for more information.
Example: Event: The specific action described in the output. Refer to Table 2-3 for more information.
Example: Port: The port field indicates the physical port on which the event occurred.
Example: Cmd: The commands associated with each event category.

Example: Args: The args filed indicates arguments associated with a task or event. Refer to section 2.1.5. Args on page 2-6 for more information.
1-2
1.2. Variations in Portlogdump Output by Fabric OS Version

The portlogdump output has changed slightly as Brocade Fabric OS has evolved, causing variations in the portlogdump output. These variations are noticed in the Task field and the Args field. The following table highlights the variations by version of Fabric OS. Table 1-1 Fabric OS Variations Task Field Args Field Prior to Fabric OS v2.1.2, portlogdump format displays only three arguments in the args field. The first two arguments belong to the FC_PH header (Word 0 and Word 1). The third argument belongs to the payload (Word 6). In Fabric OS v2.1.2 and greater, the portlogdump format displays four arguments in the args field. The first three arguments belong the FC_PH header (Word 0,Word 1, and Word 4). The fourth argument belongs to the payload. A t is displayed before a command in Fabric OS v3.x. Example of Fabric OS 3.x: tFspf Example of Fabric OS 3.x
time task event port cmd args ------------------------------------------------00:44:26.599 tFspf Tx 8 40 02fffffd,00fffffd,0284ffff,14000000,10cac760
Fabric OS Version v2.x or older
v2.x or greater
v3.x
Firmware v3.0 and greater displays five arguments in the args field, as shown below.
v4.x
The t does not appear before commands in Fabric OS v4.0 and greater. Example of Fabric OS 4.x: Fspf
In most instances, the fifth argument does not appear in Fabric OS v4.x output.
Example of Fabric OS v4.x

1-3
1.3. Using and Customizing the portlogdump

There are several commands that can be used to view certain aspects of the portlogdump (such as a list of events) and customize the output of the portlogdump. Refer to the Fabric OS Reference for more detailed command information.
1.3.1. Portlogdump Related Commands

The following commands are related to the portlogdump. Table 1-2 Command portlogdump [count[, saved[, portid]]] portlogdumpport portid portlogdump-Related Commands Action Displays the port log, listing all entries in the log without page breaks. This command displays the same information as portlogshow, but portlogshow prompts the user to enter return between each page of output. Displays the port log of the specified port. The command displays all entries in the log without any page breaks. It is identical to portlogshow, except that portlogshow prompts the user to enter return between each page of output. Displays the port log. This command displays 22 entries at a time. The portlogshow command displays the same information as portlogdump, but it has page breaks, prompting the user to enter a return after each page of output. Clears the port log. It is recommended to clear the port log before triggering an activity so that the log displays only the OUTPUT related to that activity. Displays the ID associated with the Event, the event, and the enabled/disabled status of the Event. Note: A disabled Event will not appear in the portlogdump. 0 = Enabled, 1 = Disabled. Displays the port log of a specified port, showing 22 entries at a time. It is identical to portlogdump, but it has page breaks, prompting the user to enter a return after each page of output. Disables the port log for a specified port log type. Disabling the port log type prevents it from appearing in the port log. Enables the port log for a specified port log type. Enabling the port log type allows it to appear in the port log.
portlogshow [count, saved, portid] portlogclear portlogeventshow
portlogshowport [portid]
portlogtypedisable type portlogtypeenable type
1-4
1.3.2. Displaying and Customizing the Portlogdump Output

A portlog event is the specific action that is being described by the output. For a complete list of possible Events for your switch, refer to section 2.1.2. Event on page 2-4. Use the following procedure to list portLog Events, and to find their associated ID number. 1. 2. Log into the switch as admin. Enter the command portlogeventshow.

3.
The left column displays the ID associated with the Event. This number can be used to enable/disable a particular event, keeping it from appearing in the portlogdump output. The middle column displays the Events. The right column displays the enabled/disabled status of the Event. A disabled Event will not appear in the portlogdump. 0 = Enabled, 1 = Disabled.
Enter one of the following commands:
portlogtypeenable type - to enable the particular Event in the portlogdump output. Type is the ID Number from step 2. portlogtypedisable type - to disable the particular Event in the portlogdump output. Type is the ID Number from step 2.
In the following example, the start Event is disabled. It will not appear in the portlogdump output.
1-5
Example: Portlogeventshow
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 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 switch:admin> portlogtypedisable 1
1-6
1.4. Locating Information by Task

Table 1-3 is an information map. It shows how and where to locate all non-E_Port specific portlogdump information. Table 1-3 Task tFabric portlogdump Information Mapping Table Event RSCN Port Command
t
Argument N/A
Definition / Reference section 2.3.2. SCN Codes and Descriptions on page 2-14 section 2.1.2. Event on page 2-4 section 2.5.1. I/O Control (ioctl) on page 2-22 section 2.14.2. Port State Machine Values (pstate) on page 2-105 ELS / R_CTL=22/23: section 2.6.1. ELS Command Code on page 2-30 FC-CT/R_CTL=02/03: section 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 displayed (4th argument) is from the payload, FC Word 6, and represents the FC-CT revision type being used. Additional payload information is found in corresponding ctin and ctout portlogdump events. on page 2-57
Switch ID N/A
enable ioctl pstate
Port # Port # Port #
1 = enable 2 = disable IOCTL code Port State Machine
IU pointer, 0 IU pointer, 0 N/A
Tx( )
Port #
Size of payload in bytes
Check R_CTL in section 2.2.1.1. Routing Control Bits (R_CTL) on page 2-7
1-7
1
Task tFCP
Understanding the Port Log Dump portlogdump Information Mapping Table (Continued) Event Tx( ) Port Port # Command Size of payload in bytes Argument Check R_CTL in section 2.2.1.1. Routing Control Bits (R_CTL) on page 2-7 Definition / Reference ELS / R_CTL=22/23: section 2.6.1. ELS Command Code on page 2-30 FC-CT/R_CTL=02/03: section 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 displayed (4th argument) is from the payload, FC Word 6, and represents the FC-CT revision type being used. Additional payload information is found in corresponding ctin and ctout portlogdump events. on page 2-57
Table 1-3
1-8
Understanding the Port Log Dump Table 1-3 Task portlogdump Information Mapping Table (Continued) Event FSPF ioctl Port Port # Command Argument
Definition / Reference ELS / R_CTL=22/23: section 2.6.1. ELS Command Code on page 2-30 FC-CT/R_CTL=02/03: section 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 displayed (4th argument) is from the payload, FC Word 6, and represents the FC-CT revision type being used. Additional payload information is found in corresponding ctin and ctout portlogdump events. on page 2-57
ioctl tFCPH loopscn
Port # Port #
IOCTL code Loopscan code
IU pointer, 0 N/A
section 2.5.1. I/O Control (ioctl) on page 2-22 section 2.4.1. LoopSCN Code on page 2-17
1-9
1
Task tFSPF
Understanding the Port Log Dump portlogdump Information Mapping Table (Continued) Event ioctl Tx( ) Port Port # Port # Command IOCTL code Size of payload in bytes Argument IU pointer, 0 Check R_CTL on section 2.2.1.1. Routing Control Bits (R_CTL) on page 2-7 Definition / Reference section 2.5.1. I/O Control (ioctl) on page 2-22 ELS / R_CTL=22/23: section 2.6.1. ELS Command Code on page 2-30 FC-CT/R_CTL=02/03: section 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 displayed (4th argument) is from the payload, FC Word 6, and represents the FC-CT revision type being used. Additional payload information is found in corresponding ctin and ctout portlogdump events. on page 2-57
Table 1-3
Interrupt
pstate
Port #
Port State Machine Code Internal SCN Value Speed negotiation code LIP
N/A
section 2.4.2. SilkWorm Port Physical State Values on page 2-18 Table 2-12 on page 2-14 section 2.5. Speed Negotiation on page 2-19 section 2.4.1. LoopSCN Code on page 2-17
scn sn tLOOP loopscn
Port # Port # Port #
scn code Speed negotiation keys and definitions Loop code
1-10
Understanding the Port Log Dump Table 1-3 Task tMSd portlogdump Information Mapping Table (Continued) Event Tx Port Port # Command Size of payload in bytes Argument Check R_CTL on section 2.2.1.1. Routing Control Bits (R_CTL) on page 2-7
Definition / Reference ELS / R_CTL=22/23: section 2.6.1. ELS Command Code on page 2-30 FC-CT/R_CTL=02/03: section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57
ctin
Port #
CT_Type
FC_CTs payload
section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57 section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57 section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57 section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57 section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57 section 2.5.1. I/O Control (ioctl) on page 2-22 section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57
ctout
Port #
FC_CTs payload
tNSCAM
nsRemR
Port #
FC_CT response code Word 0, Word 1, nameserver port type, IU pointer
nsRemQ
Port #
Fabric Internal FC-CT command
Word 0, Word 1, nameserver port type, IU pointer
RSCN
Port #
Request ID (24 bit addresses)
N/A
ioctl tx
Port # Port #
IOCTL code Size of payload in bytes
pointer, 1 N/A
1-11
1
Task tNsd
Understanding the Port Log Dump portlogdump Information Mapping Table (Continued) Event ctin Port Port # Command Last byte of Well-Known address Argument FC_CT's payload Definition / Reference section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57 section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57 section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57 section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57 See section 2.7.3.3. NSD Example on page 2-43 which will refer you to ILS Command Codes Table 2-33 on page 2-38 to interpret arg 2
Table 1-3
ctout
Port #
Last byte of Well-Known address
FC_CT's payload
nsRemR
Port #
FC_CT's payload
sRemQ
Port #
Fabric Internal FC-CT command
RSCN fffcxx to fffcyy
0 followed by the last 3 bytes of FC word 0 which represent the D_ID
arg 1 is FC word 1 arg 2 is SW_ILS Command Code arg 3 represents affected N_Port information arg 4 represents the detection function
RSCN fffffd to end device that did an SCR
See section 2.7.3.3. NSD Example on page 2-43 arg 2 is ELS Command Code which will refer you to ELS Command Codes arg 3 represents affected section 2.6.1. ELS N_Port information Command Code on page arg 4 represents the detection 2-30 to interpret arg 2 function arg 1 is FC word 1 Word 0, Word 1, Word 4, ELS Cmd Code Check R_CTL on section 2.2.1.1. Routing Control Bits (R_CTL) on page 2-7 ELS / R_CTL=22/23: section 2.6.1. ELS Command Code on page 2-30 FC-CT/R_CTL=02/03: section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57 section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57
Tx( )
Port #
create
null
null
tNSCAM
1-12
Understanding the Port Log Dump Table 1-3 Task tReceive portlogdump Information Mapping Table (Continued) Event Busy Port Port # Command Busy Reason Code Argument 01 = Physical N_port_busy 03 = N_port_resource_busy N/A N/A N/A LLI
Definition / Reference Table 2-29 on page 2-32
disable ioctl loopscn pstate
Port # Port # Port # Port #
1 = enable, 2 = disable IOCTL code Loopscan code Port State Machine Code null
N/A section 2.5.1. I/O Control (ioctl) on page 2-22 section 2.4.1. LoopSCN Code on page 2-17 section 2.14.2. Port State Machine Values (pstate) on page 2-105 ELS / R_CTL=22/23: section 2.6.1. ELS Command Code on page 2-30 FC-CT/R_CTL=02/03:Ta ble 2-72 on page 2-59
reject
Port #
Table 2-29 on page 2-32
Rx( )
Port #
Check R_CTL on section 2.2.1.1. Routing Control Bits (R_CTL) on page 2-7
ELS / R_CTL=22/23: section 2.6.1. ELS Command Code on page 2-30 FC-CT/R_CTL=02/03: section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57
scn
Port #
SCN Code.
Null
section Internal State Change Notification (SCN) on page 2-13
1-13
1
Task
Understanding the Port Log Dump portlogdump Information Mapping Table (Continued) Event Tx( ) Port Port # Command Size of payload in bytes Argument Check R_CTL on section 2.2.1.1. Routing Control Bits (R_CTL) on page 2-7 Definition / Reference ELS / R_CTL=22/23: section 2.6.1. ELS Command Code on page 2-30 FC-CT/R_CTL=02/03: section 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 displayed (4th argument) is from the payload, FC Word 6, and represents the FC-CT revision type being used. Additional payload information is found in corresponding ctin and ctout portlogdump events. on page 2-57 sn Port # Speed negotiation code Speed negotiation keys and definitions section 2.5. Speed Negotiation on page 2-19
Table 1-3
1-14
Understanding the Port Log Dump Table 1-3 Task portlogdump Information Mapping Table (Continued) Event Port Port # Command Size of payload in bytes Argument Check R_CTL on section 2.2.1.1. Routing Control Bits (R_CTL) on page 2-7
Definition / Reference ELS / R_CTL=22/23: section 2.6.1. ELS Command Code on page 2-30 FC-CT/R_CTL=02/03: section 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 displayed (4th argument) is from the payload, FC Word 6, and represents the FC-CT revision type being used. Additional payload information is found in corresponding ctin and ctout portlogdump events. on page 2-57
tResponse Tx( )
tRT tRtwr
Tx debug Tx
Port # 255 Port #
ILS command code Respond IU, sent IU
Table 2-1 on page 2-1 Table 2-1 on page 2-1 Table 2-1 on page 2-1
Respond IU, sent IU
1-15
1
Task tShell
Understanding the Port Log Dump portlogdump Information Mapping Table (Continued) Event Tx( ) Port Port # Command Size of payload in bytes Argument Check R_CTL on section 2.2.1.1. Routing Control Bits (R_CTL) on page 2-7 Definition / Reference ELS / R_CTL=22/23: section 2.6.1. ELS Command Code on page 2-30 FC-CT/R_CTL=02/03: section 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 displayed (4th argument) is from the payload, FC Word 6, and represents the FC-CT revision type being used. Additional payload information is found in corresponding ctin and ctout portlogdump events. on page 2-57 ioctl sn Port # Port Ioctl code Speed negotiation code null UI pointer, 0 Speed negotiation keys and definitions tFaScn section 2.5.1. I/O Control (ioctl) on page 2-22 section 2.5. Speed Negotiation on page 2-19 section 2.1.1. Task Descriptions on page 2-1
Table 1-3
tsnmpd
create
1-16
Understanding the Port Log Dump Table 1-3 Task tSwitch portlogdump Information Mapping Table (Continued) Event ioctl pstate Port Port # Port # Command Ioctl code Port State Machine Argument N/A N/A
Definition / Reference section 2.5.1. I/O Control (ioctl) on page 2-22 section 2.14.2. Port State Machine Values (pstate) on page 2-105 section 2.5. Speed Negotiation on page 2-19 ELS / R_CTL=22/23: section 2.6.1. ELS Command Code on page 2-30 FC-CT/R_CTL=02/03: section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57
sn Tx( )
Port # Port #
Speed negotiation code Size of payload in bytes
Speed negotiation keys and definitions Check R_CTL on section 2.2.1.1. Routing Control Bits (R_CTL) on page 2-7
create errlog
Table 2-3 on page 2-4 Refer to the Brocade Diagnostics and Error Messages Guide 0 = The switch started with all ports enabled 100 = The switch started with all ports disabled
start
disable
2 = Offline 3 = Testing 4 = Faulty Port # Port # BF (build fabric) Size of payload SW_ILS command codes FC-CT payload Table 2-33 on page 2-38 section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57 section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57 section 2.5.1. I/O Control (ioctl) on page 2-22
tTransmit
Reconf ctin
ctout
Port #
Size of payload
FC-CT payload
Ioctl
Port #
IOCTL code
1-17
1
Task tZone
Understanding the Port Log Dump portlogdump Information Mapping Table (Continued) Event Ioctl Reject Port Port # Port # Command IOCTL code Reject Argument IU pointer, IU pointer Reject code on section 2.7.2. SW_ILS Reject Reason Codes (SW_RJT) on page 2-40 Check R_CTL on section 2.2.1.1. Routing Control Bits (R_CTL) on page 2-7 Definition / Reference section 2.5.1. I/O Control (ioctl) on page 2-22 Table 2-29 on page 2-32
Table 1-3
Tx( )
Port #
ELS / R_CTL=22/23: section 2.6.1. ELS Command Code on page 2-30 FC-CT/R_CTL=02/03: section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57
Rx( )
Port #
ELS / R_CTL=22/23: section 2.6.1. ELS Command Code on page 2-30 FC-CT/R_CTL=02/03: section 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 displayed (4th argument) is from the payload, FC Word 6, and represents the FC-CT revision type being used. Additional payload information is found in corresponding ctin and ctout portlogdump events. on page 2-57
1-18
Understanding the Port Log Dump Table 1-3 Task PORT portlogdump Information Mapping Table (Continued) Event ioctl scn Tx ( ) Port port# port# port# Command IOCTL Code SCN Code Size of payload in bytes Argument domain, egress port Null Check R_CTL on section 2.2.1.1. Routing Control Bits (R_CTL) on page 2-7
Definition / Reference section 2.5.1. I/O Control (ioctl) on page 2-22 Table 2-12 on page 2-14 ELS / R_CTL=22/23: section 2.6.1. ELS Command Code on page 2-30 FC-CT/R_CTL=02/03: section 2.10.3.2. FC-CT Response Commands on page 2-62
Rx ( )
port#
ELS / R_CTL=22/23: section 2.6.1. ELS Command Code on page 2-30 FC-CT/R_CTL=02/03: section 2.10.3.2. FC-CT Response Commands on page 2-62
routing
Arguments 1 - 4
section 2.5.2. Reading a Routing Event on page 2-29 section 2.14.2. Port State Machine Values (pstate) on page 2-105 Internal debug codes Brocade ASIC LOOP Code LoopSCN Reason Code column debug section 2.4.1. LoopSCN Code on page 2-17
INTR
PS (primitive sequence) pstate debug loopscn
port#
State Machine Value
FLTR LOOP
Port# Port#
NA Loopscan code Brocade ASIC LOOP Code cmd column
1-19
1
Task nsd
Understanding the Port Log Dump portlogdump Information Mapping Table (Continued) Event ctin Port Port# Command Last byte of Well-Known address Argument FC_CTs payload Definition / Reference section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57 section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57 See section 2.7.3.3. NSD Example on page 2-43 which will refer you to ILS Command Codes Table 2-33 on page 2-38 to interpret arg 2
Table 1-3
ctout
Port#
FC_CTs payload
RSCN fffcxx to fffcyy
arg 1 is FC word 1 arg 2 is SW_ILS Command Code arg 3 represents affected N_Port information arg 4 represents the detection function
RSCN fffffd to end device that did an SCR
See section 2.7.3.3. NSD Example on page 2-43 arg 2 is ELS Command Code which will refer you to ELS Command Codes arg 3 represents affected section 2.6.1. ELS N_Port information Command Code on page arg 4 represents the detection 2-30 to interpret arg 2 function arg 1 is FC word 1 D_ID, S_ID, Name Server Port Type section 2.10.3. Name Server Commands and Code Descriptions on page 2-59 section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57
nsRemQ
0: 1st Last 3 nibbles: Name nibble NS Server Cmd code. cmd code Fabric internal FC-CT cmd codes section 2.10.3. Name Server Commands and Code Descriptions on page 2-59 Port# Name Server Cmd Code section 2.10.3. Name Server Commands and Code Descriptions on page 2-59 Last byte of Well-Known address
NsRemR
D_ID, S_ID, Additional information command code
section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57
msd
ctin
Port#
FC-CTs payload
section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57 section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57
ctout
Port#
FC-CTs payload
1-20
Understanding the Port Log Dump Table 1-3 Task FSS or FSSK portlogdump Information Mapping Table (Continued) Event msg Port N/A Command Argument Service ID, Component ID, Send receive data, optional flags, additional text description.
Definition / Reference section 2.7.5. FSS Messages on page 2-50
cmd event SPEE sn
N/A N/A Port # Speed negotiation code Speed negotiation keys and definitions
section 2.7.5. FSS Messages on page 2-50 section 2.7.5. FSS Messages on page 2-50 section 2.5. Speed Negotiation on page 2-19
1-21
1-22
Chapter
Troubleshooting Using the Port Logs 2.1. About the Portlogdump Fields
This section defines each field in a portlogdump output. These fields include:
Task Event Port Command (cmd) Arguments (args)
2.1.1. Task Descriptions

Table 2-1and Table 2-2 list the Tasks description and functionality for Fabric OS v2.x, v3.x, and v4.x. Table 2-1 Task tASd tErrlog tFabric tFaScn tFCP tFCPH tFCPth tFspf tHttpD tInterrupt tMsApi tMSd tNSCAM tNsd tReceive Fabric OS v2.x and v3.x Task Descriptions Description Alias Server Daemon Error Log Fabric Fabric Assist State Change Notification Fibre Channel Protocol Fibre Channel Physical Functionality The Alias service is used for managing multicast groups by supporting the create, add, remove, and destroy functions. Information fed into the error log task can be viewed using errShow/Dump commands. Fabric initialization. Fabric configuration. FC-ILS protocol - ELP, EFP Refers to Fabric Assist updates and changes. Refer to section 2.3. State Change Notification (SCN) on page 2-13. Probe - query SCSI command Handles frame sequences for FC-2 processes Frame at FC-2 level and below. Monitors SCSI static components in Fabric Fibre Channel Shortest Path First Routing Web Server Daemon Interrupt Management Server Application Programming Interface Management Server Daemon Name Server Cache Manager. Name Server Daemon Receive Monitors the Web Server See event associated with interrupt to identify the interrupt reason. Allows API calls into the switch for management and monitoring purposes. Monitors the MS - includes the Fabric Configuration Service and the Unzoned Name Server. It updates the Name Server (NS) data bases across switches as a background task. Monitors Name Server. Handle all frames received.
2-1
Brocade Portlogdump Reference Guide
2
Task
Troubleshooting Using the Port Logs Fabric OS v2.x and v3.x Task Descriptions (Continued) Description Functionality Sequence of the initiate. Task reboots system after stopping all activity. Remote Login Information. Events to be delivered, but time is not an issue (e.g., zoning delta propagation - persistently retries transmission of changed information to another switch).
Table 2-1
tResponse Response TRestart tRlogind tRT Restart Remote login daemon Reliable Transmission Task
tRtwr tSnmpd tShell tSwitch tSyslog Task tThad tTimers tThFru tTransmit
Reliable Transmission With Response Task SNMP Agent Daemon Telnet Switch Syslog daemon Description Threshold Timer Threshold Field Replaceable Unit Transmits Monitors static components in Fabric. A telnet task that starts up a shell in VX works. First task started to control switch like a parent task. Major function includes initializing Mac address. Used to forward error messages. Functionality Monitors static components in fabric. Time Out functions. A FW task that monitors physical/FRU components in fabric- comes as a default regardless of whether FW license exists. Sequences switch initiates.
2-2
Troubleshooting Using the Port Logs Table 2-2 Task Fabric OS v4.x Task Descriptions Description Functionality
Fabric OS v4.x Specific Tasks INTR PORT Internal Port kernel driver Events associated with this task: Port State (PS), and Debug Equivalent to Receive and Transmit in Fabric OS v3.x code, and any frame transmit or receive on behalf of any user processes (daemons). Events associated with task: debug, I/O control, State Change Notification, Transmit and Receive. SPEE FLTR LOOP nsd msd asd Speed Filtering Loop Name Server Daemon Management Server Daemon Alias Server Daemon ASIC speed negotiation function; speed selection between 1 or 2 Gbit/sec. ASIC frame filtering function; used in WWN zoning (WWN). ASIC loop function; loop port initialization. NS daemon, it is the same as tNSd for Fabric OS v3.x MS daemon, it is the same as tMSd for Fabric OS v3.x AS daemon, is the same as ASd for Fabric OS v3.x. Event associated with this task: ctin and ctout fspfd zone fcpd FSS Fibre Channel Shortest Path First Zoning N/A Fabric OS State Synchronization. Event associated with this task: Neighbor state transition Event associated with this task: debug No event is associated with this task. 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.
2-3
2.1.2. 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 Table 2-3. The following example indicates an internal task (INTR) --> associated event is the Port State Machine (pstate) --> and the cmd field describes the event, which is a link failure (LF2). Example:
portlogdump: time task event port cmd args ------------------------------------------------15:48:11.473 INTR pstate 19 LF2 15:48:11.474 INTR pstate 19 LF1 15:48:11.474 INTR pstate 19 OL2 15:48:11.474 INTR pstate 19 LR2 15:48:11.474 INTR pstate 19 LR3 15:48:11.474 INTR pstate 19 AC 15:48:11.474 PORT scn 19 11 00000000,00000000,00010000
Table 2-3 provides descriptions of possible events. Table 2-3 Event start disable enable ioctl Tx Tx() Rx Rx() stats scn pstate reject busy ctin ctout errlog loopscn create debug nbrfsm timer sn nsRemQ nsRemR Event Descriptions Description Describes a switch start or re-start event. Indicates a port is disabled. Indicates a port is enabled. Indicates a port I/O control is executed. Indicates a frame is transmitted. Indicates a frame is transmitted, class 1, 2 or 3. Indicates a frame is received. Indicates a frame is transmitted, class 1, 2 or 3. Indicates a port status or statistics. Indicates a state change notification. Indicates a port changes physical state. Indicates that a frame is rejected. Indicates a received frame is busied. Indicates a Common Transport (CT) based request is received. Indicates a Common Transport (CT) based response is transmitted. Indicates a message is added to the error log. Indicates a loop state change notification. Indicates a task is created. Indicates generic debugging information. Indicates a neighbor state transition. Indicates a timer. Indicates a speed negotiation. Indicates an inter-sw NS query. Indicates an inter-sw NS response.
2-4
Troubleshooting Using the Port Logs Table 2-3 Event RSCN Reconf Debug ps Event Descriptions Description Indicates a Registered State Change Notification (RSCN). Indicates a fabric reconfiguration. Indicates generic debugging information. Indicates a primitive sequence - used to denote pstates.
2.1.3. Port
The port field in the portlogdump output indicates a physical port number. Example:
Nov 25 task event port cmd args ---------------------------------------------11:00:48.433 tReceive Rx 12 40 02fffffd,00fffffd,00dbffff,14000000,11cd35a0 11:00:48.449 tTransmit Tx 12 0 c0fffffd,00fffffd,00db0189, ,11cd35a0 11:00:48.649 tReceive Rx3 5 116 22240300,00140500,07acffff,03000000,11cd35a0 11:00:48.649 tTransmit Tx3 2 116 22240300,00140500,07acffff,03000000,11cd35a0 11:00:49.166 tReceive Rx3 2 116 221500ef,17240300,0095ffff,03000000,11cd7480 11:00:49.166 tReceive reject 2 3 11:00:49.733 tFspf Tx 2 40 02fffffd,00fffffd,018affff,14000000,11cdc090
2.1.4. Cmd
The cmd field represents different values depending on the task and event. Commands (cmd) are associated with each event category. For example, in the following example output, the last line of the cmd column represents the scn code. If the event is a Rx or PORT the cmd is usually the size of the payload. Example:
portlogdump: time task event port cmd args ------------------------------------------------15:48:11.473 INTR pstate 19 LF2 15:48:11.474 INTR pstate 19 LF1 15:48:11.474 INTR pstate 19 OL2 15:48:11.474 INTR pstate 19 LR2 15:48:11.474 INTR pstate 19 LR3 15:48:11.474 INTR pstate 19 AC 15:48:11.474 PORT scn 19 11 00000000,00000000,00010000
Commands associated with an event category are also referred to as State Events. Possible commands are listed in Table 2-4. Table 2-4 Command AC FC LR1 LR2 LR3
List of Commands (cmd) Definition Active State Name Server (in MS) Link Reset: LR Transmit State Link Reset: LR Receive State Link Reset: LRR Receive State
2-5
Troubleshooting Using the Port Logs Table 2-4 Command LF1 LF2 OL1 OL2 OL3 LIP BMP LIM OLD OLP List of Commands (cmd) Definition Link Failure: NOS Transmit State Link Failure: NOS Receive State Offline: OLS Transmit State Offline: OLS Receive State Offline: Wait for OLS State For definitions of these commands refer to Table 2-16 on page 2-17
2.1.5. Args
The args field represents different values depending on the task and event. For more information about arguments, refer to section 2.5.2. Reading a Routing Event on page 2-29. Example:
time task event port cmd args ------------------------------------------------11:01:15.166 tNSCAM nsRemQ 0 4a0 00fffc24,00fffc14,0000007f,00000000 11:01:15.166 tNSCAM Tx 2 4 02fffc24,00fffc14,01adffff,0000007f,11cdde40 11:01:15.183 tReceive Rx 2 132 03fffc14,00fffc24,01ad032b,01000000,11cd35a0 11:01:15.183 tTransmit Tx 2 0 c0fffc24,00fffc14,01ad032b, ,11cd35a0
2-6
2.2. FC_PH Frames

For general Fibre Channel information, refer to section 2.14. Fibre Channel Protocol Information on page 2-103. 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 TYPE field (Word2, bit 31-24) will tell which information unit (IU) format to use. The routing control INFO bit (bit 27-24) determines how to interpret the payload. Table 2-5 4 S O F HEADER PAYLOAD 8 FC_PH Frame Diagram Up to 2112 Bytes 4 C R C 4 E O P
Table 2-6
FC_PH Frame Cross-References Word 0 1 Bits 31-24 Routing Control Bits (R_CTL) Class Specific Control Field (CS_CTL) Type Code Sequence ID (SEQ_ID) Data Field Control (DF_CTL) Bits 23-16 Bits 15-8 Bits 7-0
Destination_ID (D_ID) Sequence ID (SEQ_ID)
H E A D E R
2 3
Frame Control (F_CTL) Sequence Count (SEQ_CNT)
4 5
Originator_ID (OX_ID) Parameter Payload - 6 to N word
Responder_ID (RX_ID)
2.2.1. FC_PH Frames Definitions

2.2.1.1. Routing Control Bits (R_CTL)
Routing Control bits (R_CTL) are the first 8 bits of the header. They define the type of frame and its contents. The first four bits (Bit 31-28) of Word 0 identify the frame type. The second four bits INFO bit (Bit 27-24) defines the contents of the frame or identifies the function of the frame. Example:
00:44:26.599 tFspf Tx 8 40 02fffffd,00fffffd,0284ffff,14000000,10cac760
02 = R_CTL request
2-7
2
.
Troubleshooting Using the Port Logs Table 2-7 R_bits FC-4 Device Data x'0' Routing Control Bits - R_CTL Diagram Information 0 1 2 3 4 5 6 7 Extended Link Service x'2' 2 3 FC-4 Link Data x'3' Note: Same as FC-4 Device Data frames Basic Link Service x'8' 2 3 4 0 1 2 3 4 5 6 Others Link Control x'C' 0 1 2 3 4 5 6 7 8 9 Others Description Uncategorized Device Data Solicited Device Data Unsolicited Control Info (Request) Solicited Control Info (Reply) Unsolicited Device Data Data Descriptor Unsolicited Command Command Status Information Request Reply Request Reply Video Data No Operation (NOP) Abort Sequence (ABTS) Remove Connection (RMC) Reserved Basic_Accept (BA_ACC) Basic Reject (BA_RJT) Preempted (PRMT) Reserved ACK ACK N_Port Reject (P_RJT) Fabric Reject (F_RJT) N_Port Busy (P_BSY) Fabric Busy to Data Frame (F_BSY) Fabric Busy to Link_Control Frame (F_BSY) Link Credit Reset (LCR) Notify (NTY) End Reserved
2-8
2.2.1.2. Destination_ID (D_ID)

The Destination ID (D_ID) refers to the Native port address (24-bit address). It is located in Word 0, as indicated in bold below. Example: The fffffd field is the D_ID
Re
00:44:26.599
tFspf
Tx
40
02fffffd,00fffffd,0284ffff,14000000,10cac760
In the example above, the D_ID is the Well-Known Address of a Fabric Controller. Refer to section 2.14.3. Well-Known Addresses on page 2-106 for a list of all Well-Known Addresses.
2.2.1.3. Source_ID (S_ID)

The Source ID (S_ID) refers to the Native port address (24-bit address). It is located in Word 1, as indicated in bold below. Example: The fffffd field is the S_ID
In the example above, the S_ID is the Well-Known Address of a Fabric Controller. Refer to section 2.14.3. Well-Known Addresses on page 2-106 for a list of all Well-Known Addresses.
2.2.1.4. Frame Control (F_CTL)

This field contains miscellaneous control information regarding the frame. Table 2-8 Hex 0xC00000 0x800000 0x400000 0x200000 0x100000 0x080000 0x040000 0x020000 0x010000 0x800000 0x004000 0x003000 0x000800 0x000400 0x000200 0x000100 0x0000C0 0x0000C0 0x000080 0x000040 Frame Control (F_CTL) Diagram Abbreviation FCTL_XCHSEQ FCTL_RESPXCH FCTL_RECSEQ FCTL_1STSEQ FCTL_LASTSEQ FCTL_ENDSEQ FCTL_ENDCONN FCTL_CHAINEDSEQ FCTL_SEQINIT FCTL_NEWXID FCTL_INVXID FCTL_ACKFORM FCTL_COMPRESS FCTL_ENCRYPT FCTL_RETXSEQ FCTL_UNIDIRECTX FCTL_CSCMASK FCTL_SEQDLY FCTL_SEQSOON FCTL_SEQIMM Description Exch & Seq Context bit mask Responder of Exchange Sequence Recipient First sequence of Exchange Last sequence of Exchange Last data frame of sequence End of Connection pending Chained Sequence active Transfer sequence initiative X_ID reassigned Invalid X_ID Ack form capability Data compression Data encryption Sequence retransmission Unidirectional transmission Mask to get Cont Seq Condition Sequence to follow-delayed Sequence to follow-soon Sequence to follow-immediately
2-9
Frame Control Filed Bits (F_CTL)
Troubleshooting Using the Port Logs Table 2-8 0x000000 0x000030 0x000030 0x000020 0x000010 0x000000 0x000030 0x000030 0x000020 0x000010 0x000000 0x000008 0x000004 0x000003 0x060f00 0xffff Frame Control (F_CTL) Diagram FCTL_SEQNONE FCTL_ASCMASK FCTL_SEQABTR FCTL_SEQSTOP FCTL_SEQABTS FCTL_SEQCONT FCTL_POLICYMASK FCTL_DISCRETX FCTL_PROCESS FCTL_DISC1ABT FCTL_DISCMABT FCTL_RELOFF FCTL_XCHREASS FCTL_FILLMASK FCTL_INVALID NULL_XID No information Mask to get Abort Seq Condition Abort Seq - do ABTR Stop seq Abort seq - do ABTS Continue seq Mask to get seq policy Discard Multi Seq: Immed ReTx Process policy with Infinite Buf Discard single seq, abort Discard Multi seq, Abort Relative Offset present Exchange Reassembly - reserved Mask to get the fill bits Class 1, compression, encryption Unassigned ox_id or rx_id
Frame Control Filed Bits (F_CTL)
2.2.1.5. Sequence ID (SEQ_ID)

Used to identify and track all of the frames within a sequence between a source and destination port pair.
2.2.1.6. Sequence Count (SEQ_CNT)

Used to indicate the sequential order of frame transmission within a sequence or multiple consecutive sequences within the same exchange.
2.2.1.7. Originator_ID (OX_ID)

Originator_ID (OX_ID) refers to the exchange ID assigned by the originator port. It is located in Word 4, as indicated in bold below. In the example, 0284 is the Originator ID. Refer to Table 2-6 on page 2-7. Example:
2.2.1.8. Responder_ID (RX_ID)

The Responder_ID is assigned by the responder to the Exchange. It is located in Word 4, as indicated in bold below. In the example, ffff is the Responder ID. Refer to Table 2-6 on page 2-7. Example:
2.2.1.9. Data Field/Payload

The standard limits the size maximum up to 2112 bytes. Refer to section 2.2. FC_PH Frames on page 2-7 or FC_PH Frame Cross-References on page 2-7.
2-10
2.2.1.10. Type Code

The Type Code provides the type of protocol service (i.e., FC_CT, FCP, FCIP and etc.). Table 2-9 Code 1x 3x 00 01 04 05 06-07 08 09 0A-0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D-1F 20 21 22 23 24 25-27 28-2F 30-33 34-37 38-3F 40 41-47 48-57 58 59-DF E0-FF FC-4 Type Codes Type of Service F_BSY (Fabric Busy, x = R_CTL bits 27-24) F_BSY (N_Port Busy, x = R_CTL bits 27-24) Basic Link Service Extended Link Service ISO/IEC 8802-2 LLC (In order) ISO/IEC 8802-2 LLC/SNAP Reserved SCSI-FCP SCSI-GPP SCSI-Reserved Reserved: IPI-3 IPI-3 Master IPI-3 Slave IPI-3 Peer Reserved: IPI-3 CP IPI-3 Master CP IPI-3 Slave CP IPI-3 Peer Reserved: SBCCS SBCCS - Channel (obsolete) SBCCS - Control Unit (obsolete) SBCCS-2 - Channel (proposed) SBCCS-2 - Control Unit (proposed) Reserved: SBCCS Fibre Channel Services (FC-CT) FC-FG (not used) Internal Link Service (SW_ILS) FC-AL (not used) FC-SNMP Reserved: Fabric Services Reserved: Fabric Services Scalable Coherent Interface (SCI) MessageWay (FC-PH2) Reserved HIPPI - FP Reserved: HIPPI Reserved Virtual Interface (FC-VI) Reserved Vendor Unique
2-11
2.2.1.11. Data Field Control (DF_CTL)

This 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 2-10 0x40 0x20 0x10 0x03 0x8c Data Field Control (DF_CTL) Optional Headers DF_CTL SECURITY_HEADER NETWORK_HEADER ASSOCIATON_HEADER DEVICE_HEADER DF_RESERVED
2.2.1.12. Class Specific Control Field (CS_CTL)

Different controls are necessary for different classes of service. This field is always 0 (zero) per the standards. If the field is a non-zero value, then it is a Brocade internal CS_CTL code, as described in Table 2-11. Table 2-11
0x02 0x03 0x04 0x05 0x06 0x10 0x11 0x12 0x013 0x14 0x15 0x16 0x17 0x18 0x19 0x1a 0x1b 0x1c 0x20 0x21 0x22 0x23 0x24 0x80 0x81 0x82 0x83 0x84
2-12
Class Specific Control Field (CS_CTL) IU Status Values

IU_P_RJT IU_F_RJT IU_P_BSY IU_F_BSY IU_F_BSY_LC IU_NO_EXCH IU_OFFLINE IU_BAD_EXCH IU_NO_ACK IU_CORRUPT IU_BAD_CLASS IU_BAD_S_ID IU_BAD_D_ID IU_TIMED_OUT IU_TX_UNAVAIL IU_LOGIN_RQRD IU_PROTOCOL IU_RX_FLUSHED IU_ALPA_TMPNA IU_ALPA_PMTNA IU_LOGO_OFFLINE IU_ZONE_CONFLT IU_ABTS_RX IU_ASYNC_RESP IU_ASYNC_TO IU_ASYNC_ABTS IU_ASYNC_LOGO IU_ASYNC_ACKTO received P_RJT received F_RJT received P_BSY received F_BSY received F_BSY_LC cannot allocate exchange port is offline exchange ID not valid ED_TOV expired CRC err, encoding err, too long, etc class 1 frame invalid S_ID invalid D_ID, VC, or multicast address frame timed out, generate F_BSY Tx unavailable, generate F_BSY login required protocol error frame flushed by rx port AL_PA temporarily not available AL_PA permanently not available logo received or port goes offline Zone conflict Received an ABTS that flushed this IU async IU response payload received async IU response timeout async IU abtsed async IU killed due to port logout/offline async IU ack timeout
Brocade Specified Internal Code: CS_CTL (IU_Status Value)
async IU state, response
2.3. 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.
Register 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 shall be performed via the State Change Registration (SCR) Extended Link Service. An N_Port or NL_Port may 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.
2.3.1. Reading an SCN Event

The following examples show the same output from three different versions of firmware. Refer to section 2.3.2. SCN Codes and Descriptions on page 2-14 to view the cmd description. Example: Fabric OS v3.x
portLogDump time task event port cmd args --------------------------------------------------------------------------12:05:28.116 tReceive scn 13 0 137
Example: Fabric OS v4.0.x

time task event port cmd args -------------------------------------------------------------------12:05:28.116 PORT scn 13 137
Example: Fabric OS v4.2.0

time task event port cmd args -------------------------------------------------------------------12:05:28.116 PORT scn 7 137 00000000, 00000000, 00000008
The cmd represents the scn state. Refer to section 2.3.2. SCN Codes and Descriptions on page 2-14 to view the cmd description. Read the args columns as follows: - Arg 1 is dependant on the scn Type. For this example: First 16-bits (Most Significant) = The mode that the port is in. Refer to section 2.3.3. SCN Modes on page 2-15. Second 16-bits (Least Significant) = The error that causes the port to be marked OFFLINE. Refer to section 2.3.5. SCN Errors on page 2-16. Arg 2 is dependent on the scn Type; it is currently not used (00000000). Arg 3 is the scn type. Refer to section 2.3.4. SCN Types on page 2-15. Combine the scn type (the third arg) and the scn state (the cmd column) to uniquely identify a particular scn. The scn state alone is not sufficient, and is not guaranteed to be unique across all scn types. Refer to section 2.3.4. SCN Types on page 2-15.
2-13
2.3.2. SCN Codes and Descriptions

The SCN Codes described in Table 2-12 represent the SCN State, and appear in the cmd column of an SCN event. For Fabric OS v4.2.0, combine the SCN type (the first arg) and the SCN state (the cmd column) to uniquely identify a particular SCN. The SCN state alone is not sufficient, and is not guaranteed to be unique across all SCN types. Table 2-12 SCN Value 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 120 121
2-14
Internal State Change Notification (SCN) Command Codes Status UNKNOWN ONLINE OFFLINE TESTING FAULTY E_PORT F_PORT SEGMENTED T_Port AC_PORT LIP_ONLINE LR_Port FLOGI_DOC FORCE_OFFLINE BUF_ONLINE BUF_OFFLINE DOMAIN_VALID DOMAIN_INVALID DOMAIN_REACHABLE DOMAIN_UNREACHABLE Switch ONLINE Switch OFFLINE Zoning Configuration Change SWD_Switch_Heartbeat_Req (Watchdog probe timer expired) Description Port status is unknown Port is online (in active state) Port is offline Port is in use by diagnostics Port is marked faulty Port is an E_Port Port is Fabric aware port (F or FL) Port is segmented Port is a trunking port, not trunk master. Port is active; link reset is done for E_Port or master trunk port. Loop initialization occurred. Port is active; link reset is done for non-E_Port. FLOGI device Force OFFLINE a port that is already OFFLINE Became online by acquiring free buffers. Became offline due to lack of buffers A valid domain was reported. An invalid domain was reported. A reachable domain was reported. An unreachable domain was reported. A switch came online. A switch went offline. A zoning configuration change occurred. The software watchdog (which monitors Fabric OS modules on the kernel) probing timer expired.
SWD_Switch_Register_Req The software watchdog (which monitors Fabric OS modules (Software Watchdog register request) on the kernel) sent a register request. PASSWD_CHANGED SW_PERSISTENT_DISABLE REM_DOMAIN_SET REM_DOMAIN_CLEAR FLOGI_DCC FORCE_OFFLINE Sent when the switch is ready, i.e. after POST if POST is running, and the switch is currently persistently disabled. Routes to remote domain are set up Routes to remote domain are cleared FLOGI device Force OFFLINE a port that is already OFFLINE
Troubleshooting Using the Port Logs Table 2-12 SCN Value 122 123 128 129 135 136 137 138 144 145 Internal State Change Notification (SCN) Command Codes Status BUF_ONLINE BUF_OFFLINE FCP message probe, start probing FCP message flush, stop probing NS message update area NS message add area NS message delete area Route all done ROUTE_ALL_DONE Update SCR data Description became online by acquiring free buffers became offline due to lack of buffers Fibre Channel Protocol - message probing started. Fibre Channel Protocol - message probing stopped. Name Server update area Name Server add area Name Server message delete area Both domain and are routes are done. Both domain and are routes are done. State change registration data update
2.3.3. SCN Modes

SCN Modes appear in the first bit of Arg 1 for an port_scn Type. Refer to examples provided in section 2.3.1. Reading an SCN Event on page 2-13. Table 2-13 Value 0 1 2 3 SCN Modes Name PORT_SCN_MODE_NORMAL PORT_SCN_MODE_DISABLED PORT_SCN_MODE_LOOPBACK PORT_SCN_MODE_BYPASSED
2.3.4. SCN Types

The SCN Types appear in Arg 3. Refer to examples provided in section 2.3.1. Reading an SCN Event on page 2-13. Table 2-14 Code 0x00000001 0x00000002 0x00000008 0x00000100 0x00000400 0x00000800 0x00010000 0x00040000 Types of SCNs Abbreviation SWITCH_SCN PORT_SCN UPD_SCN ZONE_SCN FCP_SCN GBIC_SCN FAB_SCN SEC_SCN Description Switch state change notification Port state change notification Update state change notification Zone check FCP GBIC (SFP) module in/out scn Fabric application FLOGI device violation
2-15
2.3.5. SCN Errors

The following scn errors appear in the second bit of Arg 1 in a port_scn Type output. Refer to section 2.3.1. Reading an SCN Event on page 2-13. Table 2-15 Value 0 1 2 3 4 5 6 SCN Errors Name PORT_SCN_ERR_NO_ADDITIONAL_INFO PORT_SCN_ERR_NO_MODULE PORT_SCN_ERR_NO_LIGHT PORT_SCN_ERR_NO_SYNC PORT_SCN_ERR_NOT_ONLINE PORT_SCN_ERR_FAULT PORT_SCN_ERR_LASER_FAULT
2-16
2.4. Brocade Specific Code

This section contains tables used to identify and define Brocade specific code.
2.4.1. LoopSCN Code

Table 2-16 cmd LoopSCN Code (loopscan code) Reason Code 0x0 0xA45 0x5F4A 0x8001 0x8002 0x8003 LIP 0x8004 0x8005 0x8006 0x8007 0x8008 0x8009 0x800a 0x800b 0x800c 0x800d 0x800e 0x800f 0x8010 0x8011 0x8012 0x8013 0x8014 0x8015 0x816 F7F7 (F7,AL_PS) (F8,AL_PS) Retry loop init Start loop after gaining sync Restart loop after port reset LIP the loop after loop time-out Retransmitting LIP in ARBF0 LIP the loop if OPN(x,y) returns Start loop when transit out of G_Port Start loop if self loopback Per N_Port FLA LINIT ELS Per N_Port FLA LPC ELS Per QL LOOP_LIP Per QL LOOP_INIT LIP due to loop rdx buffer overflow Start loop because of loop diagnostic Per new Phantoms being added Per new Phantom being added (IPO) BloomInitRetry - loop init timed out BloomInitRetry - stuck at init state BloomInitRetry - no RSVD mini-buf for LISM BloomInitRetry - not pt-to-tp capable BloomInitRetry - no LISM rx in 2 AL_TIME BloomStopLinit - L to F transition The loop port in the initializing state is requesting loop initialization but does not currently have a valid AL_PA The loop port identified by the AL_PS value is requesting loop initialization. A loop interconnection has failed Description Loop entering OPEN_INIT state
(AL_PD,AL_PS) The Selective Reset LIP is used to perform a vendor specific reset at the loop port specified by the AL_PD value. AL_PD=FF as a destination indicating all ports. TMO BMP LIM OLD D6 D3 D2 D5 LIP time out. The loop initialization step timed out. Loop positional bitmap (QuickLoop). Loop Init completed, FL_Port in monitoring state. LISM completed, FL_Port became the loop initialization master. Loop initialization is trying to bring up the link in OLD PORT mode. This is typically seen when a switch is configured as QuickLoop. (Note: Fabric OS 4.x does not support QuickLoop) Offline
2-17
OLP
D0
2.4.2. SilkWorm Port Physical State Values

Table 2-17 State NO_CARD NO_Module LASER_FLT NO_LIGHT NO_SYNC IN_SYUNC PORT_FLT DIAG_FLT LOCK_REF Unknown Specific Physical State Values Description No optional card installed (Check license key) No GBIC module installed Laser fault No light being received Out of Synchronization In Synchronization Port Fault Diagnostic Fault Receiver Locking Reference Clock Port status is unknown
2.4.3. SilkWorm LED State Values

Table 2-18 LED State STEADY_BLACK STEADY_YELLOW SLOW_YELLOW FAST_YELLOW STEADY_GREEN SLOW_GREEN FAST_GREEN FLICKERING YELLOW_GREEN SilkWorm Specific LED State Values Description No light Receiving light, but not yet online Disabled (diagnostics or portDisable) Error, fault with port Online and ready to go Online but segmented Online in internal loopback Online and traffic flowing through port Bypass
2.4.4. SilkWorm Bypass Reason Code

Table 2-19 Code 1 2 3 Brocade Specific Bypass Reason Code Reason Disabled Potential E_Port QL task issued bypass
2-18
2.4.5. Switch Parameter Meanings

Table 2-20 Parameter TACHYON ISOLATED NOTYPES VCINDID USECSCTL NOCLASSF DISTANCE PID256FORMAT VCXLTLINIT Specific Switch Parameter Meanings Meaning Better IP behavior with Tachyon Do not probe for E_Ports Do not probe for broadcast or multicast VC encoding in DID (SilkWorm mode) Use CS_CTL in FC_header for vc Turn class 2 frames into class F frames Long distance fabric Use 256-port PID format Link init protocol for setup vcxlt mode note this is port wide config sent through op_mode in ELP
2.5. Speed Negotiation

Table 2-21 Portlog column 3 (Port) 3 (Port) 3 (Port) 4 (Cmd) 5 (Arguments) Speed Negotiation Task / Context SPEE PORT Interrupt SPEE, PORT or Interrupt SPEE, PORT or Interrupt Event sn sn sn sn Argument 1 Argument 2 Argument 3 Description Log is from this port and log belongs to speed negotiation see Table 2-22 on page 2-19. Log is from this port see Table 2-22 on page 2-19. Log is from this port see Table 2-22 on page 2-19. Speed negotiation command see Table 2-23 on page 2-20. See Table 2-24 on page 2-20. See Table 2-25 on page 2-21. See Table 2-26 on page 2-21.
Use the command setDbg SPEED 9 to enable speed logging. If speed logging is not enabled, only the first and the last line shown in the example will be displayed in the portLog. Table 2-22 Task SPEE - indicates Speed Negotiation Speed Negotiation Portlogs - Task, Event, and Port Event Port
sn - a speed negotiation xxx - Port number where event transpired. task related event occurred
2-19
Table 2-23
Speed Negotiation Command (cmd) Code
Abbreviation Description/Stage NC NF NM WS Negotiation Complete Stage Negotiate Follow Stage Negotiate Master Stage Wait for Signal Stage
Table 2-24 cmd WS NM NF
Argument #1 Keys and Definitions Output/Key 0x00 0x01 0x02 0x03 0x04 0xee 0xe0 0xc0 0xb0 0xbb 0x0f 0xff 0xd0 0xdd 0xd1 0x0b 0x12 0x14 0x15 0x1b 0x1e 0x1f 0x22 Definition Port is just enabled Speed negotiation kick started Port is disabled and hence speed negotiation disabled Fault in speed negotiation; maximum number of speed negotiation retries failed Speed negotiation results are inconsistent - software states do not match that of hardware Signal (light) received Signal (light) lost Light loss greater than a 40ms Laser failed reported from SFP No SFP detected Received synchronization loss Received synchronization gain Speed negotiation watch dog timer expired Negotiate follow state timed out Negotiation completed as identified by FC-FS Wait for signal - FC-FS state Wait for signal - FC-FS state8 Negotiate master - FC-FS state Negotiate master - FC-FS state Negotiate master - FC-FS state Negotiate follow - kick off negotiate follow -FC-FS state Negotiate follow - FC-FS state Negotiate follow - FC-FS state Negotiation complete to 1G Negotiation complete to 2G Comment Typically seen in WS stage except 0x02 which is seen in NC
NC
0x01 0x02
2-20
Table 2-25 Output/Key 0x1 - 0x4
Argument #2 Branch Tags (not complete) Definition WS, NC NM, NF Comment Timer related events to measure loss of light duration. argument #3 should be 0xcafe for these cases Current Tx speed = 1G (in some cases it is value 0 which has no meaning) Current Tx speed = 2G Code branches in state NM FC-FS Code branches in state NM FC-FS Code in state NF FC-FS NF NF Code branches in state NF FC-FS Code branches in state NF FC-FS
0x1 0xf1 - 0xf6 0xe1 - 0xe2 0xaf 0xd1 - 0xd2 0xc1 - 0xc3
NM, NF NM NM
Table 2-26 Output/Key 0xcafe 0x0 0x1
Argument #3 IUs Definition WS, NC, NM, OR NF NM, NF NM, NF Comment Indicated timer related events to measure loss of light duration Current Rx speed = 1G (in some cases it is value 0 which has no meaning) Current Rx speed = 2G
Note:
WS and NC states are logged irrespective of SPEED setdbg level; for all other commands set setdbg SPEED level >=5.
2-21
Example: Speed Negotiation 2Gbit/sec to a 1Gbit/sec switch

02:54:32.549 02:54:32.549 02:54:32.549 02:54:32.549 02:54:32.549 02:54:32.566 PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT PORT sn sn sn sn sn sn sn sn sn sn sn sn sn sn sn sn sn sn 14 14 14 14 14 14 14 WS WS WS WS NM NM NM 00,00000000,00000000 ee,00000000,00000000 f0,00000000,00000000 ff,00000000,00000000 14,00000001,00000001 f0,00000000,00000000 15,000000f5,00000000
// sync gained // change speed to rx = 2G, tx = 2G // lost sync

02:54:32.566 02:54:32.583 02:54:32.583 02:54:32.583 02:54:32.583 02:54:32.599 02:54:32.899 02:54:32.916 02:54:32.916 02:54:33.166 02:54:33.199 02:54:33.199
// state 21, branch f5

14 NM ff,00000000,00000000 14 NM 15,000000f2,00000000 14 NM 15,000000f6,00000000 14 NM 15,000000f5,00000001 14 NM f0,00000000,00000000 14 NM 1b,000000f4,00000000 14 NF 1f,000000e1,00000000 14 14 14 14 NF NC NC NC 1f,00000000,00000000 150000,00141007,001f0000 *2 ff,00000000,00000000 01,00000000,00000000
// negotiate follow stage, state 31, branch e1
// negotiate complete at 1G Example: Breakdown of Speed Negotiation Example

Date 04:53:10.105 04:53:10.118 04:53:10.377 Task SPEE SPEE SPEE Event sn sn sn Port 11 11 11 CMD WS WS NC Arguments 000000ee,00000000,00000000 00000001,00000000,00000000 00000002,00000000,00000001
2.5.1. I/O Control (ioctl)

An IOCTL event is an internal message that gives information about the port and what stage of bring-up or take down of the port(s). Table 2-27 Ioctl Code 0x00 0x01 0x02 0x04 0x20 0x30 0x31 0x32 0x33 0x34
2-22
IOCTL CTL Code Description / Interpretation Arg Enable chip level port interrupt Entry describes physical port Entry describe WWN Entry describes Al-PA bitmap Enable free buffer interrupt Get buffer and buffer port set available buffer interrupt Return buffer Get Fx port error status Get Fl port error status
Troubleshooting Using the Port Logs Table 2-27 Ioctl Code 0x35 0x36 0x37 0x38 0x39 0x3a 0x3b 0x3c 0x3d 0x3e 0x3f 0x40 0x41 0x42 0x43 0x44 0x45 0x46 0x50 0x51 0x52 0x53 0x54 0x55 0x56 0x57 0x58 0x59 0x5a 0x5b 0x5c 0x60 0x61 0x62 0x63 0x64 0x65 0x66
IOCTL CTL Code Description / Interpretation Arg Get physical state Set physical state Set FCTL_mode Get device information Get loop bmp Set E_Port flow control mode Get register map Return Tx buffer Filter processing stages Filter processing stage 2 Software frame filtering Remove all phantom nodes for port Add a phantom device (loop only) Translate phantom sid and did Create phantom node for remote did Get blm_my_alpa table from ASIC Get blm_plt_cam table from ASIC Get blm_plt_alpa table from ASIC Test phantom for (S_ID, D_ID) Add a phantom device (loop only) Remove a phantom device Get phantom AL_PA by address ID Get address ID by phantom AL_PA Looplet init (send LIPs) Looplet init sequence Arg: 1,0 Loop port (or looplet) bypass Looplet init AL_PA bitmaps. Bitmap, IU pointer Looplet Unicast Routes Set up port for loop diag mode Loop port bypass the ALPD Loop port enable the ALPD Write/read 64-bytes to/from the RAM buffer get cmem status Check if FL_Port a loopback sla Set buffer line value and offset. 1,1 Disable FC-AL transmit front-end Enable FC-AL transmit front-end Set FL_Port to be cable loopback. Interpretation Arg: Port#, 0
2-23
Troubleshooting Using the Port Logs Table 2-27 Ioctl Code 0x67 0x70 0x71 0x72 0x73 0x80 0x81 0x82 0x83 0x84 0x85 0x86 0x87 0x88 0x8e 0x8f 0x90 0x91 0x92 0x93 0x94 0x95 0x96 0x97 0x99 0x9a 0xa0 0xa1 0xa2 0xa3 0xa4 0xa5 0xa6 IOCTL CTL Code Description / Interpretation Arg Clear Diag mode flag FLA Loop INITializing FLA Loop Port Control FLA Loop Status LPORT ALPA bitmap Port administration stuff. The ports being set up while the switch is booting up a,0 Get common hardware statistics Get loop hardware statistics Get hardware frame statistics Get hardware error statistics Get interrupt statistics Get available BB_Credit Get bb credit for the Fx_PORT Get public/private/phantom counts Get GBIC module type Port performance calculation Get credits for all E_Port VCs. Credit values, 0 (0 = done) Set credits for all E_Port VCs. Credit values, 0 (0 =done) Get BB-Credit for the Fx_Port. IU pointer, 0 (0 = done) Set up port for loop diag mode Loop port bypass the ALPD Loop port enable the ALPD Get port topology Set port topology LIP the loop, TX_UNAVAIL on/off Send MRK primitive signal LED control Port is an E_Port. Interpretation Arg: 0,0 Port is an F_Port. Native address, value Port is segmented Interpretation Arg: 0,0 (done) Domain name is known Domain#, 0 (Note - 0 means done) Bring port online Take port offline
2-24
Troubleshooting Using the Port Logs Table 2-27 Ioctl Code 0xa7 0xa8 IOCTL CTL Code Description / Interpretation Arg Take port into Link Reset Add unicast route. VxWorks: Arg = Port#, cmd (cmd 1 = building; 0 = done) Linux: Arg = to domain, output port Example: 03:08:50.658 PORT ioctl 1 a8 3,8 means a unicast route has been added for port 1 to reach domain 3 using output port 8. 0xa9 Delete unicast route VxWorks: Arg = Port#, port# Linux: Arg = domain, output port 0xaa 0xab 0xac 0xad 0xae 0xaf 0xb0 0xb1 0xb2 0xb3 0xb4 0xb5 0xb6 0xb7 0xb8 0xb9 0xba 0xbb 0xbc 0xbd 0xbe 0xbf 0xc0 0xc1 0xc2
Add multicast route Arg = Well-Known Address, port# Delete multicast route Arg = Well-Known Address, port# Unicast routing table done Arg = 0,0 (0,0 = done) Multicast routing table done Arg: 0,0 (0,0 = done) Undo a previous F_Port ioctl Take a port down then up Arg = 0,0 (0,0 = done) Enable hardware zoning Arg = 0,0 (0,0 = done) Disable hardware zoning Arg = 0,0 (0,0 = done) Add members to zone Delete member from zone Add a zone type Add zone group Enable all port zoning Reset all port zoning Disable all port zoning Free zoning token Setup FLOGI command tgrap Setup report lun cmd trap Get World-Wide Name and IDs Get receiver/originator ID Add LUN information Exclude port from zoning Get port interrupt bit map Enable port interrupt Disable port interrupt
2-25
Troubleshooting Using the Port Logs Table 2-27 Ioctl Code 0xc3 0xc4 0xd0 0xd1 0xd2 0xd3 0xd4 0xd5 0xd6 0xd7 0xd8 0xd9 0xdc 0xdd 0xde 0xdf 0x13d 0x13e 0xe0 0xe1 0xe2 0xe3 0xe4 0xe5 0xe6 0xe7 0xe8 0xf0 0xf1 0xf2 0xf3 IOCTL CTL Code Description / Interpretation Arg Check if port intr pending Enable chip interrupt, SW12K Add a SID_DID pair Delete a SID_DID pair Get the list of EE keys Get the current EE mask Set the SID-ID pair Clear the CRC counter for AL_PA Get the CRC counter for AL_PA Send word count for SID_DID pair RCV word count for SID_DID pair CRC err count for SID_DID pair Auto speed negative mode for arg1 value Get port speed ala admin.h defines Arg: value, 0 Port speed capability ala admin.h Arg: Port speed value, 0 Get the ports long distance level Arg: Value, 0 Arg: IU address pointer Arg: IU address pointer, 0 Send MARK primitive onto wire Arg: 0,0 Get the MARK timestamps Arg: 0,0 Add the port to the trunk Arg: 0,0 Get all trunk masters on the quad Arg: IU address pointer, IU address pointer Update MARK timestamp with RMT Check whether port is trunkable Arg = Port #, IU address pointer Enable trunking if possible Arg = IU address pointer, IU address pointer Get trunking group information Get ISL band width Arg = IU address pointer, 0 Add a filter counter Delete a filter counter Number of filter hit count Add get perf filter references
2-26
Troubleshooting Using the Port Logs Table 2-27 Ioctl Code 0xf4 0xf5 0x100 0x101 0x102 0x103 0x104 0x105 0x106 0x107 0x108 0x120 0x121 0x122 0x123 0x124 0x125 0x126 0x127 0x128 0x129 0x12a 0x12b 0x12c 0x130 0x131 0x132 0x133 0x134 0x135 0x136 IOCTL CTL Code Description / Interpretation Arg Clear filter hit count Clear all filter counts for port Get fail detection logic statuses Arg = IU address pointer, 0 Set fail detection control bit Clear fail detection control bit Set Rx-to-Tx parity control Get Rx-to-Tx parity error status Get Rx-to-Tx parity error status Enable fail detection interrupt Disable fail detection interrupt Check for fail detection interrupt Enable IPO zoning Disable IPO zoning Fabric lookup report after enable Name server list of PIDs for IPO Query if node is IPO target/host Ask for list of nodes to zone check List of IPO hosts zoned to target RSCN received List of IPO targets zoned to host Arg = IU address pointer, 0 Check for existence of IPO hosts Fabric merge report after reconfigure Switch online SCN received add unicast single area route Arg = 0,0 Add a zone type (new) Arg = IU address pointer, IU address pointer Add zone group (new) Arg = IU address pointer, IU address pointer Enable all port zoning (new) Arg = 0,0 Reset all port zoning (new) Arg = 0,0 Disable all port zoning (new) Arg = 0,0 Free zoning token (new) Arg = IU address pointer, 1 Setup PLOGI command trap (new) Arg = 0,0
2-27
Troubleshooting Using the Port Logs Table 2-27 Ioctl Code 0x137 0x138 0x139 0x13a 0x13b 0x13c 0x13d 0x13e 0x13f 0x140 0x141 0x142 0x143 0x144 0x145 0x146 0x147 0x148 0x149 0x14a 0x14b 0x150 0x151 0x160 0x161 0x170 0x180 0x181 0x182 0x183 0x184 0x185 0x186 0x187 0x188 0x189 0x190 IOCTL CTL Code Description / Interpretation Arg Setup report lun cmd trap (new) Get World-Wide Name and IDs (new) Arg = IU address pointer, IU address pointer Get receiver/originator ID (new) Apply LUN information (new) Exclude port from zoning (new) Soft zoning port (new) Get frame filtering features (new) Set frame filtering features (new) Clear port zoning except dyn flt Load sidcam (diagnostic) Load didcam (diagnostic) Load LUN offset registers (diagnostic) Load zone group RAM (diagnostic) Load zone horizontally (diagnostic) Load filter selection (diagnostic) Load field definition (diagnostic) Load action registers (diagnostic) Get filter statistics (diagnostic) Clear all filtering hardware (diagnostic) enable frame filtering (diagnostic) Disable frame filtering (diagnostic) zone rscn handling Arg: IU address pointer, 0 Remove related CAM entries on all ports Set alpa in blm_alpa_avail[ ] reg Clear alpa in blm_alpa_avail[ ] reg Freeze RT used by diags: EMC ESSLB Get chip Time of Day Get chip Time of Day Prescaler Set chip Time of Day Prescaler Get RX TOD Pre-Confirmed Set RX TOD Pre-Confirmed Get RX TOD Active Set RX TOD Active Set RX TOD Prescaler Set Rx TOC mS to TOD click conversion TOD click to mS conversion
2-28
Troubleshooting Using the Port Logs Table 2-27 Ioctl Code 0x191 0x192 0x193 0x194 0x195 0x196 0x197 0x198 0x199 0x310 0x311 0x312 0x313 IOCTL CTL Code Description / Interpretation Arg Get VC translation link init Send MARK primitive with LRTT (link round trip timer) enabled Enable MARK retransmission Disable MARK retransmission Save link round trip timer from ASIC to BLOOM driver structure Set link round trip delay in ASIC driver structure Called from Panic to disable all ports' RX Get vcc credit of online E_port Bloom config - No bus = 0 Replace all SID-DID pairs Clear CRC counters for multiple AL_PAs Get CRC counters for multiple AL_PAs Clear the Tx and/or Rx word count
2.5.2. Reading a Routing Event

The following example shows output from Fabric OS 4.2. Example: Fabric OS v4.2.0
time task event port cmd args -------------------------------------------------------------------03:08:50.658 PORT routing 0 add00001,00010008,c6c5f3c0,c4a22bc0
The port column 0 implies switch information. The cmd column is blank. Read the args columns as follows: - Arg 1 - first nibble: first 3 characters (12-bits) of first nibble is a command (add or del) the last character is of the first nibble is the internal ID # of the log statement. There are two possible values for this first nibble of arg 1: add[0-9] or del[0-9]. This example shows an add0 which means a route of internal ID # 0 is being added. - second nibble: is the ingress or in port of the route. This example shows ingress port 1. - Arg 2 - first nibble is the domain of the route command. This example shows Domain 1. - second nibble is the egress or output port of the route command. This example shows egress port 8. - Arg 3 could be one of the following: - ingress port handle value (the ingress port value from the perspective of the blade module). Internal use only. - eeeeeeee indicating that the word is invalid and to be ignored. - ffffffff indicating that the current operation failed in the switch/blade drivers and needs special attention. This output thus reads that ingress port 1 is having routing added to Domain 1 using egress port 8 or going out port 8.
2-29
2.6. Extended Link Service (ELS)

Extended Link Services (ELS) are sent to the destination N_port to perform the requested function or service.
The R_CTL field of an Extended Link Service request is always set to 0x22. The R_CTL field of the Extended Link Service reply is set to 0x23. The Type filed 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, the portlogdump 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, word6. 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. See section 2.6.3. ELS Examples on page 2-35.
2.6.1. ELS Command Code

Table 2-28 ELS Command 01000000 02000000 03000000 04000000 05000000 06000000 07000000 08000000 09000000 0A000000 0B000000 0C000000 0D000000 0E000000 0F000000 10000000 11000000 12000000 20100000 21100000 22000000 23000000 24000000 25000000 2F000000 30000000
2-30
ELS Command Code Abbreviation RJT ACC PLOGI FLOGI LOGO ABTX RCS RES RSS RSI ESTS ESTC ADVC RTV RLS ECHO TEST RRQ PRLI PRLO SCN TPLS TPRLO Unused GAID Get Alias ID
Description Reject Accept N_Port Login F_Port Login Logout Abort Exchange Read Connection Status Read Exchange Status Block Read Sequence Status Block Request Sequence Initiative Establish Streaming Estimate Credit Advise Credit Read Timeout Value Read Link Status ECHO Test Reinstate Recovery Qualifier Process Login Process Logout State Change Notification Test Process Login State Third Party Process Logout
Troubleshooting Using the Port Logs Table 2-28 ELS Command 31000000 32000000 33000000 34000000 35000000 3F000000 40000000 41000000 42000000 4F000000 50000000 51000000 52000000 53000000 54000000 55000000 5F000000 60000000 61xxxxxx 62000000 63000000 6F000000 70000000 71000000 72000000 73000000 77000000 78000000 79000000 7A000000 7B000000 FF000000 11010000 11020000 11030000 11040000 11050000 11050100 11060000 11070000 ELS Command Code Abbreviation FACT FDACT NACT NDACT Unused QoSR RVCS Unused PDISC FDISC ADISC RNC FARP Unused FAN RSCN SCR Unused LINIT LPC LSTS Unused RNID RLIR LIRR Unused LISM LIFA LIPA LIHA LISA0 LISA1 LIRP LILP Select Master Fabric Assigned Previously Acquired Hard Assigned Soft Assigned (old) Soft Assigned (new) Report Position Loop Position Request Node Identification Data Registered Link Incident Record Link Incident Record Registration Loop Initialize Loop Port Control Loop Status Fabric Address Notification Registered State Change Notification State Change Registration Discover N_Port Service Parameters Discover F_Port Service Parameters Discover Address Report Node Capability FC Address Resolution Protocol Quality of Service Request Read Virtual Circuit Status Description Fabric Activate Alias ID Fabric Deactivate Alias ID N_Port Activate Alias ID N_Port Deactivate Alias ID
2-31
2.6.2. FC-PH - Reject Reason Codes and Explanations

Refer to Switch Fabric Internal Link Services (SW_ILS) Reject Frame Reason and Explanation Codes for a complete list.
2.6.2.1. FC-PH Reject Reason Code

Table 2-29 Reason Code 01 02 03 04 05 FC-PH Reject Reason Code Description Invalid ELS Command Code the command code is not recognized by the recipient. Invalid revision level. The recipient does not support the specified revision level. Logical Error The request identified by the command code and the payload content is invalid or logically inconsistent for the conditions present. Invalid payload size The size of the payload is inconsistent with the command code and/or any length fields in the payload. 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 07 09 0B Others FF Protocol Error an error has been detected that violates FC-2 protocols and is not covered by another reason code. Unable to perform command request the recipient is unable to perform the request at this time. Command not supported the recipient does not support the ELS command. Reserved Vendor-unique field indicating an error condition.
2-32
2.6.2.2. FC-PH Reject Explanation

F_JRT information relates to the F_Port P_RJT information relates to the N_Port FC-PH Reject Reason Explanation Codes Description Explanation
Table 2-30 Code 0x00 0x01
NO_ADDITIONAL_EXPLANATION N/A INVALID_D_ID F_RJT - the Fabric is unable to locate the destination N_Port address. P_RJT - the N_Port which received this frame does not recognize the D_ID as its own Identifier.
0x02
INVALID_S_ID
F_RJT - the S_ID does not match the N_Port Identifier assigned by the Fabric. P_RJT - the destination N_Port does not recognize the S_ID as valid.
0x03
NOT_AVAIL_TEMP
F_RJT - The N_Port specified by the D_DID is a valid destination address, but the N_Port is not functionally available. For example, the N_Port is online and may be performing a Link Recovery Protocol. F_RJT - The N_Port specified by the D_ID is a valid destination address, but the N_Port is not functionally available. The N_Port is offline, or powered down. F_RJT or P_RJT - The Class of Service (COS) specified by the Start of Frame (SOF) delimiter of the frame being rejected is not supported. Deliminator usage error. F_RJT or P_RJT - The Start of Frame (SOF) or End of Frame (EOF) is not appropriate for the current conditions. For example, a frame started by SOFc1 is received while a Class 1 Dedicated Connection already exists with the same N_Port.
0x04
NOT_AVAIL_PERM
0x05 0x06
CLASS_NOT_SUPPORTED DELIMITER_ERROR
0x07 0x08
TYPE_NOT_SUPPORTED INVALID_LINK_CONTROL
F_RJT or P_RJT - The TYPE field of the frame being rejected is not supported by the Port replying with the Reject frame. P_RJT - The command specified in the Information Category bits within R_CTL field in the frame being rejected is invalid or not supported as a Link_Control frame. P_RJT - The R_CTL field is invalid or inconsistent with the other Frame Header fields or conditions present. P_RJT - The F_CTL field is invalid or inconsistent with the other Frame_Header field or conditions present. P_RJT - The OX_ID specified is invalid, or inconsistent with the other Frame_Header field or conditions present. P_RJT - The RX_ID specified is invalid, or inconsistent with the other Frame_Header field or conditions present. P_RJT - The SEQ_ID specified is invalid, or inconsistent with the other Frame_Header field or conditions present. P_RJT - The DF_CTL field is invalid.
0x09 0x0a 0x0b 0x0c 0x0d 0x0e
INVALID_R_CTL INVALID_F_CTL INVALID_OX_ID INVALID_RX_ID INVALID_SEQ_ID INVALID_DF_CTL
2-33
2
Code 0x0f
Troubleshooting Using the Port Logs FC-PH Reject Reason Explanation Codes Description INVALID_SEQ_CNT Explanation P_RJT - The SEQ_CNT specified is invalid, or inconsistent with the other Frame_Header field or conditions present. A SEQ_CNT reject is not used to indicate out of order or missing data frames. P_RJT - The Parameter field is incorrectly specified, or invalid. P_RJT - An error has been detected in the Identified Exchange (OX_ID). This could indicate Data frame transmission without Sequence Initiative or other logical errors in handling an Exchange. P_RJT - This reject code indicates that an error has been detected that violates the rules of FC-2 signaling protocol, which are not specified by other error codes. F_RJT or P_RJT - The frame being rejected is an incorrect length for the conditions present. P_RJT - An ACK was received from an unexpected S_ID. The ACK received was not for an Open Sequence or Exchange, but was received from a Logged-in N_Port.
Table 2-30
0x10 0x11
INVALID_PARAMETER EXCHANGE_ERROR
0x12
PROTOCOL_ERROR
0x13 0x14
INCORRECT_LENGTH Unexpected_ACK
0x15 0x16
Reserved Login_Required F_RJT or P_RJT - An exchange is being initiated before the interchange of Service Parameters (i.e. Login) has been performed. F_RJT may be issued by the Fabric in order to notify an N_Port that a Login is required due to changes within the Fabric. F_RJT shall not be issued by the Fabric in order to convey Login status of a destination N_Port. P_RJT - A new Sequence was initiated by an N_Port which exceeded the capability of the Sequence Recipient as specified in the Service Parameters during Login. P_RJT - A new Exchange was initiated by an N_Port, which exceeded the capability of the Responder facilities. P_RJT - The N_Port does not support the optional Expiration_Security_Header. F_RJT - The speed of the source and destination N_Ports does not match. Other fabric characteristics related to multiple fabric domains may also use this reason code. F_RJT or P_RJT - The Vendor Unique Reject bits (bits 7 - 0) are used by specific vendors to specify additional reason codes. N/A
0x17
Excessive_Sequences_Attempted
0x18 0x19 0x1a
Unable_to Establish_Exchange Expiration_Security_Header not supported. Fabric_Path_Not_Avail
0x1b 0x1c
Vendor Unique Error Reserved
2-34
2.6.3. ELS Examples

2.6.3.1. ELS Example 1
Fabric OS v3.x Output
time task event port cmd args ------------------------------------------------1. 22:55:51.199 tFcp Tx3 12 16 220a1cef,00fffc0a,013effff,05000000,10d0d930 2. 22:55:51.199 tReceive Rx3 12 4 23fffc0a,000a1cef,013effff,02000000,10ca5ae0
Example: Line 1.
22:55:51.199 tFcp Tx3 12 16 220a1cef,00fffc0a,013effff,05000000,10d0d930
Table 2-31 Argument 1 22
ELS Arg Explanation (Line 1) Argument 2 00 = Identifier Argument 3 013e section 2.2.1.7. Originator_ID (OX_ID) on page 2-10 ffff section 2.2.1.8. Responder_ID (RX_ID) on page 2-10 Argument 4 05000000 (log out) section 2.6.1. ELS Command Code on page 2-30 IU address pointer (not available in Fabric OS v4.x). Argument 5 10d0d930
section Table 2-7 Routing Control Bits - R_CTL Diagram on page 2-8 0a1cef section 2.2.1.2. Destination_ID (D_ID) on page 2-9 Example: Line 2
fffc0a section 2.2.1.3. Source_ID (S_ID) on page 2-9
In the following example, the embedded port ffffc0a does an Extended Link Service (ELS) request logout from device 0a1cef. Device 0a1cef accepts the request.
22:55:51.199 tReceive Rx3 12 4 23fffc0a,000a1cef,013effff,02000000,10ca5ae0
Table 2-32 Argument 1
ELS Arg Explanation (Line 2) Argument 2 00 = Identifier Argument 3 013e Argument 4 05000000 Argument 5 10d0d930 IU address pointer (not available in Fabric OS v4.x).
23 (response) section Table 2-7 Routing Control Bits R_CTL Diagram on page 2-8
fffc0a
(log out) section 2.2.1.7. Originator_ID section 2.6.1. ELS (OX_ID) on page 2-10 Command Code on page 2-30 ffff section 2.2.1.8. Responder_ID (RX_ID) on page 2-10
a1cef
section 2.2.1.2. Destination_ID (D_ID) on page 2-9
section 2.2.1.3. Source_ID (S_ID) on page 2-9
2-35

Example 2 is an FLOGI frame to the F_port (R_CTL=0x22, Extended Link Services Request; D_ID=0xfffffe, F_port; S_ID=0x000000). The S_ID = 0 indicates that the attaching device does not yet have a Fabric address.
12:32:53.583 tReceive Rx3 1 116 22fffffe,00000000,0222ffff,04000000
R_CTL - Extended Link Services Request = Fabric F_port 0x000000 = S_ID (attaching device does not yet have a fabric address.
0x22 = 0xfffffe

Example 3 is the accept of FLOGI from the switch to the device (R_CTL=0x23, Extended Link Services Reply; D_ID=0xd31100, fabric F_port; S_ID=0xfffffe). The D_ID=0xd31100 is the assignment of the Fabric address.
12:23:12.049 12:23:12.049 12:23:12.049 12:23:12.049 12:23:12.049 12:23:12.049 12:23:12.049 12:23:12.049 0x23 tReceive tFspf tFspf tFspf tFspf tFspf tFspf tFspf scn ioctl ioctl ioctl ioctl ioctl ioctl Tx3 1 1 1 1 16 1 1 1 6 dd ac aa aa ad 92 116 10129da0,0* 2 0,0 ffffff,10 ffffff,1 0,0 101f466c,0 23d31100,00fffffe,02220185,02000000
= Extended Link Services Reply (R_CTL) = D_ID fabric F_port 00fffffe = the S_ID 0xd31100 = D_ID is the assignment of the Fabric address
0xd31100
2-36
2.7. Switch Fabric Internal Link Services (SW_ILS)

Internal Link Services is the service which allows a switch to communicate with the fabric. A Domain Controller (or embedded port) communicates to receive updated information. There are three primary types of communication that occur between switches: 1. R_CTL is 02, 03 or c0 (ack) and S_ID and D_ID are both FFFFFD refer to ILS Command Codes section Table 2-33 Switch Fabric Internal Link Services Command Codes on page 2-38.
Example: Fabric controllers exchanging and acknowledging ILS command code hello:
17:34:10.820 17:34:10.821 PORT PORT Rx Tx 4 4 40 0 02fffffd,00fffffd,02bdffff,14000000 c0fffffd,00fffffd,02bd0112
2.
R_CTL is 02 or 03 and S_ID and D_ID are both FFFCxx (xx representing 2 different domains in hex) refer to ILS Command Codes section Table 2-33 Switch Fabric Internal Link Services Command Codes on page 2-38 for information about that communication and see section 2.7.3. SW_ILS Examples on page 2-41. R_CTL is 02 or 03 and S_ID and D_ID are both FFFCxx (xx representing 2 different domains in hex) immediately followed by a ctin refer to section 2.10.4. ctin and ctout Event Examples on page 2-68 which will refer you to ELS Command Codes section Table 2-72 Name Server Command Codes on page 2-59 or Name Server Command Codes Fabric Internal FC_CT Commands on page 63 because the last byte of Well-Known address FFFFFC (Name Server) is being used for ctin and ctout cmd column.
01:42:55.350 01:42:55.350 01:42:55.351 01:42:55.353 01:42:55.353 01:42:55.355 PORT PORT nsd nsd PORT PORT Rx Tx ctin ctout Tx Rx 15 15 15 15 15 15 20 0 fc fc 644 0 02fffc01,00fffc02,019cffff,01000000 c0fffc02,00fffc01,019c0322 00010410,000104d1 00038002,00000001,00fffc01 03fffc02,00fffc01,019c0322,01000000 c0fffc01,00fffc02,019c0322
3.
You could also see management server exchanges using the Common Transport protocol see section 2.10.4. ctin and ctout Event Examples on page 2-68 to interpret output:
17:31:48.934 17:31:48.934 msd msd ctin ctout 0 0 fa fa 00010624,10000005 00038002,10000005,1e340112
The SW_ILS section includes the following areas:
SW_ILS Command Codes Zoning Codes (NZ) FSS Messages
2-37
2.7.1. SW_ILS Command Codes

Table 2-33 Code 0x01000000 0x 02000000 0x 03000000 0x 04000000 0x 05000000 0x 06000000 0x 07000000 0x 08000000 0x 10000000 0x 11000000 0x 12000000 0x 13000000 0x 14000000 0x 15000000 0x 16000000 0x 17000000 0x 18000000 0x 19000000 0x 1a000000 0x 1b000000 0x 1c000000 0x 1d000000 0x 1E000000 0x 1F000000 0x 20000000 0x 21000000 0x 22000000 0x 23000000 0x 24000000 0x 25000000 0x 26000000 0x 3000xxxx 0x 31000000 Switch Fabric Internal Link Services Command Codes Abbreviation IE_RJT IE_ACC IE_ELOGI IE_LOGI IE_ELOGO IE_LOGO IE_DSP IE_VN IE_ELP IE_EFP IE_DIA IE_RDI IE_HLO IE_LSU IE_LSA IE_BF IE_RCF IE_GAID IE_RAID IE_RSCN IE_INQ IE_RTE DRLIR CSWR DSCN LOOPD MR ACA RCA SFC UFC ESC ESS Description Reject Inter Exchange Accept Inter Exchange Element Login Inter Exchange Inter-Element Login Inter Exchange Element Logout Inter Exchange Inter-Element Logout Inter Exchange Distribute Service Parameters Inter Exchange Validate Name Inter Exchange Link Parameters Inter Exchange Fabric Parameters Inter Exchange Domain Identifier Assigned Inter Exchange Request Domain ID Routing: Hello Routing: Link State Update Routing: Link State Ack Build Fabric Inter Exchange Reconfigure Fabric Get Alias ID Return Alias ID Inter-switch RSCN Inquiry Interswitch Routing information Disconnect Class 1 Connection Coalesce SW_RSCNs Disconnect Class 1 Connection Detect Queued Class 1 Connection Request Deadlock Merge Request Acquire Change Authorization Release Change Authorization Stage Fabric Configuration Update Fabric Configuration Exchange Switch Capabilities Exchange Switch Support
2-38
Troubleshooting Using the Port Logs Table 2-33 Code 0x 32000000 Switch Fabric Internal Link Services Command Codes Abbreviation MRRA Description Merge Request Resource Allocation
Brocade-Specific Command Codes 0x70000000 0x71000000 0x72000000 0x73000000 0x74000000 0x75000000 0x76000000 0x77000000 0x78000000 0x79000000 0x7a000000 0x7b000000 0x7c000000 0x7d000000 0x7e000000 0x7f00000 IE_ZONE IE_SGROUP IE_SEC IE_SLAPRequest IE_SLAPAcknowledge IE_SLAPConfirm IE_SLAPDone IE_SLAPReject IE_RCS_INFO IE_RCS_ACA IE_RCS_SFC IE_RCS_UFC IE_RCS_RCA IE_RCS_TCO IE_RDTS IE_ECP Inter Exchange Zone Update (Vendor Unique) Inter Exchange Group wise commands Inter Exchange Security entry Inter Exchange SLAP Request Inter Exchange SLAP Acknowledge Inter Exchange SLAP Confirm Inter Exchange SLAP Done Inter Exchange SLAP Reject Inter Exchange Reliable commit service info Inter Exchange RCS Acquire Change Authorization Inter Exchange RCS Stage Fabric Config Inter Exchange RCS Update Fabric Config Inter Exchange RCS Release Change Authorization Inter Exchange RCS Transfer Commit Ownership Inter Exchange RDTS Request Inter Exchange credit parameters request
Trunking Support Code 0x90000000 0x91000000 IE_EMT IE_ETP Inter Exchange Read MARK timestamp(VU) Inter Exchange trunking parameter
External Link Services 0x81000000 0x82000000 0x83000000 0x84000000 0x850000 SW_RJT SW_ACC SW_CFN SW_WTV SW_ON Reject Accept Change Fabric Name Write Timeout Value Offline Notification
2-39
2.7.2. SW_ILS Reject Reason Codes (SW_RJT)

To view a reject frame, refer to section 2.13.2.2. SW_ILS Reject Frame on page 2-90. To view a reject example, refer to section 2.7.3.4. SW_ILS Reject Example on page 2-44. Table 2-34 Code 0x01 0x02 0x03 FC_SW: Reject Reason Codes (SW_RJT) Abbreviation SW_INVALID_COMMAND SW_INVALID_VERSION SW_LOGICAL_ERROR Description Invalid ELS Command Code the command code is not recognized by the recipient. Invalid revision level. The recipient does not support the specified revision level. Logical Error The request identified by the command code and the payload content is invalid or logically inconsistent for the conditions present. Invalid payload size The size of the payload is inconsistent with the command code and/or any length fields in the payload. 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 0x09 0x0b Other value 0xff SW_VENDOR_UNIQUE SW_PROTOCOL_ERROR SW_CANT_PERFORM_REQ SW_NOT_SUPPORTED Protocol Error an error has been detected that violates FC-2 protocols and is not covered by another reason code. Unable to perform command request the recipient is unable to perform the request at this time. Command not supported the recipient does not support the ELS command. Reserved Vendor-unique field indicates an error condition.
0x04 0x05
SW_INVALID_IU_SIZE SW_LOGICAL_BUSY
Table 2-35 Code 0x00 0x01 0x03 0x04 0x05 0x0d 0x0e 0x0f 0x10
2-40
FC-SW (SW-RJT): Reject Reason Explanation Codes Abbreviation SW_NO_EXPLANATION SW_CLASS_F_ERROR SW_CLASS_N_ERROR SW_UNKNOWN_CTL_MODE SW_UNKNOWN_CTL_PARAMS SW_INVALID_PORT_NAME SW_INVALID_SWITCH_NAME SW_TOV_MISMATCH SW_INVALID_DLIST Explanation No additional explanation Class F Service Parameter error Class N Service Parameter error Unknown Flow Control code Invalid Flow Control Parameters Invalid port name Invalid switch name R_A_TOV or E_D_TOV mismatch Invalid Domain_ID_List
Troubleshooting Using the Port Logs Table 2-35 Code 0x19 0x29 0x2a 0x2b 0x2c 0x2d 0x2e 0x2f 0x30 0x3a 0x3b 0x3c 0x3d FC-SW (SW-RJT): Reject Reason Explanation Codes Abbreviation SW_COMMAND_IN_PROGRESS SW_NO_MORE_RESOURCES SW_NO_DOMAIN_ID SW_INVALID_DOMAIN_ID SW_NON_SUPPORTED_REQ SW_NO_LINK_PARAMETERS SW_NO_CONT_DOMAIN_IDS SW_EPORT_ISOLATED SW_CANT_TRUNK SW_EPORT_DISABLED SW_SLAP_NOTDONE SW_RDTS_NOTDONE SW_RDTS_NOTDONE Explanation Command already in progress Insufficient resources available Domain_ID not available Invalid Domain ID Request not supported Link Parameters not yet established Requested Domain_IDs not available E_Port is Isolated Cannot trunk E port disabled Slap not done Zoning is not done RDTS not done
2.7.3. SW_ILS Examples

2.7.3.1. Routing Frame Example
Example: The Fabric Controller from one switch sends a handshake hello to the other Fabric Controller. The handshake is acknowledged.
time task event port cmd args ------------------------------------------------1. 00:44:26.599 tFspf Tx 8 40 02fffffd,00fffffd,0284ffff,14000000,10cac760 2. 00:44:26.599 tReceive Rx 8 0 c0fffffd,00fffffd,028400fb, ,10cab4d0
Output Line 1: Request - Routing hello

Table 2-36
Arg 1 02fffffd
Argument Break Down for Example (Line 1)

Arg 2 00fffffd Arg 3 0284ffff Arg 4 14000000 Arg 5 10cac760
02 = RC_CTL (request) fffffd = D_ID (Fabric controller)
00 = Identifier ffffd = S_ID (Fabric controller)
10cac760 = IU address 14000000 = SW_ILS command code (routing Hello). pointer section 2.7.1. SW_ILS ffff = RX_ID Command Codes on page 2-38 0284 = OX_ID
2-41
Output Line 2: Acknowledgement

00:44:26.599 tReceive Rx 8 0 c0fffffd,00fffffd,028400fb, ,10cab4d0
Table 2-37
Arg 1 c0fffffd
Argument Breakdown for Example (Line 2)

Arg 2 00fffffd Arg 3 028400fb Arg 4 Null Arg 5 10cab4d0
CO = RC_CTL (Link control acknowledged) fffffd = D_ID (Fabric controller)
00 = Identifier
0284 =OX_ID null = SW_ILS command code 00fb = RX_ID
10cab4d0 = IU address pointer (not available in Fabric OS v4.x).
ffffd = S_ID (Fabric controller)
2.7.3.2. Trunking Frame Example

Example: The Fabric Controller on one switch sends a trunking stamp to the Fabric Controller on the other switch. The Request is acknowledged and accepted.
22:33:38.283 22:33:38.283 22:33:38.283 22:33:38.283 tFabric tReceive tReceive tTransmit Tx Rx Rx Tx 3 3 3 3 84 0 84 0 02fffffd,00fffffd,02ceffff,9000005 c0fffffd,00fffffd,02ce0089, ,10cb1c40 03fffffd,00fffffd,02ce0089,02000050,10cb2510 c0fffffd,00fffffd,02ce0089, ,10cb2510
Output Line 1
22:33:38.283 tFabric Tx 3 84 02fffffd,00fffffd,02ceffff,9000005
Table 2-38
Arg 1 02fffffd

Arg 2 00fffffd Arg 3 02ceffff Arg 4 9000005
02 = RC_CTL (request) fffffd = D_ID
00 = Identifier fffffd = S_ID
02ce = OX_ID ffff = RX_ID
9000005 = Trunking IU Preamble
Output Line 2
22:33:38.283 tReceive Rx 3 0 c0fffffd,00fffffd,02ce0089, ,10cb1c40
Table 2-39
Arg 1 c0fffffd

Arg 2 00fffffd Arg 3 02ce0089 Arg 4 Arg 5 10cb1c40
CO = RC_CTL (Link control acknowledged) fffffd = D_ID
00 = Identifier
02ce =OX_ID
null
10cb1c40 = IU address pointer
fffffd = S_ID
ffff = RX_ID
2-42
Troubleshooting Using the Port Logs Output Line 3

22:33:38.283 tReceive Rx 3 84 03fffffd,00fffffd,02ce0089,02000050,10cb2510510
Table 2-40

Arg 2 00fffffd Arg 3 02ce0089 Arg 4 02000050 Arg 5 10cb2510510
Arg 103fffffd
03 = RC_CTL (reply) fffffd = D_ID (Fabric controller)
00 = Identifier fffffd = S_ID (Fabric controller)
02ce = OX_ID 0089 = RX_ID
02 = (Accept) 000050 =
10cb2510 = IU address pointer
Output Line 4
22:33:38.283 tTransmit Tx 3 0 c0fffffd,00fffffd,02ce0089, ,10cb2510
Table 2-41
Arg 1 c0fffffd

Arg 2 00fffffd Arg 3 02ce0089 Arg 4 Arg 5 10cb2510
0c = RC_CTL (link 00 = control acknowledge) Identifier fffffd = D_ID (Fabric fffffd = S_ID controller) (Fabric controller)
02ce = OX_ID
null
10cb2510 = IU address pointer
0089 = RX_ID
2.7.3.3. NSD Example

Example: The example shows S_ID Domain controller (fffc0a) talking to D_ID Domain controller (fffc09); they are communicating Interswitch RSCN code. The first line of an RSCN is logged from the name server, a second entry is logged from the port side and uses a regular ELS frame format.
16:09:052.553 nsd rscn 0fffc09 00fffc0a, 1b000000, 500a1f00,000000001
General Information: cmd field: A 0 followed by the last 3 bytes of FC word 0 which represent the D_ID. arg 1 is FC word 1: CS_CTL = 00 Otherwise see IU_Status codes followed by 24-bit address of the S_ID arg 2 is dependant on the S_ID and D_ID fields: If D_ID and S_ID are both ffcxx embedded port addresses use SW_ILS Command Code:section Table 2-33 Switch Fabric Internal Link Services Command Codes on page 2-38 If D_ID is a 24-bit address of an end device that did an SCR and S_ID is fffffd use ELS Command Code:section Table 2-28 ELS Command Code on page 2-30 arg 3 represents affected N_Port information First nibble in high order byte shall be: hexXx = no additional info hex1x = port is online hex2x= port is offline
Brocade Portlogdump Reference Guide 2-43
Second mibble in high order byte shall be: hexx0 = port address format hexx1 = area address format hexx2 = domain address format hexx3 = Fabric address format The remaining three bytes contain the 24-bit address of the affected device arg 4 represents the detection function: hex00000001 = Fabric detected hex00000002= N_Port detected The example above is interpreted as a Fabric detected RSCN from fffc0a to fffc09 about device 0a1f00 using port address format.
2.7.3.4. SW_ILS Reject Example

Example: The example focuses mainly on reading the areas that affect the reject response.
11:01:10.716 11:01:10.949 11:01:11.916 11:01:12.499 11:01:12.499 tFspf tShell tShell tReceive tReceive Tx ioctl ioctl Rx3 reject 2 2 3 2 2 40 02fffffd,00fffffd,01abffff,14000000,11cdde90 dd 101f24c0,0* 2 dd 101f24c0,0* 2 0 81140500,00240300,074bffff, ,11cd35a0 16
Table 2-42 Entry tFspf 14000000 tShell ioctl f2 reject
SW_ILS Reject Example Descriptions Description A Fibre Channel shortest path first (fsfp) routing Task. An ILS (hello) transmission. A Shell Task, which is a A telnet task that starts up a shell in VX works. An I/O Control event. Specific IOCTL code that displays the number of filter hit count. Reject event. Cross-Reference Refer to Table 1-3 on page 1-7. Refer to section 2.7. Switch Fabric Internal Link Services (SW_ILS) on page 2-37. Refer to section Table 2-1 Fabric OS v2.x and v3.x Task Descriptions on page 2-1. Refer to section 2.5.1. I/O Control (ioctl) on page 2-22. Refer to Table 2-27 on page 2-22. Refer to section Table 2-34 FC_SW: Reject Reason Codes (SW_RJT) on page 2-40 and section Table 2-35 FC-SW (SW-RJT): Reject Reason Explanation Codes on page 2-40.
2-44
2.7.3.5. Zone Example

Example: Embedded port fffc0a sends zoning code 70 request to other embedded port fffc0b. Embedded port fffc0b sends a link control acknowledgment.
22:48:10.633 22:48:10.633 22:48:10.633 22:48:10.633 tReceive tTransmit tSwitch tReceive Rx Tx Tx Rx 8 8 8 8 4 0 4 0 02fffc0b,00fffc0a,0053ffff,70846400,10d065f0 c0fffc0a,00fffc0b,00530235, ,10d065f0 03fffc0a,00fffc0b,00530235,02840000,10d065f0 c0fffc0b,00fffc0a,00530235, ,10d065f0
Output Line 1: Zoning Request

22:48:10.633 tReceive Rx 8 4 02fffc0b,00fffc0a,0053ffff,70846400,10d065f0
Table 2-43 Arg 1 02fffc0b
Breakdown of Arg Fields in Output (Line 1) Arg 2 00fffc0a Arg 3 0053ffff 0053 = OX_ID ffff = RX_ID Arg 4 70846400 Zoning IU Preamble: 70 = IE_ELSCode (zoning) 84 = This is internal to Zoning. It represents the version of the protocol exchanged with zoning on other switches. 00 = Zone Object Type (Name zoning) section 2.7.3.6.7 Zoning Specific Opcode on page 2-48 Arg 5 10d065f0 10d065f0 = IU address pointer
02 = RC_CTL 00 = (request) Identifier fffc0b = D_ID fffc0a = S_ID
Output Line 2: Acknowledgement

22:48:10.633 tTransmit Tx 8 0 c0fffc0a,00fffc0b,00530235, ,10d065f0
Table 2-44 Arg 1 c0fffc0a
Breakdown of Arg Fields in Output (Line 2) Arg 2 00fffc0b 00 = Identifier Arg 3 00530235 0053 = OX_ID fffc0b = S_ID 0235 = RX_ID Arg 4 SW_ILS command code = null Arg 5 10d065f0 10d065f0 = IU address pointer
c0 = RC_CTL (Link control acknowledge) fffc0a = D_ID
Output Line 3: Reply

22:48:10.633 tSwitch Tx 8 4 03fffc0a,00fffc0b,00530235,02840000,10d065f0
Table 2-45 Arg 1 03fffc0a
Breakdown of Arg Fields in Output (Line 3) Arg 2 00fffc0b 00 = Identifier Arg 3 00530235 00530 = OX_ID 0235 = RX_ID Arg 4 02840000 02 = Zoning IU preamble (accept) 84 = New zoning revision (>2.3v firmware) Refer to section 2.7.3.6.2 Operation Codes on page 2-46. Arg 5 10d065f0 10d065f0 = IU address pointer
03 = RC_CTL (reply)
fffc0a = D_ID fffc0b = S_ID
2-45
.Output Line 4: Acknowledge

22:48:10.633 tReceive Rx 8 0 c0fffc0b,00fffc0a,00530235, ,10d065f0
Table 2-46 Arg 1 c0fffc0b
Breakdown of Arg Fields in Output (Line 4) Arg 2 00fffc0a 00 = Identifier fffc0a =S_ID Arg 3 00530235 Arg 4 Arg 5 10d065f0 10d065f0 = IU address pointer
c0 = RC_CTL (Link control acknowledge) fffc0b = D_ID
0053 = OX_ID SW_ISL command code = null 0235 = RX_ID
2.7.3.6. Zoning Codes (NZ)

The following SW_ILS command codes also correlate to zone exchange messaging:
2.7.3.6.1 Zoning Request Codes

Table 2-47 Code 0x22000000 0x23000000 0x24000000 0x25000000 0x26000000 0x70000000 Zoning Request Codes for Zoning Exchange. Abbreviation IE_NZ_MR IE_NZ_ACA IE_NZ_RCA IE_NZ_SFC IE_NZ_UFC IE_ZONE Description Merge Request Acquire Change Authorization Release Change Authorization Stage Fabric configuration Update Fabric Configuration Zone Update (Vendor Unique)
2.7.3.6.2 Operation Codes

Table 2-48 Code 0x01 0x02 0x03 0x04 0x05 0x06 0x07 0x08 0x09 0x0A 0x0B 0x15 0x16 0x17 0x64 0x70 0x71 0x72 Zoning Operation Codes Abbreviation CREATE DELETE ADD REMOVE CLEAR DISABLE ENABLE SAVE MERGE REMOTE CHECK TRANS_DISABLE TRANS_ENABLE TRANS_SAVE ZONE_VERSION ZNMR_REQ_TAKECACHEDRESULT ZNMR_REQ_RESTART ZNMR_REQ_MERGE Description Create an object Delete an object Add a member to an object Remove a member from an object Clear all objects Disable configuration Enable configuration Save in flash Merge two configurations Lookup ID on remote switch Checksum configuration
Request to let receiver take merge result directly Request to let the receiver start on this switch
2-46
2.7.3.6.3 Zoning Request/Response Codes

Table 2-49 Code 0x00 0x01 0x02 (0 - 100) Zoning Request Response Codes Description NZ_SUCCESSFUL NZ_FABRIC_BUSY NZ_FAILED NZ_ERROR_BASE
2.7.3.6.4 Zoning Reason Codes

Table 2-50 Code 0x00 0x01 0x02 0x04 0x05 0x06 0x07 0x09 0x0a 0x0b Zoning Reason Codes Reason NZ_NO_REASON NZ_INVALID_DATA_LEN NZ_UNSUPPORTED_CMD NZ_NOT_AUTHORIZED NZ_INVALID_REQUEST NZ_FABRIC_CHANGING NZ_UPDATE_NOT_STAGED NZ_INVALID_DATA NZ_CANNOT_MERGE ZONING_NO_LICENSE
2.7.3.6.5 TZone Request Code

Table 2-51 TZone - New Zoning SFC Request's Operation Request Values. Description NZ_ACTIVATE_ZONESET NZ_DEACTIVATE_ZONESET NZ_SAVE_FULLZONESET
Zoning Request Value 0x03 0x04 0xF0 Vendor-unique fabric configuration server (FCS) request operation code used for saving configuration without activating or deactivating.
2-47
2.7.3.6.6 Zoning Transaction Abort Reason Codes

Table 2-52 Code 0xa0 0xa1 0xa2 0xa3 0xa4 0xa5 0xa6 0xa7 Zoning Transaction Abort Reason Codes Description ERR_ZONE_MERGE_RECEIVED ERR_ZONE_CONFIG_CHANGE ERR_ZONE_BAD_CONFIG ERR_ZONE_OP_FAILED ERR_ZONE_CANNOT_START_TRANSACTION ERR_ZONE_SHELL_EXITED ERR_ZONE_NOT_OWNER ERR_ZONE_VALIDATION_FAILED
2.7.3.6.7 Zoning Specific Opcode

SW_ILS (0x7f) ENT_MEMBER - Type of Zoning Members Table 2-53 Specific Opcode SW_ILS (0x7f) ENT_MEMBER - Type of Zoning Members 0x01 0x02 0x04 0x08 PORT ENT_WWN ENT_BMAP ENT_NAME Entry describes physical port Entry describes WWN Entry describes al_pa bitmap Entry describes a name
SW_ILS (0x80) ENT_LUN LUN information in entry_t valid 0x01 0x02 ENT_TARGET ENT_INITIATOR e_devType is TARGET e_devType is INITIATOR
2.7.3.6.8 Zone Configuration Operations Code

Table 2-54 Code (hex) 00000001 00000002 00000003 00000004 00000005 00000006 00000007 00000008 00000009 0000000A 0000000B Configuration Operations Operation CREATE DELETE ADD REMOVE CLEAR DISABLE ENABLE SAVE MERGE REMOTE CHECK Description Create an object Delete an object Add a member to an object Remove a member from an object Clear all objects Disable configuration Enable configuration Save in flash memory Merge two configurations Lookup ID on remote switch Checksum configuration
2-48
2.7.3.6.9 Zone Object Types Code

Table 2-55 Code (hex) 00 01 02 03 04 05 06 07 08 Zone Object Types Description Name Zoning Zone set (Cfg) Zone Zone Alias QLP Cfg_end IPO Enable_cfg Active_cfg
2.7.3.6.10 Zone Error (tzone- reject) Code

Table 2-56 Decimal 0 1 2 3 4 5 6 7 8 9 A B Zone error (tzone- reject) Code Abbr. NOERROR NOMEMORY ZONE RULE CHECK ERROR CODE EZACCEPT EZBADPORT FCTYPEMIX ERSINGLEDEV EZLUNMIX EZMENMIX EZHARDSOFTMIX EZFAQLMIX, EZLUNMENMIX ZONE TYPE MANAGEMENT ERROR CODE ZT_SOFTZONE ZT_FABASSIST ZT_DRIVERERR ZG_NO_MORE_CAM ZCHECKBADWWN WWN_IN_PORTZONE OFFSET_MASK_FULL PORT_EPORT Non-existent port number Specific FC type and wildcard mix More than one dev when LUN presents Mixture of devices w/ and w/o LUN at the same port Mix of port and WWN zone members Mix of hard and soft zones Mixing hard zoning with FA or QL zone Mix of QQQ Soft zoning - no need for ZT Description Generic - no error Generic malloc failure No zoning rule violation
C E F 10 11 12 13
FA zone - no need for ZT Driver returns error No more CAM entry in port driver Zone check bad WWN authentication WWN device in hard PORT zone No offset register available Port is an E_port
2-49
2.7.4. 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, etc.) and reports them either FSS compliant or not FSS compliant. A Fabric Service is deemed fault resilient (or FSS compliant) if a set of its components are operating in an active standby mode, and the state replication is carried out from the active components to their corresponding standbys. Table 2-57 outlines each line of FSS output in the portlogdump. Table 2-57 Time Displays time of event FSS Field Descriptions Task Always FSSk Event Can be msg, event, or cmd. Refer to page 2-50. Port Always 0 (FSS is related to CPs, not ports). Cmd 0 = Sent, or Transmitted (TX). 1 = Received (RX). Arg Arg1 = service ID and component ID. Refer to page 2-51 and page 2-52. Arg2 = send/receive operation data. Arg3 = Optional Flags Arg4 = a text description. Refer to page 2-50.
2.7.5. FSS Messages

The following example refers to the relationship between the event column and the final entry of the Arg column. Use Table 2-58 to decode a specific Event and Arg entry. Example:
time task event port cmd args ------------------------------------------------21:54:04.763 FSSK event 0 0 00000000,00000000,00000005,TRAC
Table 2-58 Event Type cmd cmd cmd cmd cmd cmd cmd cmd cmd cmd event
2-50
FSS Messages Abbreviation / fourth Arg CONN FREE NONE RESE STAR STOP TAKE UNFR UPDA YIEL ACTI Description Connect. Freeze. No command. Reset. The sync started. The sync stopped. Take Control. Unfreeze. State update. Yield control. Event reported. The active CP is ready.
Troubleshooting Using the Port Logs Table 2-58 Event Type event event event event event event event event event event event event event event event event event event event event event msg msg msg msg msg msg msg msg msg msg FSS Messages Abbreviation / fourth Arg AVAI COMP DOWN DUMP FAIL INCO MISM MISS NONE RECO RXQH STAN STAR STOP SYNC TAKE TRAC TXQH UPCO UPDA YIEL ACK EXCH NONE RECO STAR STOP TAKE TEST UPDA YIEL Description Event reported. Service is available. Image complete event. Down connection event. A dump is ready. Sync failure event. Incomplete incomplete event. A mismatch event occurred. Event reported. A service is missing. No event occurred. The recovery failed. Event reported. Receptions are high. Event reported. The standby CP is ready. Sync start event. Sync stopped. Sync success event. A take control event occurred. A trace of events was run. Event reported. Transmissions are high. Up connection event. A state update event occurred. A yield control event occurred. Message - state acknowledgment. Broadcast message exchange well-known address Message - no message. Message - recover. Message - sync started. Message - sync stopped. Message - Standby take control. Message - Test Point. Message state update. Message -
2.7.5.1. FSSk Service Identification

The Service ID is displayed in the first 4 bits of Arg1. Example: FSSk Component
21:54:04.882 FSSK event 0 0 00020000,00000000,00000000,UPCO
The Service ID can be viewed by running the hadump command.

Brocade Portlogdump Reference Guide 2-51
Example: 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
2.7.5.2. FSSk Component Identification

A list of possible components can be found by using the hadump command. Table 2-59 lists the component name and associated ID. The Component ID appears in the second bit of Arg 1, .use it number to determine the name of the component. Example: FSSk Component
2:15:51.430 FSSK msg 0 1 00020001,00000000,00000014,UPDA
Table 2-59
FSSk Component Identification Component Name fcsw swc fcp rt fc fabric zone fspf ns ms ps rcs evm track ts slap security web snmp fw diagfss Description The component names indicate either the application name or the kernel module name.
Component ID 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 0x9 0xA 0xB 0xC 0xD 0xE 0xF 0x10 0x11 0x12 0x13 0x14
2-52
2.7.5.3. Reading FSSK Output in the portlogdump

Example:
time task event port cmd args ------------------------------------------------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
Follow the steps for instruction on how read the example above from left to right: 1. 2. 3. 4. The task column should display FSSK. Refer to section 2.7.4. Fabric OS State Synchronization (FSS) on page 2-50 for the FSS description. Look at the event column. All events (msg, cmd, event, etc.) are described in Table 2-58 on page 2-50. Bypass the port column; it will always be 0 since FSS is not a port-related service. Look at the cmd column.
5.
0 indicates Sent, or Transmitted (TX). 1 indicates Received (RX).
Begin reading the Args column.
Arg1 (the first 8 bit set) displays the Service ID and the Component ID. Refer to the section Table 2-59 FSSk Component Identification on page 2-52. Arg2 (the second 8 bit set) displays send/receive operation data. Arg3 (the third 8 bit set) displays optional flags (send/receive data). Arg4 (the fourth entry in the Arg column), displays text that helps clarify the output. - Note the displayed text (for example, UPDA). - Look back at the event column. You will see, for example msg. - Use Table 2-58 on page 2-50 to find the message description. For example: Find msg ----> UPDA ---> read description.
2-53
2.8. Fabric Services Codes

Fabric Services refers to communication to and from any Well-Known Address. The following tables contain information for decoding Fabric Services codes. Table 2-60 Codes 0x01000000 0x02000000 0x03000000 0x04000000 0x05000000 Fabric Services Response Command Codes Abbreviation FS_RJT FS_ACC FS_INQ FS_FADDQ FS_FTOPO Description Reject Accept Vendor inquiry data Fabric address query Fabric topology
Table 2-61 Codes 0x01 0x03 0x09 0x0B
Fabric Services Reject Reason Codes Description FS_INVALID_COMMAND FS_LOGICAL_ERROR FS_CANT_PERFORM_REQ FS_NOT_SUPPORTED
Table 2-62 Codes 0x00 0x30 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x38 0x40 0x41 0x42 0x43 0x44
Fabric Service Reject Reason Code Explanation Description ASRJT_EXPL_NONE ASRJT_EXPL_NOSUCHALIAS ASRJT_EXPL_NORESOURCE ASRJT_EXPL_INVALID_ALIAS_ID ASRJT_EXPL_ALIAS_ID_NOEXIST ASRJT_EXPL_RESOURCE_PROBLEM ASRJT_EXPL_SPAR_CONFLICT ASRJT_EXPL_ALIAS_TOKEN_INVALID ASRJT_EXPL_ALIAS_TOKEN_NOTSUPP ASRJT_EXPL_CANTFORM_PORTLIST ASRJT_EXPL_CANTFORM_CLASS ASRJT_EXPL_NOSUCH_TOKEN ASRJT_EXPL_UNAUTHREQ_BADPASSWD ASRJT_EXPL_UNAUTHREQ_BADAUTH ASRJT_EXPL_INVALID_AUTH_CTL
2-54
Table 2-63 Error
Fabric Segmentation Reason Details for Port Reason Unknown reason Version mismatch Flow Control len mismatch Flow control invalid mode Passed size > fabOP_t BB credit mismatch recv DataField sz mismatch RA TOV mismatch ED TOV mismatch Op Mode mismatch Link Ctrl mismatch Class 2 mismatch Class 3 mismatch Multicast mismatch VC config mismatch VC PID MAP mismatch Class1 datasize mismatch Class1 options mismatch Class2 datasize mismatch Class2 options mismatch Class3 datasize mismatch Class3 options mismatch ClassF options mismatch ClassF init ctl mismatch ClassF rec ctl mismatch ClassF data sz mismatch ClassF con seq mismatch ClassF EE Credit mismatch ClassF OPN SEQ mismatch ClassF resvd mismatch Maximum reasons
FAB_SEG_INCOMPAT_UNKNOWN FAB_SEG_INCOMPAT_VERSION FAB_SEG_INCOMPAT_FCTL_LEN FAB_SEG_INCOMPAT_FCTL_MODE FAB_SEG_INCOMPAT_STRUCT_SZ FAB_SEG_INCOMPAT_BB_CREDIT FAB_SEG_INCOMPAT_DFSZ FAB_SEG_INCOMPAT_RATOV FAB_SEG_INCOMPAT_EDTOV FAB_SEG_INCOMPAT_OPMODE FAB_SEG_INCOMPAT_LINK_CTL FAB_SEG_INCOMPAT_CLASS2 FAB_SEG_INCOMPAT_CLASS3 FAB_SEG_INCOMPAT_MULCAST FAB_SEG_INCOMPAT_VCCONFIG FAB_SEG_INCOMPAT_PIDMAP FAB_SEG_INCOMPAT_CLASS1_SZ FAB_SEG_INCOMPAT_CLASS1_OPT FAB_SEG_INCOMPAT_CLASS2_SZ FAB_SEG_INCOMPAT_CLASS2_OPT FAB_SEG_INCOMPAT_CLASS3_SZ FAB_SEG_INCOMPAT_CLASS3_OPT FAB_SEG_INCOMPAT_CLASSF_OPT FAB_SEG_INCOMPAT_CLASSF_INITCTL FAB_SEG_INCOMPAT_CLASSF_RECCTL FAB_SEG_INCOMPAT_CLASSF_SZ FAB_SEG_INCOMPAT_CLASSF_CONSE FAB_SEG_INCOMPAT_CLASSF_EECRE FAB_SEG_INCOMPAT_CLASSF_OPNSE FAB_SEG_INCOMPAT_CLASSF_RSVD FAB_SEG_INCOMPAT_MAX_DET_REASON
2-55
2.9. ISL Flow Control and Switch Priority Field

The following tables contain information that can be used for decoding ISL Flow Control Values, ISL Flow Control Parameters, and Switch Priority Field Values. Table 2-64 Value hex0001 hex0002 hex0003 - hexFFFE Other Values ISL Flow Control Mode Values Description Vendor Unique R_RDY Flow Control Vendor Unique Reserved
Table 2-65 Size 4 16
ISL Flow Control Parameters Item BB_Credit Compatibility Parameters
Table 2-66
Switch_Priority Field Values Description Reserved Highest priority value. (Note 1) The switch was the principal switch prior to sending or receiving BF. (Note 2) Higher to lower priority values. (Note 3) The switch is not capable of acting as a principal switch.
Hexadecimal Value 00 01 02 03 to FE FF Notes -
1. This value allows the system administrator to establish which switch becomes the principal switch. 2. This allows the same switch to become principal switch if it is still part of the Fabric after sending and/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.
2-56
2.10. Fibre Channel Common Transport Protocol (FC-CT)

The Fibre Channel Common Transport Protocol is used when accessing the following generic service provisions:
Name Server (FFFFFC) Time Sever (FFFFFB) Management Sever (FFFFFA) Alias Server (FFFFF8) Security-Key Distribution Service (FFFFF7).
The N_port uses FC-4 Data Device Frames to perform the request service or query function to these generic services. The R_CTL field of FC-4 Data Device request is always set to 0x02, and the R_CTL field of the reply is set to 0x03. The Type filed for both requests and replies is 0x20 (portlogdump trace does not provide the Type field information). The command code for FC-4 Data Device is always the third word of the payload (word 8) for both the request and reply. There are 2148 bytes in a frame, portlogdump only 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 displayed (4th argument) is from the payload, FC Word 6, and represents the FC-CT revision type being used. Additional payload information is found in corresponding ctin and ctout portlogdump events. Table 2-67 FC-CT Frame Word H E A D E R 5 6 Table 2-68 Word 0-3 4-25 Parameter FC-CT Header Usage Type of FC-CT Header Usage Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 Basic CT_IU preamble Extended CT_IU preamble Bits 31-24 R_CTL =02 or 03 CS_CTL=00 Type =20 SEQ_ID OX_ID DF_CTL Bits 23-16 Bits 15-8 D_ID S_ID F_CTL SEQ_DNT RX_ID Bits 7-0
Note:
The reference in Table 2-69 only covers the Basic CT-IU Preamble. Table 2-69 Word 6 7 8 9 Basic CT_IU Preamble Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT) GS_TYPE GS_Subtype Options Reserved Command/Response Code page 2-54 Maximum/Residual Size Reserved Reason Code Reason Code Explanation Vendor Unique
2-57
2.10.1. FC-CT Definitions

2.10.1.1. CT_Rev
CT_Rev denotes the revision of the protocol. A version of hex 01 indicates prior versions of this standard. A value of hex02 should be used to indicate GS3.rev7.01. Note: The version was changed to hex 02 to allow implementations to indicate support of the extended CT_IU preamble and the partial response indicator.
2.10.1.2. IN_ID
This field shall be set to zero by the Requesting_CT. Note:
The IN_ID field is provided to allow distributed servers to communicate the identity of the original requestor. This field is
not intended to enable third-party responses by distributed servers.
2.10.1.3. GS_Type
GS_Type is used to identify the type of Fibre Channel service. Table 2-70 Value 00-1F 20 FF FE FD FC FB FA F9 F8 F7 GS_Type Values Service Vendor Unique Reserve for use FC-SW2 Broadcast Fabric_F_Port Fabric Controller Name Server Time Server Management Server QOS Provider Alias Server Key Services
2.10.1.4. GS_Subtype
The GS_Subtype field indicates the specific Server behind the Service. Values in this field provided by the individual Service. The GS_Subtype field is used to indicate second level routing behind the N_ Port. For example, if more than one server is provided by the Directory Service at the well-known address hex 'FFFFFC, then the GS_Subtype field is used to distinguish these different servers. Refer to section 2.10.3.9. Name Server GS_Subtype Code on page 2-65 and section Table 2-88 GS_Subtype Code on page 2-78.
2-58
2.10.1.5. The Command/Response Code Field

The Command Response field indicates whether the CT_IU is a request or a response. If the CT_IU is a request, this field then specifies the command to be performed. If the CT_IU is a response, then this field indicates whether the request was accepted or rejected. Requests and responses are further described in the Name Server and Management Server tables (page 2-59 and page 2-71). Table 2-71 depicts the valid Command/Response code values. There are 2148 bytes in a frame, however the portlogdump only captures a portion of the frame. For Tx and Rx events:
The Arg fields obtain portions 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 (4th argument) belongs to the payload. More payload information is obtained in the ctin and ctout events.
2.10.2. About the Name Server (SNS)

The Name Server (also referred to as the Simple Name Server or Directory Server) is a service that stores names, addresses, and attributes of end fabric devices. It provides this information when it is requested. SNS is defined by the Fibre Channel standards and exists at Well-Known Address 0x FFFFFC. Table 2-71 R_CTL 02 03 Nx_port Name Server Examples (Most Common R_CTL) ELS/Data FC-4 Data FC-4 Data Description Unsolicited request Solicited reply Examples NS get / query (FC-CT) NS Response (FC-CT)
2.10.3. Name Server Commands and Code Descriptions

2.10.3.1. Name Server Command Codes
Table 2-72 Name Server Command Codes Object(s) in Request CT_IU Object(s) in Accept CT_IU Code Mnemonic Description Query with port ID 0100 0101 0112 GA_NXT GID_A GPN_ID Get all next Get identifiers Get Port Name Port Identifier A list of Domain_IDs or Domain_ID/Area_IDs. Port Identifier is hex (Note The null value for the Port or Node Name object is hex 00 00 00 00 00 00 00 00. Port Identifier Port Identifier Port Identifier Port Identifier Port Identifier All A list of Domain_IDs or Domain_ID/Area_IDs. Port Name (Note - The null value for the Port or Node Name object is hex 00 00 00 00 00 00 00 00. Node Name Class of Service FC-4 Types Symbolic Port Name Port Type
2-59
0113 0114 0117 0118 011A
GNN_ID GCS_ID GFT_ID GSPN_ID GPT_ID
Get Node Name Get Class of Service Get FC_4 Types Get Symbolic Port Name Get Port Type
Troubleshooting Using the Port Logs Name Server Command Codes Object(s) in Request CT_IU Port Identifier Port Identifier Port Identifier Port Identifier Port Identifier Object(s) in Accept CT_IU IP Address (Port) Fabric Port Name Hard Address List of FC-4 Descriptors FC-4 Features
Table 2-72
Code Mnemonic Description 011B 011C 011D 011E 011F GIPP_ID GFPN_ID GHA_ID GFD_ID GFF_ID Get IP Address (Port) Get Fabric Port Name Get Hard Address Get FC-4 Descriptors Get FC-4 Features
Query with Port name 0121 012B GID_PN GIPP_PN Get Port Identifiers Get IP Address (Port) Port Name Port Name Port Identifier IP Address (Port)
Query With Node Name 0131 0132 0135 0136 0139 GID_NN GPN_NN GIP_NN GIPA_NN GSNN_NN Get Port Node Name Get Port Node Names Get IP Address (Node) Get Initial Process Associator
Get Symbolic Node Name
Node Identifiers Node Name Node Name Node name Node Name
List of Port Identifiers List of Port Identifiers and Port Names IP Address (Node) Initial Process Associator
Symbolic Node
Query With IP 0153 0156 0171 GNN_IP GIPA_IP GID_FT Get Node Name Get Initial Process Associator Get Port Identifiers IP Address (Node) IP Address (Node) None. Because FC-4 Type is specified as an encoded value, not as an object, see Table 2-80 on page 2-65. None, because type is specified as an encoded value, not as an object, see Table 2-80 on page 2-65. Node Name Initial Process Associator List of List of Port Identifiers.
0172 0173
GPN_FT GNN_FT
Get FC4-Type Port Name Get FC-4 Type Node Names.
List of port identifiers and port names. List of port identifiers and port names.
Query With Port Type 01A1 GID_PT Get Port Identifiers Port Type (refer to Table 2-78 on page 2-64) List of Port Identifiers
Query With IP Port 01B1 01B2 GID_IPP GPN_IPP Get Port Identifiers for IP Address (Port) Get Port Name IP Address (Port) IP Address (Port) List of Port Identifiers Port Name
Query With FC-4 Features 01F1 GID_FF Get Port Identifiers FC-4 Features List of Port Identifiers
2-60
Troubleshooting Using the Port Logs Table 2-72 Name Server Command Codes Object(s) in Request CT_IU Object(s) in Accept CT_IU
Code Mnemonic Description Registration 0212 0213 0214 0217 RPN_ID RNN_ID RCS_ID RFT_ID Register Port Name Register Node Name
Register Class of Service
Port Identifier, Port Name Port Identifier, Node Name Port Identifier, Class
None None None None
Register FC-4 Types
Port Identifier, FC-4 Types
0218
RSPN_ID
Register Port SymbolicName for this Port ID Register Port Type for this Port ID Register IP Address (Port) Register Fabric Port Name Register Hard Address Register FC-4 Descriptors Register FC-4 Features Register IP Address for this Node WWN Register IP Address for this Node WWN Register Node Symbolic Name for this Node WWN
Port Identifier, Symbolic Port Name Port Identifier, IP Address (Port) Port Identifier, IP Address (Port) Port Identifier, Fabric Port Name Port Identifier, Hard Address Port Identifier, FC-4 Types and FC-4 Descriptors Port Identifier, FC-4 Features Node Name, IP Address (Node) Node Name, Initial Process Associator Node Name, Symbolic Node Name
None
021A 021B 021C 021D 021E 021F 0235 0236 0239
RPT_ID RIPP_ID RFPN_ID RHA_ID RFD_ID RFF_ID RIP_NN RIPA_NN RSNN_NN
None None None None None None None None None
De-Registration 0300 DA_ID De-register all Port Identifier None
FC_CT Command Restrictions The following command codes shall not be 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 command Command codes F000-FFFF: Vendor unique FC-CT commands.
2-61
2.10.3.2. FC-CT Response Commands

Table 2-73 Value 0001-7FFF 8001 8002 other values FC-CT Response Commands Response Request CT_IU. These codes are used by all CT applications; for an example, refer to Table 2-72 on page 2-59). Reject Response CT_IU. These codes are used by all CT applications; for an example, refer to Table 2-74 on page 2-62). Accept Response CT_IU (hex 0000: All available information was returned in the Accept CT_IU.) Reserved
2.10.3.3. FC-CT Reject Reason Code (RJT)

Table 2-74 Reason 01 02 03 04 05 07 09 0B Others FF FC-CT Reject Reason Code Description Invalid command code Invalid version level Logical error Invalid information unit size Logical busy Protocol error Unable to perform command request Command not supported Reserved Vendor-unique error (see Vendor Unique field)
2.10.3.4. FC-CT Reason Code Explanation (NS_RJT)

Figure 2-1 FC-CT Reject Reason Code Explanation Description No additional explanation Port Identifier not registered Port Name not registered Node Name not registered Class of Service not registered IP Address (node) not registered Initial Process Associator not registered FC-4 TYPEs not registered Symbolic Port Name not registered Symbolic Node Name not registered
Encoded Value (Bits 15-8) 00 01 02 03 04 05 06 07 08 09

2-62
Troubleshooting Using the Port Logs Figure 2-1 FC-CT Reject Reason Code Explanation (Continued) Description Port Type not registered IP Address (port) not registered Fabric Port Name not registered Hard Address not registered FC-4 Descriptor not registered FC-4 Features not registered Access denied Unacceptable Port Identifier Data base empty No object registered in the specified scope Reserved
Encoded Value (Bits 15-8) 0A 0B 0C 0D 0E 0F 10 11 12 13 Others
2.10.3.5. Fabric Internal FC_CT Commands

Table 2-75 Code 0410 0420 0430 0450 04A0 04B0 04C0 04D0 04E0 Name Server Command Codes - Fabric Internal FC_CT Commands Mnemonic GE_ID GE_PN GE_NN GE_IP GE_PT GE_ZM GE_ZN GE_IPP GE_FF Description Get entry, based on port identifier Get entry, based on port name Get entries, based on node name Get entries, based on IP address Get entries, based on port type Get entries, based on zone member Get entries, based on zone name Get entries, based on port IP address Get entries based on FC-4 features
2.10.3.6. Name Server Request Types

Table 2-76 Name Server Request Types Description Get Object(s) (Query) Register Object Deregister Object(s) Fabric internal FC-CT commands Vendor unique FC-CT commands Hexadecimal Code 01xx 02xx 03xx 0400-04FF and E000-EFFF F000-FFFF
2-63
2.10.3.7. Name Server Objects

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

Table 2-78 Code 0 1 2 3 Name Server Port Type Description NSPT_UNKNOWN N_PORT NL_PORT NFL_PORT 0x04-0x80 are reserved 0x7F special value for all of the above ports 81 82 83 84 Nx_PORT F_PORT FL_PORT LT_PORT E_PORT
2-64
2.10.3.9. Name Server GS_Subtype Code

Table 2-79 Value 01 02 03 80-EF Other values Name Service GS_Subtype Code Service Reserved Name Server IP Address Server FC-4 specific Servers Reserved
2.10.3.10. FC-4 Type Codes

The FC-4 Type Code provides the Type of protocol service (i.e., FC_CT, FCP, FCIP etc.). Table 2-80 Code 0x00 0x01 0x04 0x05 0x08 0x09 0x20 0x21 0x22 0x23 0x24 0x25-0x27 0x30-0x33 0x40 0x58 0x5b 0xe0 0xff FC-4 Type Code Service Basic Link Extend Link ISO/IEC 8802-2 LLC/SNAP (in order) FCIP SCSI_FCP SCSI-GPP Fibre Channel Services (NS,MS,AS,etc.) FC-FG FC_SW FC-AL FC-SNMP Fabric Services Scalable Coherent Interface HIPPI-FP Virtual Interface Fabric Vendor Specific
2.10.3.11. Server-to-Server Protocol Data Unit Command/Response Code

Table 2-81 Server-to-Server Protocol Data Unit Command/Response Code Brocade Specific 0x0001 0x0002 0x0003 0x0004 NSS_REQUEST NSS_RESPONSE NSS_INFORM NSS_DELETE
2-65
2.10.3.12. NSS_CT Command/Response Code

Table 2-82 NSS_CT Command/Response Code CT_VU_NSS (Brocade, 0x0c) Vendor Unique Name Server Protocol Data Unit Command/Response Code. NSS_CT_SUBTYPE 1 0x0001 0x0002 0x0003 0x0004 0x0410 0x0420 0x0430 0x0450 0x0470 0x04A0 NSS_REQUEST NSS_RESPONSE NSS_INFORM NSS_DELETE NSS_GE_ID NSS_GE_PN NSS_GE_NN NSS_GE_IP NSS_GE_FT NSS_GE_PT
2.10.3.13. NSS-CT Response Commands

Table 2-83 Value 0001-7FFF 8001 8002 other values FC-CT Response Commands Response Request CT_IU. These codes are used by all CT applications; for an example, refer to Table 2-72 on page 2-59). Reject Response CT_IU. These codes are used by all CT applications; for an example, refer to Table 2-74 on page 2-62). Accept Response CT_IU (hex 0000: All available information was returned in the Accept CT_IU.) Reserved
2.10.3.14. NSS-CT Reject Reason Code (RJT)

Table 2-84 Reason 01 02 03 04 05 07 09 0B Others FF
2-66
FC-CT Reject Reason Code Description Invalid command code Invalid version level Logical error Invalid information unit size Logical busy Protocol error Unable to perform command request Command not supported Reserved Vendor-unique error (see Vendor Unique field)
2.10.3.15. NSS-CT Reason Code Explanation (NS_RJT)

Figure 2-2 FC-CT Reject Reason Code Explanation Description No additional explanation Port Identifier not registered Port Name not registered Node Name not registered Class of Service not registered IP Address (node) not registered Initial Process Associator not registered FC-4 TYPEs not registered Symbolic Port Name not registered Symbolic Node Name not registered Port Type not registered IP Address (port) not registered Fabric Port Name not registered Hard Address not registered FC-4 Descriptor not registered FC-4 Features not registered Access denied Unacceptable Port Identifier Data base empty No object registered in the specified scope Reserved Encoded Value (Bits 15-8) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 Others
2-67
2.10.4. ctin and ctout Event Examples

Example: Fabric OS v4.2 using the nsd (Name Server daemon), embedded port to embedded port.
portlogdump: time task event port cmd args ------------------------------------------------01:42:55.350 PORT Rx 15 20 02fffc01,00fffc02,019cffff,01000000 01:42:55.350 PORT Tx 15 0 c0fffc02,00fffc01,019c0322 01:42:55.351 nsd ctin 15 fc 00010410,000104d1 01:42:55.353 nsd ctout 15 fc 00038002,00000001,00fffc01 01:42:55.353 PORT Tx 15 644 03fffc02,00fffc01,019c0322,01000000 01:42:55.355 PORT Rx 15 0 c0fffc01,00fffc02,019c0322
fc = Name Server - The 02 and 03 lines of code represent FC words 0, 1, 4 (header words) and 6 (GS_Rev Code), the ctin command code 0410 represents get entry based on port identifier as found in Table 2-75 on page 2-63, the following argument represents who to get port entry for, the ctout is an accept as found in section 2.10.3.2. FC-CT Response Commands on page 2-62 followed by information unit request objects. Notice that this type of communication uses acknowledgements between each communication exchange.
Example: Fabric OS v3.x example using tNSd (Name Server daemon), end device to fabric.
12:06:16.433 12:06:16.433 12:06:16.433 12:06:16.433 tReceive tNSd tNSd tNSd Rx3 0 ctin ctout Tx3 20 0 0 0 52 fc fc 0 02fffffc,00011000,a838ffff,01000000 00010173,00000008 1st frame 00018001,00090700 2nd frame 03011000,00fffffc,a838000e
fc = Name Server - The 02 and 03 lines of code represent FC words 0, 1, 4 and 6, see section 2.10.4.1. Decoding a ctin event on page 2-68 and section 2.10.4.2. Decoding a ctout Event on page 2-69 for interpretation of the ctin and ctout code.
Example: Fabric OS v4.2 using the msd (Management Server daemon)

fa = Management Server - the ctin shows a 0624 MS_Get_Port_Name query as found in Table 2-87 on page 2-71, the ctout shows an 8002 accept as found in section 2.10.3.2. FC-CT Response Commands on page 2-62 followed by request information units.
2.10.4.1. Decoding a ctin event

Example: Management Server (fa) or Name Server (fc), this example is from the middle example above, Fabric OS v3.x example using tNSd (Name Server daemon), end device to fabric.
12:06:16.433 tNSd ctin 0 fc 00010173,00000008
1. 2.
Note the command field if the cmd field is fa use Table 2-87 on page 2-71 to interpret command code, if the cmd field is fc use Table 2-72 on page 2-59 or Table 2-75 on page 2-63. Divide argument 1 into two 16-bit fields: 0001 and 0173 a. The first 16-bit field is the bit map, which indicates whether subsequent arguments are valid.

b.
2-68
A 0001 entry (1 = 0001 in binary) means that only one additional argument will follow after argument 1 (in this example, 00000008). If the first 16-bit field is 0003, then arguments in position 1 and 2 are a set. Thus, two arguments will follow after argument 1.
The second 16-bit field is the FC_CT command code

Troubleshooting Using the Port Logs i. ii. c. if the cmd field was fa use Table 2-87 on page 2-71 to interpret command code
if the cmd field is fc use Table 2-72 on page 2-59. Let us suppose the cmd field is fc and the command code in this position is 0173 meaning GNN_FT - Get FC-4 Node Name. See CT_IU Frame below.
The FC-4 object is defined by argument 2 00000008. In this example argument 2 belongs to word 4 of the GNN_FT frame. Instructions to use FC-4 Type Code = 08 meaning SCSI- FCP are referred to in Table 2-87 on page 2-71 which refers to section 2.10.3.10. FC-4 Type Codes on page 2-65. Table 2-85 Word 0 1 2 3 4 Get FC4-Type Node Name, 0173 Frame Bits 31-24 FC_CT Rev =01 GS_TYPE GS_Subtype Bits 23-16 Bits 15-8 Bits 7-0
IN_ID (S to zero by the Requesting_CT) Options Reserved Maximum/Residual Size Reason Code Explanation Area_ID scope Vendor Unique FC-4 Type Code=08
Command Code =0173 Reserved Reserved Reason Code Domain ID scope
2.10.4.2. Decoding a ctout Event

Example:
12:06:16.433 tNSd ctout 0 fc 00018001,00090700
1.
The response frame does not care whether the command field is an fa or fc, both use the FC_CT Response Code section 2.10.3.2. FC-CT Response Commands on page 2-62 (if the response is a reject the reason and explanation for the reject are found in locations related to fa or fc). Take argument 1 and divide into two 16-bit fields. In this example we have: 0001 and 8001 a. The first 16-bit field 0001 is the bit map indicating whether subsequent args are valid.
2.

b.
A 0001 entry (1 = 0001 in binary) means the that only one additional argument will follow after argument 1 (in this example, 0090700). If the first 16-bit field is 0003, then arguments in position 1 and 2 are a set. Thus, two arguments will follow after argument 1.
The second 16-bit field represents the FC_CT response code.
If the second 16-bit field is a reject (8001) section 2.10.3.2. FC-CT Response Commands on page 2-62 If the cmd code is an fc then argument 2 is a reject reason and reason explanation, refer to section 2.10.3.3. FC-CT Reject Reason Code (RJT) on page 2-62 and section 2.10.3.4. FC-CT Reason Code Explanation (NS_RJT) on page 2-62. (The example below is a reject with reject reason and explanation: 00090700, the 09 in table section 2.10.3.3. FC-CT Reject Reason Code (RJT) on page 2-62 tells us unable to perform command request; the 07 from table section 2.10.3.3. FC-CT Reject Reason Code (RJT) on page 2-62 tells us FC-4 types not registered). If the cmd code is an fa then argument 2 is a reject reason and reason explanation, refer to Table 2-89 on page 2-78. If the second 16-bit field is an accept (8002) section 2.10.3.2. FC-CT Response Commands on page 2-62, then arguments 2 and 3 are IU response objects.
2-69
GNN_FT (0173) Table 2-86 Word 0 1 2 3 4 5 6-7 Accept Get FC4-Type Node Name, 0173 Frame Bits 31-24 FC_CT Rev =01 GS_TYPE Reserved Control Bits 23-16 GS_Subtype Reason Code =09 Bits 15-8 Options Reason Code Explanation =07 Port Identifier#1 Reserved Node Name #1 Bits 7-0 Reserved Vendor Unique IN_ID (S to zero by the Requesting_CT) Maximum/Residual Size
Command Code = 8001
2-70
2.11. The Management Server

The Management Service (MS) provides a single management access point within the Fabric. The Management Server (MS) Well-Known Address = FFFFFA.
2.11.1. About the Fabric Configuration Server

FCS switches are trusted switches and are used for managing fabrics where secure mode is enabled. The primary FCS switch is a central point for distributing fabric configuration information and management changes. All management access to the fabric must flow through the primary FCS switch. Should the primary FCS switch be unavailable, it then becomes necessary to use the first available backup FCS switch for managing the fabric. Please reference the Brocade Design, Deployment and Management Guide (part number: 53-0000366-03), Brocade Secure Fabric OS Users Guide Version, and the Brocade Secure Fabric OS Quickstart Guide for further detail about Secure Fabric OS.
2.11.2. 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 section 2.10.3.2. FC-CT Response Commands on page 2-62.
2.11.3. Management Server Response Codes

All FC_CT response codes use the section 2.10.3.2. FC-CT Response Commands on page 2-62.
2.11.4. 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. Table 2-87 Code 0x0100 Management Server Command Code Description Get Topology Information Object(s) in Request CT_IU The Request CT_IU for GTIN contains the request payload defined for the Request Topology Information Extended Link Service. Object(s) in Accept CT_IU
The Accept CT_IU for GTIN contains the ACC payload defined for the Request Topology Information Extended
Mnemonic MS_GTIN
Link Service.
0x0101
MS_GIEL
Get interconnect element list
List of Interconnect Element Names and Types Interconnect element name Interconnect element name Interconnect element type Domain identifier
0x0111 0x0112
MS_GIET MS_GDID
Get interconnect element type Get domain ID
2-71
2
Code 0x0113 0x0114 0x0115 0x0116
Troubleshooting Using the Port Logs Management Server Command Code Description Get Mgmt Identifier Get Fabric Name Get logical IE Name Get Mgmt Address list Object(s) in Request CT_IU Interconnect element name Interconnect element name Interconnect element name Interconnect element name Interconnect element name Interconnect element name Object(s) in Accept CT_IU Management Identifier Fabric Name0x0115 Interconnect element logical name Interconnect element management address list Interconnect element information list List of Port Names, Port Types, Port TX Types, and Port Module Types Port type Port number List of attached port name Port state (See Port State table) Attached topology information (4 bytes format) List of platform node name See Platform type table Platform Mgmt address list Platform Name List of platform names None (Note: The Accept CT_IU for GNID contains the ACC payload defined for the Request Node Identification Data) Extended Link Service
Table 2-87
Mnemonic MS_GMID MS_GFN MS_GLIEN MS_GMAL
0x0117 0x0118
MS_GIEIL MS_GPL
Get IE Information list Get switch port list
0x0121 0x0122 0x0124 0x0126 0x0128
MS_GPT MS_GPPN MS_GAPNL MS_GPS MS_GATIN
Get switch port type Get attached port name list Get switch port state Get attached topology information
Port Name Port WWN Port WWN Port WWN
Get switch physical port number Port WWN
Get Platform Related Info 0x0191 0x0192 0x0194 0x01A1 0x01A2 0x01B1 MS_GPLNL MS_GPLT MS_GPLA MS_GNPL MS_GPNL MS_GNID Get platform node name list Get platform type Get platform attributes Get platform name-node name Get platform name list Get node identification data Platform name Platform name Platform name Platform Node name None Platform node name
2-72
Troubleshooting Using the Port Logs Table 2-87 Code 0x0215 Management Server Command Code Description Register IE logic name Object(s) in Request CT_IU Interconnect element Name, Interconnect Element Logical Name Object(s) in Accept CT_IU None
Mnemonic MS_RIELN
Register Platform Related Info 0x0280 MS_RPL Register platform None Platform Name, Platform Type, Platform Mgmt Address list, Platform Node Name List Platform name, None Platform Node Name Platform Name, Platform Type Platform Name, Platform Mgmt Address Platform Name None None
0x0291 0x0292 0x0293
MS_RPLN MS_RPLT MS_RPLM
Register platform node name
Register platform type Register platform Mgmt address
De-Register Platform Related Info 0x0380 0x0391 0x0392 0x0393 MS_DPl MS_DPLN MS_DPLM MS_DPLML De-register platform De-register platform node name De-Register Platform Mgmt Addr De-register platform mgmt address list Get port statistics Get port errors Clear port stats Port enable Port disable Get a route between two end ports Nexthop info from remote switch Output ports to reach a domain Set static route Delete static route Platform Name None None None Platform Node Name None
Port Performance Info 0x0400 0x0401 0x0402 0x0403 0x0404 0x0405 0x0406 0x0407 0x0408 0x0750 MS_GPST MS_GPERR MS_PCLST MS_PENAB MS_PDISA MS_GROUT MS_GLROUT MS_GPATH MS_GROUT MS_DELROUT
Routing Info
Fabric Hierarchy 0x0501 0x502 MS_GFABRIC MS_GSW Return all switch and port wwns Return switch and port wwns
2-73
2
Code
Troubleshooting Using the Port Logs Management Server Command Code Description Object(s) in Request CT_IU Object(s) in Accept CT_IU
Table 2-87
Mnemonic
Switch Info 0x0505 0x0506 0x0507 0x0508 0x0509 0x050a 0x050b MS_GSWITCH MS_SSWITCH MS_GSWITCH2 MS_SSWITCH2 MS_GAPIVERSION MS_GSSWITCH_NG MS_SSWITCH_NG Get switch information Set switch information Get switch information Set switch information 2.0+ Get API version Get switch info ng Set switch info ng Get port log Get error log Get fru history log Get port flash log Get port information Set port information Get port stats information Set port stats information Get device information Get device, string len = 256 Get port err information Set port err information Asset management Get fl port info Get PortModule info Set PortModule info Get port info 2 Set port info 2 Get platform state info get all platform database Get cp info Set fru Attributes Switch Enclosure Attributes 2 Get port info ng Set port info ng Start port diag Stop port diag Get port diag profile Get port diag status
API Version Info
0x05010 MS_GPORTLOG 0x05011 MS_GERRLOG 0x05012 MS_GFRULOG 0x05013 MS_GPORTNVLOG Port Info 0x0605 0x0606 0x0607 0x0608 0x0609 0x060a 0x060b 0x060c 0x060d 0x060e 0x060f 0x0610 0x0611 0x0612 0x0613 0x0614 0x0615 0x0616 0x0617 0x0618 0x0619 0x0620 0x0621 0x0622 0x0623
2-74
MS_GPORT MS_SPORT MS_GPSTATS MS_SPSTATS MS_GDEVICE MS_GDEVICE2 MS_GPERRS MS_SPERRS MS_GENVATTR MS_GFLPORT MS_GMODULE MS_SMODULE MS_GPORT2 MS_SPORT2 MS_GPLATINFO MS_GPLATALL MS_GCP MS_SFRU MS_GENVATTR2 MS_GPORT_NG MS_SPORT_NG MS_START_PORT_DIAG MS_STOP_PORT_DIAG MS_GET_PORT_DIAG_PF MS_GET_PORT_DIAG_ST
Troubleshooting Using the Port Logs Table 2-87 Code 0x0624 0x0625 0x0626 0x0627 0x0630 RCOM 0x0701 0X0705 0x0706 0x0707 0x0708 0x0709 0x070a 0x070b 0x070c 0x070d 0x070e 0x070f 0x0710 0x0711 0x0712 0x0713 0x0714 0x0715 0x0716 0x0717 0x0718 0x0719 MS_RCOM MS_FW_LICENSE MS_FW_GET_CA MS_FW_GET_TH MS_FW_APPLY_ ALARM MS_FW_APPLY_ BOUNDARY MS_FW_CANCEL_ ALARM MS_FW_CANCEL_ BOUNDARY MS_FW_SET_ALARM_ LEVEL MS_FW_SET_ALARM MS_FW_SET_BN_ LEVEL MS_FW_SET_BN_BS MS_FW_SET_BN_HIGH MS_FW_SET_BN_LOW MS_FW_SET_BN_TB MS_FW_SET_BN_UNIT MS_FW_SET_TH_STATUS MS_FW_SET_TH_BI MS_FW_SET_TH_BT MS_FW_INIT_CONFIG MS_FW_INSERT_CONFIG MS_FW_UPDATE_ CONFIG Fabric Watch. Get Threshold. Fabric Watch. Apply alarm. Fabric Watch. Apply boundary. Fabric Watch. Cancel alarm. Fabric Watch. Cancel boundary. Fabric Watch. Set alarm level Fabric Watch. Set Alarm. Fabric Watch. Set Boundary Level Fabric Watch. Set Boundary. Fabric Watch. Set Boundary High level. Fabric Watch. Set Boundary Low Level Fabric Watch. Set Boundary. Fabric Watch. Set Boundary Unit. Fabric Watch. Set Threshold Status. Fabric Watch. Set Threshold Fabric Watch. Set Threshold Fabric Watch. Initial Configuration. Fabric Watch. Insert Configuration Fabric Watch. Update Configuration. Get group commands Management Server Command Code Description Get port name Set port name Get the node port err stats Get the node port err stats Telnet Command Tunneling Object(s) in Request CT_IU Object(s) in Accept CT_IU
Mnemonic MS_GET_PORT_NAME MS_SET_PORT_NAME MS_GNPERRS MS_SNPERRS MS_GTCT
2-75
2
Code 0x071a 0x071d 0x071e 0x071f 0x0720 0x0721 0x0722 0x0723 0x0726 0x0727 0x0728 0x0729 0x072a 0x072b 0x072c 0x072d 0x072e 0x072f 0x0730 0x0731 0x0732 0x0733
Troubleshooting Using the Port Logs Management Server Command Code Description Fabric Watch. Load Configuration Management Server event. Management Server event enable Fabric Watch. Object(s) in Request CT_IU Object(s) in Accept CT_IU
Table 2-87
Mnemonic MS_FW_LOAD_CONFIG MS_EVENT MS_EVENT_ENABLE_FW
MS_EVENT_DISABLE_FW Management Server Event disable Fabric Watch. MS_LICENSE_ADD MS_LICENSE_RM MS_LICENSE_GET MS_LICENSE_GETALL MS_PRODUCT_GET MS_PRODUCT_GETALL MS_DOWNLOAD_START MS_DOWNLOAD_ PACKET MS_DOWNLOAD_ABORT MS_DOWNLOAD_END MS_UPLOAD_START MS_UPLOAD_PACKET MS_UPLOAD_ABORT MS_UPLOAD_END MS_EVENT_ENABLE_TC MS_EVENT_DISABLE_TC MS_DOWNLOAD_ SELF_START MS_DOWNLOAD_ SELF_ABORT Management Server - license addition reported. Management Server - license removal reported. Management Server - get license. Management Server - get all licenses. Management Server - get product. Management Server - get all products. Management Server - download start reported. Management Server - download packet reported. Management Server - download aborted. Management Server - download ended. Management Server - upload started. Management Server - packet upload reported. Management Server - upload aborted. Management Server - upload ended. Management Server - Enable Track Changes. Management Server - Enable Track Changes. Management Server - self start download reported Management Server - self start download aborted.
2-76
Troubleshooting Using the Port Logs Table 2-87 Code Management Server Command Code Description Object(s) in Request CT_IU Object(s) in Accept CT_IU
Mnemonic
In-Band SGroup Command 0x0801 0x0802 0x0803 0x0810 0x0811 0x0812 0x0813 0x0814 0x0815 0x0816 0x0817 0x1000 MS_SG_GET MS_SG_SET MS_SG_DEL MS_SEC_GET_CSR MS_SEC_SET_CERT MS_SEC_SET_KEY_CERT MS_SEC_COUNTER MS_SEC_GEN_CSR MS_SEC_COUNTER2 MS_SEC_GET_BANNER MS_SEC_SET_BANNER MS_FC_API Management Server Management Server Management Server Management Server - Security Management Server - Security. Set certificate. Management Server - Security set key certificate. Management Server - Security Counters. Management Server - Security. Management Server - Security Counter 2 Management Server - Security. Get banner. Management Server - Security Set banner. Management Server -Forward compatible API Exchange Platform Database Merge Platform Database Commit the previous Reg/Dereg Plat Cmd Get Management Server Capabilities Activate Platform Management Services DeActivate Platform Management Services Enable/Disable TD Management Services Get Switch Default Zoning Behavior Set Switch Default Zoning Behavior
*Note: 0x0801 - 0x804 do not appear in Fabric OS 4.2.0
FC-SW-2 MS Command Codes 0xE000 0xE001 0xE010 0xE020 MS_EXGPLDB MS_MRGPLDB MS_PLCOMIT MS_GCAP
Brocade Vendor Unique Platform Related Info 0xF000 0xF001 0xF002 MS_PLACTV MS_PLDACTV MS_TDMGMT
Switch Default Zoning Behavior 0x0805 0x0806 MS_GSWITCHDZB MS_SSWITCHDZB
2-77
Management Server GS_Subtype Code Table 2-88 Code 01 02 03 04 10 E0-FF EO E1 E2 E3 E4 Other values GS_Subtype Code Server Fabric Configuration Server Unzoned Name Server Fabric Zone Server Reserved for Lock Server FDMI Vendor Specific Servers Unique MS Subtype. Brocade API. MS telnet subtype. Telnet. Unique MS Subtype. API Event. Unique subtype. Asynchronous Response Router (ARR). Reserved
2.11.5. 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 following reason codes: Table 2-89 Code 00 01 10 11 12 13 14 15 16 17 30 31 32 33 34
2-78
Management Server Reason Code and Explanation Reason No additional explanation Invalid Name_Identifier for Interconnect Element or Port Interconnect Element List not available Interconnect Element Type not available Domain Identifier not available Management Identifier not available Fabric Name not available Interconnect Element Logical Name not available Management Address List not available Interconnect Element Information List not available 0x18-2F reserved for IE Port List not available Port Type not available Physical Port Number not available Reserved Attached Port Name List not available
Troubleshooting Using the Port Logs Table 2-89 Code 35 36 50 60 61 62 63 64 65 66 Management Server Reason Code and Explanation Reason Reserved Port State not available Unable to register Interconnect Element Logical Name Platform Name does not exist Platform Name already exists. Platform Node Name does not exist Platform Node Name already exists. EXPL_PLATFORM_DATABASE_CONFLICT EXPL_PLATFORM_FUNC_UNABLE_TO_ACTIVATE M_E_P_UNABLE_TO_ACTIVATE MSRJT_EXPL_PLATFORM_FUNC_UNABLE_TO_ACTIVATE
MSRJT_EXPL_PLATFORM_FUNC_SEC_CONFLICT
67 F0 F1 F2 0x01 0x91 0x92 0x93 0x94 0x95 0x96 0x97 0x98 0x99 0xa1 0xa5 0xb5 0xc5 0xc6 0xc7 0xc8 0xc9 0xca 0xcb 0xcc 0xcd MSRJT_EXPL_NO_PLATFORM_MGMTADDR EXPL_AUTHORIZATION_EXCEPTION EXPL_AUTHEN_EXCEPTION EXPL_DATABASE_FULL MSRJT_EXPL_WWN_INVALID MSRJT_EXPL_NO_PORT_STAT MSRJT_EXPL_NO_PORT_ERRS MSRJT_EXPL_PORT_CLR_FAIL MSRJT_EXPL_PORT_ENABLE_FAIL MSRJT_EXPL_PORT_DISABLE_FAIL MSRJT_EXPL_NO_ROUT_INFO MSRJT_EXPL_NO_LOCAL_ROUTE MSRJT_EXPL_NO_PATH_INFO MSRJT_EXPL_SET_STATIC_ROUTE_FAILED MSRJT_EXPL_DELETE_STATIC_ROUTE_FAILED MSRJT_EXPL_NO_SUCH_SWITCH MSRJT_EXPL_NO_SUCH_PORT MSRJT_EXPL_INVALID_ARG MSRJT_EXPL_FW_INVALID_CLASS_AREA MSRJT_EXPL_FW_INVALID_INDEX MSRJT_EXPL_FW_INVALID_LEVEL_INDICATOR MSRJT_EXPL_FW_INVALID_EVENT_TYPE MSRJT_EXPL_FW_INVALID_ALARM_MATRIX MSRJT_EXPL_FW_INVALID_BUFFER_SIZE MSRJT_EXPL_FW_INVALID_LOW MSRJT_EXPL_FW_INVALID_HIGH
Definitions for Port Info Access
2-79
Troubleshooting Using the Port Logs Table 2-89 Code 0xce 0xcf 0xd0 0xd1 0xd2 0xd3 0xd4 0xd5 0xd6 0xd7 0xd8 0xd9 0xda 0xdb 0xdc 0xdd 0xde 0xe1 0xe2 0xe3 0xe4 0xe5 0xe6 0xe7 0xe8 0xe9 0xea 0xeb 0xec 0xed 0xee 0xef Management Server Reason Code and Explanation Reason MSRJT_EXPL_FW_INVALID_TB MSRJT_EXPL_FW_INVALID_UNIT_STRING MSRJT_EXPL_FW_INVALID_STATUS MSRJT_EXPL_FW_INVALID_BT MSRJT_EXPL_FW_INVALID_WWN MSRJT_EXPL_FW_DOWNLOAD_FAILED MSRJT_EXPL_FW_INVALID_PROFILE MSRJT_EXPL_FW_LOAD_FAILED MSRJT_EXPL_FW_INSERT_FAILED MSRJT_EXPL_FW_DOWNLOAD_INIT_FAILED MSRJT_EXPL_FW_TOO_MANY_PROXY MSRJT_EXPL_FW_PROXY_NOT_FOUND MSRJT_EXPL_FW_NO_LICENSE MSRJT_EXPL_CERT_ALREADY_INSTALLED MSRJT_EXPL_CERT_REQ_FAILED MSRJT_EXPL_CORRUPT_FLASH /* attach port stats errors */ MSRJI_EXPL_RLS_SERVICE_DISABLE MSRJT_EXPL_PORTCFG_FAILED MSRJT_EXPL_PORTCFG_BADPORT MSRJT_EXPL_PORTCFG_BADARG MSRJT_EXPL_PORTCFG_BADNUMARG MSRJT_EXPL_PORTCFG_CFGABT MSRJT_EXPL_PORTCFG_NOLICENSE MSRJT_EXPL_PORTCFG_BADSWTYPE MSRJT_EXPL_PORTCFG_ISQLPORT MSRJT_EXPL_PORTCFG_ISLPORT MSRJT_EXPL_PORTCFG_ISGPORT MSRJT_EXPL_PORTCFG_MCASTLB_LBEXIST MSRJT_EXPL_PORTCFG_LONGDIST_MCASTON MSRJT_EXPL_PORTCFG_LONGDIST_NOLDFAB MSRJT_EXPL_PORTCFG_BADPTTYPE MSRJT_EXPL_PORTCFG_BADSTRING Port Cfg Errors
Secure SAN PKI Installation Support
Firmwaredownload Errors
2-80
2.11.5.1. Management Server Examples

Example: Fabric OS v4.x
Output Line 1:
17:31:48.934 msd ctin 0 fa 00010624,10000005
The management server command code 0624 means get port name as found in Table 2-87 on page 2-71, the next argument specifies the object of which to the port name. Output Line 2:
17:31:48.934 msd ctout 0 fa 00038002,10000005,1e340112
Management server response code 8002 means accept as found in Table 2-83 on page 2-66, followed by information unit request objects. Example 2 is from a v3.x switch Embedded switch fffc0a requests from the embedded switch fffc0b a list of port names for the device with WWN 200000606950efa. The response from fffc0b is accepted. Example: Fabric OS v3.x
22:31:35.366 22:31:35.366 22:31:35.366 22:31:35.366 22:31:35.366 tReceive Rx 3 24 02fffc0a,00fffc0b,028dffff,01000000,10cb3a40 tTransmit Tx 3 0 c0fffc0b,00fffc0a,028d025a, ,10cb3a40 tTransmit ctin 3 fa 00030124,20000060,69500efa tTransmit ctout 3 fa 00038002,00000001,20080060 tSwitch Tx 3 16 03fffc0b,00fffc0a,028d025a,00000001,10cb44d0
Output Line 1:
22:31:35.366 tReceive Rx 3 24 02fffc0a,00fffc0b,028dffff,01000000,10cb3a40
Table 2-90 Arg 1 02fffc0a
Breakdown of Arg Fields in Output (Line 1) Arg 2 00fffc0b 00 = Identifier fffc0b = S_ID Arg 3 028dffff 028d = OX_ID ffff = RX_ID Arg 4 01000000 01000000 = FC-CT IU Preamble; 01 = CT revision Arg 5 10cb3a40 10cb3a40 = IU address pointer
02 = RC_CTL (request) fffc0a = D_ID
Output Line 2:
22:31:35.366 tTransmit Tx 3 0 c0fffc0b,00fffc0a,028d025a, ,10cb3a40
Table 2-91 Arg 1 c0fffc0b
Breakdown of Arg Fields in Output (Line 2) Arg 2 00fffc0a 00 = Identifier fffc0a = S_ID Arg 3 028d025a 028d = OX_ID 025a = RX_ID Arg 4 Null Arg 5 10cb3a40 10cb3a40 = IU address pointer
c0 = RC_CTL(Link Control acknowledge) fffc0b = D_ID

2-81
Output Line 3:
22:31:35.366 tTransmit ctin 3 fa 00030124,20000060,69500efa
0124 = CT-Management Server Code. Get a list of port names for this port WWN 200000606950efa as found in Management Server Command Code on page 71.
Output Line 4:
22:31:35.366 tTransmit ctout 3 fa 00038002,00000001,20080060
8002 =
CT-Management Server code. 8002 = accept as found in FC-CT Response Commands on page 62.
Output Line 5:
22:31:35.366 tSwitch Tx 3 16 03fffc0b,00fffc0a,028d025a,00000001,10cb44d0
Table 2-92 Arg 1 03fffc0b
Breakdown of Arg Fields in Output (Line 5) Arg 2 00fffc0a 00 = Identifier

00fffc0a = S_ID
Arg 3 028d025a
028d = OX_ID 025a = RX_ID
Arg 4 00000001 00000001 = response object
Arg 5 10cb44d0
10cb44d0 =
03 = RC_CTL (reply)
fffc0b = D_ID
IU address pointer
2.11.6. Fabric Zone Server (ZS)

Fabric Zone Server functions (including: additions, removals, 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 shall be 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 are based on Section 6.3 (Fabric Zone Server) of FC-GS4 rev 7.1, dated September 19, 2001. Brocade SilkWorm switches support only those codes that are compatible with Brocade Zoning.
2.11.7. Alias Service Request Code (FC_GS-1)

Table 2-93 Code 0 0 1 2 3 4 11 12 19
2-82
Alias Service Request Code (FC_GS-1) Abbreviation ASRV_OK ASRV_ACC ASRV_REJ ASRV_NOBUF ASRV_INVALID ASRV_BADPTR ASRV_DB_ENTRY_EXIST ASRV_DB_NOENTRY ASRV_DB_CORRUPTED Description Alias Service OK. Alias Service Accepted Alias Service. Refer to FS_RJT reason code explanation Alias Service no buffer Alias Service - Invalid parameter Alias Service - bad pointer Related to database Alias Service - No entry. Alias Service - This is a critical message.
2.12. Link Control Frames

Link Control frames are used to indicate successful or unsuccessful delivery of data frames, to control the flow of data frames, and to provide some low-level N_port commands.
2.12.1. Link Control Headers

2.12.1.1. ACK Frame
ACK_1, one data frame in a sequence (RCTL = C0)
Word 0 1 2 3 4 5 ACK Frame Bits 31-24 Bits 23-16 C0 CS_CTL Type =00 SEQ_ID DF_CTL=00 OX_ID 0000(Reserved) History bit (see note) Bits 15-8 Bits 7-0 D_ID S_ID F_CTL SEQ_DNT RX_ID Number of frames being acknowledge
H E A D E R
Note:
When bit 16 (history bit) is set to 0, it indicates all previous ACKs of that sequence have been sent.When bit 16 (history bit) is set to 1, it indicates at least one previous ACK has not been sent.
2.12.1.2. F_BSY Frame

Fabric Busy (F_BSY) Frame (RCTL = C5 or C6)
Fabric Busy (F_BSY) Frame

H E A D E R Word 0 1 2 3 4 5 Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 C5 or C6 D_ID CS_CTL S_ID Reason Code F_CTL SEQ_ID DF_CTL SEQ_DNT OX_ID RX_ID Parameter fields
2.12.1.3. F_RJT and N_RJT Frames

Refer to Table 2-60 on page 2-54 for reject reason information. When Action Code is set to 0x01, it indicates the sequence is terminated. When it is set to 0x02, it means the sequence is still alive.
Word 0 1 2 3 4 Bits 31-24 C5 or C6 CS_CTL Type SEQ_ID OX_ID Bits 23-16 Bits 15-8 Bits 7-0 D_ID S_ID F_CTL SEQ_DNT RX_ID
H E A D E R
DF_CTL
2-83
2.12.2. Link Control Frames

2.12.2.1. P_BSY UI Frame
(RCTL = C4)
Bits 15-8 Bits 7-0 D_ID S_ID F_CTL DF_CTL SEQ_DNT OX_ID RX_ID Action Code Reason Code 0x00 Vendor (Reserved) When Action Code is set to 0x01 it indicates the sequence terminated. When it set to 0x02 if means the sequence is still alive. H E A D E R Word 0 1 2 3 4 5 Bits 31-24 C4 CS_CTL Type SEQ_ID Bits 23-16
2.12.2.2. No Operation Frame (NOP)

H E A D E R Word 0 1 2 3 4 5 Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 80 D_ID CS_CTL=00 S_ID Type =00 F_CTL SEQ_ID DF_CTL=00 SEQ_DNT OX_ID RX_ID Parameter
2.12.2.3. Abort Sequence Frame (ABTS)

H E A D E R Word 0 1 2 3 4 5 Bits 31-24 Bits 23-16 81 CS_CTL=00 Type =00 SEQ_ID DF_CTL=00 OX_ID Parameter Bits 15-8 Bits 7-0 D_ID S_ID F_CTL SEQ_DNT RX_ID
2.12.2.4. Basic Accept Frame for ABTS

H E A D E R Word 0 1 2 3 4 5 6 7 8 Bits 31-24 Bits 23-16 84 CS_CTL=00 Type =00 SEQ_ID DF_CTL=00 OX_ID Parameter Set_ID valid Last SEQ_ID (80=valid, 00=not) OX_ID Aborted Low SEQ_CNT Bits 15-8 Bits 7-0 D_ID S_ID F_CTL SEQ_DNT RX_ID Reserved RX_ID Aborted High SEQ_CNT)
2-84
2.12.2.5. Basic Reject Frame for ABTS

H E A D E R Word 0 1 2 3 4 5 6 Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 85 D_ID CS_CTL=00 S_ID Type =00 F_CTL SEQ_ID DF_CTL=00 SEQ_DNT OX_ID RX_ID Parameter Reserved Reason Explanation Vendor
2.12.3. Link Control Code

2.12.3.1. F_BSY Reason Code
For Frame information, refer to section 2.12.1.2. F_BSY Frame on page 2-83. Table 2-94 R_CTL C5 C6 F_BSY Reason Code F_BSY Reason Code Reason Code 1x 3x 10 11 12 13 17 18 19 30 31 32 33 37 38 39 Others Meanings The Fabric is busy The destination N_Port is busy with a Class-1 connection The Fabric is busy; ACK_1 is not retransmitted The Fabric is busy; ACK_N or ACK_0 is not retransmitted The Fabric is busy; N_Port is rejecting. The Fabric is busy; Fabric is rejecting. The Fabric is busy; Link Credit Reset. The Fabric is busy; Notify. The Fabric is busy; End. ACK_1 is not retransmitted. ACK_0 or ACK_N is not retransmitted. N_Port is rejecting; the destination N_Port is engaged in a Class-1 connection. Fabric is rejecting; the destination N_Port is engaged in a Class-1 connection. Link Credit Reset; the destination N_Port is engaged in a Class-1 connection. Notify; the destination N_Port is engaged in a Class-1 connection. End; the destination N_Port is engaged in a Class-1 connection. Reserved
2.12.3.2. P_BSY Action and Reason Codes

Action code 01 or 02 P_BSY Action and Reason Codes Reason Code Meanings 01 Physical N_Port is busy 03 A required resource is busy 07 Partial Multicast busy FF Vendor Unique is busy
2-85
2.12.3.3. F_RJT and N_RJT Action and Reason Codes

Refer to section 2.12.1.3. F_RJT and N_RJT Frames on page 2-83 for Frame information.
Action code F_RJT and N_RJT Action and Reason Codes Reason Code Meanings 01 Invalid D_ID 02 Invalid S_ID 03 N_Port temporarily not available 04 N_Port permanently not available 05 Class of service not supported 16 Login required 17 Excessive sequences attempted 18 Unable to establish exchange 19 Reserved 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 1A 1B 1C 1D 1E 1F 20 21 22 23 FF Others Invalid R_CTL Invalid F_CTL Invalid OX_ID Invalid RX_ID Invalid SEQ_ID Invalid DF_CTL Invalid SEQ_CNT Invalid Parameter field Exchange error Protocol error Incorrect length Unexpected ACK Class of service not supported by the entity at FFFFFE Fabric path not available Invalid VC_ID Invalid CS_CTL Insufficient Resources Dedicated Simplex not supported Invalid class of services Preemption request rejected Preemption not enabled Multicast error Multicast error terminate Vendor unique Reserved
01
02
2-86
2.12.4. Link Control Abort Sequence (ABTS)

2.12.4.1. Reject Reason for ABTS
Reason Code 01 03 05 07 09 Ff Basic Reject Reason for ABTS Meanings Invalid (R_CTL) command code Logical error; service requested was invalid or inconsistent. Logical Busy; unable to process service Protocol Error; other FC-2 error Unable to perform a request Vendor Unique error
2.12.4.2. Reject Reason Explanation for ABTS

Basic Reject Reason Explanation for ABTS Reason Code Meanings 00 Invalid (R_CTL) command code 03 Logical error; service requested was invalid or inconsistent. 05 Logical Busy; unable to process service Other value Reserved
2.13. Payload Information

2.13.1. SW_ELS Payload Frames
Refer to section 2.6. Extended Link Service (ELS) on page 2-30 for command information.
2.13.1.1. ELS Acceptance Frame

Word 0 n ELS Acceptance Bits 31-24 Bits 23-16 Bits 15-8 ELS command =02 000000 ELS specific parameters (if present) Bits 7-0
2.13.1.2. ELS Rejection Frame

Word 0 1 Bits 31-24 ELS Command =01 Reserved ELS Rejection Bits 23-16 Reason Code Bits 15-8 000000 Reason Explanation Bits 7-0 Vendor Unique
2-87
2.13.1.3. N_Port Logout Frame

Word 0 1 2-3 Bits 31-24 Command =x05 Reserved N_Port Logout (LOGO) Bits 23-16 Bits 15-8 X00 X00 N_Port Identifier Port_Name of the LOGO originator Bits 7-0 X00
2.13.1.4. PDISC, FDISC,FLOGI, PLOGI

Port Discover (PDISC) x50, Fabric Discover (FDISC) x51, FLOGI = x04, N_Port login (PLOGI) x03 Word Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 0 Command X00 X00 X00 =x03,04,50,51 1-4 Common Service Parameters 5-6 N_Port Name 7-8 Node Name 9-12 Class-1 Service Parameters 13-17 Class-2 Service Parameters 18-21 Class-3 Service Parameters 22-25 Class-4 Service Parameters 26-29 Vendor Version Level 30-31 Service Availability Reserved Note - The Fabric Discover link service (FDISC) allows an N_Port to exchange service parameters with the Fabric without affecting the operating parameters between the N_Port and the Fabric.
2.13.1.5. ADISC Frame

Word 0 1 2-3 4-5 6 Bits 31-24 Command =x52 Reserved Discover Address (ADISC) Bits 23-16 Bits 15-8 X00 X00 Hard address of originator Port_Name of originator Node_name of originator N_Port ID of originator Bits 7-0 X00
Reserved
2.13.1.6. PRLI and PRLO Frames

Word 0 1-n PRLI and Process Logout (PRLO),x21 Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 Command Page Payload length =x20, x21 length=x10 Service Parameter Page
2-88
2.13.1.7. SCN Frame

State Change Notification (SCN) Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 ELS Command Page Payload length =x60 Length=x04 1-n Affected N_Port ID Pages Page Length: The length in bytes of an Affected N_Port ID page. This value is fixed at hex 04. Payload Length: The length in bytes of the entire payload, inclusive of the word 0. This value shall be a multiple of 4. The minimum value of this field is 4. The maximum value of this field is 256. Affected N_Port ID page: Each Affected N_Port ID page contains the ID of an Affected N_Port or NL_Port. The RSCN payload may contain zero or more of these pages. Word 0
2.13.1.8. SCR Frame

Word 0 1 State Change Registration (SCR) Bits 31-24 Bits 23-16 Bits 15-8 X00 X00 ELS Command =x62 Reserved Bits 7-0 X00 Registration Function
Function Value 0 = Reserved 1 = (Fabric Detected registration) - Register to receive all RSCN requests issued by the Fabric Controller for events detected by the fabric. 2 = (N_Port Detected registration) - Register to receive all RSCN requests issued by the Fabric Controller for events detected by the Affected N_Port or NL_Port. 3 = (Full registration) - Register to receive all RSCN requests issued by the Fabric Controller. The RSCN request shall return all Affected N_Port ID pages. 4 = Reserved 4 254 (Clear registration) - Remove any current RSCN registrations. 255
2.13.1.9. RSCN Frame

Registration State Change Notification Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 ELS Command Page Length Payload Length =x61 n Affected N_Port ID Pages (4 bytes each) Page Length: The length in bytes of an Affected N_Port ID page. This value is fixed at hex 04. Payload Length: The length in bytes of the entire payload, inclusive of the word 0. This value shall be a multiple of 4. The minimum value of this field is 4. The maximum value of this field is 256. Affected N_Port ID page: Each Affected N_Port ID page contains the ID of an Affected N_Port or NL_Port. The RSCN payload may contain zero or more of these pages. Word 0
2.13.1.10. LISM Frame

Word 0 1-2 Bits 31-24 LISM Frame Bits 23-16 Bits 15-8 Command code = 11010000 Port_Name Bits 7-0
2-89
2.13.1.11. LIFA, LIPA, LIHA, and LISA Frames

Word 0 1 2-4 Payload format for LIFA, LIPA, LIHA and LISA Frame Bits 31-24 Bits 23-16 Bits 15-8 Command code = 110[2-5]0000 L Bit Map of AL_PAs Bit Map of AL_PAs (continued) Bits 7-0
2.13.1.12. FAN Frame

FAN Frame Word Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 0 Command =x60000000 1 L Loop Fabric Address 2-3 Fabric Port_Name 4-5 Fabric_Name Fabric Address Notification (FAN) is sent by the FL_Port using an S_ID of xFFFFFE to each NL_Port currently logged in to that FL_Port. The purpose of FAN was to allow the FL_Port to provide information to all logged-in NL_Ports on an arbitrated loop following loop initialization.
2.13.1.13. LIRP and LILP Frames

Word 0 1 2-26 LIRP and LILP Frames Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 Loop Initialization Code (0x11060000-0x11070000) Count (Total 1st AL_PA 2nd AL_PA continueAL_PA count in (Masters ALPA) list AL_PAs list) List of AL_PA (Note - FF means AL_PA is not present.)
2.13.2. SW_ILS Payload Frames

Refer to section 2.7. Switch Fabric Internal Link Services (SW_ILS) on page 2-37 for command information.
2.13.2.1. SW_ILS Acceptance Frame

Word 0 n ELS Acceptance Bits 31-24 Bits 23-16 Bits 15-8 ELS command =02 000000 ELS specific parameters (if present) Bits 7-0
2.13.2.2. SW_ILS Reject Frame

Refer to section 2.7.2. SW_ILS Reject Reason Codes (SW_RJT) on page 2-40 for reject information. Refer to section 2.7.3.4. SW_ILS Reject Example on page 2-44 to view an example.
SW_RJT Bits 23-16 Bits 15-8 SW_ILS Command Codes =01000000 Reason Code Explanation
Word 0 1
Bits 31-24 Reserved
Bits 7-0 Vendor Unique
2-90
2.13.2.3. SW_ILS ELP Request Frame

Word 0 1 2 3 4-5 6-7 8-9 10 11 12 13-17 18 N Bits 31-24 ELP Request Bits 23-16 Bits 15-8 Bits 7-0 SW_ILS Command Codes =10xxxxxx Revision Flags Reserved R_A_TOV E_D_TOV Requester Interconnect Port Name Requester Switch Name Class F Service Parameters 16 Class 1 Interconnect Port Parameters Class 2 Interconnect Port Parameters Class 3 Interconnect Port Parameters Reserved ISL Flow Control Mode Flow Control Parameter Length (N) Flow Control Parameters
2.13.2.4. SW_ILS ELP Accept Frame

Word 6 7 8 9 10-11 12-13 14-17 18 19 20 20-24 25 N ELP Accept Bits 23-16 Bits 15-8 Bits 7-0 SW_ILS Command Codes =02000000 Revision =02 Reserved R_A_TOV E_D_TOV Responder Interconnect Port Name Responder Switch Name Class F Service Parameters 16 Class 1 Interconnect Port Parameters Class 2 Interconnect Port Parameters Class 3 Interconnect Port Parameters Reserved ISL Flow Control Mode Flow Control Parameter Length (N) Flow Control Parameters Bits 31-24
2.13.2.5. SW_ILS EFP Request Frame

Word 0 1 2-3 4-7 N Bits 31-24 Command code =11 EFP Request Payload Bits 23-16 Bits 15-8 Bits 7-0 Record length =10 Payload length Reserved Principal switch priority
Principal Switch Name Domain ID List (see SW_ISL Domain ID list format) Multicast ID List
2-91
2.13.2.6. Domain ID List Format

Item Size (Bytes)
Record_Type
Domain_ID Reserved Reserved Switch_Name for Domain_ID
1 byte 00 = reserved 01 =Domain ID List record 02 = Multicast ID List record all other = reserved 1 2 4 8
2.13.2.7. Multicast ID List Format

Item Size Bytes
Record_Type
Multicast_Group_number Reserved Reserved
1 byte 1 byte 00 = reserved 01 =Domain ID List record 02 = Multicast ID List record all other = reserved 1 2 12
2.13.2.8. DIA Request Frame

Word 0 1-2 3 Bits 31-24 DIA Request Bits 23-16 Bits 15-8 Command code = 12000000 Originating Switch Name Not Meaningful Bits 7-0
2.13.2.9. DIA Accept Frame

Word 0 1-2 3 Bits 31-24 DIA Accept Bits 23-16 Bits 15-8 Command code = 02000000 Responding Switch Name Not Meaningful Bits 7-0
2.13.2.10. RDI Request Frame

Word 0 1-2 3 4 n Bits 31-24 Command code = 13 RDI Request Bits 23-16 Bits 15-8 Bits 7-0 Reserved Payload Length Requesting Switch Name Reserved Requested Domain ID#1 Reserved Requested Domain ID#2 Reserved Requested Domain ID#n
2-92
2.13.2.11. RDI Accept Frame

Word 0 1-2 3 4 n Bits 31-24 Command code = 02 RDI Accept Bits 23-16 Reserved Bits 15-8 Bits 7-0 Payload Length
Requesting Switch Name Reserved Reserved Reserved
Granted Domain ID#1 Granted Domain ID#2 Granted Domain ID#n
2.13.2.12. BF (Build Fabric) Frame

BF Request Word Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 0 17 00 00 00 For use in Fabric Configuration, the S_ID field shall be set to hexFFFFFD, indicating the Fabric Controller of the originating Switch. The D_ID field shall be set to hexFFFFFD, indicating the Fabric Controller of the destination Switch.
2.13.2.13. RCF Frame

RCF Request Word Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 0 18 00 00 00 For use in Fabric configuration, the S_ID field shall be set to hexFFFFFD, indicating the Fabric controller of the originating switch. The D_ID field shall be set to hexFFFFFD, indicating the Fabric controller of the destination switch.
2.13.2.14. FSPF Header Format

Word 0 1 2 3-4 Bits 31-24 FSPF version FSPF header Format Bits 23-16 Bits 15-8 Command code AR Number Authentication Type Originating Domain ID Authentication Bits 7-0 Reserved
2-93
2.13.2.15. HLO Request Frame

Word FSPF Header (word 0-4) 5 6 7 8 FSPF HLO Request Frame Bits 23-16 Bits 15-8 Bits 7-0 Command code =14000000 FSPF version AR Number Authentication Reserved =02 =00 Type =00 Originating Domain ID Authentication =00000000 Reserved (option) Hello Interval Dead Interval Reserved Originating Port Index Bits 31-24
2.13.2.16. LSU Request Frame

Word FSPF Header (word 03) 5 6 n Link Status Updated Request Frame Bits 31-24 Bits 23-16 Bits 15-8 Command code =13000000 FSPF version AR Number Authentication =02 =00 Type =00 Originating Domain ID Authentication =00000000 Reserved Number of Link State Records Link State Records Bits 7-0 Reserved
Flags
2.13.2.17. Flags Field Bit Map

Bit Description
0 1
2-7
Data Base Exchange Value b1 - LSU is used for initial database synchronization Value b0 - LSU is used for a topology update Database Complete Value b1 - Last sequence of data base synchronization. LSU contains no LSRs. Value b0 - Not the last sequence of database synchronization Reserved
2.13.2.18. Link State Record Header Format

Word 0 1 2 3 4 5 Bits 31-24 LSR Type Link State Record Header Bits 23-16 Bits 15-8 Bits 7-0 Reserved LSR Age Reserved Link State Identifier Advertising Domain ID Link State Incarnation Number Check Sum LSR Length
2-94
2.13.2.19. Link State Descriptor

Word FSPF Header (Word 03) Link State Recorder Header (Word 49) 10 11-14 15-18 n Link State Descriptor Bits 23-16 Bits 15-8 Bits 7-0 Command code =15000000 FSPF version AR Number Authentication Reserved =02 =00 Type =00 Originating Domain ID Authentication =00000000 LSR Type =01 Reserved LSR Age Reserved Link State Identifier Advertising Domain ID Link State Incarnation Number Check sum LSR Length Reserved Number of Links Link Descriptor #1 Link Descriptor #2 Link Descriptor # n Bits 31-24
2.13.2.20. LSA Request Frame

Word FSPF Header (Word 0-4) 5 6 Link State Header Link State Acknowledged Request Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 Command code =16000000 FSPF version =2 AR Number Authentication Reserved =00 Type =00 Originating Domain ID Authentication Reserved Flags Number of Link State Record Headers LSR Type Reserved LSR Age Reserved Link State Identifier Advertising Domain ID Link State Incarnation Number Check Sum LSR Length
2-95
2.13.3. FC-CT Payload Frames

Refer to section 2.10. Fibre Channel Common Transport Protocol (FC-CT) on page 2-57 for Frame-related information.
2.13.3.1. FC-CT Payload Diagram

Word H E A D E R 6 Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 R_CTL =02 or 03 D_ID CS_CTL=00 S_ID Type =20 F_CTL SEQ_ID DF_CTL SEQ_DNT OX_ID RX_ID Parameter FC-CT Header Usage
2.13.3.2. FC-CT Header Usage

Word 0-3 4-25
Note:
Bits 31-24
Bits 23-16 Bits 15-8 Basic CT_IU preamble Extended CT_IU preamble
Bits 7-0
This reference only covers the Basic CT-IU Preamble.
2.13.3.3. Basic CT_IU Preamble

Word 0 1 2 3 Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT) GS_TYPE GS_Subtype Options Reserved Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation
2.13.3.3.1 CT-IU Request

GA_NXT (0100), GPN_ID (0112), GNN_ID (0113),GCS_ID (0114), GFT_ID (0117), GSPN_ID (0118), GPT_ID (011A), GIPP_ID (011B), GFPN_ID (11C), GHA_ID (011D), GFF_ID (011F)
Word 0 1 2 3 4
Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT.) GS_TYPE GS_Subtype Options Reserved Request/Response Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation Reserved Port Identifier
2-96
2.13.3.3.2 Get Identifier - GID-A (0101)

Word 0 1 2 3 4 Get Identifier {GID-A (0101) } Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT.) GS_TYPE GS_Subtype Options Reserved Request/Response Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation Reserved Domain_ID Reserved scope
2.13.3.3.3 GFD_ID (011E)

Word 0 1 2 3 4 5-12 Get FC-4 Descriptors, 011E Frame Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT.) GS_TYPE GS_Subtype Options Reserved Request/Response Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation Reserved Port Identifier FC-4 Types (32 bytes)
2.13.3.3.4 Get IP Address - GIPP_PN (012B)

Word 0 1 2 3 4 Get IP Address (Port), 012B Frame Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT.) GS_TYPE GS_Subtype Options Reserved Request/Response Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation Port Name
2.13.3.3.5 GID_NN (0131)

Word 0 1 2 3 4 Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT.) GS_TYPE GS_Subtype Options Reserved Request/Response Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation Node Name
2-97
2.13.3.3.6 Get FC4- Type Node Name - GNN_FT (0173)

Word 0 1 2 3 4 Get FC4-Type Node Name, 0173 Frame Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT) GS_TYPE GS_Subtype Options Reserved Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation Reserved Domain ID scope Area_ID scope FC-4 Type Code
2.13.3.3.7 GID_PT (01A1)

Word 0 1 2 3 4 Get Port Identifiers, 01A1 Frame Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT) GS_TYPE GS_Subtype Options Reserved Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation Port Type Domain ID scope Area_ID scope Reserved
2.13.3.4. CT_IU Response

2.13.3.4.1 GA_NXT (0100)
Accept All CT-IU request, 0100 Frame Item Size (Bytes) CT_IU preamble 16 Port Type 1 Port Identifier 3 Port Name 8 Length of Symbolic Port Name (m) 1 Symbolic Port Name m Reserved 255-m Node Name 8 Length of Symbolic Node Name (n) 1 Symbolic Node Name n Reserved 255-n Initial Process Associator 8 IP Address (Node) 16 Class of Service 4 FC4 TYPEs 32 IP Address (Port) 16 Fabric Port Name 8 Reserved 1 Hard Address 3
2-98
2.13.3.4.2 GID_A (0101)

Word 0 1 2 3 4 5 n Accept Domain_ID Scope is zero, 0101 Frame Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT) GS_TYPE GS_Subtype Options Reserved Request/Response Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation Control Domain ID#1 Reserved Control Domain ID#2 Reserved Control Domain ID#n Reserved Accept Domain_ID Scope is non-zero, 0101 Frame Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT) GS_TYPE GS_Subtype Options Reserved Request/Response Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation Control Request Domain Reserved ID#1 Control Request Domain Reserved ID#2 Control Request Domain Reserved D#n
Word 0 1 2 3 4 5 n
2.13.3.4.3 GPN_ID (0112)

Word 0 1 2 3 4 Accept Port Name, 0110 Frame Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT.) GS_TYPE GS_Subtype Options Reserved Request/Response Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation Port Name
2.13.3.4.4 GNN-ID (0113)

Word 0 1 2 3 4 Accept Node Name, 0113 Frame Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT.) GS_TYPE GS_Subtype Options Reserved Request/Response Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation Node Name
2-99
2.13.3.4.5 GCS-ID (0114)

Word 0 1 2 3 4 Accept Class of Service, 0114 Frame Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT.) GS_TYPE GS_Subtype Options Reserved Request/Response Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation Class of Service
2.13.3.4.6 GFT-ID (0117)

Word 0 1 2 3 4-11 Accept FC-4 Type, 0117 Frame Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT.) GS_TYPE GS_Subtype Options Reserved Request/Response Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation FC4-type (32 bytes)
2.13.3.4.7 GSPN_ID (0118)

Word 0 1 2 3 m n Accept Symbolic Port Name, 0118 Frame Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT.) GS_TYPE GS_Subtype Options Reserved Request/Response Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation Name Length (m) Symbolic Port Name Reserved (255 bytes +m)
2.13.3.4.8 GPT_ID (011A)

Word 0 1 2 3 4 Accept Port Type, 011A Frame Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT.) GS_TYPE GS_Subtype Options Reserved Request/Response Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation Port Type Reserved
2.13.3.4.9 GIPP_ID (011A)

Word 0 1 2 3 4-7
2-100
Accept IP Address (Port), 011B Frame Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT.) GS_TYPE GS_Subtype Options Reserved Request/Response Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation IP Address Port
2.13.3.4.10 GFPN_ID (011C)

Word 0 1 2 3 4-5 Accept Fabric Port Name, 011C Frame Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT.) GS_TYPE GS_Subtype Options Reserved Request/Response Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation Fabric Port Name
2.13.3.4.11 GHA_ID (011D)

Word 0 1 2 3 4 Accept Hard Address, 011D Frame Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT.) GS_TYPE GS_Subtype Options Reserved Request/Response Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation Reserved Hard Address
2.13.3.4.12 GNN_FD (0173)

Word 0 1 2 3 4 5 6-7 Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT) GS_TYPE GS_Subtype Options Reserved Command Code =0173 Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation Control Port Identifier#1 Reserved Node Name #1
2.13.3.4.13 GFD_ID (011E)

Accept FC-4 Descriptor, 011E FRame Item Size(Bytes) CT_IU preamble 16 (see p.85) Descriptor length (m) #1 1 FC-4 Descriptor #1 m Reserved 255-m ... .. Descriptor length (m) #n 1 FC-4 Descriptor #n m Reserved 255-m
2-101
2.13.3.4.14 GFF_ID (011F)

Word 0 1 2 3 4-35 Accept FC-4 Feature,011F Frame Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT.) GS_TYPE GS_Subtype Options Reserved Request/Response Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation FC-4 Features (128bytes)
2.13.3.4.15 GID_ID (0121)

Word 0 1 2 3 4 Accept Port Identifiers,0121 Frame Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT.) GS_TYPE GS_Subtype Options Reserved Request/Response Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation Reserved Port Identifiers
2.13.3.4.16 GIPP_ID (012B)

Word 0 1 2 3 4-7 Accept IP Address (Port) ,012B Frame Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT.) GS_TYPE GS_Subtype Options Reserved Request/Response Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation IP Address (Port)
2.13.3.4.17 GID_PT (01A1)

Word 0 1 2 3 4 Accept Port Identifiers, 01A1 Frame Bits 31-24 Bits 23-16 Bits 15-8 Bits 7-0 FC_CT Rev =01 IN_ID (S to zero by the Requesting_CT) GS_TYPE GS_Subtype Options Reserved Command Code Maximum/Residual Size Reserved Reason Code Reason Code Vendor Unique Explanation Control rrrr Control #n Port Identifier #1 Port Identifier #n
2-102
2.14. Fibre Channel Protocol Information

The Fibre Channel Standards Information refers to the following:
section 2.14.1. Well-Known Ordered Sets on page 2-103. section 2.14.2. Port State Machine Values (pstate) on page 2-105. section 2.14.3. Well-Known Addresses on page 2-106. section 2.14.4. Valid AL_PA Addresses on page 2-107.
2.14.1. 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.
2.14.1.1. Types of Ordered Sets:

There are two types of Ordered Sets:
Point-to-Point Link. Arbitrated Loop. Refer to section 2.14.1.4. Arbitrated Loop - Primitive Signals on page 2-104 and section 2.14.1.5. Arbitrated Loop - Primitive Sequence on page 2-105.
2.14.1.2. Point-to-Point Link - Primitive Signals

The following point-to-point link primitive signals indicate switch events:
Table 2-95
Point-to-Point Link - Primitive Signals

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

The following point-to-point link primitive signals indicate port states.
Table 2-96
Point-to-Point Link - Primitive Sequences

Definition Ordered Set
Primitive Sequence
Not_Operational (NOS)
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
K28.5 D21.2 D31.5 D5.2
Offline (OLS)
The FC_Port transmitting the Sequence is:
K28.5 D21.1 D10.4 D21.2

Link_Reset (LR)
initiating the Link Initialization Protocol receiving and recognizing NOS and entering the Offline State K28.5 D9.2 D31.5 D9.2 K28.5 D21.1 D31.5 D9.2
Transmitted by an FC_Port to initiate the Link Reset Protocol, or to recover from a Link Timeout.
Link_Reset_Response (LRR) Transmitted by an FC_Port to indicate that it is receiving and recognizes the LR Primitive Sequence.
2.14.1.4. Arbitrated Loop - Primitive Signals

Table 2-97
Arbitrated Loop - Primitive Signals

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

Table 2-98
Arbitrated Loop - Primitive Sequence

Primitive Sequence Ordered Set
Abbreviation
LIP(F7,F7) LIP(F8,F7) LIP(F7,x) LIPyx LIPfx LIPba LPByx LPBfx LPEyx LPEfx
Loop Initialization--F7, F7 Loop Initialization--F8, F7 Loop Initialization--F7, x Loop Initialization--reset Loop Initialization--reset all Loop Initialization--reserved Loop Port Bypass Loop Port Bypass all Loop Port Enable Loop Port Enable all
K28.5 D21.0 D23.7 D23.7 K28.5 D21.0 D24.7 D23.7 K28.5 D21.0 D23.7 AL_PS K28.5 D21.0 AL_PD AL_PS K28.5 D21.0 D31.7 AL_PS K28.5 D21.0 b a K28.5 D9.0 AL_PD AL_PS K28.5 D9.0 D31.7 AL_PS K28.5 D5.0 AL_PD AL_PS K28.5 D5.0 D31.7 AL_PS
2.14.2. Port State Machine Values (pstate)

Table 2-99
Port State Machine Values
State Machine Values
AC IDLE
Active state Idle Link Reset: LR transmit state Link Reset: LR receive state Link Reset: LRR receive state Link Failure: NOS transmit state Link Failure: NOS receive state Offline: OLS transmit state Offline: OLS receive state Offline: wait for OLS state Not Operational
LR1 LR2 LR3 LF1 LF2
OL1 OL2 OL3
NOS
2-105
2.14.3. 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 2-100 Well-Known Addresses Well-Known Address Description
0xFFFFFF 0xFFFFFE
BROADCAST - frames transmitted to this address are broadcast to all operational N_Ports. 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. FABRIC_CONTROLLER - This address is responsible for managing the Fabric. It initializes the Fabric, and routes frames to the well-known address. 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. TIME_SERVER - is an optional service that facilitates the maintenance of system time between ports. MANAGEMENT_SERVER - this is an optional service used to collect and report management information such as a link usage, error statistics, and link quality. Quality of Service Facilitator (QoSF) for Class-4 Bandwidth and Latency Management (FC_PH2). ALIAS_SERVER - is an optional service to manage the assignment of alias address identifiers. Security-Key Distribution Service - is an optional service to manage the distribution of encryption security keys to facilitate secure communications between N_Ports. Clock Synchronization Server (FC-PH3) MULTICAST SERVER (FC-PH3) - is 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. Reserved
0xFFFFFD 0xFFFFFC
0xFFFFFB 0xFFFFFA 0xFFFFF9 0xFFFFF8 0xFFFFF7 0xFFFFF6 0xFFFFF5
0xFFFFF4 - 0xFFFFF0
S_ID and D_ID Assignments 0xFFFBxx 0xFFFCxx Multicast (group in lower byte) Embedded_Port (domain in lower byte)
2-106
2.14.4. Valid AL_PA Addresses

Arbitrated Loop Physical Address (AL_PA) and Loop IDs are listed in Table 2-101. 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 preserved the running disparity on the link, and AL_PA values are restricted to those characters that result in neutral disparity after encoding.
Table 2-101 Valid AL_PA Addresses Word 0 Bit AL_PA Word 2 Bit AL_PA Word 3 Bit AL_PA Word 4 Bit AL_PA
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
L_bit 00 01 02 04 08 0F 10 17 18 1B 1D 1E 1F 23 25 26 27 29 2A 2B 2C 2D 2E 31 32 33 34 35 36 39 3A
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
3C 43 45 46 47 49 4A 4B 4C 4D 4E 51 52 53 54 55 56 59 5A 5C 63 65 66 67 69 6A 6B 6C 6D 6E 71 72
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
73 74 75 76 79 7A 7C 80 81 82 84 88 8F 90 97 98 9B 9D 9E 9F A3 A5 A6 A7 A9 AA AB AC AD AE B1 B2
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
B3 B4 B5 B6 B9 BA BC C3 C5 C6 C7 C9 CA CB CC CD CE D1 D2 D3 D4 D5 D6 D9 DA DC E0 E1 E2 E4 E8 EF
2-107
2-108

447-01 Port Log Dump Reference

Uploaded by

Copyright:

Available Formats

You might also like

447-01 Port Log Dump Reference

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

447-01 Port Log Dump Reference

Uploaded by

Copyright:

Available Formats

Brocade PortlogDump Reference Guide

Publication Number: 53-0000447-01 Publication Date: May 5, 2004

Brocade Communications Systems, Incorporated

Preface Chapter 1 Understanding the Port Log Dump

Troubleshooting Using the Port Logs

Brocade PortlogDump Reference Guide

Brocade PortlogDump Reference Guide

Brocade PortlogDump Reference Guide

Brocade PortlogDump Reference Guide

Brocade PortlogDump Reference Guide

Brocade PortlogDump Reference Guide

Brocade PortlogDump Reference Guide

Brocade PortlogDump Reference Guide

Brocade PortlogDump Reference Guide

Notes and Guidelines

Warnings alert you to potential damage to hardware, firmware, software, or data.

Brocade PortlogDump Reference Guide

Understanding the Port Log Dump

1.1. Reading Portlogdump Output

Brocade PortlogDump Reference Guide

Understanding the Port Log Dump

Example: Cmd: The commands associated with each event category.

Brocade PortlogDump Reference Guide

Understanding the Port Log Dump

1.2. Variations in Portlogdump Output by Fabric OS Version

Fabric OS Version v2.x or older

Example of Fabric OS v4.x

Brocade PortlogDump Reference Guide

Understanding the Port Log Dump

1.3. Using and Customizing the portlogdump

1.3.1. Portlogdump Related Commands

portlogshow [count, saved, portid] portlogclear portlogeventshow

portlogtypedisable type portlogtypeenable type

Brocade PortlogDump Reference Guide

Understanding the Port Log Dump

1.3.2. Displaying and Customizing the Portlogdump Output

Enter one of the following commands:

Brocade PortlogDump Reference Guide

Understanding the Port Log Dump

Brocade PortlogDump Reference Guide

Understanding the Port Log Dump

1.4. Locating Information by Task

enable ioctl pstate

Port # Port # Port #

1 = enable 2 = disable IOCTL code Port State Machine

IU pointer, 0 IU pointer, 0 N/A

Size of payload in bytes

Brocade PortlogDump Reference Guide

Brocade PortlogDump Reference Guide

ioctl tFCPH loopscn

IOCTL code Loopscan code

Brocade PortlogDump Reference Guide

scn sn tLOOP loopscn

Port # Port # Port #

scn code Speed negotiation keys and definitions Loop code

Brocade PortlogDump Reference Guide

FC_CT response code Word 0, Word 1, nameserver port type, IU pointer

Fabric Internal FC-CT command

Word 0, Word 1, nameserver port type, IU pointer