Support Show Command Ref SSCRG

The Official SupportShow Command Reference Guide
Version 1.0
Publication Number: 53-0000448-01 Publication Date: January 10, 2004
Copyright 2004, Brocade Communications Systems, Incorporated. ALL RIGHTS RESERVED. Publication Number: 53-0000448-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 Asia-Pacific Headquarters 9/F, One International Finance Center, 1 Harbour View Street, Central, Hong Kong Tel: +852 2539 0600 Fax: +852 2539 0613 Email: apac-info@brocade.com European Headquarters 29, route de lAeroport Case Postale 105 CH-1211 Geneva 15, Switzerland T: +41 22 799 56 40 F: +41 22 799 56 41 Email: europe-info@brocade.com Latin America Headquarters 5201 Blue Lagoon Drive Miami, FL 33126 T: (305) 716-4165 Email: latinam-sales@brocade.com
Document History
The table below lists all versions of the Supportshow Reference Guide. Document version Preliminary Publication Publication Number Publication Date 53-0000448-01 2/6/2004
Table of Contents
Preface
Audience 1 Guideline Conventions 1 Formatting 1 Notes and Guidelines 2
Chapter 1
SupportShow Operands
1-1 1-1 1-2 1-2 1-4 1-9
1.1. Operands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.1. Operands v3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.2. Operands v4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2. Fabric OS v3.0.x and 4.0.x SupportShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3. Fabric OS v3.1.0 and 4.1.0 SupportShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4. Fabric OS v3.1.2 and 4.2.x SupportShow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2
Fabric OS SupportShow Information
agtcfgshow 2 arpshow 4 bloomdatashow 5 bloomfdetShow 7 bloomlistdisplay 8 bloomsemsshow 9 bloomramdump 10 cfgShow 11 cfgsize 13 ChassisShow 15 configShow 20 Date 38 dbgshow 39 diagShow 42 ErrDump 45 Fablogdump 49 Fabportshow 50 fabricShow 54 fabstateShow 56
Brocade Fabric Watch Guidelines
fabstatsshow 60 fabswitchShow 64 FanShow 67 faShow 68 fastcheckheap 69 faultshow 70 fcplogshow 74 fdmicacheshow 76 fdmishow 77 feiDumpPrint 78 feiIterateRFDRings 79 Ficondbg log 80 Ficonshow ilir 82 Ficonshow lirr 83 Ficonshow rlir 84 Ficonshow rnid 86 Ficonshow switchrnid 88 Filterportshow 89 Filtershow 91 firmwareShow 96 FspfShow 98 Fssadmin -s chassis0 -q 101 Fssadmin -s fcsw0 -q 102 Fssadmin -s fcsw1 -q 105 fwalarmsfiltershow 107 fwsamshow 108 hadump 110 haShow 125 HistoryShow 126 hostShow 128 i 129 i557Dump 131 ifshow 134 inetStatShow 135 ipaddrshow 136 ipstatshow 138 islshow 139 licenseShow 140 mallocshow 141 mbufShow 142 medbg -s1 -e1 143 memshow 144 mii-tool vv Link information 145 mqshow 147 myid 149
ii
nsAllShow 150 nscamshow 151 nsShow 154 Persistent portlogdump 157 portcamshow 158 portcfgshow 163 portErrShow 166 Portflagsshow 169 portLogDump 171 portloginshow 172 PortRegshow 174 portRouteShow 177 portSemShow 179 portShow 181 portstatsshow 185 portstructshow 186 PortswapShow 188 PortzoneShow 189 Printing Proc entries 190 ps_dump 201 ps_dump -a -n port# 202 psShow 203 Ptbufshow 204 Ptcreditshow 205 ptdatashow 206 ptphantomshow 209 ptpropshow 211 ptstatsshow 212 qlShow 214 rcsinfoshow 216 rcsregistryshow 217 rcssmshow 218 routeShow 223 routestatShow 224 secFabricShow 225 secmodeshow 226 secpolicydump 227 secStatsShow 228 semaShow 230 sensorshow 231 sfpshow 232 SlotShow 236 supportshowcfgshow 238 switchShow 239 switchstatuspolicyshow 245
iii
switchstatusshow 247 sysc_dprintf 248 tcpstatshow 249 tempShow 250 timeout 251 topologyShow 252 traceshow 255 TrunkShow 257 udpstatshow 259 uptime 260 Version 262 zone stateshow & portzoneshow 264 /bin/cat/etc/fstab (Phy File Mount Points) 268 /bin/cat/etc/mtab (Current Mount Points) 269 /bin/cat/var/log/dsmg (Serial Boot or MSG File) 270 /bin/df File Systems Available 271 /bin/hostname 274 /bin/ps -elfH (Process List) 275 /bin/rpm qa 277 /sbin/bootenv 280 /sbin/ifconfig 281 /sbin/route 283 /sbin/sin 284 /usr/bin/du xh / | /bin/sort 285
Chapter 3
Non-SupportShow Commands
AgtcfgSet 2 configure 3 Ficonshow 7 FirmwareCommit 14 Firmwaredownload 15 Firmwaredownloadstatus 16 Firmwarerestore 22 fwconfigure 23 fwfrucfg 28 ifModeShow/Set 31 ifshow 32 ipAddrSet 33 killTelnet 34 netstat 35 portLogShow 36 powerofflistset 40 savecore 41 snmpmibcapset 44
iv
tcpstatshow 45
vi
Preface
The Brocade SupportShow Reference Guide is focused on covering detailed supportshow information for information gathering and troubleshooting. The Brocade SupportShow Reference Guide is intended to be used in conjunction with existing Brocade manuals, release notes, and related Brocade publications. The Brocade SupportShow Reference Guide is effective at focusing experienced Brocade SAN professionals on a the commands to use to gather pertenant information.
Audience
The Brocade SupportShow 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 SupportShow Reference Guide is an advanced document. 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.
Guideline Conventions
The formatting and conventions used in this document are designed to help the reader locate and comprehend information quickly. In addition to the information provided in standard text, there are Guidelines, Notes, and Cautions to help focus the reader on important information.
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
SAN Migration Guide
Notes and Guidelines

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.
The red circle with a slash through it (shown in Figure 0-1) indicates that a particular action or type of connection is not recommended. While the action or connection may function, there are better ways to perform the action or make the connection.
Figure 0-1
SAN Migration Guide
Chapter
Print detailed switch information for debugging purposes. Table 1-1 SYNTAX v3.0 SYNTAX v4.0 Availability Release Description
supportShow [firstPort, lastPort, nLog] supportShow slotnumber [/port1-port2] [lines]
All users v3.0 and v4.0 Use this command to capture the switch information for debugging purposes.
Note:
The output of this command can be very long.
1.1. Operands
1.1.1. Operands v3.0
SupportShow has the following operands in Fabric OS version 3.x: firstPort Specify the first port of a range of ports to dump information. The default (if no operand specified) is to print state of port 0. If only firstPort is specified, only information for firstPort is printed. This operand is optional for v3.0. Specify the last port of range of ports to dump information. If firstPort is specified but lastPort is not specified, only firstPort information is printed for the port based commands (portShow, portRegShow, portRouteShow). If no operand is supplied, firstPort is set to 0 and lastPort is set to maximum port of switch. This operand is optional for v3.0. Specify the number of lines of portLogDump to print: (This operand is optional.) 0 = dump all lines (default) N = dump the last N lines <0 = skip portLogDump
lastPort
nLog
1-1
1.1.2. Operands v4.0

SupportShow has the following operands in Fabric OS version 4.x: slotnumber Specify the slot number in a Silkworm 12000 switch. The slot number must be followed by a slash ( / ) and the port number. The Silkworm 12000 has a total of 10 slots counted from 1 to 10. Slot number 5 and 6 are control processor cards, and slot 1 through 4 and 7 through 10 are switch cards. On each switch card, there are 16 ports counted from the bottom 0 to 15. A particular port must be represented by both slot number (1 through 4 or 7 through 10), and port number (0 through 15). Specify the first port of a range of ports to display information. Enter the port area number. The default (if no operand specified) is to print state of port 0. If only port1 is specified, only information for port1 is printed. This operand is required for v4.0. Specify the last port of range of ports to display information. Enter the port area number. If port1 is specified but port2 is not specified, only port1 information is printed for the port based commands (portShow, portRegShow, portRouteShow). If no operand is supplied, port1 is set to 0 and port2 is set to maximum port of switch. This operand is required for v4.0. Specify the number of lines output from this command. This operand is optional. A consistent supportShow was captured for each FOS version; these examples (indicated by #x, where x is the order they appear in that versions supportShow output as listed on previous page) were also added to the Brocade FOS Command and/or help <command name> information shared here.
port1
port2
lines Note:
1.2. Fabric OS v3.0.x and 4.0.x SupportShow

This Supportshow is executed in the order as listed by Fabric OS version in Table 1-2 and Table 1-4. Table 1-2 Fabric OS 3.0 and 4.0 Supportshow Command Execution Order Fabric OS Version 4.0.2c
1. fabStateShow 2. fabSwitchShow 3. version 4. uptime 5. tempShow 6. psShow 7. licenseShow 8. errDump a / -p 9. switchShow 10. fspfShow** 11. portFlagsShow 12. portErrShow
Fabric OS Version 3.0.2c

1. version* 2. uptime* 3. tempShow* 4. psShow 5. licenseShow 6. diagShow 7. errDump* 8. switchShow* 9. portFlagsShow 10. portErrShow 11. mqShow 12. portSemShow
1-2
Table 1-2
Fabric OS 3.0 and 4.0 Supportshow Command Execution Order Fabric OS Version 4.0.2c
13. portErrShow 14. trunkShow 15. topologyShow 16. nsShow 17. nsAllShow 18. cfgShow 19. slotShow 20. chassisShow 21. fanShow 22. historyShow 23. /sbin/bootenv (Boot prom parms) 24. /sbin/sin (CP components) 25. /bin/df (file Sys avail.) 26. /sbin/ifconfig (all IP addr.-Eth0 ip of Active CP) 27. sbin/route 28. mii-tool vv (Ethernet type info.)
Fabric OS Version 3.0.2c

13. portShow 14. portRegShow 15. portRouteShow 16. portStructShow 17. bloomDataShow 18. fabricShow 19. trunkShow 20. topologyShow 21. qlShow 22. faShow 23. portCfgShow 24. nsShow 25. nsAllShow 26. nscamShow 27. cfgShow 28. configShow 29. faultShow 30. TraceShow 31. memShow 32. mallocShow 33 FastCheckHeap 34. PortlogDump
29. /usr/bin/du xh / | /bin/sort (Calc dir sizes) 30. /bin/ps elfH (Process List) 31. /bin/rpm qa (Redhat Pkg mgr.exe query all) 32. /bin/cat/var/log/dmsg (serial boot or msg. File) 33. /bin/cat/etc/fstab (phy file - mount points) 34. /bin/cat/etc/mtab (current mount points-file) 35. printing proc entries (all devices and info) 36. configShow 37. portLogDump 38. diagShow 39. portShow (slot#,port#) 40. portRegShow (slot#,port#) 41. portrouteShow (slot#,port#)
1-3
1.3. Fabric OS v3.1.0 and 4.1.0 SupportShow

The V3.1.0/ 4.1.0 supportshow command has been upgraded to display support information by executing groups of pre-selected Fabric OS and LINUX commands. The grouped information displayed by the supportshow command can be controlled by a set of control commands: supportshowcfgshow supportshowcfgenable supportshowcfgdisable Display which groups of commands are enabled to display under supportshow. Enable a group of commands to display under supportshow. Disable a group of commands from displaying under supportshow.
Fabric OS V3.1.0/ 4.1.0 supportshow commands are grouped into logical categories. These logical categories are called groups and are displayed by invoking supportshowcfgshow:
Switch:admin> supportshowcfgshow os enabled exception enabled port enabled fabric enabled services enabled security enabled network enabled portlog enabled system enabled extend disabled filter disabled perfmon disabled
The extend, filter, and performance command groups are disabled by default in both V3.1.0 and V4.1.0 supportshow outputs. Fabric OS V3.1.0 and V4.1.0 supportshow commands use the same operands and syntax as V3.0.2c and V4.0.2c discussed previously. The following examples show the command syntax and display outputs described. Example: SilkWorm 12000 To display all supportshow information, but only specific slot and port information and 10 lines of portLogDump output on slot 2, ports 0 2 of a SilkWorm 12000 invoke supportshow [slotnumber[/port1-port2]] [lines]
Switch12k:admin> supportshow 2/0-2 10
Example: Non - SilkWorm 12000 To display all supportshow information, but only specific port information and 10 lines of portLogDump output on ports 0 2 of any V3.1.SilkWorm switch invoke supportshow [port1-port2], [lines]:
SwitchNon12k:admin> supportshow 0-2, 10
1-4
Table 1-3 Fabric OS v 3.1 v3.1.0Switch:admin> supportshow

Date Version SupportShowCfgShow supportshow groups enabled portlog Command Group portLogDump 0, 0 portLogDump 0, 1 portlog Command Group portLogDump Persistent portlogdump
Fabric OS v 4.1 V4.1.0Switch:admin> supportshow
OS Command Group
mqShow 0 i memShow mallocShow fastCheckHeap
OS Command Group
mii-tool -vv /usr/bin/du -xh / | /bin/sort /bin/cat /var/log/dmesg /bin/cat /etc/fstab` /bin/cat /etc/mtab printing proc entries /proc/cmdline /proc/cpuinfo /proc/devices proc/filesystems /proc/interrupts /proc/meminfo /proc/modules /proc/mounts /proc/mtd /proc/partitions /proc/pci /proc/slabinfo /proc/stat /proc/tty/drivers /proc/uptime /proc/version
Exception Command Group

faultShow traceShow errDump 0
Exception Command Group

errdump -a errdump -p
Port Command Group (for each port)

portShow 0 portRegShow 0 portStructShow 0 bloomDataShow 0 portRouteShow 0 portStatsShow 0
Port Command Group (Repeats for all slots or blades)

diagshow (of slot) portshow 2 0 portloginshow 2 0 portregshow 2 0 portrouteshow 2 0
Note: These next outputs are listed once each, with port info for all ports when it fits:
portSemShow bloomSemShow semaShow 1
1-5
Table 1-3 Fabric OS v 3.1 v3.1.0Switch:admin> supportshow Fabric Command Group

fabricShow islShow trunkShow topologyShow faShow qlShow cfgShow fabStatsShow fabLogDump
Fabric OS v 4.1 V4.1.0Switch:admin> supportshow Fabric Command Group

fabricshow islshow trunkshow topologyshow fabstateshow fabswitchshow fabstatsshow fabportshow (for each slot/port) fspfshow fcplogshow zone stateshow portzoneshow portcamshow cfgsize cfgshow rcssmshow rcsinfoshow rcsregistryshow
Services Command Group

nsShow nsAllShow nscamShow * see note 5 (output change info)
Services Command Group

nsshow nsallshow nscamshow fdmishow fdmicacheshow
Security Command Group

secModeShow
Security Command Group

secModeShow secPolicyDump secStatsShow secFabricShow
Note: Subsequent outputs only displayed if secmode is enabled:

Secpolicydump Secstateshow Secfabricshow
Network Command Group

ipAddrShow ifShow ipstatShow udpstatShow tcpstatShow inetstatshow mbufShow arpShow routeShow routestatShow hostShow feiDumpPrint i557Dump feiIterateRFDRings
Network Command Group

/sbin/bootenv /sbin/sin /bin/df /sbin/ifconfig /sbin/route /bin/hostname
1-6
Table 1-3 Fabric OS v 3.1 v3.1.0Switch:admin> supportshow System Command Group

version uptime switchShow tempShow psShow licenseShow diagShow 0 portFlagsShow portErrShow portCfgShow configShow
Fabric OS v 4.1 V4.1.0Switch:admin> supportshow System Command Group

myid version firmwareshow uptime switchstatusshow switchshow hadump hashow ipaddrshow 4 sysc_ dprintf medbg -s1 -e1 fssadmin -s chassis0 -q fssadmin -s fcsw0 -q fssadmin -s fcsw1 -q /bin/cat /proc/fss/SWBD10.log tempshow sensorshow psshow fanshow licenseshow portflagsshow portcfgshow sfpshow porterrshow fwsamshow agtcfgshow slotshow chassisshow switchstatuspolicyshow fwalarmsfiltershow timeout historyshow configshow
1-7
Table 1-3 Fabric OS v 3.1 v3.1.0Switch:admin> supportshow Fabric OS v 4.1 V4.1.0Switch:admin> supportshow FC port Command Group (Repeats for all slots or blades)
diagshow (of slot) portshow 2 0 portloginshow 2 0 portregshow 2 0 portrouteshow 2 0
Extend Command Group

bloomlistdisplay bloomfdetshow bloomramdump
Extended Command Group

Ptbufshow Ptcreditshow Ptdatashow Ptphantomshow Ptpropshow Ptstatsshow
Filter Command Group

filtershow
Filter Command Group

filterportshow(per-port)
Performance Command Group

ps_dump
Performance Command Group

ps_dump -a -n port#
1-8
1.4. Fabric OS v3.1.2 and 4.2.x SupportShow

Fabric OS v3.1.2 and v4.2 supportshow include command groups that allow you to display supportshow output on an as needed basis, the same as Fabric OS v 3.1.0 and 4.1.0. However, additional commands have been added to the Fabric OS 4.2 Supportshow output. For information about controlling supportshow output, refer to Fabric OS v3.1.0 and 4.1.0 SupportShow on page 1-4. Table 1-4 Fabric OS 3.1.2 and 4.2 Supportshow Command Execution Order Fabric OS 4.2 1. Date 2. Version 3. supportshow groups enabled 4. portLogDump 5. Persistent portLogDump 6. mii-tool -vv 7. /usr/bin/du -xh / | /bin/sort 8. /bin/ps -elfH 9. /bin/rpm -qa 10. /bin/cat /var/log/dmesg 11. /bin/cat /etc/fstab 12. /bin/cat /etc/mtab 13. printing proc entries 14. /proc/cmdline 15. /proc/cpuinfo 16. /proc/devices 17. /proc/filesystems 18. /proc/interrupts 19. /proc/meminfo 20. /proc/modules
Fabric OS 3.1.2 1. 2. 3. 4. 5. 6. 7. 8. 9. Date Version SupportShowCfgShow portLogDump 0, 0 portLogDump 0, 1 mqShow 0 i memShow mallocShow
10. fastCheckHeap 11. faultShow 12. traceShow 13. errDump 0 14. portShow 0 15. portRegShow 0 16. portStructShow 0 17. bloomDataShow 0 18. portRouteShow 0 19. portStatsShow 0 Note: These next outputs are listed once each, with port info for all ports when it fits: a. b. c. portSemShow bloomSemShow semaShow 1
21. /proc/mounts 22. /proc/mtd 23. /proc/partitions 24. /proc/pci 25. /proc/slabinfo 26. /proc/stat 27. /proc/tty/drivers 28. /proc/uptime 29. /proc/version
20. fabricShow 21. islShow 22. trunkShow 23. topologyShow 24. faShow 25. qlShow
1-9
Table 1-4
Fabric OS 3.1.2 and 4.2 Supportshow Command Execution Order Fabric OS 4.2 30. errdump -a 31. errdump -p 32. fabricshow 33. islshow 34. trunkshow 35. topologyshow 36. fabstateshow 37. fabswitchshow 38. fabstatsshow 39. fabportshow 40. fspfshow 41. fcplogshow 42. zone stateshow 43. portzoneshow 44. portcamshow 45. cfgsize 46. cfgshow 47. rcssmshow 48. rcsinfoshow 49. rcsregistryshow 50. nsShow 51. nsallshow 52. nscamShow 53. fdmishow 54. fdmicacheshow 55. ficonshow rnid 56. ficonshow lirr 57. ficonshow rlir 58. ficonshow ilir 59. ficonshow switchrnid 60. ficondbg log 61. secModeShow 62. secPolicyDump 63. secStatsShow 64. secFabricShow 65. /sbin/bootenv
Fabric OS 3.1.2 26. cfgShow 27. fabStatsShow 28. fabLogDump 29. nsShow 30. nsAllShow 31. nscamShow 32. secModeShow Note: subsequent outputs only displayed if secmode is enabled: a. b. c. Secpolicydump Secstateshow Secfabricshow
33. ipAddrShow 34. ifShow 35. ipstatShow 36. udpstatShow 37. tcpstatShow 38. inetstatshow 39. mbufShow 40. arpShow 41. routeShow 42. routestatShow 43. hostShow 44. feiDumpPrint 45. i557Dump 46. feiIterateRFDRings 47. version 48. uptime 49. switchShow 50. tempShow 51. psShow 52. licenseShow 53. diagShow 0 54. portFlagsShow 55. portErrShow 56. portCfgShow 57. configShow
1-10
Table 1-4
Fabric OS 3.1.2 and 4.2 Supportshow Command Execution Order Fabric OS 4.2 66. /sbin/sin 67. /bin/df 68. /sbin/ifconfig 69. /sbin/route 70. /bin/hostname 71. myid 72. firmwareshow 73. dbgshow 74. uptime 75. switchstatusshow 76. switchshow 77. hadump a. haShow b. ipaddrshow c. sysc_dprintf d. medbg -s1 -e1 i. fssadmin -s chassis0 -q ii. fssadmin -s fcsw0 -q iii. fssadmin -s fcsw1 -q 78. tempshow 79. sensorshow 80. psshow 81. fanshow 82. licenseshow 83. portflagsshow 84. portcfgshow 85. sfpshow 86. portErrShow 87. fwsamshow 88. agtcfgShow 89. slotShow 90. chassisShow 91. switchstatuspolicyshow 92. fwalarmsfiltershow 93. timeout 94. historyshow 95. portswapshow
Fabric OS 3.1.2 58. bloomlistdisplay 59. bloomfdetshow 60. bloomramdump 61. filtershow 62. ps_dump
1-11
Table 1-4
Fabric OS 3.1.2 and 4.2 Supportshow Command Execution Order Fabric OS 4.2 96. configshow 97. diagshow 98. portshow 1 0 (per port) 99. portloginshow 1 0 (per port) 100. portrouteshow 1 0 (per port) 101. Ptbufshow 102. Ptcreditshow 103. Ptdatashow 104. Ptphantomshow 105. Ptpropshow 106. Ptstatsshow 107. filterportshow(per-port) 108. ps_dump -a -n port#
Fabric OS 3.1.2
1-12
Chapter
2
This chapter defines the output of SupportShow output for Fabric OS v3.1.2 and v4.2, but also contain information that pertains to v3.0, 3.1, 4.0 and 4.1. Each command used by supportshow is listed in alphabetical order. The commands contain the following information: Available in Fabric OS versions: Version Differences: Troubleshooting Use: Additional Example/Case Studies/Information:
Operands used by each command are not listed in this chapter. For information about operands used by a command please refer to Chapter 1, SupportShow Operands. For a list of non-supportshow commands that relate to troubleshooting commands used in supportshow, refer to Chapter 3, Non-SupportShow Commands. Note: Command Syntax and operands are not provided for the commands listed in this document. For information about syntax and operands for a command, refer to the Brocade Fabric OS Command Reference for the specific version of Fabric OS on your switch.
2-1
agtcfgshow
Available in Fabric OS versions: 4.1, 4.2 Version Differences: This command is a non-supportshow command in all other Fabric OS versions. Troubleshooting Use: Use this command to display the configuration of the SNMP agent in the switch. Check snmpmibcapset output to ensure MIB or TRAP you are attempting to use is enabled. Additional Example/Case Studies/Information: SNMP problems can also be caused by MIB dependencies - there is an order that MIBs/TRAPs need to be loaded to accurately get and set object identifiers (OIDs). MIB Browser TOV values are typically set to 2-3 seconds, most MIBs have no problem with this but SW 5.0 MIBs go into flash thus using access times of up to 4 seconds. If SW 5.0 MIBs are used SNMP browsers need TOVs of at least 5 seconds. TOVs may need to be increased in fabrics with WANs or if additional delays exist in the fabric. On the SilkWorm 12000, there is one SNMP agent per logical switch. This command is specific to the logical switch you are logged into. The following information is displayed: sysDescr sysLocation sysContact swEventTrapLevel The system description. The default value is Fibre Channel Switch. The location of the system. The default value is End User Premise. The contact information for the system. The default value is Field Support. The event trap level in conjunction with the event's severity level. When an event occurs and if its severity level is at or below the set value, the SNMP trap, swEventTrap, is sent to configured trap recipients. By default, this value is set at 0, implying that no swEventTrap is sent. Possible values are:
0 - none 1 - critical 2 - error 3 - warning 4 - informational 5 - debug authTraps The default value is 0 (off). When enabled the authentication trap, authenticationFailure, is transmitted to a configured trap recipient in the event the agent received a protocol message that is not properly authenticated. In the context of SNMPv1 and SNMPv2c, this means that a request contains a community string that is not known to the agent. The default value for this parameter is 0 (disabled). There are six communities and respective trap recipients supported by the agent. The first three communities are for read-write access (rw) and the last three are for read-only access (ro). The default value for the trap recipient of each community is 0.0.0.0. The default values for the community strings are:
Community 1: Secret Code Community 2: OrigEquipMfr Community 3: private Community 4: public Community 5: common Community 6: FibreChannel In order for an SNMP Management Station to receive a trap generated by the agent, the administrator must configure a trap recipient to correspond to the IP address of the Management Station. In addition, the trap recipient must be able to pass the access control list (ACL) check. The ACL check is as follows: There are six ACLs to restrict SNMP get/set/trap operations to hosts under a host-subnet-area. Host-subnet-area is defined by comparing non-zero IP octets. For example, an ACL of '192.168.64.0' enables access by any hosts that start with the specified octets. The connecting host is enabled to set each host-subnet-area to be read-write or read-only. Highest privilege matched out of six entries is given to the access. The ACL check is turned off when all six entries contain '0.0.0.0'.
2-2
Note:
When secure mode is enabled, the Access Control List feature is incorporated into the WSNMP and RSNMP security policies. Community strings can be changed on the primary FCS switch only and will propagate changes across the fabric.
v4.2 Example Output Example 2-1: Display SNMP agent configuration information:
agtcfgshow: sysDescr sysLocation sysContact swEventTrapLevel authTraps = = = = = Fibre Channel Switch. End User Premise Field Support. 0 0 (OFF)
SNMPv1 community and trap recipient configuration: Community 1: Secret C0de (rw) No trap recipient configured yet Community 2: OrigEquipMfr (rw) No trap recipient configured yet Community 3: private (rw) No trap recipient configured yet Community 4: public (ro) No trap recipient configured yet Community 5: common (ro) No trap recipient configured yet Community 6: FibreChannel (ro) No trap recipient configured yet SNMP access list configuration: Entry 0: No access host configured Entry 1: No access host configured Entry 2: No access host configured Entry 3: No access host configured Entry 4: No access host configured Entry 5: No access host configured
yet yet yet yet yet yet
2-3
arpshow
Available in Fabric OS versions: v3.1.0, 3.1.2 v4.2 Example Output: NA Troubleshooting Use: Use this command to view the current Address Resolution Protocol table entries. Example 2-1:
SW3800_12:user> arpshow 10.64.64.1 at 0:0:c:7:ac:47
ARP (Address Resolution Protocol) builds a table that associates an IP address with the MAC address that presents it. You can check your workstations arp table with the command arp a. This works on almost any operating system. An example is provided below. Example:
C:\>arp -a Interface: 192.168.5.100 on Interface 0x1000003 Internet Address Physical Address Type 192.168.5.25 00-60-69-60-03-ba dynamic
Dynamic ARP entries will timeout after about 5 minutes. This timeout value can be adjusted in most operating systems. Entries can be removed from the ARP table with the arp d command. If the management workstation and the switch are on different subnets, the dynamic ARP entry timeout value at the router may need to be verified. Most Switch/routers can be configured to hold dynamic ARP entries for extended periods of time. Many can also be configured for Proxy ARP, which allows a device (switch/router) to respond to ARP broadcasts on behalf of another device. In this scenario a switch/router that has dynamic ARP entries for the SW12000 can respond to the management workstations ARP broadcast. This can cause problems after a failover because the dynamic ARP entries listed in the switch/router can be incorrect. In that case the management workstation will place an invalid IP to MAC entry in the local ARP table. Disabling the Proxy ARP service and decreasing the dynamic ARP entry timeout value at the switch/router can help to avoid this issue.
2-4
bloomdatashow
Note: Internal bit maps
Available in Fabric OS versions: v3.0.2, 3.1.0, 3.1.2 (port command group) v4.2 Example Output: NA Troubleshooting Use: This command is designed for internal debugging purposes. Example 2-2:
bloomDataShow 0
Note:
Use for internal debug purposes only.
Example 2-3: v3.1.2 output with extend group turned on.

sw3800_28:admin> bloomdatashow 0 initialized : 0x01 init_retry : 0x00 copper : 0x00 lli_tov : 0x00 bufbusy_tov : 0x01 fault_reason : 0x00 linit_ct : 0x00 liphold_ct : 0x02 type : 0x00 lflags : 0x00008601 rxlipa : 0x80000000 0x00000000 0x00000000 0x00000000 rxliha : 0x00000000 0x00000000 0x00000000 0x00000000 alpamap : 0x80000000 0x00000000 0x00000000 0x00000000 lifamap : 0x80000000 0x00000000 0x00000000 0x00000000 lipamap : 0x00000000 0x00000000 0x00000000 0x00000000 qllipa : 0x00000000 0x00000000 0x00000000 0x00000000 qlliha : 0x00000000 0x00000000 0x00000000 0x00000000 qllisa : 0x00000000 0x00000000 0x00000000 0x00000000 qlzone : 0x00000000 0x00000000 0x00000000 0x00000000 pltmap : 0x00000000 0x00000000 0x00000000 0x00000000 lilpmap : 0x00000000 0x00000000 0x00000000 0x00000000 lilpmap : 0x00000000 0x00000000 0x00000000 0x00000000 lilpmap : 0x00000000 0x00000000 0x00000000 0x00000000 lilpmap : 0x00000000 0x00000000 0x00000000 0x00000000 lilpmap : 0x00000000 0x00000000 0x00000000 0x00000000 lilpmap : 0x00000000 0x00000000 0x00000000 0x00000000 lilpmap : 0x00000000 0x00000000 0x00000000 0x00000000 lilpmap : 0x00000000 0x00000000 0x00000000 0x00000000 lli : 0x00000000 lli_pending : 0x00000003 ftx : 0x000307b8 dl_ftx : 0x00000000 dl_frx : 0x00000000 tov : 0x0000 : 0x0000 fault1 : 0x00000000 fault2 : 0x0000 fltreset_time : 0x00000000 fault_tov : 0x0000 credit : 0x0000 buf_state : 0x0000 lstate : 0xffff0002 timer : 0x103047f0 tofunc : 0x0 lpsm_iu : 0x00000000 fla_iu : 0x00000000 rxbi : 0x0041 rxbo : 0x0041 negotiating : 0x00000000 nego_done : 0x00000000 members : 0x00000001 tgrpPorts : 0x0000 0x0000 0x0000 0x0000 tgrpMinPort : 0x0000 tgrpMaxPort : 0x0000 mdelay : 0x00000000 adelay : 0x00a8a95b mark_tm : 0x3bbdd2c4 rtbl_flag : 0x00000009 bcast_rtbl : 0x00010000 EtoE_head : 0x0000 EtoE_next : 0x0001 0x0002 0x0003 0x0004 EtoE_next : 0x0005 0x0006 0x0007 0x0008
open_tov
2-5
EtoE_next : 0x0009 0x000a 0x000b 0x000c EtoE_next : 0x000d 0x000e 0x000f 0xffff lism_bufno : 0x00000000 lism_rxbd : 0x00000001 0x0031d500 fltIuHead : 0xffffffff fltIuTail : 0xffffffff sn_state : 0x32 sn_inprogress : 0x00 sn_txsp_list : 0x01 0x00 0x00 0x00 sn_txsp_count : 0x02 sn_curr_tx : 0x01 sn_rxsp_list : 0x01 0x00 0x00 0x00 sn_rxsp_count : 0x02 sn_curr_rx : 0x01 sn_rx_mem : 0xff sn_rxsp_recorded: 0x00 0x00 0x00 0x00 sn_rxsp_rec_count: 0x00 sn_time_nc : 0x0a22f200 sn_time_tx : 0x0a22f200 sn_time_neg : 0xffffffff sn_time_sync : 0x0a22f1f0 sn_speed : 0x01 sn_retries : 0x00 rxsig_loss_time : 0x00 enable_arbvc : 0x00 save_enc_out : 0x00 encout_valid : 0x00 tfrctl_changed : 0x0000 tfrctl_shadow : 0x0000 msg_online : 0x0001 unwanted_lisms : 0x00000000 unw_lisms_since_boot: 0x00000000
2-6
bloomfdetShow
Available in Fabric OS versions: v3.1.0, 3.1.2 (port command group) v4.2 Example Output: NA Troubleshooting Use: This command is designed for internal debugging purposes.: Note: Use for internal debug purposes only.

sw3800_28:admin> bloomfdetshow faildet_pstat 0x81002d2c: 0x0000 0x81102d2c: 0x0000 frmtrk_mode 0x81002d26: 0xfffe 0x81102d26: 0xfffe frmtrk_prtstat 0x81002d2e: 0x0000 0x81102d2e: 0x0000 frmtrk_failinfo[0] 0x81002d18: 0x00000000 0x81102d18: 0x00000000 frmtrk_failinfo[1] 0x81002d1c: 0x00000000 0x81102d1c: 0x00000000 ministatechk_stat 0x81002d20: 0x0fff01ff 0x81042d20: 0x0fff01ff 0x81102d20: 0x0fff01ff 0x81142d20: 0x0fff01ff faildet_pctl 0x81002d2a: 0x0007 0x81102d2a: 0x0007 frmtrk_ctl 0x81002d28: 0xffff 0x81102d28: 0xffff faildet_ctl 0x81002d24: 0f37 0x81042d24: 0f37 0x81102d24: 0f37 0x81142d24: 0f37 frmtrk_failinfo[0]: C0,R0: frTrkNumErrPt=0 isTrkNum=0 sbTrkNum=0 C1,R0: frTrkNumErrPt=0 isTrkNum=0 sbTrkNum=0 frmtrk_failinfo[1]: C0,R1: rxPtQuad=0 finMsgE=0 frTrkNumE=0 txQNumE=0 mbStCkE=0 invEMsg=0 flPtMode=0 rptFrTx=0 trunkMprt=0 bufrNum=0 txQnumb=0 txPtNum=0 C1,R1: rxPtQuad=0 finMsgE=0 frTrkNumE=0 txQNumE=0 mbStCkE=0 invEMsg=0 flPtMode=0 rptFrTx=0 trunkMprt=0 bufrNum=0 txQnumb=0 txPtNum=0 Buffer Tag Mismatch (+0x2c64): 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ministatechk_stat: Q0: mbStCkE=0 finE=0 rxQParE=0 rxQFrTrkE=0 isSubSt=3 sbSS=3 isSt=f sbS=f mb#=1ff Q1: mbStCkE=0 finE=0 rxQParE=0 rxQFrTrkE=0 isSubSt=3 sbSS=3 isSt=f sbS=f mb#=1ff Q2: mbStCkE=0 finE=0 rxQParE=0 rxQFrTrkE=0 isSubSt=3 sbSS=3 isSt=f sbS=f mb#=1ff Q3: mbStCkE=0 finE=0 rxQParE=0 rxQFrTrkE=0 isSubSt=3 sbSS=3 isSt=f sbS=f mb#=1ff faildet_ctl: Q0: frcR2TqIntParE=0 frcProcRqdBufNumE=0 frcPutMsgE=0 frcBufTagE=0 bufTagCkEn=f frcFinMessageE=0 frcTrkNumCkEnable=1 txQNumCkEn=1 mbufStCkEn=1 finMsgCkEn=1 rxQParityChkEn=1 Q1: frcR2TqIntParE=0 frcProcRqdBufNumE=0 frcPutMsgE=0 frcBufTagE=0 bufTagCkEn=f frcFinMessageE=0 frcTrkNumCkEnable=1 txQNumCkEn=1 mbufStCkEn=1 finMsgCkEn=1 rxQParityChkEn=1 Q2: frcR2TqIntParE=0 frcProcRqdBufNumE=0 frcPutMsgE=0 frcBufTagE=0 bufTagCkEn=f frcFinMessageE=0 frcTrkNumCkEnable=1 txQNumCkEn=1 mbufStCkEn=1 finMsgCkEn=1 rxQParityChkEn=1 Q3: frcR2TqIntParE=0 frcProcRqdBufNumE=0 frcPutMsgE=0 frcBufTagE=0 bufTagCkEn=f frcFinMessageE=0 frcTrkNumCkEnable=1 txQNumCkEn=1 mbufStCkEn=1 finMsgCkEn=1 rxQParityChkEn=1 sw3800_28:admin>
2-7
bloomlistdisplay
Available in Fabric OS versions: v3.1.0, v3.1.2 (extend command group - not enabled by default) v4.2 Example Output: N/A Troubleshooting Use: This command is designed for internal debugging purposes.: Note: Use for internal debug purposes only.

bloomListDisplay Pt 0: putq_list_stat is empty (0xffffffff == NO_BUFFER) Pt 0: tolist_stat is empty (0xffffffff == NO_BUFFER) Pt 0: plist_stat is empty (0xffffffff == NO_BUFFER) Pt 0: aulist_stat is empty (0xffffffff == NO_BUFFER) Pt 0: piq_stat: head=0x0 tail=0x0 Pt 0: piq_stat: number of mini-buffers = 1 Pt 0: flist_stat : head=0x10 tail=0x37e (quad 0) 0x010 0x012 0x014 0x016 0x018 0x01a 0x01c 0x02a 0x02c 0x02e 0x030 0x032 0x034 0x036 0x044 0x046 0x048 0x04a 0x04c 0x04e 0x050 0x05e 0x060 0x062 0x064 0x066 0x068 0x06a 0x078 0x07a 0x07c 0x07e 0x080 0x082 0x084 0x092 0x094 0x096 0x098 0x09a 0x09c 0x09e
0x01e 0x038 0x052 0x06c 0x086 0x0a0
0x020 0x03a 0x054 0x06e 0x088 0x0a2
0x022 0x03c 0x056 0x070 0x08a 0x0a4
0x024 0x03e 0x058 0x072 0x08c 0x0a6
0x026 0x040 0x05a 0x074 0x08e
0x028 0x042 0x05c 0x076 0x090
<output truncated>
2-8
bloomsemsshow

bloomSemShow port port port port port port port port 0 buf_rdy: 1 buf_rdy: 2 buf_rdy: 3 buf_rdy: 4 buf_rdy: 5 buf_rdy: 6 buf_rdy: 7 buf_rdy: 1 1 1 1 1 1 1 1 1 bRdy0 max:0 bRdy1 max:0 bRdy2 max:0 bRdy3 max:0 bRdy4 max:0 bRdy5 max:0 bRdy6 max:0 bRdy7 max:0 phantom max:0 NONE Id 0x102fe310 NONE Id 0x102fe2e0 NONE Id 0x102fe2b0 NONE Id 0x102fe280 NONE Id 0x102fe250 NONE Id 0x102fe220 NONE Id 0x102fe1f0 NONE Id 0x102fe1c0 NONE Id 0x10366d00 BINARY BINARY BINARY BINARY BINARY BINARY BINARY BINARY owner: tSwitch owner: tSwitch owner: tSwitch owner: tSwitch owner: tSwitch owner: tSwitch owner: tSwitch owner: tSwitch queued_tasks: none queued_tasks: none queued_tasks: none queued_tasks: none queued_tasks: none queued_tasks: none queued_tasks: none queued_tasks: none
SwitchSem:
BINARY
owner: none
queued_tasks: none
2-9
bloomramdump

bloomRamDump blm_txb_ldesc (port0 size=136 inc=4) 81001800: 00000000 00000000 00000000 00000000 81001810: 00000000 00000000 00000000 00000000 81001820: 00000000 00000000 00000000 00000000 81001830: 00000000 00000000 00000000 00000000 81001840: 00000000 00000000 00000000 00000000
<output truncated>
2-10
cfgShow
Available in Fabric OS versions: All Version Differences: cfgshow output is the same in all Fabric OS versions Troubleshooting Use: Use this command in the devices do not see each other scenerio. Verify that they are both in the same enabled zone cfg. Use this command to display zone configuration information. If no operand is specified, all zone configuration information (both Defined and Effective) is displayed. If an operand is specified, it is used as a pattern to match zone configuration names in the defined configuration; those that match the pattern are displayed. The Defined configuration is the complete set of all zone objects that have been defined in the fabric. There can be multiple zone configurations defined, but only one can be enabled at a time. There may be inconsistencies in the definitions, zones or aliases that are referenced but not defined, or there may be duplicate members. The Defined configuration is the current state of the administrator input. The Effective configuration is the single zone configuration that is currently enabled. The devices that an initiator sees in the fabric are based on this configuration. The Effective configuration is built when a specific zone configuration is enabled Note: In example 2-2, the backup Compaq_DL_380 and the ATL_P1000_svr2 do not see each other because the zone they are in (backup) is not part of the enabled cfg (config1). If you want this zone to be part of this cfg you would have to add the zone to the cfg (CLI: cfgadd config1, backup) and then re-enable it to get new information read in (cfgenable config1). You could alternately create a new cfg and put in zones that you wanted enabled and enable new cfg over existing cfg.
v3.x Example Output: Example 2-2:

Defined configuration: cfg:config1sifsan1_svr1; sifsan2_svr2 zone:backupCompaq_DL_380; ATL_P1000_PRISM zone:sifsan1_svr1 svr1; clariion zone:sifsan2_svr2 svr2; clariion alias: ATL_P1000_PRISM 50:05:08:40:00:26:f0:00 alias: Compaq_DL_380 10:00:00:00:c9:28:64:3b alias: clariion 50:06:01:68:20:03:0b:9c alias: svr110:00:00:00:c9:21:83:2b alias: svr210:00:00:00:c9:22:ad:60 Effective configuration: cfg:config1 zone:sifsan1_svr1 10:00:00:00:c9:21:83:2b 50:06:01:68:20:03:0b:9c zone:sifsan2_svr2 10:00:00:00:c9:22:ad:60 50:06:01:68:20:03:0b:9c
2-11
2
Note:
When devices in a Fabric have good connections to their local switches and are seen by the Fabric in nsallshow but still do not see each other check to make sure they are not security blocked using zoning in the Fabric or lun masking at the at the end nodes. If zoning is enabled, only devices that are in the same enabled zone will see each other.
Default Access when zoning is not active In Firmware versions 2.5 and 2.6, a new parameter was introduced for security. This will provide the option to disable access to any devices in the Fabric unless zoning is enabled. The setting that controls this feature is under zoning operation parameters in configure. It's called Default Access when zoning is not active. When set to 0 and zoning is disabled, the switch automatically creates a NULL_ZONE with a dummy WWN of 00:00:00:00:00:00:00:00 and propagates it across the Fabric. If one switch in the Fabric has this feature enabled, the entire Fabric will see the NULL_ZONE when zoning is disabled and in essence is secure. A setting of 1 will disable this feature and allow all nodes to see all other nodes when zoning is disabled. configure example output used to configure default access when zoning is not enabled: Example 2-8:
admin> configure Configure... Fabric parameters (yes, y, no, n): [no] Virtual Channel parameters (yes, y, no, n): [no] Zoning Operation parameters (yes, y, no, n): [no] y Disable NodeName Zone Checking: (0..1) [0] Default Access when zoning is not active: (0..1) [0] RSCN Transmission Mode (yes, y, no, n): [no] NS Operation Parameters (yes, y, no, n): [no] Arbitrated Loop parameters (yes, y, no, n): [no] System services (yes, y, no, n): [no] Portlog events enable (yes, y, no, n): [no] No changes.
v4.2 Example Output:

cfgshow: Defined configuration: no configuration defined Effective configuration: no configuration in effect
2-12
cfgsize
Available in Fabric OS versions: v4.1, v4.2 Note: This command requires a Zoning license.
Troubleshooting Use: Use this command to display size details of the zone database. Use this command to display the size details of the zone database. The size details include the Zone DB max size, the committed size, and the transaction size. All sizes are in bytes. The 'Zone DB max size' is the upper limit for the Defined configuration, determined by the amount of flash memory available for storing the Defined configuration. The 'committed size' is the size of the Defined configuration currently stored in flash. The 'transaction size' is the size of the uncommitted Defined configuration. This value will be non-zero if the Defined configuration is being modified by telnet, API etc.; otherwise it is 0. Note: When security is enabled, this command can be issued from any switch in the fabric.
Example 2-3: To display size details of the Defined configuration:

switch:admin> cfgsize Zone DB max size - 127726 bytes committed - 8812 transaction - 0 switch:admin> cfgsize 1 Zone DB flash size - 131028 bytes switch:admin>
Note:
cfgsize can be used to ascertain a zone memory crunch.

cfgsize: Zone DB max size - 127726 bytes committed - 0 transaction - 0 value = 0 cfgshow: Defined configuration: no configuration defined Effective configuration: no configuration in effect
Note:
The zone data base flash size on VxWorks switches is ~98304 bytes. The zone data base flash size on a Linux switch is ~127726 bytes.
2-13
How can zone DB sizes be calculated? It would make sense for a WWN to be 8 bytes. If we stored it as a binary number, that's what it would be. However, it is stored as ASCII text. Each digit in the string is a byte, rather than having each two digits be a byte. That gets us to 16 bytes for a WWN. Then, of course, we also store the colons between the bytes and the semicolon delimiters between WWNs which gets up to 24 bytes for a WWN. Similarly, while one might think that a port zone entry would be 4 bytes, in fact it's stored as 6 bytes. Also note that having a second cfg doesn't double the size of the database. It can make between ~0.1% and 100% difference in the size. It depends on how many aliases and zones you need to add vs. reuse between the two configs. If you make reasonable assumptions about alias name sizes, number of configs, how many elements in each zone, etc., you end up with something like this:
Ports 64 256 512 1024
Zdb Size ~6k ~22k ~44k ~88k
It is critical to note that this is a ballpark number. That could be off by a factor of ten if you used different assumptions. (E.g. longer alias names, lots of JBODs in the fabric, multiple zones per initiator, etc.) A Zbd calculator spreadsheet yields between ~45k and ~918k (!) Zdb size for a 1024 port fabric. Finally, there are some protocol issues that need to be taken into account. So in a mixed Fabric with SW12000 in the core and 2xxx on the edge, the maximum zoning configuration size will be limited to 96KB. That is not, at present, true. You should not exceed ~34k (I think; it might be as high as ~36k.) in any fabric with a 2xxx switch at this time. This is noteworthy because it is possible to get a zone db size of ~57k with only 64 ports if you use aggressive assumptions (long alias names, etc.).
2-14
chassisShow
Available in Fabric OS versions: v4.0.2c, v4.1, v4.2 Version Differences: none Troubleshooting Use: Use this command to display all field replaceable units (FRUs) Use this command to inventory and display the field replaceable unit (FRU) header content for each object in the chassis. On some platforms for certain FRU types, a few items may not be available. In these cases the lines will be suppressed. Possibly affected are lines 2, 3, 4, 5, 6, 8, and 10 through 13. In addition, for lines 10 through 13, if there is no data set, these lines will be suppressed. The header data is formatted into a record consisting of (up to) 13 lines. The lines and their meaning are described below: Line # 1. This line displays --- Definition The first line of each record contains the object ID: Object type: CHASSIS, FAN, POWER SUPPLY, SW BLADE (switch), CP BLADE (control processor), WWN (world wide name), or UNKNOWN; and Object number: Slot <nn> (for blades), Unit <nn> (for everything else). If the FRU is part of an assembly, a brief description in parenthesis will be displayed. FRU header version number: Header Version: <x> Value used to calculate the object's power consumption, positive for power supplies, negative for consumers: Power Consume Factor: <-xxx> Brocade part number (up to 14 characters): Brocade Part Num: <xx-yyyyyyy-zz> Brocade serial number (up to 12 characters): Brocade Serial Num:<xxxxxxxxxx> Date the FRU was manufactured: Manufacture: Day: <dd> Month: <mm> Year: <yyyy> Date the FRU header was last updated: Update: Day: <dd> Month: <mm> Year: <yyyy> Cumulative time, in days, that the FRU has been powered on: Time Alive: <dddd> days Current time, in days, since the FRU was last powered on: Time Awake: <ddd> days Externally supplied ID (up to 10 characters): ID: <xxxxxxxxxx> Externally supplied part number (up to 20 characters): Part Num: <xxxxxxxxxxxxxxxxxxxx> Externally supplied serial number (up to 20 characters): Serial Num: <xxxxxxxxxxxxxxxxxxxx> Externally supplied revision number (up to 4 characters): Revision Num: <xxxx>
2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. Example
Notice embedded notes and notes at the end of this truncated output. Example 2-4:
chassisshow SW BLADE Slot: 1 Header Version: 2 Power Consume Factor: -180 Note: This is a normal pwr consumption value for port blade. See note 1. Brocade Part Num: 60-0001532-04 Brocade Serial Num: FQ000000496 Note: Most post GA sns start with FQ01 or higher. This was captured from a pre GA switch. Manufacture: Day: 8 Month: 5 Year: 2002 Update: Day: 16 Month: 10 Year: 2002 Time Alive: 193 days Note: Cummulative time blade pwrd up. Time Awake: 0 days Note: This FRU has been powered on for less than 1 day, if low like this and no fru insertion in historyshow it could imply blade reset itself. This correlates with line 9 notes above. SW BLADE Slot: 2
2-15
Header Version: 2 Power Consume Factor: -180 Brocade Part Num: 60-0001532-04 Brocade Serial Num: FQ000000790 Manufacture: Day: 22 Month: 5 Update: Day: 16 Month: 10 Time Alive: 199 days Time Awake: 0 days
Year: 2002 Year: 2002
CP BLADE Slot: 5 Header Version: 2 Power Consume Factor: -40 Note: This is a normal power consumption value for a CP blade. Brocade Part Num: 60-0001604-03 Brocade Serial Num: fp00x6003a0 Manufacture: Day: 5 Month: 12 Year: 2001 Update: Day: 16 Month: 10 Year: 2002 Time Alive: 207 days Time Awake: 0 days
<truncated output>
CHASSIS/WWN Unit: 1 Header Version: 2 Power Consume Factor: -3 Note: 03 represent normal power consumption value for WWN cards. Brocade Part Num: 40-0000031-03 Brocade Serial Num: FT00X8004B2 See note 2 below. Manufacture: Day: 6 Month: 12 Year: 2001 Update: Day: 16 Month: 10 Year: 2002 Time Alive: 175 days Time Awake: 0 days ID: 1 Serial Num: FT00x8004b2
Note:
When random errors occur look at power consumption values which are normally: - 180 for a port blade prior to v4.2 and - 40 after v4.2 - -40 for a cp blades prior to v4.2 and - 140 after v4.2 - 0-3 for a WWN card - 60 for a blower If the power consumption on a port blade is high look at time awake values, they should match historyshow output. If they dont blade could be resetting it self. DC converters have been known to cause this problem. You can test/ make it fail by executing slotoff/sloton, slotpoweroff will not work as it doesnt exercise the dc convertor the same way.
Note:
The CHASSIS/WWN Unit: 1 serial numbers last 3 bytes are the same as the last 3 bytes displayed when the licenseId command is executed.
v4.2 Example Output: Example 2-9:

chassisshow: SW BLADE Slot: 1 Header Version: 2 Power Consume Factor: -50 Factory Part Num: 40-0300909-01 Factory Serial Num: KP000000786 Manufacture: Day: 19 Month: 11 Update: Day: 31 Month: 12 Time Alive: 14 days Time Awake: 1 days
Year: 2003 Year: 2003
2-16

SW BLADE Slot: 2 Header Version: 2 Power Consume Factor: -50 Factory Part Num: 40-0300909-01 Factory Serial Num: KP000000676 Manufacture: Day: 6 Month: 11 Update: Day: 31 Month: 12 Time Alive: 15 days Time Awake: 1 days SW BLADE Slot: 4 Header Version: 2 Power Consume Factor: -50 Factory Part Num: 40-0300909-01 Factory Serial Num: KP000000795 Manufacture: Day: 19 Month: 11 Update: Day: 31 Month: 12 Time Alive: 15 days Time Awake: 1 days CP BLADE Slot: 5 Header Version: 2 Power Consume Factor: -140 Factory Part Num: 40-0300911-03 Factory Serial Num: KN00XD00428 Manufacture: Day: 16 Month: 12 Update: Day: 31 Month: 12 Time Alive: 8 days Time Awake: 1 days CP BLADE Slot: 6 Header Version: 2 Power Consume Factor: -140 Factory Part Num: 40-0300911-03 Factory Serial Num: KN00XD0040C Manufacture: Day: 16 Month: 12 Update: Day: 31 Month: 12 Time Alive: 8 days Time Awake: 1 days SW BLADE Slot: 7 Header Version: 2 Power Consume Factor: -50 Factory Part Num: 40-0300909-01 Factory Serial Num: KP000000764 Manufacture: Day: 15 Month: 11 Update: Day: 31 Month: 12 Time Alive: 14 days Time Awake: 1 days SW BLADE Slot: 8 Header Version: 2 Power Consume Factor: -50 Factory Part Num: 40-0300909-01 Factory Serial Num: KP000000816 Manufacture: Day: 15 Month: 11 Update: Day: 31 Month: 12 Time Alive: 12 days Time Awake: 1 days SW BLADE Slot: 9 Header Version: 2 Power Consume Factor: -50 Factory Part Num: 40-0300909-01 Factory Serial Num: KP000000729
Year: 2003 Year: 2003
Year: 2003 Year: 2003
Year: 2003 Year: 2003
Year: 2003 Year: 2003
Year: 2003 Year: 2003
Year: 2003 Year: 2003
2-17

Day: 10 Day: 31 13 days 1 days Month: 11 Month: 12 Year: 2003 Year: 2003
Manufacture: Update: Time Alive: Time Awake:
SW BLADE Slot: 10 Header Version: 2 Power Consume Factor: -50 Factory Part Num: 40-0300909-01 Factory Serial Num: KP000000726 Manufacture: Day: 23 Month: 11 Update: Day: 31 Month: 12 Time Alive: 15 days Time Awake: 1 days POWER SUPPLY Unit: 1 Header Version: 2 Power Consume Factor: 1000 Factory Part Num: 23-0000006-02 Factory Serial Num: FL2L0002037 Manufacture: Day: 13 Month: 5 Update: Day: 31 Month: 12 Time Alive: 400 days Time Awake: 1 days POWER SUPPLY Unit: 2 Header Version: 2 Power Consume Factor: 1000 Factory Part Num: 23-0000006-02 Factory Serial Num: FL2L0002031 Manufacture: Day: 13 Month: 5 Update: Day: 31 Month: 12 Time Alive: 394 days Time Awake: 0 days POWER SUPPLY Unit: 3 Header Version: 2 Power Consume Factor: 1000 Factory Part Num: 23-0000006-02 Factory Serial Num: FL2L0002040 Manufacture: Day: 13 Month: 5 Update: Day: 31 Month: 12 Time Alive: 399 days Time Awake: 1 days POWER SUPPLY Unit: 4 Header Version: 2 Power Consume Factor: 1000 Factory Part Num: 23-0000006-02 Factory Serial Num: FL2L0002046 Manufacture: Day: 13 Month: 5 Update: Day: 31 Month: 12 Time Alive: 394 days Time Awake: 0 days FAN Unit: 1 Header Version: 2 Power Consume Factor: -50 Factory Part Num: 60-0001662-01 Factory Serial Num: FM3E0001872 Manufacture: Day: 13 Month: 5 Update: Day: 31 Month: 12 Time Alive: 399 days Time Awake: 1 days
Year: 2003 Year: 2003
Year: 2002 Year: 2003
Year: 2002 Year: 2003
Year: 2002 Year: 2003
Year: 2002 Year: 2003
Year: 2002 Year: 2003
2-18

FAN Unit: 2 Header Version: 2 Power Consume Factor: -50 Factory Part Num: 60-0001662-01 Factory Serial Num: FM3E0001888 Manufacture: Day: 13 Month: 5 Update: Day: 31 Month: 12 Time Alive: 399 days Time Awake: 1 days FAN Unit: 3 Header Version: 2 Power Consume Factor: -50 Factory Part Num: 60-0001536-03 Factory Serial Num: FM3E0000211 Manufacture: Day: 27 Month: 9 Update: Day: 31 Month: 12 Time Alive: 429 days Time Awake: 1 days
Year: 2002 Year: 2003
Year: 2001 Year: 2003
CHASSIS/WWN Unit: 1(in same assembly as WWN Unit: 2) Header Version: 2 Power Consume Factor: -3 Factory Part Num: 60-0001501-04 Factory Serial Num: FT02X802D4A Manufacture: Day: 13 Month: 5 Year: 2002 Update: Day: 31 Month: 12 Year: 2003 Time Alive: 399 days Time Awake: 1 days WWN Unit: 2(in same assembly as WWN Unit: 1) Header Version: 2 Power Consume Factor: -3 Factory Part Num: 40-0000031-03 Factory Serial Num: FS010001130 Manufacture: Day: 13 Month: 5 Year: 2002 Update: Day: 31 Month: 12 Year: 2003 Time Alive: 399 days Time Awake: 1 days
2-19
configShow
Available in Fabric OS versions: All Version Differences: Output information varies by platform Troubleshooting Use: Use this command to display system configuration settings Use this command to view the system configuration settings set by the configure command. This command is particularly useful when troubleshooting fabric segmentation and distance extended fabric problems. The following information that could be helpful when troubleshooting can also be found: Boot information; diagnostic status; switchstatus that leads to error reports faulty or marginal and their corresponding Web Tools red or amber error reporting methodology; fabric parameters that need to be the same on all fabric switches; there are also numerous parameters indicating switch behaviors or outputs including SNMP and Fabric Watch. Notes are embedded with associated outputs. Note: Not all values shown are applicable to all system models and configurations.
In following configShow output Italicized notes and explanations follow output. Additional information depicted on the same line will be preceded with a // or will be indented. See configure information later in this reference guide for information on parameters not discussed here and for additional information on parameters that are discussed here. v3.x Example Output: Example 2-10:
switch:admin> configShow Ethernet addresses: 0:60:69:50:12:dc
The switch Ethernet address (the last 6.5 bytes of the switch WWN) Nvram data: fei(0,0)host:/usr/switch/firmware e=192.168.66.9:ffffff00 g=192.168.66.1 u=user tn=cylon The default location of switch firmware, the switch IP address, along with the default subnetmask and gateway which you need to be logged in as to set in this case user and the switch name, in this case cylon. diag.postDisable:0 // toggle type diagDisablePost or diagEnablePost
To toggle the following values type configure (switch must first be disabled using switchDisable command) and then yes to Fabric Parameters:
cylon:admin> configure Configure... Fabric parameters (yes, y, no, n): [no] y fabric.domain:9
// Each switch in a Fabric must have a unique domain ID

fabric.ops.BBCredit:16
//default buffer to buffer credit allocated to each switch port

fabric.ops.E_D_TOV:2000
Used to detect frames sent through switch port without a response within this timeout value. Switch port will typically retry (depends on traffic and need to stay within R_A_TOV) before forcing link down and re-attempting link connection. End devices do the same thing, they may or may not be set to retry.
fabric.ops.R_A_TOV:10000
Used for end-to-end error detection by ULP Host sends I/O to target, if no response within R_A_TOV (regardless of E_D_TOV) then ULP either retries or does whatever it is configured to do (it could discard). This value should be increased in switch and on end devices in remote switch Fabrics to compensate for long distance carrier time.
2-20
A special note on E_D_TOV and R_A_TOV values: E_D_TOV and R_A_TOV values are internally used in Brocade switches to optimize how long a frame will get queued if there is no credit forwarded.
fabric.ops.dataFieldSize:2112 fabric.ops.mode.SeqSwitching:0 fabric.ops.mode.fcpProbeDisable:0 fabric.ops.mode.isolate:0
//no E_Port communication allowed, can be toggled using portcfgEport command.

fabric.ops.mode.longDistance:0
// In Fabrics with version 2.x switches this command is used in conjunction with the portCfgLongDistance command to extend ISL capability (extended switch license required).
fabric.ops.mode.noClassF:0
Class F frames will not be used for inter-switch communications - Class 2 is used Ex: CNT box does not understand Class F, so it is suppressed when a CNT box is used. Toggle using Suppress Class F Traffic under configure_Fabric Parameters.
fabric.ops.mode.pidFormat:0 fabric.ops.mode.sync:0 fabric.ops.mode.sync under configure_Fabric Parameters will toggle.
Used to prevent time out delays in remote Fabrics.

fabric.ops.mode.unicastOnly:0
// This applies only to SilkWorm 1600 where they don't support broadcast or multicast. Choices are 1/0 which means on/off. It is changed using configure - Unicast-only Operation, only SilkWorm 1600s will have this option.
fabric.ops.mode.useCsCtl:0 fabric.ops.mode.vcEncode:0
The following outputs relate to Virtual Channel (vc) settings for establishing communication priority over ISLs and are configurable only when VC Encoded Address Mode is set. Like all fabric.ops parameters, the must be the same all on fabric switches. There are not any direct corresponding commands to toggle the vc information depicted in this slide. There are two groups of parameters associated with virtual channels and priorities for same. The bit map in the fabric.ops.vc.config maps vcs to priorities. The rest of the information shows that class 2 traffic is mapped to vc 2, class 3 is mapped to vc 3, link control frames are mapped to vc 0 and multicast frames are mapped to vc 7. Typically, the higher the VC value the lower the priority, but this can be changed. The default priorities have been set to maximize throughput and should not be changed. The priority settings can be viewed using the configure command: type configure (switch must first be disabled using switchDisable command) and then yes to Virtual Channel parameters:
switchname:admin> configure Configure... Fabric parameters (yes, y, no, n): [no] Virtual Channel parameters (yes, y, no, n): [no] y VC Priority 2: (2..3) [2] VC Priority 3: (2..3) [2] VC Priority 4: (2..3) [2] VC Priority 5: (2..3) [2] VC Priority 6: (2..3) [3] VC Priority 7: (2..3) [3]
2-21
The switch enables fine-tuning for a specific application, by configuring the parameters for eight virtual channels. The first two virtual channels are reserved for switch internal functions and are not available for modification. The default virtual channel settings have already been optimized for switch performance. Changing the default values can improve switch performance, but can also degrade performance. Do not change these settings without fully understanding the effects of the changes.
fabric.ops.vc.class.2:2 fabric.ops.vc.class.3:3 fabric.ops.vc.config:0xc0 fabric.ops.vc.linkCtrl:0 fabric.ops.vc.multicast:7 fabric.ops.wan_tov:0
To toggle fc4.fcIp.address and fc4.fcIp.mask values, invoke ipAddrSet To toggle the rest of the values depicted, invoke configure (the switch must first be disabled by invoking the switchDisable command) and then enter y to the Arbitrated Loop parameters query:
cylon:admin> configure Configure... Fabric parameters (yes, y, no, n): [no] Switch Operating Mode (yes, y, no, n): [no] Zoning Operation parameters(yes, y, no, n):[no] RSCN Transmission Mode (yes, y, no, n): [no] NS Pre-zoning Mode (yes, y, no, n): [no] Arbitrated Loop parameters (yes, y, no, n): [no] y Send FAN frames?: (0..1) [0] //fcAL.fanFrameDisable Always Send RSCN?: (0..1) [0] //fcAL.alwaysSendRSCN Enable CLOSE on OPEN received?: (0..1) [0] //fcAL.openSendCLS
Note:
fcAL.useAltBBCredit cannot be toggled.
Invoke configure and then enter y to the Arbitrated Loop parameters query. This enables you to disallow ALPA 0 from being used (and reserves 0 for the FL_Port).
//Do Not Allow AL_PA 0x00? fc4.fcIp.address:0.0.0.0 // To toggle fc4.fcIp.address value type ipAddrSet fc4.fcIp.mask:0.0.0.0//To toggle fc4.fcIp.mask value type ipAddrSet fcAL.alwaysSendRSCN:0 fcAL.fanFrameDisable:1 fcAL.openSendCLS:0 fcAL.useAltBBCredit:0 These control contrast on 2800 LCDs: lcdContrast:128 lcdContrast.orange:208 licenseKey:SbczcSQbRRTcd0dw // licenseShow and licenseAdd can be used to view and set route.delayReroute:0// IodSet will toggle route.embeddedPortBcast:1 route.stickyRoutes:0// DlsSet will toggle
v4.1 Example Output: Example 2-11: 1. To toggle the rpc values, type configure, then yes to Service Parameters.
rpc.rapid:1 rpc.rstatd:0 rpc.rusersd:0 shell.delete:0 // backspace 1 will toggle
2-22

shell.quiet:0 // Quietmode 1 will toggle shell.timeout:0 // Timeout <# of minutes> will toggle syslog.errDisplayLevel:5 //errDisplayFilter 4 will toggle this to syslog.errDisplayLevel:4 syslog.errsOnConsole:1 // errConsoleDisable will toggle this to syslog.errsOnConsole:0 thresh.alarmsfilter:1 // fwAlarmsFilterSet 1 will toggle thresh.thad:1 // To toggle this, type configure, then yes to Service Parameters. xlativeModeDisable:0
Note:
If you see thresh.cust.xxxx this means that custom Fabric Watch parameters have been set.
2. 3.
Configure, then yes to Fabric Parameters change VC Encoded Address Mode to 1 and another selection that says Disable Translative Mode will appear. Change this value (0 or 1/ off or on) to toggle. Use configure, then yes to Portlog events enable to toggle:
Displaying enabled/disabled portlog events start(a switch start or re-start event ): Enabled disable(a port is disabled ): Enabled enable(a port is enabled ): Enabled ioctl(a port I/O control is executed ): Enabled Tx(a frame is transmitted ): Enabled Tx1(a frame is transmitted, class 1 ): Enabled Tx2(a frame is transmitted, class 2 ): Enabled Tx3(a frame is transmitted, class 3 ): Enabled Rx(a frame is received ): Enabled Rx1(a frame is received, class 1 ): Enabled Rx2(a frame is received, class 2 ): Enabled Rx3(a frame is received, class 3 ): Enabled stats(port status or statistics ): Enabled scn(a state change notification ): Enabled pstate(a port changes physical state ): Enabled reject(a received frame is rejected ): Enabled busy(a received frame is busied ): Enabled ctin(a CT based request is received ): Enabled ctout(a CT based response is transmitted ): Enabled errlog(a message is added to the error log): Enabled loopscn(a loop state change notification ): Enabled create(a task is created ): Enabled debug(generic debug info ): Disabled nbrfsm(neighbor state transition ): Enabled timer(timer ): Enabled sn(speed negotiation ): Enabled NOTES
Note:
If portlog events are disabled the outputs associated with those events will not be available in the portlogdump.
Example 2-5:
configshow RSCN.end-device.TransmissionMode:0 alpaList:1 diag.loopID:125 diag.mode.burnin:0 diag.mode.esd:0 diag.mode.lab:0 diag.mode.mfg:0 diag.postDisable:1 diag.retryDisable:0 diag.script.SWITCH.BURNIN:switchburnin.sh diag.script.SWITCH.POST1:switchpost1.sh diag.script.SWITCH.POST2:switchpost2.sh
2-23
diag.test.crossPort.passes:5000 diag.test.passes:0 diag.test.portLoopback.passes:1000 diag.test.silkScreen.passes:180 diag.test.spinSilk.passes:120 ether.link.mode:AUTO fabric.domain:1 fabric.ops.BBCredit:16 fabric.ops.E_D_TOV:2000 fabric.ops.R_A_TOV:10000 fabric.ops.dataFieldSize:2112 fabric.ops.mode.fcpProbeDisable:0 fabric.ops.mode.isolate:0 fabric.ops.mode.longDistance:0 fabric.ops.mode.noClassF:0 fabric.ops.mode.tachyonCompat:0 fabric.ops.mode.unicastOnly:0 fabric.ops.mode.useCsCtl:0 fabric.ops.mode.vcEncode:0 fabric.ops.vc.class.2:2 fabric.ops.vc.class.3:3 fabric.ops.vc.config:0xc0 fabric.ops.vc.linkCtrl:0 fabric.ops.vc.multicast:7 fc4.fcIp.address:0.0.0.0 fc4.fcIp.mask:0.0.0.0 fc4.fcp.productId:FC Switch fc4.fcp.vendorId:BROCADE fcAL.alwaysSendRSCN:0 fcAL.fanFrameDisable:0 fcAL.openSendCLS:0 fcAL.useAltBBCredit:0 flannel.ops.frameColMethod:piling flannel.ops.openBBCredit:4 gen.fabos:0 gen.zone:0 http.javaplugin.homeURL:http://java.sun.com/products/plugin http.javaplugin.version:1,2,2 lcdContrast:128 lcdContrast.orange:208 ms.PlatEnable:0 ms.TDEnable:0 ns.prezonemode:0 oemLogo:0 portCfg:0,0x10000000;1,0xd0000000;2,0x10000000;3,0x10000000;4,0x10000000;5,0x10000000;6,0x10000000;7, 0x10000000;8,0x10000000;9,0x10000000;10,0x10000000;11,0x10000000;12,0x10000000;13,0x10000000;14,0x100 00000;15,0x10000000;16,0x10000000;17,0x10000000;18,0x10000000;19,0x10000000;20,0x10000000;21,0x100000 00;22,0x10000000;23,0x10000000;24,0x10000000;25,0x10000000;26,0x10000000;27,0x10000000;28,0x10000000; 29,0x10000000;30,0x10000000;31,0x10000000;32,0x10000000;33,0x10000000;34,0x10000000;35,0x10000000;36, 0x10000000;37,0x10000000;38,0x10000000;39,0x10000000;40,0x10000000;41,0x10000000;42,0x10000000;43,0x1 0000000;44,0x10000000;45,0x10000000;46,0x10000000;47,0x10000000;48,0x10000000;49,0x10000000;50,0x1000 0000;51,0x10000000;52,0x10000000;53,0x10000000;54,0x10000000;55,0x10000000;56,0x10000000;57,0x1000000 0;58,0x10000000;59,0x10000000;60,0x10000000;61,0x10000000;62,0x10000000;63,0x10000000; quickLoop.holdOpenInit:0 quickLoop.noAlpaZero:0 quickLoop.peerWWN:00:00:00:00:00:00:00:00 quickLoop.portBitmap:0x0000000000000000 quickLoop.softInit:0 rlsDisable:1 route.delayReroute:0 route.embeddedPortBcast:1 route.stickyRoutes:0 rpc.rapid:1 rpc.rstatd:0 rpc.rusersd:0
2-24

shell.delete:0 shell.quiet:0 snmp.accessList.0.address:0.0.0.0 snmp.accessList.0.rw:1 snmp.accessList.1.address:0.0.0.0 snmp.accessList.1.rw:1 snmp.accessList.2.address:0.0.0.0 snmp.accessList.2.rw:1 snmp.accessList.3.address:0.0.0.0 snmp.accessList.3.rw:1 snmp.accessList.4.address:0.0.0.0 snmp.accessList.4.rw:1 snmp.accessList.5.address:0.0.0.0 snmp.accessList.5.rw:1 snmp.agtParty.0.address:0.0.0.0 snmp.agtParty.0.authPrivSecret:Secret C0de snmp.agtParty.0.index:1 snmp.agtParty.0.port:162 snmp.agtParty.1.address:0.0.0.0 snmp.agtParty.1.authPrivSecret:OrigEquipMfr snmp.agtParty.1.index:2 snmp.agtParty.1.port:162 snmp.agtParty.2.address:0.0.0.0 snmp.agtParty.2.authPrivSecret:private snmp.agtParty.2.index:3 snmp.agtParty.2.port:162 snmp.agtParty.3.address:0.0.0.0 snmp.agtParty.3.authPrivSecret:public snmp.agtParty.3.index:4 snmp.agtParty.3.port:162 snmp.agtParty.4.address:0.0.0.0 snmp.agtParty.4.authPrivSecret:common snmp.agtParty.4.index:5 snmp.agtParty.4.port:162 snmp.agtParty.5.address:0.0.0.0 snmp.agtParty.5.authPrivSecret:FibreChannel snmp.agtParty.5.index:6 snmp.agtParty.5.port:162 snmp.authentTraps:0 snmp.mibCap:103 snmp.swEventTrapLevel:0 snmp.sysContact:Field Support. snmp.sysDescription:Fibre Channel Switch. snmp.sysLocation:End User Premise snmp.sysObjectID:1588.2.1.1.1 switch.interopMode:0 switch.largeEntry.cap:0 switch.mail.agent_0.item_112:NONE switch.mail.agent_10.item_112:NONE switch.status.policy.Fans.down:2 switch.status.policy.Fans.marginal:1 switch.status.policy.FaultyPorts.down:2 switch.status.policy.FaultyPorts.marginal:1 switch.status.policy.ISLStatus.down:0 switch.status.policy.ISLStatus.marginal:0 switch.status.policy.MissingSFPs.down:0 switch.status.policy.MissingSFPs.marginal:0 switch.status.policy.PortStatus.down:0 switch.status.policy.PortStatus.marginal:0 switch.status.policy.PowerSupplies.down:2 switch.status.policy.PowerSupplies.marginal:1 switch.status.policy.Temperatures.down:2 switch.status.policy.Temperatures.marginal:1 thresh.alarmsfilter:1 thresh.cust.env.Fan.above:3
2-25
thresh.cust.env.Fan.below:3 thresh.cust.env.Fan.high:3400 thresh.cust.env.Fan.inbetween:1 thresh.cust.env.Fan.unit:RPM thresh.cust.port.Signal.high:120 thresh.cust.port.Signal.low:1 thresh.cust.port.Signal.unit:Error(s) thresh.cust.port.State.above:1 thresh.cust.port.State.below:1 thresh.cust.port.State.exceeded:0 thresh.cust.port.State.high:120 thresh.cust.port.State.low:1 thresh.cust.port.State.tb:2 thresh.cust.port.State.unit:Change(s) thresh.envFan.actLevel:1 thresh.envFan.thLevel:1 thresh.portSignal.actLevel:1 thresh.portSignal.thLevel:1 thresh.portState.actLevel:1 thresh.portState.thLevel:1 thresh.thad:1 xlativeModeDisable:0 zoning.check.nodeNameDisabled:0 zoning.standardMode:0 Licenses: RcyzeSbeSgdz0fk
Additional information about the above listed configshow parameters in order listed:
RSCN.end-device.TransmissionMode:0
To toggle RSCN.end-device.TransmissionMode:0 invoke configure (the switch must first be disabled by invoking the switchDisable command) and then enter y to the RSCN Transmission Mode query. Example:
RSCN Transmission Mode (yes, y, no, n): [no] yes End-device RSCN Transmission Mode (0 = RSCN with single PID, 1 = RSCN with multiple PIDs, 2 = Fabric RSCN): (0..2) [0]
alpaList:1 diag.loopID:125 is a vestigial remnant of Flannel ASIC support and early Loom ASIC validation that serves no useful purpose in any of our currently supported platforms. It sets the ALI to be used for test frames in diagnostics tests that meet the following conditions: 1. 2. 3. They are not run on an online switch (these use ALI 0 which is the normal loop id for the switch) They are run in FL mode with internal loopback. They do not set the ALPA as part of the test.
There is no user accessible test that meets these criteria. The possible outputs are 1 - 127, the default is 125. It should never be changed but it is conceivable but unlikely that we may use it again in the future. It can only be changed using the configDownload command. diag.mode.burnin:0 is toggled using the diagSetBurnin command. This sets up the blade burn-in parameters for the registered burn-in script. The name of burn-in script can be set with burninname command alternatively. The burn-in will start at the next run of POST (Power-On Self-Test) on the designated blade(s). See help diagSetBurnin for more information. diag.mode.esd:0 diag.mode.lab:0 diag.mode.mfg:0 is toggled using diagSetEsdMode which allows the test to continue if the port fails. is toggled using setLabMode which allows panic data to be gathered. Set after a switch panic to allow future panic troubleshooting. is not used
2-26
Fabric OS SupportShow Information diag.postDisable invoke diagDisablePost.
diag.retryDisable:0 invoke diagRetry - when enabled modifies the behavior of the diagnostic test methods, POST (Power-On Self-Test), and burn-in scripts. The exact behavior depends on the tests and scripts that are run Burn-in script files set with diagSetBurin command:
diag.script.SWITCH.BURNIN:switchburnin.sh diag.script.SWITCH.POST1:switchpost1.sh diag.script.SWITCH.POST2:switchpost2.sh
These are obsolete, they were in the very first version of the file as an example of the kind of variables that could be in the configShow database, but have never been used:
diag.test.crossPort.passes:5000 diag.test.passes:0 diag.test.portLoopback.passes:1000 diag.test.silkScreen.passes:180 diag.test.spinSilk.passes:120
ether.link.mode:AUTO displays Ethernet speed negotiation setting, toggle with ifModeSet command To toggle the following values, invoke configure (the switch must first be disabled by invoking the switchDisable command) and then enter y to the Fabric Parameters query (configShow settings that correspond to configure output follows //):
fabric.domain:1 Type configure then yes to Fabric parameters to toggle Domain: (1..239) [9] //fabric.domain (This must be unique for each switch in the Fabric)
The following parameters represent fabric.ops parameters and need to be the same on all Fabric switches:
fabric.ops.BBCredit:16 fabric.ops.R_A_TOV:10000 Type configure then yes to Fabric parameters to toggle R_A_TOV: (4000..120000) [10000] //fabric.ops.E_D_TOV (R_A_TOV = Resource Allocation Time Out Value). Used for end-to-end error detection by ULP. fabric.ops.E_D_TOV:2000 Type configure then yes to Fabric parameters to toggle E_D_TOV: (1000..5000) [2000] //fabric.ops.R_A_TOV (E_D_TOV = Error Detect Time Out Value) Counts Fabric frames that exceed this value. Switch port will typically retry before forcing link down and re-attempting link connection. fabric.ops.dataFieldSize:2112
size:(256..2112)[2112]
Type configure then yes to Fabric parameters to toggle Data field //fabric.ops.dataFieldSize Sometimes toggled when using Remote Switch.
fabric.ops.mode.fcpProbeDisable:0 Type configure then yes to Fabric parameters to toggle Disable Device Probing: (0..1) [0] //fabric.ops.mode.fcpProbeDisable Disables auto discovery process on switches, the switches use this process to get private storage device information into name server data base. This process is not disabled (its enabled) by default. There is a correlation with RlsDisable, discussed later, a function that is now configurable on V4.X switches. fabric.ops.mode.isolate:0
This fabric.ops parameter is not changed using configure. allowed, used on 1st generation switches.
No E_Port communication
This fabric.ops parameter is not changed using configure in v4.X switches. This configure long distance setting is needed for 2XXX switches in Fabrics where the portCfgLongDistance command is used. This setting is not required for 3XXX or above switches.
fabric.ops.mode.longDistance:0 fabric.ops.mode.noClassF:0 Type configure then yes to Fabric parameters to toggle // fabric.ops.mode.noClassF
Class F frames will not be used for inter-switch communications - Class 2 is used - needed by some gateways.
fabric.ops.mode.tachyonCompat:0
Type configure then yes to Fabric parameters to toggle: Sequence Level
Switching: (0..1) [0]
2-27
Used to allow frame interweaving. If a Tachyon is in the middle of receiving a multiple frame (non-SCSI) sequences from one source and it receives a frame from a different source, it may either respond with a P_BSY to the second source, or it may require its attached host to perform sequence reassembly manually (causing a large amount of overhead on the host machine). Tachyon mode is phrased as Sequence Level Switching in the configure command. If this feature is set to 1, frames of the same sequence from a particular source are transmitted together as a group. When this feature is set to 0, frames are transmitted interleaved among multiple sequences. Bottom line is Tachyon mode will have big performance impact.
fabric.ops.mode.unicastOnly:0 // This applies only to Silkworm 1600 where they don't support broadcast or multicast. Choices are 1/0 which means on/off. It is changed using configure - Unicast-only Operation, is only found in the Silkworm 1600. fabric.ops.mode.useCsCtl:0
Type configure then yes to Fabric parameters and toggle Per-frame Route Priority: (0..1) [0] to change fabric.ops.mode.useCsCtl Creates additional Virtual Channel ID for per-frame based Type configure then yes to Fabric parameters and toggle VC Encoded Address Mode:
prioritization, using existing VCs plus frame header information.

fabric.ops.mode.vcEncode:0
(0..1) [0] *//fabric.ops.mode.vcEncode This will allow communication with an address format compatible with some first-generation switches
The following outputs relate to Virtual Channel (vc) settings for establishing communication priority over ISLs and are configurable only when VC Encoded Address Mode is set:
fabric.ops.vc.class.2:2 // Specifies the VC used for class 2 frame traffic. fabric.ops.vc.class.3:3 // Specifies the VC used for class 3 frame traffic. fabric.ops.vc.config:0xc0 fabric.ops.vc.linkCtrl:0 // Specifies the virtual channel used for N_Port- generated, Class 2 link control frames (ACKs, P_BSYs, P_RJTs). Forces N_Port-generated link control frames to be sent using a Class 2 data Virtual Channel when set to 0. When set to 1, the control frames are sent using a Virtual Channel normally reserved for Fabric-internal traffic. fabric.ops.vc.multicast:7 // Specifies the VC used for multicast frame traffic.
There are not any direct corresponding commands to toggle the vc information depicted in this slide. There are two groups of parameters associated with virtual channels and priorities for same. The bit map in the fabric.ops.vc.config maps vcs to priorities. The rest of the information in this slide shows that class 2 traffic is mapped to vc 2, class 3 is mapped to vc 3, link control frames are mapped to vc 0 and multicast frames are mapped to vc 7. Typically, the higher the vc value the lower the priority, but this can be changed. The default priorities have been set to maximize throughput and should not be changed. The priority settings can be viewed using the configure command: type configure (switch must first be disabled using switchDisable command) and then yes to Virtual Channel parameters: Example 2-6:
switchname:admin> configure Configure... Fabric parameters (yes, y, no, n): [no] Virtual Channel parameters (yes, y, no, n): [no] y VC Link Control: (0..1) [0] VC Class 2: (2..5) [2] VC Class 3: (2..5) [3] VC Multicast: (6..7) [7] VC Priority 2: (2..3) [2] VC Priority 3: (2..3) [2] VC Priority 4: (2..3) [2] VC Priority 5: (2..3) [2] VC Priority 6: (2..3) [3] VC Priority 7: (2..3) [3]
The switch enables fine tuning for a specific application, by configuring the parameters for eight virtual channels. The first two virtual channels are reserved for switch internal functions and are not available for modification. The default virtual channel settings have already been optimized for switch performance. Changing the default values can improve switch performance, but can also degrade performance. Do not change these settings without fully understanding the effects of the changes. Ports are assigned to VCs based on the last two bits of the middle byte of the 24-bit address. There are four possible combinations, 00, 01, 10 and 11. These correspond to VC2, 3, 4 and 5 respectively. In our course materials, we used to say ASIC/Quad 0 was assigned to VC2 and so on.
2-28

fc4.fcIp.address:0.0.0.0 fc4.fcIp.mask:0.0.0.0
Corresponding commands to toggle settings include: To toggle fc4.fcIp.address and fc4.fcIp.mask values, invoke ipAddrSet
fc4.fcp.productId:FC Switch is a product identification for FCP Inquiry changed using configdownload fc4.fcp.vendorId:BROCADE is a vendor identification for FCP Inquiry changed using configdownload
To toggle the fcAL values depicted below, invoke configure (the switch must first be disabled by invoking the switchDisable command) and then enter y to the Arbitrated Loop parameters query, information displayed after // will tell you what configure command will toggle output, comments are curved:
fcAL.alwaysSendRSCN:0 fcAL.fanFrameDisable:0 fcAL.openSendCLS:0 fcAL.useAltBBCredit:0
Descriptions of these Arbitrated Loop Parameter fields that can either be a 1 or a 0 are as follows: Send FAN frames? Specifies that fabric address notification (FAN) frames be sent to public loop devices to notify them of their node ID and address. When set to 1, frames are sent; when set to 0 frames are not sent. Enable CLOSE on OPEN received? If this is set, a CLS is returned immediately to an OPN if no buffers are available. This is required for TachLite. Always send RSCN? Following the completion of loop initialization, a remote state change notification (RSCN) is issued when FL_Ports detect the presence of new devices or the absence of pre-existing devices. When set, a RSCN is issued upon completion of loop initialization, regardless of the presence or absence of new or pre-existing devices. Do Not Allow AL_PA 0x00? This option disables ALPA values from being 0x00. These two parameters are left overs that represent 1st generation switch capabilities:
flannel.ops.frameColMethod:piling flannel.ops.openBBCredit:4
These two outputs are left over from the early design phase, and should be deleted; they will be removed from configuration database in 4.1. In 4.0 they are combined into one generation number, stored in the /etc/fabos/pdata.gen file (not in the switch configuration any more!). Every time a change of switch configuration or zoning configuration, generation number will increment by 1. Please refer the generationSet and generationShow for details.
gen.fabos:0
is the generation number of the switch configuration. Default value is zero, and will increment by 1 every time switch configuration changes. There is no need to change it, unless customer wants to reset the generation number to begin with a specific number or reset to 0.
gen.zone:0 is the generation number of the zoning configuration. Default value is zero, and will increment by 1 every time zoning configuration changes.
To toggle http settings execute httpCfgSet from a root account or edit configUpload text file:
http.javaplugin.homeURL:http://java.sun.com/products/plugin http.javaplugin.version:1,2,2
These two parameters change the 2800 front panel LCD contrast levels: lcdContrast:128 lcdContrast.orange:208 Management server related outputs:
ms.PlatEnable:0 //msplmgmtactivate command toggles this. This indicates whether MS Platform Service is enabled or not in the entire fabric. If it is 1, it's enabled in the entire fabric. Users can turn it off or disable in the entire fabric by issuing 'msPlMgmtDeactivate' from a switch
2-29
Fabric OS SupportShow Information Example 2-7: Value was changed to 0 after de-activating:
RSL_12K8_SW0:admin> configshow ms ms.PlatEnable:1 ms.TDEnable:0 RSL_12K8_SW0:admin> msplatshow *MS Platform Management Service DB is empty. RSL_12K8_SW0:admin> msplmgmtdeactivate MS Platform Management Service is currently enabled. This will erase Platform configuration information as well as Platform databases in the entire fabric. Would you like to continue disabling? (yes, y, no, n): [no] y Deactivating Platform Management Service is in progress...... *Completed deactivating Platform Management Service in the fabric! RSL_12K8_SW0:admin> configshow ms ms.PlatEnable:0 ms.TDEnable:0 ms.TDEnable:0 indicates whether MS Topology Discovery Service is enabled or not in a "local" switch. 1 means enabled in this switch, 0 means disabled. Each switch in the fabric can be configured differently unlike Platform Service. Users can disable w/ 'msTdDisable' in each switch or 'msTdDisable ALL' will disable all switches in the fabric. ns.prezonemode:0 To toggle ns.prezonemode type configure, then NS Operation Parameters (yes, y, no, n): [no] y
Pre-zoned responses Mode (0 = Standard Mode, 1 = Pre-zoning On): (0..1) [0] Specifies Name Server operating mode. If Pre-zoned responses Mode is enabled, the Name Server checks only the lot list when responding to requests from hosts.
oemLogo:0 portCfg:0,0x10000000;1,0xd0000000;2,0x10000000;3,0x10000000;4,0x10000000;5,0x10000000;6,0x10000000;7, 0x10000000;8,0x10000000;9,0x10000000;10,0x10000000;11,0x10000000;12,0x10000000;13,0x10000000;14,0x100 00000;15,0x10000000;16,0x10000000;17,0x10000000;18,0x10000000;19,0x10000000;20,0x10000000;21,0x100000 00;22,0x10000000;23,0x10000000;24,0x10000000;25,0x10000000;26,0x10000000;27,0x10000000;28,0x10000000; 29,0x10000000;30,0x10000000;31,0x10000000;32,0x10000000;33,0x10000000;34,0x10000000;35,0x10000000;36, 0x10000000;37,0x10000000;38,0x10000000;39,0x10000000;40,0x10000000;41,0x10000000;42,0x10000000;43,0x1 0000000;44,0x10000000;45,0x10000000;46,0x10000000;47,0x10000000;48,0x10000000;49,0x10000000;50,0x1000 0000;51,0x10000000;52,0x10000000;53,0x10000000;54,0x10000000;55,0x10000000;56,0x10000000;57,0x1000000 0;58,0x10000000;59,0x10000000;60,0x10000000;61,0x10000000;62,0x10000000;63,0x10000000; Displays a bitmap of portCfgShow options, changes made in this file will cause the switch to not come up!!!
Quickloop parameter mappings, read from attached switches in Quickloop: Example 2-8:
quickLoop.holdOpenInit:0 quickLoop.noAlpaZero:0 quickLoop.peerWWN:00:00:00:00:00:00:00:00 quickLoop.portBitmap:0x0000000000000000 quickLoop.softInit:0
To toggle the following commands type configure, then: System services (yes, y, no, n): [no] y
rstatd (on, off): [off] rusersd (on, off): [off] rapid (on, off): [on] thad (on, off): [on] Disable RLS probing (on, off): [on]
2-30

rlsDisable:1 To toggle the following commands type configure, then: System
services (yes, y, no, n): [no] y //Disable RLS probing (on, off): [on] By default, this disables Read Link Error Status probing of the ALPAs. When this feature is enabled the
switch will collect new Link Error Status from the devices (both F_Port and L_Port) every 4 seconds. Link Error Status contains data such as: link fail loss sync loss sig prtc err bad word crc err. This information can be displayed with fcpRlsShow telnet command. For L_Port it will show all ALPAs on that port.
route.delayReroute:0 iodSet will toggle the route.delayReroute value. In the event of a Fabric routing change, there will be a 2
second hold down period to allow frames already in transit to reach their destination ahead of frames needing rerouting
route.embeddedPortBcast:1
route.stickyRoutes:0 dlsSet will toggle the route.stickyRoutes value. This setting enables dynamic load sharing by default. In
the event of a Fabric routing change, routes will be reallocated so that all available equal link cost ISLs are shared. To toggle the rpc values invoke configure, then enter y to the Service Parameters query.
rpc.rapid:1
Rapid stands for RPC API daemon. It handles the RPC requests for the API server.
rpc.rstatd:0 Dynamically enables or disables a server that returns information about system operation information through remote procedure calls (RPC). The protocol provides for a wide-range of system statistics. The retrieval of this information is supported by a number of operating systems which support RPC. Most UNIX-based systems (HP-UX, Irix, Linux, Solaris, etc.) use the rup and rsysinfo commands to retrieve the information. See your local system documentation for the appropriate usage of the these or equivalent commands. rpc.rusersd:0
Dynamically enables or disables a server that returns information about the user logged into the system through remote procedure calls (RPC). The information returned includes user login name, the system name, login protocol or type, login time, idle time, and remote login location (if applicable). The retrieval of this information is supported by a number of operating systems which support RPC. On most UNIX-based systems (HP-UX, Irix, Linux, Solaris, etc.) the command to retrieve the information is rusers. See your local system documentation for the appropriate usage of this or equivalent command.
shell.delete:0 To toggle shell.delete from 0 to 1, press backSpace 1. The backSpace character is now BACKSPACE
(hexadecimal 08).
shell.quiet:0 This is a v3.X functionality only. quietmode 1 will toggle shell.quiet: 0 to shell.quiet: 1 If quietmode is turned on then no error messages will be forwarded anywhere!
Example 2-9: All of these SNMP parameters are configured using the agtCfgSet command:
snmp.accessList.0.address:0.0.0.0 snmp.accessList.0.rw:1 snmp.accessList.1.address:0.0.0.0 snmp.accessList.1.rw:1 snmp.accessList.2.address:0.0.0.0 snmp.accessList.2.rw:1 snmp.accessList.3.address:0.0.0.0 snmp.accessList.3.rw:1 snmp.accessList.4.address:0.0.0.0 snmp.accessList.4.rw:1 snmp.accessList.5.address:0.0.0.0 snmp.accessList.5.rw:1 snmp.agtParty.0.address:0.0.0.0 snmp.agtParty.0.authPrivSecret:Secret C0de snmp.agtParty.0.index:1 snmp.agtParty.0.port:162 snmp.agtParty.1.address:0.0.0.0 snmp.agtParty.1.authPrivSecret:OrigEquipMfr snmp.agtParty.1.index:2 snmp.agtParty.1.port:162 snmp.agtParty.2.address:0.0.0.0 snmp.agtParty.2.authPrivSecret:private snmp.agtParty.2.index:3 snmp.agtParty.2.port:162 snmp.agtParty.3.address:0.0.0.0
2-31
snmp.agtParty.3.authPrivSecret:public snmp.agtParty.3.index:4 snmp.agtParty.3.port:162 snmp.agtParty.4.address:0.0.0.0 snmp.agtParty.4.authPrivSecret:common snmp.agtParty.4.index:5 snmp.agtParty.4.port:162 snmp.agtParty.5.address:0.0.0.0 snmp.agtParty.5.authPrivSecret:FibreChannel snmp.agtParty.5.index:6 snmp.agtParty.5.port:162 snmp.authentTraps:0 snmp.mibCap:103 snmp.swEventTrapLevel:0 snmp.sysContact:Field Support. snmp.sysDescription:Fibre Channel Switch. snmp.sysLocation:End User Premise snmp.sysObjectID:1588.2.1.1.1 switch.interopMode:0 To toggle interopeMode: sw0:admin> interopeMode; InteropMode: Off ; Usage: InteropMode 0|1; 0: to
turn it off; 1: to turn it on. Enables or disables connection to other vendor switches
switch.largeEntry.cap:0 switch.mail.agent_0.item_112:NONE switch.mail.agent_10.item_112:NONE
Example 2-10: To toggle switch.status.policy parameters type switchStatusPolicySet at CLI.

switch.status.policy.Fans.down:2 switch.status.policy.Fans.marginal:1 switch.status.policy.FaultyPorts.down:2 switch.status.policy.FaultyPorts.marginal:1 switch.status.policy.ISLStatus.down:0 switch.status.policy.ISLStatus.marginal:0 switch.status.policy.MissingSFPs.down:0 switch.status.policy.MissingSFPs.marginal:0 switch.status.policy.PortStatus.down:0 switch.status.policy.PortStatus.marginal:0 switch.status.policy.PowerSupplies.down:2 switch.status.policy.PowerSupplies.marginal:1 switch.status.policy.Temperatures.down:2 switch.status.policy.Temperatures.marginal:1 thresh.alarmsfilter:1
fwAlarmsFilterSet 1 will toggle thresh.alarmsfilter
Use fwConfigure, Web Tools Fabric Watch (FW) configuration tool, or edit configUpload text FW configuration parameters to set FW thresholds:
thresh.cust.env.Fan.above:3 thresh.cust.env.Fan.below:3 thresh.cust.env.Fan.high:3400 thresh.cust.env.Fan.inbetween:1 thresh.cust.env.Fan.unit:RPM thresh.cust.port.Signal.high:120 thresh.cust.port.Signal.low:1 thresh.cust.port.Signal.unit:Error(s) thresh.cust.port.State.above:1 thresh.cust.port.State.below:1 thresh.cust.port.State.exceeded:0 thresh.cust.port.State.high:120 thresh.cust.port.State.low:1 thresh.cust.port.State.tb:2 thresh.cust.port.State.unit:Change(s) thresh.envFan.actLevel:1 thresh.envFan.thLevel:1 thresh.portSignal.actLevel:1 thresh.portSignal.thLevel:1
2-32

thresh.portState.actLevel:1 thresh.portState.thLevel:1 thresh.thad:1 To toggle thresh.thad type configure, then yes to Service Parameters.
xlativeModeDisable:0 To toggle xlativeModeDisable execute configure, then yes to Fabric Parameters change Disable
Translative Mode: (0..1) [0] to 1. To toggle this value change to 0 (on its not disabled) or 1 (off). This parameter is used in conjunction with VC_Encoding to communication with 1st generation 1XXX series switches.
To toggle zoning.check.nodeNameDisabled and zoning.standardMode execute configure, then yes to Zoning Operation parameters.
Standard Mode: (0..1) [0] Disable NodeName Zone Checking: (0..1) [0] zoning.check.nodeNameDisabled:0 Disable NodeName Zone Checking. Specify 1 to disable using Node WWN when specifying nodes in the zone database, or specify 0 to enable using Node WWN when specifying nodes in the zone data. The default value is 0. This value must be set to 1 for interoperability. zoning.standardMode:0 Licenses: RcyzeSbeSgdz0fk
The License output here is the same output displayed from licenceshow and lutil (lutil adds, displays, and removes such licenses):
admin> licenseshow: RcyzeSbeSgdz0fk: Web license Zoning license Fabric Watch license Performance Monitor license Trunking license admin> lutil v (verbose) RcyzeSbeSgdz0fk: Web license Zoning license Fabric Watch license Performance Monitor license Trunking license

configshow: RSCN.end-device.TransmissionMode:0 alpaList:1 cer.internal_port_code:1 diag.burnin.bisr_bad_row:0 diag.burnin.bisr_every:0 diag.burnin.bisr_no_consist:0 diag.burnin.bisr_npass:100 diag.burnin.bisr_on:0 diag.burnin.bisr_red_row:0 diag.burnin.bplb_on:0 diag.burnin.bpt_all_nframes:0 diag.burnin.cam_on:1 diag.burnin.cmi_on:1 diag.burnin.cntmem_on:1 diag.burnin.debug_on:1 diag.burnin.flt_passes:50 diag.burnin.frcslv_on:0
2-33
diag.burnin.label:SYSTEMVERIFICATION diag.burnin.log_length:600 diag.burnin.margin_on:0 diag.burnin.mcy1_nmegs:7 diag.burnin.mcy2_nmegs:7 diag.burnin.mcy5_nmegs:7 diag.burnin.mcy7_nmegs:7 diag.burnin.mcy7_splb_nmegs:0 diag.burnin.min_lb_mode:2 diag.burnin.mnc_lb_mode1:1 diag.burnin.mnc_lb_mode2:2 diag.burnin.mnc_lb_mode7:7 diag.burnin.number_of_runs:1 diag.burnin.plb7_nframes:100 diag.burnin.plb_lb_mode1:1 diag.burnin.plb_lb_mode2:2 diag.burnin.plb_lb_mode7:7 diag.burnin.plb_nframes:100 diag.burnin.post_screen_delay_minutes:0 diag.burnin.prt_on:1 diag.burnin.refclk_on:0 diag.burnin.reset_every:0 diag.burnin.retention_on:1 diag.burnin.screen_cmi_minutes:0 diag.burnin.screen_cmi_nframes:0 diag.burnin.screen_margin_first:0 diag.burnin.screen_margin_second:0 diag.burnin.scrn_plb_nframes:0 diag.burnin.slk_all_nmegs:0 diag.burnin.slk_lb_mode1:1 diag.burnin.sta_passes:25 diag.burnin.tbr_passes:1 diag.burnin.thermal:10 diag.burnin.txd1_nframes:0 diag.burnin.txd2_nframes:0 diag.burnin.txd5_nframes:50 diag.burnin.txd7_nframes:0 diag.burnin.txd_lb_mode1:1 diag.burnin.txd_lb_mode2:2 diag.burnin.txd_lb_mode7:7 diag.burnin.vib:2 diag.burnin.xpt_lb_mode1:1 diag.burnin.xpt_nframes:0 diag.loopID:125 diag.mode.burnin:0 diag.mode.burnin.1.name:burnin diag.mode.burnin.10.name:burnin diag.mode.burnin.2.name:burnin diag.mode.burnin.3.name:burnin diag.mode.burnin.4.name:burnin diag.mode.burnin.5.name:burnin diag.mode.burnin.6.name:burnin diag.mode.burnin.7.name:burnin diag.mode.burnin.8.name:burnin diag.mode.burnin.9.name:burnin diag.mode.burnin.level:0 diag.mode.esd:0 diag.mode.lab:0 diag.mode.mfg:0 diag.postDisable:0 diag.retryDisable:0 diag.test.crossPort.passes:5000 diag.test.passes:0 diag.test.portLoopback.passes:1000 diag.test.silkScreen.passes:180
2-34
diag.test.spinSilk.passes:120 ether.link.mode:AUTO fabric.domain:1 fabric.ididmode:0 fabric.ops.BBCredit:16 fabric.ops.E_D_TOV:2000 fabric.ops.R_A_TOV:10000 fabric.ops.dataFieldSize:2112 fabric.ops.mode.fcpProbeDisable:0 fabric.ops.mode.isolate:0 fabric.ops.mode.longDistance:0 fabric.ops.mode.noClassF:0 fabric.ops.mode.pidFormat:1 fabric.ops.mode.tachyonCompat:0 fabric.ops.mode.unicastOnly:0 fabric.ops.mode.useCsCtl:0 fabric.ops.mode.vcEncode:0 fabric.ops.vc.class.2:2 fabric.ops.vc.class.3:3 fabric.ops.vc.config:0xc0 fabric.ops.vc.linkCtrl:0 fabric.ops.vc.multicast:7 fabric.principalSwSelMode:0 fc4.fcIp.address:0.0.0.0 fc4.fcIp.mask:0.0.0.0 fc4.fcp.productId:FC Switch fc4.fcp.vendorId:BROCADE fcAL.alwaysSendRSCN:0 fcAL.fanFrameDisable:0 fcAL.openSendCLS:4 fcAL.useAltBBCredit:0 flannel.ops.frameColMethod:piling flannel.ops.openBBCredit:4 gen.fabos:0 gen.zone:0 http.javaplugin.homeURL:http://java.sun.com/products/plugin http.javaplugin.version:1,3,1,4 lcdContrast:128 lcdContrast.orange:208 ms.PlatEnable:0 ms.TDEnable:0 oemLogo:0 portCfg:0, 0x10000000; 1, 0x10000000; 2, 0x10000000; 3, 0x10000000; 4, 0x10000000; 5, 0x10000000; 6, 0x10000000; 7, 0x10000000; 8, 0x10000000; 9, 0x10000000; 10, 0x10000000; 11, 0x10000000; 12, 0x10000000; 13, 0x10000000; 14, 0x10000000; 15, 0x10000000; 16, 0x10000000; 17, 0x10000000; 18, 0x10000000; 19, 0x10000000; 20, 0x10000000; 21, 0x10000000; 22, 0x10000000; 23, 0x10000000; 24, 0x10000000; 25, 0x10000000; 26, 0x10000000; 27, 0x10000000; 28, 0x10000000; 29, 0x10000000; 30, 0x10000000; 31, 0x10000000; 32, 0x10000000; 33, 0x10000000; 34, 0x10000000; 35, 0x10000000; 36, 0x10000000; 37, 0x10000000; 38, 0x10000000; 39, 0x10000000; 40, 0x10000000; 41, 0x10000000; 42, 0x10000000; 43, 0x10000000; 44, 0x10000000; 45, 0x10000000; 46, 0x10000000; 47, 0x10000000; 48, 0x10000000; 49, 0x10000000; 50, 0x10000000; 51, 0x10000000; 52, 0x10000000; 53, 0x10000000; 54, 0x10000000; 55, 0x10000000; 56, 0x10000000; 57, 0x10000000; 58, 0x10000000; 59, 0x10000000; 60, 0x10000000; 61, 0x10000000; 62, 0x10000000; 63, 0x10000000; 64, 0x10000000; 65, 0x10000000; 66, 0x10000000; 67, 0x10000000; 68, 0x10000000; 69, 0x10000000; 70, 0x10000000; 71, 0x10000000; 72, 0x10000000; 73, 0x10000000; 74, 0x10000000; 75, 0x10000000; 76, 0x10000000; 77, 0x10000000; 78, 0x10000000; 79, 0x10000000; 80, 0x10000000; 81, 0x10000000; 82, 0x10000000; 83, 0x10000000; 84, 0x10000000; 85, 0x10000000; 86, 0x10000000; 87, 0x10000000; 88, 0x10000000; 89, 0x10000000; 90, 0x10000000; 91, 0x10000000; 92, 0x10000000; 93, 0x10000000; 94, 0x10000000; 95, 0x10000000; 96, 0x10000000; 97, 0x10000000; 98, 0x10000000; 99, 0x10000000; 100, 0x10000000; 101, 0x10000000; 102, 0x10000000; 103, 0x10000000; 104, 0x10000000; 105, 0x10000000; 106, 0x10000000; 107, 0x10000000; 108, 0x10000000; 109, 0x10000000; 110, 0x10000000; 111, 0x10000000; 112, 0x10000000; 113, 0x10000000; 114, 0x10000000; 115, 0x10000000; 116, 0x10000000; 117, 0x10000000; 118, 0x10000000; 119, 0x10000000; 120, 0x10000000; 121, 0x10000000; 122, 0x10000000; 123, 0x10000000; 124, 0x10000000; 125, 0x10000000; 126, 0x10000000; 127, 0x10000000; 128, 0x10000000; 129, 0x10000000; 130, 0x10000000; 131, 0x10000000; 132, 0x10000000; 133, 0x10000000; 134, 0x10000000; 135, 0x10000000; 136, 0x10000000; 137, 0x10000000; 138, 0x10000000; 139,
2-35

142, 148, 154, 160, 166, 172, 178, 184, 190, 196, 202, 208, 214, 220, 226, 232, 238, 244, 250, 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 143, 149, 155, 161, 167, 173, 179, 185, 191, 197, 203, 209, 215, 221, 227, 233, 239, 245, 251, 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 144, 150, 156, 162, 168, 174, 180, 186, 192, 198, 204, 210, 216, 222, 228, 234, 240, 246, 252, 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 0x10000000; 145, 151, 157, 163, 169, 175, 181, 187, 193, 199, 205, 211, 217, 223, 229, 235, 241, 246, 253,
0x10000000; 140, 0x10000000; 141, 0x10000000; 0x10000000; 146, 0x10000000; 147, 0x10000000; 0x10000000; 152, 0x10000000; 153, 0x10000000; 0x10000000; 158, 0x10000000; 159, 0x10000000; 0x10000000; 164, 0x10000000; 165, 0x10000000; 0x10000000; 170, 0x10000000; 171, 0x10000000; 0x10000000; 176, 0x10000000; 177, 0x10000000; 0x10000000; 182, 0x10000000; 183, 0x10000000; 0x10000000; 188, 0x10000000; 189, 0x10000000; 0x10000000; 194, 0x10000000; 195, 0x10000000; 0x10000000; 200, 0x10000000; 201, 0x10000000; 0x10000000; 206, 0x10000000; 207, 0x10000000; 0x10000000; 212, 0x10000000; 213, 0x10000000; 0x10000000; 218, 0x10000000; 219, 0x10000000; 0x10000000; 224, 0x10000000; 225, 0x10000000; 0x10000000; 230, 0x10000000; 231, 0x10000000; 0x10000000; 236, 0x10000000; 237, 0x10000000; 0x10000000; 242, 0x10000000; 243, 0x10000000; 0x10000000; 248, 0x10000000; 249, 0x10000000; 0x10000000; 254, 0x10000000; 255, 0x10000000; quickLoop.holdOpenInit:0 quickLoop.noAlpaZero:0 quickLoop.peerWWN:00:00:00:00:00:00:00:00 quickLoop.portBitmap:0x0000000000000000 quickLoop.softInit:0 rlsDisable:1 route.delayReroute:0 route.embeddedPortBcast:1 route.stickyRoutes:0 rpc.rapid:1 rpc.rstatd:0 rpc.rusersd:0 sec.fstov:5000 sec.mode:0 sec.versionStamp:0 shell.delete:0 shell.quiet:0 snmp.accessList.0.address:0.0.0.0 snmp.accessList.0.rw:1 snmp.accessList.1.address:0.0.0.0 snmp.accessList.1.rw:1 snmp.accessList.2.address:0.0.0.0 snmp.accessList.2.rw:1 snmp.accessList.3.address:0.0.0.0 snmp.accessList.3.rw:1 snmp.accessList.4.address:0.0.0.0 snmp.accessList.4.rw:1 snmp.accessList.5.address:0.0.0.0 snmp.accessList.5.rw:1 snmp.agtParty.0.address:0.0.0.0 snmp.agtParty.0.authPrivSecret:Secret C0de snmp.agtParty.0.index:1 snmp.agtParty.0.port:162 snmp.agtParty.1.address:0.0.0.0 snmp.agtParty.1.authPrivSecret:OrigEquipMfr snmp.agtParty.1.index:2 snmp.agtParty.1.port:162 snmp.agtParty.2.address:0.0.0.0 snmp.agtParty.2.authPrivSecret:private snmp.agtParty.2.index:3 snmp.agtParty.2.port:162 snmp.agtParty.3.address:0.0.0.0 snmp.agtParty.3.authPrivSecret:public snmp.agtParty.3.index:4 snmp.agtParty.3.port:162
2-36

snmp.agtParty.4.address:0.0.0.0 snmp.agtParty.4.authPrivSecret:common snmp.agtParty.4.index:5 snmp.agtParty.4.port:162 snmp.agtParty.5.address:0.0.0.0 snmp.agtParty.5.authPrivSecret:FibreChannel snmp.agtParty.5.index:6 snmp.agtParty.5.port:162 snmp.authentTraps:0 snmp.mibCap:3943 snmp.swEventTrapLevel:0 snmp.sysContact:Field Support. snmp.sysDescription:Fibre Channel Switch. snmp.sysLocation:End User Premise. snmp.sysObjectID:1588.2.1.1.1 switch.interopMode:0 switch.largeEntry.cap:0 switch.status.policy.Blade.down:0 switch.status.policy.Blade.marginal:1 switch.status.policy.CP.down:0 switch.status.policy.CP.marginal:1 switch.status.policy.Fans.down:2 switch.status.policy.Fans.marginal:1 switch.status.policy.FaultyPorts.down:2 switch.status.policy.FaultyPorts.marginal:1 switch.status.policy.ISLStatus.down:0 switch.status.policy.ISLStatus.marginal:0 switch.status.policy.MissingSFPs.down:0 switch.status.policy.MissingSFPs.marginal:0 switch.status.policy.PortStatus.down:0 switch.status.policy.PortStatus.marginal:0 switch.status.policy.PowerSupplies.down:3 switch.status.policy.PowerSupplies.marginal:0 switch.status.policy.Temperatures.down:2 switch.status.policy.Temperatures.marginal:1 switch.status.policy.WWN.down:0 switch.status.policy.WWN.marginal:1 thresh.thad:1 ts.clockServer:LOCL ts.tzh:0 ts.tzm:0 xlativeModeDisable:0 zoning.check.nodeNameDisabled:0 zoning.standardMode:0 Licenses: bccSReQd9Q6ddTSF
2-37
Date
Available in Fabric OS versions: v3.1.0+ and v4.1.0+ Version Differences: Linux kernel switches have UTC in output Additional Example/Case Studies: v3.1 Example Output: Example 2-13:
Date Wed Feb 12 17:17:57 2003
Troubleshooting Use: v4.2 Example Output: Example 2-14:

Date: Wed Dec 31 19:33:35 UTC 2003
Note:
The date at the top of diagshow output was the only way to determine the capture date of the supportshow output prior to Fabric OS versions containing date output as part of supportshow
2-38
dbgshow
Available in Fabric OS versions: v4.2 (system command group) Troubleshooting Use: Turn Additional Information: Note: Generally you should turn on debug if you know which module you are investigating. The command dbgShow will show you all the modules you can enable. In general there are 1-9 levels of debug. Each level enables more debug 1 being for errors to 9 being for important data at which all debug statements are enabled. A word of caution, some modules have lots of debug and enabling them at level 9 may cause the switch to reboot.
on debug if you know which module you are investigating.
Note:
VxWorks: setdbg <module_name>, <debug_level> Note the double quotes around the module name.
Note:
Linux: setdbg <module_name>, <debug_level>
Note:
See the help pages for dbgShow and setDbg.

dbgshow: Module FKIO_LIB,debug level = Module CFGLOADER,debug level = Module ERRLOG,debug level = Module SYSC,debug level = Module FSSME,debug level = Module PDM,debug level = Module FSS,debug level = Module IOT,debug level = Module uSWD,debug level = Module ulSWD,debug level = Module FAB_IPC,debug level = Module HMON,debug level = Module DIAGD,debug level = Module EM,debug level = Module HAM,debug level = Module UPG,debug level = Module HB,debug level = Module HAMLIB,debug level = Module IPADMLIBRARY,debug level Module FSPF,debug level = Module FLOOD,debug level = Module HLO,debug level = Module MPATH,debug level = Module UPATH,debug level = Module MCAST,debug level = Module UCAST,debug level = Module NBFSM,debug level = Module LSDB,debug level = Module FSPF_HA,debug level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = = 0, verbose level 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0, verbose level = 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 = 0 0 0 0 0 0 0 0 0 0 0
2-39
Module SYS,debug level = 0, verbose level = 0 Module PANIC,debug level = 0, verbose level = 0 Module FSPF_IPC,debug level = 0, verbose level = 0 Module ARR,debug level = 0, verbose level = 0 Module NS,debug level = 0, verbose level = 0 Module NSCAM,debug level = 0, verbose level = 0 Module NSZNCHK,debug level = 0, verbose level = 0 Module NSLIB,debug level = 0, verbose level = 0 Module MQ,debug level = 0, verbose level = 0 Module FCP_IPC,debug level = 0, verbose level = 0 Module NS_RTWR,debug level = 0, verbose level = 0 Module NS_PSD,debug level = 0, verbose level = 0 Module FC_ASYNC,debug level = 0, verbose level = 0 Module FABRIC,debug level = 0, verbose level = 0 Module FCLS,debug level = 0, verbose level = 0 Module AS,debug level = 0, verbose level = 0 Module MS,debug level = 0, verbose level = 0 Module SECLIB,debug level = 0, verbose level = 0 Module TSLIB,debug level = 0, verbose level = 0 Module MS_RTWR,debug level = 0, verbose level = 0 Module MS_ARF,debug level = 0, verbose level = 0 Module MSFICON,debug level = 0, verbose level = 0 Module PATHINFO,debug level = 0, verbose level = 0 Module PS,debug level = 0, verbose level = 0 Module PSH,debug level = 0, verbose level = 0 Module PSR,debug level = 0, verbose level = 0 Module PSHA,debug level = 0, verbose level = 0 Module PS_PROCLOCK,debug level = 0, verbose level = 0 Module PS_RTWR,debug level = 0, verbose level = 0 Module RCS,debug level = 0, verbose level = 0 Module RCS_RTWR,debug level = 0, verbose level = 0 Module EVMD,debug level = 0, verbose level = 0 Module FCPD,debug level = 0, verbose level = 0 Module SES,debug level = 0, verbose level = 0 Module ERRLOGD,debug level = 0, verbose level = 0 Module TRACK,debug level = 0, verbose level = 0 Module FDMI,debug level = 0, verbose level = 0 Module SLAP,debug level = 0, verbose level = 0 Module SEC,debug level = 0, verbose level = 0 Module PKI,debug level = 0, verbose level = 0 Module WEBD,debug level = 0, verbose level = 0 Module SNMP,debug level = 0, verbose level = 0 Module CMD,debug level = 0, verbose level = 0 Module FW,debug level = 0, verbose level = 0 Module THA,debug level = 0, verbose level = 0 Module PS_FWD,debug level = 0, verbose level = 0 Module FWD_PROCLOCK,debug level = 0, verbose level = 0 Module ZONE,debug level = 0, verbose level = 0 Module ZS,debug level = 0, verbose level = 0 Module ZONE_RTWR,debug level = 0, verbose level = 0 Module ZONE_SM,debug level = 0, verbose level = 0 Module ZONE_MR,debug level = 0, verbose level = 0 Module ZONE_PROG,debug level = 0, verbose level = 0 Module ZONE_HA,debug level = 0, verbose level = 0 Module TS,debug level = 0, verbose level = 0 Module HTTPD,debug level = 0, verbose level = 0 Module PROXYFCG,debug level = 0, verbose level = 0 Module IPADM,debug level = 0, verbose level = 0 Module RPCD,debug level = 0, verbose level = 0 Module PLATFORM,debug level = 0, verbose level = 0 Module FABSYS,debug level = 0, verbose level = 0 Module PANIC,debug level = 0, verbose level = 0 Module SWITCH,debug level = 0, verbose level = 0 Module CER,debug level = 0, verbose level = 0 Module CERHA,debug level = 0, verbose level = 0
2-40

Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module Module SCN,debug PORT,debug FCIU,debug FCPH,debug EXCH,debug FCLS,debug FCSW,debug FCRT,debug FCCT,debug FCP,debug FCIP,debug LOGI,debug BLADE,debug BPORT,debug CHIPS,debug MINIS,debug LOOM,debug BLOOM,debug INTR,debug PHAN,debug LOOP,debug SPEED,debug RCV,debug XMT,debug DIAG,debug FLTR,debug HA,debug TRUNK,debug DMA,debug FMF,debug ERRLOG,debug PORTLOG,debug DIAGD,debug DBGLOG,debug kSWD,debug uSWD,debug FCMISC,debug HAMKERNEL,debug SYNC_SWC,debug RCVY_SWC,debug FSSK,debug PORTSWAP,debug level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose verbose level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level level = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
2-41
diagShow
Available in Fabric OS versions: All Version Differences: There are version differences in the format of the output and in the syntax:
v3.0: diagshow [nSeconds] v4.0: diagshow [-slot slot][-uports itemlist][-bports itemlist] [-use_bports value]
Troubleshooting Use: Use this command to print diagnostic results since the last boot. It also contains the date of the capture and information on number of frames transmitted (tx) and received (rx) along with associated low level interupts (LLIs). This command prints the following information since the switch was last rebooted: 1. The state of all ports in the switch based on the results of diagnostic executions since the last reboot. Ports which passed diagnostic testing are marked OK. Ports which failed one or more diagnostic tests are marked BAD. Once a port is mark BAD it needs to be cleared by executing the diagclearerror command. If it is not cleared subsequent tests will fail, even if the faulty condition is removed.
Note:
2. 3.
The current state of the ports: active ports are shown as UP and inactive ports are shown as DN. The Frame counts of active ports. The number of frames transmitted are indicated by frTx and the number of frames received are indicated by frRx. The LLI_errs is the sum of the ports eight statistic error counters: ENC_in, CRC_err, TruncFrm, FrmTooLong, BadEOF, Enc_out, BadOrdSet, DiscC3
4. 5.
The state of the Central Memory based on the results of diagnostic executions since the last reboot. OK is displayed if previous centralMemoryTest executions passed. FAULTY is displayed if the switch failed centralMemoryTest. The Total diagnostic frames transmitted and received since last reboot. The sums represent the cumulative number of frames transmitted and received by the diagnostic functional tests (portLoopbackTest, crossPortTest (or spinSilk for the transmitted count only)) for all ports since the last reboot. For example, if the switch is rebooted with POST disabled, diagShow will show the total as 0. The values are not necessarily equal. They are not equal when an error occurs in one of the ports during one of the tests above. This command may also be executed via the s (Stats) option of the QCSL - diag prompt which is generated when a diagnostic test is keyboard interrupted. This command may also be looped by specifying the display intervals (in seconds) as the first argument. For example diagShow 4 executes diagShow every 4 seconds continuously unless stopped by a keyboard interrupt. This may be used to isolate a bad GBIC. A port with changing LLI_errs value prefixed by ** indicates port is detecting more errors. v3.x Example Output: Example 2-16:
diagShow 0 Diagnostics port#: 0 diags: OK state: UP speed: 2G Status: Thu Oct 17 1 2 3 4 5 OK OK OK OK OK UP UP UP UP UP 2G 1G 2G 2G 2G frTx107084405 frTx107090193 frTx 29565015 frTx 7349761 frTx 2011177 frTx 859950 frTx 36419372 15:24:01 2002 (Note: this is supportShow capture date) 6 7 8 9 10 11 12 13 14 15 OK OK OK OK OK OK OK OK OK OK UP UP UP DN UP UP UP UP UP UP 2G 2G 2G 2G 2G 2G 2G 2G 2G 2G 38 39 1619 95825 22 35 78 LLI_errs. LLI_errs. LLI_errs. LLI_errs. LLI_errs. LLI_errs. LLI_errs.
pt0: 43036276 pt1: 35673191 pt2: 70084586 pt3: 10575553 pt4: 3009638 pt5: 1376961 pt6:108459734
frRx frRx frRx frRx frRx frRx frRx
2-42

pt7: pt8: pt10: pt11: pt12: pt13: pt14: pt15: 8352074 frTx 8352358 frTx 103004 frTx 8184489 frTx 80614266 frTx 8737327 frTx 23116364 frTx 21436681 frTx 5070104 frRx 5074068 frRx 69219 frRx 4875626 frRx 10923977 frRx 20781940 frRx 46936163 frRx 47017360 frRx 29 LLI_errs. 20 LLI_errs. 77 LLI_errs. 35 LLI_errs. 54 LLI_errs. 133 LLI_errs. 37 LLI_errs. 38 LLI_errs.
Central Memory OK Total Diag Frames Tx: 3472 Total Diag Frames Rx: 5068 Total Diag Frames Rx: 136112
This view is from a production SAN. If diagnostics were running you would see ptx loopback information:
pt0: 100 frTx pt7: 100 frTx 100 frRx 100 frRx 0 LLI_errs. <looped-7> 0 LLI_errs. <looped-0>
Note:
Ports can be put in loopback mode using the portcfgmcastloopback command.
Look for rapidly rising LLI_errs, check porterrshow output to determine which statistical counters generated the errors. Clear some of the statistical counters on the same quad using portstatsclear <port #>, portstatsclear is an undocumented command so is subject to change by Fabric OS versions: not all Fabric OS versions clear port stats in the same format, some clear 2 or 3 ports per quad. If port statistics continue to rise, move the cable to another port. If the problem follows the cable then suspect a faulty cable or attached media (GBIC/SFP/HBA and/or HBA driver). If the problem disappears, run crossporttest with a loopback plug in online/verbose mode to determine if the GBIC/SFP or port is faulty. Crossporttest, spinsilk and portloopback tests can also be run offline, internally looped to test the port /ASIC.

diagshow of slot 1: Diagnostics Status: Slot: 1 UPORTS Port BPort 1/0 7 1/1 6 1/2 5 1/3 4 1/4 15 1/5 14 1/6 13 1/7 12 1/8 23 1/9 22 1/10 21 1/11 20 1/12 31 1/13 30 1/14 29 1/15 28 Wed Dec 31 19:34:04 2003
Diag OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK
Active DN UP DN DN DN DN DN DN DN DN DN DN DN DN DN DN
Speed 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto
FrTX -1334895 ---------------
FrRX -813241 ---------------
LLI Errs -1306 ---------------
Loopback
Central Memory: OK Total Diag Frames Tx: 0 Total Diag Frames Rx: 0 Slot: 2 UPORTS
2-43
2
Port 2/0 2/1 2/2 2/3 2/4 2/5 2/6 2/7 2/8 2/9 2/10 2/11 2/12 2/13 2/14 2/15

BPort 7 6 5 4 15 14 13 12 23 22 21 20 31 30 29 28 Diag OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK OK Active DN DN DN DN DN DN DN DN DN DN DN DN DN DN DN DN Speed 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto 2G Auto FrTX ----------------FrRX ----------------LLI Errs ----------------Loopback
2-44
errDump
Available in Fabric OS versions: All Version Differences: VxWorks switch outputs will have a small t in the front of the task name. VxWorks switches have an active error log only. Troubleshooting Use: The output of the errdump command includes the display of errors/events history recorded in the persistent error log and error/events logged in the current run time cycle. This command also provides options to display ONLY those error/event messages that are saved in the persistent error log, or ONLY those messages generated during the current run time cycle. All important error log messages, regardless of their message severity level, are stored in a persistent storage as they are logged. Both the persistent error log and the run time log are limited in space and managed as circular buffers. When either log overflows, old entries are replaced by new entries. A troubleshooting best practice includes forwarding these error logs to a host in the SAN using the syslogd capability of the switch. The persistent error log is saved across system reboots and power cycles and can be resized at run time. The error log tells a story about what happens in the fabric especially if fabric watch is used (see notes below). Use Brocade diagnostic and error message guides to interpret the output of errdump. Note: When this command is executed from the Standby CP of a Silkworm 12000, the switch instance number operand is required. The switch instance number is supplied by specifying the <-s swinst> operand. This operand is not required when logged into the Active CP. The active error Log has been enhanced to save a maximum of 1536 messages in RAM, that is, a total of 256 messages for each error message level (Panic, Critical, Error, Warning, Info, and Debug) In addition, 1024 to 2048 important messages can be stored in a separate persistent error log to guarantee that they are not lost in case of power outage or system reboot
Notes for error messages 105 through 107: The partial errdump Examples #8 below shows a log with the latest active error entries and the latest persistent error entries. See notes associated with the entries, reading from error message 105 and up. Example 2-18: v4.1 errdump -a:
errdump -a:
The following error 107, shows another Fabric Watch warning for the same port (port 10). It lets us know that the state changes per minute went below the set threshold. Its back to normal.
Error 107 -------0x32c (fabos): Oct 17 22:21:35 Switch: 0, Warning FW-BELOW, 3, fopportState010 (FOP Port State Changes 10) is below low boundary. current value : 0 Change(s)/minute. (normal)
The following error 106, shows another Fabric Watch warning for the same port (port 10), it says fopportState010, the Fopport tells us its an F, optical port and the State represents a state change message on 010 port 10. It reads in as FW_ABOVE and (faulty). There must be a threshold configured to notify when you go above x state changes (and that x must be 3 or lower per minute because that is what its reporting.3 changes per minute. A link failure will cause multiple state changes. The State Changes area counts the number of times that a port has gone offline or online; has been testing or faulty; has become an E_Port or F_Port; has joined a trunk; or has segmented. In this case the port went offline, came back online and then became an F_Port causing 3 state changes.
Error 106 -------0x32c (fabos): Oct 17 22:20:03 errDump (Cont.) Switch: 0, Warning FW-ABOVE, 3, fopportState010 (FOP Port State Changes 10) is above high boundary. current value : 3 Change(s)/minute. (faulty)
2-45
Error 105 shows a Fabric Watch link failure LF message (faulty) for an optical port above a set high boundary. The site log shows that the cable was pulled at this time to insert a FC analyzer.
-------0x32c (fabos): Oct 17 22:20:03 Switch: 0, Warning FW-ABOVE, 3, fopportLink010 (FOP Port Link Failures 10) is above high boundary. current value : 1 Error(s)/minute. (faulty)
Notes for error messages 97 104: Read the curved notes from 97 up.
Error 104 shows FW reporting that the switch is now healthy. -------0x32c (fabos): Oct 17 17:45:36 Switch: 0, Warning FW-STATUS_SWITCH, 3, Switch status changed from Marginal/Warning to HEALTHY/OK
Error 103 shows the high availability monitor kernal reading that the heartbeat between CPs is up.
-------0x2e0 (fabos): Oct 17 17:45:36 Switch: 0, Debug HAMKERNEL-IP_UP, 5, (session=12) Heartbeat up from Standby CP
Error 102 shows the high availability monitor registering that the CP in slot 5 is syncing up.going to redundant state
-------0x2e0 (fabos): Oct 17 17:45:33 Switch: 0, Info HAM-REDUNDANT_INFO, 4, (Heartbeat Up) System in REDUNDANT state
Error 101 shows CP in slot 5 that was just inserted again being set to faulty, its still trying to sync up with CP slot 6.
-------0x2c6 (fabos): Oct 17 17:43:26 Switch: 0, Error EM-CP_ERR, 2, CP in slot 5 set to faulty because of CP ERROR
Error 100 shows the high availability monitor kernal responding to CP in slot 5 being faulty, its still trying to sync up with CP slot 6.
-------0x0 (fabos): Oct 17 17:43:26 Switch: 0, Info HAMKERNEL-NON_REDUNDANT, 4, (session=11) Reset Standby CP due to CP error interrupt (hamStatus=2e1)
Error 99 shows CP in slot 5 that was just inserted being set to faulty, its trying to sync up with CP slot 6.
-------0x2c6 (fabos): Oct 17 17:34:48 Switch: 0, Error EM-CP_ERR, 2, CP in slot 5 set to faulty because of CP ERROR
Error 98 shows the high availability monitor kernal responding to the insertion.
-------0x0 (fabos): Oct 17 17:34:47 Switch: 0, Info HAMKERNEL-NON_REDUNDANT, 4, (session=11) Reset Standby CP due to CP error interrupt (hamStatus=2e1)
Error 97 shows a FRU insertion on slot 5 which is reserved for CPs, check historyshow for correlating message.
-------0x2c6 (fabos): Oct 17 17:28:56 Switch: 0, Info EM-FRU_INS, 4, Slot #5 insertion detected.
2-46
Notes for partial persistent log error messages 65 67: Notice that these last 3 persistent messages match active error messages 99 101, the additional active error messages (101 107) had not been read into the persistent error log at the time this supportshow capture. The default level for entry into the persistent log is 1 which means that, by default, only levels 1 and 0 are recorded into the persistent log. The persistent error log here has been set to at least level 4 and above by executing errsavelvlset 4 at the command line. This means that all level 0 4 error levels will be read into this log. Example 2-19: v4.1 errdump -p
errdump -p: Error 67 -------0x2c6 (fabos): Oct 17 17:43:26 Switch: 0, Error EM-CP_ERR, 2, CP in slot 5 set to faulty because of CP ERROR Error 66 -------0x0 (fabos): Oct 17 17:43:26 Switch: 0, Info HAMKERNEL-NON_REDUNDANT, 4, (session=11) Reset Standby CP due to CP error interrupt (hamStatus=2e1) Error 65 -------0x2c6 (fabos): Oct 17 17:34:48 Switch: 0, Error EM-CP_ERR, 2, CP in slot 5 set to faulty because of CP ERROR
Fabric OS v4.0.2 related commands include: errDump errShow Displays the error log without page breaks Displays the error log in with page breaks
ErrDump/Show s 0 a or p Displays the active (-a) or persistent (-p) error log for logical switch 0 from the non- active CP (-s switch instance, or logical switch number. In this case logical switch 0 was specified) errClear An ADMIN level command that clears the error log. The s 0 or 1 and a an p operands can be used here as well. This was a root level command on v3.x OS switches.
ErrSaveLvlShow/Set This command shows and sets the error message levels that will be sent to the persistent error log. Example 2-11: errSaveLvlSet examples:
sw0:admin> errSaveLvlShow Current message save level is = 1 sw0:admin> errsavelvlset 3 sw0:admin> errSaveLvlShow Current message save level is = 3
ErrNvLogSizeShow/Set This command shows and sets the max size of the persistent error log. The default is 1024, the range is 1024 to 2048. Example 2-12: errNvLogSizeShow/Set examples:
switch:admin> errNvLogSizeShow Persistent Error Log can store 1024 entries switch:admin> errNvLogSizeSet 2048 Persistent error log is resized to store 2048 entries switch:admin> errNvLogSizeShow Persistent Error Log can store 2048 entries switch:admin> errNvLogSizeSet 2148 Can not set persistent log size to more than 2048 entries
fwAlarmsFilterSet 0/1 Sets alarms filtering for Fabric Watch (0 = off; 1 =on)2, if off FW alarms will not be sent to the error log
2-47
trackChangesSet [ mode ], [ snmp-trap mode ] Enables track-changes feature if the mode operand is a 1 and disables track-changes feature if the mode operand is a 0. A SNMP-TRAP can similarly be enabled and disabled. The error output has highly valuable information, especially when used in conjunction with the Brocade Diagnostic and System Message and the Responding to FW messages Guides. The error log is used to check for segmentation problems, reboot reasons, temperature and other environment warnings, hardware error condition, switch status, high availability messages, and track changes information if track changes are enabled. Also see decoded examples and names/ pages numbers of these decoding references in the V3.0 errdump section: v4.2 Example Output: Example 2-20: errdump -a
errdump -a: Error 29 -------0x258 (fabos): Dec 31 10:18:11 Switch: 0, Info EM-FRU_REM, 4, FRU Slot #3 removal detected. Error 28 -------0x39b (fabos): Dec 30 14:55:44 Switch: 0, Warning SULIB-FWDL_END, 3, Firmwaredownload command has completed successfully. Error 27 -------0x39b (fabos): Dec 30 14:53:21 Switch: 0, Info SULIB-CP_REBOOT_OK, 4, Standby CP rebooted successfully. Error 26 -------0x238 (fabos): Dec 30 14:53:15 Switch: 0, Info FSSME-HA_IN_SYNC, 4, HA State is in sync!
Example: errdump -p
errdump -p: Error 52 -------0x258 (fabos): Dec 31 10:18:11 Switch: 0, Info EM-FRU_REM, 4, FRU Slot #3 removal detected. Error 51 -------0x39b (fabos): Dec 30 14:55:44 Switch: 0, Warning SULIB-FWDL_END, 3, Firmwaredownload command has completed successfully. Error 50 -------0x39b (fabos): Dec 30 14:53:21 Switch: 0, Info SULIB-CP_REBOOT_OK, 4, Standby CP rebooted successfully. Error 49 -------0x238 (fabos): Dec 30 14:53:15 Switch: 0, Info FSSME-HA_IN_SYNC, 4, HA State is in sync! Error 48 -------0x0 (fabos): Dec 30 14:53:00 Switch: 0, Info HAMKERNEL-HTBT_UP, 4, Heartbeat up
2-48
fablogdump
Available in Fabric OS versions:v3.0 and v3.1 Version Information: The output of this command is similar to the output of version 4.1 fabstateshow v4.2 Example Output: NA Troubleshooting Use: Use this command to display switch State Change Information read output from bottom up See fabstateshow embedded notes for additional information. Note: This command has no additional Fabric OS information at this time but the information displayed in this output is very similar to the output that is displayed in Fabric OS 4.1 fabstateshow output which is documented in this document. As the information becomes available command and command information will be inserted in this section.
Example 2-21: v3.1.2 output

22:17:46.926 22:17:46.942 22:17:46.959 22:17:46.959 22:17:46.959 22:17:46.976 22:17:47.359 22:17:50.359 22:17:50.442 22:17:50.492 22:17:50.509 22:17:50.642 22:17:50.642 22:17:50.642 22:17:50.642 22:17:50.676 22:17:50.646 22:17:50.646 22:17:51.929 tFabric tFabric tTransmit tFabric tFabric tFabric tFabric tFabric tTransmit tTransmit tFabric tFabric tFabric tFabric tFabric tFabric tFabric tFabric tTransmit 11 12 0 0 14 15 0 0 0 0 0 255 255 16 0 0 16 16 0 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000084 00000000 04000001 04000881 00000000 00000000 00000010 04000881 00000881 00000000 00000000 00000881 Fabric rcvd Offline SCN Fabric rcvd Offline SCN ELP received Sent ELP Fabric rcvd Offline SCN Fabric rcvd Offline SCN Fabric rcvd Online SCN ELP unsuccessful - Async state 0x84 EFP received AAI received RDI sent AAI flood started AAI flood end Fabric rcvd Online SCN Sent EFP Fabric rcvd Online SCN EFP flood started EFP flood end EFP received
2-49
fabportshow
Available in Fabric OS versions: v4.1, v4.2 Version Information: V3.1 plus switches have a similar output that can be viewed from the CLI. See Example 2-23 Troubleshooting Use: Use this command to display the contents of a particular port data and also any pending commands (if applicable). The following information is displayed: Port State P0 P1 P2 P3 I0 I1 I2 I3 T0 T1 T2 List Flags 0x00000001 Displays the port number. The state of the port: Port Offline Port Online ELP ACC Received Link Reset Done Trunk Initiator: EMT Sent Trunk Initiator: ETP ACC Received Trunk Initiator: ETP Sent Trunk Initiator: Link Reset Trunk Target: EMT Received Trunk Target: ETP Received Trunk Target: Link Reset IU list pointer. Port flags: slave connection
0x00000002 loop back connection 0x00000004 incompatible connection 0x00000008 overlapping domains 0x00000010 overlapping zones 0x00000020 done PTIO ioctl 0x00000040 sent a RJT to ELP 0x00000080 BF received from the port 0x00000200 segmented by routing code 0x00000800 zoning has completed 0x00001000 segmented by Platform Management 0x00002000 segmented due to no license 0x00004000 segmented due to E_Port disabling 0x00008000 DIA already sent for that port 0x00010000 RDI already sent 0x00020000 port is true T port 0x00040000 Port received an ELP 0x00080000 Port received an ELP RJT 0x00100000 LR Pending due to ELP RJT rcv 0x00200000 Received a DIA on this port 0x00400000 Port is the EMT Initiator 0x00800000 Security violation 0x01000000 Security incompatibility
2-50
Fabric OS SupportShow Information 0x02000000 Rcv a DIA ACC nbrWWN red_ports Neighboring switch's WWN All E-Ports that are connected to the same neighboring switch.
Example 2-13: To display fabric port information:

switch:admin> fabportshow 4/14 Fabric Port Information: ======================== Port: 62 State: P3 List: 0x10068418 List Count: 0 Flags: 0x280120 nbrWWN: 10:00:00:60:69:80:06:cf red_ports: 10 11 62 63 Open commands pending: ====================== No commands pending switch:admin>
Example 2-14:
fabportshow: appears in supportshow output for each port: fabportshow: fabportshow 2 0: Fabric Port Information: ======================== Port: State: List: List Count: Flags: nbrWWN: lr_tid: red_ports: 16 P0 0x1004d430 0 0x0 00:00:00:00:00:00:00:00 0x1004d520, IDLE STATE
Port Area number State Possibilities include: P, Pn -> current port state and next port state. Possible port states include: P0 Port offline or in initial state P1 Port online P2 Send /receive ELP accept P3 Receive active port state I0 - exchange trunk time stamp. I1 Receive time stamp accept, then send trunk parameters I2 Receive trunk parameter accept, transition to I3, and link reset port I3 Wait for port active state. T0 Receive trunk time stamp T1 Receive trunk parameter. T2 Send trunk parameter accept
2-51
Fabric OS SupportShow Information T3 Wait for port active state. LD After sending an ECP (Exchange Credit Parameters). This is for dynamic long distance VC Credit assignment.
List A list pointer that contains entries of pending commands sent out. List count The number of commands pending. Flags Private Brocade Engineering flags - see port flags list above. Lr_tid A Link Reset timer pointer. Red_ports Redundant E-Ports that are connected to the same switch. NbrWWN The WWN of the neighboring switch, only set if port state reaches P3 state. What are possible outputs and meanings of same for each? Expected output when port comes online is that the port state is not in P0 state. For Trunk Masters and E-Ports not segmented, port states should end at P3 state. When would I see a problem? 1) If port is at P3 state, and nbrWWN is all zero. 2) If fabric is stable with no fabric frames sent, that the list count should be zero, else a possible memory leak. 3) If port information read doesnt match switchShow output.

fabportshow: fabportshow internal port(128): Fabric Port Information: ======================== Port: State: List: List Count: Flags: nbrWWN: lr_tid: red_ports: 128 NA 0x10057a50 0 0x0 00:00:00:00:00:00:00:00 0x10057b40, IDLE STATE
Open commands pending: ====================== No commands pending
Additional Example/Case Studies: This is a v3.1.2 fabportshow, non-supportshow command output example. Much of the information shared above applies. Example 2-23: v3.1.2 output
22:17:46.926 22:17:46.942 22:17:46.959 22:17:46.959 22:17:46.959 22:17:46.976 22:17:47.359 22:17:50.359 22:17:50.442 tFabric tFabric tTransmit tFabric tFabric tFabric tFabric tFabric tTransmit 11 12 0 0 14 15 0 0 0 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000084 00000000 Fabric rcvd Offline SCN Fabric rcvd Offline SCN ELP received Sent ELP Fabric rcvd Offline SCN Fabric rcvd Offline SCN Fabric rcvd Online SCN ELP unsuccessful - Async state 0x84 EFP received
2-52

22:17:50.492 22:17:50.509 22:17:50.642 22:17:50.642 22:17:50.642 22:17:50.642 22:17:50.676 22:17:50.646 22:17:50.646 22:17:51.929 tTransmit tFabric tFabric tFabric tFabric tFabric tFabric tFabric tFabric tTransmit 0 0 255 255 16 0 0 16 16 0 04000001 04000881 00000000 00000000 00000010 04000881 00000881 00000000 00000000 00000881 AAI received RDI sent AAI flood started AAI flood end Fabric rcvd Online SCN Sent EFP Fabric rcvd Online SCN EFP flood started EFP flood end EFP received
2-53
fabricShow
Available in Fabric OS versions: All Troubleshooting Use: Use this command to display fabric membership information Use this command to display information about switches and multicast alias groups in the fabric. Multicast alias groups are created on demand by request from N_Ports attached to the alias server; typically no groups are listed. If the switch is initializing, or disabled, the message no fabric is displayed. If the fabric is reconfiguring, some or all switches may not be shown. Otherwise, the following fields are shown: Switch ID Enet IP Addr FC IP Addr Name Group ID Token The switch Domain_ID and embedded port D_ID. The switch ethernet IP address. The switch FC IP address. The switch symbolic name. An arrow (>) indicates the principal switch. The alias group number and D_ID. The alias group token (assigned by the N_Port). Worldwide Name The switch WWN.
If multicast alias groups exist, the following fields are shown:
Additional Example/Case Studies: v3.x Example Output: Example 2-15:

fabricShow Switch ID Worldwide Name Enet IP Addr FC IP Addr Name ------------------------------------------------------------------------6: fffc06 10:00:00:60:69:80:64:5a 10.134.150.8 0.0.0.0 "cfs001a" 7: fffc07 10:00:00:60:69:80:64:5b 10.134.150.9 0.0.0.0 "cfs001b" 11: fffc0b 10:00:00:60:69:51:a3:ba 10.134.150.15 0.0.0.0 "efs001" 13: fffc0d 10:00:00:60:69:51:b3:1a 10.134.150.17 0.0.0.0 "efs003" 15: fffc0f 10:00:00:60:69:51:43:66 10.134.150.19 0.0.0.0 "efs005" 17: fffc11 10:00:00:60:69:51:43:c0 10.134.150.21 0.0.0.0 >"efs007"
Note:
Use this in the host doesnt see storage scenario. Check that the host is in the same Fabric as the storage. This output can also be used to match fabric output to customer drawings. Use it, topologyshow and nsallshow to get a high level picture of the fabric. The portlogdump output can also be used in conjunction with fabricshow output to track misbehaving fabric devices - you will have to come to fabricshow output to determine which switch the misbehaving device is attached to. It would be easier to track fabric problems if the switch name had the domain id in it.
Note:
The fffcdd is the 24-bit address of the embedded port (also called domain controller or switch id) for this switch. The dd value is the domain id of the switch in hex. The Switch ID column left of : represents the switches domain, in the example above, fffc0b represents the embedded port for domain 11 and fffc11 represents the domain id for domain 17 and so on. The > symbol points to the principle fabric switch which maintain domain integrity and pulls and pushes time services to all switches in the fabric so make sure this principle switch is pointing to an accurate time server. A fabric principal switch can be set on v4.1 plus switches - see fabswitchShow on page 2-64 for standards information about fabric principal switch selection.
2-54

fabricshow: Switch ID Worldwide Name Enet IP Addr FC IP Addr Name ------------------------------------------------------------------------1: fffc01 10:00:00:60:69:80:2d:4a 10.64.148.32 0.0.0.0 >"SW24000_32"
Note:
Note: Brocade Switch WWN's can be used to identify the types of switches in the fabric from the fabricshow output.
WWN by product (look at the last 6 digits of the WWN, this is subject to change)
10:00:00:60:6910:xx:xx 10:00:00:60:6950:xx:xx 10:00:00:60:6951:xx:xx 10:00:00:60:6980:xx:xx 10:00:00:60:6990:xx:xx through 4F:xx:xx -> 2x00 series -> 3800 series -> 3200 series -> 12000 switches -> 3900 switches
2-55
fabstateShow
Available in Fabric OS versions: 4.0.2c, v4.1, v4.2 Troubleshooting Use: Use this command to display switch State Change Information See embedded notes. S,Sn -> current switch state and next switch state. Possible switch states include: When an Inter-Switch Link is established the Switch should either request Build Fabric (BF) and enter state F0, or request Exchange Fabric Parameters (EFP) and enter state F2.
F0 Non-Disruptive Fabric Reconfiguration request, Build Fabric BF, transition state F2 EFP idle state D0 Setup: At the completion of Principal Switch Selection, the Principal Switch shall assume the role of Domain Address Manager. D1 Send DIA: The Principal Switch shall then transmit a DIA SW_ILS request Sequence on all E_Ports. D2 Idle: The Principal Switch shall remain in this state until it receives an RDI SW_ILS request Sequence. Reception of RDIs and or EFPs shall be queued in this state. A0 Get Domain_ID: At the completion of Principal Switch Selection, the Switch receives the DIA SW_ILS request Sequence via the upstream Principal ISL. A1 Send DIA: After the Switch is granted a Domain_ID, it shall then transmit a DIA SW_ILS request Sequence via all ISLs other than the Principal ISL. A2 Idle: The Switch shall remain in this state until it receives an RDI SW_ILS request Sequence. Reception of RDIs and or EFPs shall be queued in this state. Switches will end up in D2 (principle) or A2 (non-principle) state. See fcsw3 standards documentation.
Note:
P, Pn -> current port state and next port state. Possible port states include:
P0 Port offline or in initial state P1 Port online P2 Send /receive ELP accept P3 Receive active port state I0 - exchange trunk time stamp. I1 Receive time stamp accept, then send trunk parameters I2 Receive trunk parameter accept, transition to I3, and link reset port I3 Wait for port active state. T0 Receive trunk time stamp T1 Receive trunk parameter. T2 Send trunk parameter accept T3 Wait for port active state. Port -> port number Xid -> exchange ID.
Example 2-25:
fabstateshow Time Stamp Input and *Action S, P Sn,Pn Port Xid =========================================================================== 07:38:55.230 *Initiate ELP NA,P0 F2,NA NA NA 07:40:07.666 SCN Switch Online F2,NA F2,NA NA NA 07:40:07.668 *Start 2 * F_S_TOV Timer F2,NA F2,NA NA NA 07:40:07.862 *Start 24 * F_S_TOV Timer F2,NA F2,NA NA NA
2-56
This shows that the switch initial state is F2 and end F2, F2 is the state that ONLINE SCN receive feed into. Each F_S_TOV timer is typically 5 seconds, the 24* F_S_TOV is the time allowed for the switch to receive a domain ID.
07:40:08.417 07:40:08.537 07:40:08.537 07:40:08.542 07:40:08.612 07:40:08.618 SCN LR_PORT (0) debug - scn port online SCN Port Online *ELP Send SCN Port Offline *Removing all nodes from port F2,P0 F2,P0 10 F2,P0 F2,P0 10 F2,P0 F2,P1 10 F2,P1 F2,P1 10 F2,P1 F2,P0 10 F2,P0 F2,P0 10 NA NA NA 0x1 NA NA
The lines above show start port state P0 and end port state P1 on port 10 followed by an ELP with OXID 0x1, then offline port 10. the last line, port start and end states both P0 cleans the slate, which is also a good starting point -see next line.
07:40:08.812 debug - scn port online 07:40:08.813 SCN Port Online 07:40:08.813 SCN Port F_PORT F2,P0 F2,P0 F2,P1 F2,P0 F2,P1 F2,P0 13 13 13 NA NA NA
The lines above show start port state P0 and end port state P1 on port 13 followed by the port becoming an F_Port.
07:40:08.814 07:40:08.815 07:40:08.815 07:40:18.734 07:40:18.735 *Removing all nodes from port SCN Port Offline *Removing all nodes from port *Cancel 24 * F_S_TOV Timer 2 * F_S_TOV Expired F2,P0 F2,P0 13 F2,P0 F2,P0 F2,P0 F2,P0 F2,NA F2,NA F2,NA D0,NA NA 13 13 NA NA NA NA NA NA
The lines above show start port state P0 and end port state P1 on port 13 followed by the port becoming an F_Port. Note that the time stamp 07:40:08.815 *Removing all nodes from port and the message: 07:40:18.735 2 * F_S_TOV Expired occurred in 10 seconds. Port 13 ends up not being an F_Port, its end stat is P0, P0 - clean the port state slate. Also notice that the switch state transitions from F2 to D0, so it became the principle switch.
07:40:18.735 07:40:18.736 07:40:18.737 07:40:18.737 07:40:18.738 *Efp *EFP *EFP *DIA *DIA Flood (Am Principal) Flood Flood Done Flood Flood Done D0,NA D0,NA D0,NA D1,NA D1,NA D0,NA D0,NA D1,NA D1,NA D2,NA NA NA NA NA NA NA NA NA NA NA
The lines above show start switch state D0, principle switch state, sending out an EFP flood with updated Fabric Parameters and then transitions to D2 to wait for possible EFPs and RDIs.
07:40:18.738 Allow Fabric 07:40:19.047 07:40:19.047 07:40:19.194 07:40:19.253 Start Ext DomVal time to forwared Ext DomVal Timer *Validate Domain 1) fabInqData 2) fabInqData Timer RDIs Expired 1 D2,NA D2,NA D2,NA D2,NA D2,NA D2,NA D2,NA D2,NA D2,NA D2,NA NA NA NA NA NA NA NA NA NA NA
Getting information for fabricshow, in this one switch fabric information will only come from itself
07:40:19.329 07:40:19.463 07:40:19.597 07:40:19.597 07:40:19.599 07:40:19.643 07:40:19.644 07:40:19.924 07:40:19.924 07:40:19.924 07:40:19.925 07:40:20.745 07:40:22.652 09:08:46.191 09:08:46.192 09:08:46.271 09:08:46.413 09:08:46.547 09:08:46.547 09:08:46.549 RSCN Rcv addr: 0x3000000 SCN LR_PORT (0) debug - scn port online SCN Port Online *ELP Send SCN Port F_PORT *Removing all nodes from port debug - scn port online SCN Port Online SCN Port F_PORT *Removing all nodes from port RSCN Rcv addr: 0x50010a00 RSCN Rcv addr: 0x51010d00 SCN Port Offline *Removing all nodes from port RSCN Rcv addr: 0x60010a00 SCN LR_PORT (0) debug - scn port online SCN Port Online *ELP Send D2,NA D2,P0 D2,P0 D2,P0 D2,P1 D2,P1 D2,P0 D2,P0 D2,P0 D2,P1 D2,P0 D2,NA D2,NA D2,P0 D2,P0 D2,NA D2,P0 D2,P0 D2,P0 D2,P1 D2,NA D2,P0 D2,P0 D2,P1 D2,P1 D2,P0 D2,P0 D2,P0 D2,P1 D2,P0 D2,P0 D2,NA D2,NA D2,P0 D2,P0 D2,NA D2,P0 D2,P0 D2,P1 D2,P1 NA 10 10 10 10 10 10 13 13 13 13 NA NA 10 10 NA 10 10 10 10 NA NA NA NA 0x13 NA NA NA NA NA NA NA NA NA NA NA NA NA NA 0x21e
2-57

SCN Port F_PORT *Removing all nodes from port RSCN Rcv addr: 0x51010d00 SCN Port Offline *Removing all nodes from port RSCN Rcv addr: 0x61010d00 debug - scn port online SCN Port Online SCN Port F_PORT *Removing all nodes from port RSCN Rcv addr: 0x51010d00 SCN Switch Offline *Removing all nodes *Cancel F_S_TOV Timer *Cancel 2 * F_S_TOV Timer *Cancel RDI Receive Timer *Cancel RDI Send Timer *Cancel 24 * F_S_TOV Timer *Cancel EFP Flood Timer 1) fabInqData 2) fabInqData SCN Port Offline *Removing all nodes from port SCN Port Offline *Removing all nodes from port SCN Switch Online 1) fabInqData 2) fabInqData *Start 2 * F_S_TOV Timer *Start 24 * F_S_TOV Timer SCN LR_PORT (0) debug - scn port online SCN Port Online *ELP Send SCN Port Offline *Removing all nodes from port debug - scn port online SCN Port Online SCN Port F_PORT *Removing all nodes from port SCN Port Offline *Removing all nodes from port *Cancel 24 * F_S_TOV Timer 2 * F_S_TOV Expired *Efp Flood (Am Principal) *EFP Flood *EFP Flood Done *DIA Flood *DIA Flood Done Start Ext DomVal Timer Ext DomVal Timer Expired *Validate Domain 1 1) fabInqData 2) fabInqData RSCN Rcv addr: 0x3000000 SCN LR_PORT (0) debug - scn port online SCN Port Online *ELP Send SCN Port F_PORT *Removing all nodes from port debug - scn port online SCN Port Online SCN Port F_PORT *Removing all nodes from port D2,P1 D2,P0 D2,NA D2,P0 D2,P0 D2,NA D2,P0 D2,P0 D2,P1 D2,P0 D2,NA D2,NA F2,NA F2,NA F2,NA F2,NA F2,NA F2,NA F2,NA F2,NA F2,NA F2,P0 F2,P0 F2,P0 F2,P0 F2,NA F2,NA F2,NA F2,NA F2,NA F2,P0 F2,P0 F2,P0 F2,P1 F2,P1 F2,P0 F2,P0 F2,P0 F2,P1 F2,P0 F2,P0 F2,P0 F2,NA F2,NA D0,NA D0,NA D0,NA D1,NA D1,NA D2,NA D2,NA D2,NA D2,NA D2,NA D2,NA D2,P0 D2,P0 D2,P0 D2,P1 D2,P1 D2,P0 D2,P0 D2,P0 D2,P1 D2,P0 D2,P0 D2,P0 D2,NA D2,P0 D2,P0 D2,NA D2,P0 D2,P1 D2,P0 D2,P0 D2,NA F2,NA F2,NA F2,NA F2,NA F2,NA F2,NA F2,NA F2,NA F2,NA F2,NA F2,P0 F2,P0 F2,P0 F2,P0 F2,NA F2,NA F2,NA F2,NA F2,NA F2,P0 F2,P0 F2,P1 F2,P1 F2,P0 F2,P0 F2,P0 F2,P1 F2,P0 F2,P0 F2,P0 F2,P0 F2,NA D0,NA D0,NA D0,NA D1,NA D1,NA D2,NA D2,NA D2,NA D2,NA D2,NA D2,NA D2,NA D2,P0 D2,P0 D2,P1 D2,P1 D2,P0 D2,P0 D2,P0 D2,P1 D2,P0 D2,P0 10 10 NA 13 13 NA 13 13 13 13 NA NA NA NA NA NA NA NA NA NA NA 10 10 13 13 NA NA NA NA NA 10 10 10 10 10 10 13 13 13 13 13 13 NA NA NA NA NA NA NA NA NA NA NA NA NA 10 10 10 10 10 10 13 13 13 13 NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA 0x646 NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA NA 0x658 NA NA NA NA NA NA
09:08:46.606 09:08:46.606 09:09:16.647 16:47:01.362 16:47:01.362 16:47:01.377 16:47:07.080 16:47:07.080 16:47:07.081 16:47:07.081 16:47:08.714 16:50:20.063 16:50:20.063 16:50:20.063 16:50:20.063 16:50:20.064 16:50:20.064 16:50:20.064 16:50:20.065 16:50:20.065 16:50:20.072 16:50:20.075 16:50:20.076 16:50:20.076 16:50:20.077 16:59:06.601 16:59:06.601 16:59:06.608 16:59:06.612 16:59:06.612 16:59:06.875 16:59:07.007 16:59:07.007 16:59:07.009 16:59:07.066 16:59:07.067 16:59:07.316 16:59:07.317 16:59:07.317 16:59:07.317 16:59:07.318 16:59:07.318 16:59:16.741 16:59:16.741 16:59:16.741 16:59:16.742 16:59:16.742 16:59:16.742 16:59:16.742 16:59:16.742 16:59:17.047 16:59:17.047 16:59:17.182 16:59:17.188 16:59:17.202 16:59:17.461 16:59:17.587 16:59:17.587 16:59:17.589 16:59:17.643 16:59:17.644 16:59:17.915 16:59:17.915 16:59:17.915 16:59:17.915
2-58

16:59:19.208 16:59:21.111 17:15:58.166 17:15:58.167 17:15:58.181 17:16:04.487 17:16:04.488 17:16:04.500 17:27:00.118 17:27:00.247 17:27:00.247 17:27:00.249 17:27:00.299 17:27:00.300 17:27:01.339 17:27:03.334 17:27:03.334 17:27:03.334 17:27:03.334 17:27:05.466 22:19:57.460 22:19:57.460 22:19:57.473 22:20:38.058 22:20:38.187 22:20:38.187 22:20:38.189 22:20:38.247 22:20:38.247 22:20:39.289 RSCN Rcv addr: 0x50010a00 RSCN Rcv addr: 0x51010d00 SCN Port Offline *Removing all nodes from port RSCN Rcv addr: 0x61010d00 SCN Port Offline *Removing all nodes from port RSCN Rcv addr: 0x60010a00 SCN LR_PORT (0) debug - scn port online SCN Port Online *ELP Send SCN Port F_PORT *Removing all nodes from port RSCN Rcv addr: 0x50010a00 debug - scn port online SCN Port Online SCN Port F_PORT *Removing all nodes from port RSCN Rcv addr: 0x51010d00 SCN Port Offline *Removing all nodes from port RSCN Rcv addr: 0x60010a00 SCN LR_PORT (0) debug - scn port online SCN Port Online *ELP Send SCN Port F_PORT *Removing all nodes from port RSCN Rcv addr: 0x50010a00 D2,NA D2,NA D2,P0 D2,P0 D2,NA D2,P0 D2,P0 D2,NA D2,P0 D2,P0 D2,P0 D2,P1 D2,P1 D2,P0 D2,NA D2,P0 D2,P0 D2,P1 D2,P0 D2,NA D2,P0 D2,P0 D2,NA D2,P0 D2,P0 D2,P0 D2,P1 D2,P1 D2,P0 D2,NA D2,NA D2,NA D2,P0 D2,P0 D2,NA D2,P0 D2,P0 D2,NA D2,P0 D2,P0 D2,P1 D2,P1 D2,P0 D2,P0 D2,NA D2,P0 D2,P1 D2,P0 D2,P0 D2,NA D2,P0 D2,P0 D2,NA D2,P0 D2,P0 D2,P1 D2,P1 D2,P0 D2,P0 D2,NA NA NA 13 13 NA 10 10 NA 10 10 10 10 10 10 NA 13 13 13 13 NA 10 10 NA 10 10 10 10 10 10 NA NA NA NA NA NA NA NA NA NA NA NA 0x800 NA NA NA NA NA NA NA NA NA NA NA NA NA NA 0xa93 NA NA NA
The rest of these lines show ports 10 and 13 as they come online and register to receive RSCNs.
2-59
fabstatsshow
Available in Fabric OS versions: v3.1, v3.1.2, v4.1, v4.2 Troubleshooting Use: Use this command to display the statistics information of fabric segmentations. This is a quick way to determine what caused the fabric to segment - switchshow and errdump (this output will give you the most information) will also display fabric segmentation reasons. The fabstatsshow command is brief and concise but be cautious - the counters are not cleared when the segmentation is fixed, but as of v3.1.2/4.2, there will be a date (seeExample 2-16) indicating when the segmentation occurred. The information displayed is as follows:
Number of times a switch domain ID has been forcibly changed Number of E_Port offline transitions Number of fabric reconfigurations Number of fabric segmentations due to: Loopback - Number of times this switch segmented port due to port being placed into mcastloopback mode used to prevent IP/FC broadcast problems. Incompatibility - Fabric.ops parameters are different. Overlap - there are duplicate domains in attaching fabrics and fabrics are being hot plugged Zoning - cfgmismatch (only one enabled cfg allowed), type mismatch (fabric A has a zone called eng27, fabric B has an Alias called eng27), content mismatch (fabric A has an eng27 zone with 2,4; 2,6; 4,6, fabric B has an eng27 zone with 2,4; 4,6. When a switch is taken out of a fabric for maintenance persistently disable ports (v3.1/4.1+), clean the zoning out (cfgdisable; cfgclear; cfgsave), re-attach switch to fabric establish E_Port connection and allow the existing fabrics zone to propagate to the new switch and then persistently enable or enable end device ports. Routing - v4.x engineers responsible for routing says it is not used yet. Licensing - When a value line (VL2 or VL4) or entry fabric switch exceeds its maximum number of fabric switches a segmentation due to licensing will occur. V3.1.2/4.2 allows a grace period during which extra switches are allowed to connect. Disabling E_Port - a segmentation occurs because a ports E_Port capability was disabled using the portcfgeport command / operands. Incompatible management server platform DBs - Management server platform DBs when enabled need to be compatible. If you have incompatible platform db segmentation use the msplcleardb command on merging fabric to clear data base, incorporate merging fabric members into the existing fabrics access list. Management server platform databases are enabled (msplmtactivate) and configured (msconfigure) when applications that use the management server are desired in a fabric. The management server enables a management application to access and configure switches in the fabric. It is located at the Fibre Channel address, FFFFFAh. If the access control list (ACL) is empty (default value), the management server is available to all systems connected in-band to the fabric. To restrict access, specify the World Wide Name (WWN) for one or more management applications using the msconfigure command; access is then restricted to those WWNs. Up to 16 maximum WWNs are supported in the ACL. The ACL is implemented on a per-switch basis and should be configured on the switch to which the management application station is directly connected. The msconfigure command is interactive and provides the following choices: 0 Done 1 Display the access list 2 Add member based on its port/node WWN 3 Delete member based on its port/node WWN
2-60
Security violations - A security violation could occur if: -Port used to connect switches has a DCC policy that doesnt allow switch into fabric or fabric has SCC policy that doesnt allow switch into fabric Security incompatibility - A security incompatibility could occur for the following reasons: - - Security Incompatibility - Unknown incompatibility - - Security Incompatibility - Security parameters incompatibility - - Security Incompatibility - Exchange FCS failed - - Security Incompatibility Data incompatibility - - Security Incompatibility - MS Platform config incompatibility
Example Story Output: Example 2-16: To display the fabric statistics information:
switch:admin> fabstatsshow Description Count Port Time --------------------------------------------------------------Domain ID forcibly changed: 0 E_Port offline transitions: 1 0 Reconfigurations: 9 0 WED JAN 21 23:23:13 2004 Segmentations due to: Loopback: 0 Incompatibility: 1 < WED JAN 21 23:24:10 2004 Overlap: 0 Zoning: 0 Routing: 0 Licensing: 0 Disabling E_Port: 0 Incompatible platform DB: 0 Security violation: 0 Security incompatibility: 0
Note:
Command outputs associated with the above fabstatsshow output (Example 2-16) follow.
Console output when switch was enabled:

Command in progress 0x1027f7f0 (tFabric): Jan 21 23:40:45 WARNING FABRIC-SEGMENTED, 3, port 0, ELP rejected
switchshow output (notice segmented - unknown incompat message):

switch_28:admin> switchshow switchName: sw3800_28 switchType: 9.1 switchState: Online switchMode: Native switchRole: Principal switchDomain: 3 switchId: fffc03 switchWwn: 10:00:00:60:69:50:10:80 switchBeacon: OFF Zoning: OFF port 0: id N2 Online E-Port (segmented,incompatible,(Unknown incompat)) port 1: id N2 No_Light
2-61
errshow output (notice segmented - ELP rejected message - you can use Diagnostic and Error message guide, Fabric module, segmented error message to determine how to fix):
switch_28:admin> errshow Error 39 -------0x1027f7f0 (tFabric): Jan 21 23:24:10 WARNING FABRIC-SEGMENTED, 3, port 0, ELP rejected
fabstatsshow and errshow output from switch at the other end of the link (notice this fabstatsshow output does not have a date, only an arrow. The error message gives the reason why this switch segmented the other switches ELP. Also notice that this output is from a Linux switch while the earlier messages originated from a vxWorks switch as they have the small t in front of the task name):
Sw3850:admin> fabstatsshow Description Count ----------------------------------------Domain ID forcibly changed: 0 E_Port offline transitions: 2 (Last on port 11) Reconfigurations: 3 Segmentations due to: Loopback: 0 Incompatibility: 9 < Overlap: 0 Zoning: 0 Routing: 0 Licensing: 0 Disabling E_Port: 0 Sw3850:admin> errshow Error 118 -------0x269 (fabos): Jan 21 15:24:09 Switch: 0, Warning FABRIC-SEGMENTED, 3, port 11, incompatible flow control parameters (2)
Note:
To fix go to the switch whose ELP was rejected and compare fabric.ops parameters.
v3.x Example Output: Example 2-17: Example 2

Switch:admin> fabstatsshow Description Domain ID forcibly changed: E_Port offline transitions: Reconfigurations: Segmentations due to: Loopback: Incompatibility: Overlap: Zoning: Routing: Licensing: Disabling E_Port: Count 0 0 0 0 0 0 0 0 1 < 0
Note:
The <symbol to the right of the * Licensing value in Example 2-16 indicates current segmentation reason = licensing.
The attached switch is an Entry Fabric Switch that was ISLed to this Full Fabric Switch with no problem (first E_Port transition). When a second ISL was added, switchShow from attached switch, gave this readout: port X: sw Online E-Port (license required). The fabstatsShow command above was then issued.
2-62
Fabric OS SupportShow Information v4.2 Example Output: Example 2-26:

fabstatsshow Description Count ----------------------------------------Domain ID forcibly changed: 0 E_Port offline transitions: 0 Reconfigurations: 0 Segmentations due to: Loopback: 0 Incompatibility: 0 Overlap: 0 Zoning: 0 Routing: 0 Licensing: 0 Disabling E_Port: 0
2-63
fabswitchShow
Available in Fabric OS versions: 4.0.2c, v4.1, v4.2 Version Differences: Version 4.2 output added some statistical information about the number of times the switch entered different states. Troubleshooting Use: Use this command to display switch State information (examples of state information includes: fabric builds, Domain, WWN, and principal priority information). See embedded notes and comments in Example 2-21 explaining some command output information. Additional Example/Case Studies: v4.1 Example Output: Example 2-27:
fabswitchshow Fabric Switch State Structure Information ========================================= State: D2 Rdi Receive Timer: 0x10051b48, IDLE STATE
Timer to help prevent principle switch from flooding Fabric for each RDI.
Unconfirmed Sw Timer: 0x10051c50, IDLE STATE Another name for 24 * F_S_TOV. Principal Domain: 1 Upstream Port: 64
If this switch is principle value defaults to 64

Principal Wwn: Principal Prioritry: 10:00:00:60:69:80:04:b2 0x2
Per standards, see note, Fabric OS v4.1 will allow you to set 01 here thus forcing this switch to be principal. Note: According to the standards, possible values for this bit are 00: Reserved; 01 Highest priority value (a value that can be set by a system administrator in Brocade fabrics this is the fabricprincipal command); 02: The switch was the principal switch prior to sending or receiving a build fabric (BF); 03-FE: Higher to lower Priority Values (vendor principal switch selection methodology); or FF: The switch is not capable of acting as a principal switch.
0x4 1 1
Flags: inq_sem count: dbg_sem count:
Default semaphore values, if value = 0 then there is a problem.

fibbed current count: fab_q high water: 0 3
The highest number of messages that have been in the Fabric queue.
fab_q age: 0 (sec) dup xid occurance: 0 last message: 22:20:39.289 RSCN Rcv addr: 0x50010a00
D2,NA
D2,NA
NA
NA
The last line of Fabstateshow output.

reachable domains: no domains reachable Ports used for EFP/BF/DIA flood:
2-64

fabswitchshow Fabric Switch State Structure Information ========================================= State: D0 Stage: warm done Rdi Receive Timer: 0x10057b98, IDLE STATE Unconfirmed Sw Timer: 0x10057ca0, IDLE STATE NTP Timer: 0x10057d50, IDLE STATE ME Timer: 0x10057da8, IDLE STATE Principal Domain: 1 Upstream Port: 128 Principal Wwn: 10:00:00:60:69:80:2d:4a Principal Priority: 0xfe Flags: 0x20 me retry count: 0 inq_sem count: 1 dbg_sem count: 1 ha efp count: 0 fab_q current count: 0 fab_q high water: 3 fab_q age: 0 (sec) dup xid occurance: 0 iu nodes outstanding: 0 EFP update port: 128 test check point: No check point set fabric license: TRUE last message: 10:43:57.048 RSCN Rcv addr: 0x50015e00 NTP ports online: RSCN domain recovery list: no domain RSCN's to recover reachable domains: no domains reachable Ports used for EFP/BF/DIA flood: Command Statistics: command high(ms) low(ms) ave(ms) total dropped ========================================================= fc_write 0 0 0 1 N/A P Timer 0 0 0 0 N/A BF Timer 0 0 0 0 N/A RDI Timer 0 0 0 0 N/A Unc Timer 0 0 0 0 N/A EFP Flood 0 0 0 0 N/A HA EFP Fld0 0 0 1 N/A inq_sem 10 0 0 3843 N/A dbg_sem 0 0 0 107 N/A AC_DONE 0 0 0 0 N/A LR_DONE 0 0 0 2 N/A D_REACH 0 0 0 0 N/A D_UNREACH 0 0 0 0 N/A P_ONLINE 0 0 0 2 N/A P_OFFLINE 0 0 0 1 N/A S_ONLINE 0 0 0 0 N/A S_OFFLINE 0 0 0 0 N/A ELP RESP 0 0 0 0 N/A ELP RCV 0 0 0 0 0
D0,NA
D0,NA
NA
NA
2-65

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 2 2 N/A N/A 0 N/A N/A N/A N/A 0 N/A N/A 0 N/A N/A 0 N/A N/A 0 N/A N/A 0 N/A N/A 0 N/A 0 0 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A
ELP TO EFP RESP EFP RCV EFP TO HA EFP RP HA EFP TO DIA RESP DIA RCV DIA TO RDI RESP RDI RCV RDI TO BF RESP BF RCV BF TO EMT RESP EMT RCV EMT TO ETP RESP ETP RCV ETP TO INQ RESP INQ RCV INQ TO FORWARD GRE RCV SW ST UD SW FG UD UPSTRM UD INQ UD PRI UD DLST UD ALST UD NBRWWN UD PTFLG UD PTST UD HDNEP UD SYCDMP UD INQSYC UD
2-66
fanShow
Available in Fabric OS versions: All Version Differences: Different hardware platforms have a different number of fans. See platform hardware reference manual for correct fan RPM values for your platform. Troubleshooting Use: Use this command to display fan status Use this command to display the current status of the switch fans.The format of the display varies according to the switch model and number of fans. Some switch models show fan speed measured in RPM (revolutions per minute). Fan status is shown as: OK absent unknown faulty Note: Fan is functioning correctly. Fan is not present. Unknown fan unit installed. Fan has exceeded hardware tolerance.
below minimum Fan is present but rotating too slowly or stopped.
The output from this command varies depending on switch type and number of fans present.
v4.2 Example Output: Example 2-18: To display the status and RPMs for the fans:
fanshow: Fan #1 is OK, speed is 2500 RPM Fan #2 is OK, speed is 2481 RPM Fan #3 is OK, speed is 2518 RPM
As of v4.0.2a + fan faults will be generated in the error log if fan rpm values exceed 10,000. Prior to this version messages were only generated according to settings in switchstatuspolicyshow parameters. If you see errshow fan fault messages for fan x, look for correlating temperature messages, if the switch overheats (sensors on blades) fans will kick into high gear. The remaining blowers will also kick into high gear if one of the fans/ blowers is faulty but should not exceed upper rpm limit. In the case of a failed blower (you will see error messages in the log), leave failed blower in chassis until replacement is available. This will allow better air circulation for the remaining two, higher rpm blowers. Also notice that when you remove the blower, a rubber flap drops into place, again for better air flow. Warning: Be careful not to carry blowers by their pull out handle. These handles were designed to make pulling out the blower easier, not to carry it.
2-67
faShow
Available in Fabric OS versions: v3.x Troubleshooting Use: Use this command to display Fabric Assist information. This command displays information about Fabric Assist host ports. This command will display the port number and PID for each Fabric Assist host port located on this switch. It will also display a listing of each Target that has a Fabric Assist phantom on the hosts port. The targets PID, assigned phantom ALPA, preferred ALPA and current online/offline status will all be displayed. The message No Fabric Assist Host Ports on this Switch is displayed if Fabric Assist is disabled, or if there are no Fabric Assist host ports on the switch. If the switch was unable to assign a phantom for the target then the message No Phantom will be displayed in the Status column. This switch will be unable to create a phantom if there are no available AL_PAs on the loop, or if there are more than 125 phantoms zoned to hosts on any one switch. If the preferred alpa can not be assigned as the targets alpa, then the AL_PA field of the target will be left blank and ALPA Conflict will be displayed in the Status column. In this situation the targets phantom wont be created. Each line of output shows: Fabric Assist Mode: port PID Target ALPA Status Enabled or Disabled The port number of the Fabric Assist host The 24-bit Fibre Channel address of the host. The 24-bit Fibre Channel address of a zoned Target that current has a phantom assigned to the host. The assigned phantom ALPA for the target. The Online/Offline status of the target.
Fabric Assist The Online/Offline status of the host.
PREF_ALPA The preferred ALPA given for the target. Example: Two Fabric Assist host ports on the switch and the targets that they are set up to communicate with using QLFA.
sw1:admin> faShow Fabric Assist Mode: Enabled Port PID Fabric Assist Target ALPA PREF_ALPA 00 0x011001 Online 0x011498 (0xef) Online 0x011497 (0x97) Online 0x011490 (0x90) Online 0x01148f (0x8f) Online 0x011488 (0x88) Online 0x011484 (0x84) Online 0x011482 (0x82) Online 0x011481 (0x81) Online 0x011480 (0x80) Online 0x01147c (0x7c) Online 0x01147a (0x7a) Online 0x011475 (0x75) Online 01 0x0111e2 Online0x0115ab (0xab) Online 0x0115b4 (0xb4) Online 0x0115b3 (0xb3) Online 0x0115b2 (0xb2) Online 0x0115b1 (0xb1) Online 0x0115ae (0xae) Online 0x0115ad (0xad) Online 0x0115ac (0xac) Online
Status
Example 2-29:
sw1:admin> faShow Fabric Assist Mode: Disabled No Fabric Assist Host Ports on this Switch
2-68
fastcheckheap
Available in Fabric OS versions: v3.0, v3.1.0, v3.1.2 (OS command group - not enabled by default) v4.2 Example Output: N/A Troubleshooting Use: This command is designed for internal debugging purposes.: Note: Use for internal debug purposes only.

fastcheckheap Per Task Summary: tThad held: 158944 max_block:0x11eb4bf0len:8048 tSecurity held: 96 max_block:0x11e96f00len:96 tFabric held: 12000 max_block:0x11ed70c0len:3232 tSnmpd held: 5392 max_block:0x11ecacc0len:3232 tSwitch held: 2744704 max_block:0x11f5edb0len:640032 tASd held: 185440 max_block:0x11f2db50len:168992 tPSd held: 96 max_block:0x11f5ca60len:96 tMsApi held: 96 max_block:0x11f5cd60len:96 tPSrqm held: 288 max_block:0x102fc250len:96 tMSd held: 288 max_block:0x102fc130len:96 tHttpD held: 640 max_block:0x102fbcb0len:80 tFcp held: 48 max_block:0x10294390len:48 tRapid held: 8048 max_block:0x10292330len:8048 tFspf held: 54368 max_block:0x1007ff70len:26912 tNSd held: 99936 max_block:0x1006cc80len:49184 tNSCAM held: 192 max_block:0x10052150len:96 tfdmic held: 96 max_block:0x10037bb0len:96 Total blocks held: 3270672
2-69
faultshow
Troubleshooting Use: Use this command for internal debugging purposes. Available in Fabric OS versions: v3.0, v3.1, v3.1.2 v4.2 Example Output: NA Additional Example/Case Studies: Note: See traceshow on page 2-257 for related information.
Example outputs with some embedded notes: Example 2-31:

Traceshow Switch:root> traceshow [INDX] TIMEFROM TO ---------------------------------------------[24] Dec 29 03:11:11.066unknown tSwitch 0x101ca8500x103bbb00 120080
Is 120 and 080 important...what are they? This is the tasklog in RAM before reboot and its time. 120 and 80 are the task priorities. Tasklogs the task context (e.g. current executing instructions) at task switch, called by the scheduler when it selects a new task to run. The log is a circular buffer that stores the last 25 tasks that were running on the switch before the switch reboots. Example 2-32:
READY READY [unknown] [0]_vxTaskEntry + 0x10 (0x10735914) [1]_crashTask + 0x40 (0x104dd310)
Does this tell me I've had a panic or a watchdog error? No. You should check uptime to find out it is a panic or watchdog, etc.
[2]_taskDelay + 0x98 (0x10780048) <- instruction pointer
This is address of instruction. At 0x10780048, there may be a static function Example 2-33:
[tSwitch] [0]_vxTaskEntry + 0x10 (0x10735914) [1]_switchTask + 0x184 (0x105101f4) [2]_fabricInit + 0xbc (0x104dd27c) [3]_fcServiceResponseQ + 0x1c (0x1056c91c) [4]_mqRead + 0x14 (0x10576d34) [6]_qJobGet + 0x48 (0x1079e628) Reset at: Dec 29 03:11:11 Reset reason 2: Bus error
If I see this I can ascertain there was a panic or there was a watchdog error. Bus error is another category of reboot, i.e., CPU accesses a memory location that does not exist. It is a typical memory corruption. See the TOI for the difference with watchdog and panic.
2-70
Fabric OS SupportShow Information Example 2-34:

Task: Interrupt ... Frame #2 Address: (0x103f5108) Local registers (0x10276af0): pfp = 0x103bbea7, sp = 0x1081af10, r4 = 0x00000040, r5 = 0x1081aed0, r8 = 0x003d0004, r9 = 0x00000000, r12 = 0x756f7920, r13 = 0x00000000, Interrupt call: Saved pc = 0x3 Saved ac = 0x1100 Vector = 0xf8 (NMI) User's stack, length = 64: 756f7920 00000000 001f0000 00000012 00000007 756f7920 0000001b 00000040 00000000 00000000 00000000 00000000
rip r6 r10 r14
= = = =
0x103f5108, 0x00000000, 0x00000000, 0xeeeeeeee,
r3 r7 r11 r15
= = = =
0xeeeeeeee 0x00000000 0x103bbb00 0xeeeeeeee
* you............* *.... you....@...* *................*
Note:
The user stack gives helpful information for debugging. It is for Brocade software engineer's internal use.
When will I see traceshow output? If the switch reboots due to bus error, panic and watchdog, you will see traceshow in supportshow. Example 2-35:
FaultShow Fault at: Aug 22 23:37:45 Task: 0x10927810 (tRapi0)
The API made a call.

Global registers: g0 = 0x1041786c, g1 = 0x00000002, g2 g4 = 0x00000001, g5 = 0x10927810, g6 g8 = 0x00000000, g9 = 0x00000000, g10 g12 = 0x00000000, g13 = 0x00000000, g14 pfp = 0x10927f50, ac = 0x00001001, pc Frame #0 Address: _excStub + 0x4c (0x1072449c) Local registers: pfp = 0x10927d41, sp = 0x10927e20, rip r4 = 0x0000000f, r5 = 0xeeeeeeee, r6 r8 = 0x00000000, r9 = 0x00000001, r10 r12 = 0x106a1c00, r13 = 0xeeeeeeee, r14 Fault: Saved pc = 0x3 Saved ac = 0x1002 Type = OPERATION (0x2) Subtype = INVALID_OPCODE (0x1) = = = = = 0x10927db0, 0x103ff470, 0x00000000, 0x00000000, 0x00000003, g3 g7 g11 fp tc = = = = = 0x00000001 0x00000000 0x00000000 0x10927fa0 0x00000080
= = = =
0x1072449c, 0xeeeeeeee, 0x00000000, 0xeeeeeeee,
r3 r7 r11 r15
= = = =
0x00000030 0x107e4650 0x10724450 0xeeeeeeee
Could this be API call that caused error? Any function call can cause a fault when memory corruption occurs.
Flags = 0 Address of faulting instruction = 0x109255e8 User's stack, length = 0: Frame #1 Address: _semClass + 0x8 (0x109255e8) Local registers: pfp = 0x10927d00, sp = 0x10927d80, rip = 0x109255e8, r4 = 0x106a1c00, r5 = 0xeeeeeeee, r6 = 0xeeeeeeee, r8 = 0x00000000, r9 = 0xeeeeeeee, r10 = 0xeeeeeeee, r12 = 0x106a1c00, r13 = 0xeeeeeeee, r14 = 0xeeeeeeee,
r3 r7 r11 r15
= = = =
0xeeeeeeee 0xeeeeeeee 0x10927810 0xeeeeeeee
2-71
User's stack, length = 0: Frame #2 Address: _xdrrec_endofrecord + 0x18c (0x1076056c) Local registers: pfp = 0x10927cc0, sp = 0x10927d40, rip = 0x1076056c, r4 = 0x1093fe40, r5 = 0x00000000, r6 = 0xeeeeeeee, r8 = 0x00000000, r9 = 0xeeeeeeee, r10 = 0xeeeeeeee, r12 = 0x106a1c00, r13 = 0xeeeeeeee, r14 = 0xeeeeeeee, User's stack, length = 0: Frame #3 Address: _xdrrec_endofrecord + 0x2e8 (0x107606c8) Local registers: pfp = 0x10927c80, sp = 0x10927d00, rip = 0x107606c8, r4 = 0x107e7c20, r5 = 0x1093fe40, r6 = 0xeeeeeeee, r8 = 0x00000000, r9 = 0xeeeeeeee, r10 = 0xeeeeeeee, r12 = 0x106a1c00, r13 = 0xeeeeeeee, r14 = 0xeeeeeeee, User's stack, length = 0: Frame #4 Address: _xdrrec_skiprecord + 0x18 (0x10760328) Local registers: pfp = 0x10927c40, sp = 0x10927cc0, rip = 0x10760328, r4 = 0x1093fe40, r5 = 0x10927bc0, r6 = 0x1095ed80, r8 = 0x00000000, r9 = 0xeeeeeeee, r10 = 0xeeeeeeee, r12 = 0x106a1c00, r13 = 0xeeeeeeee, r14 = 0xeeeeeeee, User's stack, length = 0: Frame #5 Address: _svcfd_create + 0x3a0 (0x1075e7e0) Local registers: pfp = 0x10927b80, sp = 0x10927c80, rip = 0x1075e7e0, r4 = 0x1095ed90, r5 = 0x10927bc0, r6 = 0x1095ed80, r8 = 0x00000000, r9 = 0xeeeeeeee, r10 = 0xeeeeeeee, r12 = 0x106a1c00, r13 = 0xeeeeeeee, r14 = 0xeeeeeeee, User's stack, length = 0: Frame #6 Address: _svc_getreqset + 0xe0 (0x1075d6f0) Local registers: pfp = 0x10927ad0, sp = 0x10927c40, rip = 0x1075d6f0, r4 = 0x1092d860, r5 = 0x0000000c, r6 = 0x109946c0, r8 = 0x00000000, r9 = 0xeeeeeeee, r10 = 0xeeeeeeee, r12 = 0x106a1c00, r13 = 0xeeeeeeee, r14 = 0xeeeeeeee, User's stack, length = 0: Frame #7 Address: _subtask_svc_run + 0x134 (0x106a1574) Local registers: pfp = 0x10927a80, sp = 0x10927b80, rip = 0x106a1574, r4 = 0x00000100, r5 = 0x00000000, r6 = 0x00000000, r8 = 0x00000000, r9 = 0xeeeeeeee, r10 = 0xeeeeeeee, r12 = 0x106a1c00, r13 = 0xeeeeeeee, r14 = 0xeeeeeeee, User's stack, length = 0: Frame #8 Address: _RapiConxTask + 0x1a8 (0x106a1da8) Local registers: pfp = 0x10927a00, sp = 0x10927ad0, rip = 0x106a1da8, r4 = 0x10921ce0, r5 = 0x10927810, r6 = 0xeeeeeeee, r8 = 0xeeeeeeee, r9 = 0xeeeeeeee, r10 = 0xeeeeeeee, r12 = 0x106a1c00, r13 = 0xeeeeeeee, r14 = 0xeeeeeeee, User's stack, length = 0: Frame #9 Address: _vxTaskEntry + 0x10 (0x10725834) Local registers: pfp = 0x00000000, sp = 0x10927a80, rip = 0x10725834, r4 = 0xeeeeeeee, r5 = 0xeeeeeeee, r6 = 0xeeeeeeee, r8 = 0xeeeeeeee, r9 = 0xeeeeeeee, r10 = 0xeeeeeeee,
r3 r7 r11 r15
= = = =
r3 r7 r11 r15
= = = =
r3 r7 r11 r15
= = = =
0xeeeeeeee 0x10998560 0x10927810 0xeeeeeeee
r3 r7 r11 r15
= = = =
r3 r7 r11 r15
= = = =
r3 r7 r11 r15
= = = =
r3 r7 r11 r15
= = = =
r3 = 0xeeeeeeee r7 = 0xeeeeeeee r11 = 0x10927810
2-72

r12 = 0x106a1c00, r13 = 0xeeeeeeee, r14 = 0xeeeeeeee, r15 = 0xeeeeeeee User's stack, length = 0:
Will faultshow output always have task information in it that, if task is known, can help identify error? Yes Is it true to assume that if there is a faultshow output there was a problem that caused the switch to reboot or will we get faultshow outputs without panics?....or without watchdog errors? Sometimes we have both faultshow and traceshow together, and most times we get only one of them. In either case, the root cause is either memory corruption or memory leak. When will I see faultshow output? When a fault causes switch reboot, you will have faultshow in supportshow. There are typically the following cases: *INVALID_OPCODE --the program pointer is corrupted, and CPU fetches instruction from data area and get invalid opcode. * TYPE MISMATCH--data pointer is corrupted, and CPU tries to access some area that is prohibited. When will I see both faultshow and traceshow output....or will I? When there are both fault and bus error, etc.
2-73
fcplogshow
Available in Fabric OS versions: v4.1, 4.2 Troubleshooting Use: Internal Engineering use only. Note: This is for internal debugging of the fcpd. It basically a log mechanism to debug an event and trace the calls throughout the various functions in fcp. In order to decode, you would need the source code, hence the file and lineno columns.
Example from v4.1 output: fcplogshow: Time Stamp Event Port file&lineno arg0 arg1 arg2 arg3 arg4 ====================================================================================== 22:36:46.245 FlshOrProbe 19 1 459 81 :0 :0 :0 :0 22:36:46.247 ProbeFlsh 19 1 2764 0 :0 :0 :0 :0 22:36:49.756 FlshOrProbe 35 1 459 81 :0 :0 :0 :0 22:36:49.756 ProbeFlsh 35 1 2764 0 :0 :0 :0 :0 22:37:26.426 FlshOrProbe 23 1 459 81 :0 :0 :0 :0 22:37:26.426 ProbeFlsh 23 1 2764 0 :0 :0 :0 :0 22:37:30.226 FlshOrProbe 39 1 459 81 :0 :0 :0 :0 22:37:30.226 ProbeFlsh 39 1 2764 0 :0 :0 :0 :0 22:38:06.406 FlshOrProbe 27 1 459 81 :0 :0 :0 :0 22:38:06.406 ProbeFlsh 27 1 2764 0 :0 :0 :0 :0 22:38:10.245 FlshOrProbe 43 1 459 81 :0 :0 :0 :0 22:38:10.245 ProbeFlsh 43 1 2764 0 :0 :0 :0 :0 22:38:47.117 FlshOrProbe 31 1 459 81 :0 :0 :0 :0 22:38:47.117 ProbeFlsh 31 1 2764 0 :0 :0 :0 :0 22:38:50.096 FlshOrProbe 47 1 459 81 :0 :0 :0 :0 22:38:50.096 ProbeFlsh 47 1 2764 0 :0 :0 :0 :0 22:39:30.566 FlshOrProbe 19 1 459 81 :0 :0 :0 :0 22:39:30.566 ProbeFlsh 19 1 2764 0 :0 :0 :0 :0 22:39:30.566 FlshOrProbe 18 1 459 81 :0 :0 :0 :0 22:39:30.566 ProbeFlsh 18 1 2764 0 :0 :0 :0 :0 22:39:30.566 FlshOrProbe 17 1 459 81 :0 :0 :0 :0 22:39:30.566 ProbeFlsh 17 1 2764 0 :0 :0 :0 :0 22:39:30.566 FlshOrProbe 16 1 459 81 :0 :0 :0 :0 22:39:30.566 ProbeFlsh 16 1 2764 0 :0 :0 :0 :0
<Truncated Output>

fcplogshow Time Stamp Event Port file&lineno arg0 arg1 arg2 arg3 arg4 ====================================================================================== 10:11:00.850 FlshOrProbe 94 1 455 80 :0 :0 :0 :0 10:11:00.850 PrbMsg 94 1 490 0 :0 :0 :0 :0 10:11:00.851 StartProbe 94 1 957 1 :0 :0 :0 :0 10:11:00.851 StartProbe 94 1 996 40000000:0 :0 :0 :0 10:11:00.851 ProbeFlsh 94 1 2765 1 :0 :0 :0 :0 10:11:00.854 SndPLOGI 94 1 1428 1002dd28:15e00 :1 :0 :207cc 10:11:00.855 AsyResp 94 1 1537 1002dd28:1002de90:80 :1 :107cc 10:11:00.855 ElsRsp 94 1 1603 15e00 :2000000 :8 :0 :980000 10:11:00.856 SndPRLI 94 1 2013 1002dd28:15e00 :2 :7cd :0 10:11:00.856 AsyResp 94 1 1537 1002dd28:1002e028:80 :2 :107cd 10:11:00.856 ElsRsp 94 1 1603 15e00 :2100014 :0 :21 :980000 10:11:00.858 SndLOGO 94 1 1926 15e00 :1002dd28:0 :0 :207ce 10:11:00.858 SndLOGO 94 1 1933 6a5 :0 :0 :0 :0 10:11:00.858 AsyResp 94 1 1537 1002dd28:1002e028:80 :4 :107ce 10:11:00.858 ElsRsp 94 1 1603 15e00 :2000000 :2 :0 :980000
2-74

10:11:00.858 10:42:45.374 10:42:45.374 10:42:45.374 10:43:57.039 10:43:57.039 10:43:57.040 10:43:57.040 10:43:57.040 10:43:57.041 10:43:57.042 10:43:57.042 10:43:57.043 10:43:57.043 10:43:57.043 10:43:57.044 10:43:57.044 10:43:57.045 10:43:57.045 10:43:57.045 IUDel FlshOrProbe ProbeFlsh SCNRcvd FlshOrProbe PrbMsg StartProbe StartProbe ProbeFlsh SndPLOGI AsyResp ElsRsp SndPRLI AsyResp ElsRsp SndLOGO SndLOGO AsyResp ElsRsp IUDel 94 94 94 94 94 94 94 94 94 94 94 94 94 94 94 94 94 94 94 94 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1728 455 2765 3530 455 490 957 996 2765 1428 1537 1603 2013 1537 1603 1926 1933 1537 1603 1728 1002dd28:1002dd28:0 81 :0 :0 0 :0 :0 2 :0 :0 80 :0 :0 0 :0 :0 1 :0 :0 40000000:0 :0 1 :0 :0 1002dd28:15e00 :1 1002dd28:1002de90:80 15e00 :2000000 :8 1002dd28:15e00 :2 1002dd28:1002e028:80 15e00 :2100014 :0 15e00 :1002dd28:0 6a5 :0 :0 1002dd28:1002e028:80 15e00 :2000000 :2 1002dd28:1002dd28:0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :0 :1 :0 :ae5 :2 :21 :0 :0 :4 :0 :0 :1 :0 :0 :0 :0 :0 :0 :0 :0 :20ae4 :10ae4 :980000 :0 :10ae5 :980000 :20ae6 :0 :10ae6 :980000 :1
2-75
fdmicacheshow
Available in Fabric OS versions: v4.1, v4.2 Troubleshooting Use: Use this command to display abbreviated remote FDMI device information according to remote domain ID. This information is gathered from edge devices that support the FDMI protocol. If an HBA in the fabric supports FDMI then information can be gathered from the HBA using the FDMIshow command, information would also be shared among fabric switches and displayed using this fdmicacheshow command. Use this command to display FDMI cache information for remote domains only. The state of each remote domain, identified by its domain ID, is shown to be either UNKNOWN, KNOWN, UNSUPPORTED, or ERROR. The revision of FDMI supported is also shown followed by the identifiers of all the HBAs at the domain and the corresponding registered port list. For HBAs, only the HBA identifiers and registered port lists are show. No detailed HBA attributes are displayed. For registered ports, only its port identifier and its corresponding HBA are shown. No detailed port attributes are displayed. Example 2-19: To display the FDMI cache:
switch:admin> fdmicacheshow Switch entry for domain 1 state: known version: v410 wwn: 10:00:00:60:69:80:4f:85 No devices. Total count of devices on the switch is 0 switch:admin>
Example 2-20: Example:

fdmicacheshow: Switch entry for domain 2 state: known version: v310 wwn: 10:00:00:60:69:51:2d:0b No devices. Total count of devices on the switch is 0

fdmicacheshow: No entry is found!
2-76
fdmishow
Available in Fabric OS versions: v4.1, v4.2 Troubleshooting Use: Use this command to display detailed FDMI device information. Use this command to display FDMI information for all HBAs and ports. Detailed FDMI information is displayed for local HBAs and ports. This information includes the HBA with its corresponding ports, along with their respective attributes. Only abbreviated FDMI information is shown for HBA and ports on remote switches. Example 2-21: To display FDMI information on a local switch:
switch:admin> fdmishow Local HBA database contains: 10:00:00:00:c9:25:9b:96 Ports: 1 10:00:00:00:c9:25:9b:96 Port attributes: FC4 Types: 0x0000010000000001000000000000000000000000000000000000000 000000000 Supported Speed: 0x00000001 Port Speed: 0x00000001 Frame Size: 0x00000800 HBA attributes: Node Name: 20:00:00:00:c9:25:9b:96 Manufacturer: Emulex Corporation Serial Number: 0000c9259b96 Model: LP9000 Model Description: Emulex LightPulse LP9000 1 Gigabit PCI Fibre Channel Adapter Hardware Version: 1002806D Driver Version: 5-5.00A6 Firmware Version: 3.81A1 OS Name and Version: Windows 2000 Max CT Payload Length: 0x00ff0000 Local Port database contains: 10:00:00:00:c9:25:9b:96 Remote HBA database contains: 10:00:00:00:c9:26:0f:e4 Ports: 1 10:00:00:00:c9:26:0f:e4 Remote Port database contains: 10:00:00:00:c9:26:0f:e4 switch:admin>

fdmishow: Local HBA database contains no entry. Local Port database contains no entry. Remote HBA database contains no entry. Remote Port database contains no entry.
2-77
feiDumpPrint
Troubleshooting Use: Use this command to identify Ethernet problems that could be preventing clean Ethernet access to the switch. Symptoms would include firmware download or configupload timeouts or failures. Attempt fixing by setting the Ethernet settings at each end the same or by directly accessing the switch using a cross-over cable or HUB. Available in Fabric OS versions: v3.1, v3.1.2 (Network Command Group) Version Differences: v4.2 Example Output: NA Additional Example/Case Studies: Example 2-39: This is an example output from v3.1.2
feiDumpPrint Tx good frames: Tx MAXCOL errors: Tx LATECOL errors: Tx underrun errors: Tx lost CRS errors: Tx deferred: Tx single collisions: Tx multiple collisions: Tx total collisions: Rx good frames: Rx CRC errors: Rx alignment errors: Rx resource errors: Rx overrun errors: Rx collision detect errors: Rx short frame errors: 714 0 0 0 0 0 0 0 0 890 0 0 0 0 0 0
2-78
feiIterateRFDRings
Available in Fabric OS versions: v3.1, v3.1.2 (Network Command Group) v4.2 Example Output: NA Additional Example/Case Studies: Example 2-40: Output from v3.1.2
feiIterateRFDRings pRFD ring forwards [0] pRFD=0x10017800 [1] pRFD=0x10017e00 [2] pRFD=0x10018400 [3] pRFD=0x10018a00 [4] pRFD=0x1000d000 [5] pRFD=0x1000d600 [6] pRFD=0x1000dc00
Troubleshooting Use: Note: This command has no additional Fabric OS information at this time. As the information becomes available the command will be inserted in this section.
2-79
ficondbg log
Available in Fabric OS versions: v4.2 (Services Command Group) Troubleshooting Use: This is a Ficon Internal command. It displays FICON internal data structures. It is used for debugging FICON in a simulation mode. This command allows an administrator to display FICON environment information and allows testing FICON in a simulation environment mode. Note: Use the output of this command to quickly see that attached device went through all FICON protocol steps: QSA (verify security is present), LIRR, and RNID. See Ficonshow lirr on page 2-83 and ficonshow rnid on page 2-86.
Note:
For additional information see Brocade Support for FICON Reference Guide, v4.1.2 2-3 Publication Number: 53-0000525-05
v4.2 Example Output: Example 2-41: See associated supportshow output in Example 2-42
Port 43 : Idx Description Requestor 1 ELS_QSA_BEGIN 0x502b00 2 ELS_QSA_END 0x502b00 3 ELS_LIRR_BEGIN 0x502b00 4 ELS_LIRR_END 0x502b00 5 ELS_RNID_BEGIN 0x502b00 6 ELS_RNID_END 0x502b00 7 ELS_LIRR_BEGIN 0x502b00 8 ELS_LIRR_END 0x502b00 9 MSG_IU_TO_BEGIN0x0 10 MSG_IU_TO_END 0x0 DlyMS 1 0 0 0 3 0 0 0 4 0 ElpMS 0 8 0 64 0 25 0 5 0 49 T_ID 916 916 916 916 916 916 916 916 916 916 RcvT Wed Feb Wed Feb Wed Feb Wed Feb Wed Feb Wed Feb Wed Feb Wed Feb Wed Feb Wed Feb
4 4 4 4 4 4 4 4 4 4
10:41:15 10:41:15 10:41:15 10:41:15 10:41:15 10:41:15 10:41:15 10:41:15 10:41:15 10:41:15
2004 2004 2004 2004 2004 2004 2004 2004 2004 2004
Example 2-42: switchshow output associated with all FICON related commands
switchshow: switchName:uly80 switchType:10.0 switchState:Online switchMode:Native switchRole:Principal switchDomain:80 switchId:fffc50 switchWwn:10:00:00:60:69:80:1e:4e zoning: ON (ficon1) switchBeacon:OFF blade1 Beacon: OFF blade2 Beacon: OFF blade3 Beacon: OFF blade4 Beacon: OFF Area Slot Port Media Speed State ===================================== 0 1 0 -N2 No_Module 1 1 1 id N2 Online E-Port 10:00:00:05:1e:34:01:36 "daz22" (Trunk master) 2 1 2 -N2 No_Module 3 1 3 id N2 No_Light 4 1 4 -N2 No_Module 5 1 5 id N2 No_Light 6 1 6 id N2 Online E-Port 10:00:00:60:69:90:02:95 "term206" (downstream)(Trunk master) 7 1 7 id N2 No_Light 8 1 8 -N2 No_Module 9 1 9 id N2 No_Light
2-80

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 10 11 12 13 14 15 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 id ---id id id id -id id -id id id id -id id id id id id id id id -id --id id id id id id id id id id id -id id id id -id id id id id id id N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2
Online F-Port 50:05:07:64:01:40:14:54 No_Module No_Module No_Module Online F-Port 50:05:07:64:01:00:14:62 No_Light No_Light No_Light No_Module No_Light Online F-Port 10:00:00:00:c9:2b:9d:83 No_Module No_Light Online F-Port 50:05:07:64:01:00:0b:45 No_Light No_Light No_Module Online F-Port 50:05:07:64:01:00:10:d2 Online L-Port 1 private No_Light No_Light Online F-Port 50:05:07:64:01:00:11:79 No_Light No_Light Online F-Port 50:05:07:63:00:c6:96:aa Online F-Port 50:05:07:64:01:00:14:54 No_Module No_Light No_Module No_Module No_Light Online E-Port (Trunk port, master is Slot 3 Port 10) Online E-Port 10:00:00:60:69:80:1e:4f "uly81" (downstream)(Trunk master) Online F-Port 50:05:07:64:01:00:16:05 No_Light Online F-Port 50:05:07:64:01:40:11:79 No_Light No_Light No_Light No_Light No_Light No_Module No_Light Online F-Port 50:05:07:63:00:cc:96:aa Online E-Port 10:00:00:60:69:80:1e:4f "uly81" (Trunk master) Online E-Port (Trunk port, master is Slot 4 Port 6) No_Module Online E-Port 10:00:00:60:69:90:0c:a8 "term208" (downstream)(Trunk master) Online E-Port (Trunk port, master is Slot 4 Port 9) Online L-Port 1 private Online E-Port (Trunk port, master is Slot 4 Port 13) Online E-Port 10:00:00:60:69:80:45:7c "uly120" (downstream)(Trunk master) No_Light Online F-Port 50:05:07:64:01:40:16:05
2-81
ficonshow ilir
Available in Fabric OS versions: v4.2 Troubleshooting Use: Display all implicit link incidents (FRU failures) within the local switch. Invoke ficonshow ilir fabric to display fabric FRU failures. Note: For additional information see Brocade Support for FICON Reference Guide, v4.1.2 2-3 Publication Number: 53-0000525-05

ficonshow ilir: {FRU Failure [2]: Power Supply[2] failure occurred on Mon Jan 13 12:11:38 2003 Fmt Protocol Domain Fabric WWN Switch WWN 0x18 FICON 80 10:00:00:60:69:33:33:33 10:00:00:60:69:80:1e:4e FRU part number: 23000000602 FRU serial number: FL2L0001071 {Listener Port Type Listener PID Listener Port WWN N 0x502b00 50:05:07:64:01:00:15:8d) {FRU Failure [3]: Power Supply[4] failure occurred on Mon Jan 13 12:11:38 2003 Fmt Protocol Domain Fabric WWN Switch WWN 0x18 FICON 80 10:00:00:60:69:33:33:33 10:00:00:60:69:80:1e:4e FRU part number: 23000000602 FRU serial number: FL2L0001060 {Listener Port Type Listener PID Listener Port WWN N 0x502b00 50:05:07:64:01:00:15:8d
Note:
The above outputs show a power supply failure on domain 80, WWN 10:00:00:60:69:80:1e:4e in a fabric with principal switch WWN 10:00:00:60:69:33:33:33 (Fabric WWN). The power supply part number and serial number are displayed along with listening port information (an end device listening for this type of information and possibly reporting same).
2-82
ficonshow lirr
Available in Fabric OS versions: v4.2 Troubleshooting Use: Use this command to determine which devices did an LIRR. Link Incident Record Registration (LIRR): Link Incident Record Registration (LIRR) allows a device to register to listen for link incidents; the device does not need to identify itself. If the device needs to be monitored for link incidents, then the device can perform the steps of RNID.
v4.2 Example Output: Example 2-44: See associated supportshow output in Example 2-42
ficonshow lirr: {Fmt Type PID Listener Port WWN 0x18 N 500a00 50:05:07:64:01:40:14:54 0x18 N 500e00 50:05:07:64:01:00:14:62 0x18 N 501700 50:05:07:64:01:00:0b:45 0x18 N 501b00 50:05:07:64:01:00:10:d2 0x18 N 501f00 50:05:07:64:01:00:11:79 0x18 N 502300 50:05:07:64:01:00:14:54 0x18 N 502b00 50:05:07:64:01:00:16:05 0x18 N 502d00 50:05:07:64:01:40:11:79 0x18 N 503f00 50:05:07:64:01:40:16:05 } The Local LIRR database has 9 entries. Switch Port WWN 20:0a:00:60:69:80:1e:4e 20:0e:00:60:69:80:1e:4e 20:17:00:60:69:80:1e:4e 20:1b:00:60:69:80:1e:4e 20:1f:00:60:69:80:1e:4e 20:23:00:60:69:80:1e:4e 20:2b:00:60:69:80:1e:4e 20:2d:00:60:69:80:1e:4e 20:3f:00:60:69:80:1e:4e Listener Type Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional
The output fields depicted above are: Fmt Port Type Displays the record-registration format. Displays the port type.
U is unknown. N is N_Port.
NL is NL_Port.
PID Displays the 24-bit Fibre Channel Port address in 0xDDAAPP format. DD is Domain ID. AA is Area ID. PP is AL_PA ID. Listener Port WWNDisplays the channel HBA port World Wide Name. Switch Port WWN Displays the switch port World Wide Name. Listener Type Indicates the listener type as one of the following:
Conditional: This port receives a link incident record if no other recipients from the established registration list have been chosen.
Unconditional: This port is always chosen as a recipient of a link incident record.
Note:
For additional information see Brocade Support for FICON Reference Guide, v4.1.2 2-3 Publication Number: 53-0000525-05
2-83
ficonshow rlir
Available in Fabric OS versions: 4.2 Troubleshooting Use: Displays all RLIR entries for the local RLIR database. RLIR - Registered Link Incident Record Link incidents are problems that occur either on links between a host channel and the switch or between the storage CU port and the switch, including the following: bit-error-rate threshold exceeded loss of signal or synchronization non-operational primitive sequence (NOS) recognized primitive sequence timeout invalid primitive sequence for port state An RLIR report is generated for each link incident and reported to a LIRR registered listener. v4.2 Example Output: Example 2-45:
ficonshow RLIR {Fmt Type PID PortIncident Count TS Format Time Stamp 0x18 F d00d00 13 2 Time server Tue Sep 30 04:11:01 2003 Port Status: Link not operational Link Failure Type: Loss of signal or synchronization Registered Port WWN Registered Node WWN Flag Node Parameters 50:05:07:64:01:40:13:dd 50:05:07:64:00:c1:69:ca 0x10 0x200127 Type Number: 002064 Model Number: 103 Manufacturer: IBM Plant of Manufacture: 02 Sequence Number: 0000000169CA tag: 270d Switch Port WWN Switch Node WWN Flag Node Parameters 20:0d:00:60:69:90:0c:a8 10:00:00:60:69:90:0c:a8 0x00 0x200a0d Type Number: SLKWRM Model Number: 12K Manufacturer: BRD Plant of Manufacture: CA Sequence Number: 0FA03X900CA8 tag: d00d The RLIR database has 1 entry.
The output fields depicted above are: Fmt Port Type Displays the record-registration format. Displays the port type.
U is unknown. N is N_Port.
NL is NL_Port.
Port Number Incident Count TS Format Time Stamp 13 Displays the incident count. This number increases by 1 for each incident within the individual switch. Displays the Time Server format. Displays the time stamp expressed in the date format.
2-84
Fabric OS SupportShow Information Port Status Displays the status of the port. One of the following messages is displayed: Link degraded but operational
Link not operational

Link Failure (Incident) Type Indicates the link incident type as one of the following (in this case the link failure being reported in a Loss of Signal or Synchronization failure): Bit-error-rate threshold exceeded Loss of Signal or Synchronization NOS recognized Primitive Sequence timeout
Invalid Primitive Sequence for Port State

Registered Port WWN - Displays the devices (channel or storage CU) port World Wide Name associated with the device HBA. Registered Node WWN - Displays the devices node World Wide Name associated with the device HBA. Flag 10 Indicates that the node ID of the channel port is valid.: Node ParametersDisplays the node type for the switch in three bytes: 0xAABBCC. The meaning of each byte 0x200127 is described here: Byte AA: 0x20 FC-SB-2 and updates. Byte BB: In this case 0x01- Direct access storage device, if it is a storage port; otherwise, it is not channel-to-channel capable. Byte CC: 0x27 Port number. It is dynamically assigned whenever a link incident occurs. Type Number Model Number Manufacturer Sequence Number Tag Flag 00 Displays the type number of the self-describing node. It also describes the machine type. Displays the model number. Displays the manufacture name or code. The sequence number of the self-describing node, in this case is 0000000169CA Displays the physical identifier for the self-describing node interface (270d in this case) indicates that the node ID of the (storage port for RNID, switch for SwitchRNID) is valid.
Plant of manufacturer Displays the manufacture plant name or code. The code in this case is 02
Switch node and port WWN Node Parameters Displays the node type for the switch in three bytes: 0xAABBCC. The meaning of each byte 0x200a0d is described here: Byte AA: 0x20 FC-SB-2 and updates. Byte BB: In this case 0x0a- Switch Byte CC: 0x0d Port number that is dynamically assigned whenever a link incident occurs. Type Number: SLKWRM describes a Brocade switch type Model Number: Brocade (vendor) model number 12k Manufacturer: Brocade (BRD) Plant of Manufacturer: CA (California) Sequence Number: 0FA03X900CA8 (This looks like the switch serial number with extra numbers) Tag: d00d - a physical identifier for the self-describing node interface Note: For additional information see Brocade Support for FICON Reference Guide, v4.1.2. (Publication Number: 53-0000525-05)
2-85
ficonshow rnid
Available in Fabric OS versions: 4.2 Troubleshooting Use: Displays all registered node identification data within the local switch Request Node Identification Data (RNID): Request Node Identification Data (RNID) allows a device (host channel or storage CU port) and switch to identify themselves to each other, as follows: 1. 2. The host channel or storage CU port initiates the exchange by asking the switch for its node ID. The switch responds with the following information (default values are in parentheses):
switch World Wide Name switch type (SLKWRM) switch model number (12K) switch manufacturer (BRD) switch plant of manufacture (CA) switch sequence number switch tag
The sequence number for Brocade switches is the Brocade serial number that is labeled on the outside of the switch. Note: For additional information see Brocade Support for FICON Reference Guide, v4.1.2 2-3 Publication Number: 53-0000525-05. Use the information in this document to decipher the ficonshow RNID information depicted here.

ficonshow rnid: {Fmt Type PID Registered Port WWN Registered Node WWN flag Parm 0x18 N 500a00 50:05:07:64:01:40:14:54 50:05:07:64:00:c1:69:ca 0x10 0x20013f Type number: 002064 Model number:103 Manufacturer:IBM Plant of Manufacture:02 Sequence Number:0000000169CA tag: 3f0a {Fmt Type PID Registered Port WWN Registered Node WWN flag Parm 0x18 N 500e00 50:05:07:64:01:00:14:62 50:05:07:64:00:c1:69:ca 0x10 0x200116 Type number: 002064 Model number:103 Manufacturer:IBM Plant of Manufacture:02 Sequence Number:0000000169CA tag: 160e {Fmt Type PID Registered Port WWN Registered Node WWN flag Parm 0x18 N 501700 50:05:07:64:01:00:0b:45 50:05:07:64:00:c1:69:ca 0x10 0x200128 Type number: 002064 Model number:103 Manufacturer:IBM Plant of Manufacture:02 Sequence Number:0000000169CA tag: 2817 {Fmt Type PID Registered Port WWN Registered Node WWN flag Parm 0x18 N 501b00 50:05:07:64:01:00:10:d2 50:05:07:64:00:c1:69:ca 0x10 0x200142 Type number: 002064 Model number:103
2-86

Manufacturer:IBM Plant of Manufacture:02 Sequence Number:0000000169CA tag: 421b {Fmt Type PID Registered Port WWN 0x18 N 501f00 50:05:07:64:01:00:11:79 Type number: 002064 Model number:103 Manufacturer:IBM Plant of Manufacture:02 Sequence Number:0000000169CA tag: 3c1f {Fmt Type PID Registered Port WWN 0x18 N 502200 50:05:07:63:00:c6:96:aa Type number: 002105 Model number:800 Manufacturer:IBM Plant of Manufacture:13 Sequence Number:000000022802 tag: 0088 {Fmt Type PID Registered Port WWN 0x18 N 502300 50:05:07:64:01:00:14:54 Type number: 002064 Model number:103 Manufacturer:IBM Plant of Manufacture:02 Sequence Number:0000000169CA tag: 3e23 {Fmt Type PID Registered Port WWN 0x18 N 502b00 50:05:07:64:01:00:16:05 Type number: 002064 Model number:103 Manufacturer:IBM Plant of Manufacture:02 Sequence Number:0000000169CA tag: 082b {Fmt Type PID Registered Port WWN 0x18 N 502d00 50:05:07:64:01:40:11:79 Type number: 002064 Model number:103 Manufacturer:IBM Plant of Manufacture:02 Sequence Number:0000000169CA tag: 3d2d {Fmt Type PID Registered Port WWN 0x18 N 503500 50:05:07:63:00:cc:96:aa Type number: 002105 Model number:800 Manufacturer:IBM Plant of Manufacture:13 Sequence Number:000000022802 tag: 0020 {Fmt Type PID Registered Port WWN 0x18 N 503f00 50:05:07:64:01:40:16:05 Type number: 002064 Model number:103 Manufacturer:IBM Plant of Manufacture:02 Sequence Number:0000000169CA tag: 093f 11 valid entries, 0 not current entries The Local RNID database has 11 entries.
Registered Node WWN flag Parm 50:05:07:64:00:c1:69:ca 0x10 0x20013c
Registered Node WWN flag Parm 50:05:07:63:00:c0:96:aa 0x00 0x200100
Registered Node WWN flag Parm 50:05:07:64:00:c1:69:ca 0x10 0x20013e
Registered Node WWN flag Parm 50:05:07:64:00:c1:69:ca 0x10 0x200108
Registered Node WWN flag Parm 50:05:07:64:00:c1:69:ca 0x10 0x20013d
Registered Node WWN flag Parm 50:05:07:64:00:c1:69:ca 0x10 0x200109
2-87
ficonshow switchrnid
Available in Fabric OS versions: 4.2 Troubleshooting Use: Displays node identification data for the local switch. Request Node Identification Data (RNID): Request Node Identification Data (RNID) allows a device (host channel or storage CU port) and switch to identify themselves to each other, as follows: 1. 2. The host channel or storage CU port initiates the exchange by asking the switch for its node ID. The switch responds with the following information (default values are in parentheses):
switch World Wide Name switch type (SLKWRM) switch model number (12K) switch manufacturer (BRD) switch plant of manufacture (CA) switch sequence number switch tag
The sequence number for Brocade switches is the Brocade serial number that is labeled on the outside of the switch. v4.2 Example Output: Example 2-47: See associated supportshow output in Example 2-42
ficonshow switchrnid: { {Switch WWN flag Parm 10:00:00:60:69:80:1e:4e0x00 0x200a00 Type number: 123456 Model number:0BC Manufacturer:BRD Plant of Manufacture:NY Sequence Number:abc123456789 tag: 00ff } } The Local switch RNID database has 1 entries.
Note:
For additional information see Brocade Support for FICON Reference Guide, v4.1.2 2-3 Publication Number: 53-0000525-05. Use the information in this document to decipher the ficonshow switchrnid information depicted here.
2-88
filterportshow
Available in Fabric OS versions: v4.1, 4.2 (Filter Command Group) v4.2 Example Output: This Filter Command Group output is not enabled by default. When enabled it will display the filters per port. Troubleshooting Use: If filtering is used the output of this command would tell you what filtering is enabled on each port. Additional Example/Case Studies: Example 2-48: Truncated output from a SW3900 with v4.2 code, no filtering enabled.
filterportshow 0: Filter port indicator: BF_ACCESS_CTL=0, BF_ZTYPE_SET=0, BF_TRAP_PLOGI=0 BF_TRAP_RPTLUN=0, BF_EXCLUDE=0, BF_LUN_ZONING=0 BF_BLOCKING=0, BF_ZONE_ENABLE=0, BF_ONE_PROTOCOL=0 BF_SOFT_ZONING=0, BF_ZGROUP_SET=0 0xcaaa44b0: priority 7fffffff0xcaaa4480: listA 0xcaaa4484: listB 000000070xcaaa4488: frozen 0xcaaa448c: discard 004008000xcaaa4490: forward Filter parity check control register: Destination Group RAM parity=1 Source Group RAM parity=1 Field value RAM D parity=1 Field value RAM C parity=1 Field value RAM B parity=1 Field value RAM A parity=1 Filter parity check status register: Destination Group RAM parity=0 Source Group RAM parity=0 Field value RAM D parity=0 Field value RAM C parity=0 Field value RAM B parity=0 Field value RAM A parity=0 Shadowed lun offset register: Don't check AL_PA=0, Don't check FC_TYPE=0 fc_type=0xff offset mask: 0x40 0x40 0x40 0x40 Real lun offset register: Don't check AL_PA=0, Don't check FC_TYPE=0 fc_type=0xff offset mask: 0x40 0x40 0x40 0x40 Zoning (hardware) disabled Shadowed filters Filter 0: fv_select= 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 scam_nomatch=0, dcam_nomatch=1, scam_match=0, dcam_match=1 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 Filter 1: fv_select= 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 scam_nomatch=0, dcam_nomatch=1, scam_match=0, dcam_match=1 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 <truncated output> Real filters Filter 0: fv_select= 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 scam_nomatch=0, dcam_nomatch=1, scam_match=0, dcam_match=1 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 Filter 1: fv_select= 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 scam_nomatch=0, dcam_nomatch=1, scam_match=0, dcam_match=1
001297f0 000c0000 00a16008
2-89
inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 Filter 2: fv_select= 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 scam_nomatch=0, dcam_nomatch=1, scam_match=0, dcam_match=1 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 <truncated output> Filter dirty indicator: 0x00000000 Dynamic filter management structures 0: age=0, cmd=0x00, els=0 firstValid=0, lastValid=0 firstSeqCnt=0, lastSeqCnt=0 framesTrapped=0, lunData=0x00000000 Dynamic filter management structures 1: age=0, cmd=0x00, els=0 firstValid=0, lastValid=0 firstSeqCnt=0, lastSeqCnt=0 framesTrapped=0, lunData=0x00000000 Dynamic filter management structures 2: age=0, cmd=0x00, els=0 firstValid=0, lastValid=0 firstSeqCnt=0, lastSeqCnt=0 framesTrapped=0, lunData=0x00000000 iu pending queue for dynamic filter:
Note:
This command has no additional Fabric OS information at this time. As the information becomes available the command will be inserted in this section.
2-90
filtershow
Available in Fabric OS versions: v3.1, v3.1.2 (Filter Command Group) Version Differences: filtershow is a v4.x filterportshow like command v4.2 Example Output: NA Additional Example/Case Studies: Troubleshooting Use: This Filter Command Group output is not enabled by default. When enabled it will display the filters per port. If filtering is used the output of this command would tell you what filtering is enabled on each port. Example 2-49: V3.1.1b output from a fabric with 12 switches, 71 end devices and a zone with 1984 bytes committed from the 98232 byte zone database.
filtershow Default features: port_zoning: 1 wwn_zoning: 1 protocol_zoning: 0 lun_zoning 0 access_control: 0 forwardLun0ReportLun: 0 forwardLun0Inquiry: 0 forwardLun0TestUnitReady: 0 overwriteWithLunsCfged: 0 clearLunEntriesMissed: 0 virtualExpandable: 0 performance: 1 diagnostics: 1 Current features: port_zoning: 1 wwn_zoning: 1 protocol_zoning: 0 lun_zoning 0 access_control: 0 forwardLun0ReportLun: 0 forwardLun0Inquiry: 0 forwardLun0TestUnitReady: 0 overwriteWithLunsCfged: 0 clearLunEntriesMissed: 0 virtualExpandable: 0 performance: 1 diagnostics: 1 Port 0: (output truncated to only port 0) Filter port indicator: BF_ACCESS_CTL=0, BF_ZTYPE_SET=0, BF_TRAP_PLOGI=1 BF_TRAP_RPTLUN=0, BF_EXCLUDE=0, BF_LUN_ZONING=0 BF_BLOCKING=0, BF_ZONE_ENABLE=1, BF_ONE_PROTOCOL=0 BF_SOFT_ZONING=1 Shadowed lun offset register: Don't check AL_PA=0, Don't check FC_TYPE=0 fc_type=0xff offset mask: 0x40 0x40 0x40 0x40 Shadowed filters Filter DYNAMIC1-3 (outputs the same so combined): Not Installed fv_select= 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 scam_nomatch=0, dcam_nomatch=1, scam_match=0, dcam_match=1 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 Filter REMOTE_EMBEDDED: Installed fv_select= 0x10 0x10 0x10 0x10 0x10 0x10 0x08 0x10 0x10 0x10 0x10 0x10 0x10 0x10 0x10 0x10 scam_nomatch=0, dcam_nomatch=0, scam_match=0, dcam_match=0 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 Filter REPORT_LUN: Not Installed fv_select= 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
2-91
scam_nomatch=0, dcam_nomatch=1, scam_match=0, dcam_match=1 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 Filter PLOGI/PDISC/ADISC/LOGO trap1-3(outputs the same so combined): Installed fv_select= 0x02 0x10 0x10 0x10 0x0f 0x10 0x10 0x10 0x10 0x10 0x10 0x10 0x01 0x10 scam_nomatch=0, dcam_nomatch=0, scam_match=0, dcam_match=0 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=1, scam_or_dcam_mis=0 Filter RNID trap1-3 (outputs the same so combined): Installed fv_select= 0x02 0x10 0x10 0x01 0x10 0x10 0x10 0x10 0x10 0x10 0x10 0x10 0x10 0x10 scam_nomatch=0, dcam_nomatch=0, scam_match=0, dcam_match=0 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=1, scam_or_dcam_mis=0 Filter NON_FCP_CMD: Not Installed fv_select= 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 scam_nomatch=0, dcam_nomatch=1, scam_match=0, dcam_match=1 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 Filter FORWARD_ZONE_MATCH: Not Installed fv_select= 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 scam_nomatch=0, dcam_nomatch=1, scam_match=0, dcam_match=1 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 Filter TUR_INQ: Not Installed fv_select= 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 scam_nomatch=0, dcam_nomatch=1, scam_match=0, dcam_match=1 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 Filter FORWARD_LINK_CTL: Installed fv_select= 0x10 0x10 0x10 0x10 0x10 0x10 0x10 0x10 0x10 0x10 0x10 0x01 0x10 0x10 scam_nomatch=0, dcam_nomatch=0, scam_match=0, dcam_match=0 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 Filter TRAP_ELS_BLS: Not Installed fv_select= 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 scam_nomatch=0, dcam_nomatch=1, scam_match=0, dcam_match=1 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 Filter DCAM_MISS_SCAM_MATCH: Not Installed fv_select= 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 scam_nomatch=0, dcam_nomatch=1, scam_match=0, dcam_match=1 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 Filter SCAM_MISS_DCAM_MATCH: Not Installed fv_select= 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 scam_nomatch=0, dcam_nomatch=1, scam_match=0, dcam_match=1 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 Filter DCAM_OR_SCAM_MISS: Not Installed fv_select= 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 scam_nomatch=0, dcam_nomatch=1, scam_match=0, dcam_match=1 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 Filter ZONE_MISS: Not Installed fv_select= 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 scam_nomatch=0, dcam_nomatch=1, scam_match=0, dcam_match=1 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 Filter FORWARD_MULTICAST: Installed fv_select= 0x10 0x10 0x10 0x10 0x10 0x10 0x10 0x10 0x08 0x10 0x10 0x10 0x10 0x10 scam_nomatch=0, dcam_nomatch=0, scam_match=0, dcam_match=0 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 Filter DISCARD_ALL: Not Installed fv_select= 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 scam_nomatch=0, dcam_nomatch=1, scam_match=0, dcam_match=1 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 Filter FORWARD_ALL: Installed fv_select= 0x10 0x10 0x10 0x10 0x10 0x10 0x10 0x10 0x10 0x10 0x10 0x10 0x10 0x10 scam_nomatch=0, dcam_nomatch=0, scam_match=0, dcam_match=0 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 Filter FREE: Not Installed fv_select= 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 scam_nomatch=0, dcam_nomatch=1, scam_match=0, dcam_match=1 inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 Filter PERF1-8 (outputs the same so combined): Not Installed fv_select= 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 scam_nomatch=0, dcam_nomatch=1, scam_match=0, dcam_match=1
0x10 0x10
0x10 0x10
0x00 0x00
0x00 0x00
0x00 0x00
0x10 0x10
0x00 0x00
0x00 0x00
0x00 0x00
0x00 0x00
0x00 0x00
0x10 0x10
0x00 0x00
0x10 0x10
0x00 0x00
0x00 0x00
2-92

inA=0, noA=0, inB=0, noB=0, eitherAorB=0, neitherAnorB=0, scam_or_dcam_mis=0 Filter dirty indicator: 0x00000000 Dynamic filter management structures 0: age=0, cmd=0x00, els=0 firstValid=0, lastValid=0 firstSeqCnt=0, lastSeqCnt=0 framesTrapped=0, lunData=0x00000000 Dynamic filter management structures 1: age=0, cmd=0x00, els=0 firstValid=0, lastValid=0 firstSeqCnt=0, lastSeqCnt=0 framesTrapped=0, lunData=0x00000000 Dynamic filter management structures 2: age=0, cmd=0x00, els=0 firstValid=0, lastValid=0 firstSeqCnt=0, lastSeqCnt=0 framesTrapped=0, lunData=0x00000000 iu pending queue for dynamic filter: Performance filter: 0 Filter priority register: 0x7fffffff Filter selection (List A): 0x0000a7f0 Filter selection (List B): 0x00000007 Filter selection (frozen): 0x000f0000 Filter selection (discard): 0x00200000 Filter selection (forward): 0x00505808 Filter parity check control register: Destination Group RAM parity=1 Source Group RAM parity=1 Field value RAM D parity=1 Field value RAM C parity=1 Field value RAM B parity=1 Field value RAM A parity=1 Filter parity check status register: Destination Group RAM parity=0 Source Group RAM parity=0 Field value RAM D parity=0 Field value RAM C parity=0 Field value RAM B parity=0 Field value RAM A parity=0 Real lun offset register: Don't check AL_PA=0, Don't check FC_TYPE=0 fc_type=0xff offset mask: 0x40 0x40 0x40 0x40 Zoning (hardware) enabled Filter DIDCAM GMISS workaround not applied Real filters <output trucated ... see shadow filter information above> Filter counters Filter counter for DYNAMIC1: 0x00000000 Filter counter for DYNAMIC2: 0x00000000 Filter counter for DYNAMIC3: 0x00000000 Filter counter for REMOTE_EMBEDDED: 0x00000006 Filter counter for REPORT_LUN: 0x00000000 Filter counter for PLOGI/PDISC/ADISC/LOGO trap1: 0x00000004 Filter counter for PLOGI/PDISC/ADISC/LOGO trap2: 0x00000004 Filter counter for PLOGI/PDISC/ADISC/LOGO trap3: 0x00000004 Filter counter for RNID trap1: 0x00000000 Filter counter for RNID trap2: 0x00000000 Filter counter for RNID trap3: 0x00000000 Filter counter for NON_FCP_CMD: 0x00000000 Filter counter for FORWARD_ZONE_MATCH: 0x00000000 Filter counter for TUR_INQ: 0x00000000 Filter counter for FORWARD_LINK_CTL: 0x00000000 Filter counter for TRAP_ELS_BLS: 0x00000000 Filter counter for DCAM_MISS_SCAM_MATCH: 0x00000000 Filter counter for SCAM_MISS_DCAM_MATCH: 0x00000000
2-93
Filter counter for DCAM_OR_SCAM_MISS: 0x00000000 Filter counter for ZONE_MISS: 0x00000000 Filter counter for FORWARD_MULTICAST: 0x00000000 Filter counter for DISCARD_ALL: 0x00000000 Filter counter for FORWARD_ALL: 0x0000001a Filter counter for FREE: 0x00000000 Filter counter for PERF1: 0x00000000 Filter counter for PERF2: 0x00000000 Filter counter for PERF3: 0x00000000 Filter counter for PERF4: 0x00000000 Filter counter for PERF5: 0x00000000 Filter counter for PERF6: 0x00000000 Filter counter for PERF7: 0x00000000 Filter counter for PERF8: 0x00000000 Shadowed fields Field 0: value=0x00 0x01 0x05 0x08, mask=0xff, offset=12 Field 1: value=0x06 0x00 0x00 0x00, mask=0xff, offset=4 Field 2: value=0x2a 0x0a 0x28 0x08, mask=0xff, offset=40 Field 3: value=0x78 0xff 0xff 0xff, mask=0xff, offset=28 Field 4: value=0x03 0x52 0x50 0x05, mask=0xff, offset=28 Field 5: value=0xff 0xff 0xff 0xff, mask=0xff, offset=9 Field 6: value=0xff 0xff 0xff 0xfc, mask=0xff, offset=10 Field 7: value=0xff 0xff 0xff 0xff, mask=0xff, offset=11 Field 8: value=0xff 0xff 0xff 0xff, mask=0xff, offset=7 Field 9: value=0xff 0xff 0xff 0xff, mask=0xff, offset=20 Field 10: value=0xff 0xff 0xff 0xff, mask=0xff, offset=21 Field 11: value=0xc0 0xff 0xff 0xff, mask=0xf0, offset=4 Field 12: value=0x00 0xff 0xff 0xff, mask=0xff, offset=29 Field 13: value=0xff 0xff 0xff 0xff, mask=0xff, offset=0 Field 14: value=0xff 0xff 0xff 0xff, mask=0xff, offset=0 Field 15: value=0xff 0xff 0xff 0xff, mask=0xff, offset=0 Field control Field 0: control=0xff 0xff 0xff 0xff Field 1: control=0xff 0x00 0x00 0x00 Field 2: control=0xff 0xff 0xff 0xff Field 3: control=0xff 0x00 0x00 0x00 Field 4: control=0xff 0xff 0xff 0xff Field 5: control=0xfe 0xfe 0xfe 0xfe Field 6: control=0xfe 0xfe 0xfe 0xff Field 7: control=0xfe 0xfe 0xfe 0x00 Field 8: control=0xfe 0xfe 0xfe 0xff Field 9: control=0xfe 0xfe 0xfe 0x00 Field 10: control=0xfe 0xfe 0xfe 0x00 Field 11: control=0xff 0x00 0x00 0x00 Field 12: control=0xff 0x00 0x00 0x00 Field 13: control=0x00 0x00 0x00 0x00 Field 14: control=0x00 0x00 0x00 0x00 Field 15: control=0x00 0x00 0x00 0x00 Field dirty indicator: 0x00000000 Real fields <truncated output - see shadowed fields output above> ...<truncated...only port 0 output displayed> Quad 0, port 0 to port 3: Real sidcam parameters Total # of rcam entries: 64 Current # of active rcam entries: 64 Size of cam entry (32bit word): 1 Offset of this rzgroup: 0 Size of this rzgroup: 2 Cam entries (only non-empty entries will be shown): Real didcam parameters Total # of rcam entries: 512 Current # of active rcam entries: 512 Size of cam entry (32bit word): 2 Offset of this rzgroup: 2
2-94

Size of this rzgroup: 16 Cam entries (only non-empty entries will be shown): Virtual sidcam parameters Total # of vcam entries: 64 Current # of active vcam entries: 0 Size of cam entry: 1 words Offset of associated vzgroup: 0 words Size of associated vzgroup: 2 words Cam entries (only non-empty entries will be shown): Cam index sort array: Virtual didcam parameters Total # of vcam entries: 512 Current # of active vcam entries: 0 Size of cam entry: 2 words Offset of associated vzgroup: 2 words Size of associated vzgroup: 16 words Cam entries (only non-empty entries will be shown): Cam index sort array: Real zone group A parameters Total # of RZgroups: 64 Current # of active RZgroups: 64 Size of RZgroup (in 32bit word): 18 words Free (head): 65535 Real zone group members index (only non-empty entries will be Real zone group B parameters Total # of RZgroups: 64 Current # of active RZgroups: 64 Size of RZgroup (in 32bit word): 18 words Free (head): 65535 Real zone group members index (only non-empty entries will be Virtual zone group A parameters Total # of VZgroups: 64 Current # of active VZgroups: 0 Size of VZgroup: 18 words Free (head): 0 Virtual zone group members index (only non-empty entries will Free virtual zone groups 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 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 Virtual zone group B parameters Total # of VZgroups: 64 Current # of active VZgroups: 0 Size of VZgroup: 18 words Free (head): 0 Virtual zone group members index (only non-empty entries will Free virtual zone groups 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 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
shown):
shown):
be shown):
be shown):
...<ouput for Quads 1-3 duplicate Quad 0 type information truncated >
2-95
firmwareShow
Available in Fabric OS versions: v4.1, v4.2 (supportshow - this command is available in all Fabric OS v4.x versions from CLI) Version Differences: Dual CP switch outputs show dual CP information. Additional Example/Case Studies: Troubleshooting Use: Use this command to display the Fabric OS versions on both partitions (primary and secondary) on the local CP and on the remote CP. This command identifies the status for each CP as Active or Standby, and will also identify the slot number for each CP. If there is only one CP available, the command displays the Fabric OS versions for the primary and secondary partitions on that CP. In order to invoke an auto magic firmwaredownload process all switch partitions must be at the same revision level. Use the firmwaredownload - s option to download firmware to the partitions on one logical switch of a dual CP switch. Use the firmwarecommit command to copy the firmware in the primary partition to the secondary partition. Use the firmwarerestore command to copy the firmware from the secondary partition to the primary. For more information, see the Brocade Fabric OS Reference and Chapter 3, Non-SupportShow Commands of this guide for more information. Examples: Example 2-22: To display the firmware version of a Silkworm 3900:
switch3900:admin> firmwareshow Local CP (Slot 5, CP0): Active Primary partition: v4.0.2 Secondary Partition: v4.0.2 Remote CP is Non-redundant. switch3900:admin>
Example 2-23: To display the firmware version of a Silkworm 12000:

firmwareshow: Local CP (Slot 5, CP0): Active Primary partition:v4.1.0 Secondary Partition:v4.1.0 Remote CP (Slot 6, CP1): Standby Primary partition:v4.1.0 Secondary Partition:v4.1.0

firmwareshow: Local CP (Slot 6, CP1): Active Primary partition:v4.2.0_beta1 Secondary Partition:v4.2.0_beta1 Remote CP (Slot 5, CP0): Standby Primary partition:v4.2.0_beta1 Secondary Partition:v4.2.0_beta1
Note:
If Local CP and Remote CP have different versions of firmware, please retry the firmwaredownload command or use firmwaredownload -s option to get the firmware on one CP to match the firmware on the other. If you choose not to automatically reboot when asked using this option and you later want to perform a non-disruptive reboot use the hareboot command instead of fastboot or reboot.
Firmware download problems could be related to network connectivity. 1. 2. 3. To verify network connectivity, execute host based ping to switch and/or traceroute (UNIX)/ tracert (Windows). Check network configuration: ifmodeshow eth0 for Linux switches or ifmodeshow fei0 for VxWorks switches (also look at supportShow /sbin/ifconfig output (Linux) or ifShow output (VxWorks). Use ifModeSet to change network configuration VxWorks switches require reboot.
2-96
Fabric OS SupportShow Information 4. 5. 6.
Try cycling the internet interface - on VxWorks based switches execute: ifdown fei0 and then ifUp fei0, on Linux based switches execute: ifdown eth0 and then ifUp eth0. FTP from server to itself determine directory your in and modify the path request line in the firmware download process accordingly. Compare switch behavior: RJ45 connected/not connected (Watch for CLOSE WAIT state outputs that do not disappear within 15 minutes in inetstatshow (VxWorks) and netstat a (Linux) outputs. Alternately, compare the SilkWorm 2800 push button tPBMenu response times, if more sluggish with network cable attached check LAN segment for excessive collisions.) Verify FTP server functionality and directory structure (you may need to use forward slashes). Understand expected firmware download processes so that you can recognize deviations; use the Brocade Fabric OS v4.2 Diagnostic and Error Message Guide to interpret firmware download error messages. Many firmware download process errors can be solved setting both ends of the network to the same speed or executing firmware download process using a direct attach method: a cross-over cable or HUB (check network router and switch tables).
7. 8.
2-97
fspfShow
Available in Fabric OS versions: v4.0, v4.1, v4.2 Additional Example/Case Studies: Troubleshooting Use: Use this command to display the Fibre Channel Shortest Path First (FSPF) protocol information, and internal data structures. FSPF is implemented by a single task, called tFspf. It displays global FSPF data structures. The display shows the following fields: Table 2-1 fspfShow display fields Field version domainID switchOnline domainConfirmed isl_ports trunk_ports f_ports seg_ports active_ports minLSArrival minLSInterval LSoriginCount startTime fspfQ fabP agingTID agingTo lsrDlyTID lsrDelayTo lsrDelayCount ddb_sem event_sch lsrRefreshCnt Description Version of FSPF protocol. Domain number of local switch. State of the local switch. v4.0 only. Domain of the local switch is currently confirmed. Fabric OS v4.0 only. Bit map of all E_Ports. Bit map of all the trunk ports. Fabric OSv4.0 only. Bit map of all the Fx_Ports. Fabric OSv4.0 only. Bit map of all the segmented ports. Fabric OSv4.0 only. Bit map of all the ONLINE ports. Fabric OS v4.0 only. FSPF constant used to throttle flooding procedure. The min* outputs are recorded in seconds FSPF constant used to throttle flooding procedure. The min* outputs are recorded in seconds. Internal variable. Start time of tFspf task (milliseconds from boot). FSPF input message queue. Pointer to fabric data structure. Aging timer ID . Aging time out value, in milliseconds used to age out old LSR information. The aging time out value is 10 seconds. Link State Record delay timer ID used to throttle new LSR generation. Link State Record delay time out value, in milliseconds. The delay LSR origination is 5 seconds. Counter of delayed Link State Records. FSPF semaphore ID. FSPF scheduled events bit map. Internal variable.
2-98
Example 2-24:
fspfshow: version= 2 domainID= 1 switchOnline= TRUE domainValid= TRUE isl_ports[0]= 0x00000000 isl_ports[1]= 0x00000000 trunk_ports[0]= 0x00000000 trunk_ports[1]= 0x00000000 f_ports[0]= 0x00002400 f_ports[1]= 0x00000000 seg_ports[0]= 0x00000000 seg_ports[1]= 0x00000000 active_ports[0]= 0x00002400 active_ports[1]= 0x00000000 minLSArrival= 3 minLSInterval= 5 LSoriginCount= 0 startTime= 120760 fspfQ= 0x10037790 fabP= 0x10037780 fspfShow (Cont.) agingTID= 0x1004cb00 agingTo= 10000 lsrDlyTID= 0x1004cb90 lsrDelayTo= 5000 lsrDelayCount= 0 ddb_sem= 0x10037858 fabP: event_sch= 0x0 lsrRefreshCnt= 0

fspfshow version = 2 domainID= 1 switchOnline= TRUE domainValid= TRUE isl_ports[0]= 0x00000000 isl_ports[1]= 0x00000000 isl_ports[2]= 0x00000000 isl_ports[3]= 0x00000000 trunk_ports[0]= 0x00000000 trunk_ports[1]= 0x00000000 trunk_ports[2]= 0x00000000 trunk_ports[3]= 0x00000000 f_ports[0]= 0x00000002 f_ports[1]= 0x00000000 f_ports[2]= 0x40000000 f_ports[3]= 0x80000000 seg_ports[0]= 0x00000000 seg_ports[1]= 0x00000000 seg_ports[2]= 0x00000000 seg_ports[3]= 0x00000000 active_ports[0]= 0x00000002 active_ports[1]= 0x00000000 active_ports[2]= 0x40000000
2-99
active_ports[3]= 0x80000000 minLSArrival= 3 minLSInterval= 5 LSoriginCount= 0 startTime= 29670 fspfQ = 0x1005dbc0 fabP = 0x1005dbb0 agingTID= 0x1007c818 agingTo = 10000 lsrDlyTID= 0x1007c870 lsrDelayTo= 5000 lsrDelayCount= 0 ddb_sem = 0x1005dc88
2-100
fssadmin -s chassis0 -q
Available in Fabric OS versions: v4.1, v4.2 Troubleshooting Use: This command is part of the hadump command output. Use the output of this and the rest of the hadump output to understand dual CP failover and firmwaredownload processes. fssadmin s -chassis0 q means give me fss output per single instance on chassis 0. Additional Example/Case Studies: See hadump on page 2-110 output for a complete story of this command and other hadump commands:
hadump/ System Command Group haShow/ System Command Group ipaddrshow / System Command Group sysc_dprintf/ System Command Group medbg -s1 -e1/ System Command Group fssadmin -s chassis0 q/ System Command Group fssadmin -s fcsw0 q/ System Command Group fssadmin -s fcsw1 q/ System Command Group

fssadmin -s chassis0 -q: === FSS Service Dump : chassis0 === == State == chassis0(0): ACTIVE(0), Required local = SYN_SUCC, prev = SYN_SUCC, peer = SYN_SUCC Name LocalRemote chassis0(M)SYN_SUCCSYN_SUCC em(M)SYN_SUCCSYN_SUCC pdm(M)SYN_SUCCSYN_SUCC rpc(M)SYN_SUCCSYN_SUCC == Statistic == tx-pkt tx(KB) rx-pkt rx(KB) UP (tor=341, tod=1357) em 9 32 2 0 61 W=2,1,-,-,303,1, pdm 85 151 2 0 43 W=2,2,-,-,-,-, rpc 2 0 2 0 0 W=2,1,-,-,-,-, == Config == chassis0(1.1) comp chassis01:1U comp em1:1U comp pdm1:1U comp rpc1:1U Warm Table: emEM_WARM_CHECK_POWER_STATES,,,EM_WARM_CHECK_FRU_OBJS,FSS_RECOV_ACTIVE pdmFSS_RECOV_ACTIVE,,,, rpcFSS_RECOV_ACTIVE,,,, Cold Table: emEM_COLD_CHECK_FRU_OBJS,FSS_RECOV_ACTIVE pdmFSS_RECOV_ACTIVE, rpcFSS_RECOV_ACTIVE, == SVC == major: 1minor: 1 lo: 0minor: 1 id: 0peerid: 0 epoch: 7log: 0 conn: 3bits: 1 recov: 0index: 6 upper: 6coldnum: 3 warmnum: 6stbynum: 4 stat: 4prevstat: 4 peerstat: 4sv_winsz: 64 nscm: 4
2-101
fssadmin -s fcsw0 -q
Available in Fabric OS versions: v4.1, v4.2 Troubleshooting Use: This command is part of the hadump command output. Use the output of this and the rest of the hadump output to understand dual CP failover and firmwaredownload processes. fssadmin s -fcsw0 q means give me fc switch output per single instance on logical switch 0. Additional Example/Case Studies: See hadump on page 2-110 output for a complete story of this command and other hadump commands: hadump haShow ipaddrshow sysc_dprintf medbg -s1 -e1 fssadmin -s chassis0 q fssadmin -s fcsw0 q fssadmin -s fcsw1 q v4.2 Example Output: Example 2-53:
fssadmin -s fcsw0 -q: === FSS Service Dump : fcsw0 === == State == fcsw0(2): ACTIVE(0), Required local = SYN_SUCC, prev = SYN_SUCC, peer = SYN_SUCC Name LocalRemote fcsw0(M)SYN_SUCCSYN_SUCC swc(M)SYN_SUCCSYN_SUCC cer(M)SYN_SUCCSYN_SUCC fcp(M)SYN_SUCCSYN_SUCC rt(M)SYN_SUCCSYN_SUCC fc(M)SYN_SUCCSYN_SUCC fabric(M)SYN_SUCCSYN_SUCC zone(M)SYN_SUCCSYN_SUCC fspf(M)SYN_SUCCSYN_SUCC ns(M)SYN_SUCCSYN_SUCC ms(M)SYN_SUCCSYN_SUCC ps(M)SYN_SUCCSYN_SUCC rcs(M)SYN_SUCCSYN_SUCC evm(M)SYN_SUCCSYN_SUCC track(M)SYN_SUCCSYN_SUCC ts(M)SYN_SUCCSYN_SUCC slap(M)SYN_SUCCSYN_SUCC security(M)SYN_SUCCSYN_SUCC web(M)SYN_SUCCSYN_SUCC snmp(M)SYN_SUCCSYN_SUCC fw(M)SYN_SUCCSYN_SUCC fdmi(M)SYN_SUCCSYN_SUCC diagfss(M)SYN_SUCCSYN_SUCC == Statistic == tx-pkt tx(KB) rx-pkt rx(KB) UP (tor=255, tod=67) swc 3717 1284 9 0 240 W=1,15,1,-,-,1,-,66,-,-,-,-,-,-,-,-, cer 18 3 10 0 246 W=1,-,-,1,-,-,-,66,1,-,-,-,-,-,-,-, fcp 11 5 4 0 263 W=3,-,-,2,-,-,-,76,1,-,-,-,-,-,-,-, rt 2 0 2 0 261 W=1,-,-,-,-,-,-,66,-,-,-,-,-,-,-,-, fc 3 0 2 0 261 W=1,-,-,1,2,-,-,-,-,-,-,-,-,-,-,-, fabric 4 7 2 0 260 W=1,-,-,-,-,1,-,-,1,4,-,-,-,-,-,-, zone 8 1 4 0 727 W=3,-,-,2,-,-,-,-,1,-,4,2,-,-,-,-, fspf 1839 110 3 0 182 W=2,-,-,-,4,-,-,-,1,-,-,-,-,-,-,-, ns 20 34 8 0 240 W=2,-,-,-,-,-,-,81,1,4,4,-,-,-,-,-,
/ / / / / / / /
System System System System System System System System
Command Command Command Command Command Command Command Command
Group Group Group Group Group Group Group Group
2-102

ms 8 51 ps 15 1 rcs 4 2 evm 3 13 track 2 0 ts 3230 504 slap 2 0 security 6 0 web 2 0 snmp 2 0 fw 2 0 fdmi 2 0 diagfss 2 0 == Config == fcsw0(2.1) comp fcsw02:1U comp swc2:1U comp cer2:2U comp fcp1:1U comp rt1:1U comp fc1:1U comp fabric1:1U comp zone1:1U comp fspf1:1U comp ns1:1U comp ms2:1U comp ps1:1U comp rcs1:1U comp evm1:1U comp track1:1U comp ts1:1U comp slap1:1U comp security2:1U comp web1:1U comp snmp1:1U comp fw1:1U comp fdmi1:1U comp diagfss1:1U 2 6 2 2 2 5 2 2 2 2 2 2 2 0 0 0 0 0 0 0 0 0 0 0 0 0 291 263 78 92 164 901 233 494 245 91 342 144 266 W=3,-,-,-,-,-,-,-,-,-,4,2,-,-,-,-, W=2,-,-,-,-,-,-,76,-,-,-,1,-,-,-,-, W=2,-,-,1,-,-,-,-,-,4,2,-,-,-,-,-, W=2,-,-,-,-,-,-,-,-,-,-,-,5,-,-,-, W=1,-,-,-,-,-,-,-,-,-,2,-,-,-,-,-, W=1,-,-,-,-,-,-,82,-,-,-,-,-,-,-,-, W=1,-,-,-,-,-,-,76,-,-,-,-,-,-,-,-, W=1,27,-,-,-,-,-,-,-,-,102,-,-,-,-,-, W=1,-,-,-,-,-,-,-,-,-,-,-,-,1,-,-, W=1,-,-,-,-,-,-,-,-,-,-,-,8,-,-,-, W=6,-,-,-,-,-,-,91,1,-,-,-,-,19,-,-, W=1,-,-,-,-,-,-,-,-,-,-,-,-,1,1,-, W=1,15,-,-,-,-,-,-,1,1,-,-,-,-,-,-,
Warm Table: swcSWC_RECOV_ONLINE_PORTS,SWC_RECOV_ONLINE_DONE,,,FSS_RECOV_ACTIVE,,SWC_RECOV_RESET_PORTS,,,,,,,, cer,,CER_RECOV_ONLINE_PORTS,,,,FSS_RECOV_ACTIVE,CER_RECOV_MASS_REROUTE,,,,,,, fcp,,FCP_WARM_INIT,,,,FCP_DATA_RECOV,FSS_RECOV_ACTIVE,,,,,,, rt,,,,,,FSS_RECOV_ACTIVE,,,,,,,, fc,,FC_FSS_WARM_1,FSS_RECOV_ACTIVE,,,,,,,,,,, fabric,,,,fab_recov_warm,,,fab_recov_eport,FSS_RECOV_ACTIVE,,,,,, zone,,ZN_IPC_REG,,,,,ZN_APPLY_PUSH,,FSS_RECOV_ACTIVE,ZN_EPORT_VALID,,,, fspf,,,FSPF_WARM_1,,,,FSS_RECOV_ACTIVE,,,,,,, ns,,,,,,NS_RDCFG,NS_SYNC,NSCAM_VER,FSS_RECOV_ACTIVE,,,,, ms,,,,,,,,,MS_WARMINIT,FSS_RECOV_ACTIVE,,,, ps,,,,,,FSS_PS_VERIFY,,,,FSS_RECOV_ACTIVE,,,, rcs,,RCS_IPC_REG,,,,,,RCS_XACT_COMPLETE,FSS_RECOV_ACTIVE,,,,, evm,,,,,,,,,,,FSS_RECOV_ACTIVE,,, track,,,,,,,,,FSS_RECOV_ACTIVE,,,,, ts,,,,,,FSS_RECOV_ACTIVE,,,,,,,, slap,,,,,,FSS_RECOV_ACTIVE,,,,,,,, securitySEC_FSS_RDDB,,,,,,,,,FSS_RECOV_ACTIVE,,,,, web,,,,,,,,,,,,FSS_RECOV_ACTIVE,, snmp,,,,,,,,,,,FSS_RECOV_ACTIVE,,, fw,,,,,,fwd_init,fwd_warm,,,,,FSS_RECOV_ACTIVE,, fdmi,,,,,,,,,,,,FSS_FDMI_SYNC_KERN,FSS_RECOV_ACTIVE, diagfssDIAGFSS_SW_RECOV_PRESWC,,,,,,,DIAGFSS_SW_RECOV_POSTSWC,FSS_RECOV_ACTIVE,,,,,, Cold Table: swcSWC_RECOV_COLD,,,FSS_RECOV_ACTIVE,,,,,
2-103
cerFSS_RECOV_ACTIVE,,,,,,,, fcpFCP_COLD_INIT,,,,FSS_RECOV_ACTIVE,,,, rt,,FSS_RECOV_ACTIVE,,,,,, fcFC_FSS_COLD_1,FSS_RECOV_ACTIVE,,,,,,, fabricfab_recov_cold,,,,FSS_RECOV_ACTIVE,,,, zone,ZN_CONF_INIT,ZN_DB_RES,,FSS_RECOV_ACTIVE,,,, fspfFSPF_COLD_1,,,,FSS_RECOV_ACTIVE,,,, nsNS_INIT_REG,,,,FSS_RECOV_ACTIVE,,,, ms,,,,,MS_COLDINIT,FSS_RECOV_ACTIVE,, ps,,,,,FSS_PS_CONF_INIT,FSS_RECOV_ACTIVE,, rcsRCS_CONF_INIT,,,,FSS_RECOV_ACTIVE,,,, evm,,,,,,,FSS_RECOV_ACTIVE, track,,,,,FSS_RECOV_ACTIVE,,, ts,TS_FSS_RCS_REG,,,,FSS_RECOV_ACTIVE,,, slap,,,,FSS_RECOV_ACTIVE,,,, security,SEC_FSS_RCS_REG,,,,,FSS_RECOV_ACTIVE,, web,,,,,,FSS_RECOV_ACTIVE,, snmp,,,,,FSS_RECOV_ACTIVE,,, fwfwd_init,fwd_cold,,,,,,FSS_RECOV_ACTIVE, fdmi,,,,,,,,FSS_RECOV_ACTIVE diagfssFSS_RECOV_ACTIVE,,,,,,,, == SVC == major: 2minor: 1 lo: 0minor: 1 id: 2peerid: 2 epoch: 7log: 0 conn: 3bits: 1 recov: 0index: 16 upper: 16coldnum: 10 warmnum: 16stbynum: 4 stat: 4prevstat: 4 peerstat: 4sv_winsz: 64 nscm: 23
2-104
fssadmin -s fcsw1 -q
Available in Fabric OS versions: v4.1, v4.2 Troubleshooting Use: This command is part of the hadump command output. Use the output of this and the rest of the hadump output to understand dual CP failover and firmwaredownload processes. fssadmin s -fcsw1 q means give me fc switch output per single instance on logical switch 1. Additional Example/Case Studies: See hadump on page 2-110 output for a complete story of this command and other hadump commands: hadump haShow ipaddrshow sysc_dprintf medbg -s1 -e1 fssadmin -s chassis0 q fssadmin -s fcsw0 q fssadmin -s fcsw1 q / / / / / / / / System System System System System System System System Command Command Command Command Command Command Command Command Group Group Group Group Group Group Group Group

fssadmin -s fcsw1 -q: /bin/cat /proc/fss/SWBD21_opt1.log [XCP] Tx 9292, Rx 388, Txb 2861K, Rxb 659K; dropped: 1, queued: 3898; pending evt: 0, pending Tx: 0 MEM-kern: 0, MEM-atom: 0, sor: 4844, tor: 39 STAMP SEQ SID CID ARG FLG evt-SYNCSUCC5019490620 0 0 evt-START501277602 0 0 0 cmd-START501277592 0 0 0 evt-SYNCSUCC5012775800 0 0 evt-DUMPRDY4978275420 0 0 evt-COMP497827532 0 0 2 evt-START487706380 0 0 0 cmd-START487706370 0 0 0 evt-DUMPRDY4877063500 0 0 evt-COMP487706340 0 0 2 cmd-CONNECT4877063020 0 0 cmd-CONNECT4877062800 0 0 evt-UPCONN4877062720 0 0 evt-UPCONN4877062600 0 0 evt-AVAILSVC4877062520 0 0 evt-AVAILSVC4877062400 0 0 msg-EXCH:Rx48770623655356553511 msg-EXCH:Tx487706226553565535140d0800 evt-TRACE487706210 0 0 5 evt-TRACE486786200 0 0 3 evt-TRACE373296190 0 0 4 evt-DOWNCONN3609761820 0 0 evt-STOP360976172 0 0 0 evt-DOWNCONN3609761600 0 0 evt-STOP360976150 0 0 0 evt-TRACE360976140 0 0 6 evt-SYNCSUCC1836559920 0 0 evt-START182614362 0 0 0 cmd-START182614352 0 0 0 evt-SYNCSUCC1826143400 0 0 evt-DUMPRDY1803943020 0 0 evt-COMP180394292 0 0 2
2-105
evt-START173663210 0 0 0 cmd-START173663200 0 0 0 evt-DUMPRDY1736631500 0 0 evt-COMP173663140 0 0 2 cmd-CONNECT1736631020 0 0 cmd-CONNECT1736630800 0 0 evt-UPCONN1736630720 0 0 evt-UPCONN1736630600 0 0 evt-AVAILSVC1736630520 0 0 evt-AVAILSVC1736630400 0 0 msg-EXCH:Rx17366303655356553511006f768 msg-EXCH:Tx172663026553565535140d0800 evt-TRACE172663010 0 0 5 evt-TRACE172653000 0 0 3 msg-EXCH:Tx5103299655356553530 evt-ACTIVE51032982 0 0 0 cmd-TAKE48482972 0 0 0 evt-ACTIVE48462960 0 0 0 cmd-TAKE48442950 0 0 0 evt-DOWNCONN479029420 0 0 evt-STOP47902932 0 0 0 evt-DOWNCONN479029200 0 0 evt-STOP47902910 0 0 0 evt-TRACE47902900 0 0 6 evt-TRACE47902890 0 0 4 evt-SYNCSUCC425228720 0 0 evt-START41771432 0 0 0 evt-SYNCSUCC417714000 0 0 evt-TRACE3939560 0 0 2 evt-COMP393253 2 0 0 0 evt-TRACE3021360 0 0 1 evt-COMP302025 2 0 0 2 evt-START3020200 0 0 0 cmd-CONNECT3020182 0 0 0 cmd-CONNECT3020170 0 0 0 evt-COMP302016 0 0 0 2 msg-EXCH:Tx30198655356553511 evt-UPCONN301972 0 0 0 evt-UPCONN301960 0 0 0 evt-AVAILSVC301952 0 0 0 evt-AVAILSVC301940 0 0 0 msg-EXCH:Rx30193655356553514290800 evt-TRACE30192 0 0 0 5 evt-TRACE30191 0 0 0 3 evt-COMP27340 0 0 0 0
2-106
fwalarmsfiltershow
Available in Fabric OS versions: v4.1, v4.2 (All Fabric OS versions have this command as a CLI but not all have it as part of supportshow) Note: This command requires a Fabric Watch License. If enabled using fwalarmsfilterset 1 then FW alarms will be mirrored to the serial console and possibly to telnet if quietmode is disabled at telnet. Quietmode is always disabled at v4.x serial console, it is enabled by default at telnet unless it is deliberately toggled (this feature only available in version 4.2).
Additional Example/Case Studies: Troubleshooting Use: Use this command to display alarm filtering status for Fabric Watch. Example 2-25: Example To display the status of alarm filtering in Fabric Watch:
switch:admin> fwalarmsfiltershow fw: alarms are enabled switch:admin> fwalarmsfiltershow FW: Alarms are disabled
Example 2-26: Example:

fwalarmsfiltershow: FW: Alarms are disabled
Note:
If fwalarmsfilter is not enabled, FW error messages will not be recorded at the system console.

fwalarmsfiltershow: FW: Alarms are disabled
Note:
If FW is enabled and licensed and you are experiencing difficulties getting FW messages, verify that the FW daemons are running on both logical Linux switches in a 12k chassis (fwd = fabric watch daemon | -s 0 = switch 0 | -s1 = switch 1)
847 875 1 1 0 0 78 78 19 19 993 rt_sig Feb12 ? 993 rt_sig Feb12 ? 00:00:00 00:00:00 fwd -s 0 fwd -s 1
000 S root 000 S root
2-107
fwsamshow
Available in Fabric OS versions: v4.1, v4.2 Note: This command requires a Fabric Watch License.
Version Differences: Additional Example/Case Studies: Troubleshooting Use: Use this command to display the switch availability monitor (SAM) information. Use this command to displays information about port availability. The information displayed includes: total uptime, total down time, number of faulty occurrences, and total percent of off time for each port. Example 2-27:
fwsamshow: Total Port# Number Of Total Type UpTime DownTime Occurences OffTime (Percent) (Percent) (Times) (Percent) ============================================================================= 16 U_PORT 0 0 0 100 17 U_PORT 0 0 0 100 18 U_PORT 0 0 0 100 19 Loopback 100 0 0 0 20 U_PORT 0 0 0 100 21 U_PORT 0 0 0 100 22 U_PORT 0 0 0 100 23 U_PORT 0 0 0 100 24 U_PORT 0 0 0 100 25 U_PORT 0 0 0 100 26 U_PORT 0 0 0 100 27 U_PORT 0 0 0 100 28 U_PORT 0 0 0 100 29 U_PORT 0 0 0 100 30 U_PORT 0 0 0 100 31 U_PORT 0 0 0 100 32 F_PORT 100 0 0 0 33 F_PORT 100 0 0 0 34 F_PORT 100 0 0 0 35 U_PORT 0 0 0 100 36 U_PORT 0 0 0 100 37 U_PORT 0 0 0 100 38 U_PORT 0 0 0 100 39 U_PORT 0 0 0 100 40 E_PORT 100 0 0 0 41 E_PORT 100 0 0 0 42 E_PORT 100 0 0 0 43 E_PORT 100 0 0 0 44 U_PORT 0 0 0 100 45 U_PORT 0 0 0 100 46 U_PORT 0 0 0 100 47 U_PORT 0 0 0 100 Total
Note:
Number of Occurrences means: number of faulty occurrences Number of occurrences means the number of times any of the following condition has occurred to an ONLINE port. 1. not receiving idle frame from other side after speed negotiation. 2. if there is loss of light due to pulling of cable. Fabric Watch configuration does not effect faulty occurrence.
2-108

fwsamshow: Total Total Number Of Total UpTime DownTime Occurences OffTime (Percent) (Percent) (Times) (Percent) ============================================================================= 0 U_PORT 0 0 0 100 1 F_PORT 100 0 0 0 2 U_PORT 0 0 0 100 3 U_PORT 0 0 0 100 4 U_PORT 0 0 0 100 5 U_PORT 0 0 0 100 6 U_PORT 0 0 0 100 7 U_PORT 0 0 0 100 8 U_PORT 0 0 0 100 9 U_PORT 0 0 0 100 10 U_PORT 0 0 0 100 11 U_PORT 0 0 0 100 12 U_PORT 0 0 0 100 13 U_PORT 0 0 0 100 14 U_PORT 0 0 0 100 15 U_PORT 0 0 0 100 16 U_PORT 0 0 0 100 17 U_PORT 0 0 0 100 18 U_PORT 0 0 0 100 19 U_PORT 0 0 0 100 20 U_PORT 0 0 0 100 21 U_PORT 0 0 0 100 22 U_PORT 0 0 0 100 23 U_PORT 0 0 0 100 24 U_PORT 0 0 0 100 25 U_PORT 0 0 0 100 26 U_PORT 0 0 0 100 27 U_PORT 0 0 0 100 28 U_PORT 0 0 0 100 29 U_PORT 0 0 0 100 30 U_PORT 0 0 0 100 31 U_PORT 0 0 0 100 48 U_PORT 0 0 0 100 49 U_PORT 0 0 0 100 50 U_PORT 0 0 0 100 51 U_PORT 0 0 0 100 52 U_PORT 0 0 0 100 53 U_PORT 0 0 0 100 54 U_PORT 0 0 0 100 55 U_PORT 0 0 0 100 56 U_PORT 0 0 0 100 57 U_PORT 0 0 0 100 58 U_PORT 0 0 0 100 59 U_PORT 0 0 0 100 60 U_PORT 0 0 0 100 61 U_PORT 0 0 0 100 62 U_PORT 0 0 0 100 63 U_PORT 0 0 0 100 <output truncated> Port# Type
2-109
hadump
Available in Fabric OS versions: v4.1, v4.2 Additional Example/Case Studies: Troubleshooting Use: Use this command to display information about the status of the High Availability features in the switch particularly during failover or firmwaredownload processes This command displays the following information:

Note:
Local CP state (slot number and CP id); Remote CP state (slot number and CP id); High Availability Enabled/Disabled Heartbeat Up/Down Health of Standby CP. The Health of the Standby CP can show one of the following values: Healthy The Standby CP is running and the background health diagnostic has not detected any errors. Failed The Standby CP is running, but the background health diagnostic has discovered a problem with the blade. The logs should be checked to determine the appropriate repair action. Fail-over will be disabled until the Standby CP can be repaired. HA Synchronization Status. The HA Synchronization Status field can show one of the following values: HA State Synchronized The system is currently fully synchronized. If a fail-over were necessary at this time, the fail-over would be non-disruptive. HA State Not In Sync The system is unable to synchronize the two CPs, due to the Standby CP being faulty or another system error. If a fail-over were to take place at this time, the Standby CP would be rebooted, and the fail-over will be disruptive. IP and Fibre Channel addresses configured for the switch. Additional internal HA state information, subject to change. Observing this output before and after hafail overs, firmware downloads gives you a picture of the FSS synchronization process. See embedded notes after / symbol and notes in example below. The output of this command displays these outputs, in the order listed. haShow ipaddrshow sysc_dprintf medbg -s1 -e1 fssadmin -s chassis0 q fssadmin -s fcsw0 q fssadmin -s fcsw1 q / / / / / / / / System System System System System System System System Command Command Command Command Command Command Command Command Group Group Group Group Group Group Group Group
hadump
Example 2-28:
ipaddrshow 4: SWITCH0 Ethernet IP Address: 10.255.255.149 Ethernet Subnetmask: 255.255.252.0 Fibre Channel IP Address: 0.0.0.0 Fibre Channel Subnetmask: 0.0.0.0 SWITCH1 Ethernet IP Address: 10.255.255.150 Ethernet Subnetmask: 255.255.252.0 Fibre Channel IP Address: 0.0.0.0 Fibre Channel Subnetmask: 0.0.0.0
2-110

CP0 Ethernet IP Address: 10.255.255.151 Ethernet Subnetmask: 255.255.252.0 HostName : cp0 Gateway Address: 10.255.255.1 CP1 Ethernet IP Address: 10.255.255.152 Ethernet Subnetmask: 255.255.252.0 HostName : cp1 Gateway Address: 10.255.255.1 Backplane IP address of CP0 : 10.0.0.5 Backplane IP address of CP1 : 10.0.0.6
Note:
sysc_dprintf issued from both active and standby CPs after a hafailover the first output is taken from the just turned active CP, notes are embedded after / symbols:
sysc_dprintf: FSSME registered: TRUE FSSME ready: TRUE Event HA state: HA_ACCEPT_YIELD_CTRL /current active yields Event head: 19, Event tail: 19 EVT_FSSME_REG:COMPLETED EVT_FSSME_READY:COMPLETED EVT_LOAD_REPLY:COMPLETED EVT_SVC_STANDBY:COMPLETED EVT_LOAD_REPLY:COMPLETED EVT_LOAD_REPLY:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_SVC_STANDBY:COMPLETED EVT_SVC_STANDBY:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_TAKE_CONTROL:COMPLETED /tkover stndby doesn't have this line EVT_SVC_ACTIVE:COMPLETED /tkover stndby doesn't have this line EVT_BLADE_LIST:COMPLETED EVT_SVC_ACTIVE:COMPLETED /tkover stndby doesn't have this line EVT_SVC_ACTIVE:COMPLETED /tkover stndby doesn't have this line cmd_tail = 4, cmd_head = 4 /tkover has number 2 CMD_START_DEFAULT:COMPLETED CMD_BLADELIST_START:COMPLETED CMD_TAKE_CONTROL:COMPLETED /tkover stndby doesn't have this line CMD_BLADELIST_START:COMPLETED Service name: fcsw Service instance 0, state SI_ST_ACTIVE, refcnt 5 /other says stndby Service name: fcsw Service instance 1, state SI_ST_ACTIVE, refcnt 5 /other says stndby Service name: chassis Service instance 0, state SI_ST_ACTIVE, refcnt 7 /other says stndby Slot 2:Bladeid 0x02,SYSC_BLADE_ACTION_DONE Slot 3:Bladeid 0x02,SYSC_BLADE_ACTION_DONE Slot 5:Bladeid 0x01,SYSC_BLADE_ACTION_DONE Slot 6:Bladeid 0x01,SYSC_BLADE_ACTION_DONE Slot 7:Bladeid 0x02,SYSC_BLADE_ACTION_DONE Slot 8:Bladeid 0x02,SYSC_BLADE_ACTION_DONE
2-111
Fabric OS SupportShow Information Example 2-29: The 2nd output is taken from the just turned standby CP, notes are embedded after /:
sysc_dprintf: FSSME registered: TRUE FSSME ready: TRUE Event HA state: HA_ACCEPT_TAKE_CTRL /new active takes control Event head: 14, Event tail: 14 EVT_FSSME_REG:COMPLETED EVT_FSSME_READY:COMPLETED EVT_LOAD_REPLY:COMPLETED EVT_SVC_STANDBY:COMPLETED EVT_LOAD_REPLY:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_LOAD_REPLY:COMPLETED EVT_SVC_STANDBY:COMPLETED EVT_SVC_STANDBY:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_BLADE_LIST:COMPLETED cmd_tail = 2, cmd_head = 2 /active taken from has # 4 CMD_START_DEFAULT:COMPLETED CMD_BLADELIST_START:COMPLETED Service name: fcsw Service instance 0, state SI_ST_STANDBY, refcnt 5 /other says active Service name: fcsw Service instance 1, state SI_ST_STANDBY, refcnt 5 /other says active Service name: chassis Service instance 0, state SI_ST_STANDBY, refcnt 7 /other says active Slot 2:Bladeid 0x02,SYSC_BLADE_ACTION_DONE Slot 3:Bladeid 0x02,SYSC_BLADE_ACTION_DONE Slot 5:Bladeid 0x01,SYSC_BLADE_ACTION_DONE Slot 6:Bladeid 0x01,SYSC_BLADE_ACTION_DONE Slot 7:Bladeid 0x02,SYSC_BLADE_ACTION_DONE Slot 8:Bladeid 0x02,SYSC_BLADE_ACTION_DONE
Note:
medbg -s1 -e1 issued from both active and standby CPs after a hafailover the first output is taken from the just turned active CP, notes are embedded after /:
medbg -s1 -e1: Group Name = RightSwitch MF Name = RightSwitchCP0 /other is CP1 Sync Order: chassis:0 fcsw:1 chassis:0 CurSt = FSS_SYNC_SUCCESS PrevSt = FSS_SYNC_STARTED LaunchSt = SVC_ACTIVE Sync Time = Wed May 7 16:02:23 2003 Unsync Time = FabSt = STABLE fcsw:1 CurSt = FSS_SYNC_SUCCESS PrevSt = FSS_SYNC_STARTED LaunchSt = SVC_ACTIVE Sync Time = Wed May 7 16:02:24 2003 Unsync Time = FabSt = STABLE /other 2ndary says unstable Group Name = LeftSwitch MF Name = LeftSwitchCP0 Sync Order: chassis:0 fcsw:0 chassis:0 CurSt = FSS_SYNC_SUCCESS PrevSt = FSS_SYNC_STARTED LaunchSt = SVC_REGISTERRED Sync Time = Wed May 7 16:02:23 2003 Unsync Time = FabSt = STABLE fcsw:0 CurSt = FSS_SYNC_SUCCESS PrevSt = FSS_SYNC_STARTED LaunchSt = SVC_ACTIVE Sync Time = Wed May 7 16:02:24 2003 Unsync Time = FabSt = STABLE Group Name = RightSwitch MF Name = RightSwitchCP0 Sync Order: chassis:0 fcsw:1
2-112
chassis:0 FSS_EVENTNEXT_STATEFSS CMD SENTSYSCTL MSG L:FSS_EVT_SYNC_SUCCESSFSS_SYNC_SUCCESS NONE NONE L:FSS_EVT_SYNC_STARTFSS_SYNC_STARTED NONE NONE L:FSS_EVT_DUMP_READYFSS_SYNC_STARTED SYNC_STARTNONE L:FSS_EVT_ACTIVE_RDYFSS_ACTIVE_READY NONE SVC_ACTIVE L:SCTL_EVT_TAKE_CTRLSCTL_ACTIVE TAKE_CTRL NONE R:FSS_EVT_IMAGE_INCOMPFSS_STANDBY_READY NONE NONE L:FSS_EVT_SYNC_SUCCESSFSS_SYNC_SUCCESS NONE NONE L:FSS_EVT_SYNC_STARTFSS_SYNC_STARTED NONE NONE L:FSS_EVT_IMAGE_COMPFSS_IMAGE_COMP NONE SVC_STANDBY L:SCTL_EVT_SLAUNCHSCTL_SLAUNCH NONE NONE L:ME_EVT_FSS_INITFSS_INIT NONE NONE fcsw:1 FSS_EVENTNEXT_STATEFSS CMD SENTSYSCTL MSG L:FSS_EVT_SYNC_SUCCESSFSS_SYNC_SUCCESS NONE NONE L:FSS_EVT_SYNC_STARTFSS_SYNC_STARTED NONE NONE L:ME_EVT_SYNC_NEXT_SVCFSS_SYNC_STARTED SYNC_STARTNONE L:FSS_EVT_DUMP_READYFSS_DUMP_READY NONE NONE L:FSS_EVT_ACTIVE_RDYFSS_ACTIVE_READY NONE SVC_ACTIVE L:SCTL_EVT_TAKE_CTRLSCTL_ACTIVE TAKE_CTRL NONE R:FSS_EVT_IMAGE_INCOMPFSS_STANDBY_READY NONE NONE L:FSS_EVT_SYNC_SUCCESSFSS_SYNC_SUCCESS NONE NONE L:FSS_EVT_SYNC_STARTFSS_SYNC_STARTED NONE NONE L:FSS_EVT_IMAGE_COMPFSS_IMAGE_COMP NONE SVC_STANDBY L:SCTL_EVT_SLAUNCHSCTL_SLAUNCH NONE NONE L:ME_EVT_FSS_INITFSS_INIT NONE NONE Group Name = LeftSwitch MF Name = LeftSwitchCP0 Sync Order: chassis:0 fcsw:0 chassis:0 FSS_EVENTNEXT_STATEFSS CMD SENTSYSCTL MSG L:ME_EVT_FSS_INITFSS_INIT NONE NONE fcsw:0 FSS_EVENTNEXT_STATEFSS CMD SENTSYSCTL MSG L:FSS_EVT_SYNC_SUCCESSFSS_SYNC_SUCCESS NONE NONE L:FSS_EVT_SYNC_STARTFSS_SYNC_STARTED NONE NONE L:ME_EVT_SYNC_NEXT_SVCFSS_SYNC_STARTED SYNC_STARTNONE L:FSS_EVT_DUMP_READYFSS_DUMP_READY NONE NONE L:FSS_EVT_ACTIVE_RDYFSS_ACTIVE_READY NONE SVC_ACTIVE L:SCTL_EVT_TAKE_CTRLSCTL_ACTIVE TAKE_CTRL NONE R:FSS_EVT_IMAGE_INCOMPFSS_STANDBY_READY NONE NONE L:FSS_EVT_SYNC_SUCCESSFSS_SYNC_SUCCESS NONE NONE L:FSS_EVT_SYNC_STARTFSS_SYNC_STARTED NONE NONE L:FSS_EVT_IMAGE_COMPFSS_IMAGE_COMP NONE SVC_STANDBY L:SCTL_EVT_SLAUNCHSCTL_SLAUNCH NONE NONE L:ME_EVT_FSS_INITFSS_INIT NONE NONE
fssadmin -s chassis0 -q:

on chassis 0.
/fssadmin s chassis0 q means give me fss ouput per single instance
=== FSS Service Dump : chassis0 === == State == chassis0(0): ACTIVE(0), Required local = SYN_SUCC, prev = SYN_SUCC, peer = SYN_SUCC Name LocalRemote chassis0(M)SYN_SUCCSYN_SUCC em(M)SYN_SUCCSYN_SUCC pdm(M)SYN_SUCCSYN_SUCC rpc(M)SYN_SUCCSYN_SUCC == Statistic == tx-pkt tx(KB) rx-pkt rx(KB) UP (tor=496, tod=3689) em 3 21 2 0 321 W=2,1,-,-,406,1,
2-113

3 3 0 190 W=2,3,-,-,-,-, 0 0 W=1,1,-,-,-,-,
pdm 105 282 rpc 2 0 == Config == chassis0(1.1) comp chassis01:1U comp em1:1U
comp
comp
pdm1:1U /pdm stands for Protocol data module

rpc1:1U
Warm Table: / Warm table is used for non-disruptive recovery, while cold table is used for disruptive recovery or startup. emEM_WARM_CHECK_POWER_STATES,,,EM_WARM_CHECK_FRU_OBJS,FSS_RECOV_ACTIVE pdmFSS_RECOV_ACTIVE,,,, rpcFSS_RECOV_ACTIVE,,,, Cold Table: emEM_COLD_CHECK_FRU_OBJS,FSS_RECOV_ACTIVE pdmFSS_RECOV_ACTIVE, rpcFSS_RECOV_ACTIVE, == SVC == major: 1minor: 1 lo: 0minor: 1 id: 0peerid: 0 epoch: 2log: 0 conn: 3bits: 1 recov: 0index: 6 upper: 6coldnum: 3 warmnum: 6stbynum: 4 stat: 4prevstat: 4 peerstat: 4sv_winsz: 64 nscm: 4 fssadmin -s fcsw0 -q: === FSS Service Dump : fcsw0 === == State == fcsw0(4): ACTIVE(0), Required local = SYN_SUCC, prev = SYN_SUCC, peer = SYN_SUCC Name LocalRemote fcsw0(M)SYN_SUCCSYN_SUCC swc(M)SYN_SUCCSYN_SUCC fcp(M)SYN_SUCCSYN_SUCC rt(M)SYN_SUCCSYN_SUCC fc(M)SYN_SUCCSYN_SUCC fabric(M)SYN_SUCCSYN_SUCC zone(M)SYN_SUCCSYN_SUCC fspf(M)SYN_SUCCSYN_SUCC ns(M)SYN_SUCCSYN_SUCC ms(M)SYN_SUCCSYN_SUCC ps(M)SYN_SUCCSYN_SUCC rcs(M)SYN_SUCCSYN_SUCC evm(M)SYN_SUCCSYN_SUCC track(M)SYN_SUCCSYN_SUCC ts(M)SYN_SUCCSYN_SUCC slap(M)SYN_SUCCSYN_SUCC security(M)SYN_SUCCSYN_SUCC web(M)SYN_SUCCSYN_SUCC snmp(M)SYN_SUCCSYN_SUCC fw(M)SYN_SUCCSYN_SUCC fdmi(M)SYN_SUCCSYN_SUCC diagfss(M)SYN_SUCCSYN_SUCC == Statistic == tx-pkt tx(KB) rx-pkt rx(KB) UP (tor=1632, tod=117) swc 6 104 2 01139 W=1,24,11,-,2,-,127,-,-,-,-,-,-,-,-, fcp 4 0 2 0 979 W=2,-,-,10,-,-,128,1,-,-,-,-,-,-,-, rt 2 0 3 01145 W=1,-,-,-,-,-,127,-,-,-,-,-,-,-,-,
2-114

fc 3 fabric 4 zone 5 fspf 20 ns 8 ms 6 ps 3 rcs 4 evm 3 track 2 ts 34 slap 2 security 6 web 2 snmp 2 fw 2 fdmi 2 diagfss 2 == Config == fcsw0(2.1) comp fcsw02:1U comp swc1:1U comp fcp1:1U comp rt1:1U comp fc1:1U comp fabric1:1U comp zone1:1U comp fspf1:1U comp ns1:1U comp ms1:1U comp ps1:1U comp rcs1:1U comp evm1:1U comp track1:1U comp ts1:1U comp slap1:1U comp security1:1U comp web1:1U comp snmp1:1U comp fw1:1U comp fdmi1:1U comp diagfss1:1U 0 6 0 1 3 49 0 2 13 0 5 0 0 0 0 0 0 0 3 2 4 2 3 2 3 3 3 3 2 3 3 3 3 3 3 3 01145 0 341 02439 0 590 01054 01470 0 943 0 811 0 649 0 637 02222 0 911 02593 01265 0 113 01577 0 749 01149 W=1,-,-,1,2,-,-,-,-,-,-,-,-,-,-, W=1,-,-,-,1,-,-,1,9,-,-,-,-,-,-, W=2,-,-,22,-,-,-,2,-,6,3,-,-,-,-, W=2,-,-,14,-,-,149,-,-,-,-,-,-,-,-, W=2,-,-,-,-,-,149,2,3,9,-,-,-,-,-, W=2,-,-,-,-,-,-,-,-,53,2,-,-,-,-, W=2,-,-,-,-,-,151,-,-,-,2,-,-,-,-, W=2,-,-,9,-,-,-,-,3,6,-,-,-,-,-, W=2,-,-,-,-,-,-,-,-,-,-,4,-,-,-, W=2,-,-,-,-,-,-,-,-,6,-,-,-,-,-, W=2,-,-,-,-,-,149,-,-,-,-,-,-,-,-, W=2,-,-,-,-,-,128,-,-,-,-,-,-,-,-, W=1,24,-,-,-,-,-,-,-,1367,-,-,-,-,-, W=1,-,-,-,-,-,-,-,-,-,2,-,-,-,-, W=1,-,-,-,-,-,-,-,-,294,-,-,-,-,-, W=34,-,-,-,-,-,157,2,-,-,-,10,-,-,-, W=1,-,-,-,-,-,-,-,-,-,-,-,1,1,-, W=1,24,-,-,-,-,-,4,1,-,-,-,-,-,-,
Warm Table: swc SWC_RECOV_ONLINE_PORTS,SWC_RECOV_ONLINE_DONE,,FSS_RECOV_ACTIVE,,SWC_RECOV_RESET_PORTS,,,,,,,, fcp,,FCP_WARM_INIT,,,FCP_DATA_RECOV,FSS_RECOV_ACTIVE,,,,,,, rt,,,,,FSS_RECOV_ACTIVE,,,,,,,, fc,,FC_FSS_WARM_1,FSS_RECOV_ACTIVE,,,,,,,,,, fabric,,,fab_recov_warm,,,fab_recov_eport,FSS_RECOV_ACTIVE,,,,,, zone,,ZN_IPC_REG,,,,ZN_APPLY_PUSH,,FSS_RECOV_ACTIVE,ZN_EPORT_VALID,,,, fspf,,FSPF_WARM_1,,,FSS_RECOV_ACTIVE,,,,,,,, ns,,,,,NS_RDCFG,NS_SYNC,NSCAM_VER,FSS_RECOV_ACTIVE,,,,, ms,,,,,,,,MS_WARMINIT,FSS_RECOV_ACTIVE,,,, ps,,,,,FSS_PS_VERIFY,,,,FSS_RECOV_ACTIVE,,,, rcs,,RCS_IPC_REG,,,,,RCS_XACT_COMPLETE,FSS_RECOV_ACTIVE,,,,, evm,,,,,,,,,,FSS_RECOV_ACTIVE,,, track,,,,,,,,FSS_RECOV_ACTIVE,,,,, ts,,,,,FSS_RECOV_ACTIVE,,,,,,,, slap,,,,,FSS_RECOV_ACTIVE,,,,,,,, securitySEC_FSS_RDDB,,,,,,,,FSS_RECOV_ACTIVE,,,,, web,,,,,,,,,FSS_RECOV_ACTIVE,,,, snmp,,,,,,,,FSS_RECOV_ACTIVE,,,,, fw,,,,,fwd_init,fwd_warm,,,,FSS_RECOV_ACTIVE,,, fdmi,,,,,,,,,,,FSS_FDMI_SYNC_KERN,FSS_RECOV_ACTIVE,
2-115
diagfssDIAGFSS_SW_RECOV_PRESWC,,,,,,DIAGFSS_SW_RECOV_POSTSWC,FSS_RECOV_ACTIVE,,,,,, Cold Table: swcSWC_RECOV_COLD,,,FSS_RECOV_ACTIVE,,,,, fcpFCP_COLD_INIT,,,,FSS_RECOV_ACTIVE,,,, rt,,FSS_RECOV_ACTIVE,,,,,, fcFC_FSS_COLD_1,FSS_RECOV_ACTIVE,,,,,,, fabricfab_recov_cold,,,,FSS_RECOV_ACTIVE,,,, zone,ZN_CONF_INIT,ZN_DB_RES,,FSS_RECOV_ACTIVE,,,, fspfFSPF_COLD_1,,,,FSS_RECOV_ACTIVE,,,, nsNS_INIT_REG,,,,FSS_RECOV_ACTIVE,,,, ms,,,,,MS_COLDINIT,FSS_RECOV_ACTIVE,, ps,,,,,FSS_PS_CONF_INIT,FSS_RECOV_ACTIVE,, rcsRCS_CONF_INIT,,,,FSS_RECOV_ACTIVE,,,, evm,,,,,,,FSS_RECOV_ACTIVE, track,,,,,FSS_RECOV_ACTIVE,,, ts,TS_FSS_RCS_REG,,,,FSS_RECOV_ACTIVE,,, slap,,,,FSS_RECOV_ACTIVE,,,, security,SEC_FSS_RCS_REG,,,,,FSS_RECOV_ACTIVE,, web,,,,,,FSS_RECOV_ACTIVE,, snmp,,,,,FSS_RECOV_ACTIVE,,, fwfwd_init,fwd_cold,,,,,,FSS_RECOV_ACTIVE, fdmi,,,,,,,,FSS_RECOV_ACTIVE diagfssFSS_RECOV_ACTIVE,,,,,,,, == SVC == major: 2minor: 1 lo: 0minor: 1 id: 4peerid: 4 epoch: 2log: 0 conn: 3bits: 1 recov: 0index: 15 upper: 15coldnum: 10 warmnum: 15stbynum: 4 stat: 4prevstat: 4 peerstat: 4sv_winsz: 64 nscm: 22 fssadmin -s fcsw1 -q: === FSS Service Dump : fcsw1 === == State == fcsw1(2): ACTIVE(0), Required local = SYN_SUCC, prev = SYN_SUCC, peer = SYN_SUCC Name LocalRemote fcsw1(M)SYN_SUCCSYN_SUCC swc(M)SYN_SUCCSYN_SUCC fcp(M)SYN_SUCCSYN_SUCC rt(M)SYN_SUCCSYN_SUCC fc(M)SYN_SUCCSYN_SUCC fabric(M)SYN_SUCCSYN_SUCC zone(M)SYN_SUCCSYN_SUCC fspf(M)SYN_SUCCSYN_SUCC ns(M)SYN_SUCCSYN_SUCC ms(M)SYN_SUCCSYN_SUCC ps(M)SYN_SUCCSYN_SUCC rcs(M)SYN_SUCCSYN_SUCC evm(M)SYN_SUCCSYN_SUCC track(M)SYN_SUCCSYN_SUCC ts(M)SYN_SUCCSYN_SUCC slap(M)SYN_SUCCSYN_SUCC security(M)SYN_SUCCSYN_SUCC web(M)SYN_SUCCSYN_SUCC snmp(M)SYN_SUCCSYN_SUCC fw(M)SYN_SUCCSYN_SUCC fdmi(M)SYN_SUCCSYN_SUCC diagfss(M)SYN_SUCCSYN_SUCC == Statistic ==
2-116

tx-pkt tx(KB) rx-pkt rx(KB) UP (tor=927, tod=121) swc 6 103 2 01289 W=1,12,11,-,1,-,64,-,-,-,-,-,-,-,-, fcp 3 0 3 0 742 W=2,-,-,9,-,-,149,1,-,-,-,-,-,-,-, rt 2 0 3 01297 W=1,-,-,-,-,-,64,-,-,-,-,-,-,-,-, fc 3 0 3 01297 W=1,-,-,1,1,-,-,-,-,-,-,-,-,-,-, fabric 4 6 2 0 898 W=1,-,-,-,1,-,-,1,1,-,-,-,-,-,-, zone 5 0 4 02263 W=2,-,-,23,-,-,-,1,-,4,2,-,-,-,-, fspf 24 1 2 0 719 W=2,-,-,18,-,-,150,-,-,-,-,-,-,-,-, ns 8 2 3 0 881 W=2,-,-,-,-,-,150,1,3,4,-,-,-,-,-, ms 6 49 3 01126 W=2,-,-,-,-,-,-,-,-,79,2,-,-,-,-, ps 3 0 4 0 662 W=2,-,-,-,-,-,147,-,-,-,11,-,-,-,-, rcs 4 2 3 0 600 W=2,-,-,1,-,-,-,-,3,4,-,-,-,-,-, evm 3 13 3 0 434 W=2,-,-,-,-,-,-,-,-,-,-,2,-,-,-, track 2 0 3 0 534 W=2,-,-,-,-,-,-,-,-,4,-,-,-,-,-, ts 34 5 2 01571 W=2,-,-,-,-,-,148,-,-,-,-,-,-,-,-, slap 2 0 3 0 616 W=2,-,-,-,-,-,128,-,-,-,-,-,-,-,-, security 6 0 3 02083 W=2,47,-,-,-,-,-,-,-,664,-,-,-,-,-, web 2 0 3 0 815 W=2,-,-,-,-,-,-,-,-,-,1,-,-,-,-, snmp 2 0 3 0 50 W=1,-,-,-,-,-,-,-,-,296,-,-,-,-,-, fw 2 0 3 0 909 W=10,-,-,-,-,-,159,2,-,-,-,7,-,-,-, fdmi 2 0 3 0 453 W=1,-,-,-,-,-,-,-,-,-,-,-,1,1,-, diagfss 2 0 3 01302 W=1,12,-,-,-,-,-,2,1,-,-,-,-,-,-, == Config == fcsw1(2.1) comp fcsw12:1U comp swc1:1U comp fcp1:1U comp rt1:1U comp fc1:1U comp fabric1:1U comp zone1:1U comp fspf1:1U comp ns1:1U comp ms1:1U comp ps1:1U comp rcs1:1U comp evm1:1U comp track1:1U comp ts1:1U comp slap1:1U comp security1:1U comp web1:1U comp snmp1:1U comp fw1:1U comp fdmi1:1U comp diagfss1:1U Warm Table: swc SWC_RECOV_ONLINE_PORTS,SWC_RECOV_ONLINE_DONE,,FSS_RECOV_ACTIVE,,SWC_RECOV_RESET_PORTS,,,,,,,, fcp,,FCP_WARM_INIT,,,FCP_DATA_RECOV,FSS_RECOV_ACTIVE,,,,,,, rt,,,,,FSS_RECOV_ACTIVE,,,,,,,, fc,,FC_FSS_WARM_1,FSS_RECOV_ACTIVE,,,,,,,,,, fabric,,,fab_recov_warm,,,fab_recov_eport,FSS_RECOV_ACTIVE,,,,,, zone,,ZN_IPC_REG,,,,ZN_APPLY_PUSH,,FSS_RECOV_ACTIVE,ZN_EPORT_VALID,,,, fspf,,FSPF_WARM_1,,,FSS_RECOV_ACTIVE,,,,,,,, ns,,,,,NS_RDCFG,NS_SYNC,NSCAM_VER,FSS_RECOV_ACTIVE,,,,, ms,,,,,,,,MS_WARMINIT,FSS_RECOV_ACTIVE,,,, ps,,,,,FSS_PS_VERIFY,,,,FSS_RECOV_ACTIVE,,,, rcs,,RCS_IPC_REG,,,,,RCS_XACT_COMPLETE,FSS_RECOV_ACTIVE,,,,, evm,,,,,,,,,,FSS_RECOV_ACTIVE,,, track,,,,,,,,FSS_RECOV_ACTIVE,,,,, ts,,,,,FSS_RECOV_ACTIVE,,,,,,,, slap,,,,,FSS_RECOV_ACTIVE,,,,,,,, securitySEC_FSS_RDDB,,,,,,,,FSS_RECOV_ACTIVE,,,,,
2-117

web,,,,,,,,,FSS_RECOV_ACTIVE,,,, snmp,,,,,,,,FSS_RECOV_ACTIVE,,,,, fw,,,,,fwd_init,fwd_warm,,,,FSS_RECOV_ACTIVE,,, fdmi,,,,,,,,,,,FSS_FDMI_SYNC_KERN,FSS_RECOV_ACTIVE, diagfssDIAGFSS_SW_RECOV_PRESWC,,,,,,DIAGFSS_SW_RECOV_POSTSWC,FSS_RECOV_ACTIVE,,,,,,
Cold Table: swcSWC_RECOV_COLD,,,FSS_RECOV_ACTIVE,,,,, fcpFCP_COLD_INIT,,,,FSS_RECOV_ACTIVE,,,, rt,,FSS_RECOV_ACTIVE,,,,,, fcFC_FSS_COLD_1,FSS_RECOV_ACTIVE,,,,,,, fabricfab_recov_cold,,,,FSS_RECOV_ACTIVE,,,, zone,ZN_CONF_INIT,ZN_DB_RES,,FSS_RECOV_ACTIVE,,,, fspfFSPF_COLD_1,,,,FSS_RECOV_ACTIVE,,,, nsNS_INIT_REG,,,,FSS_RECOV_ACTIVE,,,, ms,,,,,MS_COLDINIT,FSS_RECOV_ACTIVE,, ps,,,,,FSS_PS_CONF_INIT,FSS_RECOV_ACTIVE,, rcsRCS_CONF_INIT,,,,FSS_RECOV_ACTIVE,,,, evm,,,,,,,FSS_RECOV_ACTIVE, track,,,,,FSS_RECOV_ACTIVE,,, ts,TS_FSS_RCS_REG,,,,FSS_RECOV_ACTIVE,,, slap,,,,FSS_RECOV_ACTIVE,,,, security,SEC_FSS_RCS_REG,,,,,FSS_RECOV_ACTIVE,, web,,,,,,FSS_RECOV_ACTIVE,, snmp,,,,,FSS_RECOV_ACTIVE,,, fwfwd_init,fwd_cold,,,,,,FSS_RECOV_ACTIVE, fdmi,,,,,,,,FSS_RECOV_ACTIVE diagfssFSS_RECOV_ACTIVE,,,,,,,, == SVC == major: 2minor: 1 lo: 0minor: 1 id: 2peerid: 2 epoch: 2log: 0 conn: 3bits: 1 recov: 0index: 15 upper: 15coldnum: 10 warmnum: 15stbynum: 4 stat: 4prevstat: 4 peerstat: 4sv_winsz: 64 nscm: 22
Note:
from both active and standby CPs after a hafailover this 2nd output is taken from the just turned standby CP, notes are embedded after / symbols:
medbg -s1 -e1 issued
medbg -s1 -e1: Group Name = RightSwitch MF Name = RightSwitchCP1 /other is CP0 Sync Order: chassis:0 fcsw:1 chassis:0 CurSt = FSS_SYNC_SUCCESS PrevSt = FSS_SYNC_STARTED LaunchSt = SVC_LAUNCHED Sync Time = Wed May 7 16:02:31 2003 Unsync Time = FabSt = STABLE /time diff from original is 8m fcsw:1 CurSt = FSS_SYNC_SUCCESS PrevSt = FSS_SYNC_STARTED LaunchSt = SVC_LAUNCHED Sync Time = Wed May 7 16:02:24 2003 Unsync Time = FabSt = UNSTABLE /active says stable Group Name = LeftSwitch MF Name = LeftSwitchCP1 Sync Order: chassis:0 fcsw:0 chassis:0 CurSt = FSS_SYNC_SUCCESS PrevSt = FSS_SYNC_STARTED LaunchSt = SVC_REGISTERRED Sync Time = Wed May 7 16:02:31 2003 Unsync Time = FabSt = STABLE fcsw:0 CurSt = FSS_SYNC_SUCCESS PrevSt = FSS_SYNC_STARTED
2-118

LaunchSt = SVC_LAUNCHED Sync Time = Wed May Unsync Time = FabSt = UNSTABLE 7 16:02:24 2003
Group Name = RightSwitch MF Name = RightSwitchCP1 Sync Order: chassis:0 fcsw:1 chassis:0 FSS_EVENTNEXT_STATEFSS CMD SENTSYSCTL MSG L:FSS_EVT_SYNC_SUCCESSFSS_SYNC_SUCCESS NONE NONE L:FSS_EVT_SYNC_STARTFSS_SYNC_STARTED NONE NONE L:FSS_EVT_IMAGE_COMPFSS_IMAGE_COMP NONE SVC_STANDBY L:SCTL_EVT_SLAUNCHSCTL_SLAUNCH NONE NONE L:ME_EVT_FSS_INITFSS_INIT NONE NONE fcsw:1 FSS_EVENTNEXT_STATEFSS CMD SENTSYSCTL MSG L:FSS_EVT_SYNC_SUCCESSFSS_SYNC_SUCCESS NONE NONE L:FSS_EVT_SYNC_STARTFSS_SYNC_STARTED NONE NONE L:FSS_EVT_IMAGE_COMPFSS_IMAGE_COMP NONE SVC_STANDBY L:SCTL_EVT_SLAUNCHSCTL_SLAUNCH NONE NONE L:ME_EVT_FSS_INITFSS_INIT NONE NONE Group Name = LeftSwitch MF Name = LeftSwitchCP1 Sync Order: chassis:0 fcsw:0 chassis:0 FSS_EVENTNEXT_STATEFSS CMD SENTSYSCTL MSG L:ME_EVT_FSS_INITFSS_INIT NONE NONE fcsw:0 FSS_EVENTNEXT_STATEFSS CMD SENTSYSCTL MSG L:FSS_EVT_SYNC_SUCCESSFSS_SYNC_SUCCESS NONE NONE L:FSS_EVT_SYNC_STARTFSS_SYNC_STARTED NONE NONE L:FSS_EVT_IMAGE_COMPFSS_IMAGE_COMP NONE SVC_STANDBY L:SCTL_EVT_SLAUNCHSCTL_SLAUNCH NONE NONE L:ME_EVT_FSS_INITFSS_INIT NONE NONE fssadmin -s chassis0 -q: === FSS Service Dump : chassis0 === == State == chassis0(0): STANDBY(0), Required local = SYN_SUCC, prev = SYN_SUCC, peer = SYN_SUCC Name LocalRemote chassis0(M)SYN_SUCCSYN_SUCC em(M)SYN_SUCCSYN_SUCC pdm(M)SYN_SUCCSYN_SUCC rpc(M)SYN_SUCCSYN_SUCC == Statistic == tx-pkt tx(KB) rx-pkt rx(KB) UP (tor=0, tod=3688) em 0 0 3 21 370 pdm 0 0 105 278 270 rpc 0 0 2 0 0 == Config == chassis0(1.1) comp chassis01:1U comp em1:1U comp pdm1:1U comp rpc1:1U Warm Table: emEM_WARM_CHECK_POWER_STATES,,,EM_WARM_CHECK_FRU_OBJS,FSS_RECOV_ACTIVE pdmFSS_RECOV_ACTIVE,,,, rpcFSS_RECOV_ACTIVE,,,, Cold Table: emEM_COLD_CHECK_FRU_OBJS,FSS_RECOV_ACTIVE pdmFSS_RECOV_ACTIVE,
2-119
rpcFSS_RECOV_ACTIVE, == SVC == major: 1minor: lo: 0minor: id: 0peerid: epoch: 2log: conn: 3bits: recov: 0index: upper: 0coldnum: warmnum: 6stbynum: stat: 4prevstat: peerstat: 4sv_winsz: nscm: 4
1 1 0 0 0 0 3 4 4 64
fssadmin -s fcsw0 -q: === FSS Service Dump : fcsw0 === == State == fcsw0(4): STANDBY(0), Required local = SYN_SUCC, prev = SYN_SUCC, peer = SYN_SUCC Name LocalRemote fcsw0(M)SYN_SUCCSYN_SUCC swc(M)SYN_SUCCSYN_SUCC fcp(M)SYN_SUCCSYN_SUCC rt(M)SYN_SUCCSYN_SUCC fc(M)SYN_SUCCSYN_SUCC fabric(M)SYN_SUCCSYN_SUCC zone(M)SYN_SUCCSYN_SUCC fspf(M)SYN_SUCCSYN_SUCC ns(M)SYN_SUCCSYN_SUCC ms(M)SYN_SUCCSYN_SUCC ps(M)SYN_SUCCSYN_SUCC rcs(M)SYN_SUCCSYN_SUCC evm(M)SYN_SUCCSYN_SUCC track(M)SYN_SUCCSYN_SUCC ts(M)SYN_SUCCSYN_SUCC slap(M)SYN_SUCCSYN_SUCC security(M)SYN_SUCCSYN_SUCC web(M)SYN_SUCCSYN_SUCC snmp(M)SYN_SUCCSYN_SUCC fw(M)SYN_SUCCSYN_SUCC fdmi(M)SYN_SUCCSYN_SUCC diagfss(M)SYN_SUCCSYN_SUCC == Statistic == tx-pkt tx(KB) rx-pkt rx(KB) UP (tor=0, tod=94) swc 0 0 6 1041296 fcp 0 0 4 0 880 rt 0 0 2 01302 fc 0 0 3 01302 fabric 0 0 4 6 447 zone 0 0 5 02463 fspf 0 0 21 0 503 ns 0 0 8 2 538 ms 0 0 6 491449 ps 0 0 3 0 642 rcs 0 0 4 2 598 evm 0 0 3 13 600 track 0 0 2 0 537 ts 0 0 36 32185 slap 0 0 2 0 826 security 0 0 6 02493 web 0 0 2 01128 snmp 0 0 2 0 233 fw 0 0 2 01405 fdmi 0 0 2 0 772
2-120

diagfss 0 == Config == fcsw0(2.1) comp fcsw02:1U comp swc1:1U comp fcp1:1U comp rt1:1U comp fc1:1U comp fabric1:1U comp zone1:1U comp fspf1:1U comp ns1:1U comp ms1:1U comp ps1:1U comp rcs1:1U comp evm1:1U comp track1:1U comp ts1:1U comp slap1:1U comp security1:1U comp web1:1U comp snmp1:1U comp fw1:1U comp fdmi1:1U comp diagfss1:1U 0 2 01307
Warm Table: swc SWC_RECOV_ONLINE_PORTS,SWC_RECOV_ONLINE_DONE,,FSS_RECOV_ACTIVE,,SWC_RECOV_RESET_PORTS,,,,,,,, fcp,,FCP_WARM_INIT,,,FCP_DATA_RECOV,FSS_RECOV_ACTIVE,,,,,,, rt,,,,,FSS_RECOV_ACTIVE,,,,,,,, fc,,FC_FSS_WARM_1,FSS_RECOV_ACTIVE,,,,,,,,,, fabric,,,fab_recov_warm,,,fab_recov_eport,FSS_RECOV_ACTIVE,,,,,, zone,,ZN_IPC_REG,,,,ZN_APPLY_PUSH,,FSS_RECOV_ACTIVE,ZN_EPORT_VALID,,,, fspf,,FSPF_WARM_1,,,FSS_RECOV_ACTIVE,,,,,,,, ns,,,,,NS_RDCFG,NS_SYNC,NSCAM_VER,FSS_RECOV_ACTIVE,,,,, ms,,,,,,,,MS_WARMINIT,FSS_RECOV_ACTIVE,,,, ps,,,,,FSS_PS_VERIFY,,,,FSS_RECOV_ACTIVE,,,, rcs,,RCS_IPC_REG,,,,,RCS_XACT_COMPLETE,FSS_RECOV_ACTIVE,,,,, evm,,,,,,,,,,FSS_RECOV_ACTIVE,,, track,,,,,,,,FSS_RECOV_ACTIVE,,,,, ts,,,,,FSS_RECOV_ACTIVE,,,,,,,, slap,,,,,FSS_RECOV_ACTIVE,,,,,,,, securitySEC_FSS_RDDB,,,,,,,,FSS_RECOV_ACTIVE,,,,, web,,,,,,,,,FSS_RECOV_ACTIVE,,,, snmp,,,,,,,,FSS_RECOV_ACTIVE,,,,, fw,,,,,fwd_init,fwd_warm,,,,FSS_RECOV_ACTIVE,,, fdmi,,,,,,,,,,,FSS_FDMI_SYNC_KERN,FSS_RECOV_ACTIVE, diagfssDIAGFSS_SW_RECOV_PRESWC,,,,,,DIAGFSS_SW_RECOV_POSTSWC,FSS_RECOV_ACTIVE,,,,,, Cold Table: swcSWC_RECOV_COLD,,,FSS_RECOV_ACTIVE,,,,, fcpFCP_COLD_INIT,,,,FSS_RECOV_ACTIVE,,,, rt,,FSS_RECOV_ACTIVE,,,,,, fcFC_FSS_COLD_1,FSS_RECOV_ACTIVE,,,,,,, fabricfab_recov_cold,,,,FSS_RECOV_ACTIVE,,,, zone,ZN_CONF_INIT,ZN_DB_RES,,FSS_RECOV_ACTIVE,,,, fspfFSPF_COLD_1,,,,FSS_RECOV_ACTIVE,,,, nsNS_INIT_REG,,,,FSS_RECOV_ACTIVE,,,, ms,,,,,MS_COLDINIT,FSS_RECOV_ACTIVE,, ps,,,,,FSS_PS_CONF_INIT,FSS_RECOV_ACTIVE,, rcsRCS_CONF_INIT,,,,FSS_RECOV_ACTIVE,,,, evm,,,,,,,FSS_RECOV_ACTIVE, track,,,,,FSS_RECOV_ACTIVE,,, ts,TS_FSS_RCS_REG,,,,FSS_RECOV_ACTIVE,,,
2-121
slap,,,,FSS_RECOV_ACTIVE,,,, security,SEC_FSS_RCS_REG,,,,,FSS_RECOV_ACTIVE,, web,,,,,,FSS_RECOV_ACTIVE,, snmp,,,,,FSS_RECOV_ACTIVE,,, fwfwd_init,fwd_cold,,,,,,FSS_RECOV_ACTIVE, fdmi,,,,,,,,FSS_RECOV_ACTIVE diagfssFSS_RECOV_ACTIVE,,,,,,,, == SVC == major: 2minor: 1 lo: 0minor: 1 id: 4peerid: 4 epoch: 2log: 0 conn: 3bits: 0 recov: 0index: 0 upper: 0coldnum: 10 warmnum: 15stbynum: 4 stat: 4prevstat: 4 peerstat: 4sv_winsz: 64 nscm: 22 fssadmin -s fcsw1 -q: === FSS Service Dump : fcsw1 === == State == fcsw1(2): STANDBY(0), Required local = SYN_SUCC, prev = SYN_SUCC, peer = SYN_SUCC Name LocalRemote fcsw1(M)SYN_SUCCSYN_SUCC swc(M)SYN_SUCCSYN_SUCC fcp(M)SYN_SUCCSYN_SUCC rt(M)SYN_SUCCSYN_SUCC fc(M)SYN_SUCCSYN_SUCC fabric(M)SYN_SUCCSYN_SUCC zone(M)SYN_SUCCSYN_SUCC fspf(M)SYN_SUCCSYN_SUCC ns(M)SYN_SUCCSYN_SUCC ms(M)SYN_SUCCSYN_SUCC ps(M)SYN_SUCCSYN_SUCC rcs(M)SYN_SUCCSYN_SUCC evm(M)SYN_SUCCSYN_SUCC track(M)SYN_SUCCSYN_SUCC ts(M)SYN_SUCCSYN_SUCC slap(M)SYN_SUCCSYN_SUCC security(M)SYN_SUCCSYN_SUCC web(M)SYN_SUCCSYN_SUCC snmp(M)SYN_SUCCSYN_SUCC fw(M)SYN_SUCCSYN_SUCC fdmi(M)SYN_SUCCSYN_SUCC diagfss(M)SYN_SUCCSYN_SUCC == Statistic == tx-pkt tx(KB) rx-pkt rx(KB) UP (tor=0, tod=121) swc 0 0 6 1031487 fcp 0 0 3 0 562 rt 0 0 2 01508 fc 0 0 3 01508 fabric 0 0 4 6 796 zone 0 0 5 02009 fspf 0 0 25 0 463 ns 0 0 8 1 689 ms 0 0 6 491065 ps 0 0 3 0 764 rcs 0 0 4 2 333 evm 0 0 3 13 408 track 0 0 2 0 412 ts 0 0 36 31416 slap 0 0 2 0 565
2-122

security 0 web 0 snmp 0 fw 0 fdmi 0 diagfss 0 == Config == fcsw1(2.1) comp fcsw12:1U comp swc1:1U comp fcp1:1U comp rt1:1U comp fc1:1U comp fabric1:1U comp zone1:1U comp fspf1:1U comp ns1:1U comp ms1:1U comp ps1:1U comp rcs1:1U comp evm1:1U comp track1:1U comp ts1:1U comp slap1:1U comp security1:1U comp web1:1U comp snmp1:1U comp fw1:1U comp fdmi1:1U comp diagfss1:1U 0 0 0 0 0 0 6 2 2 2 2 2 01811 0 743 0 63 0 867 0 480 01513
Warm Table: swc SWC_RECOV_ONLINE_PORTS,SWC_RECOV_ONLINE_DONE,,FSS_RECOV_ACTIVE,,SWC_RECOV_RESET_PORTS,,,,,,,, fcp,,FCP_WARM_INIT,,,FCP_DATA_RECOV,FSS_RECOV_ACTIVE,,,,,,, rt,,,,,FSS_RECOV_ACTIVE,,,,,,,, fc,,FC_FSS_WARM_1,FSS_RECOV_ACTIVE,,,,,,,,,, fabric,,,fab_recov_warm,,,fab_recov_eport,FSS_RECOV_ACTIVE,,,,,, zone,,ZN_IPC_REG,,,,ZN_APPLY_PUSH,,FSS_RECOV_ACTIVE,ZN_EPORT_VALID,,,, fspf,,FSPF_WARM_1,,,FSS_RECOV_ACTIVE,,,,,,,, ns,,,,,NS_RDCFG,NS_SYNC,NSCAM_VER,FSS_RECOV_ACTIVE,,,,, ms,,,,,,,,MS_WARMINIT,FSS_RECOV_ACTIVE,,,, ps,,,,,FSS_PS_VERIFY,,,,FSS_RECOV_ACTIVE,,,, rcs,,RCS_IPC_REG,,,,,RCS_XACT_COMPLETE,FSS_RECOV_ACTIVE,,,,, evm,,,,,,,,,,FSS_RECOV_ACTIVE,,, track,,,,,,,,FSS_RECOV_ACTIVE,,,,, ts,,,,,FSS_RECOV_ACTIVE,,,,,,,, slap,,,,,FSS_RECOV_ACTIVE,,,,,,,, securitySEC_FSS_RDDB,,,,,,,,FSS_RECOV_ACTIVE,,,,, web,,,,,,,,,FSS_RECOV_ACTIVE,,,, snmp,,,,,,,,FSS_RECOV_ACTIVE,,,,, fw,,,,,fwd_init,fwd_warm,,,,FSS_RECOV_ACTIVE,,, fdmi,,,,,,,,,,,FSS_FDMI_SYNC_KERN,FSS_RECOV_ACTIVE, diagfssDIAGFSS_SW_RECOV_PRESWC,,,,,,DIAGFSS_SW_RECOV_POSTSWC,FSS_RECOV_ACTIVE,,,,,, Cold Table: swcSWC_RECOV_COLD,,,FSS_RECOV_ACTIVE,,,,, fcpFCP_COLD_INIT,,,,FSS_RECOV_ACTIVE,,,, rt,,FSS_RECOV_ACTIVE,,,,,, fcFC_FSS_COLD_1,FSS_RECOV_ACTIVE,,,,,,, fabricfab_recov_cold,,,,FSS_RECOV_ACTIVE,,,, zone,ZN_CONF_INIT,ZN_DB_RES,,FSS_RECOV_ACTIVE,,,, fspfFSPF_COLD_1,,,,FSS_RECOV_ACTIVE,,,, nsNS_INIT_REG,,,,FSS_RECOV_ACTIVE,,,, ms,,,,,MS_COLDINIT,FSS_RECOV_ACTIVE,,
2-123
ps,,,,,FSS_PS_CONF_INIT,FSS_RECOV_ACTIVE,, rcsRCS_CONF_INIT,,,,FSS_RECOV_ACTIVE,,,, evm,,,,,,,FSS_RECOV_ACTIVE, track,,,,,FSS_RECOV_ACTIVE,,, ts,TS_FSS_RCS_REG,,,,FSS_RECOV_ACTIVE,,, slap,,,,FSS_RECOV_ACTIVE,,,, security,SEC_FSS_RCS_REG,,,,,FSS_RECOV_ACTIVE,, web,,,,,,FSS_RECOV_ACTIVE,, snmp,,,,,FSS_RECOV_ACTIVE,,, fwfwd_init,fwd_cold,,,,,,FSS_RECOV_ACTIVE, fdmi,,,,,,,,FSS_RECOV_ACTIVE diagfssFSS_RECOV_ACTIVE,,,,,,,, == SVC == major: 2minor: 1 lo: 0minor: 1 id: 2peerid: 2 epoch: 2log: 0 conn: 3bits: 0 recov: 0index: 0 upper: 0coldnum: 10 warmnum: 15stbynum: 4 stat: 4prevstat: 4 peerstat: 4sv_winsz: 64 nscm: 22
Summary of general medbg -s1 -e1 notes:
fssadmin s chassis0 q means gives fss ouput per single instance on chassis 0. pdm stands for Protocol data module Warm Table: / Warm table is used for non-disruptive recovery, while cold table is used for disruptive recovery or startup information.
2-124
haShow
Available in Fabric OS versions: v4.1, v4.2 Troubleshooting Use: Use this command to display control processor (CP) status. This command is part of hadump output. Use this command to display the control processor status, which includes:
Local CP state (slot number and CP id); Remote CP state (slot number and CP id); High Availability Enabled/Disabled Heartbeat Up/Down Fabric State Synchronization (v4.1 +)
Additional Example/Case Studies: v4.0 Example Output: Example 2-30: To display control processor (CP) status:
switch:admin> haShow Local CP (Slot 6, CP1): Active Remote CP (Slot 5, CP0): Standby HA Enabled, Heartbeat Up
Note:
HA Enabled, Heartbeat Up indicates a good HA status on a v4.0 switch. You would expect to also see HA State synchronized on a v4.1 plus switch.

hashow: Local CP (Slot 6, CP1): Active Remote CP (Slot 5, CP0): Standby, Healthy HA enabled, Heartbeat Up, HA State synchronized
Note:
An additional HA State synchronized parameter was added to hashow output in V4.1 because Fabric State Synchronization (FSS) was introduced to enable hot code activation.
2-125
historyShow
Available in Fabric OS versions: v4.x Troubleshooting Use: Use this command to display up to 100 lines of the history log. Compare history log to time awake value in chassisshow. If the FRU has been awake for a short period of time its insertion should be listed in both historyshow and errdump outputs UNLES the fru is resetting itself. Each history record contains three lines of information: 1. The first line of each record contains the following data sets:

2.
object type: CHASSIS, FAN, POWER SUPPLY, SW BLADE (switch), CP BLADE (control processor), WWN (world wide name), or UNKNOWN. object number: Slot <nn> (for blades), Unit <nn> (for everything else). event: Inserted, Removed, or Invalid. time of the event: at <Dow> <Mon> <dd> <hh:mm:ss> <yyyy>
The second contains one data set, Brocade Part Number:
3.
Brocade Part Number: <xx-yyyyyyy-zz> or Unknown
The third line contains one data set, Brocade Serial Number:
Brocade Serial Number: <xxxxxxxxxxxx> or Unknown

historyshow FAN Unit 3 Removed at Mon May 20 08:32:54 2002 Brocade Part Number: 60-0001536-03 Brocade Serial Number: FM3E0000255 FAN Unit 3 Inserted at Mon May 20 08:33:12 2002 Brocade Part Number: 60-0001536-03 Brocade Serial Number: FM3E0000255 FAN Unit 3 Removed at Mon May 20 08:33:29 2002 Brocade Part Number: 60-0001536-03 Brocade Serial Number: FM3E0000255
< truncated output > Note: This 100 line database is extremely useful. It allows you to correlate dates and times with error log messages. It will help you determine if Chassisshow time awake value correlates to a FRU insertion. Most important, it will help you determine if a failover or blade failure was manually induced. If it was not manually induced, check for dc converter issues (port blades), watchdog reason: reboot or panic dump messages.

historyshow: SW BLADE Slot 7 Inserted at Fri Apr 25 20:02:58 2003 Factory Part Number: 60-0001532-03 Factory Serial Number: 1013456800 UNKNOWN Slot 7 Removed at Fri Apr 25 20:03:09 2003 Factory Part Number: Not Available Factory Serial Number: Not Available
2-126

SW BLADE Slot 7 Inserted at Fri Apr 25 20:03:21 2003 Factory Part Number: 60-0001532-03 Factory Serial Number: 1013456800 SW BLADE Slot 8 Removed at Fri Apr 25 20:03:26 2003 Factory Part Number: 60-0001653-01 Factory Serial Number: FQ010003702 SW BLADE Slot 8 Inserted at Fri Apr 25 20:03:35 2003 Factory Part Number: 60-0001653-01 Factory Serial Number: FQ010003702 SW BLADE Slot 7 Removed at Sat Apr 26 21:00:07 2003 Factory Part Number: 60-0001532-03 Factory Serial Number: 1013456800 SW BLADE Slot 7 Inserted at Sat Apr 26 21:00:18 2003 Factory Part Number: 60-0001532-03 Factory Serial Number: 1013456800 POWER SUPPLY Unit 3 Removed at Tue Apr 29 19:29:38 2003 Factory Part Number: 23-0000006-02 Factory Serial Number: FL2L0002040 POWER SUPPLY Unit 3 Inserted at Tue Apr 29 19:29:58 2003 Factory Part Number: 23-0000006-02 Factory Serial Number: FL2L0002040 SW BLADE Slot 9 Inserted at Mon May 12 18:01:36 2003 Factory Part Number: 60-0001653-01 Factory Serial Number: FQ010002945 SW BLADE Slot 10 Inserted at Mon May 12 18:04:31 2003 Factory Part Number: 60-0001653-01 Factory Serial Number: FQ010010418
<output truncated>
2-127
hostShow
Available in Fabric OS versions: v3.1, v3.1.2 v4.2 Example Output: N/A. However v4.1 and above has a /sbin/route command that gives the same information Troubleshooting Use: Use this command to identify both the switch name and IP address. Example 2-59: V3.1.2 hostshow output
hostShow hostname -------sw3800_28 localhost e=10.64.147.28 inet address -----------10.64.147.28 127.0.0.1 0.0.0.0 aliases -------
2-128
i
Description: Use this command to display task summary. Available in Fabric OS versions: v3.1, v3.1.2 v4.2 Example Output: NA Troubleshooting UseUse this command to display information of all of the processes or of a specific process if a process ID is supplied. One line is displayed per process. The following table explains the fields displayed with this command. Examples Example 2-60: To display information about process ID 433:
switch:admin> i 433
F S UID PID PPID C PRI NI ADDR SZ WCHAN TTY TIME CMD 000 S 0 433 1 0 69 0 - 1283 5c64 ? 00:00:02 fabricd switch:admin>
Example 2-61: supportshow example

i NAME ---------tExcTask tLogTask tRestart tShell tRlogind tTelnetd tTelnetOutT tTelnetInTa tTimers tErrLog tNetTask tSwitch tResponse tPBmenu tReceive tTransmit tPortmapd tFabric tFspf tPTestD tRcs tSLAP tFDMIis tRtwr tRt tQL tFcph tRTZone tZone tFcp tNSd tTSd tASd tSecurity tPSrqm tPSd tNSCAM tFDMId tfdmic tMSd tMSRxd tMSLd ENTRY -----------_excTask _logTask _restartTask _shellTask _rlogind _telnetd _telnetOutTa _telnetInTas _timerTask _errLogTask _netTask _switchTask _responseTas _menuTask _portRxTask _portTxTask _portmapd _fabricTask _fspfTask _portTestD 104f3780 10800670 _fdmi_is 104fe850 _rtTask _qlTask _fcphTask _cfgRealTime _cfgTask _fcpTask _ns_svr 10699a80 _as_svr _secSvr _psrqmgr_svr _ps_svr _ns_cam _fdmi_svr _fdmi_cache _ms_svr _ms_rx_svr _ms_l_svr TID -------103fc5f0 103fa660 102daab0 102d5a70 10372400 10346dc0 102cd930 102c9c70 10335ff0 103375a0 10396a50 1033ba30 101c5d90 1032c200 1030f510 1030b850 1033f670 101d86d0 101c7340 11eb3b20 10288b30 101d9c80 11ef0720 1028a410 11fc8630 11fbefa0 102a6eb0 11f68250 11f69800 102a4080 11fa9e40 11f630e0 11f60f80 11eeb4c0 11ee86e0 11ee5db0 11f75520 11eeddf0 11ef7dd0 11f53230 11f24840 11f21f10 PRI --0 0 0 1 2 2 2 2 10 20 50 80 80 90 95 95 100 100 100 100 105 105 105 110 110 110 120 128 130 150 150 150 150 150 150 150 151 151 152 154 154 154 STATUS ---------PEND PEND PEND+T READY PEND PEND READY PEND READY PEND READY DELAY PEND+T PEND PEND PEND PEND PEND PEND READY PEND PEND PEND PEND PEND PEND PEND+T PEND PEND PEND+T PEND PEND PEND PEND PEND PEND PEND PEND PEND PEND PEND PEND PC -------108c54d0 108c54d0 108c54d0 1087fea0 10876cf8 10876cf8 10876b80 10876cf8 10895ba0 108c54d0 10876cf8 10870f6c 108c54d0 108c54d0 108c54d0 108c54d0 10876cf8 108c54d0 108c54d0 10870f6c 108c54d0 108c54d0 108c54d0 108c54d0 108c54d0 108c54d0 108c54d0 108c54d0 108c54d0 108c54d0 108c54d0 108c54d0 108c54d0 108c54d0 108c54d0 108c54d0 108c54d0 108c54d0 108c54d0 108c54d0 108c54d0 108c54d0 SP ERRNO DELAY -------- ------- ----103fc950 3d0001 0 103fa9c0 0 0 102dae40 3d0004 28 102d5cf0 c0008 0 103729c0 0 0 10347750 0 0 102cdf80 0 0 102ca390 0 0 10336530 0 0 10337940 0 0 10396db0 0 0 1033bd70 3d0002 23 101c6160 3d0004 9 1032c5d0 0 0 1030f8b0 3d0002 0 1030bbf0 3d0002 0 1033fad0 16 0 101d8ab0 3d0004 0 101c76e0 0 0 11eb3e20 0 0 10288fc0 0 0 101da010 0 0 11ef0ab0 0 0 1028a7a0 0 0 11fc89c0 0 0 11fbf330 0 0 102a7240 3d0004 13 11f68670 0 0 11f69c10 3d0002 0 102a4410 3d0004 8 11faa7d0 3d0002 0 11f63490 0 0 11f61310 0 0 11eeb850 0 0 11ee8a70 0 0 11ee6140 0 0 11f758b0 3d0002 0 11eee180 0 0 11ef8160 3d0002 0 11f535d0 3d0002 0 11f24be0 0 0 11f222a0 0 0
2-129

_ms_lrx_svr _rapid 108b34a0 _WC_START_We 10715ba0 10717250 _arrresp_svr _arrroute_sv _ms_apiTask _ms_arTask _thad 105c45a0 1051e270 _nssrl_svr 11f1f5e0 102a2ad0 101ca670 100381e0 10298da0 10293770 11f57580 11f55bf0 11f1ccb0 11f1a380 101c88f0 11ec8740 11eb7a20 11f6adb0 154 155 155 155 157 157 159 159 159 159 160 161 161 170 PEND PEND PEND PEND PEND+T PEND PEND PEND PEND PEND READY PEND PEND PEND 108c54d0 10876cf8 10876cf8 10876cf8 108c54d0 108c54d0 108c54d0 108c54d0 108c54d0 108c54d0 10870f6c 108c54d0 108c54d0 108c54d0 11f1f970 102a2f80 101cb3c0 100386b0 102993c0 10293b00 11f57920 11f55f90 11f1d1c0 11f1a710 101c8bf0 11ec8ad0 11eb7db0 11f6b140 0 d0003 0 0 3d0004 0 0 0 0 0 0 0 0 0 0 0 0 0 470 0 0 0 0 0 0 0 0 0
tMSLRxd tRapid tSnmpd tHttpD tRan tRanscn tArrResp tArrRoute tMsApi tMSAr tThad tFaScn tThFru tSRL
2-130
i557Dump
Troubleshooting Use: Use
this command to view the current Ethernet chipset register values, statistics, and frame-buffer contents.
Available in Fabric OS versions: v3.1, v3.1.2 (Network Command Group) v4.2 Example Output: NA Example 2-62: A v3.x switch i557dump output
SDriver Control: unit = 0 ifq_head = 0x0 attached = TRUE pCSR = 0x83800000 pCFD = 0x10006400 pRFD = 0x10013000 pRFDL = 0x1001ba00 numLoans = 0 numFrees = 0 nCFD = 32 nRFD = 32 txRestart = 0x103d0ec0 rxRestart = 0x103d0e10 rxLockTicks = 900 rxLocks = 61 rxHandle = FALSE txStall = FALSE rxBcastDropped = 0 rxBcastPassed = 5083 vector = 0x42 baseAddr = 0x83800000 intEnable = 0x10406950 intDisable = 0x10406980 intAck = 0x104069a0 sysLocalToBus = 0x104069d0 sysBusToLocal = 0x10406a20 phyAddr = 1 phySpeed = 2 phyDpx = 2 others = 0 tcbTxThresh = 16 Physical Layer device (PHY): OUI: 0x00aa00 Intel Model: 0x154 82559[ER] (Embedded 82555) Generic MDI Registers: 0x00 ( 0): 0x1000 0x01 ( 1): 0x782d 0x02 ( 2): 0x02a8 0x03 ( 3): 0x0154 0x04 ( 4): 0x01e1 0x05 ( 5): 0x45e1 0x06 ( 6): 0x0001
10 AUTO HALF 100TXF 100TXH 10TF 10TH DONE AUTO LINK EXT
100TXF 100TX 10TF 10T CSMACD ACK 100TXF 100TX 10TF 10T CSMACD LPAUTO
Vendor-unique MDI Registers: 0x10 (16): 0x0a03
2-131
2
Note:
Vendor-unique Register 0x10 (16) indicates the current speed and duplexity of the Ethernet port. This can be derived by examining the lowest order 2 bits of the value: 0x0a03 = 0000 1010 0000 0011 Bit 0 of this register indicates duplexity; 0 => half duplex, 1 => full duplex Bit 1 of this register indicates speed; 0 => 10 Mbps, 1 => 100 Mbps This port is running at 100 Mbps, full.
0x11 (17): 0x0000 0x12 (18): 0x0001 0x13 (19): 0x0000 0x14 (20): 0x0000 0x15 (21): 0x0000 0x16 (22): 0x0000 0x17 (23): 0x0000 0x18 (24): 0x0000 0x19 (25): 0x0000 0x1a (26): 0x0000 0x1b (27): 0x0000 Receive Frame Area: 10d2bec0: 00000000 f0013600 10d2bed0: 50696000 07002611 10d2bee0: e0ec2800 067c0040 10d2bef0: 520d0c44 19111700 10d2bf00: bdbee840 00000000 10d2bf10: 44414641 43474443 10d2bf20: 43414341 41414341 10d2bf30: 46414646 46504541 Command Block List: 10d2cec0: 0004a000 10d2ced0: 070c0000 10d2cee0: 1c052802 10d2cef0: 17001685 10d2cf00: 9c300010 10d2cf10: 2e2e2e2e 10d2cf20: 203a3064 10d2cf30: 37343030
ffffffff 0aace084 a8c0e47d dd00f790 00000000 43414341 45200041 43454643
05eac03c 00450008 400a1685 1050cd6b 46464644 43414341 46444644 43414341
*.....6......<...* *.ìP.&........E.* *.(..@.|.}......@* *D..R........k.P.* *@...........DFFF* *AFADCDGCACACACAC* *ACACACAAA. EDFDF* *FFAFAEPFCFECACAC*
[some output omitted]

f0006a00 600047ac 061e0000 dd00520d 2e2a0000 2a2e2e2e 30373020 32206361 ffffffff 26115069 400aaa01 1911cd75 2e2e2e2e 30310d0a 30303063 35313136 00108236 00450008 a8c00c44 1850f790 2e2e2e40 33643264 30362030 20393630 *.....j......6...* *.....G.ìP.&..E.* *.(.........@D...* *.....R..u.....P.* *..0...*.....@...* *.......*..10d2d3* *d0: 070c0000 60* *0047ac 26115069 *
[some output omitted]
Note:
If there is no connection via TCP/IP condition on VxWorks switched during which no communication is possible via the Ethernet management port. This includes Ping, Web Tools, SNMP, Telnet, API, RSH and commands such as configUpload/Download and firmwareDownload. This condition is easier to troubleshoot on switches with a RS-232 port. A serial cable that connects to the motherboard is needed for the SW2800. This requires the switch to be powered off and the motherboard removed. To verify this condition on switches running a VxWorks based Fabric OS, run the command ifUp fei0 and retest with ping. If the condition did not change, run the command i557Show. If the second word of the Receive Frame Area section is the same for any Frame areas (see underlined words in example below), the switch has encountered the receive frame descriptor loan defect (#5753/8250). This is fixed in Fabric OS v2.4.1j, v2.5.1a, v2.6.0, and v3.0.2. This condition is not known to occur on Linux based Fabric OS versions.
Receive Frame Area: 10d09520: 00000000 f000dc00 10d09530: 50696000 07002611 10d09540: 6c4b2b00 067c0040 10d09550: be0e0c44 48151700 10d09560: 5e17e540 fdff0000 10d09570: 46504541 43454643 10d09580: 43414341 004c4241
ffffffff 0aace084 a8c0561f 18aa4292 00000001 43414341 01002000
05eac03c 00450008 400a1685 18500562 46414646 43414341 46444644
*............<...* *.ìP.&........E.* *.+Kl@.|..V.....@* *D......H.B..b.P.* *@..^........FFAF* *AEPFCFECACACACAC* *ACACABL.. ..DFDF*
2-132

10d09590: 10d095a0: 10d095b0: 10d095c0: 10d095d0: 10d095e0: 10d095f0: 10d09600: 10d09610: 46414646 00000000 50696000 6d4b2800 be0e0c44 6418b740 46504541 43414341 45504650 46504541 f000dc00 07002611 067c0040 48151700 00000000 43454643 004c4241 4544464e 43454643 ffffffff 0aace084 a8c0581f 18aa4592 00000000 43414341 01002000 45434643 43414341 05eac03c 00450008 400a1685 10503362 46414646 43414341 46434142 46484650 *FFAFAEPFCFECACAC* *............<...* *.ìP.&........E.* *.(Km@.|..X.....@* *D......H.E..b3P.* *@..d........FFAF* *AEPFCFECACACACAC* *ACACABL.. ..BACF* *PFPENFDECFCEPFHF*
2-133
ifshow
Available in Fabric OS versions: This is a CLI non-supportshow command in all VxWorks switch Fabric OS versions v4.2 Example Output: NA Additional Example/Case Studies: Troubleshooting Use: Use this command to display network interface information Use this command to display network interface information. If the operand ifname is provided, only that interface is displayed. If ifname is omitted, all interfaces are displayed. Each switch has three interfaces:
ei or fei is the 10BaseT or 100BaseT ethernet interface lo is the loopback interface fc is the Fibre Channel interface
The fc interface is displayed for switches running IP over Fibre Channel that have been assigned an FC-IP address. For each interface selected, the following information is displayed:
Flags (for example, loopback, broadcast, arp, running, debug) Internet address Broadcast address Netmask and subnetmask Ethernet address Route metric Maximum transfer unit Number of packets received and sent Number of input errors, output errors, and collisions
Example 2-63: To display ethernet interface information for a switch with a 10BaseT connection:
switch:admin> ifShow "ei" ei (unit number 0): Flags: (0x63) UP BROADCAST ARP RUNNING Internet address: 192.168.1.65 Broadcast address: 192.168.1.255 Netmask 0xffffff00 Subnetmask 0xffffff00 Ethernet address is 00:60:69:00:00:8a Metric is 0 Maximum Transfer Unit size is 1500 42962 packets received; 127 packets sent 0 input errors; 0 output errors 7 collisions
2-134
inetStatShow
Note: See root level netstat -a for v4.0.2c
Troubleshooting Use: Use this command to display active internet connections (including servers). Use this command or v4.x netstat - a command to test network connectivity between a management server and a switch. Available in Fabric OS versions: v3.1, v3.1.2 v4.2 Example Output: NA Troubleshooting Use: Use this command to display active internet connections (including servers). Example 2-32: To display the active Internet connections:
SW3800_12:admin> inetstatshow Active Internet connections (including servers) PCB Proto Recv-Q Send-Q Local Address -------- ----- ------ ------ -----------------103f918c TCP 0 0 0.0.0.0.80 103f980c TCP 0 0 0.0.0.0.1008 103f988c TCP 0 0 10.64.68.12.23 103f998c TCP 0 0 0.0.0.0.111 103f9b0c TCP 0 0 0.0.0.0.23 103f9e8c TCP 0 0 0.0.0.0.513 103f910c UDP 0 0 0.0.0.0.161 103f9a0c UDP 0 0 0.0.0.0.111
Foreign Address -----------------0.0.0.0.0 0.0.0.0.0 192.168.133.22.341 0.0.0.0.0 0.0.0.0.0 0.0.0.0.0 0.0.0.0.0 0.0.0.0.0
(state) ------LISTEN LISTEN ESTABLISHED LISTEN LISTEN LISTEN
Note:
From web page http://www.scit.wlv.ac.uk/cgi-bin/mansec?1M+netstat
TCP Sockets - The possible state values for TCP sockets are as follows: BOUND CLOSED CLOSING CLOSE_WAIT FIN_WAIT_1 FIN_WAIT_2 IDLE LAST_ LISTEN SYN_SENT TIME_WAIT Bound, ready to connect or listen. Closed. The socket is not being used. Closed, then remote shutdown; awaiting acknowledgment. Remote shutdown; waiting for the socket to close. Socket closed; shutting down connection. Socket closed; waiting for shutdown from remote. Idle, opened but not bound. ACK Remote shutdown, then closed; awaiting acknowledgment. Listening for incoming connections. Actively trying to establish connection. Wait after close for remote shutdown retransmission.
ESTABLISHED Connection has been established.
SYN_RECEIVED Initial synchronization of the connection under way.
2-135
ipaddrshow
Available in Fabric OS versions: v3.1, v.3.1.2, v4.1, v4.2 Version Differences: Version 4.x outputs have more than one Ethernet IP address v4.2 Example Output: Additional Example/Case Studies: Troubleshooting Use: Use this command to display the IP address for a switch or control processor. Use this command to display the Ethernet and FC IP addresses configured in the system. This command shows the Ethernet IP Address, Ethernet Subnetmask, Fibre Channel IP Address, Fibre Channel Subnetmask, and Gateway IP address for the switch. The FC IP Address shows none if the switch is not configured to run IP over Fibre Channel. Note that all Fibre Channel ports on a switch have the same IP address and subnet mask. All IP addresses are displayed in conventional dot ('.') notation or by the special value none. Subnet Masks show none if IP sub netting is not in effect. Example Example 2-64: To display the IP configuration details for the switch:
switch:admin> ipaddrshow Ethernet IP Address: 10.32.225.190 Ethernet Subnet Mask: 255.255.240.0 Fibre Channel IP Address: none Fibre Channel Subnet Mask: none Gateway Address: 10.32.224.1 switch:admin>
Example 2-65: v4.1 output from a 12000

CS12000_44:admin> ipaddrshow Switch number [0 for switch0, 1 for switch1, 2 for CP0, 3 for CP1, 4 for all IP addresses in system]: 4 SWITCH0 Ethernet IP Address: 10.64.148.44 Ethernet Subnetmask: 255.255.240.0 Fibre Channel IP Address: 0.0.0.0 Fibre Channel Subnetmask: 0.0.0.0 SWITCH1 Ethernet IP Address: 10.64.148.45 Ethernet Subnetmask: 255.255.240.0 Fibre Channel IP Address: 10.0.0.1 Fibre Channel Subnetmask: 255.0.0.0 CP0 Ethernet IP Address: 10.64.148.46 Ethernet Subnetmask: 255.255.240.0 HostName : cp0 Gateway Address: 10.64.144.1 CP1 Ethernet IP Address: 10.64.148.47 Ethernet Subnetmask: 255.255.240.0 HostName : cp1 Gateway Address: 10.64.144.1 Backplane IP address of CP0 : 10.0.0.5 Backplane IP address of CP1 : 10.0.0.6
Example 2-66: V4.2 output from a 24000

SW24000_32:admin> ipaddrshow SWITCH Ethernet IP Address: 10.64.148.32
2-136

Ethernet Subnetmask: 255.255.240.0 Fibre Channel IP Address: 0.0.0.0 Fibre Channel Subnetmask: 0.0.0.0 CP0 Ethernet IP Address: 10.64.148.34 Ethernet Subnetmask: 255.255.240.0 HostName : cp0 Gateway Address: 10.64.144.1 CP1 Ethernet IP Address: 10.64.148.35 Ethernet Subnetmask: 255.255.240.0 HostName : cp1 Gateway Address: 10.64.144.1 Backplane IP address of CP0 : 10.0.0.5 Backplane IP address of CP1 : 10.0.0.6 SW24000_32:admin>
2-137
ipstatshow
Available in Fabric OS versions: v3.1, v3.1.2 Version Differences: v4.2 Example Output: N/A Additional Example/Case Studies: Troubleshooting Use: Use this command to display the Internet Protocol (IP) statistics for an interface Use this command to display the Internet Protocol Statistics for an interface. If the operand ifname is provided, only that interface is displayed. If ifname is omitted, all interfaces are displayed. Each switch has three interfaces:
ei or fei is the 10BaseT or 100BaseT ethernet interface lo is the loopback interface fc is the fibre channel interface
The fc interface is displayed for switches running IP over Fibre Channel that have been assigned an FC-IP address. Example 2-67: To display the Internet Protocol Statistics for the 10BaseT connection interface:
SW3800_12:admin> ipstatshow "fei" total 182 badsum 0 tooshort 0 toosmall 0 badhlen 0 badlen 0 fragments 0 fragdropped 0 fragtimeout 0 forward 0 cantforward 0 redirectsent 0
2-138
islshow
Available in Fabric OS versions: v3.1, v3.1.2, v4.1, v4.2 Version Differences: Additional Example/Case Studies: Troubleshooting Use: Use this command to display ISL information Use this command to display the current connections and status of the ISL of each port on this switch. The WWN where the ISL is connected to, the speed of the connection, and whether this ISL is trunked, are displayed. Example 2-33: To display the ISL connections for the switch:
switch:admin> islshow 1: 33 -> 29 10:00:00:60:69:80:4f:84 switch sp: 2G bw: 4G TRUNK 2: 39 -> 7 10:00:00:60:69:80:4f:84 switch sp: 2G bw: 8G TRUNK 3: 41 -> (incompatible) 4: 47 -> (incompatible) 5: 57 -> 25 10:00:00:60:69:80:4f:84 switch sp: 2G bw: 4G TRUNK 6: 60 -> 2 10:00:00:60:69:80:4f:84 switch sp: 2G bw: 4G TRUNK
switch:admin> Note: Run trunkdebug < slot/port associated with area 41 & 47> to determine (incompatible) output reason. IslShow aggregate output allows a one glance trunk assessment of switch.
v4.2 Example Output: Example 2-68: v4.x islshow output from a 12 switch fabric
V4d227sw3900:admin> islshow 1: 0 -> 0 10:00:00:60:69:90:02:34 2: 16 -> 15 10:00:00:60:69:51:0e:ae 3: 20 -> 15 10:00:00:60:69:50:0d:9f 4: 24 -> 15 10:00:00:60:69:51:0d:dd 5: 31 -> 31 10:00:00:60:69:90:02:34 xiotech1_core_1 xiotech2_edge_2 xiotech2_edge_3 xiotech2_edge_1 xiotech1_core_1 sp: sp: sp: sp: sp: 2G 2G 2G 2G 2G bw: bw: bw: bw: bw: 2G 2G 2G 2G 2G
TRUNK TRUNK TRUNK
2-139
licenseShow
Available in Fabric OS versions: This is a supportshow output in all Fabric OS versions Troubleshooting Use: Use this command to display current license keys. Some features of the switch and of the Fabric are optional licensed products. An example is Web Tools which allows the Fabric to be managed through the worldwide web. Without a license key installed, the licensed product wont function. This command displays the current license keys, and a list of the licensed products that are enabled by these keys, or displays none if no license key is installed. A license key is a string of approximately 16 upper and lower case letters and digits. Case is significant. The key is an encrypted form of the switchs ID and the products licensed to run on this switch. Example 2-69:
licenseShow SbyzeQcdybTcz0fb: Web license bdR9ebd9zdceSAfy: Zoning license Ryydzz9zedSzze0R: QuickLoop license RcbzbSzzSSdc0cP: Fabric license bSeeQybcc9eTffRZ: Fabric Watch license bSeeQybcc9kTffRf: Trunking license
Note:
Verify all license stings have an associated option listed under it. A license without an associated option listed under it indicates an invalid license key.

dazzler16_49:admin> licenseshow cQy9Qz9QcQdRzARn: Web license 9SdRdbRdeATeSey: Zoning license eyRd9QeSQf0SeAg: 4 Domain Fabric license e9yycdcQSAAzzdN: Web license Zoning license SES license QuickLoop license Remote Switch license Remote Fabric license Extended Fabric license Fabric Watch license Performance Monitor license Trunking license Security license dazzler16_49:admin>
Note:
Check for entry fabric and value line licenses when you get a segmentation because of licensing issue. Entry fabric and value line 2 (VL2) licenses allow you to connect a max of 2 fabric switches, a value line 4(VL4) license will allow you to connect a maximum of 4 fabric switches. Notice license eyRd9QeSQf0SeAg in above v4.2 output says 4 Domain Fabric license - this is a VL 4 license.
2-140
mallocshow
Note: For internal debuggubg purposes only.
Available in Fabric OS versions: v3.0, v3.1, v3.2 Version Differences: v4.2 Example Output: Additional Example/Case Studies: Troubleshooting Use: Use this command to view memory allocation and de-allocation statistics.
Note:
This command has no additional Fabric OS information at this time. As the information becomes available the command will be inserted in this section.
2-141
mbufShow
Troubleshooting Use: Use this command to display IP memory information. Available in Fabric OS versions: v3.1, v3.1.2 (Network Command Group) v4.2 Example Output: NA Additional Example/Case Studies: Example 2-71: v3.1.2 output
Switch3200:admin> mbufshow type number -------------FREE : 799 DATA : 0 HEADER : 1 SOCKET : 0 PCB : 0 RTABLE : 0 HTABLE : 0 ATABLE : 0 SONAME : 0 ZOMBIE : 0 SOOPTS : 0 FTABLE : 0 RIGHTS : 0 IFADDR : 0 CONTROL : 0 OOBDATA : 0 IPMOPTS : 0 IPMADDR : 0 IFMADDR : 0 MRTABLE : 0 TOTAL : 800 number of mbufs: 800 number of times failed to find space: 0 number of times waited for space: 0 number of times drained protocols for space: 0 __________________ CLUSTER POOL TABLE _______________________________________________________________________________ size clusters free usage ------------------------------------------------------------------------------64 100 99 518 128 100 100 1358 256 40 40 40 512 40 40 25 1024 25 25 1 2048 25 25 0
-------------------------------------------------------------------------------
Note:
Mbufs are memory buffers used to hold parts of network packets. An mbuf is quite small, 128 bytes. It contains a header and then something like 100 bytes of data storage. You can chain them together to form bigger storage area's or you can use a cluster. A cluster is just a 2Kbytes buffer. A cluster can be linked to an mbuf. When this happens the data is stored only in the cluster and not the mbuf.
2-142
medbg -s1 -e1

Troubleshooting Use: This command is part of hadump output. See hadump for more information. Available in Fabric OS versions: v4.1, v4.2 Additional Example/Case Studies: See hadump output information Note: See hadump on page 2-110 output for additional medbg -s1 -e1 information

medbg -s1 -e1: Group Name = Switch MF Name = SwitchCP1 Sync Order: chassis:0 fcsw:0 chassis:0 CurSt = FSS_SYNC_SUCCESS PrevSt = FSS_SYNC_STARTED LaunchSt = SVC_ACTIVE Sync Time = Tue Dec 30 14:53:14 2003 Unsync Time = Tue Dec 30 14:50:54 2003 FabSt = STABLE fcsw:0 CurSt = FSS_SYNC_SUCCESS PrevSt = FSS_SYNC_STARTED LaunchSt = SVC_ACTIVE Sync Time = Tue Dec 30 14:53:15 2003 Unsync Time = Tue Dec 30 14:50:54 2003 FabSt = STABLE Group Name = Switch MF Name = SwitchCP1 Sync Order: chassis:0 fcsw:0 chassis:0 FSS_EVENTNEXT_STATEFSS CMD SENTSYSCTL MSG L:FSS_EVT_SYNC_SUCCESSFSS_SYNC_SUCCESS NONE NONE L:FSS_EVT_SYNC_STARTFSS_SYNC_STARTED NONE NONE L:FSS_EVT_DUMP_READYFSS_SYNC_STARTED SYNC_STARTNONE R:FSS_EVT_IMAGE_INCOMPFSS_ACTIVE_READY NONE NONE L:FSS_EVT_SYNC_STOPFSS_SYNC_STOPPED NONE NONE L:FSS_EVT_SYNC_SUCCESSFSS_SYNC_SUCCESS NONE NONE L:FSS_EVT_SYNC_STARTFSS_SYNC_STARTED NONE NONE L:FSS_EVT_DUMP_READYFSS_SYNC_STARTED SYNC_STARTNONE L:FSS_EVT_ACTIVE_RDYFSS_ACTIVE_READY NONE SVC_ACTIVE L:SCTL_EVT_TAKE_CTRLSCTL_ACTIVE TAKE_CTRL NONE R:FSS_EVT_IMAGE_INCOMPFSS_STANDBY_READY NONE NONE L:FSS_EVT_SYNC_STOPFSS_SYNC_STOPPED NONE NONE L:FSS_EVT_SYNC_SUCCESSFSS_SYNC_SUCCESS NONE NONE L:FSS_EVT_SYNC_STARTFSS_SYNC_STARTED NONE NONE L:FSS_EVT_IMAGE_COMPFSS_IMAGE_COMP NONE SVC_STANDBY L:SCTL_EVT_SLAUNCHSCTL_SLAUNCH NONE NONE L:ME_EVT_FSS_INITFSS_INIT NONE NONE
2-143
memshow
Note: For internal debuggubg purposes only.
Available in Fabric OS versions: v3.0, v3.1, v3.1.2 Version Differences: v4.2 Example Output: NA Troubleshooting Use: Use this command to view the amount of free and used memory in switch Additional Example/Case Studies: Example 2-73: v3.1.2 output
Switch3200:admin> memshow status bytes blocks avg block max block ------ --------- -------- ---------- ---------current free 21642816 15 1442854 21642320 alloc 5508784 4886 1127 cumulative alloc 8269712 49521 166 Switch3200:admin>
2-144
mii-tool vv Link information

Available in Fabric OS versions: v4.0, v4.1, v4.2 Troubleshooting Use: Use this command to view 10 Base T, full duplex type information. Look for link OK in output (see embedded note). Example 2-34:
mii-tool -vv eth0: negotiated 100baseTx-FD, link ok registers for MII PHY 1: 3000 782d 0040 61e1 01e1 41e1 0005 2001 0000 0000 0000 0000 0000 0000 0000 ------- 0300 0000 0000 0200 0051 0200 0000 003f 851f 9f00 008a 082f 0000 80a0 000b product info: Broadcom BCM5221 rev 1 basic mode: autonegotiation enabled basic status: autonegotiation complete, link ok / Note: This is what you want to see! capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD eth1: negotiated 100baseTx-HD, link ok registers for MII PHY 1: 3000 782d 02a8 0154 05e1 40a1 0001 ------- ---- ---- ---- ---- ---- ---- ---0a02 0000 0001 0000 0000 0000 0000 0001 0000 0000 0000 0000 ---- ---- ---- ---product info: Intel 82555 rev 4 basic mode: autonegotiation enabled basic status: autonegotiation complete, link ok capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control link partner: 100baseTx-HD 10baseT-HD
Note:
If you see link ok above but still can not cannot try connecting to the other Ethernet sidethe other CPs access. Then run ifmodeset and hardest the IP address to 10 or 100 half duplex, all Ethernets can do half duplex. 10/ half duplex is the safest setting. If you are on a v4.x switch you do not have to reboot for ifmodeset changes to take effect (v3.x or lower switch you will have to reboot to get ifmodeset changes to take effect).

mii-tool -vv: eth0: negotiated 100baseTx-FD, link ok registers for MII PHY 1: 3000 782d 0040 61e4 01e1 41e1 0005 2001 0000 0000 0000 0000 0000 0000 0000 ------- 0301 0000 0000 0200 003c 0100 0001 003f 851f 9f00 008a 082f 0000 80a0 000b product info: Broadcom BCM5221 rev 4 basic mode: autonegotiation enabled basic status: autonegotiation complete, link ok capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD eth1: link ok registers for MII PHY 2: 3000 780d 0040 61e4 01e1 0000 0004 2001 0000 0000 0000 0000 0000 0000 0000 ------- 8323 0000 00b6 0200 0009 0100 0001 0037 000d 9f00 008a 0827 0000 0000 000b product info: Broadcom BCM5221 rev 4
2-145

autonegotiation enabled link ok 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
basic mode: basic status: capabilities: advertising:
2-146
mqshow
Note: For internal debugging purposes only.
Available in Fabric OS versions: v3.0, v3.1, v3.1.2 v4.2 Example Output: NA Additional Example/Case Studies: Troubleshooting Use: Use this command if memory problems on the switch are suspected. VxWorks is a flat memory system such that each task does not have its own consistent space in memory. Each task in the Fabric OS has an associating queue. Tasks either get called or functions get put into associated task queues thus requiring read action. The response task tresponse has an associated queue called response_q. When frames are put into the response queue, the response task reads them and appropriately acts on them. The following example shows port 0s queue names, associated memory addresses, maximum value in bytes (Max), the number of times queue went over max value since boot (High) and the current queue status (Current). In the example below, the receive queue went over its high 2560 Bytes, 16 times. It is important to have a known good supportshow baseline to compare and contrast supportshow output information like mqshow. This is not abnormal for this queue. Internal Brocade engineers might look here if they suspected a memory problem as seen with MQ-Errors in the error log. Example 2-75:
mqShow 0 Name Id Max High Current ------------------------------------------------------restart_q 0x10395000 2560 00 err_q 0x10380f80 2560 00 timer_q 0x1036b960 2560 40 response_q 0x10356340 2560 00 receive_q 0x103422c0 2560 16 transmit_q 0x1032e240 2560 11 scn_q 0x1031a1c0 2560 80 pb_q 0x102fcb30 2560 00 fcp_q 0x10196250 2560 80 ran_q0 0x1018f180 512 00 ran_q1 0x1018b100 512 00 ran_q2 0x10187080 512 00 ran_q3 0x10183000 512 00 ran_q4 0x1017ef80 512 00 ranscn_q 0x10175930 1024 00 diag_q 0x10160310 2560 10 MS_RAPImq0 0x1015c290 512 00 MS_RAPImq1 0x10158210 512 00 MS_RAPImq2 0x10154190 512 00 MS_RAPImq3 0x10150110 512 00 MS_RAPImq4 0x1014c090 512 00 MS_RAPImq5 0x10148010 512 00 MS_RAPImq6 0x10143f90 512 00 MS_RAPImq7 0x1013ff10 512 00 MS_RAPImq8 0x1013be90 512 00 MS_RAPImq9 0x10137e10 512 00 fabric_q 0x1011d580 2560 80 HttpMSmq0 0x11f41390 128 00 HttpMSmq1 0x11f40310 128 00 HttpMSmq2 0x11f3f290 128 00 HttpMSmq3 0x11f3e210 128 00 HttpMSmq4 0x11f3d190 128 00 HttpMSmq5 0x11f3c110 128 00 HttpMSmq6 0x11f3b090 128 00
2-147

0x11f3a010 0x11f38f90 0x11f37f10 0x11f20270 0x11f0abf0 0x11ef2720 0x11ede6a0 0x11ec7af0 0x11e8dc50 0x11e79bd0 0x11e63170 0x11dfb7f0 0x11de37f0 0x11dcf700 0x11db8d00 0x11da0f20 0x11d8cea0 128 128 128 2560 2560 2560 2560 2560 2560 2560 2560 2560 2560 2560 2560 2560 2560 00 00 00 60 10 80 80 200 50 10 90 20 110 00 80 00 80
HttpMSmq7 HttpMSmq8 HttpMSmq9 rt_q qloop_q zone_realtime_q zone_q fspf_q ns_q nsirc_q nscam_q as_q ms_q msAsync_q famib_q apims_q fru_q
Number of message queues = 52
2-148
myid
Available in Fabric OS versions: v4.1, v4.2 Troubleshooting Use: Use this command to display the current login session details. Use this command to display the status of the system and the login session details. The Status displays if the system is Redundant or Non-Redundant or Unknown.The login session gives details of the following:
Which CP/Switch (or console/serial port) was used to login The IP address of the current login session for telnet or the name of the current Console port or the Serial port (if modem login used). The Current CP's mode (Active or Standby or Unknown) The Current System Status (Redundant or Non-Redundant or Unknown).

switch:admin> myid Current Switch: switch Session Detail: switch (123.123.123.123) Active Redundant switch:admin>
Note:
The myid command is extremely helpful to identify a switch that is not named in a meaningful manner, myid output provides an easy way to determine switch IP address and status.

myid: Current Switch: Session Detail: SW24000_32 SW24000_32 (10.64.148.32) Active
Redundant
2-149
nsAllShow
Available in Fabric OS versions: All Version Differences None Troubleshooting Use: Use this command to dispaly global Name Server information. Additional Example/Case Studies: Use this command to display the 24-bit fibre channel addresses of all devices in all switches in the fabric. If the operand type is supplied, only devices of specified FC-PH type are displayed. If type is omitted, all devices are displayed. Note: Specifying the type operand causes the switch to send out a query to every switch in the fabric. On a large fabric it is recommended NOT to run a script that repeatedly issues the nsallshow command with a type operand specified.
Example 2-36: To display all devices in the Fabric, followed by all type 8 (SCSI-FCP) devices and all type 5 (SCSIFCIP) devices:
switch:admin> nsallshow 12 Nx_Ports in the Fabric { 011200 0118e2 0118e4 0118e8 0118ef 021200 0214e2 0214e4 0214e8 0214ef } switch:admin> nsallshow 8 8 FCP Ports { 0118e2 0118e4 0118e8 0118ef 0214e2 0214e4 0214e8 0214ef } switch:admin> nsallshow 5 2 FC-IP Ports in the Fabric { 011200 021200}
Example 2-37: 4.02c

nsallshow: 28 Nx_Ports in the Fabric { 010a00 010dba 010dbc 010dc3 010dc5 010dc6 010dc7 010dc9 010dca 010dcb 010dcc 010dcd 010dce 010dd1 010dd2 010dd3 010dd4 010dd5 010dd6 010dd9 010dda 010ddc 010de0 010de1 010de2 010de4 010de8 010def
Note:
The output of this command in conjunction with fabricshow and topologyshow can be used to draw the fabric. A topologyshow output from the Fabric switches can then be used to map interconnections. In order for two devices in a Fabric to see each other they must both be in the nsallshow output unless Quickloop is being used in the Fabric.

nsallshow: { 010100 015e00 017fd1 017fd2 017fd3 017fd4 017fd5 017fd6 017fd9 017fda 017fdc 017fe0 017fe1 017fe2 017fe4 017fe8 017fef 17 Nx_Ports in the Fabric }
2-150
nscamshow
Available in Fabric OS versions: v3.0, v3.1, v3.1.2, v4.1, v4.2 (not available as part of v4.0 supportshow output) Version Differences: Prior to versions 2.6.1, 3.1 and 4.1 nscamshow displayed hot and cold switch and device lists. When the nodefind (input a WWN get out hex 24-bit fabric address) and nszonemember (use hex 24-bit fabric address to display an nsshow like output of all devices zoned with given 14-bit address ex: nszonmember 0x020400 will display an nsshow view of all devices zoned with the fabric device on domain 2, port 4) commands were introduced in v3.1/4.1 the nscamshow outputs deleted the hot and cold switch and device lists. Additional Example/Case Studies: Troubleshooting Use: Use this command to display information about remote devices in the Name Server Cache. Use this command to display the local Name Server Cache Manager (NSCaM) information about the devices discovered in the fabric by the Name Server Cache manager. The message No Entry found! is displayed if the Name Server Cache Manager hasn't discovered new switches and any new devices in the fabric. Prior to versions 3.1 and 4.1 information displayed showed whether the other switch was hot or cold. A hot switch has devices in a zone with devices on the local switch. A cold switch does not have any attached devices in a zone with any of the local switches devices. There are also hot and cold tables for the devices on attached switches depicting exactly which devices are hot (in a zone with local switch devices) and which devices are cold (not in a zone with local switch devices. This ns cache feature allows a nscam task to run in the background retrieving information from other switches, making the name server and RSCN functionality much less intrusive in a Fabric. For each remote switch found the output of this command shows the domain number, state, revision, owner, the list of cold and hot devices for that domain number. For each device found in the cold or hot devices list, the following information is displayed: Type U Pid COS PortName NodeName for unknown, N for N_Port, NL for NL_Port. The 24-bit Fibre Channel address. A list of classes of service supported by the device. The device's port Worldwide Name. The device's node Worldwide Name.
There may be additional lines if the device has registered any of the following information (the switch automatically registers SCSI inquiry data for FCP target devices): FC4s supported and fabric port name. Example 2-78: (from a single switch)
switch:admin> nscamshow No entry is found!
v3.0 Example Output before hot and cold lists were removed (v3.1/4.1 nodefind and nszonemember nulled the need for nscamshow hot/cold lists): Example 2-79:
switch:admin> nscamshow Switch entry for 14 state rev owner hot v302 0xfffc09 Hot device list: count 3 Type Pid COS PortName NodeName N 0e0000; 3;50:05:02:e0:10:00:0b:27;50:05:02:e0:10:00:0b:27; FC4s: FCP Fabric Port Name: 20:00:00:60:69:50:04:c1 N 0e0c00; 2,3;10:00:00:00:c9:23:d3:6b;20:00:00:00:c9:23:d3:6b; FC4s: FCP Fabric Port Name: 20:0c:00:60:69:50:04:c1 N 0e0d00; 2,3;10:00:00:00:c9:24:05:5c;20:00:00:00:c9:24:05:5c;
2-151
FC4s: FCP Fabric Port Name: 20:0d:00:60:69:50:04:c1 Cold device list: count 5 Type Pid COS PortName NodeName N 0e0300; 2,3;20:00:00:e0:69:c0:68:87;10:00:00:e0:69:c0:21:31; FC4s: FCIP Fabric Port Name: 20:03:00:60:69:50:04:c1 N 0e0400; 2,3;20:00:00:e0:69:c0:78:67;10:00:00:e0:69:c0:6a:fd; FC4s: FCIP Fabric Port Name: 20:04:00:60:69:50:04:c1 N 0e0700; 2,3;20:00:00:e0:69:c0:7d:4a;10:00:00:e0:69:c0:71:38; FC4s: FCIP Fabric Port Name: 20:07:00:60:69:50:04:c1 N 0e0900; 2,3;20:00:00:e0:69:c0:78:7c;10:00:00:e0:69:c0:6c:70; FC4s: FCIP Fabric Port Name: 20:09:00:60:69:50:04:c1 N 0e0b00; 2,3;20:00:00:e0:69:c0:7d:39;10:00:00:e0:69:c0:68:46; FC4s: FCIP Fabric Port Name: 20:0b:00:60:69:50:04:c1 Total count of devices on the switch is 8 Switch entry for 15 state rev owner cold v302 0xfffc09 Hot device list: count 0 No entry is found! Cold device list: count 1 Type Pid COS PortName NodeName NL 0f0201; 2,3;10:00:00:00:c9:2c:33:ba;20:00:00:00:c9:2c:33:ba; Fabric Port Name: 20:02:00:60:69:50:05:2d Total count of devices on the switch is 1 Switch entry for 33 state rev owner cold v302 0xfffc09 Hot device list: count 0 No entry is found! Cold device list: count 0 No entry is found! Total count of devices on the switch is 0
See output in Example 2-79 (partial extract from a switch in a twenty four switch fabric remote switches status varies. Zoning is enabled. Switch 14 is in a hot state with local switch (indicated in state column) indicating it has devices that are in a zone with the local switch running Fabric OS version 3.0.2 (indicated in rev column by v302). The domain of the local switch is 9 as indicated in by domain controller name (also referred to as embedded port name) address fffc09 in owner column. There are 3 devices on switch 14 in zones with local devices (indicated in Hot device list: count 3). There are five devices not in a zone with local switch devices (indicated in Cold device list: count 5). The last line of the output indicates that there are 8 devices on this attached switch. Switch 15 is in a cold state with local switch (indicated in state column) indicating it has no devices that are in a zone with the local switch running Fabric OS version 3.0.2 (indicated in rev column by v302). The domain of the local switch is 9 as indicated in by domain controller name (also referred to as embedded port name) address fffc09 in owner column. There are 0 devices on switch 15 in zones with local devices (indicated in Hot device list: count 0). There is 1 devices not in a zone with local switch devices (indicated in Cold device list: count 1). The last line of the output indicates that there is 1 device on this attached switch. Switch 33 is in a cold state with local switch (indicated in state column) indicating it has no devices that are in a zone with the local switch running Fabric OS version 3.0.2 (indicated in rev column by v302). The domain of the local switch is 9 as indicated in by domain controller name (also referred to as embedded port name) address fffc09 in owner column. There are 0 devices on switch 33 in zones with local devices (indicated in Hot device list: count 0). There are 0 devices not in a zone with local switch devices (indicated in Cold device list: count 0). The last line of the output indicates that there are not any devices on this attached switch.
2-152
Note:
See v2.6.0c and 3.0.2c nscamShow information in this guide above for information about how nscamShow worked in pre v3.1/4.1 Fabric OS versions. The major difference in v3.1/4.1 information is that the hot and cold device lists have been merged. You can no longer determine which devices on remote switches are in a zone with devices on local switch, where this command was issued, using this command. It is still useful, along with nsShow, to retrieve a complete WWN listing of all Fabric devices at the CLI.
v4.1 Example Output (notice that there are no hot or cold lists - modefine and nszonemember nulled the need): Example 2-38:
nscamshow: nscam show for remote switches: Switch entry for 2 state rev owner known v310 0xfffc01 Device list: count 3 Type Pid COS PortName NodeName N 020000; 2,3;10:00:00:00:c9:2b:fe:94;20:00:00:00:c9:2b:fe:94; Fabric Port Name: 20:00:00:60:69:51:2d:0b N 020100; 2,3;10:00:00:00:c9:29:23:98;20:00:00:00:c9:29:23:98; FC4s: FCP Fabric Port Name: 20:01:00:60:69:51:2d:0b N 020200; 2,3;50:06:04:82:bf:d2:7b:93;50:06:04:82:bf:d2:7b:93; FC4s: FCP Fabric Port Name: 20:02:00:60:69:51:2d:0b v4.2 Example Output:
Example 2-80:
nscamshow: nscam show for remote switches: No entry is found!
2-153
nsShow
Available in Fabric OS versions: All Version Differences: versions 3.1/4.1 added a -r parameter that allowed SCR information gathering. Additional Example/Case Studies: Troubleshooting Use: Use this command to display local Name Server information, including information about devices connected to this switch, and cached information about devices connected to other switches in the fabric. The following message is displayed if there is no information in this switch:
There is no entry in the Local Name Server
There still may be devices connected to other switches in the fabric. The command nsAllShow displays information from all switches. Each line of output shows: * Indicates a cached entry from another switch.
Type U for unknown, N for N_Port, NL for NL_Port. PID 24-bit fibre channel address. COS List of classes of service supported by device. PortName Device port worldwide name. NodeName Device node worldwide name. TTL Time-to-live (in seconds) for cached entries, NA (not applicable) if the entry is local, or if -r operand used this
column lists the State Change Registration: 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 (1 and 2)) Register to receive all RSCN requests issued by the Fabric Controller for events detected by the affected N_Port ID pages.
There may be additional lines if the device has registered any of the following information (the switch automatically registers SCSI inquiry data for FCP target devices):
FC4s supported IP address IPA Port and node symbolic names Fabric Port Name - This is the WWN of the port on the switch that the device is physically connected to. Hard address and/or port IP address

nsshow: The Local Name Server has 2 entries { Type Pid COS PortName NodeName TTL(sec) N 010a00; 2,3;10:00:00:00:c9:2a:6b:3b;20:00:00:00:c9:2a:6b:3b; na FC4s: FCIP FCP Fabric Port Name: 20:0a:00:60:69:80:40:b2 NL 010dba; 3;21:00:00:20:37:00:ff:c8;20:00:00:20:37:00:ff:c8; na FC4s: FCP [SEAGATE ST39103FC 0002] Fabric Port Name: 20:0d:00:60:69:80:04:b2
2-154
Note:
The nsShow output can be used to match customer drawings to what is actually attached to the local switch. It can also be used to determine if the Fabric sees the device. Devices do not see each other if the Fabric doesnt see them first. If a device is depicted in the nsShow output then the local switch can see it. The next step would be to determine if the entire Fabric sees it.look in nsallshow and nscamShow.

nsshow: { Type Pid COS PortName NodeName SCR N 010100; 2,3;10:00:00:00:c9:29:06:7d;20:00:00:00:c9:29:06:7d; 3 FC4s: FCIP FCP NodeSymb: [36] "Emulex LP9002 FV3.90A7 DVv5-2.21a7 " Fabric Port Name: 20:01:00:60:69:80:2d:4a N 015e00; 2,3;10:00:00:00:c9:2b:7f:90;20:00:00:00:c9:2b:7f:90; 3 FC4s: FCP NodeSymb: [35] "Emulex LP9002 FV3.90A7 DV5-5.01A0 " Fabric Port Name: 20:5e:00:60:69:80:2d:4a 017fd1; 3;21:00:00:04:cf:4c:e6:6b;20:00:00:04:cf:4c:e6:6b; 0 FC4s: FCP [SEAGATE ST336605FC 0003] Fabric Port Name: 20:7f:00:60:69:80:2d:4a 017fd2; 3;21:00:00:04:cf:62:0c:05;20:00:00:04:cf:62:0c:05; 0 FC4s: FCP [SEAGATE ST336605FC 0003] Fabric Port Name: 20:7f:00:60:69:80:2d:4a 017fd3; 3;21:00:00:04:cf:62:04:b2;20:00:00:04:cf:62:04:b2; 0 FC4s: FCP [SEAGATE ST336605FC 0003] Fabric Port Name: 20:7f:00:60:69:80:2d:4a 017fd4; 3;21:00:00:04:cf:4c:ef:ee;20:00:00:04:cf:4c:ef:ee; 0 FC4s: FCP [SEAGATE ST336605FC 0003] Fabric Port Name: 20:7f:00:60:69:80:2d:4a 017fd5; 3;21:00:00:04:cf:62:07:58;20:00:00:04:cf:62:07:58; 0 FC4s: FCP [SEAGATE ST336605FC 0003] Fabric Port Name: 20:7f:00:60:69:80:2d:4a 017fd6; 3;21:00:00:20:37:15:09:c3;20:00:00:20:37:15:09:c3; 0 FC4s: FCP [SEAGATE ST336605FC 0002] Fabric Port Name: 20:7f:00:60:69:80:2d:4a 017fd9; 3;21:00:00:20:37:42:5f:da;20:00:00:20:37:42:5f:da; 0 FC4s: FCP [SEAGATE ST336605FC 0002] Fabric Port Name: 20:7f:00:60:69:80:2d:4a 017fda; 3;21:00:00:20:37:15:0b:bc;20:00:00:20:37:15:0b:bc; 0 FC4s: FCP [SEAGATE ST336605FC 0003] Fabric Port Name: 20:7f:00:60:69:80:2d:4a 017fdc; 3;21:00:00:20:37:42:43:b1;20:00:00:20:37:42:43:b1; 0 FC4s: FCP [SEAGATE ST336605FC 0003] Fabric Port Name: 20:7f:00:60:69:80:2d:4a 017fe0; 3;21:00:00:20:37:42:66:3e;20:00:00:20:37:42:66:3e; 0 FC4s: FCP [SEAGATE ST336605FC 0003] Fabric Port Name: 20:7f:00:60:69:80:2d:4a
NL
NL
NL
NL
NL
NL
NL
NL
NL
NL
2-155
2
NL

017fe1; 3;21:00:00:20:37:e6:8e:3e;20:00:00:20:37:e6:8e:3e; 0 FC4s: FCP [SEAGATE ST336605FC 0002] Fabric Port Name: 20:7f:00:60:69:80:2d:4a 017fe2; 3;21:00:00:20:37:e6:9a:b9;20:00:00:20:37:e6:9a:b9; 0 FC4s: FCP [SEAGATE ST336605FC 0002] Fabric Port Name: 20:7f:00:60:69:80:2d:4a 017fe4; 3;21:00:00:20:37:42:66:2d;20:00:00:20:37:42:66:2d; 0 FC4s: FCP [SEAGATE ST336605FC 0002] Fabric Port Name: 20:7f:00:60:69:80:2d:4a 017fe8; 3;21:00:00:20:37:15:18:08;20:00:00:20:37:15:18:08; 0 FC4s: FCP [SEAGATE ST336605FC 0003] Fabric Port Name: 20:7f:00:60:69:80:2d:4a 017fef; 3;21:00:00:20:37:e6:9a:cb;20:00:00:20:37:e6:9a:cb; 0 FC4s: FCP [SEAGATE ST336605FC 0002] Fabric Port Name: 20:7f:00:60:69:80:2d:4a
NL
NL
NL
NL
The Local Name Server has 17 entries }
2-156
persistent portlogdump
Available in Fabric OS versions: v4.1, v4.2 Additional Example/Case Studies: Troubleshooting Use: Use this command to view a portion of the portlog saved to flash. There is no command to enable persistent portlog. Portlog is saved in flash only by the panic dump subsystem under system panic conditions. This command is also integrated as part of the v4.x pdShow command. Basically when you type pdShow it shows persistent portlog for all switch instances along with other, relevant panic/ watchdog information. By default whenever a panic condition occurs, a part of the portlog is saved in flash automatically. So there is no need to enable anything specifically. Example 2-40:
Persistent portlogdump: showing from flash syslogdupdatecfg: fopen failed on /etc/syslog.conf portLogDisplay: failed to read from flash portLogDump 0,1 after a panic or watchdog reboot could give you portLogDump output saved from last failure.
Note:
portLogDump 0,1 output is the persistent portlogdump output that is part of v3.1 plus supportshows.

Persistent portlogdump: port log in flash is empty
2-157
portcamshow
Available in Fabric OS versions: v4.1, v4.2 Additional Example/Case Studies: Troubleshooting Use: Use this command to display the current filter CAM utilization of all ports or one port specified at input. See story in Example 2-51 to illustrate command use. The following information is displayed: SID used Display total number of CAM entries used by this port. Please note that each CAM entry (either SID or DID CAM) can be shared among ports in the same quad. DID used Display total number of CAM entries used by this port. Please note that each CAM entry (either SID or DID CAM) can be shared among ports in the same quad. SID entries Display all existing Source ID entries within the CAM per quad. Please note that each CAM entry (either SID or DID CAM) can be shared among ports in the same quad. DID entries Display all existing Destination ID entries within the CAM per quad. Please note that each CAM entry (either SID or DID CAM) can be among ports in the same quad. SID Free Display the total number of free SID CAM entries per quad. DID Free Display the total number of free DID CAM entries per quad. Example 2-41: Since stories shed the best light. portcamshow and sometimes portzoneshow commands were invoked before zoning created, after zoning created but before it was enabled and then again after it was enabled: There was no portcamshow output (everything was 0) until zoning was enabled (output after zoning created was the same as pre-zone output):
SWITCH:admin> cfgenable "testcfg" zone config "testcfg" is in effect Updating flash ... SWITCH:admin> cfgshow Defined configuration: cfg:testcfg test zone:test 1,11; 2,15 Effective configuration: cfg:testcfg zone:test1,11 2,15 SWITCH:admin> portcamshow Ports of Slot 7 -----------------------Port SID used DID used 0 0 0 1 1 1 /slot 7, port 1 had a host not in zone 2 0 0 3 0 0 4 0 0 5 0 0 6 0 0 7 0 0 8 0 0 9 0 0 10 0 0 11 2 1 /slot 7, port 11 had a host in zone 12 0 0 13 0 0 14 0 0 15 0 0 -----------------------Quad ports (SID Free, DID Free)
2-158

00-03 (63, 511) 04-07 (64, 512) 08-11 (62, 511) 12-15 (64, 512) /since it is not in a zone, port 1 can only talk to itself, portrayed in portcamshow 7/1 output: switch:admin> portcamshow 7/1 -------------------------------------------------Area SID used DID used SID entries DID entries 01 1 1 010100 010100 -------------------------------------------------Quad ports (SID Free, DID Free) 00-03 (63, 511)
/since it is in a zone, port 11 can talk to itself and port on attached switch in same zone, portrayed in portcamshow 7/11 output: switch:admin> portcamshow 7/11 -------------------------------------------------Area SID used DID used SID entries DID entries 11 2 1 010b00 010b00 020f00 -------------------------------------------------Quad ports (SID Free, DID Free) 08-11 (62, 511) Ports of Slot 8 -----------------------Port SID used DID used 0 0 0 1 0 0 2 0 0 3 0 0 4 0 0 5 0 0 6 0 0 7 0 0 8 0 0 9 0 0 10 0 0 11 0 0 12 0 0 13 0 0 14 0 0 15 1 1 -----------------------Quad ports (SID Free, DID Free) 00-03 (64, 512) 04-07 (64, 512) 08-11 (64, 512) 12-15 (63, 511) /like slot 7, port 1 above slot 8, port 15 (since it is not in a zone) can only talk to itself.
Example 2-42: This portzoneshow output displays how zoning is enforced on the switch:
SWITCH:admin> PORT: PORT: PORT: PORT: PORT: PORT: PORT: PORT: PORT: PORT: PORT: PORT: PORT: PORT: PORT: PORT: PORT: PORT: portzoneshow 0 Not Zoned 1 Enforcement: HARD PORT defaultHard: 1 F-port: 1 2 Enforcement: E-Port defaultHard: 0 F-port: 0 3 Not Zoned 4 Enforcement: E-Port defaultHard: 0 F-port: 0 5 Enforcement: E-Port defaultHard: 0 F-port: 0 6 Enforcement: E-Port defaultHard: 0 F-port: 0 7 Not Zoned 8 Not Zoned 9 Not Zoned 10 Not Zoned 11 Enforcement: HARD PORT defaultHard: 0 F-port: 1 12 Not Zoned 13 Not Zoned 14 Not Zoned 15 Not Zoned 16 Not Zoned 17 Not Zoned
2-159

PORT: PORT: PORT: PORT: PORT: PORT: PORT: PORT: PORT: PORT: PORT: PORT: PORT: PORT: 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Not Zoned Not Zoned Not Zoned Not Zoned Not Zoned Not Zoned Not Zoned Not Zoned Not Zoned Not Zoned Not Zoned Not Zoned Not Zoned Enforcement: HARD PORT
defaultHard: 1
F-port: 1
Portzoneshow output, hard, soft and session-based enforced, has to do with how zoning is configured. In bloom ASICs all zones defined using WWNs or domain, area are hard enforced. Hard enforced means that communication to the device on the target port is blocked if not in the same zone as communicating device. All devices should go to the name server (directory server) to determine who they can communicate with in the Fabric. Some devices, called bad citizens, attempt communication with devices not in same zone even after name server communication. If target is in a hard defined zone then communication to that target will be blocked on the ASIC port. Session-based enforced zoning occurs on Bloom ASICs when mixed zones are created (a mix of WWN and domain, area in the same zone). Session-based zoning enforcement is only available in Bloom ASIC switches - in Bloom based switches mixed zone elements will go session based before they go soft-enforced (until available ASIC memory runs out). Session based enforcement blocks PLOGIs at the destination port. End devices in a fabric cannot communicate before they PLOGI into each other. Soft enforced zoning means devices still query the name server for a list of accessible devices but can communicate with them, even if they are not in the same zone, if soft enforced. Soft enforcement could also occur if ASIC zone memory is close to saturation. In a mixed Fabric, Loom and Bloom ASICs soft enforced or session enforced zoning occurs per Bloom ASIC rules defined above on Bloom ports but devices become soft enforced on Loom ASICs when defined using all WWNs. v4.2 Example Output: Example 2-83:
portcamshow: Ports of Slot 1 -----------------------Port SID used DID used 0 0 0 1 0 0 2 0 0 3 0 0 4 0 0 5 0 0 6 0 0 7 0 0 8 0 0 9 0 0 10 0 0 11 0 0 12 0 0 13 0 0 14 0 0 15 0 0 -----------------------Quad ports (SID Free, DID Free) 00-03 (64, 512) 04-07 (64, 512) 08-11 (64, 512) 12-15 (64, 512) Ports of Slot 2 -----------------------Port SID used DID used 0 0 0 1 0 0 2 0 0
2-160

3 0 0 4 0 0 5 0 0 6 0 0 7 0 0 8 0 0 9 0 0 10 0 0 11 0 0 12 0 0 13 0 0 14 0 0 15 0 0 -----------------------Quad ports (SID Free, DID Free) 00-03 (64, 512) 04-07 (64, 512) 08-11 (64, 512) 12-15 (64, 512) Ports of Slot 4 -----------------------Port SID used DID used 0 0 0 1 0 0 2 0 0 3 0 0 4 0 0 5 0 0 6 0 0 7 0 0 8 0 0 9 0 0 10 0 0 11 0 0 12 0 0 13 0 0 14 0 0 15 0 0 -----------------------Quad ports (SID Free, DID Free) 00-03 (64, 512) 04-07 (64, 512) 08-11 (64, 512) 12-15 (64, 512) Ports of Slot 7 -----------------------Port SID used DID used 0 0 0 1 0 0 2 0 0 3 0 0 4 0 0 5 0 0 6 0 0 7 0 0 8 0 0 9 0 0 10 0 0 11 0 0 12 0 0 13 0 0 14 0 0 15 0 0 -----------------------Quad ports (SID Free, DID Free) 00-03 (64, 512) 04-07 (64, 512) 08-11 (64, 512) 12-15 (64, 512) Ports of Slot 8 ------------------------
2-161
Port SID used DID used 0 0 0 1 0 0 2 0 0 3 0 0 4 0 0 5 0 0 6 0 0 7 0 0 8 0 0 9 0 0 10 0 0 11 0 0 12 0 0 13 0 0 14 0 0 15 0 0 -----------------------Quad ports (SID Free, DID Free) 00-03 (64, 512) 04-07 (64, 512) 08-11 (64, 512) 12-15 (64, 512) Ports of Slot 9 -----------------------Port SID used DID used 0 0 0 1 0 0 2 0 0 3 0 0 4 0 0 5 0 0 6 0 0 7 0 0 8 0 0 9 0 0 10 0 0 11 0 0 12 0 0 13 0 0 14 0 0 15 0 0 -----------------------Quad ports (SID Free, DID Free) 00-03 (64, 512) 04-07 (64, 512) 08-11 (64, 512) 12-15 (64, 512) Ports of Slot 10 -----------------------Port SID used DID used 0 0 0 1 0 0 2 0 0 3 0 0 4 0 0 5 0 0 6 0 0 7 0 0 8 0 0 9 0 0 10 0 0 11 0 0 12 0 0 13 0 0 14 0 0 15 0 0 -----------------------Quad ports (SID Free, DID Free) 00-03 (64, 512) 04-07 (64, 512) 08-11 (64, 512) 12-15 (64, 512)
2-162
portcfgshow
Available in Fabric OS versions: All Version Differences: Different versions of Fabric OS have additional outputs. Troubleshooting Use: Use this command to display port configuration settings. Use this command to display the current configuration of all ports. If no operand is specified, all the port configuration settings are displayed for that switch, or for the SilkWorm 12000 logical switch. The following configuration information is displayed (not all information the same in all FOS versions):
Speed mode is displayed as 1G, 2G, or AN (when in Auto speed Negotiation mode). This value is set by the portcfgspeed command. Trunk Port mode is displayed as ON when port is set for trunking or blank (..) when trunking is disabled on the port. This value is set by the portCfgTrunkport command. Long Distance mode is displayed as blank (..) when long distance mode is off, LE when the link is up to 10Km, LM when the link is up to 25Km, L1 when the link is up to 50Km, L2 when the link is up to 100Km or LD when the distance is to be determined dynamically. This value is set by the portCfgLongDistance command. VC Link Init mode (virtual channel) is displayed as blank (..) when the long distance link initialization option is turned off and (ON) when it is turned on for long distance mode. This value is set by the portcfglongdistance command. Locked L_Port mode is displayed as ON when port is locked to L_Port only or blank (..) when L_Port lock mode is disabled (and it behaves as a U_Port). This value is set by the portcfglport command. Locked G_Port mode is displayed as ON when port is locked to G_Port only or blank (..) when G_Port lock mode is disabled (and it behaves as a U_Port). This value is set by the portcfggport command. Disabled E_Port mode is displayed as ON when port is not allowed to be an E_Port or blank (..) when the port is allowed to function as an E_Port. This value is set by the portcfgeport command. Mcast LoopBack mode is displayed as blank (..) when Mcast LoopBack mode is off, and (ON) when Mcast LoopBack mode is enabled. This command allows a user to dedicate an unused port in a leaf (edge) switch, with no F_Port belonging to a multicast group, to receive multicast frames. This value is set by the portcfgmcastloopback command. ISL R_RDY Mode mode is displayed as ON when the port has been R_RDY mode enabled or blank (..) when the port is allowed to function as an E_Port. This value is set by the portcfgislmode command. Persistent Disable mode is displayed as ON when the port is disabled across reboots or power cycles or (..) when the port is allowed to function normally. This value is set by the portcfgpersistentdisable command. Disabled due to Buffer mode is displayed whenr the port is disabled due to lack of buffers. Value is set when available buffers in the associated quad are not enough to assign to this port which usually results from configuration of long distance ports in the quad. Will only displayed when giving the [SlotNumber/][PortNumber]. Refer to portCfgLongDistance more information. Locked Loop HD displays the half duplex mode 2 of this L_Port. Will only displayed when giving the [SlotNumber/][PortNumber]. Refer to portCfgLport for more information: mode2 - If mode2 is not present, it will be set to 0 by default. 1: The L_PORT will be a half-duplex L_PORT. 0: The L_PORT will be a full-duplex L_PORT.
Delay Flogi Shows that the portCfgDelayFlogi[slot_number/]port_number, retries (1-7 retries possible) command has been set on the port. This commands delays the FLOGI Accept for the port until routes are setup for the entire fabric. After a link disruption (caused by say, hafailover), certain hosts do not query the Name Server before re-establishing communication with the targets. If the host does not receive a response to its PLOGI, the I/Os that were in progress before the link disruption do not resume. By using this command, the user can specify the ports that have this behavior so that the switch will not send an FLOGI Accept until all routes are setup. That way after the link disruption, I/Os will resume.
2-163
Fabric OS SupportShow Information Example 2-43: v4.1 output
settings of ports in a SilkWorm 3900: switch:admin> portcfgshow Ports of Slot 0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 -----------------+--+--+--+--+----+--+--+--+----+--+--+--+----+--+--+-Speed AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN Trunk Port ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON Long Distance .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. VC Link Init .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Locked L_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Locked G_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Disabled E_Port .. ON .. .. .. .. .. .. .. .. .. .. .. .. .. .. Mcast LoopBack .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ISL R_RDY Mode .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Persistent Disable.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ports of Slot 0 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 -----------------+--+--+--+--+----+--+--+--+----+--+--+--+----+--+--+-Speed AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN Trunk Port ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON Long Distance .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. VC Link Init .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Locked L_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Locked G_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Disabled E_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Mcast LoopBack .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ISL R_RDY Mode .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Persistent Disable.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. where AN:AutoNegotiate, ..:OFF, ??:INVALID.
Example 2-44: v4.2 output

portcfgshow: Ports of Slot 1 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 -----------------+--+--+--+--+----+--+--+--+----+--+--+--+----+--+--+-Speed AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN Trunk Port ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON Long Distance .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. VC Link Init .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Locked L_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Locked G_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Disabled E_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ISL R_RDY Mode .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Persistent Disable.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Locked Loop HD .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Ports of Slot 3 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 -----------------+--+--+--+--+----+--+--+--+----+--+--+--+----+--+--+-Speed AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN AN Trunk Port ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON Long Distance .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. VC Link Init .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Locked L_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Locked G_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Disabled E_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ISL R_RDY Mode .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Persistent Disable.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. Locked Loop HD .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
<output truncated>
where AN:AutoNegotiate, ..:OFF, ??:INVALID.
2-164
portErrShow
Available in Fabric OS versions: All Troubleshooting Use: Use this command to display port error summary and troubleshoot marginal link problems. This command displays an error summary for all ports. One output line is displayed per port, and shows error counters in ones, thousands (the number is followed by k), or millions (the number is followed by m). The lines of the display show: Frames tx/rx N/A counters representing the number of frames transmitted. enc_in: 8bit/10bit encoding errors inside frame. Words inside of frames are encoded, if this encoding is corrupted or an error is detected enc_in is generated. crc_err: a mathematical formula generates counters at the sending port. The receiving port uses same formula to check and compare. Also see bad_eof below. too_long: too_short: FC frames are 2148 byes maximum. If an eof is corrupted or data generation is incorrect a too_long error is generated. The too_short is an error statistics counter which is incremented whenever a frame, bounded by an SOF and EOF, is received and the number of words between the SOF and EOF is less than 7 words (6 words header plus 1 word CRC), i.e., 38 bytes (not 48) including the SOF and EOF. This could be caused by the transmitter, or an unreliable link. After a loss-of-synchronization error continuous-mode alignment allows the receiver to reestablish word alignment at any point in the incoming bit stream while the receiver is Operational. Such realignment is likely (but not guaranteed) to result in Code Violations and subsequent loss of Synchronization. Under certain conditions, it may be possible to realign an incoming bit stream without loss of Synchronization. If such a realignment occurs within a received frame, detection of the resulting error condition is dependent upon higher-level function (e.g., invalid CRC, missing EOF Delimiter). 8bit/10bit encoding errors occurred in words (ordered sets) outside the FC frame. Words outside of frames are encoded, if this encoding is corrupted or an error is detected enc_out is generated. Discard class 3 errors could be generated by switch when devices send frames without FLOGIing first or with an invalid destination. This error is just reporting that such a discard occurred. If a Port remains in the LR Receive State for a period of time greater than a timeout period (R_T_TOV), a Link Reset Protocol Timeout shall be detected which results in a Link Failure condition (enter the NOS Transmit State). The link failure also indicates that loss of signal or loss of sync lasting longer than the R_T_TOV value was detected while not in the Offline state Synchronization failures on either bit or Transmission-Word boundaries are not separately identifiable and cause loss-of synchronization errors. Occurs when a signal is transmitted but none is being received on the same port. If the fabric cant process a Class 2 frame a F_RJT is returned. If fabric cant deliver a class 2 frame within E_D_TOV frame will be discarded and a F_BSY returned. Loss of Sync; Loss of Signal; Enc_Out Error are expected every time user brings the port down and up (reboot host, power-cycle storage subsystem, unplug/plug cable, or portdisable/portenable etc.)
bad_eof:
enc_out: Disc c3: Link fail:
Loss sync: Loss sig: Frjt: Frbsy: Note:
Example 2-84: The following example shows an eight port switch where port six has a high number of errors and should be examined:
sw5:admin> portErrShow frames enc crc too too bad enc disc link loss loss frjt fbsy tx rx in err shrt long eof out c3 fail sync sig -------------------------------------------------------------------------------0: 0 0 0 0 0 0 0 0 0 0 0 1 1: 2.5m 38 0 0 0 0 0 2 0 0 1 1 0
0 0
2-165
2
2: 3: 4: 5: 6: 7:

0 95k 0 0 61k 0 48 0 15k 0 0 2 0 0 0 0 0 15 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3k 0 0 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0 1 0 0 0 1 0 0 1 1 0 0 1 0 0 0 0 0 0 0 0 0 0
Example 2-85: Consistent trace eample:

portErrShow frames enc crc too too bad enc disc link loss loss frjt fbsy tx rx in err shrt long eof out c3 fail sync sig --------------------------------------------------------------------43m 107m 0 0 0 0 0 38 0 76 84 17 0 0 35m 107m 0 0 0 0 0 39 0 75 111 17 0 0 70m 29m 0 0 0 0 0 1.6k 0 9 5 9 0 0 10m 7.3m 0 0 0 0 0 95k 33 0 21 30 0 0 3.0m 2.0m 0 0 0 0 0 0 22 1 15 22 0 0 1.3m 859k 0 0 0 0 0 0 35 2 16 18 0 0 108m 36m 0 0 0 0 0 8 70 0 10 13 0 0 8.3m 5.0m 0 0 0 0 0 0 29 0 23 27 0 0 8.3m 5.0m 0 0 0 0 0 0 20 4 516 519 0 0 0 0 0 0 0 0 0 0 0 0 0 3 0 0 103k 69k 0 0 0 0 0 7 70 0 11 14 0 0 8.1m 4.8m 0 0 0 0 0 0 35 12 42 50 0 0 80m 10m 0 0 0 0 0 54 0 0 28 7 0 0 8.7m 20m 0 0 0 0 0 133 0 0 16 19 0 0 23m 46m 0 0 0 0 0 37 0 826 107 20 0 0 21m 47m 0 0 0 0 0 38 0 888 140 20 0 0
0: 1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15:
Statistical error depicted here could be since the last reboot and indicate devices being plugged in/ out and set up/ configuration work that occurred. Use portstatsclear <port #> to clear all the errors to the left of disc c3 on the same quad as specified port number. If the errors rapidly rise, look for a physical media problem. Statistically, enc_out errors alone imply cables, enc_out & crc_err combo implies GBIC/ SFP. If the error counters continue to rise, move cable to another port. If the problem follows the cable then suspect a faulty cable or attached media (GBIC/SFP/HBA and/or HBA driver). If the problem disappears, run crossporttest with a loopback plug in online/verbose mode to determine if the GBIC/SFP or port is faulty. Crossporttest, spinsilk and portloopback tests can also be run offline, internally looped to test port / ASIC. These statistical counters are based on the FC standards bit error rate (BER). Bit error rate of 10^-12 to 10^-15 ! At 10^-12 and 1Gbps, thats one bit error every 16 minutes ! At 10^-15 and 1Gbps, thats one bit error every 16,000 minutes (10 days) Note: Abnormally high ENC_OUT errors - It has been observed that during an ISL cable pull, the portErrShow for the port displays the Encoding Out errors in the millions. This situation occurs when a link is between a 1 Gb/sec port and an auto negotiate port. The reason is - when a port is capable to transmit at 2Gbps, the port register in the hardware is configured to 2 Gb/sec This register also controls the receiver speed. Therefore, when a 1Gbps signal is received and the speed negotiation is transmitting at 2 Gb/sec, this mismatch will generate lots of encoding-out errors. Therefore the 'enc-out' parameter can no longer be used to determine a potential marginal-link issue unless a baseline is established using portstatsclear command after speed negotiation occurs. There is no Auto-negotiation code in v2.x (it's a 1Gbit/sec only capable switch).
2-166

porterrshow: frames enc crc too too bad enc disc link loss loss frjt fbsy tx rx in err shrt long eof out c3 fail sync sig ===================================================================== 0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1: 1.3m 813k 0 0 0 0 0 1.3k 0 0 0 0 0 0 2: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5: 0 0 0 0 0 0 0 24 0 0 0 1 0 0 6: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 7: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 9: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 10: 0 0 0 0 0 0 0 0 0 0 0 1 0 0 11: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 12: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 13: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 14: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 15: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 16: 0 0 0 0 0 0 0 0 0 0 0 1 0 0 17: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 18: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 19: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 <OUTPUT TRUCATED> 121: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 122: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 123: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 124: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 125: 0 0 0 0 0 0 0 0 0 0 0 1 0 0 126: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 127: 576k 1.1m 0 0 0 0 0 145 0 0 0 0 0 0
2-167
portflagsshow
Available in Fabric OS versions: all Version Differences: This command behaves the same in all versions with one exception. Some versions do not have embedded port information (maximum port number +1). Troubleshooting Use: Use this command for the initialization state of the switch port The portFlagsShow command displays the initialization process that a switch port goes through (read from right to left) along with the port state and status of switch port. In the portFlagsShow output in the read out below shows the port going active (ACCEPT & LED), then it sees NOELP and the LOGIN process begins U_Port send out LIPs, if no response go through Fabric initialization process and become a G_Port, send out ELPs, if FLOGI received it become a F_Port. If the device is a private storage device it does not FLOGI put still registers a FLOGI to indicate it went through the process and timed out. In the case of a private storage. v3.0.2c Example Output:
portFlagsShow Port SNMP Physical Flags ------------------------------0: Online In_Sync PRESENT 1: Online In_Sync PRESENT 2: Online In_Sync PRESENT 3: Online In_Sync PRESENT 4: Online In_Sync PRESENT 5: Online In_Sync PRESENT 6: Online In_Sync PRESENT 7: Online In_Sync PRESENT 8: Online In_Sync PRESENT 9: Offline No_Light PRESENT 10: Online In_Sync PRESENT 11: Online In_Sync PRESENT 12: Online In_Sync PRESENT 13: Online In_Sync PRESENT 14: Online In_Sync PRESENT 15: Online In_Sync PRESENT 16: Online UNKNOWN PRESENT
ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE U_PORT ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE
E_PORT E_PORT F_PORT F_PORT F_PORT F_PORT F_PORT F_PORT F_PORT LED F_PORT F_PORT F_PORT F_PORT E_PORT E_PORT U_PORT
T_PORT T_PORT G_PORT G_PORT G_PORT G_PORT G_PORT G_PORT G_PORT G_PORT G_PORT G_PORT G_PORT T_PORT T_PORT
G_PORT U_PORT LOGIN LED T_MASTER G_PORT U_PORT LOGIN LED U_PORT LOGIN NOELP LED ACCEPT U_PORT LOGIN NOELP LED ACCEPT U_PORT LOGIN NOELP LED ACCEPT U_PORT LOGIN NOELP LED ACCEPT U_PORT LOGIN NOELP LED ACCEPT U_PORT LOGIN NOELP LED ACCEPT U_PORT LOGIN NOELP LED ACCEPT U_PORT LOGIN NOELP LED ACCEPT U_PORT LOGIN NOELP LED ACCEPT U_PORT LOGIN NOELP LED ACCEPT U_PORT LOGIN NOELP LED ACCEPT G_PORT U_PORT LOGIN LED T_MASTER G_PORT U_PORT LOGIN LED
Port 16 above represents the domain controller. The information depicted here is very much like switchshow port state information (online, in_syncF_Port L_Port = FL_Port or F_Port without the L_Port = F_Port). Here, like switchshow, you can see which port became the trunk master. What you also see here is the port initialization process as read from right to left. In the portFlagsShow output above, reading from right to left, you can see the port going active (ACCEPT & LED), then it sees NOELP and the LOGIN process begins U_Port send out LIPs, if no response go through Fabric initialization process and become a G_Port, send out ELPs, if FLOGI received it become a F_Port. If the device is a private storage device it does not FLOGI put still registers a FLOGI to indicate it went through the process and timed out. In the case of a private storage device, switch probes the device to get it into the name server. The information to the right of U_PORT is internal switch information.
2-168

portflagsshow: Slot Port SNMP Physical Flags -----------------------------------1 0 Offline No_Module PRESENT 1 1 Online In_Sync PRESENT 1 2 Offline No_Module PRESENT <trucated output> 8 12 Offline No_Module PRESENT 8 13 Offline No_Module PRESENT 8 14 Online In_Sync PRESENT 8 15 Offline No_Module PRESENT 9 0 Offline No_Module PRESENT 9 1 Offline No_Module PRESENT 9 2 Offline No_Module PRESENT 9 3 Offline No_Module PRESENT 9 4 Offline No_Light PRESENT 9 5 Offline No_Module PRESENT 9 6 Offline No_Module PRESENT 9 7 Offline No_Module PRESENT 9 8 Offline No_Module PRESENT 9 9 Offline No_Module PRESENT 9 10 Offline No_Light PRESENT 9 11 Offline No_Module PRESENT 9 12 Offline No_Module PRESENT 9 13 Offline No_Module PRESENT 9 14 Offline No_Module PRESENT 9 15 Offline No_Module PRESENT 10 0 Offline No_Module PRESENT 10 1 Offline No_Module PRESENT 10 2 Offline No_Light PRESENT 10 3 Offline No_Module PRESENT 10 4 Offline No_Module PRESENT 10 5 Offline No_Module PRESENT 10 6 Offline No_Module PRESENT 10 7 Offline No_Module PRESENT 10 8 Offline No_Module PRESENT 10 9 Offline No_Module PRESENT 10 10 Offline No_Module PRESENT 10 11 Offline No_Module PRESENT 10 12 Offline No_Module PRESENT 10 13 Offline No_Light PRESENT 10 14 Offline No_Module PRESENT 10 15 Online In_Sync PRESENT
U_PORT LED ACTIVE F_PORT G_PORT U_PORT LOGICAL_ONLINE LOGIN NOELP LED ACCEPT U_PORT LED U_PORT U_PORT ACTIVE U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT U_PORT ACTIVE LED LED F_PORT G_PORT U_PORT LOGICAL_ONLINE LOGIN NOELP LED ACCEPT LED LED LED LED LED LED LED LED LED LED LED LED LED LED LED LED LED LED LED LED LED LED LED LED LED LED LED LED LED LED LED LED F_PORT L_PORT U_PORT LOGICAL_ONLINE LOGIN NOELP LED ACCEPT
2-169
portLogDump
Available in Fabric OS versions: ALL Version Differences: Per logical switch - VxWorks switches have 1024 lines of output, Linux switches have 8000 lines. See the portlogdump reference guide for more information. Troubleshooting Use: The output of this command captures device to switch, switch to device and switch control information. Use the output to detect timeout problems, device bouncing on and off, protocol problems, misbehaving fabric devices, initialization problems, and marginal links. Because of the limited lines of entry you may have to clear the portlog before forcing a suspected device to log into the fabric. See the portlogdump reference guide for information about how to interpret the output. Portlogdump outputs can be disabled using the configure command. Note: See additional non-supportshow portlogshow along with the portlogdump decoding reference guide for additional information.
Use this command to display 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 returns between each page. If the port log is disabled, the following message appears as the first line (see portLogClear for details):
WARNING: port log is disabled

portlogdump time task event port cmd args ------------------------------------------------22:20:37.735 SPEE sn 10 WS 00000000,00000000,00000000 22:20:37.736 SPEE sn 10 WS 000000ee,00000000,00000000 22:20:37.746 SPEE sn 10 WS 00000001,00000000,00000000 22:20:38.016 SPEE sn 10 NC 00000002,00000000,00000001 22:20:38.017 LOOP loopscn 10 LIP 8002 22:20:38.027 LOOP loopscn 10 LIP f7f7 22:20:38.027 PORT Tx3 10 12 22000000,00000000,ffffffff,11010000 22:20:38.029 PORT Rx3 10 12 22000000,00000000,ffffffff,11010000 22:20:38.029 LOOP loopscn 10 LIM 0 22:20:38.029 PORT Tx3 10 20 22000000,00000000,ffffffff,11020000 22:20:38.030 PORT Rx3 10 20 22000000,00000000,ffffffff,11020000 22:20:38.030 PORT Tx3 10 20 22000000,00000000,ffffffff,11030000 22:20:38.037 PORT Rx3 10 20 22000000,00000000,ffffffff,11030000 22:20:38.037 PORT Tx3 10 20 22000000,00000000,ffffffff,11040000 22:20:38.039 PORT Rx3 10 20 22000000,00000000,ffffffff,11040000 22:20:38.039 PORT Tx3 10 20 22000000,00000000,ffffffff,11050100 22:20:38.040 PORT Rx3 10 20 22000000,00000000,ffffffff,11050100 22:20:38.041 LOOP loopscn 10 LIP 8017 22:20:38.047 LOOP loopscn 10 LIP f7f7 22:20:38.047 INTR pstate 10 LF2 22:20:38.051 INTR pstate 10 OL2 22:20:38.057 INTR pstate 10 LR3 22:20:38.057 INTR pstate 10 AC 22:20:38.057 PORT scn 10 11 22:20:38.186 PORT scn 10 1
<Output Truncated>
2-170
portloginshow
Available in Fabric OS versions: v4.1, v4.2 Troubleshooting Use: Use this command to display port login information. Use this command to display port login information. The portloginshow command logs 3 types of logings: fe = Fabric login to Fabric F_Port - end devices have to log into the fabric (FLOGI) before they can communicate to any other fabric end nodes; ff = PLOGI or port login after end devices FLOGI they will PLOGI into the Name Server then register information about themselves and if they are initiators they will also query for a list of fabric devices, initiators will also register to receive RSCNs using and SCR to the Fabric Controller (FFFFFD) after this PLOGI; fd=FDISK used when an initiator receives an RSCN and wants to determine the current state of the target that caused the RSCN. If current login session to target is valid, initiator can continue operations with affected target, if possible if not possible initiator can attempt to re-login to affected port. If login to affected port not possible initiator can implicitly log out of affected port thereby freeing resources. The lines of the diplay include: Type of login:
fe FLOGI, Fabric Login to Fabric F_Port. ff PLOGI, Process Login to specific N- Ports or well-known address like Name Server. fd FDISC, Virtual N_Port login. PID The port's 24-bit D_ID. WWN The port's Worldwide Name. credit The credit for this login as appropriate, this is BB (Buffer to Buffer) Credit for FLOGIs and EE (End to End) Credit for PLOGIs. df_sz The default frame size for this login. cos Class of Services supported. This can be a combination of the following bits. 8 Class of Service includes class 2. 10 Class of Service includes class 3.
There is further information about the login after the above columns. This can include the DID (Destination Identifier) that the port is logged on to. Example 2-46: :
switch:admin> portloginshow 23 Type PID World Wide Name credit df_sz cos ===================================================== fe 201700 21:00:00:e0:8b:05:a3:c9 3 2048 8 scr=1 ff 201700 21:00:00:e0:8b:05:a3:c9 0 0 8 d_id=FFFC20 ff 201700 21:00:00:e0:8b:05:a3:c9 0 0 8 d_id=FFFFFC
Note:
In the above example, port with decimal area 23 (HEX area 17) on domain 32 has logged into fffffe with a FLOGI to the F_port also called Fabric Login. Port 23 also did a PLOGI to FFFC20 (domain 32 embedded port also called switch id or domain controller) and FFFFFC (Name/Directory Server).
Example 2-88: Supportshow Example 2 (from v4.2 supportshow with host (slot1/port1) and then storage attached):
portloginshow 1 1: Type PID World Wide Name credit df_sz cos ===================================================== fe 010100 10:00:00:00:c9:29:06:7d 64 2048 c ff 010100 10:00:00:00:c9:29:06:7d 12 2048 c
scr=3 d_id=FFFFFC
2-171
2
Note:
Note that the device on slot 1, port 1(area 01), domain 1 has port logged into FFFFFC and done an SCR of type 3 (full registration): 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 (1 and 2)) Register to receive all RSCN requests issued by the Fabric Controller for events detected by the affected N_Port ID pages
portloginshow 10 15: Type PID World Wide Name credit df_sz cos ===================================================== fe 017fe8 21:00:00:20:37:15:18:08 0 2112 8 fe 017fe4 21:00:00:20:37:42:66:2d 0 2112 8 fe 017fdc 21:00:00:20:37:42:43:b1 0 2112 8 fe 017fd3 21:00:00:04:cf:62:04:b2 0 2112 8 fe 017fd5 21:00:00:04:cf:62:07:58 0 2112 8 fe 017fd4 21:00:00:04:cf:4c:ef:ee 0 2112 8 fe 017fd2 21:00:00:04:cf:62:0c:05 0 2112 8 fe 017fd1 21:00:00:04:cf:4c:e6:6b 0 2112 8 fe 017fda 21:00:00:20:37:15:0b:bc 0 2112 8 fe 017fe1 21:00:00:20:37:e6:8e:3e 0 2112 8 fe 017fe0 21:00:00:20:37:42:66:3e 0 2112 8 fe 017fd9 21:00:00:20:37:42:5f:da 0 2112 8 fe 017fd6 21:00:00:20:37:15:09:c3 0 2112 8 fe 017fe2 21:00:00:20:37:e6:9a:b9 0 2112 8 fe 017fef 21:00:00:20:37:e6:9a:cb 0 2112 8 ff 017fe8 21:00:00:20:37:15:18:08 0 0 8 ff 017fe4 21:00:00:20:37:42:66:2d 0 0 8 ff 017fdc 21:00:00:20:37:42:43:b1 0 0 8 ff 017fd3 21:00:00:04:cf:62:04:b2 0 0 8 ff 017fd5 21:00:00:04:cf:62:07:58 0 0 8 ff 017fd4 21:00:00:04:cf:4c:ef:ee 0 0 8 ff 017fd2 21:00:00:04:cf:62:0c:05 0 0 8 ff 017fd1 21:00:00:04:cf:4c:e6:6b 0 0 8 ff 017fda 21:00:00:20:37:15:0b:bc 0 0 8 ff 017fe1 21:00:00:20:37:e6:8e:3e 0 0 8 ff 017fe0 21:00:00:20:37:42:66:3e 0 0 8 ff 017fd9 21:00:00:20:37:42:5f:da 0 0 8 ff 017fd6 21:00:00:20:37:15:09:c3 0 0 8 ff 017fe2 21:00:00:20:37:e6:9a:b9 0 0 8 ff 017fef 21:00:00:20:37:e6:9a:cb 0 0 8
d_id=FFFFFC d_id=FFFFFC d_id=FFFFFC d_id=FFFFFC d_id=FFFFFC d_id=FFFFFC d_id=FFFFFC d_id=FFFFFC d_id=FFFFFC d_id=FFFFFC d_id=FFFFFC d_id=FFFFFC d_id=FFFFFC d_id=FFFFFC d_id=FFFFFC
Note:
Note that each of the ALPAs on decimal area 127 (slot 10, port 10) did a fe type loging (FLOGI) along with an ff type login (PLOGI) to the name server (FFFFFC).
2-172
portRegshow
Available in Fabric OS versions: All Troubleshooting Use: This is primarily an internal use only command but there is a portion at the end of the output that have information useful to understand virtual credit and bb credit usage. Use when error messages indicate lack of buffer credits - check tx and rx buffer credits The first part of portregshow output is ASIC specific it shows ASIC registers at bit values. ASIC specifications needed to decipher. The output generated by transmit credit count (tcc) per VC and receive credit count (rcc) per VC could be useful. If the values (rcc and tcc) of associated ports are zero (as shown here), then either the port has not initialized (as in this case no device connected) or the buffer to buffer credit allocated to that port has been used up (there would be error messages in errdump output).
0x81010080: 0x81010090: tcc_vc rqc_vc 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Example 2-89:
portRegShow 0 0x81000000: chip_id 0x81000004: vc_mapping 0x8100000a: int_status 0x8100000e: vc_config 0x81000014: mem_bufline 0x8100001a: mem_offset 0x8100001e: quad_imask 0x81000024: lli_status 0x8100002c: lli_def 0x81000034: prescaler0 0x81000038: toc0 0x8100003c: toc_ctl 0x8100004c: flist_stat 0x8100005c: plist_stat 0x8100006c: aulist_stat 0x81000072: tfr_status 0x81000076: avail_mbuf 0x8100007c: lli_flag 0x810000a2: chip_no 0x810000a6: debug 0x810000ae: tcci 0x810000d0: fm_thrsh 0x810000d8: holdoff_toc 0x81000180: link_tblMsk 0x81002854: port2vc 0x810028a4: b_rdy_stat 0x810028ac: b_rdy_ctl 0x810028b8: button 0x810028bc: lcd 0x81002900: bzio_status 0x81002908: tstmode_ctl 0x81002910: lvbis_ctl0 0x81002918: lvbis_stat0 0x81002920: flare_data0 0x81002928: cam_pat0 0x81002c04: loop_config 0x81002c0c: loop_status 0x81002c14: loop_osctl 0x81002c1c: loop_lip 0x81002c24: tod1 0x81002c30: alpa_avail 0x81002c60: test_ctl 0x81002c68: more_n 0x81002c80: ram_test 0x81002c78: link_rt_tmr 0x104 0x81000002: port_config 0xa38 0x800 0x81000008: int_mask 0x274f 0x1020 0x8100000c: cmi_err 0x2 0xc0 0x81000010: buf_error 0x0 0xc620c62 0x81000018: mem_ctl 0x08000094 0xc 0x8100001c: port_ctl 0x0 0x400f 0x81000020: port_addr 0xb0000 0x140000 0x81000028: lli_ctl 0x80180 0x140000 0x81000030: lli_mask 0x319e0007 0x8 0x81000036: tod0 0x11d 0xb 0x8100003a: toc1 0xd 0x0 0x81000044: putq_stat 0xffffffff 0x2602bc 0x81000054: tolist_stat 0xffffffff 0xffffffff0x81000064: cflist_stat 0xb008b 0xffffffff0x81000070: tfr_ctl 0x2100 0x2100 0x81000074: min_free 0x72 0x1b4 0x81000078: cmi_stat 0x0 0x0 0x810000a0: quad_istat 0x0 0x0 0x810000a4: led 0x1 0x0 0x810000aa: fbpc 0x0 0x0 0 255 15 1 0x0 0x810000da: holdoff_fc 0x0 0xfff 0x81002850: r2t_qctl 0x1f980000 0x7df0b1a 0x810028a0: share_buf 0x52(82) 0x1f 0x810028a8: b_rdy_mask 0x0 0x0 0x810028b0: tachometer 0x42 0x400f 0x810028ba: Reset/NMI 0x0 0xd0 0x810028be: gbic 0x0 0x153 0x81002904: bzio_ctl 0x34153 0x0 0x8100290c: pll_ctl 0x1e 0x24 0x81002914: lvbis_ctl1 0x0 0x0 0x8100291c: lvbis_stat1 0x3000 0xfdb09ff40x81002924: flare_data1 0x6f18 0x0 0x8100292c: cam_pat1 0x0 0x0 0x81002c08: loop_ctl 0x0 0x1 0x81002c10: loop_imask 0x4 0xbc15f7f70x81002c18: lli_mrkpbe 0x5fff00 0xf7f7 0x81002c20: prescaler1 0xc000c 0x3 0x81002c28: piq_stat 0x0 00000000 00000000 00000000 00000000 0x6 0x81002c64: less_n 0x0 0x0 0x81002c78: link_rt_tmr 0x0 3030 3030 3030 3030 3030 3030 0030 0x0 0x81002c90: rtest_ctl 0x2b0300
2-173

rtest_addr rtest_wpat port_speed deskew_tmr epi1_stat epi2_stat listB_stat tfrq_perCtl r2tq_perCtl stat_csr flt_perStat phan_perSta rsv_mbfIsta frzfrm_bufn vc_xlCtl skew_tod frtrk_fail0 minstck_sta frmtrk_mode faildet_pct frtrk_ptSta listA frozen forward lun_offset1 grp_data frzfrm_cam frzfrm_did frzfrm_flt tcc_vc rqc_vc rct_vc rcc_vc desired_buf busy_buf alloc_buf busy_mini mini_alloc 0x0 0x81002c98: rtest_rpat 0x0 0x0 0x81002ca0: rtest_mask 0x0 0xfffb0x81002ca8: trunk_ctl 0x99 0x10 0x81002cb0: epi1_mask 0x11b 0x40 0x81002cb4: epi2_mask 0xf 0x0 0x81002cc4: listA_stat 0xffffffff 0xffffffff0x81002cdc: listD_stat 0xffffffff 0x1fff 0x81002ce2: tfrq_perSta 0x0 0x1f 0x81002ce6: r2tq_perSta 0x0 0x0 0x81002cec: flt_per_ctl 0x3f 0x0 0x81002cf4: phan_perCtl 0x7 0xc600 0x81002cfc: quad_ctl 0x0 0xff 0x81002d02: rsv_mbfImsk 0x0 0x89 0x81002d08: vc_xlTxptMd 0x0 0x0 0x81002d0e: vc_xlParam 0x0 0x1d43973 0x81002d14: time_stamp 0x7808434 0x0 0x81002d1c: frtrk_fail1 0x0 0xfff01ff 0x81002d24: faildet_ctl 0xf37 0x200 0x81002d28: frmtrk_ctl 0xffff 0x7 0x81002d2c: faildet_pst 0x0 0x0 0x81002d30: q_dbg_ctl 0x0 0x52f0 0x81005484: listB 0x7 0x78000 0x8100548c: discard 0x100100 0x282c08 0x810054a0: lun_offset0 0x40404040 0xff 0x810054a8: grp_update 0x0 0x1 0x810054b0: priority 0x7fffffff 0x9ffff 0x810054c4: frzfrm_sidf 0x80b0300 0xf0b00 0x810054cc: frzfrm_lun 0x7070707 0x300800 4 0 5 5 5 5 1 1 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 26 , embedded port: 2 1 , embedded port: 1 26 , embedded port: 2 2 , embedded port: 1 208, embedded port: 17
0x81002c94: 0x81002c9c: 0x81002ca4: 0x81002cac: 0x81002cb2: 0x81002cb6: 0x81002ccc: 0x81002ce0: 0x81002ce4: 0x81002ce8: 0x81002cf0: 0x81002cf8: 0x81002d00: 0x81002d04: 0x81002d0c: 0x81002d10: 0x81002d18: 0x81002d20: 0x81002d26: 0x81002d2a: 0x81002d2e: 0x81005480: 0x81005488: 0x81005490: 0x810054a4: 0x810054ac: 0x810054c0: 0x810054c8: 0x810054d0: 0x81000080: 0x81000090: 0x810000b0: 0x810000c0: 0x81002800: 0x81002820: 0x81002840: 0x81002860: 0x81002880:
What do the different fields at the end of this output mean? Port 0 of this trace is a non-trunk master trunk port. The bold items above represent Virtual channel allocations and buffer credit information for this non-trunk master port. There are 8 virtual channels (vcs), 0 7 that optimize communication across an ISL. The information to the right of *_vc above displays the current vc allocations for these virtual channels on this ISL. VC 0, the link control vc, is allocated 4 buffer credits and so on: Virtual credits are read in columns from left to right: VC0 = 0 VC1 = 1 VC2 = 2 VC3 = 2 VC4 = 2 VC5 = 2 VC6 = 3 VC7 = 3 Control - For Link Control Frames Control - For Class 2 ACKs and Link Control Frames Data Data Data Data Admin/housekeeping - For Multicast traffic Admin/housekeeping - For Broadcast traffic
Communication from ports across this ISL is assigned to VCs based on the last two bits of the middle byte of the 24-bit address. There are four possible combinations, 00, 01, 10 and 11. These correspond to VC2, 3, 4 and 5 respectively. tcc and rcc mean transmit credit counter and receive credit counter for each VC (Virtual Channel)
2-174
Fabric OS SupportShow Information rqc_vc mean receive credit queue ctr for each VC rct_vc mean receive credit clear threshold for each VC Desired_buff is the desired buffers for this port in this case 16, embedded port allocated 2 Busy_bufs represent link control buffers.
Alloc_buf represent the buffers actually allocated, there are 16 reserved buffers guaranteed to each port but because this is an E_Port 26 are allocated. Read the alloc_bufs parameter (Allocated Buffers) to determine the number of buffers allocated to each port in the quad. The first value is for the highest-numbered port in the quad, and the fourth value indicates the lowest-numbered port in the quad. In the example above, the ports for this quad (ports 8 through 11 on slot 7) each have 26 buffers allocated. Busy_mini buffers represent smaller/ back end buffers that are managed by the ASIC to make efficient buffer usage for small frames. There are multiple mini buffers in each full size buffer. The embedded port = 1 represents the smaller/ back end busy buffers allocated to the embedded port. Mini_alloc represent the actual number of smaller/ back end buffers allocated for this port and embedded port = 17 represents the smaller/ back end buffers allocated to the embedded port. How does it work? There are total of 112 full size frame buffers in each quad. The embedded port uses two of them so the firmware can send frames. Other link control functions use 2 more, also to process frames. Among those 108 buffers remaining, some of them are reserved for each port and the rest are shared by all. We reserve sixteen buffers for each F_Port or FL_Port (thats the bb credit we advertise). If all four ports in the chip are Fx_Ports then, sixty-four buffers are reserved for advertised bb credit value. The remaining forty-six buffers are shared among all ports. These reserved buffers are called Desired_buff. We reserve twenty-six buffers for each E_Port (distributed among eight virtual channels) so if all four ports in a chip are E_Port, then there are only two buffers that can be shared. When a frame arrives at the receiving port, the switch always tries to allocate a sharable buffer first. Once a sharable buffer is found for the frame, the switch returns the R_RDY immediately before the actual frame is consumed (i.e. sent out of the transmit port). In this way, non of the bb credit buffers are used, therefore more frames can be received than the actual bb credit value advertised before they are shipped out of the switch. If no sharable buffer can be found, then the switch consumes one of the reserved buffers to hold the frame. In this case, an R_RDY will not be sent back until that frame leaves the switch (i.e. buffer is released). v4.2 Example Output: Example 2-90: v4.2 output from host port (slot 1/ port 1) and storage port (slot 10/ port 15) associated with portlogin information in Example 2-88
portregshow 1 1: 0xd2d5f000: chip_id <output truncated> 0xd2d644d0: frzfrm_flt 0xd2d5f080: tcc_vc 0xd2d5f090: rqc_vc 0xd2d5f0b0: rct_vc 0xd2d5f0c0: rcc_vc 0xd2d61800: desired_bufs 0xd2d61820: busy_bufs 0xd2d61840: alloc_bufs 0xd2d61860: busy_mini 0xd2d61880: mini_allocated portregshow 0xd3ce34d0: 0xd3cde080: 0xd3cde090: 10 15: frzfrm_flt tcc_vc rqc_vc 02040xd2d5f002: port_config 00800000 0 0 0 0 0 0 1 1 1 0 0 0 0 0 16 0 0 1 0 0 16 0 0 2 0 0 128 0a3a
0 0 1 0 0 0 0 0 0
0 0 1 0 2 1 2 1 17
0 0 1 0
0 0 1 0
63 0 1 0
00800000 0 0 0 0 0 0
0 0
0 0
0 0
0 0
0 16
2-175

rct_vc rcc_vc desired_bufs busy_bufs alloc_bufs busy_mini mini_allocated 1 0 16 1 16 2 128 1 0 0 0 0 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 1 0 2 1 2 1 17 1 0 1 0 1 16
0xd3cde0b0: 0xd3cde0c0: 0xd3ce0800: 0xd3ce0820: 0xd3ce0840: 0xd3ce0860: 0xd3ce0880:
2-176
portRouteShow
Available in Fabric OS versions: All Troubleshooting Use: Use this command to display various routing tables for a port This command displays the port address ID and the following port routing tables contents: external unicast routing table: This table shows how a unicast frame will be routed to another switch element in the Fabric. The format of the output is a list of domain_number: ports_bitmap. The domain_number is the switch element number that a unicast frame can reach from the port_number port. The ports_bitmap contains all output port numbers, in bitmap hex format, that can forward unicast frames from port_number to domain_number. For any active port, this table contains at least one entry:
local_switch_domain_number: 0x10000
This is for routing unicast frames designated to the embedded port of the local switch element. internal unicast routing table: This table lists all ports in the local switch that a unicast frame can reach from port_number. The format for each entry is: destination_port: output_ports_bitmap. Since the destination_port is in the local switch, output_ports_bitmap usually only contains one bit whose bit position number represents the destination_port number. multicast routing table: This table shows how a multicast frame will be to the destination multicast group. The format of the output is a list of mcast_group_number: (mcast_group_id) ports_bitmap, where mcast_group_number if the multicast group number, mcast_group_id is the multicast frames destination ID, and the ports_bitmap is a hex bitmap of all output port numbers that can forward a multicast frame from the port_number to mcast_group_id. broadcast routing table: This is actually a bitmap, listing all ports that a received broadcast frame can reach. Bit 16 of the bitmap is always set so that the switch element will always receive broadcast frames. Example 2-91:
portRouteShow 0 port address ID: 0x0b0000 external unicast routing table: 7: 0x8000 11: 0x10000 17: 0x8000 internal unicast routing table: 1: 0x2 2: 0x4 3: 0x8 4: 0x10 5: 0x20 6: 0x40 7: 0x80 8: 0x100 10: 0x400 11: 0x800 12: 0x1000 13: 0x2000 multicast routing table: 0-255: (all mcast aliases) 0x8000 broadcast routing table: 0x10000
2-177
v4.2 Example Output: Example 2-92: v4.2 host (slot 1/ port 1) and storage (slot 10/ port 15) output associated withExample 2-88 and Example 2-90.
portrouteshow 1 1: port address ID: 0x010100 external unicast routing table: 1: 0x10000 (vc=0) internal unicast routing table: 1: 0x40 (vc=3) 94: 0x8 (vc=2) 127: 0x800 (vc=2) broadcast routing table: 0x10000
Note:
portrouteshow 1 1 and 10 15 both show internal routing from ports 1 and 127 respectively to ports 1, 94, and 127 on the same switch. Ports 1 and 64 have hosts attached, port 127 has a JBOD attached.
portrouteshow 10 15: port address ID: 0x017f00 external unicast routing table: 1: 0x10000 (vc=0) internal unicast routing table: 1: 0x200 (vc=4) 94: 0x4 (vc=4) 127: 0x1000 (vc=5) broadcast routing table: 0x10000
2-178
portSemShow
Available in Fabric OS versions: v3.0, v3.1, v3.1.2 Version Differences: v4.2 Example Output: N/A Additional Example/Case Studies: Troubleshooting Use: Use this command when experiencing sluggishness or timeout issues. Some tasks require one event to be finished before another begins (switch initialization process) and some require exclusive access because what is being processed directly affects related processes. For example: If something takes the port 0 semaphore to access the ASIC and there is an incoming frame to the ASIC at the same time, an interrupt is generated to try to get the port 0 semaphore to the ASIC. But the first task owns it, so a timeout value could be exceeded. To understand this focus on external behavior: If a device does a FLOGI, it expects and accepts back within a certain time period. Each initiated task has an associated time stamp. This time stamp difference must be less than E_D_TOV. Example 2-93: keeps a running log of semaphore information
portSemShow port 0: 1 p0sem max:150 tThad Id 0x102faf50 MUTEX tThad was blocked for 150 ms by tReceive (85) at 03:38:02.783 _vxTaskEntry + 0x10 (0x10731174) _portRxTask + 0x128 (0x10466c28) _bloomReceive + 0x5e8 (0x10495cc8) _bloomFault + 0x40 (0x1049fc00) _bloomTaskDelay + 0x18 (0x104a8ac8) _taskDelay + 0x98 (0x1077b8a8) tTransmit was blocked for 16 ms by tReceive (95) at 03:00:33.899 _vxTaskEntry + 0x10 (0x10731174) _portRxTask + 0x128 (0x10466c28) _bloomReceive + 0x64 (0x10495744) _iuMalloc + 0x14 (0x10559c24) _memAlloc + 0x164 (0x10571c54) _semTake + 0x48 (0x10779208) _semMTake + 0x138 (0x10779b98) port 1: 1 p1sem max:17 tReceive Id 0x102faec0 MUTEX tReceive was blocked for 17 ms by tThad (160) at 08:49:51.316 _vxTaskEntry + 0x10 (0x10731174) _thad + 0x84 (0x105bc414) _thaCheck + 0x74 (0x105bd2f4) _thCheck + 0x38 (0x105baf18) _eportAgentAreaValidAct + 0xe54 (0x1059a8c4) _portGet + 0x144 (0x105b8484) _portLESB + 0x34 (0x104751f4) _zoneStateShow + 0xc88 (0x10474258) owner: none queued_tasks: none
owner: none
queued_tasks: none
Note:
Notice that tTransmit was blocked for 17 ms by tRTZone. Make sure zoning updates are in place before data is transferred,.thus the semaphore.
owner: none queued_tasks: none
port 2: 1 p2sem max:17 tTransmit Id 0x102fae30 MUTEX tTransmit was blocked for 17 ms by tRTZone (128) at 21:27:49.766 _vxTaskEntry + 0x10 (0x10731174) _cfgRealTimeTask + 0x314 (0x10517094) _newZoneVerify + 0x11a4 (0x10524414) _portIoctl + 0x13c (0x104669cc)
2-179
_bloomIoctl + 0xf70 (0x104aea90) _filterZoneTokenFree + 0x1b8 (0x104c56a8) _portReTransmit + 0x80 (0x10467760) _mqWrite + 0x30 (0x105738f0) tTransmit was blocked for 17 ms by tRTZone (128) at 21:27:49.766 _vxTaskEntry + 0x10 (0x10731174) _cfgRealTimeTask + 0x314 (0x10517094) _newZoneVerify + 0x11a4 (0x10524414) _portIoctl + 0x13c (0x104669cc) _bloomIoctl + 0xf70 (0x104aea90) _filterZoneTokenFree + 0x1b8 (0x104c56a8) _portReTransmit + 0x80 (0x10467760) _mqWrite + 0x30 (0x105738f0)
<output truncated>
2-180
portShow
Available in Fabric OS versions: All Version Differences: Information varies with the switch model and port type. Additional Example/Case Studies: Troubleshooting Use: Use this command to display port status for a port The display shows: Field Descriptions portname portCFlags portFlags portType portState Online Offline Testing Faulty portPhys No_Card No_Light No_Sync In_Sync Laser_Flt Port_Flt Diag_Flt Lock_Ref portScn portId portWwn Distance Interrupts User assigned port name Port control flags. A bit map of port status flags. The ports type and revision numbers. / The type of ASIC and the revision # for same. 3.1 is loom ASIC rev 1, 4.1 is a Bloom ASIC rev 1. The ports SNMP state: - up and running - not online, portPhys gives details - running diagnostics - failed diagnostics The ports physical state: - no interface card present - the module is not receiving light - receiving light but out of sync - receiving light and in sync - module is signaling a laser fault - port marked faulty - port failed diagnostics - locking to the reference signal The ports last State Change Notification. The ports 24-bit D_ID. The ports Worldwide Name. The ports long distance level (see portCfgLongDistance) Total number of interrupts. / The total number of interrupts received - there are many different kinds of interrupts, such as LLI, processing required, timed-out, etc - anything needing CPU attention, but they are all dealt with differently Interrupts that are not counted elsewhere. Low-level interface (physical state, primitive seqs). Frames delivered for embedded N_Port processing. /Processing required list interrupts - number of received frames that cannot be processed by HW. Reasons can be due to invalid DID, SID, DID not in routing tables, invalid VC, class of service, etc. Frames which have timed out. Frames requiring translation. Frames returned from an unavailable transmitter.
No_Module - no module (GBIC or other) present
The first column of the display:
Unknown Lli Proc_rqrd
Timed_out Rx_flushed Tx_unavail
2-181
2
Overrun
Fabric OS SupportShow Information Free buffer available interrupts. Buffer overrun interrupts. Transmission suspended interrupts. Real Tx data parity errors.
Free_buffer Suspended Parity_err
2ndary_parity_err Secondary Tx data parity errors. These are not real Tx data parity errors but rather forced by the ASIC due to certain central memory errors so that the transmitter will abort the frame. This field will only be displayed when there are errors. CMI_bus_err Control message interface errors. The second column shows Link Error Status Block counters. The third column shows the number of F_RJTs and F_BSYs generated. For L_Ports, the third column also shows the number of LIPs received, number of LIPs transmitted, and the last LIP received. v4.2 Example Output: Example 2-47:
portshow 1 10: portCFlags: 0x1 ENABLED portFlags: 0x23805b PRESENT ACTIVE F_PORT G_PORT U_PORT LOGIN NOELP LED ACCEPT portType: 4.1 / The type of ASIC and the revision # for same. 3.1 is loom ASIC rev 1, 4.1 Bloom ASIC rev 1 and so on.
portState: 1Online portPhys: 6In_Sync portScn: 6F_Port
/ see Decoding Ref Guide Internal State Change Notification Table / see Decoding Ref Guide Internal State Change Notification Table / see Decoding Ref Guide Internal State Change Notification Table
portId: 010a00 portWwn: 20:0a:00:60:69:80:04:b2 portWwn of device(s) connected: 10:00:00:00:c9:2a:b6:3b Distance: normal Speed: N2Gbps Interrupts: 1751 Link_failure: Unknown: 18 Loss_of_sync: Lli: 43 Loss_of_sig: Proc_rqrd: 1690 Protocol_err: Timed_out: 0 Invalid_word: Rx_flushed: 0 Invalid_crc: Tx_unavail: 0 Delim_err: Free_buffer: 0 Address_err: Overrun: 0 Lr_in: Suspended: 0 Lr_out: Parity_err: 0 Ols_in: 2_parity_err: 0 Ols_out: CMI_bus_err: 0
12 1 1 0 0 0 0 1141 7 7 6 2
Frjt: Fbsy:
0 0
Note:
Note the high number of address errors, 1141. This is normal for a loop port or a port with a tape device but it is not normal for a port with an E or F_Port. These often, but not always represent a misbehaving device in the Fabric. If you suspect a problem look in the portlogdump for entries that show a device getting rejects. Because we are looking at a switch in a test environment it is probably OK.
Proc_rqrd counters might have occurred during the process of setting up the applications that will be running in this test environment. They indicate the number of received frames that cannot be processed by HW. Reasons can be due to invalid DID, SID, DID not in
routing tables, invalid VC, class of service, etc. If these continue to increment this customer could begin experiencing problems. v4.2 Example Output: Example 2-94: Examples from supportshow associated with Example 2-88, Example 2-90 and Example 2-92 where a host port is on slot 1/ port 1 and a storage (JBOD) port is on slot 10 / port 15:
portshow 1 1:
2-182

portName: portDisableReason: None portCFlags: 0x1 portFlags: 0x24b03 PRESENT ACTIVE F_PORT G_PORT U_PORT LOGICAL_ONLINE LOGIN NOELP LED ACCEPT portType: 4.0 portState: 1Online portPhys: 6In_Sync portScn: 6F_Port portId: 010100 portWwn: 20:01:00:60:69:80:2d:4a portWwn of device(s) connected: 10:00:00:00:c9:29:06:7d Distance: normal portSpeed: N2Gbps Interrupts: 39998 Link_failure: 0 Frjt: 0 Unknown: 0 Loss_of_sync: 0 Fbsy: 0 Lli: 0 Loss_of_sig: 0 Proc_rqrd: 39998 Protocol_err: 0 Timed_out: 0 Invalid_word: 0 Rx_flushed: 0 Invalid_crc: 0 Tx_unavail: 0 Delim_err: 0 Free_buffer: 0 Address_err: 0 Overrun: 0 Lr_in: 0 Suspended: 0 Lr_out: 0 Parity_err: 0 Ols_in: 0 2_parity_err: 0 Ols_out: 0 CMI_bus_err: 0 portshow 10 15: portName: portDisableReason: None portCFlags: 0x1 portFlags: 0x24b03 PRESENT ACTIVE F_PORT L_PORT U_PORT LOGICAL_ONLINE LOGIN NOELP LED ACCEPT portType: 4.0 portState: 1Online portPhys: 6In_Sync portScn: 6F_Port portId: 017f00 portWwn: 20:7f:00:60:69:80:2d:4a portWwn of device(s) connected: 21:00:00:20:37:15:18:08 21:00:00:20:37:42:66:2d 21:00:00:20:37:42:43:b1 21:00:00:04:cf:62:04:b2 21:00:00:04:cf:62:07:58 21:00:00:04:cf:4c:ef:ee NOTICE LOOP OUTPUT LISTS ALL PORT WWNS FOR ALL LOOP DEVICES 21:00:00:04:cf:62:0c:05 21:00:00:04:cf:4c:e6:6b 21:00:00:20:37:15:0b:bc 21:00:00:20:37:e6:8e:3e 21:00:00:20:37:42:66:3e 21:00:00:20:37:42:5f:da 21:00:00:20:37:15:09:c3 21:00:00:20:37:e6:9a:b9 21:00:00:20:37:e6:9a:cb Distance: normal portSpeed: N2Gbps Interrupts: 134 Link_failure: 0 Frjt: 0 Unknown: 4 Loss_of_sync: 0 Fbsy: 0 Lli: 3 Loss_of_sig: 0 Lip_in: 0 Proc_rqrd: 127 Protocol_err: 0 Lip_out: 1 Timed_out: 0 Invalid_word: 0 Lip_Freq_Cnt: 0 Rx_flushed: 0 Invalid_crc: 0 Tx_unavail: 0 Delim_err: 0 Free_buffer: 0 Address_err: 15
2-183

0 0 0 0 0 Lr_in: Lr_out: Ols_in: Ols_out: 0 0 0 0
Overrun: Suspended: Parity_err: 2_parity_err: CMI_bus_err:
Note:
Notice the address errors on this loop port -some address errors on a loop port are normal. Notice the last column of the output has Lip information - the number of Lips out should always be greater than the number of Lips in. If devices on the loop were Lipping then the number of Lips in would be greater than the number of Lips out which could be indicative of a problem with that loop device.
2-184
portstatsshow
Available in Fabric OS versions: v3.1, v4.1 v4.2 Example Output: N/A in supportshow Additional Example/Case Studies: Troubleshooting Use: Use this command to display port hardware statistics counters. Note: ptstatsshow is similar to portstatsshow output for v3.x switches. See portErrShow and portshow output information for additional information on parameters depicted. Here is an v3.x example output with some supporting information:
Example 2-48: v3.0:admin> portStatsShow 3

stat_wtx stat_wrx stat_ftx stat_frx stat_c2_frx stat_c3_frx stat_lc_rx stat_mc_rx stat_mc_to stat_mc_tx tim_rdy_pri tim_txcrd_z er_enc_in er_crc er_trunc er_toolong er_bad_eof er_enc_out er_disc_c3 open transfer opened starve_stop fl_tenancy nl_tenancy frame_nozone 29597 27003 1472 1545 0 1545 0 1 0 0 57 12 0 0 0 0 0 10 31 0 0 0 0 0 0 0 4-byte words transmitted 4-byte words received Frames transmitted Frames received Class 2 frames received Class 3 frames received Link control frames received Multicast frames received Multicast timeouts Multicast frames transmitted Time R_RDY high priority Time BB_credit zero Encoding errors inside of frames Frames with CRC errors Frames shorter than minimum Frames longer than maximum Frames with bad end-of-frame Encoding error outside of frames Class 3 frames discarded loop_open loop_transfer FL_Port opened tenancies stopped due to starvation number of times FL has the tenancy number of times NL has the tenancy frames rejected due to zone protection
Note:
Notice Time BB_Credit Zero. A high value could occur for many reasons: - HBA does not have enough buffers to be able to receive 1 Gbps traffic. - Disk may not be able to handle 1 Gbps data coming at it. Switch port is buffering the data while waiting for an r_rdy from disk. - May be congestion in the Fabric, if not enough ISLs are present to accommodate the traffic that is being sent through.
If you invoke portstatsshow, you will see all portstatsshow outputs for all ports on the switch. Portstatsshow <port #> displays only one port. Pay attention to: enc, crc, trunc, toolong bad_eof; enc_out, er_disc. Unlike portShow and portErrShow outputs, the counters that generated portstatsshow statistics occur between and on interrupts. Note: Start looking at these errors if you see the enc out going from 100, to 200, and to 300 (quickly rising values). You should see considerably less than 5% tx plus rx counters on any statistic. These errors are based on a BER (bit error rate) of 10 to the minus 12 rate for all the error commands. These BERs generate error statistics when exceeded. Unless they get really bad, they often cause timeouts in the Fabric. We recommend using Fabric Watch to monitor these error statistics, as these problems may cause production outages or slowdowns.
2-185
portstructshow
Note:
Implementation specific command useful to check ALPAs
Available in Fabric OS versions: v3.0, v3.1, v3.1.2 - All VxWorks switches v4.2 Example Output: NA Additional Example/Case Studies: Troubleshooting Use: Use this command to Example 2-95:
portStructShow 0 Pt 0: port_t struct p_flags:0x14028057 PRESENT ACTIVE E_PORT T_PORT G_PORT U_PORT LOGIN LED p_lb_mode:0x0 p_type:0x4 p_rev:0x1 p_state:0x1 p_phstate:0x6 p_scn:0x5 p_phscn:0x1 p_tick:0xa p_cbl_lb:0x0 p_led:0x4 p_led_state:0x4 p_ie_fctl_mode:0x1 p_distance:0x0 p_speed:0x00000002 p_master:0x00000001 p_mcast_lb:0x00000000 p_regs:0x81000000 p_data:0x101e8b30 p_id:0x000b0000 p_wwn:20:00:00:60:69:51:3a:ba p_sem:1 p0sem max:150 tThad Id 0x102faf50 MUTEX owner:none queued_tasks:none tThad was blocked for 150 ms by tReceive (85) at 03:38:02.783 _vxTaskEntry + 0x10 (0x10731174) _portRxTask + 0x128 (0x10466c28) _bloomReceive + 0x5e8 (0x10495cc8) _bloomFault + 0x40 (0x1049fc00) _bloomTaskDelay + 0x18 (0x104a8ac8) _taskDelay + 0x98 (0x1077b8a8) tTransmit was blocked for 16 ms by tReceive (95) at 03:00:33.899 _vxTaskEntry + 0x10 (0x10731174) _portRxTask + 0x128 (0x10466c28) _bloomReceive + 0x64 (0x10495744) _iuMalloc + 0x14 (0x10559c24) _memAlloc + 0x164 (0x10571c54) _semTake + 0x48 (0x10779208) _semMTake + 0x138 (0x10779b98) plogi_t:0x0 p_phntm:0x0 p_devbmp:0x00000000, 0x00000000, 0x00000000, 0x00000000 p_newbmp:0x00000000, 0x00000000, 0x00000000, 0x00000000 p_nocbmp:0x00000000, 0x00000000, 0x00000000, 0x00000000 p_prbbmp:0x00000000, 0x00000000, 0x00000000, 0x00000000 p_fcpbmp:0x00000000, 0x00000000, 0x00000000, 0x00000000
2-186

p_tobmp: 0x00000000, 0x00000000, 0x00000000, 0x00000000 p_pfbmp: 0x00000000, 0x00000000, 0x00000000, 0x00000000 p_prbtc:0x0 p_x_num:0x0 p_x_use:0x0 p_x_acc:0x0 p_x_els:0x0 p_iu_fst:0x0 p_iu_lst:0x0 p_wdtx:0x34ae4c93 p_wdrx:0x6520dc91 p_wtot:0x99cf2bae p_rxperf:0x0000034c p_txperf:0x00000be4 p_c1ac:0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 p_c2ac:0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 p_c3ac:0x0660d233 0x0025fe67 0x000009d8 0x00000000 0x00000000 p_errs:0x0000004c 0x00000054 0x00000011 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000028 0x00000012 0x00000012 0x0000004c p_flers:0x00000000 0x00000041 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0xf7f7 p_ints:0x0007b367 0x000000cf 0x000001de 0x0007b15c 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 p_conf:0x20 0x6 0xc 0x6 0x1 0x0 0x1 0x1 0x10 0x8 0x1 0x0 0x0 0x0010 0x0840 0x00002710 0x000007d0 0x10313010 0xc8 p_oper:0x00000000 0x0 0x00000000 0x00000010 p_flog:0x0 0x0 0x0 0x0 0x0 0x0 0x0000 0x0000 p_phys:0x0 0x0 0x0 0x00000000 p_cap:0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 p_gstats:0x34a4e505 0x651f63cf 0x0290a972 0x0661f869 0x00000000 0x0660d233 0x00009496 0x00000000 0x0001c665 0x00000043 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000026 0x00000000 0x00000000 0x00000000 0x00000000 state_trans_no:0x00000041 p_rtstate:0x0
2-187
portswapShow
Available in Fabric OS versions: V4.2 is the only Fabric OS version with portswapshow in supportshow output Troubleshooting Use: Use this command to display when ports have been swapped. Port swapping is a feature required by FICON but can be enabled for any Bloom ASIC port in the fabric after v3.1/4.1. Additional Example/Case Studies: Here we see an example where portswapping is enabled, ports that are going to be swapped are disabled and then ports are swapped, portswapshow depicts the swapped condition. Example 2-96: portswapping
s3900_9:admin> portswapenable s3900_9:admin> portdisable 30 s3900_9:admin> portdisable 29 s3900_9:admin> portswap 30 29 portswap done s3900_9:admin> portswapshow PortSwap is enabled Port Area ==================== 29 30 30 29

portswapshow: portswap feature is not enabled No ports have been swapped
2-188
portzoneShow
Troubleshooting Use: Use this command to determine port zone enforcement. This command can also be used along with cfgsize, cfgshow and zone stateshow commands to troubleshoot zoning problems. Available in Fabric OS versions: v4.1, v4.2 Version Differences: None, this command is available at CLI on all Bloom ASIC switches. Additional Example/Case Studies: Portzoneshow output depicts hard, soft and session-based enforced, has to do with how zoning is configured. In bloom ASICs all zones defined using WWNs or domain, area are hard enforced. Hard enforced means that communication to the device on the target port is blocked if not in the same zone as communicating device. All devices should go to the name server (directory server) to determine who they can communicate with in the Fabric. Some devices, called bad citizens, attempt communication with devices not in same zone even after name server communication. If target is in a hard defined zone then communication to that target will be blocked on the ASIC port. Session-based enforced zoning occurs on Bloom ASICs when mixed zones are created (a mix of WWN and domain, area in the same zone). Session-based zoning enforcement is only available in Bloom ASIC switches - in Bloom based switches mixed zone elements will go session based before they go soft-enforced (until available ASIC memory runs out). Session based enforcement blocks PLOGIs at the destination port. End devices in a fabric cannot communicate before they PLOGI into each other. Soft enforced zoning means devices still query the name server for a list of accessible devices but can communicate with them, even if they are not in the same zone, if soft enforced. Soft enforcement could also occur if ASIC zone memory is close to saturation. In a mixed Fabric, Loom and Bloom ASICs soft enforced or session enforced zoning occurs per Bloom ASIC rules defined above on Bloom ports but devices become soft enforced on Loom ASICs when defined using all WWNs. Note: See portcamshow and zone stateshow story notes for a better understanding of portzoneshow output
Note:
For portZoneShow, "defaultHard 0" means that the port is either: (a) not an F-port and therefore does not have a zone type, or (b) the port is an F-port and has a regular zone type of one of {HARD WWN, HARD PORT, SESSION BASED HARD}. When you see "defaultHard 1", it means the port is not zoned with any one else.
Example 2-98: list switch ports and zone enforcement policy in use.
portzoneshow: PORT: 0 Not Zoned PORT: 1 Enforcement: HARD WWNdefaultHard: 0F-port: 0 PORT: 2 Not Zoned PORT: 3 Not Zoned PORT: 4 Enforcement: E-PortdefaultHard: 0F-port: 0 PORT: 5 Enforcement: E-PortdefaultHard: 0F-port: 0 PORT: 6 Not Zoned PORT: 7 Not Zoned PORT: 8 Not Zoned PORT: 9 Not Zoned PORT: 10 Not Zoned PORT: 11 Enforcement: HARD WWNdefaultHard: 0F-port: 1 PORT: 12 Not Zoned PORT: 13 Not Zoned PORT: 14 Not Zoned PORT: 15 Not Zoned PORT: 16 Not Zoned PORT: 17 Not Zoned PORT: 18 Not Zoned PORT: 19 Not Zoned PORT: 20 Not Zoned PORT: 21 Not Zoned PORT: 22 Not Zoned PORT: 23 Not Zoned PORT: 24 Not Zoned
2-189

25 26 27 28 29 30 31 Not Zoned Not Zoned Not Zoned Not Zoned Not Zoned Not Zoned Enforcement: HARD WWNdefaultHard: 0F-port: 1
PORT: PORT: PORT: PORT: PORT: PORT: PORT:
2-190
printing proc entries

Available in Fabric OS versions: All v4.x supportshow outputs Troubleshooting Use: Use this command to list all devices, with information about each. Note: This shows you what the OS (Linux) sees at a hardware level. This kind of info would be useful when the CP will boot but will not access a specific device or possibly when a driver will not load because a device cannot be found. Devices include all hardware...PCI, RAM, CPU etc.
Additional Example/Case Studies: Example 2-49:

printing proc entries /proc/cmdline mem=127m /proc/cpuinfo processor: 0 cpu : 405GP clock: 200MHz revision: 1.69 (pvr 4011 0145) bogomips: 199.47 zero pages: total: 0 (0Kb) current: 0 (0Kb) hits: 0/0 (0%) plb bus clock: 100MHz pci bus clock: 33MHz /proc/devices Character devices: 1 mem 2 pty 3 ttyp 4 ttyS 5 cua 10 misc 89 i2c 90 mtd 128 ptm 136 pts 162 raw 240 ham 241 fmf 245 swd 248 pcidma 249 fc 250 fc-switch 251 fabsys 252 portlog 253 pcmcia 254 platform Block devices: 1 ramdisk 3 ide0 7 loop 43 nbd /proc/filesystems nodevsockfs nodevshm nodevpipefs nodevproc ext2 nodevramfs nodevautofs xfs
2-191
nodevnfs nodevdevpts nodevdfs /proc/interrupts CPU0 1: 1089 2: 2677332 9: 0 10: 0 11: 34898 12: 117701 13: 0 14: 0 15: 0
405GP 405GP 405GP 405GP 405GP 405GP 405GP 405GP 405GP
UIC UIC UIC UIC UIC UIC UIC UIC UIC
Edge Edge Edge Edge Edge Edge Edge Edge Edge
serial PPC405 405eth 405eth 405eth 405eth 405eth 405eth 405eth
IIC Wakeup MAL SERR TX EOB RX EOB TX DE RX DE MAC
< Output Truncated > v4.2 Example Output: Example 2-99:

printing proc entries /proc/cmdline: quiet /proc/cpuinfo: cpu : 440GP Rev. C clock : 466MHz revision: 4.129 (pvr 4012 0481) bogomips: 699.59 machine : Brocade Silkworm440 plb bus clock: 133MHz pci bus clock: 33MHz uart clock: 687KHz (external) /proc/devices: Character devices: 1 mem 2 pty 3 ttyp 4 ttyS 5 cua 10 misc 89 i2c 90 mtd 128 ptm 136 pts 162 raw 244 swd 245 ham 246 fc 247 fc-switch 248 fabsys 249 fss_kt 250 fss_data 251 fss_mgmt 252 portlog 253 platform 254 mem_page Block devices: 1 ramdisk 3 ide0 7 loop
2-192

/proc/filesystems: nodevrootfs nodevbdev nodevproc nodevsockfs nodevtmpfs nodevshm nodevpipefs ext3 ext2 nodevramfs nodevnfs nodevdevpts xfs nodevdfs /proc/interrupts: CPU0 0: 2 IBM 1: 1043 IBM 2: 27 IBM 3: 9175366 IBM 10: 228467 IBM 11: 357092 IBM 23: 1 IBM 24: 40000 IBM 25: 0 IBM 27: 4 IBM 28: 0 IBM 29: 0 IBM 32: 0 IBM 33: 0 IBM 34: 0 IBM 50: 370735 IBM FIT: 146 PIT: 10372654 BAD: 0 /proc/meminfo: total: Mem: 262119424 Swap: 0 MemTotal: MemFree: MemShared: Buffers: Cached: SwapCached: Active: Inactive: HighTotal: HighFree: LowTotal: LowFree: SwapTotal: SwapFree: /proc/modules: dubby-module swd-module ham-module fc-module bloom-module blade-module switch-module
UIC UIC UIC UIC UIC UIC UIC UIC UIC UIC UIC UIC UIC UIC UIC UIC
Cascade Cascade Cascade Cascade Cascade Cascade Cascade Cascade Cascade Cascade Cascade Cascade Cascade Cascade Cascade Cascade
Level Level Level Level Level Level Level Level Level Level Level Level Level Level Level Level
serial serial IBM OCP IIC IBM OCP IIC TX EOB (eth0), TX EOB (eth1) RX EOB (eth0), RX EOB (eth1) pb_change pb_attn cp_change cp_attn core_attn pb_pwr_fail SERR (eth0), SERR (eth1) TX DE (eth0), TX DE (eth1) RX DE (eth0), RX DE (eth1) ide0
used: free: shared: buffers: cached: 184524800 77594624 0 118784 110329856 0 0 255976 kB 75776 kB 0 kB 116 kB 107744 kB 0 kB 25292 kB 113496 kB 0 kB 0 kB 255976 kB 75776 kB 0 kB 0 kB
623794 34673 24460 207035 707943 247423 3367175
2 23 10 21 0 0 22
[swd-module] [dubby-module] [dubby-module swd-module ham-module fc-module] [bloom-module] [dubby-module fc-module bloom-module blade-module]
2-193
iu 10634 0 [dubby-module fc-module bloom-module blade-module switch-module] fabsys-module 86555 25 [dubby-module bloom-module blade-module switch-module iu] fss-module 122639 21 [dubby-module fc-module switch-module] tp-module 40623 0 [bloom-module switch-module fss-module] portlog-module 81483 0 [dubby-module swd-module ham-module fc-module bloom-module blade-module switch-module fabsys-module fss-module] hameteor-module 15977 2 [ham-module fss-module] meteor-module 572422 20 [dubby-module swd-module ham-module fc-module bloom-module blade-module switch-module fabsys-module portlog-module hameteor-module] fablog-module 21542 0 [dubby-module swd-module ham-module fc-module bloom-module blade-module switch-module iu fabsys-module fss-module tp-module portlog-module hameteor-module meteor-module] db-module 32753 0 [hameteor-module meteor-module] dfs 5426 1 [dubby-module] consolelog-module 8203 0 (unused) panicdump-module 15023 0 [swd-module switch-module portlog-module meteor-module consolelog-module] xfsnotificationhandler 4858 0 (unused) /proc/mounts: rootfs / rootfs rw 0 0 dev/hda1 / xfs rw,noatime 0 0 /proc /proc proc rw 0 0 none /dev/pts devpts rw 0 0 none /tmp ramfs rw 0 0 /dev/hda2 /mnt xfs rw,noatime 0 0 /diag /diag dfs rw 0 0 /proc/mtd: dev: size mtd0: 00010000 mtd1: 00060000 mtd2: 00800000 mtd3: 00400000 mtd4: 00400000 mtd5: 00800000 mtd6: 00400000 mtd7: 00400000
erasesize name 00010000 "boot environment" 00010000 "boot prom" 00020000 "User flash 1" 00020000 "kernel and initrd (1)" 00020000 "log data (1)" 00020000 "User flash 2" 00020000 "Kernel and initrd (2)" 00020000 "log data (2)"
/proc/partitions: major minor #blocks 3 3 3 0 1 2
name
250880 hda 124912 hda1 124928 hda2
/proc/pci: PCI devices found: Bus 0, device 0, function 0: Bridge: PCI device 1014:01ef (IBM) (rev 1). Bus 0, device 1, function 0: Bridge: PCI device 8086:b555 (Intel Corp.) (rev 3). IRQ 26. Non-prefetchable 32 bit memory at 0x40000000 [0x43ffffff]. I/O at 0x1400 [0x14ff]. Non-prefetchable 32 bit memory at 0x48000000 [0x4fffffff]. Non-prefetchable 32 bit memory at 0x50000000 [0x5fffffff]. Non-prefetchable 32 bit memory at 0x60000000 [0x6fffffff]. Bus 0, device 2, function 0: Bridge: PCI device 8086:b555 (Intel Corp.) (rev 3). IRQ 26. Non-prefetchable 32 bit memory at 0x70000000 [0x73ffffff]. I/O at 0x1000 [0x10ff]. Non-prefetchable 32 bit memory at 0x78000000 [0x7fffffff]. Non-prefetchable 32 bit memory at 0x80000000 [0x8fffffff]. Non-prefetchable 32 bit memory at 0x90000000 [0x9fffffff]. Bus 0, device 3, function 0:
2-194

Bridge: PCI device 8086:b555 (Intel Corp.) (rev 3). IRQ 26. Non-prefetchable 32 bit memory at 0xa0000000 [0xa3ffffff]. I/O at 0x2000 [0x20ff]. Non-prefetchable 32 bit memory at 0xa8000000 [0xafffffff]. Non-prefetchable 32 bit memory at 0xb0000000 [0xbfffffff]. Non-prefetchable 32 bit memory at 0xc0000000 [0xcfffffff]. Bus 0, device 4, function 0: IDE interface: CMD Technology Inc PCI0649 (rev 2). IRQ 50. Master Capable. Latency=64. Min Gnt=2.Max Lat=4. I/O at 0x3000 [0x3007]. I/O at 0x4000 [0x4003]. I/O at 0x5000 [0x5007]. I/O at 0x6000 [0x6003]. I/O at 0x7000 [0x700f]. Bus 1, device 14, function 0: PCI bridge: PCI device 104c:ac28 (rev 0). Bus 11, device 0, function 0: Non-VGA unclassified device: PCI device 1657:0001 (rev 0). IRQ 26. Non-prefetchable 32 bit memory at 0x48000000 [0x4807ffff]. Bus 11, device 1, function 0: Non-VGA unclassified device: PCI device 1657:0001 (rev 0). IRQ 26. Non-prefetchable 32 bit memory at 0x48080000 [0x480fffff]. Bus 11, device 2, function 0: Non-VGA unclassified device: PCI device 1657:0001 (rev 0). IRQ 26. Non-prefetchable 32 bit memory at 0x48100000 [0x4817ffff]. Bus 11, device 3, function 0: Non-VGA unclassified device: PCI device 1657:0001 (rev 0). IRQ 26. Non-prefetchable 32 bit memory at 0x48180000 [0x481fffff]. Bus 1, device 15, function 0: PCI bridge: PCI device 104c:ac28 (rev 0). Bus 21, device 0, function 0: Non-VGA unclassified device: PCI device 1657:0001 (rev 0). IRQ 26. Non-prefetchable 32 bit memory at 0x50000000 [0x5007ffff]. Bus 21, device 1, function 0: Non-VGA unclassified device: PCI device 1657:0001 (rev 0). IRQ 26. Non-prefetchable 32 bit memory at 0x50080000 [0x500fffff]. Bus 21, device 2, function 0: Non-VGA unclassified device: PCI device 1657:0001 (rev 0). IRQ 26. Non-prefetchable 32 bit memory at 0x50100000 [0x5017ffff]. Bus 21, device 3, function 0: Non-VGA unclassified device: PCI device 1657:0001 (rev 0). IRQ 26. Non-prefetchable 32 bit memory at 0x50180000 [0x501fffff]. Bus 1, device 17, function 0: PCI bridge: PCI device 3388:0022 (rev 4). Bus 41, device 0, function 0: Non-VGA unclassified device: PCI device 1657:0001 (rev 0). IRQ 26. Non-prefetchable 32 bit memory at 0x60000000 [0x6007ffff]. Bus 41, device 1, function 0: Non-VGA unclassified device: PCI device 1657:0001 (rev 0). IRQ 26. Non-prefetchable 32 bit memory at 0x60080000 [0x600fffff]. Bus 41, device 2, function 0: Non-VGA unclassified device: PCI device 1657:0001 (rev 0). IRQ 26.
2-195

at 0x60100000 [0x6017ffff]. device 1657:0001 (rev 0). at 0x60180000 [0x601fffff]. (rev 2). device 1657:0001 (rev 0). at 0xa8000000 [0xa807ffff]. device 1657:0001 (rev 0). at 0xa8080000 [0xa80fffff]. device 1657:0001 (rev 0). at 0xa8100000 [0xa817ffff]. device 1657:0001 (rev 0). at 0xa8180000 [0xa81fffff]. device 1657:0001 (rev 0). at 0xa8200000 [0xa827ffff]. device 1657:0001 (rev 0). at 0xa8280000 [0xa82fffff]. device 1657:0001 (rev 0). at 0xa8300000 [0xa837ffff]. device 1657:0001 (rev 0). at 0xa8380000 [0xa83fffff]. (rev 2). device 1657:0001 (rev 0). at 0xb0000000 [0xb007ffff]. device 1657:0001 (rev 0). at 0xb0080000 [0xb00fffff]. device 1657:0001 (rev 0). at 0xb0100000 [0xb017ffff]. device 1657:0001 (rev 0). at 0xb0180000 [0xb01fffff]. device 1657:0001 (rev 0). at 0xb0200000 [0xb027ffff]. device 1657:0001 (rev 0). at 0xb0280000 [0xb02fffff].
Non-prefetchable 32 bit memory Bus 41, device 3, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 129, device 14, function 0: PCI bridge: PCI device 104c:ac28 Bus 139, device 0, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 139, device 1, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 139, device 2, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 139, device 3, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 139, device 4, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 139, device 5, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 139, device 6, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 139, device 7, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 129, device 15, function 0: PCI bridge: PCI device 104c:ac28 Bus 149, device 0, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 149, device 1, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 149, device 2, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 149, device 3, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 149, device 4, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 149, device 5, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory
2-196

Bus 149, device 6, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 149, device 7, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 65, device 14, function 0: PCI bridge: PCI device 104c:ac28 Bus 75, device 0, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 75, device 1, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 75, device 2, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 75, device 3, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 65, device 15, function 0: PCI bridge: PCI device 104c:ac28 Bus 85, device 0, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 85, device 1, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 85, device 2, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 85, device 3, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 65, device 16, function 0: PCI bridge: PCI device 104c:ac28 Bus 95, device 0, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 95, device 1, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 95, device 2, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 95, device 3, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 65, device 17, function 0: PCI bridge: PCI device 104c:ac28 Bus 105, device 0, function 0:
device 1657:0001 (rev 0). at 0xb0300000 [0xb037ffff]. device 1657:0001 (rev 0). at 0xb0380000 [0xb03fffff]. (rev 0). device 1657:0001 (rev 0). at 0x78000000 [0x7807ffff]. device 1657:0001 (rev 0). at 0x78080000 [0x780fffff]. device 1657:0001 (rev 0). at 0x78100000 [0x7817ffff]. device 1657:0001 (rev 0). at 0x78180000 [0x781fffff]. (rev 0). device 1657:0001 (rev 0). at 0x80000000 [0x8007ffff]. device 1657:0001 (rev 0). at 0x80080000 [0x800fffff]. device 1657:0001 (rev 0). at 0x80100000 [0x8017ffff]. device 1657:0001 (rev 0). at 0x80180000 [0x801fffff]. (rev 0). device 1657:0001 (rev 0). at 0x88000000 [0x8807ffff]. device 1657:0001 (rev 0). at 0x88080000 [0x880fffff]. device 1657:0001 (rev 0). at 0x88100000 [0x8817ffff]. device 1657:0001 (rev 0). at 0x88180000 [0x881fffff]. (rev 0).
2-197

device 1657:0001 (rev 0). at 0x90000000 [0x9007ffff]. device 1657:0001 (rev 0). at 0x90080000 [0x900fffff]. device 1657:0001 (rev 0). at 0x90100000 [0x9017ffff]. device 1657:0001 (rev 0). at 0x90180000 [0x901fffff].
Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 105, device 1, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 105, device 2, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory Bus 105, device 3, function 0: Non-VGA unclassified device: PCI IRQ 26. Non-prefetchable 32 bit memory /proc/slabinfo: slabinfo - version: 1.1 kmem_cache 77 102 ip_mrt_cache 0 0 tcp_tw_bucket 2 40 tcp_bind_bucket 10 113 tcp_open_request 0 59 inet_peer_cache 1 59 ip_fib_hash 17 113 ip_dst_cache 43 72 arp_cache 4 30 blkdev_requests 128 160 xfs_chashlist 239 404 xfs_ili 5807 5824 xfs_ifork 0 0 xfs_efi_item 0 12 xfs_efd_item 0 12 xfs_buf_item 0 52 xfs_dabuf 0 202 xfs_da_state 0 10 xfs_trans 0 84 xfs_inode 7326 7326 xfs_btree_cur 0 27 xfs_bmap_free_item 0 202 page_buf_t 8 180 page_buf_reg_t 2 113 avl_object_t 2 113 avl_entry_t 2 226 nfs_write_data 0 0 nfs_read_data 0 0 nfs_page 0 0 journal_head 0 0 revoke_table 0 0 revoke_record 0 0 dnotify cache 0 0 file lock cache 3 40 fasync cache 0 0 uid_cache 2 113 skbuff_head_cache 256 288 sock 33 54 sigqueue 0 29 cdev_cache 101 118 bdev_cache 3 59 mnt_cache 13 59 inode_cache 7523 7536 dentry_cache 8007 8040 filp 1702 1710 names_cache 2 6 buffer_head 26053 26280
112 96 96 32 64 64 32 160 128 96 16 152 56 328 328 152 16 392 584 448 144 16 192 32 32 32 416 384 96 48 12 32 20 96 16 32 160 832 132 64 64 64 480 128 128 4096 96
3 0 1 1 0 1 1 2 1 4 2 224 0 0 0 0 0 0 0 814 0 0 2 1 1 1 0 0 0 0 0 0 0 1 0 1 12 4 0 2 1 1 941 267 57 2 652
3 0 1 1 1 1 1 3 1 4 2 224 0 1 1 2 1 1 12 814 1 1 9 1 1 2 0 0 0 0 0 0 0 1 0 1 12 6 1 2 1 1 942 268 57 6 657
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 1 1 1 1 1 1 1 1 1
2-198

mm_struct vm_area_struct fs_cache files_cache signal_act size-131072(DMA) size-131072 size-65536(DMA) size-65536 size-32768(DMA) size-32768 size-16384(DMA) size-16384 size-8192(DMA) size-8192 size-4096(DMA) size-4096 size-2048(DMA) size-2048 size-1024(DMA) size-1024 size-512(DMA) size-512 size-256(DMA) size-256 size-128(DMA) size-128 size-64(DMA) size-64 size-32(DMA) size-32 60 4386 59 59 64 0 1 0 2 0 6 0 53 0 502 0 162 0 580 0 633 0 461 0 256 0 5544 0 2380 0 5664 72 160 4600 96 118 64 72 416 75 1312 0 131072 2 131072 0 65536 3 65536 0 32768 19 32768 0 16384 59 16384 0 8192 521 8192 0 4096 207 4096 0 2048 730 2048 0 1024 672 1024 0 512 504 512 0 256 270 256 0 128 6150 128 0 64 2596 64 0 32 5763 32 3 110 1 7 22 0 1 0 2 0 6 0 53 0 502 0 162 0 290 0 160 0 59 0 18 0 187 0 43 0 51 3 115 2 8 25 0 2 0 3 0 19 0 59 0 521 0 207 0 365 0 168 0 63 0 18 0 205 0 44 0 51 1 1 1 1 1 32 32 16 16 8 8 4 4 2 2 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
/proc/stat: cpu 17858 88586 56043 10210183 cpu0 17858 88586 56043 10210183 page 53904 53471 swap 0 0 intr 10172752 2 1043 27 9175366 0 0 0 0 0 0 228480 357094 0 0 0 0 0 0 0 0 0 0 0 1 40000 0 0 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 370735 0 0 0 0 0 0 0 0 0 0 0 0 0 disk_io: (3,0):(11172,4312,110506,6860,260227) ctxt 44809046 btime 1072795494 processes 11461 /proc/tty/drivers: serial serial pty_slave pty_master pty_slave pty_master /dev/ptmx /dev/console /dev/tty /proc/uptime: 103726.74 102184.12 /proc/version: Linux version 2.4.19 (swrel@donner) (gcc version 2.95.3 20010112 (prerelease)) #1 Mon Dec 15 00:14:29 PST 2003 find /core_files /mnt/core_files -type f /core_files/.misc_file /mnt/core_files/.misc_file
/dev/cua /dev/ttyS /dev/pts /dev/ptm /dev/ttyp /dev/pty /dev/ptmx /dev/console /dev/tty
5 4 136 128 3 2 5 5 5
64-65 64-65 0-255 0-255 0-255 0-255 2 1 0
serial:callout serial pty:slave pty:master pty:slave pty:master system system:console system:/dev/tty
2-199
validating ......G. ......G. ......G. .......T c ......GT c S.5...GT c S.5....T S.5...GT c S.5...GT c S.5....T c ......G. S.5....T .M...... .......T c S.5....T S.5....T S.5....T missing .....U.. .....U.. .....U.. .....U.. .....U.. .....U.. .....U.. .....U.. .M....G. .......T c S.5....T c .......T c .......T c S.5....T c .......T c S.5....T c S.5....T c S.5....T c S.5....T c .......T c .......T c .......T c .......T c .......T c S.5....T c validating ......G. ......G. .......T c ......GT c S.5...GT c S.5....T S.5....T c S.5....T c S.5....T c ......G. S.5....T .M...... .......T c S.5....T S.5....T .....U.. .....U.. .....U..
rpm database on primary partition /mnt /proc /tmp /etc/idle.conf /etc/passwd /etc/passwd.upgrade /etc/services /etc/hosts /etc/static-routes.options /etc/ld.so.conf /dev/initctl /etc/inittab /dev/ttyS1 /etc/syslog.conf /etc/gettydefs /etc/mail/sendmail.cf /etc/mail/statistics /tmp/webtools/logs /fabos/users/admin /fabos/users/admin/.bash_logout /fabos/users/admin/.inputrc /fabos/users/admin/.profile /fabos/users/diag /fabos/users/diag/.bash_logout /fabos/users/diag/.inputrc /fabos/users/diag/.profile /diag /etc/fabos/chassisid /etc/fabos/fabos.0.conf /etc/fabos/fabos.1.conf /etc/fabos/fabos.chassis.conf /etc/fabos/pdata.gen /etc/fabos/pki/switch.0.crt /etc/fabos/pki/switch.0.csr /etc/fabos/pki/switch.0.key /etc/fabos/pki/switch.0.pp /etc/fabos/pki/switch.0.rootcrt /etc/fabos/pki/switch.1.crt /etc/fabos/pki/switch.1.csr /etc/fabos/pki/switch.1.key /etc/fabos/pki/switch.1.pp /etc/fabos/pki/switch.1.rootcrt /etc/fabos/wwnid rpm database on secondary partition /mnt /proc /etc/idle.conf /etc/passwd /etc/passwd.upgrade /etc/services /etc/hosts /etc/static-routes.options /etc/ld.so.conf /dev/initctl /etc/inittab /dev/ttyS1 /etc/syslog.conf /etc/gettydefs /etc/mail/sendmail.cf /fabos/users/admin /fabos/users/admin/.bash_logout /fabos/users/admin/.inputrc
2-200

.....U.. .....U.. .....U.. .....U.. .....U.. .M....G. .......T S.5....T .......T .......T S.5....T .......T S.5....T S.5....T S.5....T S.5....T .......T .......T .......T .......T .......T S.5....T /fabos/users/admin/.profile /fabos/users/diag /fabos/users/diag/.bash_logout /fabos/users/diag/.inputrc /fabos/users/diag/.profile /diag /etc/fabos/chassisid /etc/fabos/fabos.0.conf /etc/fabos/fabos.1.conf /etc/fabos/fabos.chassis.conf /etc/fabos/pdata.gen /etc/fabos/pki/switch.0.crt /etc/fabos/pki/switch.0.csr /etc/fabos/pki/switch.0.key /etc/fabos/pki/switch.0.pp /etc/fabos/pki/switch.0.rootcrt /etc/fabos/pki/switch.1.crt /etc/fabos/pki/switch.1.csr /etc/fabos/pki/switch.1.key /etc/fabos/pki/switch.1.pp /etc/fabos/pki/switch.1.rootcrt /etc/fabos/wwnid
c c c c c c c c c c c c c c c c
2-201
ps_dump
Available in Fabric OS versions: v3.1.2, v4.1, v4.1 (Performance Command Group - not enabled by default) Version Differences: Version 4.x outputs that have ps_dump as part of supportshow will depict the output on a port basis with the command header: ps_dump -a -n ,port#> Additional Example/Case Studies: The output of this command is very large and would only be used at the direction of an ASIC engineer a partial output for a host port on a 3900 with no performance monitoring enabled is displayed in Example 2-100 Troubleshooting Use: Use this command to display performance monitoring information Note: For internal debugging purposes only.
Example 2-100: Partial ps_dump output

ps_dump -a -n 0/31 Dumping port info Port 31: pi_eecount = 0 pi_fltcount = 0 pi_flags = 0x40 pi_intents = 0 pi_eeintents = 0 pi_fltintents = 0 Dumping EE monitor info Port 31: eeMask = 0xfff eeMaskOwner = -1 e_status = 1 key 0 e_objp = 0x0 e_flags = 0x0 e_state = 0 e_key = 0 e_key1 = 0 e_key2 = 0 e_sid = 0x0 e_did = 0x0 e_rx(h) = 0 e_rx(l) = 0 e_tx(h) = 0 e_tx(l) = 0 e_crc(h) = 0 e_crc(l) = 0 e_tstamp = 0 e_rxrate(h) = 0 e_rxratea(l) = 0 e_txrate(h) = 0 e_txrate(l) = 0 e_crcrate(h) = 0 e_crcrate(l) = 0 e_creator = -1 e_ipaddr = 0x0 <output truncated>
2-202
ps_dump -a -n port#
Note: See ps_dump command information
2-203
psShow
Available in Fabric OS versions: All Version Differences: The number and type of power supplies vary by hardware platform. Troubleshooting Use: Use this command to display the current status of the switch power supplies. The format of the display varies according to the switch model and number of power supplies present. Optionally, depending upon switch model, the OEM Serial ID Data is displayed after each power supply status line. The status of each supply is shown as: OK absent Unknown Predicting Failure Power supply functioning correctly. Power supply not present. Unknown power supply unit installed. Power supply is present but predicting failure.
faulty Power supply present but faulty (no power cable, power switch turned off, fuse blown, or other internal error). Example 2-50: Example
psshow: Power Supply #1 is OK DELTA DPS-1001AB-1E 23000000601 Power Supply #2 is OK DELTA DPS-1001AB-1E 23000000601 Power Supply #3 is OK DELTA DPS-1001AB-1E 23000000601 Power Supply #4 is OK DELTA DPS-1001AB-1E 23000000601
S1 S1 S1 S1
IXD0130001068 IXD0130001078 IXD0130001064 IXD0130001086
Note:
If errshow messages indicate a power supply error look here to make sure all power supplies are OK.

psshow: Power Supply #1 is OK DELTA DPS-1001AB-1E 23000000602 Power Supply #2 is faulty DELTA DPS-1001AB-1E 23000000602 Power Supply #3 is OK DELTA DPS-1001AB-1E 23000000602 Power Supply #4 is faulty DELTA DPS-1001AB-1E 23000000602
S2 S2 S2 S2
FL2L0002037 FL2L0002031 FL2L0002040 FL2L0002046
Note:
Notice that there are power supply #2 and 4 faulty conditions on this switch. Power supplies 2 and 4 are associated with power source 2, power source 2 was not plugged in during this capture.
2-204
ptbufshow
Available in Fabric OS versions: v4.1, 4.2 (Extended Command Group - not enabled by default) Additional Example/Case Studies: Troubleshooting Use: Use this command to dump port buffer contents Note: For internal debugging purposes only. The output of this command is very large and would only be used at the direction of an ASIC engineer a partial output for a host port on a 3900 with no performance monitoring enabled is displayed inExample 2-102
Example 2-102: v4.2 output from a 3900 with a JBOD on port 31 and a host on port 30
ptbufshow 31: Port Buffers for port: 27 putq_list_stat is empty (0xffffffff tolist_stat is empty (0xffffffff == plist_stat is empty (0xffffffff == aulist_stat is empty (0xffffffff == piq_stat: head=0x0 tail=0x0 piq_stat: number of mini-buffers = 1 == NO_BUFFER) NO_BUFFER) NO_BUFFER) NO_BUFFER)
flist_stat : head=0x1e4 tail=0xf6 0x1e4 0x016 0x316 0x05c 0x2a6 0x18c 0x278 0x304 0x10c 0x2dc 0x2de 0x274 0x1de 0x226 0x30c 0x0f4 0x04e 0x2d0 0x130 0x032 0x19a 0x254 0x310 0x35e 0x1a8 0x108 0x330 0x062 0x242 0x364 0x2fe 0x23a 0x078 0x098 0x196 0x17c ......<output truncated>..... 0x26e 0x03e 0x28c 0x16e 0x06e 0x0ba 0x266 0x0d2 0x10a 0x068 0x046 0x1f4 flist_stat : number of mini-buffers = 437 missing buf 0x184 missing buf 0x222 missing buf 0x272 cflist_stat: head=0x1b5 tail=0x1a5 0x1b5 0x27b 0x1b9 0x2a7 0x285 0x32f 0x21b 0x00b 0x171 0x273 .....<output truncated>
0x14c 0x090 0x35a 0x228 0x13a 0x2e4 0x15c 0x20e
0x146 0x34e 0x188 0x206 0x0f2 0x088 0x106 0x07e
0x1da 0x0d4 0x0ea 0x300 0x178 0x136 0x1a4
0x132 0x182 0x028 0x190 0x2b4 0x264 0x280
0x2d4 0x18a 0x244 0x252 0x2b6 0x212 0x1d6
0x0ec 0x01e 0x2ac 0x27e 0x290 0x1fc 0x2ba
0x276 0x344 0x12a 0x268 0x03a 0x234 0x1e6
0x1db
0x039
0x1ab
0x1c5
0x073
0x22d
0x103
0x1cd
2-205
ptcreditshow
Available in Fabric OS versions: v4.1, v4.2 Troubleshooting Use: Use this command to display port credit information. Example 2-51: v4.1 example
display port credits Example: ptcreditshow 2 0: slot: 2 tcc_vc bpt15: L 0 0 0 0 0 0 0 0
rqc_vc 0 0 0 0 0 0 0 0
rct_vc 1 1 1 1 1 1 1 31
rcc_vc 0 0 0 0 0 0 0 0
tcc and rcc mean transmit credit counter and receive credit counter for each VC (Virtual Channel) rqc_vc mean receive credit queue ctr for each VC rct_vc mean receive credit clear threshold for each VC
Note:
See portregshow sections in this guide for additional information regarding some of these parameters.
Example 2-103: Output from a 3900 with extended groups enabled, there is a host on port 31 and a JBOD on port 30 (associated portregshow outputs appended to cross reference)
ptcreditshow 30: tcc_vc rqc_vc rct_vc rcc_vc /bin/cat: /proc/fabos/blade/0/1/1/2/asic26/cebs: RFS specific error bpt26: L 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 16 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 16 ptcreditshow 31: tcc_vc rqc_vc rct_vc rcc_vc /bin/cat: /proc/fabos/blade/0/1/1/3/asic27/cebs: Device not a stream bpt27: F 0 0 0 0 0 0 0 14 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 portregshow 30:
....<output truncated>....
0xcaa3e080: 0xcaa3e090: 0xcaa3e0b0: 0xcaa3e0c0: 0xcaa40800: 0xcaa40820: 0xcaa40840: 0xcaa40860: 0xcaa40880: portregshow 0xcaa4e080: 0xcaa4e090: 0xcaa4e0b0: 0xcaa4e0c0: 0xcaa50800: 0xcaa50820: 0xcaa50840: 0xcaa50860: 0xcaa50880: tcc_vc rqc_vc rct_vc rcc_vc desired_bufs busy_bufs alloc_bufs busy_mini mini_allocated 31: tcc_vc rqc_vc rct_vc rcc_vc desired_bufs busy_bufs alloc_bufs busy_mini mini_allocated 0 0 1 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 0 16 1 16 2 128 0 0 1 0 16 1 16 2 128 0 0 1 0 2 1 2 1 17 0 0 1 0 0 0 1 0 15 0 1 0 0 0 1 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 0 16 1 16 2 128 0 0 1 0 16 1 16 2 128 0 0 1 0 2 1 2 1 17 0 0 1 0 0 0 1 0 0 16 1 16
....<output truncated>....
2-206
ptdatashow
Available in Fabric OS versions: Version Differences: v4.2 Example Output: Additional Example/Case Studies: Troubleshooting Use: Use this command to display port data structures. Note: This command is not intended for normal user operation and is available to provide supplemental information during system debug.
Example 2-52: To display the port data structure for slot 1 port 1:
switch:admin> ptdatashow 1/1 Port Data Structure for slot: 1, port: 1 Bloom Data Pointers: bloomp = 0xc6eb7200 (fbloomp = 0x00000000) ------------------blm_regs 0xc9b17000 blm_proc_dir 0xc50d9f20 fab_ptr 0xc04f0000 fab_Iop 0xc04f0050 qdblm 0xc5702c00 chblm 0xc661b5a0 pt 0xc5701760 blm_miniS_handle 0xc57012e0 Bloom Local Variables --------------------blm_type = 0x00000012 G_PORT E_PORTto stop blm_state = 0x00000001 ONLINE p_phstate = IN_SYNC blm_flags = 0x00000000 NORMAL lab_mode = 0x00 EFD blm_port_type = Intra-blade blm_rev 1 blm_initialized 0 my_domain 1 blm_quad_idx 1 blm_chip_idx 1 blm_miniS_idx 1 blm_blade_idx 1
--- <output truncated> --Example 2-53:

ptdatashow 2 0: Port Data Structure for Slot: 2 port: 15 Bloom Data Pointers: bloomp = 0xc3944800 (fbloomp = 0xc391c000) ------------------blm_regs 0xca9e9000blm_proc_dir 0xc685d0e0 fab_ptr 0xc7b10000fab_Iop 0xc7b10050 qdblm 0xc38ab000chblm 0xc6234cc0 pt 0xc38afcc0blm_miniS_handle 0xc5568940 Bloom Local Variables --------------------blm_type = 0x00000001FL_PORT blm_state = 0x00000000OFFLINEp_phstate = NO_LIGHT blm_flags = 0x00000000NORMAL blm_diagflags = 0x00000000NULL lab_mode = 0x00EFD blm_port_type = User blm_rev 1 blm_initialized 1 my_domain 1 blm_quad_idx 3 blm_chip_idx 7 blm_miniS_idx 15 blm_blade_idx 15 blm_UI_idx 16 blm_slot_no 2 blm_mode 0 blm_ie_fctl_mode 0 chip fdet_enabled 1 quad fdet_enabled 1 fdet_enabled 1 frmtrk_type 0x00000106 fl_bbc 0 fl_fan 0
2-207
fl_cls 4 fl_rscn 0 blm_tfrctl_changed0x00000000 blm_tfrctl_shadow0x00000000 p_etcc 0 0 0 0 0 0 0 blm_buf_state = 0x00000000BUF_RDY_DONE HA blm_more_n = 0x0001Offline
Bloom User Variables -------------------blm_lstate 0x00000000unknown state blm_lflags 0x00000000 lpsm_iu 0x00000000fla_iu 0x00000000 blm_lli 5 blm_lli_pending 0 blm_copper 1 blm_bufbusy_tov 0 blm_linit_ct 0 blm_liphold_ct 0 blm_ftx 0 blm_open_tov 0 blm_tov 0 blm_fault1 16 blm_fault2 0 blm_fault_tov 0 blm_credit 0 blm_alpamap 0x00000000 0x00000000 0x00000000 0x00000000 blm_lipamap 0x00000000 0x00000000 0x00000000 0x00000000 blm_lifamap 0x00000000 0x00000000 0x00000000 0x00000000 blm_rxlipa 0x00000000 0x00000000 0x00000000 0x00000000 blm_rxliha 0x00000000 0x00000000 0x00000000 0x00000000 blm_pltmap 0x00000000 0x00000000 0x00000000 0x00000000 blm_loginmap 0x00000000 0x00000000 0x00000000 0x00000000 Speed Negotiation Variables --------------------------blm_cfg_speed = AUTO_SPEED_NEGO negotiation state = WAIT_FOR_SIGNAL_18 blm_speed = UNKNOWN blm_rx_signal = FALSEblm_rx_sync = FALSE blm_sn_inprogress 0 blm_retries 0 blm_curr_tx 1 blm_curr_rx 1 blm_currtx_indx 0 blm_currrx_indx blm_time_nc 0 blm_time_tx 0 blm_time_neg 0 blm_time_sync 0 blm_txsp_list 1 0 0 0 blm_curr_txsp_list 1 0 0 0 blm_curr_rxsp_list 1 0 0 0 blm_rxsp_recorded 255 255 255 255 Trunking Variables -----------------blm_tMaster = NULL blm_members 0 blm_port_group 0 blm_adelay 0xffffffffblm_mdelay 0x00000000 blm_mark_tm 0xffffffff pt(0 0 0 0) ts[0]: 0 0 0 0 pt(0 0 0 0) ts[1]: 0 0 0 0 pt(0 0 0 0) ts[2]: 0 0 0 0 pt(0 0 0 0) ts[3]: 0 0 0 0 pt(0 0 0 0) md[0] (mark/time_stamp): 0(0) 0(0) 0(0) 0(0) pt(0 0 0 0) md[1] (mark/time_stamp): 0(0) 0(0) 0(0) 0(0) pt(0 0 0 0) md[2] (mark/time_stamp): 0(0) 0(0) 0(0) 0(0) pt(0 0 0 0) md[3] (mark/time_stamp): 0(0) 0(0) 0(0) 0(0) Fail Detection Data -----------------------Slot: 2, MiniS: 0, Quad: 3:
2-208
faildet_pstat frmtrk_mode frmtrk_prtstat frmtrk_failinfo[0] frmtrk_failinfo[1] ministatechk_stat faildet_pctl frmtrk_ctl faildet_ctl
0xca9ebd2c: 0xca9ebd26: 0xca9ebd2e: 0xca9ebd18: 0xca9ebd1c: 0xca9ebd20: 0xca9ebd2a: 0xca9ebd28: 0xca9ebd24:
0x0000 0xe000 0x0000 0x00000000 0x00000000 0x0fff01ff 0x0007 0xffcc 0x0f37
frmtrk_failinfo[0]: frTrkNumErrPt=0 isTrkNum=0 sbTrkNum=0 frmtrk_failinfo[1]: rxPtQuad=0 finMsgE=0 frTrkNumE=0 txQNumE=0 flPtMode=0 rptFrTx=0 trunkMprt=0 bufrNum=0
mbStCkE=0 txQnumb=0
invEMsg=0 txPtNum=0
Buffer Tag Mismatch for 4 quad ports (0xca9ebc64 blm_less_n): 0 0 0 0 ministatechk_stat: mbStCkE=0 finE=0 rxQParE=0 rxQFrTrkE=0 actSubSt=3 actSt=f expSubSt=3 expSt=f mb#=1ff faildet_ctl: frcR2TqIntParE=0 frcProcRqdBufNumE=0 frcPutMsgE=0 frcBufTagE=0 bufTagCkEn=000f frcFinMessageE=0 frcTrkNumCkEn=1 txQNumCkEn=1 mbufStCkEn=1 finMsgCkEn=1 rxQParCkEn=1
Note:
No additional information available at this time.
2-209
ptphantomshow
Available in Fabric OS versions: v4.1, v4.2 Troubleshooting Use: Use this command to display the Quickloop Content Addressable Memory (CAM) tables used when private devices (even when they are not in Quickloop) are attached to a switch. Note: This command is not intended for normal user operation and is available to provide supplemental information during system debug.
Example 2-54:
ptphantomshow 2 0: Port Routing table for port: 15
The following ALPAs are private on some switch ports: (alpa, UI port bitmap on the blade)
plt_cam table and plt_alpa table: index sid plt_alpas(UI port 15 - 0 w 1 byte/port) plt_did table for this port: ali alpa sidali alpa sidali
alpa
sid
Note:
If private storage devices where attached to this switch this output would be interpreted the same as bloomphantomshow output for v3.x firmware and loomphantomshow output for v2.x firmware. Here is a v3.x output example with supporting information:
switchname:admin> bloomPhantomShow The following alpas are private on some switch ports: (0xdc, 0080) (0xe0, 0080) (0xe1, 0080) (0xe2, 0080) (0xe4, 0080) (0xe8, 0080) (0xef, 0080) plt_cam table and plt_alpa table: index sid plt_alpas 0 0x00fffc01 ffffffff ffffffff 01ffffff ffffffff plt_did table for this port: ali alpa sid ali alpa my_alpa: 0xdc 0xe0 0xe1 0xe2 0xe4 0xe8 0xef
sid
ali
alpa
sid
The following ALPAs are private on some switch ports: (Note - These are the private devices on the switch.) Let us take (0xdc,0080): dc is a private AL_PA. 0080 represents port# bit map. And that port# is online, dc AL_PA is attached to it. Convert 0080 into binary notation: 0000 0000 1000 0000 Count from right to left starts with port 0. 1 is toggled in the 7th position. This means port 7 is the FL_port and it has dc, eo, e1, e2, e4, e8 and ef AL_PAs. plt_cam table and plt_alpa table: To interpret this table, the SID is source ID or 24-bit address, ffffc01 is the 24-bit address of the embedded port on this switch, it has ALPA 01 on port 7 (read pairs of fs right to left, each pair represents a port number starting at port 0).
index 0 sid 0x00fffc01 plt_alpas ffffffff ffffffff 01ffffff ffffffff
2-210
Fabric OS SupportShow Information Plt_did table for this port: No information available at this time. my_alpa: represents the local phantom ALPAs on this switch. Warning:
A word of caution: Bloomphantomshow, although extremely helpful, is currently an un-documented command and is not supported. This command shares all the other inherent dangers of undocumented commands. Different versions of firmware could show output differently, programmers could drop the command without notice, and so forth.
porttalpashow slot/port #s can also be used to gather information about private devices on the switch. It is similar to loomalpashow <port #> from a v2.x switch and bloomalpashow <port #> from a v3.x switch. Here is a v3.x switch example with corresponding information: Example 2-55:
switchname:admin> bloomAlpaShow AL_PA type AL_PA 0x01 (0xfffc01) 0xdc 0xe1 private 0xe2 0xe8 private 0xef 7 type private private private AL_PA 0xe0 0xe4 type private private
The bloomAlpaShow <port #> command displays the AL_PA type for this port. In this example, AL_PA 01 taken by the 24-bit address (0xfffc01). Phantom AL_PAs are depicted in parentheses. Use switchshow output to ascertain the number of phantoms and to review what fffc01 represents. Warning: A word of caution: (B)loomAlpaShow <port #>, although extremely helpful, is currently an undocumented command and is not supported. This command shares all the other inherent dangers of undocumented commands: different versions of firmware could show output differently, programmers could drop the command without notice, and so forth.
2-211
ptpropshow
Available in Fabric OS versions: v4.1, v4.2 Troubleshooting Use: Use this command to display the ASIC port properties for the specified port. Note: This command is not intended for normal user operation and is available to provide supplemental information during system debug.
Example 2-56:
ptpropshow 2 0: Port Property for Slot: 2 port: 15 P15: [fe,0,12],Port,CAP:[1,1,1,(1,1,0)],CFG:[D:0,G:0,T:1,S:0,M:0,E:0,L:0],WWN: 00:00:00:00:00:00:00:00
Note:
No additional information available about this command at this time.
2-212
ptstatsshow
Available in Fabric OS versions: v4.1, v4.2 (Extended Command Group - not enabled by default) Troubleshooting Use: Use this command to display the port statistic properties for the specified port. Note: This command is not intended for normal user operation and is available to provide supplemental information during system debug.
Example 2-57:
ptstatshow 2 0: Port Statistics for Slot: 2 port: 15 Connection type: FE Configured Speed: 0 Interrupts: 56 Unknown: 0 Lli: 16 Proc_rqrd:40 Timed_out:0 Rx_flushed:0 Tx_unavail:0 Free_buffer:0 Overrun: 0 Suspended:0 Parity_err:0 2_parity_err:0 CMI_bus_err:0 stat_wtx stat_wrx stat_ftx stat_frx stat_c2_frx stat_c3_frx stat_lc_rx stat_mc_rx stat_mc_to stat_mc_tx tim_rdy_pri tim_txcrd_z er_enc_in er_crc er_trunc er_toolong er_bad_eof er_enc_out er_disc_c3 open transfer opened starve_stop fl_tenancy nl_tenancy 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4819 0 0 0 0 0 0 0 Link_failure:6 Loss_of_sync:0 Loss_of_sig:1 Protocol_err:0 Invalid_word:0 Invalid_crc:0 Delim_err: 0 Address_err:0 Lr_in: 3 Lr_out: 3 Ols_in: 3 Ols_out: 3
4-byte words transmitted 4-byte words received Frames transmitted Frames received Class 2 frames received Class 3 frames received Link control frames received Multicast frames received Multicast timeouts Multicast frames transmitted Time R_RDY high priority Time BB_credit zero Encoding errors inside of frames Frames with CRC errors Frames shorter than minimum Frames longer than maximum Frames with bad end-of-frame Encoding error outside of frames Class 3 frames discarded loop_open loop_transfer FL_Port opened tenancies stopped due to starvation number of times FL has the tenancy number of times NL has the tenancy
Note:
ptstatsshow is similar to portstatsshow output for v3.x switches. See portErrShow and portshow output information for additional information on parameters depicted. Here is an v3.x example output with some supporting information:
2-213
Fabric OS SupportShow Information Example 2-58: v3.0:admin> portStatsShow 3
stat_wtx stat_wrx stat_ftx stat_frx stat_c2_frx stat_c3_frx stat_lc_rx stat_mc_rx stat_mc_to stat_mc_tx tim_rdy_pri tim_txcrd_z er_enc_in er_crc er_trunc er_toolong er_bad_eof er_enc_out er_disc_c3 open transfer opened starve_stop fl_tenancy nl_tenancy frame_nozone
29597 27003 1472 1545 0 1545 0 1 0 0 57 12 0 0 0 0 0 10 31 0 0 0 0 0 0 0
4-byte words transmitted 4-byte words received Frames transmitted Frames received Class 2 frames received Class 3 frames received Link control frames received Multicast frames received Multicast timeouts Multicast frames transmitted Time R_RDY high priority Time BB_credit zero Encoding errors inside of frames Frames with CRC errors Frames shorter than minimum Frames longer than maximum Frames with bad end-of-frame Encoding error outside of frames Class 3 frames discarded loop_open loop_transfer FL_Port opened tenancies stopped due to starvation number of times FL has the tenancy number of times NL has the tenancy frames rejected due to zone protection
Note:
Notice Time BB_Credit Zero. A high value could occur for many reasons: - HBA does not have enough buffers to be able to receive 1 Gbps traffic. - Disk may not be able to handle 1 Gbps data coming at it. Switch port is buffering the data while waiting for an r_rdy from disk. - May be congestion in the Fabric, if not enough ISLs are present to accommodate the traffic that is being sent through.
If you invoke portstatsshow, you will see all portstatsshow outputs for all ports on the switch. Portstatsshow <port #> displays only one port. Pay attention to: enc, crc, trunc, toolong bad_eof; enc_out, er_disc. Unlike portShow and portErrShow outputs, the counters that generated portstatsshow statistics occur between and on interrupts. Start looking at these errors if you see the enc out going from 100, to 200, and to 300 (quickly rising values). You should see considerably less than 5% tx plus rx counters on any statistic. These errors are based on a BER (bit error rate) of 10 to the minus 12 rate for all the err commands. For reference a BER of 10 to the minus 15 implies that a bit every 3 days was bad. These BERs generate error statistics when exceeded. Unless they get really bad, they often cause timeouts in the Fabric. We recommend using Fabric Watch to monitor these error statistics so that you know about problems before they cause production outages or slowdowns.
2-214
qlShow
Available in Fabric OS versions: All v2.x and 3.x supportshow outputs. Quickloop is not available on v4.x switches. Troubleshooting Use: Use this command to display Quickloop information This command displays quick loop info. Self worldwide name and domain ID of this switch Peer State Master Non master Local Lip Remote Lip Online Offline Scope AL_PA bitmap Remote AL_PAs Local AL_PAs Local looplet state worldwide name and domain ID of partner switch Peer is displayed only if the switch has a partner configured Quick loop state Master switch in dual switch QuickLoop. Non master in dual switch QuickLoop. Looplet on local switch lipped Looplet on partner switch lipped Switch comes online Switch goes offline Dual or single (switch Quick Loop) AL_PA bitmaps of devices on the Quick Loop. AL_PA of devices on partner switch. AL_PAs are listed per port base AL_PA of devices on local switch. AL_PAs are listed per port base indicates state of local looplet
Member: current quick loop member ports Online: current online ports in the quick loop Looplet can be in one of the following states: Online Lipped Lipping Initializing Bypassed Error Offline completed loop initialization NL_port lipped FL_port lipped loop initialization in progress Looplet being bypassed Error found in this looplet Looplet offline
The following command displays the quick loop info: Example 2-104:
sw5:admin> qlShow Switch is not in Quick Loop mode.
Example 2-105:
sw2:admin> qlShow Self: 10:00:00:60:69:10:02:09 domain 1 Peer: 10:00:00:60:69:10:02:0d domain 2 State: Master Scope: dual AL_PA bitmap: 18000000 00000000 00000000 000000ff Remote AL_PAs [021600]: e2 e4 e8 ef [021700]: 04 [021900]: da dc e0 e1 Local AL_PAs [011900]: 02 Local looplet states
2-215
Member: 0 9 Online: - 9
Note: Self Peer State Scope
If there is a dual switch QuickLoop, the E_Port will appear as part of the QuickLoop even though it is not a real looplet. the local switch with its WWN and domain number. the remote switch with its WWN and domain number. If QuickLoop is in single switch mode, no peer is listed. indicates if the local switch is the master or non-master. indicates the QuickLoop mode as dual or single switch.
AL_PA bitmap All AL_PAs in the entire QuickLoop Remote AL_PAs The looplets and devices that are in QuickLoop mode on the remote switch Local AL_PAs The looplets and devices that are in QuickLoop mode on the local switch Local looplet states the looplets, member (switch ports), online (QuickLoop ports, looplet) status (port). How do we use this information? If a port is put into quickloop (QL) mode and the attached device is a Fabric host it will FLOGI itself to death because QL disables FLOGIs at the port and the attached device is set up as Fabric which means FLOGI! A definite mismatch! Also if a private host needs to communicate in a Fabric QL must be licensed and enabled.
2-216
rcsinfoshow
Note: rcs stands for Reliable Commit Service
Troubleshooting Use: rcsinfoshow command shows the RCS capability of the switches. The user can tell
if all the switches in the fabric support RCS.

Available in Fabric OS versions: v4.1, v4.2 Additional Example/Case Studies: Example 2-59: v4.1 output
rcsinfoshow: Domain : Version : capability 2: 1 | 1 Domain list 1, 2, g_rcsDisabled = 0 g_rcsForceDisabled = 0 g_rcsMyDomain = 1
Note:
RCS (Reliable commit service) is used to propagate data from one switch to the rest of the switches in the fabric. This is a service that application for example: Zoning, Security and MS are used to send data from one switch to rest of the switches in the fabric. The RCS has 4 phases to ensure that all the switches in the fabric will have the same data. If one or more switches are not able to accept the new update, all the switches in the fabric will stay with the old data. If all the switches accept the new update, then the data will be committed on all the switches in the fabric.

rcsinfoshow: Domain : Version : capability Domain list 1, g_rcsDisabled = 0 g_rcsForceDisabled = 0 g_rcsMyDomain = 1
2-217
rcsregistryshow
Note: rcs stands for Reliable Commit Service
Troubleshooting Use: Rcsregisteryshow Available in Fabric OS versions: v4.1, v4.2 Additional Example/Case Studies: v4.1 Example Output: Example 2-60:
rcsregistryshow: RCS Registry 0: appcode 1 1: appcode 2 2: appcode 3 3: appcode 4
command shows which application registered for RCS
callbacks callbacks callbacks callbacks
[0x10011644; [0x10011644; [0x10011644; [0x10011644;
0x10011644; 0x10011644; 0x10011644; 0x10011644;
0x10011644; 0x10011644; 0x10011644; 0x10011644;
0x10011644] 0x10011644] 0x10011644] 0x10011644]

rcsregistryshow: RCS Registry 0: appcode 1 callbacks [0x10011cc4; 0x10011cc4; 0x10011cc4; 0x10011cc4] 1: appcode 2 callbacks [0x10011cc4; 0x10011cc4; 0x10011cc4; 0x10011cc4] 2: appcode 3 callbacks [0x10011cc4; 0x10011cc4; 0x10011cc4; 0x10011cc4]
Note:
RCS (Reliable commit service) is used to propagate data from one switch to the rest of the switches in the fabric. This is a service that application for example: Zoning, Security and MS are used to send data from one switch to rest of the switches in the fabric. The RCS has 4 phases to ensure that all the switches in the fabric will have the same data. If one or more switches are not able to accept the new update, all the switches in the fabric will stay with the old data. If all the switches accept the new update, then the data will be committed on all the switches in the fabric.
2-218
rcssmshow
Troubleshooting Use: This command is useful for debuging the case where a RCS transaction is stuck. Available in Fabric OS versions: v4.1, v4.2 Note: rcs stands for Reliable Commit Serivice, sm stands for state change. This is a reliable commit service state change show command. The rcssmshow command can be used to display the state machine of all the applications that use RCS. First structure is for Zoning, 2nd for Security etc. This debug command shows the Application Id, the rcs phase (Sender or receiver: ACA, SFC, UFC, RCA ), list of domains that got that phase, which domain accepted, rejected or left the fabric in the middle of the RCS transaction. Example: The first structure (RCS opcode 1) shows the RCS state machine used for the Zoning application. This structure shows the internal of the RCS state machine. It does not show the application data. zone stateshow will display the zoning application debug information. Zoning uses RCS only for the commit operations (cfgEnable, cfgDisable & cfgSave). It is not used during zone merge. Therefore, RCS will not cause segmentation.
Additional Example/Case Studies: v4.2 Example Output: Example 2-61:

rcssmshow: === Barrier 0x1001fb90 === nupdates(0) flags(0x0) ================================ === RCS APPCODE - 1 ==== ---------------------------------------------Rcs Xact State Machine Control Block: 0x10020518 ++++++++++++++++++++++++++++++++++++++++++++++ Application ID : -1 Transaction State : 0 RTWR Handle : 0x1002afe0 Transaction Prev State: 0 Rca Reason : 0 Original CM : 0 New CM : 0 Last Local Callback : 0 Original Domains : { Number Of Domains : 0 } { } { } { } Domains that Left Fabric during Commit: Number Of Domains : 0 Rejected Domains : Number Of Domains : 0 Accepted Domains : Number Of Domains : 0 Sent Domains : Number Of Domains : 0
{ }
Timer ID
: 0x1002acd8
2-219

Application Data CB : { application id application data size application data ptr }
: -1 : -1 : (nil)
Preamble size : 0 ---------------------------------------------=== RCS APPCODE - 2 ==== ---------------------------------------------Rcs Xact State Machine Control Block: 0x10020a48 ++++++++++++++++++++++++++++++++++++++++++++++ Application ID : -1 Transaction State : 0 RTWR Handle : 0x10030478 Transaction Prev State: 0 Rca Reason : 0 Original CM : 0 New CM : 0 Last Local Callback : 0 Original Domains : { Number Of Domains : 0 } { } { } { } Domains that Left Fabric during Commit: Number Of Domains : 0 Accepted Domains : Number Of Domains : 0 Rejected Domains : Number Of Domains : 0 Sent Domains : Number Of Domains : 0
{ }
Timer ID : 0x1002ad30 Application Data CB : { application id : -1 application data size : -1 application data ptr : (nil) } Preamble size : 0 ---------------------------------------------=== RCS APPCODE - 3 ==== ---------------------------------------------Rcs Xact State Machine Control Block: 0x10020f78 ++++++++++++++++++++++++++++++++++++++++++++++ Application ID : -1 Transaction State : 0 RTWR Handle : 0x100394a8 Transaction Prev State: 0 Rca Reason : 0 Original CM : 0 New CM : 0 Last Local Callback : 0 Original Domains : { Number Of Domains : 0 }
2-220

Sent Domains : Number Of Domains : 0
{ } { } { }
Accepted Domains : Number Of Domains : 0
Rejected Domains : Number Of Domains : 0 Domains that Left Fabric during Commit: Number Of Domains : 0
{ }
Timer ID : 0x1002ad88 Application Data CB : { application id : -1 application data size : -1 application data ptr : (nil) } Preamble size : 0 ---------------------------------------------=== RCS APPCODE - 4 ==== ---------------------------------------------Rcs Xact State Machine Control Block: 0x100214a8 ++++++++++++++++++++++++++++++++++++++++++++++ Application ID : -1 Transaction State : 0 RTWR Handle : 0x10034c90 Transaction Prev State: 0 Rca Reason : 0 Original CM : 0 New CM : 0 Last Local Callback : 0 Original Domains : { Number Of Domains : 0 } { } { } { } Domains that Left Fabric during Commit: Number Of Domains : 0 Rejected Domains : Number Of Domains : 0 Accepted Domains : Number Of Domains : 0 Sent Domains : Number Of Domains : 0
{ }
Timer ID : 0x1002ade0 Application Data CB : { application id : -1 application data size : -1 application data ptr : (nil) } Preamble size : 0
2-221
----------------------------------------------
Note:
No additional information is available at this time.

rcssmshow: === Barrier 0x10020450 === nupdates(0) flags(0x0) ================================ === RCS APPCODE - 1 ==== ---------------------------------------------Rcs Xact State Machine Control Block: 0x10020e58 ++++++++++++++++++++++++++++++++++++++++++++++ Application ID : -1 Transaction State : 0 RTWR Handle : 0x10030ec8 Transaction Prev State: 0 Rca Reason : 0 Original CM : 0 New CM : 0 Last Local Callback : 0 Original Domains : { Number Of Domains : 0 } Sent Domains : { Number Of Domains : 0 } { } { } Accepted Domains : Number Of Domains : 0 Rejected Domains : Number Of Domains : 0 Domains that Left Fabric during Commit: Number Of Domains : 0 Timer ID : 0x1002b6e0 SHM ID : 720917 SHM Size : 131072 Socket : -1 Application Data CB : { application id : -1 application data size : -1 application data ptr : (nil) } Preamble size : 0 ---------------------------------------------=== RCS APPCODE - 2 ==== ---------------------------------------------Rcs Xact State Machine Control Block: 0x10021398 ++++++++++++++++++++++++++++++++++++++++++++++ Application ID : -1 Transaction State : 0
{ }
2-222

RTWR Handle : Transaction Prev State: Rca Reason : Original CM : New CM : Last Local Callback : Original Domains : Number Of Domains : 0 Sent Domains : Number Of Domains : 0 Accepted Domains : Number Of Domains : 0 Rejected Domains : Number Of Domains : 0 Domains that Left Fabric during Commit: Number Of Domains : 0 Timer ID : 0x1002b738 SHM ID : 753686 SHM Size : 131072 Socket : -1 Application Data CB : { application id : -1 application data size : -1 application data ptr : (nil) } Preamble size : 0 ---------------------------------------------=== RCS APPCODE - 3 ==== ---------------------------------------------Rcs Xact State Machine Control Block: 0x100218d8 ++++++++++++++++++++++++++++++++++++++++++++++ Application ID : -1 Transaction State : 0 RTWR Handle : 0x1002b9e8 Transaction Prev State: 0 Rca Reason : 0 Original CM : 0 New CM : 0 Last Local Callback : 0 Original Domains : { Number Of Domains : 0 } Sent Domains : { Number Of Domains : 0 } Accepted Domains : { Number Of Domains : 0 } Rejected Domains : { Number Of Domains : 0 } Domains that Left Fabric during Commit: { Number Of Domains : 0 } Timer ID : 0x1002b790 SHM ID : 786455 SHM Size : 131072 Socket : -1 0x10035728 0 0 0 0 0
{ } { } { } { }
{ }
2-223

Application Data CB : { application id application data size application data ptr
: -1 : -1 : (nil)
} Preamble size : 0 ----------------------------------------------
2-224
routeShow
Available in Fabric OS versions: v3.1, v3.1.2 (Networking Command Group) v4.2 Example Output: NA Troubleshooting Use: Use the output of this command along with other network command group commands to troubleshoot TCP/IP network access problems. The output of this command will help determine TCP/IP routing.
Example 2-109: Output from a v3.1.2 switch

routeShow ROUTE NET TABLE destination gateway flags Refcnt Use Interface ---------------------------------------------------------------------------0.0.0.0 10.64.144.1 3 1 710 fei0 10.64.144.0 10.64.147.28 101 0 0 fei0 ---------------------------------------------------------------------------ROUTE HOST TABLE destination gateway flags Refcnt Use Interface ---------------------------------------------------------------------------127.0.0.1 127.0.0.1 5 0 0 lo0 ----------------------------------------------------------------------------
network Command Group Commands: ipAddrShow ifShow ipstatShow udpstatShow tcpstatShow inetstatshow mbufShow arpShow routeShow routestatShow hostShow feiDumpPrint i557Dump feiIterateRFDRings
2-225
routestatShow
Available in Fabric OS versions: v3.1, v3.1.2 (Networking Command Group) v4.2 Example Output: NA Troubleshooting Use: Use the output of this command along with other network command group commands to troubleshoot TCP/IP network access problems. This command displays TCP/IP network routing statistics. Example 2-110: Output from a v3.1.2 switch
routestatShow routing: 0 bad routing redirect 0 dynamically created route 0 new gateway due to redirects 0 destination found unreachable 0 use of a wildcard route
network Command Group Commands: ipAddrShow ifShow ipstatShow udpstatShow tcpstatShow inetstatshow mbufShow arpShow routeShow routestatShow hostShow feiDumpPrint i557Dump feiIterateRFDRings
2-226
secFabricShow
Available in Fabric OS versions: v3.1, v3.1.2, v4.1, v4.2 Troubleshooting Use: Use this command to display security related fabric information. This command displays the security related information about the fabric. The information displayed is as follows: Role WWN DId Status Ready Busy Error Enet IP Addr Name Note: Displays whether the switch is the Primary FCS, Backup FCS, or Non FCS. Displays the world wide name of the switch. Displays the Domain of the switch. Displays the security state of the switch. This switch is in a stable state. This switch is updating its security database. This switch's security database is inconsistent with the Primary FCS. Displays the Ethernet IP address. Displays the switch name.
When security mode is enabled, this command can be executed on any switch in fabric.
Example 2-62: To display security related fabric information on the Primary FCS switch.
secpolicydump switch:admin> secfabricshow Role WWN DId Status Enet IP Addr Name ================================================================ non-FCS 10:00:00:60:69:10:03:231 Ready 192.168.100.148 "nonfcs" Backup 10:00:00:60:69:00:12:53 2 Ready 192.168.100.147 "backup" Primary 10:00:00:60:69:22:32:83 3 Ready 192.168.100.135 "switch" ___________________________________________ Secured switches in the fabric: 3 switch:admin>

secFabricShow: Can only execute this command when secure mode is enabled.
2-227
secmodeshow
Available in Fabric OS versions: Version Differences: Additional Example/Case Studies: Troubleshooting Use: Use this command to display the current security mode of the fabric (enabled or disabled) Use this command to display the current security mode of the fabric. The fabric can be in secure mode or non secure mode. If the fabric is in secure mode, the following information is displayed:

Note:
Version stamp - Displays the current version and build date and time of the security database FCS switches - Displays a list of FCS switches Primary - Displays whether the switch is a Primary FCS or Backup FCS WWN - Displays the WWN of the FCS switch Did - Displays the Domain of the FCS switch swName - Displays the alias name of the FCS switch
Note: When security mode is enabled, this command can be executed on any switch in fabric
Examples Example 2-112:

primaryfcs:admin> secmodeshow Secure Mode: ENABLED. Version Stamp: 9182, Wed Mar 13 16:37:01 2001. POS Primary WWN DId swName. ==================================================== 1 Yes 10:00:00:60:69:00:00:5a 21 SW47. 2 No 12:00:00:60:60:03:23:5b 5 SW12. primaryfcs:admin>
Example 2-113: v4.1 example

secModeShow Secure Mode: DISABLED.

secModeShow: Secure Mode: DISABLED.
2-228
secpolicydump
Available in Fabric OS versions: v3.1 plus, v4.2 plus Troubleshooting Use: Use this command to display the members of an existing policy in the Active and Defined (saved) databases without page breaks. Note: When security mode is enabled, this command can be executed on any FCS switch in fabric.
Examples Example 2-115: To view all security policy information from all databases (active, updating, defined).
primaryfcs:admin> secpolicydump
____________________________________________________
DEFINED POLICY SET FCS_POLICY Pos Primary WWN
DId swName
__________________________________________________
1 Yes 10:00:00:60:69:30:15:5c 1 primaryfcs HTTP_POLICY IpAddr __________________________________________________ 192.155.52.0 __________________________________________________ ACTIVE POLICY SET FCS_POLICY Pos Primary WWN DId swName
__________________________________________________
1 Yes 10:00:00:60:69:30:15:5c 1 primaryfcs HTTP_POLICY IpAddr

__________________________________________________
192.155.52.0 192.155.53.1 192.155.54.2 192.155.55.3

__________________________________________________
primaryfcs:admin>
Example 2-116: To view all security policy information for the TELNET_POLICY without page breaks:
primaryfcs:admin> secpolicydump "*", "TELNET_POLICY"
____________________________________________________
DEFINED POLICY SET TELNET_POLICY IpAddr

__________________________________________________
192.155.52.13 192.155.52.11
_________________________________________________
ACTIVE POLICY SET TELNET_POLICY IpAddr

__________________________________________________
192.155.52.0
__________________________________________________
primaryfcs:admin>

secPolicyDump: Can only execute this command when secure mode is enabled.
2-229
secStatsShow
Available in Fabric OS versions: v3.1 plus, v4.2 plus Troubleshooting Use: Use this command to display security statistic for a policy or for all policies.This command can be issued to any switch. If issued on the Primary FCS switch, this command can retrieve and display the security statistics for any or all switches in the fabric. Note: When security mode is enabled, this command can be issued from any switch in the fabric.
Additional Example/Case Studies:

An ongoing procedure of security is monitoring and auditing logs to identify if violations have occurred at the switch using errShow or at a syslogdIpAdd server. Fabric Watch can be configured to notify when violations have occurred using SNMP, Email, Fabric Manager or SyslogdIpAdd. As an alternative security violations can be viewed using secStatsShow on a per switch basis or for the entire fabric. From the Primary FCS the command secStatsShow can be used to view all violations on all domains or individual violations on a particular domain. If secStatsShow is used on any switch other than the primary FCS only the local violations can be viewed. An example of secStatsShow has been formatted for this document is shown below:
TELNET_POLICY API_POLICY WSNMP_POLICY MS_POLICY FRONTPANEL_POLICY DCC_POLICY INVALID_TS INVALID_CERT SLAP_BAD_PKT NO_FCS ILLEGAL_CMD
0 0 0 0 0 0 0 0 0 0 0
HTTP_POLICY RSNMP_POLICY SES_POLICY SERIAL_POLICY SCC_POLICY LOGIN INVALID_SIGN SLAP FAIL TS_OUT_SYNC INCOMP_DB
0 0 0 0 0 0 0 0 0 0
When a violation has occurred the counter for the policy type will be incremented.
0x10309360 (tReceive): Feb 12 20:44:44 INFO SEC-SECVIOL_DCC, 4, Security violation: Unauthorized device 10:00:00:00:c9:2a:b7:38 tries to flogin to port 7 of switch 10:00:00:60:69:50:06:e4.
Feb 12 20:44:44.733
port 7: Rejecting the FLOGI from 0x020700(10:00:00:00:c9:2a:b7:38) due to security violation
Since a DCC_POLICY was violated, the DCC_POLICY counter incremented from zero to 1
DCC_POLICY 1

secStatsShow: Fabric Statistics: Domain 1: Name Value =========================================
2-230

TELNET_POLICY HTTP_POLICY API_POLICY RSNMP_POLICY WSNMP_POLICY SES_POLICY MS_POLICY SERIAL_POLICY FRONTPANEL_POLICY SCC_POLICY DCC_POLICY LOGIN INVALID_TS INVALID_SIGN INVALID_CERT SLAP FAIL SLAP_BAD_PKT TS_OUT_SYNC NO_FCS INCOMP_DB ILLEGAL_CMD 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
2-231
semaShow
Available in Fabric OS versions: v3.1, v3.1.2 (Port Command Group) v4.2 Example Output: NA Troubleshooting Use: Semashow Example 2-119: v3.1.2 output
semaShow 1
1 is a VX Works command. It shows the semaphores that are currently being held. The example below has no semaphores being held.
Note:
This command has no additional Fabric OS information at this time. As the information becomes available the command will be inserted in this section
2-232
sensorshow
Available in Fabric OS versions: v4.1, v4.2 Troubleshooting Use: Use this command to display sensor readings. Version Differences: Switch 24000 version 4.2 sensorshow output displays sensor information for all slots. Switch 12000 sensorshow information depicted depends on where the command was issued. Read notes under Additional Example / Case Studies Notes. Additional Example/Case Studies Notes: Use this command to display the current temperature, fan and power supply status and readings from sensors located on the switch. The actual location of the sensors varies depending on the switch type. In the SilkWorm 12000, the information returned with sensorshow is specific to the logical switch you are logged into:
If you are logged into Logical switch 0, sensors 1 through 4 are for switch blade slots 1 through 4, respectively. Sensors 5 and 6 are for the two CPs in slots 5 and 6, respectively. If you are logged into Logical switch 1, sensors 1 and 2 are for the two CPs in slots 5 and 6, respectively. Sensors 3 through 6 are for switch blade slots 7 through 10, respectively. If you are logged into the Active CP through the console port, you are prompted to specify the logical switch this command is executed on. If you login to the Active CP through the Fabric OS shell, this command always executes on the default switch (logical switch 0). Regardless of logical switch, sensors 7 through 9 are for the three chassis fans, left to right, and sensors 10 through 13 are for the four chassis power supplies, bottom to top.
Example 2-63: v4.1 example from logical switch 0

sensorshow: sensor 1: (Temperature) sensor 2: (Temperature) sensor 3: (Temperature) sensor 4: (Temperature) sensor 5: (Temperature) sensor 6: (Temperature) sensor 7: (Fan ) sensor 8: (Fan ) sensor 9: (Fan ) sensor 10: (Power Supply sensor 11: (Power Supply sensor 12: (Power Supply sensor 13: (Power Supply is Absent is Ok, value is Ok, value is Absent is Ok, value is Ok, value is Ok, speed is Ok, speed is Ok, speed ) is Ok ) is Ok ) is Ok ) is Ok
is 32 C is 32 C is is is is is 20 C 20 C 2556 RPM 2537 RPM 2481 RPM

sensorshow: sensor 1: (Temperature) sensor 2: (Temperature) sensor 3: (Temperature) sensor 4: (Temperature) sensor 5: (Temperature) sensor 6: (Temperature) sensor 7: (Temperature) sensor 8: (Temperature) sensor 9: (Temperature) sensor 10: (Temperature) sensor 11: (Fan ) sensor 12: (Fan ) sensor 13: (Fan ) sensor 14: (Power Supply sensor 15: (Power Supply sensor 16: (Power Supply sensor 17: (Power Supply is Ok, value is Ok, value is Absent is Ok, value is Ok, value is Ok, value is Ok, value is Ok, value is Ok, value is Ok, value is Ok, speed is Ok, speed is Ok, speed ) is Ok ) is Faulty ) is Ok ) is Faulty is 26 C is 26 C is is is is is is is is is is 26 C 30 C 30 C 26 C 26 C 25 C 26 C 2500 RPM 2481 RPM 2518 RPM
2-233
sfpshow
Available in Fabric OS versions: v4.1, v4.2 Troubleshooting Use: Use this command to display information about Serial Identification SFPs (also known as module definition 4 SFPs). These SFPs provide extended information that describes the SFPs capabilities, interfaces, manufacturer, and other information. Note: SFPs are polled by a background process. The sfpshow command retrieves the latest information from cache. The cache values for each SFP are updated when the SFP is hot plugged, when it is removed, or when the Fabric OS polls the SFPs. In the SilkWorm 12000, if there is a lot of activity on the switch, poll updates may take several minutes. Use this command with no operand to display a summary of all SFPs in the switch. The summary shows the SFP type (see switchshow for an explanation of the two letter codes) and, for Serial ID SFP, the vendor name and SFP serial number. Use this command with the slot and portnumber operand to display detailed information about the Serial ID SFP in that port. For Finisar smart SFPs, five additional fields are displayed: module temperature, voltage, received optical power, transmitted optical power (longwave only), and laser diode drive current.
Example 2-64: The example below shows SFP summary information followed by detailed information for an SFP: This example shows detailed SFP information for a SilkWorm 12000:
switch:admin> sfpshow Area 0: id (sw) Vendor: AGILENT Serial No: A00149567 Area 1: id (sw) Vendor: AGILENT Serial No: A00108650 Area 2: id (sw) Vendor: AGILENT Serial No: A00149568 Area 3: id (sw) Vendor: AGILENT Serial No: A00108567 Area 4: id (sw) Vendor: AGILENT Serial No: A00152395 Area 5: id (sw) Vendor: AGILENT Serial No: A00149623 Area 6: id (sw) Vendor: AGILENT Serial No: A00152423 Area 7: id (sw) Vendor: AGILENT Serial No: A00108932 Area 8: id (sw) Vendor: AGILENT Serial No: A00111165 Area 9: id (sw) Vendor: AGILENT Serial No: A00079899 Area 10: id (sw) Vendor: AGILENT Serial No: A00079319 Area 11: id (sw) Vendor: AGILENT Serial No: A00079917 Area 12: id (sw) Vendor: AGILENT Serial No: A00079274 Area 13: id (sw) Vendor: AGILENT Serial No: A00079348 Area 14: id (sw) Vendor: AGILENT Serial No: A00079843 Area 15: id (sw) Vendor: AGILENT Serial No: A00150114 Area 16: id (sw) Vendor: AGILENT Serial No: A00079337 Area 17: id (sw) Vendor: AGILENT Serial No: A00148599 Area 18: id (sw) Vendor: AGILENT Serial No: A00079856 Area 19: id (sw) Vendor: AGILENT Serial No: A00079937 Area 20: id (sw) Vendor: AGILENT Serial No: A00079832 Area 21: id (sw) Vendor: AGILENT Serial No: A00079835 Area 22: id (sw) Vendor: AGILENT Serial No: A00079332 Area 23: id (sw) Vendor: AGILENT Serial No: A00079852 Area 24: id (sw) Vendor: AGILENT Serial No: A00148593 Area 25: id (sw) Vendor: AGILENT Serial No: A00084645 Area 26: id (sw) Vendor: AGILENT Serial No: A00079381 Area 27: id (sw) Vendor: AGILENT Serial No: A00084644 Area 28: id (sw) Vendor: AGILENT Serial No: A00084654 Area 29: id (sw) Vendor: AGILENT Serial No: A00079318 Area 30: id (sw) Vendor: AGILENT Serial No: A00079848 Area 31: id (sw) Vendor: AGILENT Serial No: A00079356 switch:admin>
Note:
Additional sfp information can be gathered per port from the CLI using sfpshow <slot / port #>
2-234

switch:admin> sfpshow 1/3 Identifier: 3 SFP Connector: 7 LC Transceiver: 050c402000000000 100,200_MB/s M5,M6 sw Inter_dist Encoding: 1 8B10B Baud Rate: 21 (units 100 megabaud) Length 9u: 0 (units 100 meters) Length 50u: 30 (units 10 meters) Length 625u: 13 (units 10 meters) Length Cu: 0 (units 1 meter) Vendor Name: FINISAR CORP. Vendor OUI: 00:90:65 Vendor PN: FTRJ-8519-3-2.5 Vendor Rev: X1 Options: 0012 Loss_of_Sig,Tx_Disable BR Max: 0 BR Min: 0 Serial No: H112YFR Date Code: 010418

sfpshow: Area 0: Area 1: Area 2: Area 3: Area 4: Area 5: Area 6: Area 7: Area 8: Area 9: Area 10: Area 11: Area 12: Area 13: Area 14: Area 15: Area 16: Area 17: Area 18: Area 19: Area 20: Area 21: Area 22: Area 23: Area 24: Area 25: Area 26: Area 27: Area 28: Area 29: Area 30: Area 31: Area 48: Area 49: Area 50: Area 51: Area 52: Area 53: Area 54: -id ---id ----id -----id ----id ----id ----id ---id id ---
(sw) Vendor: FINISAR CORP.
Serial No: H11XTJK
Serial No: H11S8Z5
Serial No: H11AUVX
Serial No: H11ATDD
Serial No: H11ASFL
Serial No: H11ATMT
Serial No: H115AFQ
(sw) Vendor: FINISAR CORP. (sw) Vendor: FINISAR CORP.
Serial No: P119QYF Serial No: H11QVNF
2-235
2
Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area Area

55: -56: -57: -58: -59: id (sw) Vendor: FINISAR CORP. 60: -61: -62: -63: id (sw) Vendor: FINISAR CORP. 64: -65: -66: -67: -68: -69: -70: -71: -72: -73: id (sw) Vendor: FINISAR CORP. 74: -75: id (sw) Vendor: FINISAR CORP. 76: -77: -78: -79: -80: -81: -82: -83: -84: -85: -86: id (sw) Vendor: FINISAR CORP. 87: -88: -89: -90: -91: -92: -93: -94: id (sw) Vendor: FINISAR CORP. 95: -96: -97: -98: -99: -100: id (sw) Vendor: FINISAR CORP. 101: -102: -103: -104: -105: -106: id (sw) Vendor: FINISAR CORP. 107: -108: -109: -110: -111: -112: -113: -114: id (sw) Vendor: FINISAR CORP. 115: -116: -117: -118: -119: --
Serial No: H112TX1
Serial No: H1172TF
Serial No: H11GD8N Serial No: H116Q91
Serial No: H112TPP
Serial No: H117F6F
Serial No: H11S8S2
Serial No: H115AE4
Serial No: H11UFE2
2-236

Area Area Area Area Area Area Area Area 120: 121: 122: 123: 124: 125: 126: 127: -----id (sw) Vendor: FINISAR CORP. -id (sw) Vendor: FINISAR CORP.
Serial No: H11AUFM Serial No: H112T3N
2-237
slotShow
Available in Fabric OS versions: 4.0.2c Additional Example/Case Studies: Troubleshooting Use: Use this command to displays slot status Example 2-65: Use this command to inventory and display the current status of each slot in the system.
slotshow Slot Blade Type ID Status --------------------------------1 UNKNOWN VACANT 2 UNKNOWN VACANT 3 SW BLADE 2 ENABLED 4 SW BLADE 2 FAULTY 5 CP BLADE 1 ENABLED 6 CP BLADE 1 ENABLED 7 SW BLADE 2 ENABLED 8 SW BLADE 2 ENABLED 9 UNKNOWN VACANT 10 UNKNOWN VACANT
The format of the display includes a header and four fields for each slot. The fields and their possible values are as follows: Slot SW BLADE CP BLADE UNKNOWN ID Status VACANT Displays the physical slot number. The blade is a Switch. The blade is a Control Processor. Blade not present or its type is not recognized. Displays the hardware ID of the blade type. Displays the status of the blade:
The slot is empty.
Blade Type Displays the blade type:
INSERTED, NOT POWERED ON The blade is present in the slot but is turned off. DIAG RUNNING POST1 The blade is present, powered on, and running the post initialization power on self tests. DIAG RUNNING POST2 The blade is present, powered on, and running the POST (power on self tests). ENABLED The blade is on and enabled. DISABLED The blade is powered on but disabled. FAULTY The blade is faulty because an error was detected. UNKNOWN The blade is inserted but its state cannot be determined.
Note:
Check this when there are blade/ bloom errors in the errlog or if the customer reports a blade down. Also use this to check that both CPs are up and running. See additional notes in V4.1 slotshow output information.

slotshow: Slot Blade Type ID Status --------------------------------1 SW BLADE 4 ENABLED 2 SW BLADE 4 ENABLED 3 UNKNOWN VACANT 4 SW BLADE 4 ENABLED 5 CP BLADE 5 ENABLED 6 CP BLADE 5 ENABLED 7 SW BLADE 4 ENABLED
2-238

8 9 10 SW BLADE SW BLADE SW BLADE 4 4 4 ENABLED ENABLED ENABLED
2-239
supportshowcfgshow
Available in Fabric OS versions: v3.1, v3.2, v4.1, v4.2 Additional Example/Case Studies: Troubleshooting Use: Use this command to display groups of commands enabled for display Use this command to display the groups of commands enabled for display by the supportshow command. Use the supportshowcfgenable and the supportshowdisable commands to modify which groups are displayed. Example 2-123:
switch:admin> supportshowcfgshow portlog enabled os enabled exception enabled port enabled fabric enabled services enabled security enabled network enabled system enabled extend disabled filter disabled perfmon disabled
Note:
As of ver 3.1/4.1 plus supportshow outputs can be enabled or disabled per group.
2-240
switchShow
Available in Fabric OS versions: All Version Differences: Slotted switches will display slot and port columns. Troubleshooting Use: Use this command to display switch and port status. A good port state (online) will tell you that you have a good link. A device that comes in as expected (L-Port, F_Port or E_Port) lets you know that a good connection exchange occurred. Use this command to display switch and port status information. Information may vary by switch model. Below is the information provided. The first section provides switch summary information; it is followed by a section covering summary information by port. Switch summary information: switchName switchType switchState switchMode switchRole switchDomain switchId switchWwn switchBeacon Displays the switch symbolic name. Displays the switch model and firmware revision number. See switchType notes below Displays the switch state: online, offline, testing, faulty. Displays the switch mode: native, interop. This value is only displayed in v3.0. Displays the switch role: principal, subordinate, disabled. Displays the switch domain ID: 0-31 or 1-239. Displays the switch embedded port D_ID. See switchId notes below Displays the switch worldwide name. Displays the switch's beaconing state (either ON or OFF).
blade_n:Beacon Displays the blades beaconing state (either ON or OFF). Each blade is numbered by its position in the Silkworm 12000 chassis (from 1 to 10). This parameter is for v4.0 only. Zoning Displays the switch zoning mode: On or Off. This value is only displayed in v3.0. switchType <model_type>.<motherboard_revision_level> The model types are as follows: 1 = Brocade SilkWorm 1000; 2 = Brocade SilkWorm 2800; 3 = Brocade SilkWorm 2400; 4 = Brocade SilkWorm 20x0; 5 = Brocade SilkWorm 22x0; 9 = Brocade SilkWorm 3800; 10 = Brocade SilkWorm 12000; 16 = Brocade SilkWorm 3200; 12 = Brocade SilkWorm 3900; 21 = Brocade 24000; 26 = Brocade 3250; & 27 = Brocade 3850. The motherboard revision level varies per type. The switchId, embedded port and domain controller all refer to the switches Fabric services functionality. The domain controller is responsible for all communication to/from Well-Known addresses: FF FF FF = Broadcast; FF FF FE = Fabric Login; FF FF FD = Fabric Controller; FF FF FC = Directory Server; FF FF FB = Time Server; FF FF FA = Management Server; FF FF F9 = Quality of Service Facilitator; FF FF F8 = Alias Server (FC-PH2); FF FF F7 = Security Key Distribution Server; FF FF F6 = Clock Synchronization Server; FF FF F5 = Multicast Server; FF FF F4 - FF FF F0 = reserved. See the Decoding Reference Guide for additional information, search for Well-Known Addresses. The switch summary is followed by one line per port: Area Each slot and port combination in the Silkworm 12000 is assigned an area number. For example, the area number of slot 3/port 15 is 63 (in switch 0), the area number for slot 10/port 15 is also 63 (in switch 1). This parameter is for v4.0 only. The Silkworm 12000 has 10 slots numbered from 1 to 4 and 7 to 10. Slots 5 and 6 are control processor cards. This parameter is for v4.0 only. Valid values vary depending on the switch type. The Silkworm 12000 has 16 ports per slot, and ports are numbered from 0 to 15. no module present shortwave laser longwave laser copper serial ID
Slot number. Port number.
SFP Port module type (SFP or other): -sw lw cu id
2-241
2
1G 2G N1 N2 AN
Speed The speed of the port: 1G per second fixed transfer speed 2G per second fixed transfer speed 1G per second negotiated transfer speed 2G per second negotiated transfer speed Auto negotiating
Port state information: No_Card No_Module No_Light No_Sync In_Sync Laser_Flt Port_Flt Diag_Flt Lock_Ref Testing Online Comment: Disabled Bypassed Loopback Note: no interface card present no module (SFP or other) present module not receiving light module receiving light but out of sync module receiving light and in sync module signaling a laser fault port marked faulty port failed diagnostics locking to the reference signal running diagnostics port is up and running The comment field may be blank, or it may display: port is disabled port is bypassed (see bypassed notes below) port is in loopback mode
A port in bypass state means that it is not ready for some reason. A port could go into bypass state: while the switch is booting up and a device tries to log in the switch port not ready may cause it to go into bypass mode; it goes into bypass mode when a device is continually logging in and the switch port gets confused; or when a host runs a script that on the fly takes down the HBA's driver and alternates the topology setting too rapidly.
Additional port information: E_port F_port G_port L_port (Trunk master) (upstream) (downstream) WWN Lx fabric port, shows WWN and name of attached switch point-to-point port, shows WWN of attached N_port point-to-point but not yet E_port or F_port loop port, shows number of NL_ports This port is the master port in a group of trunking ports This E-port is an upstream path towards the principal switch of the fabric. This E-port is a downstream path away from the principal switch of the fabric. This is the WWN of the switch connected to the E-port. switch_name - This is the switch name of the connected switch. if a port is configured as a long distance port, the long distance level is shown in the format of Lx, x being the long distance level number. See portCfgLongDistance for the level description.
(Trunk port, master is port #x) This port is configured as a trunking port, the master port is port number x.
When a port is configured as a long distance port like port 0, the long distance level is shown in the format of Lx, x being the long distance level number.
2-242
Fabric OS SupportShow Information x = L0: deconfigure the port - regular switch port. Port supports up to 10 km links.
x = LE: level one half long distance, up to 25 km. A total of 13/19 (1G/2G) full-size frame buffers will be reserved for the port. x = L0.5: level one half long distance, up to 25 km. A total of 19/34 (1G/2G) full-size frame buffers will be reserved for the port. L0.5 capability was introduced in V3.1/4.1 x = L1: level one long distance, up to 50 km. A total of 27/54 (1G/2G) full-size frame buffers will be reserved for the port. x = L2: level two long distance, up to 100 km. A total of 60/63 (1G/2G) full-size frame buffers will be reserved for the port. x = LD: level three long distance, from 10 to 100 km. A total of 13-60/19-63 (1G/2G) full-size frame buffers will be reserved for the port according to the distance actually established. LD capability was introduced in V3.1/4.1. The D in LD stands for dynamic. Configure a port as a long distance port with portCfgLongDistance [slot/]port [,distance_level], <VC Translation Link Init> command. Notice the extended Fabric (LE) output slot 1/port 1 in the Example 2-77 port 1 below. Note: Brocade Switch WWN's can be used to identify the types of switches in the fabric from the fabricshow output.
WWN by product (look at the last 6 digits of the WWN, this is subject to change) 10:00:00:60:6910:xx:xx through 4F:xx:xx -> 2x00 series 10:00:00:60:6950:xx:xx -> 3800 switch 10:00:00:60:6951:xx:xx -> 3200 switch 10:00:00:60:6980:xx:xx -> 12000 switch 10:00:00:60:6990:xx:xx -> 3900 switch 10:00:00:05:1e:xx:xx:xx -> 3x50 switch v4.1 Example Output: Example 2-66:
switchName:sw0 switchType:10.1 switchState:Online switchRole:Principal switchDomain:1 switchId:fffc01 switchWwn:10:00:00:60:69:80:04:b2 switchBeacon:OFF blade1 Beacon:OFF blade2 Beacon:OFF Area Slot Port Gbic Speed State ===================================== 0 1 0 id N2 No_Light 1 1 1 id N2 No_Light LE 2 1 2 id N2 No_Light 3 1 3 -N2 No_Module 4 1 4 -N2 No_Module 5 1 5 -N2 No_Module 6 1 6 -N2 No_Module 7 1 7 -N2 No_Module 8 1 8 -N2 No_Module 9 1 9 -N2 No_Module
2-243
2
10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 10 11 12 13 14 15 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 id id id id id -id id --------id -id -id -N2 N2 N2 N1 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 Online F-Port No_Light No_Light Online L-Port No_Light No_Module No_Light No_Light No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Light No_Module No_Light No_Module No_Light No_Module 10:00:00:00:c9:2a:6b:3b
27 public
Note:
If your having trouble seeing a device in a Fabric switchshow is still one of the first commands to type. It will let you know the link status of a port and the switch. Until a port comes in with a port state of online or in sync on a online switch (switch state online), it has no hope of the Fabric seeing it. If the Fabric doesnt see it, other devices in the Fabric sure wont see it! If everything looks good here (online portstate and device comes in as F or L as expected, then check the name server databases (local: nsShow; global/24 bit address only; remote detail: nscamShow) and zoning (cfgshow) to make sure the device is seen in the entire Fabric and is in the same zone as device trying to access it.

switchshow: switchName:SW24000_32 switchType:21.0 switchState:Online switchMode:Native switchRole:Principal switchDomain:1 switchId:fffc01 switchWwn:10:00:00:60:69:80:2d:4a zoning: OFF switchBeacon:OFF blade1 Beacon: OFF blade2 Beacon: OFF blade4 Beacon: OFF blade7 Beacon: OFF blade8 Beacon: OFF blade9 Beacon: OFF blade10 Beacon: OFF Area Slot Port Media Speed State ===================================== 0 1 0 -N2 No_Module 1 1 1 id N2 Online F-Port 2 1 2 -N2 No_Module 3 1 3 -N2 No_Module 4 1 4 -N2 No_Module 5 1 5 id N2 No_Light 6 1 6 -N2 No_Module
10:00:00:00:c9:29:06:7d
2-244

7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 8 8 8 8 8 8 8 8 7 8 9 10 11 12 13 14 15 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0 1 2 3 4 5 6 7 ---id -----id ----id ----id ----id ---id id ------id ---id ---------id -id ----------id -N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 No_Module No_Module No_Module No_Light No_Module No_Module No_Module No_Module No_Module No_Light No_Module No_Module No_Module No_Module No_Light No_Module No_Module No_Module No_Module No_Light No_Module No_Module No_Module No_Module No_Light No_Module No_Module No_Module No_Light No_Light No_Module No_Module No_Module No_Module No_Module No_Module No_Light No_Module No_Module No_Module No_Light No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Light No_Module No_Light No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Light No_Module
2-245
2
88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127

8 8 8 8 8 8 8 8 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 8 9 10 11 12 13 14 15 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ------id -----id -----id -------id ----------id -id N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 N2 No_Module No_Module No_Module No_Module No_Module No_Module Online F-Port No_Module No_Module No_Module No_Module No_Module No_Light No_Module No_Module No_Module No_Module No_Module No_Light No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Light No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Module No_Light No_Module Online L-Port
10:00:00:00:c9:2b:7f:90
15 public
2-246
switchstatuspolicyshow
Available in Fabric OS versions: v4.1, v4.2 Version Differences: This command can be invoked from all Fabric OS versions from the CLI. The outputs depicted will depend on the capability of the platform. Additional Example/Case Studies: Troubleshooting Use: Use this command to display the policy parameters that determine the overall switch status.These policy parameters determine the number of failed or non-operational units allowed for each contributor before triggering a status change in the switch. The command will print the current parameters in a three column table format. The first column specifies the contributor; the second column specifies the minimum number that contributes to the DOWN/FAILED status; the third column specifies the minimum number that contributes to the MARGINAL/WARNING status. The default values for the policy parameters are as follows: The policy parameters determine the number of failed or non-operational units for each contributor that trigger a status change in the switch. For example, if the FaultyPorts DOWN parameter is set to 3, and 3 ports fail in the switch, then the status of the switch changes to DOWN. Example 2-67: v4.1 output
switchstatuspolicyshow: The current overall switch status policy parameters: Down Marginal ---------------------------------FaultyPorts 2 1 MissingSFPs 0 0 PowerSupplies 2 1 Temperatures 2 1 Fans 2 1 PortStatus 0 0 ISLStatus 0 0
Note:
switchstatuspolicyshow settings determine the overall switch status depicted as either healthy, marginal or faulty (down). Associated error log messages can be viewed in errdump output. These messages will be more descriptive if FW is installed. If FW isnt installed, the FW error reporting mechanism will report switchstatuspolicyshow status as follows:
errDump 0/MARGINAL/WARNING TO/FROM HEALTHY/OK ARE NOT TOO HELPFUL WITHOUT A FW LICENSE BUT NOTICE TIMINGS.... MARGINAL/WARNING TO HEALTHY/OK ~ 2 - 4 SECONDS, VERY CONSISTENT WITH A DEVICE GOING OFFLINE AND COMING BACK IN..THESE SAME ERROR MESSAGE CYCLES APPEAR FOR ALL 64 ERROR MESSAGE OUTPUTS ON THIS SWITCH. Error 64 -------0x101274c0 (tThad): May 31 03:16:51 WARNING FW-STATUS_SWITCH, 3, Switch status changed from Marginal/Warning to HEALTHY/OK Error 63 -------0x101274c0 (tThad): May 31 03:16:48 WARNING FW-STATUS_SWITCH, 3, Switch status changed from HEALTHY/OK to Marginal/Warning Error 62 -------0x101274c0 (tThad): May 31 03:16:45 WARNING FW-STATUS_SWITCH, 3, Switch status changed from Marginal/Warning to HEALTHY/OK Error 61 -------0x101274c0 (tThad): May 31 03:16:41 WARNING FW-STATUS_SWITCH, 3, Switch status changed from HEALTHY/OK to Marginal/Warning
2-247
2
Note:
With FW installed the error messages are much more informative, they will tell you what is causing the switch to go marginal.

switchstatuspolicyshow: The current overall switch status policy parameters: Down Marginal ---------------------------------FaultyPorts 2 1 MissingSFPs 0 0 PowerSupplies 3 0 Temperatures 2 1 Fans 2 1 PortStatus 0 0 ISLStatus 0 0 CP 0 1 WWN 0 1 Blade 0 1
Note:
Version 4.2 added WWN and blades to the policy list. This allows the status of the WWN and switch blades to be reported.
2-248
switchstatusshow
Available in Fabric OS versions: v4.1, v4.2 Troubleshooting Use: Use this command to display the overall status of the switch. The overall status is calculated based on the most severe status of all contributors:
Internal Switch Status Faulty Ports Missing SFPs Power Supplies Fans Temperatures Port Status
The overall status can be one of the following: Healthy/OK - every contributor is healthy Marginal/Warning - one or more components are causing a warning status Down/Failed - one or more contributors have failed
If the overall status is not HEALTHY/OK, the contributing factors are listed. Examples: There are two examples below. The first shows a switch with a status of MARGINAL, the second shows the same switch after all the errors have been fixed. Example 2-68:
switch:admin> switchstatusshow The overall switch status is Marginal/Warning Contributing factors: * 1 missing power supply triggered the Marginal/Warning status * 1 bad fans, 2 good fans triggered the Marginal/Warning status * 1 missing SFP triggered the Marginal/Warning status switch:admin> switchstatusshow The overall switch status is HEALTHY/OK
Example 2-69:
switchstatusshow: The overall switch status is HEALTHY/OK
Note:
switchstatuspolicyset and fruconfig (where applicable) parameters determine switchstatus output.

switchstatusshow: The overall switch status is Marginal/Warning Contributing factors: * power supplies are not in the correct slots triggered the Marginal/Warning status
2-249
sysc_dprintf
Available in Fabric OS versions: v4.1, v4.2 - this command is a subset of the hadump command Additional Example/Case Studies: Troubleshooting Use: Use this command to display information about the status of the High Availability features in the switch particularly during failover or firmwaredownload processes Note: See hadump output information in this guide for additional information and a story related to the sysc_dprintf command that depicts an hafailover and the different outputs displayed from the original Active and Standby CPs.

sysc_dprintf: FSSME registered: TRUE FSSME ready: TRUE Event HA state: HA_ACCEPT_YIELD_CTRL Event head: 21, Event tail: 21 EVT_FSSME_REG:COMPLETED EVT_FSSME_READY:COMPLETED EVT_LOAD_REPLY:COMPLETED EVT_SVC_STANDBY:COMPLETED EVT_LOAD_REPLY:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_SVC_STANDBY:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_TAKE_CONTROL:COMPLETED EVT_SVC_ACTIVE:COMPLETED EVT_SVC_ACTIVE:COMPLETED EVT_BLADE_LIST:COMPLETED EVT_BLADE_LIST:COMPLETED cmd_tail = 4, cmd_head = 4 CMD_START_DEFAULT:COMPLETED CMD_BLADELIST_START:COMPLETED CMD_TAKE_CONTROL:COMPLETED CMD_BLADELIST_START:COMPLETED Service name: fcsw Service instance 0, state SI_ST_ACTIVE, refcnt 10 Service name: fcsw Service instance 1, state SI_ST_UNLOADED, refcnt 0 Service name: chassis Service instance 0, state SI_ST_ACTIVE, refcnt 10 Slot 1:Bladeid 0x04,SYSC_BLADE_ACTION_DONE Slot 2:Bladeid 0x04,SYSC_BLADE_ACTION_DONE Slot 4:Bladeid 0x04,SYSC_BLADE_ACTION_DONE Slot 5:Bladeid 0x05,SYSC_BLADE_ACTION_DONE Slot 6:Bladeid 0x05,SYSC_BLADE_ACTION_DONE Slot 7:Bladeid 0x04,SYSC_BLADE_ACTION_DONE Slot 8:Bladeid 0x04,SYSC_BLADE_ACTION_DONE Slot 9:Bladeid 0x04,SYSC_BLADE_ACTION_DONE
2-250
tcpstatshow
Available in Fabric OS versions: v3.x non-supportshow Network Command Group Troubleshooting Use: Use this command along with other network command group commands to display the transmission Control Protocol statistics for the Ethernet connection(s) to switch. Example 2-128: To display the Transmission Control Protocol statistics
SW3800_12:admin> tcpstatshow TCP: 523 packets sent 514 data packets (105265 bytes) 0 data packet (0 byte) retransmitted 9 ack-only packets (8 delayed) 0 URG only packet 0 window probe packet 0 window update packet 0 control packet 1060 packets received 454 acks (for 105266 bytes) 7 duplicate acks 0 ack for unsent data 305 packets (426 bytes) received in-sequence 0 completely duplicate packet (0 byte) 0 packet with some dup. data (0 byte duped) 0 out-of-order packet (0 byte) 0 packet (0 byte) of data after window 0 window probe 0 window update packet 0 packet received after close 0 discarded for bad checksum 0 discarded for bad header offset field 0 discarded because packet too short 0 connection request 1 connection accept 1 connection established (including accepts) 4 connections closed (including 0 drop) 1 embryonic connection dropped 419 segments updated rtt (of 419 attempts) 0 retransmit timeout 0 connection dropped by rexmit timeout 0 persist timeout 7 keepalive timeouts 7 keepalive probes sent 0 connection dropped by keepalive
network Command Group: ipAddrShow ifShow ipstatShow udpstatShow tcpstatShow inetstatshow mbufShow arpShow routeShow routestatShow hostShow feiDumpPrint i557Dump feiIterateRFDRings
2-251
tempShow
Available in Fabric OS versions: All Version Differences: The number of temperature sensors depends on the hardware platform. Troubleshooting Use: Use this command to display internal temperature information Use this command to display the current temperature readings of all temperature sensors in a switch. Each temperature sensor has an index. The indices start from 1. There can be more than one sensor per slot. The slot number to which a sensor belongs is displayed in the column next to the index. The temperature readings are given in both Centigrade and Fahrenheit. The temperatures listed by this command are the temperature sensor values and do not represent the ambient temperature operating range listed in the Hardware Reference Manual for your switch. Example 2-70: #5
tempshow: IndexSlotState Centigrade Fahrenheit ========================================================= 1 1 Ok 41 105 2 2 Ok 37 98 3 3 Absent 4 4 Absent 5 5 Ok 25 77 6 6 Ok 27 80
Note:
These readings represent internal temperature sensors on the main board. Internal temperature sensors will cause shut down at or above 70 Celsius (158 Fahrenheit). Also verify that the ambient or external air temperature does not exceed 40 Celsius (104 Fahrenheit) while the switch is operating.
If you suspect a temperature problem, possibly because of intermittent error, check chassisshow for extra power being consumed anywhere. Also check errshow output for temperature related messages.

tempshow: IndexSlotStateCentigrade Fahrenheit ===================================================== 1 1 Ok 26 78 2 2 Ok 26 78 3 3 Absent 4 4 Ok 26 78 5 5 Ok 30 86 6 6 Ok 30 86 7 7 Ok 26 78 8 8 Ok 26 78 9 9 Ok 25 77 10 10 Ok 26 78
2-252
timeout
Available in Fabric OS versions: v4.2 Version Differences: All Fabric OS versions after 3.0/4.0 have CLI timeout capability Troubleshooting Use: Use this command to set or show the IDLE timeout value for a login session. Use this command with no operands to display the current telnet timeout value. Use this command with an operand to sets the idle timeout value to the specified minutes. Using a timeout value of zero will disable the timeout functionality so that login sessions would never be disconnected. Example 2-71: To set the idle timeout to 10 minutes:
switch:admin> timeout 10 IDLE Timeout Changed to 10 minutes The modified IDLE Timeout will be in effect after NEXT login switch:admin> Example: timeout: Current IDLE Timeout is 60 minutes

timeout: Current IDLE Timeout is 10 minutes
2-253
topologyShow
Available in Fabric OS versions: Version Differences: This command output has the same information in it as v3.x topologyshow but v4.x format is quit a bit different. Troubleshooting Use: Use this command to display the unicast fabric topology This command displays the fabric topology, as seen by the local switch. The fabric topology consists of a list of all domains that are part of the fabric, and for each of those domains, of all the possible paths to reach it from the local switch. For each path the cost, the number of hops from the local switch to the destination switch, and a summary of all ports are routed through that path. A path is described by the output port that a frame addressed to a certain domain will be forwarded to by the switch routing hardware, in order to reach the domain. With the domain number specified, this command displays the topology information for the specified destination domain The display shows the following fields: Local Domain ID:The domain number of the local switch. Domain: Metric: Name: Path Count: Hops: Out Port: In Ports: The domain number of the destination switch. The cost of reaching the destination domain. The name of the destination switch. The number of currently active paths to the destination domain The maximum number of hops required to reach the destination domain. The port that an incoming frame will be forwarded to, in order to reach the destination domain. Input ports that use the corresponding Out Port to reach the destination domain. This is the same information provided by portrouteshow and urouteshow Always a 'D', indicating a dynamic path. A dynamic path is discovered automatically by the FSPF(TM) path selection protocol.
Total Bandwidth: The maximum bandwidth (in Gb/s) of the out port. Flags:
v3.x Example Output: Example 2-72:

switch:admin> topologyShow 6 domains in the fabric; Local Domain ID: 11 Domain Metric Hops Out Port In Ports Flags Bandwidth Name ----------------------------------------------------------------------6 500 1 1 0x0000bdfc D 4 (Gbs) "cfs001a" 7 500 1 15 0x00003dfe D 4 (Gbs) "cfs001b" 13 1000 2 1 0x00002d48 D 4 (Gbs) "efs003" 15 0x000010b4 D 4 (Gbs) 15 1000 2 1 0x0000bdfc D 4 (Gbs) "efs005" 17 1000 2 15 0x00003dfe D 4 (Gbs) "efs007"
Note:
This shows that local domain 11 is in a Fabric with 5 other switches, two of those switches are directly connected or neighbor switches to domain 11 because there is 1 Hop to each of these neighbor switches (domain 6 efs001and domain 7 efs001b. A Hop is an ISL (inter switch link) that connects two switches. Neighbor switches pass frames to the other domains that are 2 hops away (domain 13 cfs003, domain 15 efs 005 and domain 17 efs007).
2-254
Starting with the 1st line from domain 11 to domain 6: notice that the metric (also called linkcost) is 500. 500 is the default metric or linkcost of a 2Gbyte/sec ISL connection. Use the linkcost command to display linkcost settings. This metric of 500 is associated with 1 hop so there is only 1 ISL in the path from domain 11 to domain 6. The output port that is connected to domain 6 is port 1. The input ports that were dynamically routed to output port 1 are depicted in bit map 0x0000bdfc. Start by changing 0x0000bdfc into its binary equivalent and then read the toggled bits from right to left as input ports:
b 0 1 1 1 4 3 1 1 2
d 1 1 1 1 1 0
NA
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5
0 1 1 1 1 1 1 1 0 0 IN 0 0 0 0 0 0 0 0 0 0 Ports 9 8 7 6 5 4 3 2 1 0
In this case ports 2-8, 10 13 and 15 were all mapped to output port 1

RSL_SWT121:admin> topologyshow 4 domains in the fabric; Local Domain ID: 2 Domain: 1 Metric: 1500 Name: RSL_SWT129 Path Count: 1 Hops: 3 Out Port: 4/11 In Ports: 4/1 Total Bandwidth: 8 Gbps Bandwidth Demand: 25 % Flags: D Domain: 153 Metric: 500 Name: RSL_SWT153 Path Count: 1 Hops: 1 Out Port: 4/11 In Ports: 4/1 Total Bandwidth: 8 Gbps Bandwidth Demand: 25 % Flags: D Domain: 157 Metric: 1000 Name: RSL_SWT157 Path Count: 1 Hops: 2 Out Port: 4/11 In Ports: 4/1 Total Bandwidth: 8 Gbps Bandwidth Demand: 25 % Flags: D
Note:
The output in Example 2-84 and Example 2-85 shows the local domain 2 going to 3 other domains: 1, 153 and 157. The neighbor switch is domain 153 because there is only one hop between it and the local domain (switch, since each switch must have a unique domain id). All communication from this local domain to the others in the Fabric occurs through this neighbor switch. Slot 4/ port 1 is routed to slot 4/ port 11 to get to its neighbor, domain 153. Domain 157 is directly connected to domain 153 because it is two hops away from the local domain.
2-255
Fabric OS SupportShow Information Since domain 1 is 3 hops away and the only other switch in the Fabric, it must be connected to domain 157. All domains have dynamic flags, so no static routing has been set going out from slot 4/port 11. The total bandwidth is 8 Gbps so slot 4/ port 11 must be the trunk master for a 4 ISL trunk. Each ISL in a 4 ISL trunk would have a maximum bandwidth potential of 25%, the total bandwidth being split across all 4 ISLs. Here are some supporting captures from the same switch at approximately the same time stamp: Example 2-74:
RSL_SWT133:admin> version Kernel: 2.4.2 Fabric OS: v4.0.2b Made on: Wed Oct 30 01:43:47 2002 Flash: Wed Feb 5 22:02:29 2003 BootProm: 3.1.18 RSL_SWT121:admin> fabricshow Switch ID Worldwide Name Enet IP Addr FC IP Addr Name ------------------------------------------------------------------------1: fffc01 10:00:00:60:69:80:05:1c 10.255.255.129 0.0.0.0 "RSL_SWT129" 2: fffc02 10:00:00:60:69:80:04:5e 10.255.255.121 0.0.0.0 "RSL_SWT121" 153: fffc99 10:00:00:60:69:50:0d:d6 10.255.255.153 0.0.0.0 "RSL_SWT153" 157: fffc9d 10:00:00:60:69:51:2d:57 10.255.255.157 0.0.0.0 >"RSL_SWT157" The Fabric has 4 switches RSL_SWT121:admin> switchshow switchName:RSL_SWT121 switchType:10.1 switchState:Online switchRole:Subordinate switchDomain:2 switchId:fffc02 switchWwn:10:00:00:60:69:80:04:5e switchBeacon:OFF blade3 Beacon:OFF blade4 Beacon:OFF Area Slot Port Gbic Speed State ===================================== 32 3 0 id N2 No_Light < truncated output > 48 4 0 id N2 No_Light 49 4 1 id N2 Online F-Port 10:00:00:00:c9:2a:b5:43 50 4 2 id N2 No_Light < truncated output > 55 4 7 id N2 No_Light 56 4 8 id N2 Online E-Port (Trunk port, master is Slot 4 Port 57 4 9 id N2 Online E-Port (Trunk port, master is Slot 4 Port 58 4 10 id N2 Online E-Port (Trunk port, master is Slot 4 Port 59 4 11 id N2 Online E-Port 10:00:00:60:69:50:0d:d6 "RSL_SWT153" master) 60 4 12 id N2 No_Light 61 4 13 id N2 No_Light 62 4 14 id N2 No_Light
11) 11) 11) (upstream)(Trunk
63
15
id
N2
No_Light
Note:
How do we use this information? The supportShow, nsallshow output and topology information depicted here and on subsequent switches in the Fabric can be used to draw the Fabric. This helps verify that the customer drawings match what is actually shown. Information here can also be used in conjunction with portperfshow to determine if ISLs are being over used, or experiencing realized over subscription.
v4.2 Example Consistent Output: Example 2-131:

topologyshow 1 domains in the fabric; Local Domain ID: 1
2-256
traceshow
Note: This command has no additional Fabric OS information at this time. As the information becomes available the command will be inserted in this section.
Troubleshooting Use: Use this command for internal debugging purposes Available in Fabric OS versions: v3.x v4.2 Example Output: NA Additional Example/Case Studies: Example outputs with some embedded notes: Example 2-132:
Traceshow Switch:root> traceshow [INDX] TIME FROM TO ---------------------------------------------[24] Dec 29 03:11:11.066unknown tSwitch 0x101ca8500x103bbb00 120080
Note:
Is 120 and 080 important...what are they? This is the tasklog in RAM before reboot and its time. 120 and 80 are the task priorities. tasklog logs the task context (e.g. current executing instructions) at task switch, called by the scheduler when it selects a new task to run. The log is a circular buffer that stores the last 25 tasks that were running on the switch before the switch reboots.
Example 2-133:
READY READY [unknown] [0]_vxTaskEntry + 0x10 (0x10735914) [1]_crashTask + 0x40 (0x104dd310)
Does this tell me I've had a panic or a watchdog error? No. You should check uptime to find out it is a panic or watchdog, etc.
[2]_taskDelay + 0x98 (0x10780048) <- instruction pointer
This is address of instruction. At 0x10780048, there may be a static function Example 2-134:
[tSwitch] [0]_vxTaskEntry + 0x10 (0x10735914) [1]_switchTask + 0x184 (0x105101f4) [2]_fabricInit + 0xbc (0x104dd27c) [3]_fcServiceResponseQ + 0x1c (0x1056c91c) [4]_mqRead + 0x14 (0x10576d34) [6]_qJobGet + 0x48 (0x1079e628) Reset at: Dec 29 03:11:11 Reset reason 2: Bus error
Note:
Bus error is another category of reboot, i.e., CPU accesses a memory location that does not exist. It is a typical memory corruption.
Example 2-135:
Task: Interrupt
2-257
... Frame #2 Address: (0x103f5108) Local registers (0x10276af0): pfp = 0x103bbea7, sp = 0x1081af10, r4 = 0x00000040, r5 = 0x1081aed0, r8 = 0x003d0004, r9 = 0x00000000, r12 = 0x756f7920, r13 = 0x00000000, Interrupt call: Saved pc = 0x3 Saved ac = 0x1100 Vector = 0xf8 (NMI) User's stack, length = 64: 756f7920 00000000 001f0000 00000012 00000007 756f7920 0000001b 00000040 00000000 00000000 00000000 00000000
rip r6 r10 r14
= = = =
0x103f5108, 0x00000000, 0x00000000, 0xeeeeeeee,
r3 r7 r11 r15
= = = =
0xeeeeeeee 0x00000000 0x103bbb00 0xeeeeeeee
* you............* *.... you....@...* *................*
Note:
If the switch reboots due to bus error, panic and watchdog, you will see traceshow in supportshow.
2-258
trunkShow
Available in Fabric OS versions: All Bloom ASIC switches Troubleshooting Use: Use this command to display trunking information. Make sure that deskew values are within specifications - The shortest ISL is selected as the base deskew and is assigned a deskew value of 150 nseconds. The deskew values are expressed (shown in all command displays) by dividing the deskew value by 10. Example: A deskew value of 150 nseconds is expressed as 15 (150/10). To not affect performance the greatest deskew difference should be 15 or less (this would correspond to a 30 meter cable difference but could also be due to cable integrity). A trunk will not form is the deskew difference is 2000 or more, this correlates to a cable difference of 400 meters. Use this command to display trunking information. The fields displayed are as follows: Trunking Group Number: Displays each trunking group on a switch. All the ports that are part of this trunking group are displayed. Port to port connections: Displays the port-to-port trunking connections. WWN Displays the WWN of the connected switch. deskew Master Example 2-136:
trunkShow 1: 1 -> 14 0 -> 13 2:15 -> 15 14 -> 14 10:00:00:60:69:80:46:5a 10:00:00:60:69:80:46:5a 10:00:00:60:69:80:46:5b 10:00:00:60:69:80:46:5b deskew deskew deskew deskew 15 16 15 16 MASTER MASTER
Displays the single trip time difference between trunked links. Each number corresponds to 10 ns. Displays whether this trunking port connection is the master port connection for the trunking group.
What is trunking?
Aggregates traffic onto fewer logical links Allows from 2-4 ISLs in the same quad to logically merge into a single trunk Automatically created when switches are connected Fault-tolerant logical fat ISL will withstand failure of individual links Supports multiple trunks between switches Preserves in-order delivery Trunking license key on both sides of the ISL is required Ports must be operating at 2 Gbit/sec
How are trunks built? First ISL in trunk to initialize becomes the Trunk Master Shortest ISL of the initialized ISLs becomes the base Master ISL will only be the base if it is the shortest ISL1 Deskew values are represented in nanoseconds divided by 10 Base ISL will always have a deskew value of 15 (150 nsec/10) Deskew value is calculated for each direction of the ISL Longer cables will have higher deskew values Trunking should not be used in conjunction with long distance2
Cables of the same length can have different deskew values due to differences in optical media signal quality (cable/SFPs)3
The Master ISL will only be the base if it is also the shortest. The deskew values for the other ISLs in the trunk will be calculated from the base ISL and will have a higher value. Each switch connected by the ISL will have a deskew value since each has a separate transmit line to the other.
2-259
2
Note:
If the portcfglongdistance command is used then trunking should not be used.
Due to the signal quality/optical media, cables that are identified as the same length (e.g. cables manufactured as 1 meter) may have a different deskew value. For example, one cable may have a deskew value of 16 and a cable of the same length may calculate to be 17. This is not a problem since it is a true measurement of its transmission capabilities.
Additional Notes: The first ISL in the trunk to initialize is selected as the trunk Master. The length of the cable is not a consideration when selecting the Master. Trunking allows up to 4 ISL ports in a quad to be seen as a single fat ISL to provide greater bandwidth. The difference in cable lengths between the ISLs in a trunk determines the deskew value. This is needed for timing purposes so in-order delivery of frames across the trunk can be ensured. The shortest ISL is selected as the base deskew and is assigned a deskew value of 150 nseconds. The deskew values are expressed (shown in all command displays) by dividing the deskew value by 10. Example: A deskew value of 150 nseconds is expressed as 15 (150/10). To not affect performance the greatest deskew difference should be 15 or less (this would correspond to a 30 meter cable difference but could also be due to cable integrity). A trunk will not form is the deskew difference is 2000 or more, this correlates to a cable difference of 400 meters. portLogDump output:
The Fabric Controller in one switch (FFFFFD) does a (90000000) IE_EMT (Read MARK timestamp (VU) to the FFFFFD of the other switch, who accepts. The switches then exchange trunk parameters: 91000000 IE_ETP Exchange Trunking Parameters
Additional Resource: Brocade ISL Trunking Users Guide Version 3.0/4.0 Publication Number 53-0000184-02

trunkshow No trunking links
2-260
udpstatshow
Available in Fabric OS versions: v3.1, v3.1.2 (Network Command Group) Troubleshooting Use: Use this command to display the User datagram Protocol Statistics
Example 2-138: To display the User Datagram Protocol statistics:

SW3800_12:admin> udpstatshow UDP: 33324 total packets 33311 input packets 13 output packets 0 incomplete header 0 bad data length field 0 bad checksum 33307 broadcasts received with no ports 0 full socket
Note:
Use this command and other network group commands when experiencing Ethernet problems. Other network command group commands include:
network Command Group: ipAddrShow ifShow ipstatShow udpstatShow tcpstatShow inetstatshow mbufShow arpShow routeShow routestatShow hostShow feiDumpPrint i557Dump feiIterateRFDRings
2-261
uptime
Available in Fabric OS versions: All Version Differences: VxWorks and Linux switches depict slightly different outputs. VxWorks switches to not depict load average information. Additional Example/Case Studies: Troubleshooting Use: Use this command to display the length of time the system has been in operation (also known as up time), the total cumulative amount of up time since the system was first powered-on, the date and time of the last reboot, and the reason for the last reboot. The system load averages are listed for the past 1, 5, and 15 minutes are also displayed for LINUX switches. For up and powered-on times less than 60 seconds, the time is displayed in seconds. For times greater than or equal to 60 seconds, the time is displayed in minutes. The output format adjusts accordingly. The reason for the last switch reboot is also recorded in the error log. Reasons are listed below. Not all the below responses are applicable to all switch models: Unknown Bus time-out* Bus error* Panic* Fault* Power-on Watchdog* PushButtons Reboot Reason is unknown. Port ASIC was accessed and no response was received. Non-existent system address was accessed. Firmware detected a critical hardware error or an internal inconsistency. CPU signaled a fault condition (critical firmware error). Last reboot was caused by a power-on. Watchdog timer caused a reset. Push buttons 1 and 3 were depressed for two seconds, causing a system reset. Last reboot was caused by a user (from any management interface).
Powerfail NMI* Power supply caused a nonmaskable interrupt. Watchdog NMI* Watchdog timer caused a nonmaskable interrupt. PushButton NMI*Push buttons 2 and 4 were depressed for two seconds, causing a nonmaskable interrupt. Software NMI* Firmware caused a nonmaskable interrupt. Note: The items marked with an asterisk (*) are usually caused by hardware or firmware failures.Information on the failure is stored in the switch errlogs and for reboot reason Panic or watchdog errors additional information can be found in savecore/pdshow (LINUX) or traceshow/faultshow (VxWorks) outputs.
Example 2-139: V3.1.2 uptime output

uptime Up for: 4 mins Powered for: 705 days, 7:03 Last up at: Mon Jan 5 22:17:22 2004 Reason: Reboot
Note:
Statistical counters displayed in porterrshow commands are based on uptime unless they are cleared using the portstatsclear <port#> command.
Example 2-75: v4.1 output

uptime: 10:21pm up 14:43, 2 users, load average: 1.21, 1.19, 1.21
2-262
Check the up 14:43 time up against what the customer tells you. If the customer says that the switch has been up for 6 months either the customer doesnt know about a reboot 14:43 hours ago or the switch rebooted itself, check errlog (errshow) for reboot reason. As noted above, the system load averages are listed for the past 1, 5, and 15 minutes. 1.21 is the load average for the past 15 minutes. The load average is number of jobs waiting to run. It doesn't tell you CPU load as much as it tells you how backlogged a system is... if your load average is 25, that means that 25 processes need CPU time, and are backed up behind the one running process. Even a multitasking OS can only run one program at a time (on a single CPU), the rest are suspended for micro/milliseconds while the one gets some time slices. Note: If you start seeing load average numbers in excess of 10, then the switch is backed up and getting slammed - it will be quite slow.

uptime: 7:33pm up 1 day, 4:49, 1 user, load average: 1.34, 1.08, 1.03
2-263
version
Available in Fabric OS versions: All Version Differences: Flash value differences between VxWorks and Linux based switches. See Flash notes. Additional Example/Case Studies: Troubleshooting Use: Use this command to display firmware version information. A known Fabric OS version allows you to check for known issues in release or OEM qualification notes. The version command also Use this command to display firmware version information and build dates. The following is displayed: Kernel: Fabric OS: Made on: Flash: BootProm: Examples Example 2-141: v3.1.2 output
version Kernel: Fabric OS: Made on: Flash: BootProm: 5.4 v3.1.2_beta1 Wed Dec 24 11:24:08 PST 2003 Wed Dec 24 11:24:57 PST 2003 Wed May 23 12:37:30 PDT 2001
Displays the version of switch kernel operating system; Displays the version of switch Fabric OS; Displays the build date of firmware running in switch. See additional examples below. VxWorks switches display the build date of the Fabric OS downloaded to the switch. Linux switches display the date that the firmware was downloaded (before reboot, after firmwaredownload) This field displays the build date of firmware stored in boot PROM.
Note:
The flash output in Example 2-141 depicts the build date of firmware in flash. For VxWorks switches - if the made on and flash dates differ by more that a few minutes firmware was downloaded but the switch was not rebooted to read in new firmware.
Note:
Use the Fabric OS information release notes to check if the problem youre experiencing has already been documented. Since the switch mounts the file system on its nonvolatile firmware at boot time, Made on is also the build date of its nonvolatile firmware. The dates shown here is displayed in GMT-universal time.
Example 2-142: Examples before and after firmwareDownload on a Linux switch

Kernel: 2.4.2 Fabric OS: v4.0.2rc1.9 Made on: Fri Oct 11 22:33:25 2002 Flash: Thu Oct 17 07:34:48 2002 BootProm: 3.1.18 Kernel: 2.4.2 Fabric OS: v4.0.2a Made on: Mon Oct 14 17:20:34 2002 Flash: Thu Oct 17 23:24:44 2002 BootProm: 3.1.18
Note:
The output in Example 2-142 depict the actual dates that the firmware was downloaded.
2-264

Version: Kernel: 2.4.19 Fabric OS: v4.2.0_beta1 Made on: Thu Dec 18 19:21:47 2003 Flash: Tue Dec 30 14:41:26 2003 BootProm: 4.1.0
2-265
zone stateshow & portzoneshow

Available in Fabric OS versions: v4.1, v4.2 Troubleshooting Use: Use this command, cfgsize, portzoneshow and cfgshow to troubleshoot zone problems. To display these command output information, a story is used. Start without any zoning, display zone stateshow command. Create and enable zoning using WEBTOOLS, display zone stateshow and portzoneshow command outputs. Disable zoning, display zone stateshow. Clear all zoning and reissue both display zone stateshow and portzoneshow commands. See embedded notes after / symbols for additional information. Example 2-76:
cfgshow Defined configuration: no configuration defined Effective configuration: no configuration in effect RSL_12K8_SW1:root> zone stateshow ============================ Switch Instance 1: ZoneRcsSyncSem IS available zone_mutex IS available g_cfgEnabled = 0 /Value 0 means zoning is not enabled (0 = off; 1 = on). g_znRcsState = 0x0 gCfgChangeInProgress = 0 Committed CfgSize = 0 Zone Cfg. Gen Cnt. = 1 /Value is incremented with every zone change trans_in_progress = 0 g_znInternalState = 0x0 zoneDomain switchIsOnline(1), domainCnt(2) domainBM 1, 2, xactEnabledDomainBM 1, 2, portsOnlineBM g_znSmCb.sm_lock IS available Global State 0x0 F-port 1: state 0x80100 E-port 4: state 0x400200 T-port 5: state 0x300 ============================ ENABLED ZONING WITH WEBTOOLS RSL_12K8_SW1:root> cfgshow Defined configuration: cfg:FabricZone1 Sun_1; Win2k_1 zone:Sun_120:00:00:00:c9:2b:ff:97; 20:00:00:20:37:e6:2d:90; 20:00:00:20:37:e6:36:f9; 20:00:00:20:37:e6:36:8b; 20:00:00:20:37:e6:32:fe; 20:00:00:20:37:e6:32:a7 zone:Win2k_120:00:00:00:c9:29:05:e8; 20:00:00:20:37:42:66:46; 20:00:00:20:37:e6:2e:13; 20:00:00:20:37:e6:37:40; 20:00:00:20:37:e6:34:46 Effective configuration: cfg:FabricZone1 zone:Sun_120:00:00:00:c9:2b:ff:97 20:00:00:20:37:e6:2d:90 20:00:00:20:37:e6:36:f9 20:00:00:20:37:e6:36:8b 20:00:00:20:37:e6:32:fe 20:00:00:20:37:e6:32:a7
2-266
zone:Win2k_120:00:00:00:c9:29:05:e8 20:00:00:20:37:42:66:46 20:00:00:20:37:e6:2e:13 20:00:00:20:37:e6:37:40 20:00:00:20:37:e6:34:46 zone stateshow: ============================ Switch Instance 1: ZoneRcsSyncSem IS available zone_mutex IS available g_cfgEnabled = 1 /Value is 1 if zoning on, 0 without. Possibilities include 0 (off) and 1 (On), Eff. Cfg name = FabricZone1 g_znRcsState = 0x0 gCfgChangeInProgress = 0 Committed CfgSize = 308 /alternately use cfgsize command Zone Cfg. Gen Cnt. = 2 /Value is incremented with every zone change trans_in_progress = 0 g_znInternalState = 0x0 port Control installed switchedToSoft defaultHard ---- ----------------- -------------- ----------11 HARD WWN 1 0 0 31 HARD WWN 1 0 0 zoneDomain ---------switchIsOnline(1), domainCnt(2) domainBM /BM bit map; domains in Fabric 1, 2, xactEnabledDomainBM /BM bit map; enabled domains in Fabric 1, 2, portsOnlineBM /BM bit map; ports online in Fabric 11, 31,
BM means Bit Map

g_znSmCb.sm_lock IS available Global State 0x0 F-port 1: state 0x80100 E-port 4: state 0x400200 T-port 5: state 0x300 F-port 11: state 0x40100 F-port 31: state 0x80100 portzoneshow:/lists switch ports and zone enforcement policy in use. PORT: 0 Not Zoned PORT: 1 Enforcement: HARD WWNdefaultHard: 0F-port: 0 PORT: 2 Not Zoned PORT: 3 Not Zoned PORT: 4 Enforcement: E-PortdefaultHard: 0F-port: 0 PORT: 5 Enforcement: E-PortdefaultHard: 0F-port: 0 PORT: 6 Not Zoned PORT: 7 Not Zoned PORT: 8 Not Zoned PORT: 9 Not Zoned PORT: 10 Not Zoned PORT: 11 Enforcement: HARD WWNdefaultHard: 0F-port: 1 PORT: 12 Not Zoned PORT: 13 Not Zoned PORT: 14 Not Zoned PORT: 15 Not Zoned PORT: 16 Not Zoned PORT: 17 Not Zoned PORT: 18 Not Zoned PORT: 19 Not Zoned PORT: 20 Not Zoned PORT: 21 Not Zoned PORT: 22 Not Zoned
2-267

23 24 25 26 27 28 29 30 31 Not Zoned Not Zoned Not Zoned Not Zoned Not Zoned Not Zoned Not Zoned Not Zoned Enforcement: HARD WWNdefaultHard: 0F-port: 1
PORT: PORT: PORT: PORT: PORT: PORT: PORT: PORT: PORT:
RSL_12K8_SW1:root> cfgdisable Updating flash ... RSL_12K8_SW1:root> cfgshow Defined configuration: cfg:FabricZone1 Sun_1; Win2k_1 zone:Sun_120:00:00:00:c9:2b:ff:97; 20:00:00:20:37:e6:2d:90; 20:00:00:20:37:e6:36:f9; 20:00:00:20:37:e6:36:8b; 20:00:00:20:37:e6:32:fe; 20:00:00:20:37:e6:32:a7 zone:Win2k_120:00:00:00:c9:29:05:e8; 20:00:00:20:37:42:66:46; 20:00:00:20:37:e6:2e:13; 20:00:00:20:37:e6:37:40; 20:00:00:20:37:e6:34:46 Effective configuration: no configuration in effect RSL_12K8_SW1:root> zone stateshow ============================ Switch Instance 1: ZoneRcsSyncSem IS available zone_mutex IS available g_cfgEnabled = 0 /displays zoning not enabled g_znRcsState = 0x0 gCfgChangeInProgress = 0 Committed CfgSize = 308 /still using space for defined zone db Zone Cfg. Gen Cnt. = 3/Value is incremented with every zone change trans_in_progress = 0 g_znInternalState = 0x0 zoneDomain ---------switchIsOnline(1), domainCnt(2) domainBM 1, 2, xactEnabledDomainBM 1, 2, portsOnlineBM 11, 31, g_znSmCb.sm_lock IS available Global State 0x0 F-port 1: state 0x80100 E-port 4: state 0x400200 T-port 5: state 0x300 F-port 11: state 0x80100 F-port 31: state 0x80100 ============================ RSL_12K8_SW1:root> cfgclear Do you really want to clear all configurations? zone stateshow: ============================ Switch Instance 1: ZoneRcsSyncSem IS available zone_mutex IS available
(yes, y, no, n): [no] y
2-268
g_cfgEnabled = 0 g_znRcsState = 0x0 gCfgChangeInProgress = 0 Committed CfgSize = 308 Zone Cfg. Gen Cnt. = 3 /Value is incremented with every zone change, did not increment when zoning cleared, stayed at last count. trans_in_progress = 26853 g_znInternalState = 0x0 zoneDomain switchIsOnline(1), domainCnt(2) domainBM 1, 2, xactEnabledDomainBM 1, 2, portsOnlineBM 11, 31, g_znSmCb.sm_lock IS available Global State 0x0 F-port 1: state 0x80100 E-port 4: state 0x400200 T-port 5: state 0x300 F-port 11: state 0x80100 F-port 31: state 0x80100

zone stateshow: ============================ Switch Instance 0: ZoneRcsSyncSem IS available zone_mutex IS available g_cfgEnabled = 0 g_znRcsState = 0x0 gCfgChangeInProgress = 0 Committed CfgSize = 0 Zone Cfg. Gen Cnt. = 1 trans_in_progress = 0 g_znInternalState = 0x0 zoneDomain ---------switchIsOnline(1), domainCnt(1) domainBM 1, xactEnabledDomainBM 1, portsOnlineBM 1, 94, 127, g_znSmCb.sm_lock IS available Global State 0x0 F-port 1: state 0x80100 F-port 94: state 0x80100 F-port 127: state 0x80100 ============================
2-269
/bin/cat/etc/fstab (Phy File Mount Points)

Troubleshooting Use: Use this command to display mount points. This is a physical file that shows mount points Available in Fabric OS versions: v4.x Additional Example/Case Studies: Physical file that shows mount points. Example 2-77:
/bin/cat /etc/fstab /dev/root/ xfs rw,noatime0 0 none /proc procdefaults0 0 none /dev/ptsdevptsmode=6200 0
Note:
Shows automatically mounted filesystems
2-270
/bin/cat/etc/mtab (Current Mount Points)

Available in Fabric OS versions: v4.x Troubleshooting Use: Use this command to display current mount points, like df but its a file not an output. Example 2-78:
/bin/cat /etc/mtab /dev/root / xfs rw,noatime 0 0 none /proc proc rw 0 0 none /dev/pts devpts rw,mode=620 0 0 none /tmp ramfs rw 0 0 /dev/hda2 /mnt xfs rw,noatime 0 0 /diag /diag dfs rw 0 0
Note:
These will only come in handy when troubleshooting Compact Flash problems. It really only tells you what filesystems are defined for auto-mount and which filesystems are currently mounted at each mount point.
2-271
/bin/cat/var/log/dsmg (Serial Boot or MSG File)

Available in Fabric OS versions: v4.x Troubleshooting Use: Use this command to display system boot messages. There is a dmesg non-persistent command that displays this information. Example 2-79:
/bin/cat /var/log/dmesg read_silkworm_bdinfo: silkworm->board = 10, silkworm->board_rev =2 id mach(): done _Linux version 2.4.2_hhl20 (swrel@nermal) (gcc version 2.95.3 20010112 (prerelease)) #1 Fri Oct 11 12:19:12 PDT 2002 setup_arch: enter _setup_arch: bootmem _CPLD - v1.1 arch: exit _On node 0 totalpages: 32512 zone(0): 32512 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: mem=127m Calibrating delay loop... 199.47 BogoMIPS Memory: 123692k available (1508k kernel code, 480k data, 60k init, 0k highmem) Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes) Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes) Page-cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 8192 (order: 4, 65536 bytes) POSIX conformance testing by UNIFIX PCI: Probing PCI hardware _<6>Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Starting kswapd v1.8 i2c-core.o: i2c core module i2c-dev.o: i2c /dev entries driver module i2c-core.o: driver i2c-dev dummy driver registered. pty: 256 Unix98 ptys configured block: queued sectors max/low 82152kB/27384kB, 256 slots per queue RAMDISK driver initialized: 16 RAM disks of 6144K size 1024 blocksize Uniform Multi-Platform E-IDE driver Revision: 6.31 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx eth0: Rx Interrupt mitigation (1500 pps) RAMDISK: Compressed image found at block 0 Freeing initrd memory: 1978k freed loop: loaded (max 8 devices) Serial driver version 5.02 (2000-08-09) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled ttyS00 at 0x0000 (irq = 1) is a 16550A ttyS01 at 0x0000 (irq = 0) is a 16550A SWBD Platform Driver v1.0 M41T11 Driver v1.0 PPC 405 gpio driver version 00.08.02.d
<Output Truncated> Note: This captures all messages including errors during boot. If you are having trouble booting, this is really handy. It's kind of a bootlog. These are messages won't make it into the error log because the errlog is not running yet.
2-272
/bin/df File Systems Available

Available in Fabric OS versions: v4.x Troubleshooting Use: Use this command to view available file system memory usage. This is a UNIX command that displays how much of the file system is in use. You can also use df k to get the output in Kilobytes and df m to get the output in Megabytes. Example 2-80:
/bin/df Filesystem /dev/root /dev/hda2 1k-blocks 120112 120128 Used Available Use% Mounted on 36848 83264 31% / 36920 83208 31% /mnt
Note:
The percent use, currently 31% should be less than 80%.
Note:
You can verify that the FW daemons are running on both switches (fwd = fabric watch daemon | -s 0 = switch 0 | -s1 = switch 1)
847 875 1 1 0 0 78 78 19 19 993 rt_sig Feb12 ? 993 rt_sig Feb12 ? 00:00:00 00:00:00 fwd -s 0 fwd -s 1
000 S root 000 S root

/bin/df: Filesystem /dev/root /dev/hda2 1k-blocks 120112 120128 Used Available Use% Mounted on 53328 66784 44% / 53152 66976 44% /mnt
Note:
There is a known CF Full problem on V4.1 switches that is fixed in v4.1.1b. See notes about this problem below.
Compact Flash Full

Products Affected: SilkWorm 3900 and 12000 running on Fabric OS v4.1.x Problem Description: Under the Fabric OS v4.1.x code stream there is a possibility for the compact flash to become full as a result of the Apache web server/embedded Linux implementation. The problem begins to surface when the log rotation program/script deletes the current access log file intending to replace it with a newly created one. If a close function is not sent the old access log file will continue to be written even though a new file has been created. This issue is exacerbated with management stations in the environment doing polling via the Web Tools interface. Note that only those units which have Web Tools or Fabric Manager accessing the switch web server are susceptible to this condition. Symptoms: Compact flash full may result in a switch panic. To determine the status of the Compact Flash, the percentage of the file system used can be checked by issuing the /bin/df command under Root level access, or by viewing a Supportshow and looking for this same output. Below is an example of output:
Filesystem 1k-blocks Used Available Used% Mounted on /dev/root 120112 81520 40 80% / /dev/hda2 120128 51520 68608 43% /mnt
2-273
Risk Assessment: If the compact flash does become full, any process that attempts to write to the compact flash has a high probability of corrupting an open file. Brocade has observed issues in which the host, password and zoning database files have become corrupted as a result of the inability to write to the compact flash, which could in turn result in a switch panic. Corrective Action: Fabric OS v4.1.1b is available to Brocades partners that fixes issue. Some OEM partners will support the fix in a subsequent maintenance release available in early 2004. Workaround Procedure: To determine the status of the compact flash, the percentage of the file system used can be checked by issuing the /bin/df command under Root level access, or by viewing a Supportshow and looking for this same output.
Filesystem 1k-blocks Used Available Used% Mounted on Filesystem 1k-blocks Used Available Used% Mounted on /dev/root 120112 81520 40 80% / /dev/hda2 120128 51520 68608 43% /mnt
If the percentage used in the root file system is observed to be over 80% you will be given a procedure (see procedure below) that has you ftp a script to the switch to fix this problem. Note: Do not place this procedure on a switch that is in excess of 95% compact flash capacity without contacting Brocade Technical Support for instructions. There are more steps involved when a switch is in excess of 95% compact flash capacity.
Note:
Once you follow the OEM or Brocade support specified step that include running a script on the switch, there is no need to ever run it again.
Note:
Make sure to capture the console output when issuing all commands on the switch.
Procedure Instructions: 1. Place logcleanrev2.sh script from OEM or Brocade customer support in an appropriate directory of an FTP server. The IP address of the sever and the relative path to the file.
Note: 2. 3. 4. 5. 6. 7. 8. 9.
Log in to Switch or Active CP as root Enter the command "cd/var/tmp" Enter the command "ftp<ftpserverip" Enter appropriate user id and password Enter the command "bin" Enter the command "cd<pathtofile" Enter the command "getlogcleanrev2.sh" Enter the command "quit"
10. Enter the command "pwd" and verify that you are still in /var/tmp
2-274
Fabric OS SupportShow Information 11. Enter the command "chmod755/var/tmp/logcleanrev2.sh" 12. Enter the command "/var/tmp/logcleanrev2.sh" 13. Enter the command "rm/var/tmp/logcleanrev2.sh" 14. Verify that Web Tools is currently working by pointing a Web Browser to the switches IP Address. Overview of script behavior: 1. 2. 3. 4. 5. 6. 7. 8. Check current disk usage on the active partition of the compact flash Create a daily cron job that keeps /var/log/wtmp from growing too large If /var/log/wtmp is already growing too large it replaces it with /var/run/utmp Disables logging access logs for WebTools by modifying /fabos/webtools/bin/httpd.conf Checks the file size of the access logs and removes them if they have grown too large Checks for any httpd processes that have dangling inodes and removes them Restarts Web Tools so that the log changes take effect Replicate all file changes to each partition and each CP (if SW12000)
2-275
/bin/hostname
Available in Fabric OS versions: v4.1, v4.2 Troubleshooting Use: Use this command determine active switch host name. The myid command will also display hostname. v3.1 and v3.1.2 have a hostshow command that gives similar information. Example 2-81:
/bin/hostname: cp0
Note:
This command is only displayed at the admin level by invoking supportshow. The supportshowcfgdisable command can be used to turn off all supportshow outputs but system (wherein this command lies). This shows the active cp.

/bin/hostname: cp1
2-276
/bin/ps -elfH (Process List)

Available in Fabric OS versions:All v4.x Troubleshooting Use: Use this command to display the process ID list where you can see which daemons are running on the switch. Example 2-82:
/bin/ps -elfH F S UID PID PPID C 100 S root 1 0 0 040 S root 2 1 0 040 S root 3 1 0 040 S root 4 1 0 040 S root 5 1 0 040 S root 6 1 0 040 S root 7 1 0 040 S root 74 1 0 140 S bin 272 1 0 140 S root 278 1 0 000 S root 1374 278 0 192.168.133.22 100 S root 1375 1374 0 000 S root 10157 278 0 192.168.84.18 100 S root 10158 10157 0 000 S root 10644 10158 5 /fabos/link_bin/supportshow 000 R root 10771 10644 0 040 S root 316 1 0 140 S root 317 1 0 040 S root 324 1 0 040 D root 367 1 0 000 S root 490 1 0 100 S root 495 1 0 040 S root 500 495 0 040 S root 501 500 0 040 S root 502 500 0 040 S root 503 500 0 040 S root 504 500 0 040 S root 545 500 0 000 S root 507 1 0 040 S root 894 507 0 040 S root 900 894 0 040 S root 910 894 0 040 S root 919 894 0 040 S root 940 894 0 040 S root 7704 894 0 000 S root 513 1 0 040 S root 895 513 0 040 S root 899 895 0 040 S root 912 895 0 040 S root 916 895 0 040 S root 10292 895 0 000 S root 519 1 0 040 S root 524 519 0 040 S root 525 524 0 PRI 68 69 69 69 69 69 69 69 69 69 69 69 69 69 69 76 69 69 68 69 69 65 65 65 65 65 65 65 68 69 69 69 69 69 69 69 69 69 69 69 69 69 69 69 NI ADDR 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 -10 -10 -10 -10 -10 -10 -10 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 SZ WCHAN STIME TTY 297 do_sel 07:38 ? 0 contex 07:38 ? 0 kswapd 07:38 ? 0 krecla 07:38 ? 0 bdflus 07:38 ? 0 kupdat 07:38 ? 0 pagebu 07:38 ? 289 nanosl 07:38 ? 298 do_sel 07:38 ? 312 do_sel 07:38 ? 400 do_sel 07:42 ? 612 read_c 07:42 pts/1 400 do_sel 22:12 ? 583 wait4 690 wait4 22:12 pts/0 22:21 pts/0 TIME CMD 00:00:04 init 00:00:00 [keventd] 00:00:00 [kswapd] 00:00:00 [kreclaimd] 00:00:00 [bdflush] 00:00:01 [kupdate] 00:00:00 [pagebuf_daemon] 00:00:00 /sbin/wdtd -p 30 -n 5 00:00:00 /sbin/portmap 00:00:00 /usr/sbin/inetd 00:00:00 in.telnetd: 00:00:00 00:00:01 00:00:00 00:00:00 -sh in.telnetd: -rbash /bin/sh
733 22:21 pts/0 311 do_sel 07:38 ? 292 Letext 07:38 ? 364 nanosl 07:38 ? 0 end 07:38 ? 804 do_sel 07:38 ? 936 rt_sig 07:38 ? 936 do_pol 07:38 ? 936 Letext 07:38 ? 936 do_sel 07:38 ? 936 rt_sig 07:38 ? 936 rt_sig 07:38 ? 936 rt_sig 07:39 ? 962 rt_sig 07:38 ? 962 do_pol 07:40 ? 962 Letext 07:40 ? 962 do_sel 07:40 ? 962 Letext 07:40 ? 962 rt_sig 07:40 ? 962 rt_sig 16:46 ? 921 rt_sig 07:38 ? 921 do_pol 07:40 ? 921 Letext 07:40 ? 921 do_sel 07:40 ? 921 nanosl 07:40 ? 921 rt_sig 22:15 ? - 1253 rt_sig 07:38 ? - 1253 do_pol 07:38 ? - 1253 Letext 07:38 ?
00:00:01 /bin/ps -elfH 00:00:00 /usr/sbin/syslogd -m 0 00:00:00 /usr/sbin/klogd -x 00:00:00 /usr/sbin/crond 00:00:00 [kerrlog] 00:00:00 diagd 00:00:00 fabricd -s 0 00:00:00 fabricd -s 0 00:00:03 fabricd -s 0 00:00:00 fabricd -s 0 00:00:00 fabricd -s 0 00:00:00 fabricd -s 0 00:01:15 fabricd -s 0 00:00:00 zoned -s 0 00:00:00 zoned -s 0 00:00:00 zoned -s 0 00:00:00 zoned -s 0 00:00:00 zoned -s 0 00:00:00 zoned -s 0 00:00:00 zoned -s 0 00:00:00 fspfd -s 0 00:00:00 fspfd -s 0 00:00:00 fspfd -s 0 00:00:00 fspfd -s 0 00:00:00 fspfd -s 0 00:00:00 fspfd -s 0 00:04:49 nsd -s 0 00:00:00 nsd -s 0 00:03:55 nsd -s 0
<Output Truncated.>
2-277
Example 2-147:
/bin/ps -elfH F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD 100 S root 1 0 0 68 0 298 do_sel Dec30 ? 00:00:01 init 040 S root 2 1 0 69 0 0 contex Dec30 ? 00:00:00 [keventd] 040 S root 3 1 0 79 19 0 ksofti Dec30 ? 00:00:00 [ksoftirqd_CPU0] 040 S root 4 1 0 69 0 0 kswapd Dec30 ? 00:00:00 [kswapd] 040 S root 5 1 0 69 0 0 bdflus Dec30 ? 00:00:00 [bdflush] 040 S root 6 1 0 69 0 0 kupdat Dec30 ? 00:00:01 [kupdated] 040 S root 7 1 0 69 0 0 pagebu Dec30 ? 00:00:00 [pagebuf_daemon] 040 S root 52 1 0 69 0 290 nanosl Dec30 ? 00:00:00 /sbin/wdtd 140 S bin 292 1 0 69 0 297 do_sel Dec30 ? 00:00:00 [portmap] 140 S root 316 1 0 69 0 355 do_sel Dec30 ? 00:00:00 /usr/sbin/inetd 000 S root 11070 316 0 69 0 - 314 do_sel 19:31 ? 00:00:00 in.telnetd: 192.168.80.59 100 S root 11076 11070 0 69 0 890 wait4 19:31 ? 00:00:00 [login] 040 S root 11077 11076 0 69 0 890 do_pol 19:31 ? 00:00:00 [login] 100 S root 11080 11076 0 69 0 575 wait4 19:31 pts/0 00:00:00 -rbash 000 S root 11158 11080 4 69 0 658 wait4 19:33 pts/0 00:00:00 /bin/sh /fabos/link_bin/supportshow 000 R root 11406 11158 0 78 0 775 19:33 pts/0 00:00:00 /bin/ps -elfH 040 S root 348 1 0 69 0 312 do_sel Dec30 ? 00:00:00 /usr/sbin/syslogd 140 S root 349 1 0 69 0 479 Letext Dec30 ? 00:00:00 /usr/sbin/klogd 040 S root 359 1 0 68 0 365 nanosl Dec30 ? 00:00:00 /usr/sbin/crond 040 D root 447 1 0 69 0 0 end Dec30 ? 00:00:00 [kerrlog] 040 S root 532 1 0 69 0 0 end Dec30 ? 00:00:00 [CERK_TH] 000 S root 535 1 0 68 0 840 rt_sig Dec30 ? 00:00:00 sysctrld /etc/fabos/services SWBD21/opt1 -t XCP -d 0 040 S root 553 535 0 69 0 840 do_pol Dec30 ? 00:00:00 sysctrld /etc/fabos/services SWBD21/opt1 -t XCP -d 0 040 S root 554 553 0 69 0 840 rt_sig Dec30 ? 00:00:00 sysctrld /etc/fabos/services SWBD21/opt1 -t XCP -d 0 040 S root 565 553 0 69 0 840 Letext Dec30 ? 00:00:00 sysctrld /etc/fabos/services SWBD21/opt1 -t XCP -d 0 040 S root 566 553 0 69 0 840 do_sel Dec30 ? 00:00:00 sysctrld /etc/fabos/services SWBD21/opt1 -t XCP -d 0 040 S root 576 553 0 69 0 840 rt_sig Dec30 ? 00:00:00 sysctrld /etc/fabos/services SWBD21/opt1 -t XCP -d 0 100 S root 582 535 0 61 -16 475 wait_f Dec30 ? 00:00:00 /fabos/libexec/proxy -d 0 -S chassis -s 0 040 S root 586 582 0 61 -16 475 do_pol Dec30 ? 00:00:00 /fabos/libexec/proxy -d 0 -S chassis -s 0 040 S root 587 586 0 61 -16 475 Letext Dec30 ? 00:00:00 /fabos/libexec/proxy -d 0 -S chassis -s 0 100 S root 583 535 0 69 0 786 nanosl Dec30 ? 00:00:00 /fabos/libexec/pdmd -S chassis -s 0 040 S root 597 583 0 69 0 786 do_pol Dec30 ? 00:00:00 /fabos/libexec/pdmd -S chassis -s 0 040 S root 601 597 0 69 0 786 Letext Dec30 ? 00:00:00 /fabos/libexec/pdmd -S chassis -s 0 040 S root 612 597 0 69 0 786 do_sel Dec30 ? 00:00:00 /fabos/libexec/pdmd -S chassis -s 0 000 S root 584 535 0 68 0 659 nanosl Dec30 ? 00:00:00 /fabos/libexec/hmond -S chassis -s 0 040 S root 588 584 0 69 0 659 do_pol Dec30 ? 00:00:00 /fabos/libexec/hmond -S chassis -s 0 040 S root 595 588 0 69 0 659 Letext Dec30 ? 00:00:00 /fabos/libexec/hmond -S chassis -s 0 040 S root 645 588 0 69 0 659 rt_sig Dec30 ? 00:00:00 /fabos/libexec/hmond
<Output Truncated.>
2-278
/bin/rpm qa
Available in Fabric OS versions: All v4.x Troubleshooting Use: Use this Red Hat package manager command to display all packages running on the switch. Example 2-83:
/bin/rpm -qa dir-1.0.4-3 setup-1.3.4-9 ldconfig-1.9.11-3 bash-2.04-5 readline-4.1-1 grep-2.4.2-1 wget-1.5.3-1 termcap-1.3-2 which-2.12-1 findutils-4.1-1 bzip-1.0.1-1 zlib-1.1.3-1 chkconfig-1.0.0-5 fileutils-4.0-1 sed-3.02-1 textutils-1.22-1 procps-2.0.7-3 psmisc-19-2 modutils-2.4.3-6 misc-1.0.0-2 util-linux-2.10s-11 sh-utils-2.0-7 popt-1.3-1 hex-1.2-1 rpm-3.0.6-2 sysvinit-2.78-4 man-1.5g-4 less-3.4.0-2 gzip-1.2.4a-1 tar-1.13.19-1 cpio-2.4.2-1 dev-1.4.0-2 bootenv-1.0.2-4
Note:
You can verify the version of each package if firmwaredownload goes wrong

/bin/rpm -qa dir-1.0.4-3 setup-1.3.4-14 swbd21-setup-1.3.4-1 ldconfig-1.9.11-3 glibc-2.1.3-6 bash-2.04-5 readline-4.1-1 terminfo-11.0.1-3 termcap-1.3-2 which-2.12-1 findutils-4.1-1 bzip-1.0.1-1 zlib-1.1.3-1
2-279
chkconfig-1.0.0-5 fileutils-4.0-1 sed-3.02-1 textutils-1.22-1 procps-2.0.7-3 psmisc-19-2 modutils-2.4.3-6 sin-1.1.0-2 rcinit-1.1.4-2 misc-1.0.0-2 pam-0.74-23 util-linux-2.11w-12 sh-utils-2.0-7 popt-1.3-1 grep-2.4.2-1 rpm-3.0.6-2 sysvinit-2.78-5 man-1.5g-4 less-3.4.0-2 gzip-1.2.4a-1 tar-1.13.19-1 rsync-2.5.5-1 cpio-2.4.2-1 dev-1.4.0-2 bootenv-1.0.2-4 wdtd-1.0.0-2 wget-1.5.3-1 fwdl-1.0.2-38 prom-3.2.4-1 kernel-2.4.19-70 swbd21-drivers-2.4.19-1 pcmcia-cs-3.1.29-2 sysklogd-1.4-6 getty-2.0.7j-5 net-tools-1.57-2 vixie-cron-3.0.1-62_1 uucp-1.06-2 binutils-libs-2.10.1-1 binutils-2.10.1-1 ksymoops-2.4.1-1 portmap-4.0-1 inetd-0.17-5 iptables-1.2-6a tcpd-7.6-1 telnet-server-0.17-3 rsh-server-0.17-1 rsh-0.17-1 openssl-libs-0.9.6-2 openssh-server-3.5p1-4 rusers-server-0.17-1 rdate-990821-2 logrotate-3.5.4-3 ntp-5.93e-1 pciutils-2.1.8-1 strace-4.2-1 ftp-0.17-1 ncftp-3.0.3-3 sendmail-8.9-8 iproute2-2.4-7 fastcgi-2.2-1 fabos-fw-4.2.0_beta1-8 fabos-wwnhs-4.2.0_beta1-8 fabos-hmon-4.2.0_beta1-8 apache-1.3.26-3 tz-7.11-1
2-280

fabos-drivers-4.2.0_beta1-8 fabos-zoning-4.2.0_beta1-8 fabos-webtools-4.2.0_beta1-8 fabos-fss-4.2.0_beta1-8 fabos-setup-4.2.0_beta1-10 fabos-libs-4.2.0_beta1-8 fabos-diag-4.2.0_beta1-9 fabos-man-4.2.0_beta1-8 fabos-4.2.0_beta1-8
2-281
/sbin/bootenv
Troubleshooting Use: Use this command to output boot from parameters. Tells you which partition, which part of flash memory switch booted from in order from left to right. In the example below hda1 is listed first so that is where this switch booted from. Available in Fabric OS versions: All v4.x Additional Example/Case Studies: running user commands
/sbin/bootenv AutoLoad=yes ENET_MAC=00606960045C Note: This is the mac address (WWN without 1st 3 bytes) of CP your on. InitTest=MEM() LoadIdentifier=IDE w/ XFS;IDE w/ XFS & NFS Root OSLoadOptions=mem=127m;mem=127m OSLoader=MEM()0xF0800000;MEM()0xF0000000 OSRootPartition=hda1;hda2 SkipWatchdog=yes tmp_OSLoadOptions=mem=127m;mem=127m
This file is used during a firmwaredown load process. Here is an example that illustrates what happens: Suppose you start a firmwaredownload: Firmware will be loaded on a 2ndary partition, it could either be hda1 or hda2, for this example lets assume its hda1. When the firmware is being loaded on hda1, hda2 gets marked as bad so that it will not be used to boot from after the firmware is downloaded. Here is what the /sbin/bootenv file looks like at that point in time:
cp0:root> bootenv AutoLoad=yes BadRootDev=hda2 ENET_MAC=0060696003a0 InitTest=MEM() OSLoader=MEM()0xF0800000;MEM()0xF0800000;ENET() OSRootPartition=hda1;hda2;nfs SkipWatchdog=yes SoftUpgrade=commit cp0:root>
If the firmwaredownload in progress fails at this point, perhaps because a timer didnt wait long enough for the 2ndary partition to reboot. The boot process would then be marked bad and the /sbin/bootenv file would look like this:
cp0:root> bootenv AutoLoad=yes BadRootDev=hda2 ENET_MAC=0060696003a0 InitTest=MEM() OSLoader=MEM()0xF0800000;MEM()0xF0800000;ENET() OSRootPartition=hda1;hda2;nfs SkipWatchdog=yes SoftUpgrade=SUS_SELF_FAILOVER or SoftUpgrade=SUS_SBY_REBOOT (another flag that could cause system to not boot) cp0:root>

/sbin/bootenv: AutoLoad=yes ENET_MAC=006069D0040C InitTest=MEM() LoadIdentifiers=Fabric Operating System;Fabric Operating System OSLoadOptions=quiet;quiet OSLoader=MEM()0xF0000000;MEM()0xF0800000 OSRootPartition=hda1;hda2 SkipWatchdog=yes
2-282
/sbin/ifconfig
Troubleshooting Use: Use this command to list all IP addresses. Eth0 is the IP of the active CP. Available in Fabric OS versions: All v4.x Additional Example/Case Studies: See embedded notes after / symbols. Also see firmwaredownload related commands in additional non-supportshow commands section. Example 2-84:
/sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:60:69:60:04:5C / Note: eth0 represents the active CP. This is the mac address (WWN without 1st 3 bytes) of the active CP inet addr:10.64.69.2 Bcast:10.255.255.255 Mask:255.255.240.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:119542 errors:0 dropped:0 overruns:0 frame:0 TX packets:34890 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:9 Base address:0xffe0 eth0:1 Link encap:Ethernet HWaddr 00:60:69:60:04:5C / Note: eth0:1 represents logical switch 0, SW0. This is its mac address (WWN without 1st 3 bytes), the same as the active CPs inet addr:10.64.69.3 Bcast:10.255.255.255 Mask:255.255.240.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:9 Base address:0xffe0 eth0:2 Link encap:Ethernet HWaddr 00:60:69:60:04:5C / Note: eth0:2 represents logical switch 1, SW1. This is its mac address (WWN without 1st 3 bytes), the same as the active CPs inet addr:10.64.69.4 Bcast:10.255.255.255 Mask:255.255.240.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:9 Base address:0xffe0 eth1 Link encap:Ethernet HWaddr 00:60:69:60:04:5D / Note: eth1 represents the backplane inet addr:10.0.0.6 Bcast:10.255.255.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:35801 errors:0 dropped:0 overruns:0 frame:0 TX packets:35893 errors:0 dropped:0 overruns:0 carrier:0 collisions:17 txqueuelen:100 Interrupt:29 Base address:0x4000 fc0 Link encap:Fibre Channel HWaddr 00:60:69:80:04:B2 / Note: fc0 and fc1 both represent IP over FC addresses. UP BROADCAST RUNNING MTU:2024 Metric:1 RX packets:772 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 fc1 Link encap:Fibre Channel HWaddr 00:60:69:80:04:B3 / Note: fc0 and fc1 both represent IP over FC addresses. UP BROADCAST RUNNING MTU:2024 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 lo Link encap:Local Loopback Note: Internal loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3904 Metric:1 RX packets:18400 errors:0 dropped:0 overruns:0 frame:0 TX packets:18400 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0

/sbin/ifconfig: eth0 Link encap:Ethernet HWaddr 00:60:69:D0:04:0C inet addr:10.64.148.35 Bcast:10.255.255.255 Mask:255.255.240.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:142766 errors:0 dropped:0 overruns:0 frame:0
2-283

TX packets:8579 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:60
eth0:1
Link encap:Ethernet HWaddr 00:60:69:D0:04:0C inet addr:10.64.148.32 Bcast:10.64.159.255 Mask:255.255.240.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:60 Link encap:Ethernet HWaddr 00:60:69:D0:04:0D inet addr:10.0.0.6 Bcast:10.255.255.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:219778 errors:7 dropped:14 overruns:0 frame:14 TX packets:220077 errors:0 dropped:0 overruns:0 carrier:0 collisions:8 txqueuelen:100 Interrupt:62 Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:35590 errors:0 dropped:0 overruns:0 frame:0 TX packets:35590 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0
eth1
lo
2-284
/sbin/route
Available in Fabric OS versions: All v4.x Troubleshooting Use: Kernel Routing Table Example 2-85:
/sbin/route Kernel IP routing table Destination Gateway cp_0_inteth * cp1 localhost 10.0.0.0 * 10.64.64.0 * default 10.64.64.1
Genmask 255.255.255.255 255.255.255.255 255.255.255.0 255.255.240.0 0.0.0.0
Flags UH UGH U U UG
Metric 0 0 0 0 0
Ref 0 0 0 0 0
Use 0 0 0 0 0
Iface eth1 lo eth1 eth0 eth0
Note:
Default IP routes, starts with destination and depicts routes as you read right.

/sbin/route: Kernel IP routing table Destination Gateway cp1 localhost 10.0.0.0 * 10.64.144.0 * default 10.64.144.1
Genmask 255.255.255.255 255.255.255.0 255.255.240.0 0.0.0.0
Flags UGH U U UG
Metric 0 0 0 0
Ref 0 0 0 0
Use 0 0 0 0
Iface lo eth1 eth0 eth0
2-285
/sbin/sin
Available in Fabric OS versions: All v4.x Troubleshooting Use: Use this command to hardware listing of CP components. Example 2-86:
/sbin/sin Boot PROM: Version 3.1.18, Checksum: 00dbaf43, Fri Oct 11 19:16:29 2002 Note: from boot prom. Platform: SWBD10, Revision 2 Processor: CPU: 200 MHz PowerPC 405GP, Revision E Primary data cache: 8 KB, 32 B lines Primary instruction cache: 16 KB, 32 B lines Flash memory: 16 MB x 32b @ 0xf0000000, Manufacturer ID 0x4f, Device ID 0x0 Flash memory: 16 MB x 32b @ 0xf1000000, Manufacturer ID 0x0, Device ID 0x0 Flash memory: 16 MB x 32b @ 0xf2000000, Manufacturer ID 0x0, Device ID 0x0 Flash memory: 16 MB x 32b @ 0xf3000000, Manufacturer ID 0x0, Device ID 0x0 Flash memory: 512 KB x 8b @ 0xfff80000, Manufacturer ID 0x1, Device ID 0x4f PCI device: Bus 0, Slot 1, Function 0, Vendor 0x1011, Device 0x0046 PCI device: Bus 0, Slot 2, Function 0, Vendor 0x1011, Device 0x0046 PCI device: Bus 0, Slot 3, Function 0, Vendor 0x8086, Device 0x1209 PCI device: Bus 0, Slot 4, Function 0, Vendor 0x104c, Device 0xac51 PCI device: Bus 0, Slot 4, Function 1, Vendor 0x104c, Device 0xac51 Main memory: 128 MB (ECC) @ 0x00000000
Control Processor No: 1 Note: this is referring to the fact that there is currently only 1 ACTIVE CP Note: This is a device table for Linux, a listing of all the devices IDs. Not commonly used for troubleshooting right now.

/sbin/sin: Boot PROM: Version 4.1.0, Checksum: 0433fb18, Mon Dec 15 08:27:57 2003 Platform: SWBD21, Revision 1 Processor: CPU: 466 MHz PowerPC Main memory: 256 MB (ECC) @ 0x00000000 Primary data cache: 32 KB, 32 B lines Primary instruction cache: 32 KB, 32 B lines Flash memory: 8 MB x 16b @ 0xf0000000, Manufacturer ID 0x89, Device ID 0x17 Flash memory: 8 MB x 16b @ 0xf0800000, Manufacturer ID 0x89, Device ID 0x17 Flash memory: 512 KB x 8b @ 0xfff80000, Manufacturer ID 0x1, Device ID 0x4f PCI device: Bus 0, Slot 1, Function 0, Vendor 0x8086, Device 0xb555 PCI device: Bus 0, Slot 2, Function 0, Vendor 0x8086, Device 0xb555 PCI device: Bus 0, Slot 3, Function 0, Vendor 0x8086, Device 0xb555 PCI device: Bus 0, Slot 4, Function 0, Vendor 0x1095, Device 0x0649 Control Processor No: 1
2-286
/usr/bin/du xh / | /bin/sort
Available in Fabric OS versions: All v4.x Troubleshooting Use: Use this command to calculates directory sizes, diff can be used to determine if something is missing. Example 2-87:
/usr/bin/du -xh / | /bin/sort 0/core_files/asd 0/core_files/evmd 0/core_files/fabricd 0/core_files/fcpd 0/core_files/fspfd 0/core_files/fwd 0/core_files/httpd 0/core_files/msd 0/core_files/nsd 0/core_files/psd 0/core_files/snmpd 0/core_files/snmpstartd 0/core_files/track_changes 0/core_files/webd 0/core_files/zoned 0/etc/cron.d 0/etc/cron.hourly 0/etc/cron.monthly 0/etc/cron.weekly 0/etc/logrotate.d 0/etc/pcmcia/cis 0/etc/rc.d/rc0.d 0/etc/rc.d/rc1.d 0/etc/rc.d/rc2.d 0/etc/rc.d/rc3.d 0/etc/rc.d/rc4.d 0/etc/rc.d/rc5.d 0/etc/rc.d/rc6.d 0/etc/rpm 0/export 0/fabos/man/cat2 0/fabos/man/cat3 0/fabos/man/cat4 0/fabos/man/cat5 0/fabos/man/cat6 0/fabos/man/cat7 0/fabos/man/cat8 0/fabos/man/cat9 0/fabos/man/catl 0/fabos/man/catn 0/fabos/man/cato 0/fabos/man/catp 0/fabos/man/man1 0/fabos/man/man1d 0/fabos/man/man1m 0/fabos/man/man2 0/fabos/man/man3 0/fabos/man/man4 0/fabos/man/man5 0/fabos/man/man6 0/fabos/man/man7 0/fabos/man/man8 0/fabos/man/man9 0/fabos/man/manl /usr/bin/du -xh / | /bin/sort
2-287
0/fabos/man/mann 0/fabos/man/mano 0/fabos/man/manp 0/import 0/initrd 0/lib/modules/default/kernel/drivers/block 0/lib/modules/default/kernel/drivers/i2c 0/users 0/usr/apache/htdocs 0/usr/libexec 0/usr/man/cat2 0/usr/man/cat3 0/usr/man/cat4 0/usr/man/cat6 0/usr/man/cat7 0/usr/man/cat9 0/var/lock 1.0M/usr/sbin 1.1M/sbin 1.2M/etc 1.2M/fabos/webtools/jars 1.4M/fabos/man 1.6M/fabos/lib 1.9M/fabos/webtools/htdocs 112k/usr/apache/conf 124k/etc/config 128k/lib/modules/default/kernel/drivers/pcmcia 12k/dev 12k/fabos/etc 12k/fabos/factory 12k/fabos/users/admin 12k/fabos/users/diag 12k/fabos/users/user 140k/usr/share 144k/fabos/webtools/bin 14M/fabos 160k/lib/modules/default/kernel 160k/lib/modules/default/kernel/drivers 160k/var/log 164k/fabos/share 16k/root 16k/usr/lib/rpm 188k/lib/modules 188k/lib/modules/default 2.1M/usr/apache 2.1M/usr/lib 2.6M/lib 2.7M/bin 212k/var/run 3.1M/boot 3.2M/fabos/webtools 3.3M/fabos/modules 3.5M/usr/bin 32k/lib/modules/default/kernel/drivers/net 32k/usr/man/cat1m 35M/ 364k/fabos/man/cat1d 36k/etc/webtools 36k/etc/webtools/conf 36k/fabos/users 36k/usr/man/cat1 /usr/bin/du -xh / | /bin/sort cont. 396k/fabos/man/cat1
2-288

4.0k/config 4.0k/core_files 4.0k/etc/cron.daily 4.0k/etc/default 4.0k/usr/apache/cgi-bin 4.0k/usr/man/cat5 4.0k/usr/man/cat8 4.0k/var/spool 4.0k/var/spool/cron 4.1M/fabos/sbin 432k/usr/apache/include 44k/etc/mail 504k/var/lib/rpm 508k/var/lib 60k/etc/pcmcia 640k/fabos/man/cat1m 68k/etc/rc.d/init.d 696k/fabos/bin 72k/etc/fabos 72k/fabos/standby_bin 76k/usr/apache/include/xml 76k/usr/man 780k/usr/apache/libexec 8.0k/fabos/standby_sbin 8.0k/var/tmp 8.9M/usr 804k/usr/apache/bin 80k/etc/rc.d 892k/var

/usr/bin/du -xh / | /bin/sort: 0 /core_files/arrd 0 /core_files/asd 0 /core_files/emd 0 /core_files/evmd 0 /core_files/fabricd 0 /core_files/fcpd 0 /core_files/fdmid 0 /core_files/fspfd 0 /core_files/fssme 0 /core_files/fwd 0 /core_files/msd 0 /core_files/nsd 0 /core_files/panic 0 /core_files/pdmd 0 /core_files/proxyfcg 0 /core_files/psd 0 /core_files/rcsd 0 /core_files/rpcd 0 /core_files/secd 0 /core_files/slapd 0 /core_files/snmpd 0 /core_files/sysctrld 0 /core_files/track_changes 0 /core_files/tsd 0 /core_files/webd 0 /core_files/weblinkerfcg 0 /core_files/zoned 0 /dev/fss 0 /etc/cron.d
2-289
0 /etc/cron.daily 0 /etc/cron.monthly 0 /etc/cron.weekly 0 /etc/logrotate.d 0 /etc/pcmcia/cis 0 /etc/rc.d/rc0.d 0 /etc/rc.d/rc1.d 0 /etc/rc.d/rc2.d 0 /etc/rc.d/rc3.d 0 /etc/rc.d/rc4.d 0 /etc/rc.d/rc5.d 0 /etc/rc.d/rc6.d 0 /etc/rpm 0 /export 0 /fabos/man/cat2 0 /fabos/man/cat3 0 /fabos/man/cat4 0 /fabos/man/cat5 0 /fabos/man/cat6 0 /fabos/man/cat7 0 /fabos/man/cat8 0 /fabos/man/cat9 0 /fabos/man/catl 0 /fabos/man/catn 0 /fabos/man/cato 0 /fabos/man/catp 0 /fabos/man/man1 0 /fabos/man/man1d 0 /fabos/man/man1m 0 /fabos/man/man2 0 /fabos/man/man3 0 /fabos/man/man4 0 /fabos/man/man5 0 /fabos/man/man6 0 /fabos/man/man7 0 /fabos/man/man8 0 /fabos/man/man9 0 /fabos/man/manl 0 /fabos/man/mann 0 /fabos/man/mano 0 /fabos/man/manp 0 /import 0 /initrd 0 /lib/modules/default/kernel/drivers/block 0 /lib/modules/default/kernel/drivers/i2c 0 /lib/modules/default/kernel/drivers/net 0 /users 0 /usr/apache/htdocs 0 /usr/lib/rpm 0 /usr/man/cat2 0 /usr/man/cat3 0 /usr/man/cat4 0 /usr/man/cat6 0 /usr/man/cat7 0 /usr/man/cat9 0 /var/lock 1.0M/usr/sbin 1.5M/sbin 1.6M/fabos/webtools/htdocs 1.7M/fabos/man 1.9M/usr/share/zoneinfo 104k/etc/fabos/services/SWBD21 108k/lib/security 112k/etc/rc.d 128k/etc/fabos/services
2-290

128k/lib/modules/default/kernel 128k/lib/modules/default/kernel/drivers 128k/lib/modules/default/kernel/drivers/pcmcia 12k /dev 12k /fabos/factory 12k /fabos/users/admin 12k /fabos/users/diag 12k /fabos/users/user 12k /usr/share/zoneinfo/Mexico 12k /usr/share/zoneinfo/Mideast 144k/usr/share/zoneinfo/Etc 156k/lib/modules 156k/lib/modules/default 160k/etc/config 164k/usr/share/zoneinfo/Pacific 16k /etc/fabos/services/SWBD21/opt1/chassis.svc 16k /etc/fabos/services/SWBD21/opt2/chassis.svc 16k /lib/rpm 16k /root 16k /usr/share/zoneinfo/America/Indiana 16k /usr/share/zoneinfo/Brazil 188k/var/run 2.1M/usr/apache 2.1M/usr/share 2.3M/fabos/webtools/jars 20k /etc/fabos/pki 20k /fabos/etc 212k/usr/share/zoneinfo/Europe 24k /etc/fabos/services/SWBD21/opt1/fcsw.svc 24k /etc/fabos/services/SWBD21/opt2/fcsw.svc 24k /etc/fabos/services/fcsw.svc 252k/lib/iptables 26M /fabos 288k/fabos/share 3.3M/bin 3.4M/fabos/lib 3.5M/usr/bin 3.9M/fabos/webtools 320k/usr/share/zoneinfo/Asia 32k /usr/man/cat1m 340k/etc/fabos 356k/fabos/man/cat1d 36k /fabos/users 36k /usr/man/cat1 36k /usr/share/zoneinfo/Antarctica 36k /usr/share/zoneinfo/Canada 4.0M/boot 4.0k/config 4.0k/etc/cron.hourly 4.0k/etc/default 4.0k/etc/fabos/lo 4.0k/fabos/libexec/frureplace 4.0k/usr/apache/cgi-bin 4.0k/usr/man/cat5 4.0k/usr/man/cat8 4.0k/usr/share/zoneinfo/Arctic 4.0k/var/log/webtools 4.0k/var/spool 4.0k/var/spool/cron 4.2M/lib 40k /etc/pam.d 432k/usr/apache/include 48k /etc/mail 48k /fabos/webtools/bin 48k /usr/share/zoneinfo/Atlantic
2-291
48k /usr/share/zoneinfo/Indian 496k/usr/share/zoneinfo/America 51M / 52k /etc/fabos/services/SWBD21/opt1 52k /etc/fabos/services/SWBD21/opt2 52k /usr/share/zoneinfo/US 556k/fabos/man/cat1 56k /usr/share/zoneinfo/SystemV 6.1M/fabos/libexec 60k /etc/pcmcia 60k /var/log 664k/var/lib/rpm 668k/var/lib 68k /fabos/standby_bin 76k /usr/apache/include/xml 76k /usr/man 776k/fabos/man/cat1m 788k/usr/apache/libexec 8.0k/fabos/standby_sbin 8.0k/usr/libexec 8.0k/usr/share/zoneinfo/America/Kentucky 8.0k/usr/share/zoneinfo/Chile 8.0k/var/tmp 84k /core_files 864k/fabos/sbin 880k/usr/apache/bin 88k /usr/apache/conf 88k /usr/share/zoneinfo/Australia 9.1M/fabos/modules 9.7M/usr 928k/var 92k /etc/rc.d/init.d 952k/fabos/bin 964k/usr/lib 968k/etc
2-292
Chapter
3
The commands listed in this chapter are not part of supportshow. However these commands prove useful and helpful. Note: Command Syntax and operands are not provided for the commands listed in this document. For information about syntax and operands for a command, refer to the Brocade Fabric OS Command Reference for the specific version of Fabric OS on your switch.
3-1
AgtcfgSet
Available in Fabric OS versions: v4.0.2, 4.1, 4.2 Troubleshooting Use: Use this command to show/set SNMP configuration values
switch:admin> agtcfgSet Customizing MIB-II system variables... At each prompt, do one of the following: <Return> to accept current value, enter the appropriate new value, <Control-D> to skip the rest of configuration, or <Control-C> to cancel any change. To correct any input mistake: <Backspace> erases the previous character, <Control-U> erases the whole line, sysDescr: [FC Switch] sysLocation: [End User Premise] sysContact: [Field Support.] swEventTrapLevel: (0..5) [3] authTrapsEnabled (true, t, false, f): [true] SNMP community and trap recipient configuration: Community (rw): [Secret C0de] Trap Recipients IP address in dot notation: [192.168.1.51] Community (rw): [OrigEquipMfr] Trap Recipients IP address in dot notation: [192.168.1.26] Community (rw): [private] Trap Recipients IP address in dot notation: [0.0.0.0] 192.168.64.88 Community (ro): [public] Trap Recipients IP address in dot notation: [0.0.0.0] Community (ro): [common] Trap Recipients IP address in dot notation: [0.0.0.0] Community (ro): [FibreChannel] Trap Recipients IP address in dot notation: [0.0.0.0] After setting the MIB-II parameters, the SNMP access control lists (ACLs) are configured. There are six ACLs to restrict SNMP get/set operations to hosts under a host subnet-area. Host-subnet-area is defined by comparing non-zero IP octets. For example, an ACL of "192.168.64.0" enables access for any hosts that start with "192.168.64.xx". An ACL check is turned off when all six entries contain "0.0.0.0". SNMP access list configuration: Access host subnet area in dot notation: Read/Write? (true, t, false, f): [true] Access host subnet area in dot notation: Read/Write? (true, t, false, f): [true] Access host subnet area in dot notation: Read/Write? (true, t, false, f): [true] Access host subnet area in dot notation: Read/Write? (true, t, false, f): [true] Access host subnet area in dot notation: Read/Write? (true, t, false, f): [true] Access host subnet area in dot notation: Read/Write? (true, t, false, f): [true] Committing configuration...done. switch:admin>
[0.0.0.0] 192.168.64.0 [0.0.0.0] [0.0.0.0] [0.0.0.0] [0.0.0.0] [0.0.0.0]
3-2
configure
Available in Fabric OS versions: None, this command information is included due to its relation to configshow outputs. Version Differences: v4.2 Example Output: No examples available Additional Example/Case Studies: Troubleshooting Use: - Use this command to change the following system configuration settings:
Fabric parameters Virtual channel settings Switch Operating Mode Zoning Operation parameters RSCN Transmission Mode NS Pre-zoning Mode Arbitrated Loop parameters System services Portlog events enable Do not run this command on an operational switch. First disable the switch using the switchDisable command.
Warning:
The configure command is navigated using a series of menus. Top level menus, and associated submenus consist of a text prompt, a list of acceptable values, and a default value (in brackets). Use the following options to control input: Return when entered at a prompt with no preceding input--accepts the default value (if applicable) and moves to the next prompt.
Interrupt (Control-C) Aborts the command immediately and ignores all changes made.This keystroke is common on many computers, but can be different on your system. End-of-file (Control-D) When entered at a prompt with no preceding input, terminates the command and saves changes made. This keystroke is common on many computers, but may be different on your system. Fabric Parameters There are a number of settings that control the overall behavior and operation of the Fabric. Some of these values, such as the domain, are assigned automatically by the Fabric and may differ from one switch to another in the Fabric. Other parameters, such as the BB credit, can be changed for specific applications or operating environments, but must be in agreement among all switches to allow formation of the Fabric. The Fabric parameters are as follows: D Table 3-1 Configure Command Fabric Parameters Command Domain Definition The domain number uniquely identifies the switch in a Fabric. The Fabric can automatically assign this value. The range of valid values varies depending on the switch model and other system parameter settings (refer to VC Encoded Address mode). The buffer-to-buffer (BB) credit represents the number of buffers available to attached devices for frame receipt. The range of allowed values varies depending on other system settings (see Unicast-only Operation).
BB Credit
3-3
Non-SupportShow Commands Configure Command Fabric Parameters Definition The Resource Allocation Time Out Value (R_A_TOV) is displayed in milliseconds. This variable works with the variable E_D_TOV to determine switch actions when presented with an error condition. Allocated circuit resources with detected errors are not released until the time value has expired. If the condition is resolved prior to the timeout, the internal timeout clock resets and waits for the next error condition. Error Detect Time Out Value (E_D_TOV) is displayed in milliseconds. This timer is used to flag a potential error condition when an expected response is not received (an acknowledgment or reply in response to packet receipt, for example) within the set time limit. If the time for an expected response exceeds the set value, then an error condition occurs. //The WAN_TOV parameter should be left to its default of [0]. This is made configurable only for internal testing purposes only. //The MAX_HOPS parameter was inadvertently displayed in this non-GA release of version 3.02a firmware. This is not a parameter that can be configured. //The WAN_RTT_DLY_MAX parameter should be left to its default of 200mS. This is made configurable only for internal debugging purposes only. The data field size specifies the largest possible value, in bytes, and advertises this value to other switches in the Fabric during construction of the Fabric as well as to other devices when they connect to the Fabric. Setting this to a value smaller than 2112 may result in decreased performance. When Sequence Level Switching is set to 1, frames of the same sequence from a particular source are transmitted together as a group. When this feature is set to 0, frames are transmitted interleaved among multiple sequences. Under normal conditions, Sequence Level Switching should be disabled for better performance. However, some host adapters have performance issues when receiving interleaved frames from multiple sequences. When there are such devices attached to the Fabric, Sequence Level Switching should be enabled. When Disable Device Probing is set to 1, devices that do not register with the Name Server are not present in the Name Server database. Set this mode only if the switch N_Port discovery process (PLOGI, PRLI, INQUIRY) causes an attached device to fail. When this mode is set to 1, all class F interswitch frames are transmitted as class 2 frames. This is to support remote Fabrics that involve ATM gateways that do not support class F traffic. When Sync IO mode is set to 1, FSPF frames are sent in synchronous mode (expecting ACKs back from the other side for every frame) that helps in detecting the failures in the link between the ATM gateways in remote Fabrics. When VC Encoded Address Mode is set to 1, frame source and destination address utilize an address format compatible with Brocade Silkworm 1000 switches. Set this mode only if the Fabric includes this type of switch. This is used to set the 256 port PID format that is used for core switches.
Table 3-1 Command R_A_TOV
E_D_TOV
Version 3.02a has three additional options under configure: WAN_TOV: (0..2000) [0] MAX_HOPS: (7..13) [7] ] WAN_RTT_DLY_MAX: (0.9500) [200] Data Field Size
Sequence Level Switching
Disable Device Probing
Suppress Class F Traffic
SYNC IO mode
VC Encoded Address Mode
Core Switch PID Format
3-4
Non-SupportShow Commands Table 3-1 Command Per-frame Route Priority Configure Command Fabric Parameters Definition
In addition to the eight virtual channels used in frame routing priority, support is also available for per-frame based prioritization when this value is set. When Per-frame Route Priority is set to 1, the virtual channel ID is used in conjunction with a frame header to form the final virtual channel ID. When this mode is set to 1, ISLs in a Fabric can be up to 100 km long. The exact distance level is determined by the per-port configuration on the E_Ports of each ISL. Both E_Ports in an ISL must be configured to run the same long distance level; otherwise, the Fabric will be segmented. The Extended Fabric License is required to set this mode.
Long Distance Fabric
Virtual Channel Settings The switch enables fine tuning for a specific application, by configuring the parameters for eight virtual channels. The first two virtual channels are reserved for switch internal functions and are not available for modification. The default virtual channel settings have already been optimized for switch performance. Changing the default values can improve switch performance, but can also degrade performance. Do not change these settings without fully understanding the effects of the changes. The Virtual Channel Setting fields are as follows:: Table 3-2 Configure Command Virtual Channel Settings
Zoning Operation Parameters Standard Mode Specify 1 to force the switch to issue interswitch traffic conforming to FCSW, or specify 0 to enable proprietary interswitch traffic. The default value is 0. This value must be set to 1 for interoperability. Specify 1 to disable using Node WWN when specifying nodes in the zone database, or specify 0 to enable using Node WWN when specifying nodes in the zone data. The default value is 1. This value must be set to 1 for interoperability.
Disable NodeName Zone Checking
RSCN Transmission Mode End-device RSCN Transmission Mode NS Pre-zoning Mode Pre-zoned responses Mode Specify 0 for Standard Mode, or 1 for Pre-zoning On. Specify 0 for RSCN with single PID, 1 for RSCN with multiple PIDs, or 2 Fabric RSCN.
3-5
Arbitrated Loop Settings The Arbitrated Loop Setting fields are as follows: Table 3-3 Configure Command Arbitrated Loop Settings
Send FAN frames?
Specifies that Fabric address notification (FAN) frames be sent to public loop devices to notify them of their node ID and address. When set to 1, frames are sent; when set to 0 frames are not sent. Following the completion of loop initialization, a remote state change notification (RSCN) is issued when FL_Ports detect the presence of new devices or the absence of pre-existing devices. When set, a RSCN is issued upon completion of loop initialization, regardless of the presence or absence of new or preexisting devices. If this is set, a CLS is returned immediately to an OPN if no buffers are available. This is required for TachLite. This option disallows ALPA values from being 0. When this is set, all looplets including the ones not in the same zone are always re-initialized. This is required for certain RAID subsystems to work properly during failover.
Always send RSCN?
Enable CLOSE on OPEN received? Do Not Allow AL_PA 0x00? Initialize All Looplets?
System Services Descriptions of the system service setting fields are as follows: Table 3-4 Configure Command System Services Parameters
rstatd
Dynamically enables or disables a server that returns information about system operation information through remote procedure calls (RPC). The protocol provides for a wide-range of system statistics; however, only Ethernet interface statistics (see ifShow) and system up time (see uptime) are supported. The retrieval of this information is supported by a number of operating systems that support RPC. Most UNIX-based systems (HP-UX, Irix, Linux, Solaris, etc.) use the rup and rsysinfo commands to retrieve the information. See your local system documentation for the appropriate usage of these or equivalent commands. Dynamically enables or disables a server that returns information about the user logged into the system through remote procedure calls (RPC). The information returned includes user login name, the system name, login protocol or type, login time, idle time, and remote login location (if applicable). The retrieval of this information is supported by a number of operating systems that support RPC. On most UNIX-based systems (HP-UX, Irix, Linux, Solaris, etc.) the command to retrieve the information is rusers. See your local system documentation for the appropriate usage of this or equivalent command. Dynamically enables or disables a service that handles RPC requests for the API server. This disables Read Link Error Status probing of the ALPAs.
rusersd
Rapid Disable RLS probing
3-6
Ficonshow
Displays the contents of the specified FICON management database. Synopsis ficonshow RNID [fabric] ficonshow LIRR [fabric] ficonshow SwitchRNID [fabric] ficonshow RLIR [fabric] ficonshow ILIR [fabric] Availability All users. Description Use this command to display the contents of a FICON management database. The first operand for ficonshow is the name of the database to display. If the second operand is absent, the command displays the members of the named database that are local to the switch on which the command was issued. If the second operand is present, it must be entered fabric exactly as shown, and this specifies that all members are displayed, both local and remote. The following information might be displayed, depending on what database you enter and which operands you use with the command: Domain Fabric WWN Flag Displays the domain ID. Displays the fabric WWN. Indicates if the node is valid, not valid, or not current. Flag values indicate the following: Fmt 0x00 indicates that the node ID of the (storage port for RNID, switch for SwitchRNID) is valid. 0x10 indicates that the node ID of the channel port is valid. 0x20 indicates that the node ID of the storage port is not current. 0x30 indicates that the node ID of the channel port is not current. 0x40 indicates that the node ID of the (storage port for RNID, switch for RLIR) is not valid. 0x50 indicates the node ID of the channel port is not valid.
Displays the record-registration format.
FRU Failure Description Indicates the FRU failure type as one of the following: WWN card [unit number] Power Supply [unit number] Hardware Slot [unit number] Blower [unit number]
FRU Part Number Displays the FRU part number. FRU Serial Number Displays the FRU serial number. Incident Count Displays the incident count. This number increases by 1 for each incident within the individual switch. Link Incident Description Same as Link Incident Type.
3-7
Link Incident Type Indicates the link incident type as one of the following: Listener PID Bit-error-rate threshold exceeded Loss of Signal or Synchronization NOS recognized Primitive Sequence timeout Invalid Primitive Sequence for Port State
Same as PID.
Listener Port Type Same as Port Type. Listener Port WWN Displays the channel HBA port World Wide Name. Listener Type Indicates the listener type as one of the following: Manufacturer Conditional: This port receives a link incident record if no other recipients from the established registration list have been chosen. Unconditional: This port is always chosen as a recipient of a link incident record.
Displays the manufacture name or code.
Model Number Displays the model number. Node ParametersSame as Parameters. Parameters Displays the node type for the switch in three bytes: 0xAABBCC. The meaning of each byte is described here: Parm Byte AA: 0x20 FC-SB-2 and updates. Byte BB: 0x0a Switch. Byte CC: 0x00 Port number. It is dynamically assigned whenever a link incident occurs.
Displays the incident node parameters type in three bytes: 0xAABBCC. The meaning of each byte is described below: Byte AA: 0x00 Reserved 0x20 FC-SB-2 and updates. 0x40 Other FC-4s, including FCP and updates. 0x60 FC-SB-2 and updates and other FC-4s, including FCP and updates. 0x80 FC-4 support not specified. 0xa0 Reserved. 0xc0 Reserved. 0xe0 Vendor specific. Byte BB: 0x00 Unspecified class 0x01 Direct access storage device, if it is a storage port; otherwise, it is not channel-to-channel capable. 0x02 Magnetic tape, if it is a storage port; otherwise, if it is a reserved field for a channel port. 0x03 Input unit record, if it is a storage port; otherwise, it is a reserved field for a channel port. 0x04 Output unit, if it is a storage port; otherwise, it is a reserved field for a channel port. 0x05 Reserved field for a channel port. 0x06 Controller, if it is a storage port; otherwise, it is a reserved field for a channel port.
3-8
0x07 Terminal - Full screen if it is a storage port; otherwise, it is a reserved field for a channel port. 0x08 Terminal - Line mode if it is a storage port; otherwise, it is an emulated control unit support only. 0x09 Reserved. 0x10 Switch, if it is a switch device; otherwise, it is reserved. 0x0b-0xff Reserved. Byte CC: 0x00 if storage CU port has registered with the switch. 0xID CHIPID if channel port has registered with the switch. 0xPN If switch has registered with the channel, then PN represents the FL_Port number.
Part Number PID
Displays switch chassis part number. Displays the 24-bit Fibre Channel Port address in 0xDDAAPP format. DD is Domain ID. AA is Area ID. PP is AL_PA ID.
Plant of Manufacture Displays the manufacture plant name or code. Port Port Status Physical port number. Displays the status of the port. One of the following messages is displayed: Port Type Link degraded but operational Link not operational
Displays the port type. U is unknown. N is N_Port. NL is NL_Port.
Protocol
Displays whether the traffic is using FICON or FCP.
Registered Node WWN Displays the devices node World Wide Name associated with the device HBA. Registered Port WWN Displays the devices (channel or storage CU) port World Wide Name associated with the device HBA. Sequence Number Displays the sequence number of the self-describing node. Serial Number Displays the switch serial number. Switch node WWN Displays the switch node World Wide Name. Switch Port WWN Displays the switch port World Wide Name. Switch WWN Tag TS Format Time Stamp Type Type Number Operands This command has the following operands: Displays the switch World Wide Name. Displays the physical identifier for the self-describing node interface. Displays the Time Server format. Displays the time stamp expressed in the date format. Same as Port Type. Displays the type number of the self-describing node. It also describes the machine type.
3-9
3
database
Non-SupportShow Commands Specify the database to display. Valid values are: RNID LIRR SwitchRNID RLIR ILIR This operand is required.
fabric Example
Specify fabric to display both local and remote information. This operand must be entered exactly as fabric. This operand is optional.
This section contains of the examples of the ficonshow command for each database.
3-10
Non-SupportShow Commands Example: To display the local RNID database:

switch:admin> ficonshow rnid { {Fmt Type PID Registered Port WWN 0x18 N 0d0500 50:05:07:64:01:00:15:af Type number: 002064 Model number: 103 Manufacturer: IBM Plant of Manufacture: 02 Sequence Number: 0000000169CA tag: 1e05 } {Fmt Type PID Registered Port WWN 0x18 N 0d0900 50:05:07:64:01:00:14:02 Type number: 003868 Model number: 002 Manufacturer: IBM Plant of Manufacture: PK Sequence Number: 000000000057 tag: 0111 } {Fmt Type PID Registered Port WWN 0x18 N 0d0d00 50:05:07:63:00:cd:96:aa Type number: 002105 Model number: 800 Manufacturer: IBM Plant of Manufacture: 13 Sequence Number: 000000022802 tag: 00ac } } 3 valid entries, 0 not current entries The Local RNID database has 3 entries.
Registered Node WWN flag Parm 50:05:07:64:00:c1:69:ca 0x10 0x20011e
Registered Node WWN flag Parm 50:05:07:64:00:c1:69:ca 0x10 0x20011f
Example: To display the local and remote LIRR database:

switch:admin> ficonshow lirr fabric {Fmt Type PID Listener Port WWN 0x18 N 0a0000 50:05:07:64:01:40:14:0c 0x18 N 0a1000 50:05:07:64:01:40:14:02 0x18 N 0a1100 50:05:07:64:01:00:14:02 0x18 N 0a1200 50:05:07:64:01:40:16:13 0x18 N 0a1300 50:05:07:64:01:00:16:13 0x18 N 0a2000 50:05:07:64:01:40:0b:45 0x18 N 0b1000 50:05:07:64:01:00:13:f6 0x18 N 0b1400 50:05:07:64:01:40:0f:e6 0x18 N 0b1600 50:05:07:64:01:00:0f:e6 0x18 N 0b2000 50:05:07:64:01:40:13:f6 0x18 N 0b2400 50:05:07:64:01:00:0f:c4 0x18 N 0b2c00 50:05:07:64:01:60:09:32 0x18 N 0b2d00 50:05:07:64:01:20:09:32 0x18 N 0b2e00 50:05:07:64:01:40:0f:bb 0x18 N 0b2f00 50:05:07:64:01:00:0f:bb 0x18 N 0b3400 50:05:07:64:01:00:14:95 0x18 N 0c0400 50:05:07:64:01:40:16:16 0x18 N 0c0900 50:05:07:64:01:00:16:16 } The LIRR database has 18 entries. Switch Port WWN 20:00:00:60:69:80:0f:c8 20:10:00:60:69:80:0f:c8 20:11:00:60:69:80:0f:c8 20:12:00:60:69:80:0f:c8 20:13:00:60:69:80:0f:c8 20:20:00:60:69:80:0f:c8 20:10:00:60:69:80:0f:c9 20:14:00:60:69:80:0f:c9 20:16:00:60:69:80:0f:c9 20:20:00:60:69:80:0f:c9 20:24:00:60:69:80:0f:c9 20:2c:00:60:69:80:0f:c9 20:2d:00:60:69:80:0f:c9 20:2e:00:60:69:80:0f:c9 20:2f:00:60:69:80:0f:c9 20:34:00:60:69:80:0f:c9 20:04:00:60:69:90:02:12 20:09:00:60:69:90:02:12 Listener Type Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional
3-11
Example: To display the local SwitchRNID database:

switch:admin> ficonshow switchRNID { {Switch WWN flag Parm 10:00:00:60:69:80:1e:4e 00 200a00 Type number: SLKWRM Model number: 12K Manufacturer: BRD Plant of Manufacture: CA Sequence Number: 0FT02X801E4E tag: 50ff } } The Local switch RNID database has 1 entries. switch:admin>
Example: To display the local RLIR database:

switch:user> ficonshow RLIR { {Fmt 0x18 Port Link Type PID Port Incident Count TS Format Time Stamp F d00d00 13 2 Time server Tue Sep 30 04:11:01 2003 Status: Link not operational Failure Type: Loss of signal or synchronization Flag 0x10 Node Parameters 0x200127
Registered Port WWN Registered Node WWN 50:05:07:64:01:40:13:dd 50:05:07:64:00:c1:69:ca Type Number: 002064 Model Number: 103 Manufacturer: IBM Plant of Manufacture: 02 Sequence Number: 0000000169CA tag: 270d Switch Port WWN Switch Node WWN 20:0d:00:60:69:90:0c:a8 10:00:00:60:69:90:0c:a8 Type Number: SLKWRM Model Number: 12K Manufacturer: BRD Plant of Manufacture: CA Sequence Number: 0FA03X900CA8 tag: d00d } } The RLIR database has 1 entry. switch:user>
Flag 0x00
Node Parameters 0x200a0d
3-12
Non-SupportShow Commands Example: To display the local ILIR database:

switch:user> ficonshow ILIR { {FRU Failure [2]: Power Supply[2] failure occurred on Mon Jan 13 12:11:38 2003 Fmt 0x18 Protocol Domain Fabric WWN Switch WWN FICON 80 10:00:00:60:69:33:33:33 10:00:00:60:69:80:1e:4e 23000000602 FL2L0001071
FRU part number: FRU serial number:
{Listener Port Type Listener PID Listener Port WWN N 0x502b00 50:05:07:64:01:00:15:8d } } {FRU Failure [3]: Power Supply[4] failure occurred on Mon Jan 13 12:11:38 2003 Fmt 0x18 Protocol Domain Fabric WWN Switch WWN FICON 80 10:00:00:60:69:33:33:33 10:00:00:60:69:80:1e:4e 23000000602 FL2L0001060
FRU part number: FRU serial number:
{Listener Port Type Listener PID Listener Port WWN N 0x502b00 50:05:07:64:01:00:15:8d } } } The local ILIR database has 2 entries. switch:user>
3-13
FirmwareCommit
Available in Fabric OS versions: 4.0.2c Troubleshooting Use: Use this command to commit switch firmware update Use this command to commit a firmware download to a CP. This command copies an updated firmware image to both partitions and commits both partitions of a CP to an updated version of the firmware. This must be done after each firmwaredownload, and after the switch has been rebooted and a sanity check is performed to make sure the new image is fine. For switches which have flash memory set into two equal partitions, the primary partition is the where the system boots from, the secondary partition is where a copy of the firmware is stored, in case the primary partition is damaged. To maintain the integrity of the firmware image in the flash memory, the firmwaredownload command updates the secondary partition only. When firmwaredownload completes successfully and the CP is rebooted, the system switches the primary partition (with the old firmware) to the secondary, and the secondary partition (with the new firmware) to the primary. The default behavior of the firmwaredownload command automatically runs the firmwarecommit command after the reboot. For the cautious, the firmwaredownload command has an option to disable auto-commit of the new firmware. If you decide to disable the auto-commit option when running firmwaredownload, then, after the CP is rebooted, you must execute one of two commands:
run the firmwarecommit command to copy the primary partition (with new firmware) to the secondary, and commit the new firmware to both partitions of the CP. or, run the firmwarerestore command to copy the secondary partition (with the old firmware) to the primary, and back out of the new firmware download. The firmwarerestore command can only be run if auto-commit was disabled during the firmwaredownload.
Example 3-1: To commit a firmware file:

switch:admin> firmwarecommit writing flash 0 .................. writing flash 1 .................. commit complete
3-14
Firmwaredownload
Available in Fabric OS versions: 4.0.2c Troubleshooting Use: Use this command to download switch firmware from a remote host or from a local directory. Use this command to download switch firmware from a FTP server or from a local (NFS) directory to the switch's non-volatile storage area. The new firmware is in the form of RPM packages with names defined in a pfile. Pfile is a binary file which contains specific firmware information (time stamp, platform code, version, etc.) and the names of packages of the firmware to be downloaded. These packages are made available periodically to add features or to remedy defects. Contact customer support to obtain information about available firmware versions. In the Silkworm 12000, this command by default downloads firmware image to both CPs in a rollover mode to prevent disruption to application services. This operation depends on HA support. If HA is not available, a user will still be able to upgrade the CPs one at a time using -s option. The Silkworm 3900 and each CP of the Silkworm 12000 have two partitions of non-volatile storage areas, a primary and a secondary, to store two firmware images. Firmwaredownload will always load the new image into the secondary partition and will swap the secondary partition to be the primary. It will then reboot the CP and activate the new image. Finally, it will perform firmwarecommit automatically to copy the new image to the other partition unless -s is used. The command supports both non-interactive and interactive modes. If it is invoked without any command line parameters, or if there is any syntax error in the parameters, the command will go into the interactive mode in which the user is prompted for input. Note: Refer to the Fabric OS Procedures Guide Firmware Download chapter for limitations when changing Fabric OS versions. When installing Fabric OS v4.1, the procedure may vary depending on the current version of Fabric OS from which you are migrating.
Example: To download the firmware to a HA switch:

switch:admin> firmwareDownload 192.168.166.30,johndoe,/pub/dist/release.plist,12345 You can run firmwareDownloadStatus from a telnet session to get the status of this command. This command will cause the active CP to reset. This will cause disruption to devices attached to both switch 0 and switch 1 momentarily and will require that existing telnet sessions be restarted. Do you want to continue [Y]: y FirmwareDownload has started in Standby CP. It may take up to 10 minutes. And you will the following on Standby CP: Start to install packages...... dir ################################################## terminfo ################################################## termcap ################################################## glibc ################################################## sin ################################################## Write kernel image into flash Verification SUCCEEDED Firmwaredownload completes successfully.
Diagnostics: The following issues may cause a firmware download to fail. Table 3-1
The switch does not know Host Host cannot be reached by the switch User does not have permission on host The pfile does not exist on host The pfile is not in the right format
Package specified in the pfile doesn't exist The FTP server is not running on host Running firmwaredownload during POST A loss of power to the switch
3-15
Firmwaredownloadstatus
Available in Fabric OS versions: 4.0.2c + Troubleshooting Use: Use this command to display the status of a firmware download Use this command (introduced in V4.0.2) to display an event log that records the progress and status of the current firmwaredownload command. The event log is created by the current firmwaredownload command and is kept until another firmwaredownload command is issued. There is a timestamp associated with each event. In a Silkworm 12000, when firmwaredownloadstatus is run, the event logs in the two CPs are synchronized. The command can be run from either CP. Example 3-2: To display the status of a firmware download:
switch:admin> firmwaredownloadstatus [1]: Tue Jan 18 13:21:25 2005 cp1: FirmwareDownload has started on Standby CP. It may take up to 10 minutes. [1]: Tue Jan 18 13:21:35 2005 cp1: FirmwareDownload has completed successfully on Standby CP. [2]: Tue Jan 18 13:21:37 2005 cp1: Standby CP reboots. [3]: Tue Jan 18 13:24:44 2005 cp1: Standby CP boots up. [4]: Tue Jan 18 13:24:45 2005 cp1: Standby CP booted up with new firmware. <output truncated> [9]: Tue Jan 18 13:33:54 2005 cp0: Standby CP booted up with new firmware. [10]: Tue Jan 18 13:33:56 2005 cp0: Firmwarecommit has started on both Active and Standby CPs. [11]: Tue Jan 18 13:38:29 2005 cp0: FirmwareCommit has completed successfully on Active CP. [12]: Tue Jan 18 13:38:30 2005 cp0: FirmwareDownload has completed successfully.
Note:
Command output helpful to follow download status to verify that all is going well.
Note:
Both CPs must have the same version of firmware to use auto magic firmwaredownload process and both partitions on each CP must have the same version of firmware. If Local CP and Remote CP have different versions of firmware, please retry firmwaredown load on a CP. If one of the CPs partitions has a different version of firmware try either the firmwareCommit or the firmwarerestore command
Since stories shed the best light firmwaredownloadstatus, myid, haShow, and firmwareshow outputs were captured while a SilkWorm 12000 firmwaredownload process was in progress, curved notes act as explanation headers This firmwaredownloadstatus output was taken at the end of the firmwaredownload process, from the new ACTIVE CP, and represents a great summary from which to view the steps well follow: Example 3-3:
RSL_12K8_SW1:admin> firmwaredownloadstatus [0]: Thu Jun 12 19:06:25 2003 cp0: Firmwaredownload has started on Standby CP. It may take up to 10 minutes. [1]: Thu Jun 12 19:11:56 2003 cp0: Firmwaredownload has completed successfully on Standby CP. [2]: Thu Jun 12 19:11:59 2003 cp0: Standby CP reboots. [3]: Thu Jun 12 19:14:55 2003 cp0: Standby CP booted up. [4]: Thu Jun 12 19:17:33 2003 cp1: Active CP forced failover succeeded. Now this CP becomes Active.
3-16
[5]: Thu Jun 12 19:17:36 2003 cp1: Firmwaredownload has started on Standby CP. It may take up to 10 minutes. [6]: Thu Jun 12 19:23:09 2003 cp1: Firmwaredownload has completed successfully on Standby CP. [7]: Thu Jun 12 19:23:12 2003 cp1: Standby CP reboots. [8]: Thu Jun 12 19:26:33 2003 cp1: Standby CP booted up with new firmware. [9]: Thu Jun 12 19:26:36 2003 cp1: Firmwarecommit has started on both Active and Standby CPs. [10]: Thu Jun 12 19:32:23 2003 cp1: Firmwarecommit has completed successfully on Active CP. [11]: Thu Jun 12 19:32:24 2003 cp1: Firmwaredownload command has completed successfully.
Example 3-4: The firmwaredownload was invoked from the active CP:
myid Current Switch: Session Detail: RSL_12K8_SW1 RSL_12K8_SW1 (10.255.255.150) Active
Redundant
RSL_12K8_SW1:admin> hashow Local CP (Slot 5, CP0): Active Remote CP (Slot 6, CP1): Standby, Healthy HA enabled, Heartbeat Up, HA State synchronized RSL_12K8_SW1:admin> firmwareshow Local CP (Slot 5, CP0): Active Primary partition:v4.1.0 Secondary Partition:v4.1.0 Remote CP (Slot 6, CP1): Standby Primary partition:v4.1.0 Secondary Partition:v4.1.0 Note: If Local CP and Remote CP have different versions of firmware, please retry firmwaredownload command. RSL_12K8_SW1:admin> firmwaredownload This command will upgrade both CPs in the switch. If you want to upgrade a single CP only, please use -s option. You can run firmwareDownloadStatus to get the status of this command. This command will cause the active CP to reset and will require that existing telnet, secure telnet or SSH sessions be restarted. RSL_12K8_SW1:admin> firmwaredownload This command will upgrade both CPs in the switch. If you want to upgrade a single CP only, please use -s option. You can run firmwareDownloadStatus to get the status of this command. This command will cause the active CP to reset and will require that existing telnet, secure telnet or SSH sessions be restarted. Do you want to continue [Y]: y Server Name or IP Address: 10.255.253.6 User Name: root File Name: /firmware/v4.1.1_rc1/release.plist Password: Firmwaredownload has started on Standby CP. It may take up to 10 minutes.
3-17
Firmwaredownload has completed successfully on Standby CP. Standby CP reboots. Standby CP booted up. Standby CP booted up with new firmware.
Note:
Information captured from current standby, CP1, before and just after firmwaredownload was initiated from current active CP0:
myid Current Switch: Session Detail:
RSL_12K8_SW1 cp1 (10.255.255.152) Standby
Redundant
RSL_12K8_SW1:admin> hashow Local CP (Slot 6, CP1): Standby Remote CP (Slot 5, CP0): Active HA enabled, Heartbeat Up, HA State synchronized RSL_12K8_SW1:admin> firmwareshow Local CP (Slot 6, CP1): Standby Primary partition:v4.1.0 Secondary Partition:v4.1.0 Remote CP (Slot 5, CP0): Active Primary partition:v4.1.0 Secondary Partition:v4.1.0 Note: If Local CP and Remote CP have different versions of firmware, please retry firmwaredownload command. NOTE: FIRMWAREDOWNLOAD initiated from current active cp0, then this output captured from cp1: RSL_12K8_SW1:admin> firmwareshow Local CP (Slot 6, CP1): Standby Primary partition:v4.1.0 Secondary Partition:Version is not available Remote CP (Slot 5, CP0): Active Primary partition:v4.1.0 Secondary Partition:v4.1.0 Note: If Local CP and Remote CP have different versions of firmware, please retry firmwaredownload command. _The system is going down for reboot NOW !!
Note:
Logged back into CP1 and watched it become the active cp, note firmwareshow and firmwaredownload status output show CP0, new standby, booting up:
myid Current Switch: RSL_12K8_SW1 Session Detail: cp1 (10.255.255.152) Standby RSL_12K8_SW1:admin> firmwareshow
Redundant
Broadcast message from root Thu Jun 12 19:15:05 2003... ******************************************************************** Warning: Control Processor (CP) has changed state to Active. All Active commands are available now. ******************************************************************** Local CP (Slot 6, CP1): Active Primary partition:v4.1.1_rc1 Secondary Partition:v4.1.0 Remote CP is Non-redundant. RSL_12K8_SW1:admin> firmwaredownloadstatus
3-18
[0]: cp0: [1]: cp0: [2]: cp0: [3]: cp0: Thu Jun 12 19:06:25 2003 Firmwaredownload has started on Standby CP. It may take up to 10 minutes. Thu Jun 12 19:11:56 2003 Firmwaredownload has completed successfully on Standby CP. Thu Jun 12 19:11:59 2003 Standby CP reboots. Thu Jun 12 19:14:55 2003 Standby CP booted up.
Note:
After the new standby, CP0, reboots this information was captured from CP1, you can see that the firmware is being downloaded to the 2ndary partition:
RSL_12K8_SW1:admin> firmwareshow Local CP (Slot 6, CP1): Active Primary partition:v4.1.1_rc1 Secondary Partition:v4.1.0 Remote CP (Slot 5, CP0): Standby Primary partition:v4.1.0 Secondary Partition:Version is not available RSL_12K8_SW1:admin> firmwaredownloadstatus [0]: Thu Jun 12 19:06:25 2003 cp0: Firmwaredownload has started on Standby CP. It may take up to 10 minutes. [1]: Thu Jun 12 19:11:56 2003 cp0: Firmwaredownload has completed successfully on Standby CP. [2]: Thu Jun 12 19:11:59 2003 cp0: Standby CP reboots. [3]: Thu Jun 12 19:14:55 2003 cp0: Standby CP booted up. [4]: Thu Jun 12 19:17:33 2003 cp1: Active CP forced failover succeeded. Now this CP becomes Active. [5]: Thu Jun 12 19:17:36 2003 cp1: Firmwaredownload has started on Standby CP. It may take up to 10 minutes.
Note:
Here you see CP0, the new standby, rebooting:
RSL_12K8_SW1:admin> firmwareshow Local CP (Slot 6, CP1): Active Primary partition:v4.1.1_rc1 Secondary Partition:v4.1.0 Remote CP is Non-redundant. RSL_12K8_SW1:admin> firmwaredownloadstatus [0]: Thu Jun 12 19:06:25 2003 cp0: Firmwaredownload has started on Standby CP. It may take up to 10 minutes. [1]: cp0: [2]: cp0: Thu Jun 12 19:11:56 2003 Firmwaredownload has completed successfully on Standby CP. Thu Jun 12 19:11:59 2003 Standby CP reboots.
[3]: Thu Jun 12 19:14:55 2003 cp0: Standby CP booted up. [4]: Thu Jun 12 19:17:33 2003 cp1: Active CP forced failover succeeded. Now this CP becomes Active.
3-19
[5]: Thu Jun 12 19:17:36 2003 cp1: Firmwaredownload has started on Standby CP. It may take up to 10 minutes. [6]: Thu Jun 12 19:23:09 2003 cp1: Firmwaredownload has completed successfully on Standby CP. [7]: Thu Jun 12 19:23:12 2003 cp1: Standby CP reboots.
Note:
Here we see firmwareCommit being executed on CPs, it will go to the new standby CP first and then the current active CP, notice that HA enabled, heartbeat and HA synchronization states are healthy:
RSL_12K8_SW1:admin> firmwareshow Local CP (Slot 6, CP1): Active Primary partition:v4.1.1_rc1 Secondary Partition:Version is not available Remote CP (Slot 5, CP0): Standby Primary partition:v4.1.1_rc1 Secondary Partition:Version is not available RSL_12K8_SW1:admin> hashow Local CP (Slot 6, CP1): Active Remote CP (Slot 5, CP0): Standby, Healthy HA enabled, Heartbeat Up, HA State synchronized RSL_12K8_SW1:admin> firmwaredownloadstatus [0]: Thu Jun 12 19:06:25 2003 cp0: Firmwaredownload has started on Standby CP. It may take up to 10 minutes. [1]: Thu Jun 12 19:11:56 2003 cp0: Firmwaredownload has completed successfully on Standby CP. [2]: Thu Jun 12 19:11:59 2003 cp0: Standby CP reboots. [3]: Thu Jun 12 19:14:55 2003 cp0: Standby CP booted up. [4]: Thu Jun 12 19:17:33 2003 cp1: Active CP forced failover succeeded. Now this CP becomes Active. [5]: Thu Jun 12 19:17:36 2003 cp1: Firmwaredownload has started on Standby CP. It may take up to 10 minutes. [6]: Thu Jun 12 19:23:09 2003 cp1: Firmwaredownload has completed successfully on Standby CP. [7]: Thu Jun 12 19:23:12 2003 cp1: Standby CP reboots. [8]: Thu Jun 12 19:26:33 2003 cp1: Standby CP booted up with new firmware. [9]: Thu Jun 12 19:26:36 2003 cp1: Firmwarecommit has started on both Active and Standby CPs.
Note:
Here we see myid, haShow and firmwareshow outputs from both CPs after the process is done. CP0 became the standby CP. CP1 is the new Active CP. Both CPs have new version of firmware committed. Process is complete
This first output is from the new standby CP0:

myid Current Switch: Session Detail: RSL_12K8_SW1 cp0 (10.255.255.151) Standby
Redundant
RSL_12K8_SW1:admin> hashow Local CP (Slot 5, CP0): Standby Remote CP (Slot 6, CP1): Active HA enabled, Heartbeat Up, HA State synchronized
3-20
RSL_12K8_SW1:admin> firmwareshow Local CP (Slot 5, CP0): Standby Primary partition:v4.1.1_rc1 Secondary Partition:v4.1.1_rc1 Remote CP (Slot 6, CP1): Active Primary partition:v4.1.1_rc1 Secondary Partition:v4.1.1_rc1 Note: If Local CP and Remote CP have different versions of firmware, please retry firmwaredownload command.
This second output is from the new active CP1 and included finished firmwaredownloadstatus output:
RSL_12K8_SW1:admin> myid Current Switch: RSL_12K8_SW1 Session Detail: cp1 (10.255.255.152) Active
Redundant
RSL_12K8_SW1:admin> hashow Local CP (Slot 6, CP1): Active Remote CP (Slot 5, CP0): Standby, Healthy HA enabled, Heartbeat Up, HA State synchronized RSL_12K8_SW1:admin> firmwareshow Local CP (Slot 6, CP1): Active Primary partition:v4.1.1_rc1 Secondary Partition:v4.1.1_rc1 Remote CP (Slot 5, CP0): Standby Primary partition:v4.1.1_rc1 Secondary Partition:v4.1.1_rc1
Note:
If Local CP and Remote CP have different versions of firmware, please retry firmwaredownload command.
RSL_12K8_SW1:admin> firmwaredownloadstatus [0]: Thu Jun 12 19:06:25 2003 cp0: Firmwaredownload has started on Standby CP. It may take up to 10 minutes. [1]: Thu Jun 12 19:11:56 2003 cp0: Firmwaredownload has completed successfully on Standby CP. [2]: Thu Jun 12 19:11:59 2003 cp0: Standby CP reboots. [3]: Thu Jun 12 19:14:55 2003 cp0: Standby CP booted up. [4]: Thu Jun 12 19:17:33 2003 cp1: Active CP forced failover succeeded. Now this CP becomes Active. [5]: Thu Jun 12 19:17:36 2003 cp1: Firmwaredownload has started on Standby CP. It may take up to 10 minutes. [6]: Thu Jun 12 19:23:09 2003 cp1: Firmwaredownload has completed successfully on Standby CP. [7]: Thu Jun 12 19:23:12 2003 cp1: Standby CP reboots. [8]: Thu Jun 12 19:26:33 2003 cp1: Standby CP booted up with new firmware. [9]: Thu Jun 12 19:26:36 2003 cp1: Firmwarecommit has started on both Active and Standby CPs. [10]: Thu Jun 12 19:32:23 2003 cp1: Firmwarecommit has completed successfully on Active CP. [11]: Thu Jun 12 19:32:24 2003 cp1: Firmwaredownload command has completed successfully.
3-21
Firmwarerestore
Available in Fabric OS versions: 4.0.2 + Troubleshooting Use: Use this command to restore old active firmware image Use this command to restore the old active firmware image. This command can only be run if autocommit was disabled during the firmwaredownload. After a firmwaredownload and a reboot (with auto-commit disabled), the downloaded firmware will become active. If you then do not want to commit the firmware, and instead want to restore the old firmware, run firmwarerestore. After running firmwarerestore, you can run firmwaredownload again. This command will reboot the system and make the old firmware active. After reboot, both primary and secondary partitions are restored to the old firmware. This command will only take action if the system is booted after a firmwaredownload. Otherwise, it will return with an error code. Example 3-5: To restore old active firmware image:
switch:admin> firmwarerestore Restore Kernel Image... ................................ No firmware undo is needed switch:admin>
3-22
fwconfigure
Available in Fabric OS versions: All Note: This command requires a Fabric Watch License.
Version Differences: Different versions offer different FW options - some do not allow security, some do. Troubleshooting Use: Use this command to display and modify the configuration and status of Fabric Watch Use this command to display and modify threshold information for the Fabric Watch configuration. Switch elements monitored by Fabric Watch are divided into classes, which are further divided into areas. In addition, each area can include multiple thresholds. Example 3-6: Fwconfigure and sub category examples:
fwconfigure 1 : Environment class 2 : SFP class 3 : Port class 4 : Fabric class 5 : E-Port class 6 : F/FL Port (Optical) class 7 : Alpa Performance Monitor class 8 : EE Performance Monitor class 9 : Filter Performance Monitor class 10 : Security class 11 : Switch Availability Monitor class 12 : Quit Select a class => : (1..12) [12] 1 1 : Temperature 2 : Fan 3 : Power Supply 4 : return to previous page Select an area => : (1..4) [4] 1 Index ThresholdName Status CurVal LastEvent LasteventTime LastVal LastState ================================================================================ 1 envTemp001 enabled 21 C inBetween Thu Jun 12 19:15:47 2003 20 C Normal 2 envTemp002 enabled 21 C inBetween Thu Jun 12 19:15:47 2003 20 C Normal 3 envTemp003 enabled 33 C inBetween Thu Jun 12 19:15:47 2003 33 C Normal 4 envTemp004 enabled 33 C inBetween Thu Jun 12 19:15:47 2003 33 C Normal 1 : refresh 2 : disable a threshold 3 : enable a threshold 4 : advanced configuration 5 : return to previous page Select choice => : (1..5) [5] 4 Index ThresholdName 1 envTemp001 2 envTemp002 3 envTemp003 4 envTemp004 BehaviorType Triggered Triggered Triggered Triggered BehaviorInt 1 1 1 1
3-23
Threshold boundary level is set at : Default Default C 0 75 10 Custom C 0 75 10
Unit Time base Low High BufSize
Threshold alarm level is set at : Default Errlog-1, SnmpTrap-2, RapiTrap-8 EmailAlert-16 Valid alarm matrix is 27 Default 0 0 3 3 3 Custom 0 0 3 3 3 : : : : : : : : : change threshold alarm level change changed alarm change exceeded alarm change below alarm change above alarm change inBetween alarm apply threshold alarm changes cancel threshold alarm changes return to previous page
Changed Exceeded Below Above InBetween
1 : change behavior type 11 2 : change behavior interval 12 3 : change threshold boundary level 13 4 : change custom unit 14 5 : change custom time base 15 6 : change custom low 16 7 : change custom high 17 8 : change custom buffer 18 9 : apply threshold boundary changes 19 10 : cancel threshold boundary changes Select choice => : (1..19) [19]
Index ThresholdName Status CurVal LastEvent LasteventTime LastVal LastState ================================================================================ 1 envTemp001 enabled 21 C inBetween Thu Jun 12 19:15:47 2003 20 C Normal 2 envTemp002 enabled 21 C inBetween Thu Jun 12 19:15:47 2003 20 C Normal 3 envTemp003 enabled 33 C inBetween Thu Jun 12 19:15:47 2003 33 C Normal 4 envTemp004 enabled 33 C inBetween Thu Jun 12 19:15:47 2003 33 C Normal 1 : refresh 2 : disable a threshold 3 : enable a threshold 4 : advanced configuration 5 : return to previous page Select choice => : (1..5) [5] 1 : Temperature 2 : Fan 3 : Power Supply 4 : return to previous page Select an area => : (1..4) [4] 1 2 3 4 5 6 : : : : : : Environment class SFP class Port class Fabric class E-Port class F/FL Port (Optical) class
3-24
7 : Alpa Performance Monitor class 8 : EE Performance Monitor class 9 : Filter Performance Monitor class 10 : Security class 11 : Switch Availability Monitor class 12 : Quit Select a class => : (1..12) [12] 2 1 : Temperature 2 : RXP 3 : TXP 4 : Current 5 : Voltage 6 : return to previous page Select an area => : (1..6) [6]
1 : Environment class 2 : SFP class 3 : Port class 4 : Fabric class 5 : E-Port class 6 : F/FL Port (Optical) class 7 : Alpa Performance Monitor class 8 : EE Performance Monitor class 9 : Filter Performance Monitor class 10 : Security class 11 : Switch Availability Monitor class 12 : Quit Select a class => : (1..12) [12] 3 /Note: All classes with name "port" in them will have similar areas. 1 : Link loss 2 : Sync loss 3 : Signal loss 4 : Protocol error 5 : Invalid words 6 : Invalid CRCS 7 : RXPerformance 8 : TXPerformance 9 : State Changes 10 : return to previous page Select an area => : (1..10) [10] 1 : Environment class 2 : SFP class 3 : Port class 4 : Fabric class 5 : E-Port class 6 : F/FL Port (Optical) class 7 : Alpa Performance Monitor class 8 : EE Performance Monitor class 9 : Filter Performance Monitor class 10 : Security class 11 : Switch Availability Monitor class 12 : Quit Select a class => : (1..12) [12] 7 1 : Invalid CRCS 2 : return to previous page Select an area => : (1..2) [2] 1 2 3 4 5 6 : : : : : : Environment class SFP class Port class Fabric class E-Port class F/FL Port (Optical) class
3-25
7 : Alpa Performance Monitor class 8 : EE Performance Monitor class 9 : Filter Performance Monitor class 10 : Security class 11 : Switch Availability Monitor class 12 : Quit Select a class => : (1..12) [12] 8 1 : Invalid CRCS 2 : RXPerformance 3 : TXPerformance 4 : return to previous page Select an area => : (1..4) [4] 1 : Environment class 2 : SFP class 3 : Port class 4 : Fabric class 5 : E-Port class 6 : F/FL Port (Optical) class 7 : Alpa Performance Monitor class 8 : EE Performance Monitor class 9 : Filter Performance Monitor class 10 : Security class 11 : Switch Availability Monitor class 12 : Quit Select a class => : (1..12) [12] 9 1 : Customer Define 2 : return to previous page Select an area => : (1..2) [2] 1 : Environment class 2 : SFP class 3 : Port class 4 : Fabric class 5 : E-Port class 6 : F/FL Port (Optical) class 7 : Alpa Performance Monitor class 8 : EE Performance Monitor class 9 : Filter Performance Monitor class 10 : Security class 11 : Switch Availability Monitor class 12 : Quit Select a class => : (1..12) [12] 10 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 : : : : : : : : : : : : : : : : : : : Telnet Violations HTTP Violations API Violations RSNMP Violations WSNMP Violations SES Violations MS Violations Serial Violations Front Panel Violations SCC Violations DCC Violations Login Violations Invalid Timestamps Invalid Signatures Invalid Certificates SLAP Failures SLAP Bad Packets TS Out of Sync No-FCS
3-26
20 : Incompatible Security DB 21 : Illegal Command 22 : return to previous page Select an area => : (1..22) [22] 1 : Environment class 2 : SFP class 3 : Port class 4 : Fabric class 5 : E-Port class 6 : F/FL Port (Optical) class 7 : Alpa Performance Monitor class 8 : EE Performance Monitor class 9 : Filter Performance Monitor class 10 : Security class 11 : Switch Availability Monitor class 12 : Quit Select a class => : (1..12) [12] 11 1 : Total Down time 2 : Total Up time 3 : Duration of Occurrences 4 : Frequency of Occurrences 5 : return to previous page Select an area => : (1..5) [5] 1 : Environment class 2 : SFP class 3 : Port class 4 : Fabric class 5 : E-Port class 6 : F/FL Port (Optical) class 7 : Alpa Performance Monitor class 8 : EE Performance Monitor class 9 : Filter Performance Monitor class 10 : Security class 11 : Switch Availability Monitor class 12 : Quit Select a class => : (1..12) [12]
3-27
fwfrucfg
Available in Fabric OS versions: v4.x Note: This command requires a Fabric Watch License.
Troubleshooting Use: Use this command to display or modify FRU state alert configuration. Use this command to configure FRU states and actions. Based on these configuration settings Fabric Watch generates action when FRU state changes. To configure email alerts use fwmailcfg. Example 3-7: Fwfrucfg and sub category examples:
RSL_12K8_SW1:admin> fwfrucfg 1 : Slot 2 : Power Supply 3 : Fan 4 : WWN 5 : Configure All 6 : Set All to Default 7 : Quit Select an item => : (1..7) [7] 1 Alarm Id Label Status State Level =================================================== 5 Slot #5 enabled 1 0 6 Slot #6 enabled 1 0 7 Slot #7 enabled 1 0 8 Slot #8 enabled 1 0 9 Slot #9 enabled 1 0 10 Slot #10 enabled 1 0 1 : change fru alarm state 2 : change fru alarm level 3 : change fru status Select choice => : (1..6) [6] 4 : apply fru configuration 5 : cancel fru configuration changes 6 : return to previous page
1 : Slot 2 : Power Supply 3 : Fan 4 : WWN 5 : Configure All 6 : Set All to Default 7 : Quit Select an item => : (1..7) [7] 2 Alarm Id Label Status State Level =================================================== 1 Power Supply #1 enabled 1 0 2 Power Supply #2 enabled 1 0 3 Power Supply #3 enabled 1 0 4 Power Supply #4 enabled 1 0 1 : change fru alarm state 2 : change fru alarm level 3 : change fru status Select choice => : (1..6) [6] 1 2 : Slot : Power Supply 4 : apply fru configuration 5 : cancel fru configuration changes 6 : return to previous page
3-28
3 : Fan 4 : WWN 5 : Configure All 6 : Set All to Default 7 : Quit Select an item => : (1..7) [7] 3 Alarm Id Label Status State Level =================================================== 1 Fan #1 enabled 1 0 2 Fan #2 enabled 1 0 3 Fan #3 enabled 1 0 1 : change fru alarm state 2 : change fru alarm level 3 : change fru status Select choice => : (1..6) [6] 4 : apply fru configuration 5 : cancel fru configuration changes 6 : return to previous page
1 : Slot 2 : Power Supply 3 : Fan 4 : WWN 5 : Configure All 6 : Set All to Default 7 : Quit Select an item => : (1..7) [7] 4 Alarm Id Label Status State Level =================================================== 1 WWN #1 enabled 1 0 2 WWN #2 enabled 1 0 1 : change fru alarm state 2 : change fru alarm level 3 : change fru status Select choice => : (1..6) [6] 1 2 3 4 5 6 7 : : : : : : : Slot Power Supply Fan WWN Configure All Set All to Default Quit => : (1..7) [7] 5 4 : apply fru configuration 5 : cancel fru configuration changes 6 : return to previous page
Select an item
Absent-1, Inserted-2, Ready-4 Up-8, On-16, Off-32, Faulty-64 Enter fru alarm state => : (0..127) [1] Errlog-1, EmailAlert-16 Enter fru alarm action => : (0..17) [0]
Disable-1 Enable-2 Enter fru status => : (1..2) [2] 1 2 3 4 5 : : : : : Slot Power Supply Fan WWN Configure All
3-29
3
6 7
: Set All to Default : Quit => : (1..7) [7] 6
Select an item 1 2 3 4 5 6 7 : : : : : : :
Slot Power Supply Fan WWN Configure All Set All to Default Quit => : (1..7) [7]
Select an item
3-30
ifModeShow/Set
Available in Fabric OS versions: 3.x and 4.x Troubleshooting Use: Use this command to show/set the link operating mode for a network interface Use ifShow to list network interfaces available on the system. An operating mode is confirmed with a y or yes at the prompt. If the operating mode selected differs from the current mode, the change is saved and the command exits. The system must be rebooted for changes to take effect. Changing the link mode is not supported for all network interfaces or for all Ethernet network interfaces. At present, this command is only functional for fei interfaces. Exercise care when using this command. Forcing the link to an operating mode not supported by the network equipment to which it is attached may result in an inability to communicate with the system through its Ethernet interface. Example 3-8: To force the link for the fei0 Ethernet interface from auto-negotiate operation to 10 Mbps / Half duplex operation:
SW3800_12:admin> ifModeSet "fei0" Auto-negotiate (yes, y, no, n): [no] 100 Mbps / Full Duplex (yes, y, no, n): [no] 100 Mbps / Half Duplex (yes, y, no, n): [no] 10 Mbps / Full Duplex (yes, y, no, n): [no] 10 Mbps / Half Duplex (yes, y, no, n): [no] yes Committing configuration...done.
Example 3-9: To display the link operating mode for the fei0 ethernet interface:
SW3800_12:admin> ifmodeshow fei (unit number 0): Link mode: Auto-negotiate lo (unit number 0): Link mode: Not applicable SW3800_12:admin> dazzler16_49:admin> ifmodeshow eth0 Link mode: negotiated 100baseTx-FD, link ok
Example 3-1: V4.2 output from a SW3850 switch

dazzler16_49:admin> ifmodeset eth0 Exercise care when using this command. Forcing the link to an operating mode not supported by the network equipment to which it is attached may result in an inability to communicate with the system through its ethernet interface. It is recommended that you only use this command from the serial console port. Are you sure you really want to do this? (yes, y, no, n): [no] y Proceed with caution. Auto-negotiate (yes, y, no, n): [no] y Advertise 100 Mbps / Full Duplex (yes, y, no, n): [yes] Advertise 100 Mbps / Half Duplex (yes, y, no, n): [yes] Advertise 10 Mbps / Full Duplex (yes, y, no, n): [yes] Advertise 10 Mbps / Half Duplex (yes, y, no, n): [yes] Committing configuration...done.
3-31
ifshow
Available in Fabric OS versions: This is a CLI non-supportshow command in all VxWorks switch FOS versions Troubleshooting Use: Use this command to display network interface information Use this command to display network interface information. If the operand ifname is provided, only that interface is displayed. If ifname is omitted, all interfaces are displayed. Each switch has three interfaces:
ei or fei is the 10BaseT or 100BaseT ethernet interface lo is the loopback interface fc is the Fibre Channel interface
The fc interface is displayed for switches running IP over Fibre Channel that have been assigned an FC-IP address. For each interface selected, the following information is displayed:
Flags (for example, loopback, broadcast, arp, running, debug) Internet address Broadcast address Netmask and subnetmask Ethernet address Route metric Maximum transfer unit Number of packets received and sent Number of input errors, output errors, and collisions
Example 3-2: To display ethernet interface information for a switch with a 10BaseT connection:
switch:admin> ifShow "ei" ei (unit number 0): Flags: (0x63) UP BROADCAST ARP RUNNING Internet address: 192.168.1.65 Broadcast address: 192.168.1.255 Netmask 0xffffff00 Subnetmask 0xffffff00 Ethernet address is 00:60:69:00:00:8a Metric is 0 Maximum Transfer Unit size is 1500 42962 packets received; 127 packets sent 0 input errors; 0 output errors 7 collisions
3-32
ipAddrSet
Available in Fabric OS versions: A non-supportshow command available in all FOS versions Troubleshooting Use: Use this command to show/set ethernet and FC_IP addresses Use this command to set the ethernet and FC IP addresses. You are prompted for: Ethernet IP Address IP address of the ethernet port. Ethernet Subnetmask IP subnet mask of the ethernet port. Fibre Channel IP Address IP address of the fibre channel ports. Fibre Channel Subnetmask IP subnet mask of the fibre channel ports. Gateway Address IP address of the gateway. After each prompt the current value is shown. You may:
Press Enter to retain the current value Enter an IP address in conventional dot notation Enter none Press Control-C to cancel changes Press Control-D to accept changes and end input
The final prompt allows you to set the new IP addresses immediately; enter y to set new addresses immediately, enter n to delay the changes until the next switch reboot. Entering y closes the telnet session. The default IP address for a Brocade switch is 10.77.77.77. A change to these values issues a domain address format RSCN, refer to FC-FLA for a description of RSCNs. Examples Example 3-10: To display the switch IP addresses:
SW3800_12:admin>ipaddrshow Ethernet IP Address: 10.64.68.12 Ethernet Subnetmask: 255.255.240.0 Fibre Channel IP Address: none Fibre Channel Subnetmask: none Gateway Address: 10.64.64.1
Example 3-11: To enable IP over fibre channel:

SW3800:admin> ipAddrSet Ethernet IP Address: 10.64.68.12 Ethernet Subnetmask: 255.255.240.0 Fibre Channel IP Address [none]: 192.168.65.65 Fibre Channel Subnetmask [none]: Gateway Address: 10.64.64.1 Committing configuration...done. Set IP addresses now? [y = set now, n = next reboot]: y
3-33
killTelnet
Available in Fabric OS versions: This is a non-supportshow command in all v4.1 plus FOS versions Troubleshooting Use: Use this command to display and terminate telnet sessions. Use this command to view or terminate an open telnet session. The killtelnet command is an interactive menu driven command. Upon invocation, it lists all the current telnet and serial port login sessions. It lists information such as the session number, login name, the idle time, the IP address of the connection, and the time stamp of when the login session was opened. A prompt is then displayed where you can specify the session number of the connection you wish to terminate Example 3-12: Kill an active telnet session:
SW3900_128:root> killtelnet Collecting login information....Done List of telnet sessions (3 found) Session No USER TTY IDLE FROM LOGIN@ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 0 root pts/0 1.00s 192.168.133.22 9:57am 1 admin pts/1 57:21 192.168.192.89 11:17am 2 user pts/2 4:15 192.168.133.22 12:10pm ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Enter Session Number to terminate (q to quit) 1 Collecting process information... Done. You have opted to terminate the telnet session:logged in as "admin ", from "192.168.192.89 " since "11:17am" and has been inactive for "57:21 ", the current command executed being: "-rbash ". The device entry is: "pts/1 ". This action will effectively kill these process(es):USER PID ACCESS COMMAND /dev/pts/1 root 1387 f.... rbash Please Ensure (Y/[N]): y killing session.... Done! Collecting login information....Done List of telnet sessions (2 found) Session No USER TTY IDLE FROM LOGIN@ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 0 root pts/0 4.00s 192.168.133.22 9:57am 1 user pts/2 4:53 192.168.133.22 12:10pm ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Enter Session Number to terminate (q to quit)q
Note:
The list of open sessions displayed with killtelnet includes the users current session. Make sure you do not kill your own telnet session.
3-34
netstat
Troubleshooting Use: Use this non-supportshow command to print network connections, routing tables, interface statistics, masquerade connections, and multi-cast memberships. Available in Fabric OS versions: 4.x Additional Example/Case Studies: Note: See inetstatshow for similar v3.x information.
Description netstat prints information about the Linux networking sub-system. Example 3-13: Display all active TCP connections:
SW3900_128:root> netstat -t Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address tcp 0 0 SW3900_128:www tcp 0 126 SW3900_128:telnet
Foreign Address SW3900_128:1112 192.168.133.22:2569
State TIME_WAIT ESTABLISHED
Example 3-3: Output from a v4.2 3850 switch.

dazzler16_49:root> netstat Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address tcp 0 0 dazzler16_49:www tcp tcp tcp tcp 0 0 0 0 0 dazzler16_49:www 0 dazzler16_49:telnet 126 dazzler16_49:telnet 0 dazzler16_49:telnet
Foreign Address dazzler16_49:1308 dazzler16_49:1307 192.168.130.55:1135 192.168.80.15:1669 192.168.80.15:1276
State TIME_WAIT TIME_WAIT ESTABLISHED ESTABLISHED ESTABLISHED
Active UNIX domain sockets (w/o servers) Proto RefCnt Flags Type State unix 7 [ ] DGRAM unix 2 [ ] DGRAM unix 2 [ ] DGRAM unix 2 [ ] DGRAM unix 2 [ ] DGRAM unix 2 [ ] DGRAM
I-Node Path 348 /dev/log 730736 700049 697101 407 358
3-35
portLogShow
Available in Fabric OS versions: All versions of Fabric OS have CLI portlogshow output. Version Differences: VxWorks switches have a t for task names. Version 3.x output has a 5th argument column that represents an information unit only column. v4.2 Example Output: Additional Example/Case Studies: Troubleshooting Use: Use this command to display the part activity log. This command displays the port log, showing 22 entries at a time. It is identical to portLogDump, except that portLogDump does not prompts the user to type return between each page of output. If the port log is disabled, the following message is printed as the first line:
WARNING: port log is disabled
The following fields are shown: time task event start disable enable ioctl Tx Rx scn pstate reject busy ctin fc The date and time of the event. The clock resolution is 16 milliseconds. The name of the task that logged the event, or interrupt if the event was logged in interrupt context, or unknown if the task no longer exists. Possible events are: - a switch start or re-start event - a port is disabled - a port is enabled - a port I/O control is executed - a frame is transmitted (class is indicated) - a frame is received (class is indicated) - a state change notification is posted (see state codes below) - a port changes physical state (see pstate codes below) - a received frame is rejected - a received frame is busied - a CT based request is received: the CT-subtype: - means the Simple Name Server,
f8 - means the Alias Server. ctout errlog loopscn create port cmd ioctl Tx & Rx errlog loopscn OLP: LIP: LIM: - a CT based response is transmitted; same as ctin above. - a message is added to the error log - a loop state change notification is posted - a task is created The port number of the effected port. A command value. The meaning of this field depends on the event type: - I/O control command code - frame payload size - error level (see errShow) - current loop state during loop initialization, possible values are: offline (disconnected or nonparticipating) FL_Port entered INITIALIZING or OPEN_INIT state LISM completed, FL_Port became the loop master
3-36
Non-SupportShow Commands BMP: OLD: TMO: loop init completed, FL_Port in MONITORING state port transited to the OLD_PORT state
loop init times out; encoded value of the state when loop init timed out. This value is usually equal to the first word of a loop init frame payload. Other possible values include: 2: 40: LIP (req. INITIALIZING) timeout CLS timeout 94F0F0: ARB(F0) timeout
argsstart
The command arguments. The meaning of this field depends on the event type: start type: 0 = enable ports, 100 = disable ports
disable state (see state codes below) enable ioctl mode: 0 = normal, non-zero = loopback I/O control arguments
Tx & Rx header words 0,1,4 (R_CTL,D_ID,S_ID,OX_ID,RX_ID), the first payload word if the payload length is none zone, and the IU address that contains the frame. reject busy ctin FC-PH reject reason FC-PH busy reason Argument 0 is divided into two 16-bit fields: [A] a bit map indicating whether subsequent args are valid (0001 means argument 1 is valid, 0003 means arguments 1 and 2 are valid); [B] the ct-based service command code. Argument 1 is the first word of the CT payload, if applicable (as specified in [A]). Argument 2 is the second word of the CT payload, if applicable (as specified in [A]). ctout - Argument 0 is also divided into two 16-bit fields:
[A] a bit map indicating whether subsequent args are valid (0001 means argument 1 is valid, 0003 means arguments 1 and 2 are valid) [B] the CT command code indicating whether an accept (8002) or a reject (8001). If [B] is an accept, argument 1 and 2 represents the first and second words of the CT payload, if applicable (as specified in [A]). If [B] is a reject, argument 1 contains the CT reject reason and explanation code. errlog create - error type (see errShow) - name of the task being created
TMO: encoded value of the state when loop init timed out. This value is usually equal to the first word of a loop init frame payload. Other possible values include: 2: LIP (req. INITIALIZING) timeout 94F0F0: ARB(F0) timeout 40: CLS timeout
3-37
Codes used in various fields are: Table 3-1
state 1- Online 2 - Offline 3- Testing 4- Faulty 5- E_Port 6- F_Port 7 - Segmented pstate LR1 LR2 LR3 LF1 LF2 OL1 OL2 OL3 ioctl 90 - get virtual channel credits 91- set virtual channel credits a1 - port is an E_Port a2 - port is an F_Port a3 - port is segmented a4 - domain name is known a5- port enable a6 - port disable a7 - link reset a8 - add unicast route a9 - delete unicast route aa - add multicast route ab - delete multicast route ac - unicast path selection done ad - multicast path selection done ACActive State 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
3-38
Non-SupportShow Commands Table 3-1
LIP reason 8001 - retry loop init 8002 - start loop after gaining sync 8003 - restart loop after port reset 8004 - LIP when a loop hangs 8005 - restart loop if LIP received when sending out ARB(F0) 8006 LIP when an OPN returns 8007 - restart loop when LIPs received in OLD_PORT AC state 8008 - restart loop if loop not empty but E_Port loopback 8009 - LIP as requested by the LINIT ELS received 800a - LIP as requested by the LPC ELS received 800b - restart loop for QuickLoop looplet setup 800c - restart loop for QuickLoop looplet re-initialization EXAMPLE The following example shows a section of the port log with an E_Port coming online. The ELP and EFP exchanges are shown; a name service request was processed. Example 3-4:
sw5:admin> portLogShow 24 Feb 6 task event port cmd args -----------------------------------------------------08:35:27.899 tShell pstate 14 OL1 08:35:27.899 tReceive pstate 14 LR2 08:35:27.916 tReceive pstate 14 AC 08:35:28.416 interrupt scn 14 1 08:35:28.433 tFabric ioctl 14 90 101d9910,0 08:35:28.433 tFabric Tx 14 164 02fffffd,00fffffd,0005ffff,10000000 08:35:28.433 tReceive Rx 14 0 c0fffffd,00fffffd,00050006 08:35:28.433 tReceive Rx 14 164 03fffffd,00fffffd,00050006,02000000 08:35:28.433 tTransmit Tx 14 0 c0fffffd,00fffffd,00050006 08:35:28.433 tFabric ioctl 14 91 103646d8,0 08:35:28.466 tFabric ioctl 14 a7 3c,1 08:35:28.466 tFabric pstate 14 LR1 08:35:28.466 tReceive pstate 14 LR3 08:35:28.466 tReceive pstate 14 AC 08:35:28.483 tFabric Tx 14 96 02fffffd,00fffffd,0006ffff,11100060 08:35:28.483 tReceive Rx 14 0 c0fffffd,00fffffd,00060007 08:35:28.483 tReceive Rx 14 96 03fffffd,00fffffd,00060007,02100060 08:35:28.483 tTransmit Tx 14 0 c0fffffd,00fffffd,00060007 08:35:28.483 tFabric ioctl 14 a1 0,0 08:35:28.483 tFabric scn 14 5 08:35:28.516 tReceive Rx3 12 20 02fffffc,00021c00,001affff,01000000 08:35:28.516 tNSd ctin 12 fc 00010112,00011300 08:35:28.516 tNSd ctout 12 fc 00038002,10000000,c920d2c7 08:35:28.516 tNSd Tx3 12 8 03021c00,00fffffc,001a0007,10000000
< Output truncated >
3-39
powerofflistset
Available in Fabric OS versions: This a v4.x non-supportshow command Troubleshooting Use: Use this command to set slot power-off list order Use this command to set the physical power off slot order. The system available power is compared to the system demand power to determine if there is enough power to operate. If there is less power available than the demand, then the power off list is processed until there is enough power for the system to operate. The format of the display varies depending on the switch model and the number of slots present. When this command is executed, the first item displayed is the current power off list order. Then you are prompted to make any changes, and finally the new power off list order is displayed. The command then prompts to verify and commit the changes. Example 3-14: To modify the power off list order:
switch:admin> powerofflistset Slot Current POL ------------------10 1st 9 2nd 8 3rd 7 4th 4 5th 3 6th 2 7th 1 8th 1st slot to be power off: (1..10) [10] 7 2nd slot to be power off: (1..10) [9] 8 3rd slot to be power off: (1..10) [9] 4th slot to be power off: (1..10) [10] 5th slot to be power off: (1..4) [4] 1 6th slot to be power off: (2..4) [3] 2 7th slot to be power off: (3..4) [3] 8th slot to be power off: (4..4) [4] Old POL New POL Power Off Order ------------------------------------10 7 1st 9 8 2nd 8 9 3rd 7 10 4th 4 1 5th 3 2 6th 2 3 7th 1 4 8th Proceed to change the POL order? (yes, y, no, n): [no] y switch:admin>
3-40
savecore
Available in Fabric OS versions: v4.0.2 + Troubleshooting Use: Use this command to save or remove core files created by daemons Use this command to FTP core files, to remove core files, or to list core files. With no arguments, savecore will enter into interactive mode. Options This command has the following options: -h ip-address -u user_name -p password -a Specify a host-name if FTP requires it. Specify a user-name for login in the above host-name default will be anonymous. Specify a password for the above user-name. Specify to use anonymous FTP to download the core files. This option cannot be used with -u option.
-d remote_directory Specify the name of the remote directory into which the core files are copied into. The directory will be created if it does not already exists. It is assumed that the user has sufficient privilege to create files at this location. -f core-file-directory-list Specify a list of the core file directories to transfer to a remote site. This list can be comma (,) separated directory list or just a single directory name. Only the standard core files directories can be specified (/core_files and /mnt/core_files); all other files or directories are ignored. -R Specify this option to remove all core files. -r <core-files-directory-list> Specify this option to remove core files under the directory list given. Removes all the core files under the listed directories. The directory list is a comma separated list of core files directory and other files, if any, will be ignored. No confirmation will be made before removal. -l Specify this option to list all core files. Example 3-15: To list all core files in a CP:
switch:admin> savecore -l /core_files/panic/core.873 /core_files/zoned/core.1234 /core_files/zoned/core.5678 /mnt/core_files/nsd/core.873 /mnt/core_files/panic/core.873 switch:admin>
Example 3-16: To remove selected core files from a CP:

switch:admin> savecore -r /core_files/panic/,/core_files/zoned/,/mnt/core_files/nsd/ Removing: /core_files/panic/ Removing: /core_files/zoned/ Removing: /mnt/core_files/nsd/ switch:admin>
Example 3-17: To remove selected core files from the CP (using multiple -r operands):
switch:admin> savecore -r /core_files/panic/ -r /core_files/zoned/,/mnt/core_files /nsd/ Removing: /core_files/panic/ Removing: /core_files/zoned/ Removing: /mnt/core_files/nsd/ switch:admin>
Example 3-18: To remove all core files:

switch:admin> removing core removing core removing core savecore -R files under: /core_files/panic files under: /core_files/zoned files under: /mnt/core_files/nsd
3-41
removing core files under: /mnt/core_files/panic switch:admin>
Example 3-19: To FTP all core files:

switch:admin> savecore -h 192.168.204.188 -u jsmith -d core_files_here -p fexosophy -F /core_files/panic/core.873: 1.12 kB 381.87 B/s /core_files/zoned/core.1234: 1.12 kB 382.14 B/s /core_files/zoned/core.5678: 1.12 kB 382.50 B/s /mnt/core_files/nsd/core.873: 1.12 kB 381.93 B/s /mnt/core_files/panic/core.873: 1.12 kB 381.90 B/s Files transferred successfully! switch:admin>
Example 3-20: To FTP selected core file directories:

switch:admin> savecore -h 192.168.204.188 -u jsmith -d core_files_here -p password -f /core_files/zoned/,/mnt/core_files/nsd/ /core_files/zoned//core.1234: 1.12 kB 382.60 B/s /core_files/zoned//core.5678: 1.12 kB 381.95 B/s /mnt/core_files/nsd//core.873: 1.12 kB 382.53 B/s Files transferred successfully! switch:admin>
Example 3-21: To remove all core files using the savecore management utility:
switch:admin> savecore following 1 directories contains core files: [ ]0: /mnt/core_files/panic Welcome to core files management utility. Menu 1(or R): Remove all core files 2(or F): FTP all core files 3(or r): Remove marked files 4(or f): FTP marked files 5(or m): Mark Files for action 6(or u): Un Mark Files for action 9(or e): Exit Your choice: 1 /mnt/core_files/panic You have opted to remove ALL core files:Please confirm (Y/[N]): y Removing files.... removing core files under: /mnt/core_files/panic Done! switch:admin> switch:admin> savecore No core files found! switch:admin>
Example 3-22: To FTP core files using the savecore management utility:
switch:admin> savecore following 1 directories contains core files: [ ]0: /core_files/zoned Welcome to core files management utility. Menu 1(or R): Remove all core files 2(or F): FTP all core files 3(or r): Remove marked files 4(or f): FTP marked files 5(or m): Mark Files for action 6(or u): Un Mark Files for action 9(or e): Exit Your choice: F /core_files/zoned You have opted to FTP these core files:Please confirm (Y/[N]): y Destination IP Address? 192.168.10.10
3-42
User Name [anonymous]? jsmith Remote Directory [.]? brcd Password: ********** /core_files/zoned/core.8323: 1.12 kB 382.40 B/s Files transferred successfully! switch:admin>
Example 3-23: To remove core files from a selected directory:

switch:admin> savecore following 2 directories contains core files: [ ]0: /core_files/nsd [ ]1: /core_files/zoned Welcome to core files management utility. Menu 1(or R): Remove all core files 2(or F): FTP all core files 3(or r): Remove marked files 4(or f): FTP marked files 5(or m): Mark Files for action 6(or u): Un Mark Files for action 9(or e): Exit Your choice: m Enter File Number to mark: 1 Enter CR To Continue.... following 2 directories contains core files: [ ]0: /core_files/nsd [*]1: /core_files/zoned Welcome to core files management utility. Menu 1(or R): Remove all core files 2(or F): FTP all core files 3(or r): Remove marked files 4(or f): FTP marked files 5(or m): Mark Files for action 6(or u): Un Mark Files for action 9(or e): Exit Your choice: r /core_files/zoned You have opted to remove core files under these directories:Please confirm (Y/[N]): y Removing files.... removing core files under: /core_files/zoned Done! switch:admin>
3-43
snmpmibcapset
Note: Platform versions will have different MIBS to select
Available in Fabric OS versions: 3.0.2 and 4.0.2 Troubleshooting Use: Use this command to view and modify options for configuring SNMP MIB trap capability This command enables a user to turn on or off certain MIBS and TRAPS. This command also enables a user to turn on or off group information and SSN in SW trap messages. It first displays current settings and then prompts the user to change the values for each parameter. FA-MIB HA-MIB SW-TRAP FA-TRAP Specifying yes means the user can access FA-MIB variables with an SNMP manager. The default value is yes. Specifying yes means the user can access HA-MIB variables with an SNMP manager. The default value is yes. Specifying yes means the SNMP management application can receive SW-TRAPS from the switch. The default value is yes. Specifying yes means the SNMP management application can receive FA-TRAPS from the switch. The default value is yes.
SW-EXTTRAP Specifying yes means the SNMP management application can receive SWEXTTRAPS from the switch. The default value is yes. HA-TRAP Specifying yes means the SNMP management application can receive HA-TRAPS from the switch. The default value is yes.
Example 3-24: To view or modify the options for configuring SNMP MIB traps:
switch:admin> snmpmibcapset The SNMP Mib/Trap Capability has been set to support FE-MIB SW-MIB FA-MIB FICON-MIB HA-MIB SW-TRAP FA-TRAP FICON-TRAP HA-TRAP FA-MIB (yes, y, no, n): [yes] FICON-MIB (yes, y, no, n): [yes] HA-MIB (yes, y, no, n): [yes] SW-TRAP (yes, y, no, n): [yes] FA-TRAP (yes, y, no, n): [yes] SW-EXTTRAP (yes, y, no, n): [no] y FICON-TRAP (yes, y, no, n): [yes] HA-TRAP (yes, y, no, n): [yes] switch:admin>
Note:
Use this command to verify/ enable MiB or Traps
3-44
tcpstatshow
Available in Fabric OS versions: v3.x non-supportshow Network Command Group Troubleshooting Use: Use this command along with other network command group commands to display the transmission Control Protocol statistics for the Ethernet connection(s) to switch. Example 3-5: To display the Transmission Control Protocol statistics
SW3800_12:admin> tcpstatshow TCP: 523 packets sent 514 data packets (105265 bytes) 0 data packet (0 byte) retransmitted 9 ack-only packets (8 delayed) 0 URG only packet 0 window probe packet 0 window update packet 0 control packet 1060 packets received 454 acks (for 105266 bytes) 7 duplicate acks 0 ack for unsent data 305 packets (426 bytes) received in-sequence 0 completely duplicate packet (0 byte) 0 packet with some dup. data (0 byte duped) 0 out-of-order packet (0 byte) 0 packet (0 byte) of data after window 0 window probe 0 window update packet 0 packet received after close 0 discarded for bad checksum 0 discarded for bad header offset field 0 discarded because packet too short 0 connection request 1 connection accept 1 connection established (including accepts) 4 connections closed (including 0 drop) 1 embryonic connection dropped 419 segments updated rtt (of 419 attempts) 0 retransmit timeout 0 connection dropped by rexmit timeout 0 persist timeout 7 keepalive timeouts 7 keepalive probes sent 0 connection dropped by keepalive
Network Command Group: Table 3-1 ipAddrShow ifShow ipstatShow udpstatShow tcpstatShow inetstatshow mbufShow arpShow routeShow routestatShow hostShow feiDumpPrint i557Dump feiIterateRFDRings
3-45
3-46

Support Show Command Ref SSCRG

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Support Show Command Ref SSCRG

Загружено:

Авторское право:

Доступные форматы

The Official SupportShow Command Reference Guide

Publication Number: 53-0000448-01 Publication Date: January 10, 2004

Brocade Communications Systems, Incorporated

Fabric OS SupportShow Information

Brocade Fabric Watch Guidelines

Brocade Fabric Watch Guidelines

Brocade Fabric Watch Guidelines

Brocade Fabric Watch Guidelines

Brocade Fabric Watch Guidelines

Brocade Fabric Watch Guidelines

SAN Migration Guide

Notes and Guidelines

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

SAN Migration Guide

The output of this command can be very long.

The Official SupportShow Command Reference Guide

1.1.2. Operands v4.0

1.2. Fabric OS v3.0.x and 4.0.x SupportShow

Fabric OS Version 3.0.2c

The Official SupportShow Command Reference Guide

Fabric OS Version 3.0.2c

The Official SupportShow Command Reference Guide

1.3. Fabric OS v3.1.0 and 4.1.0 SupportShow

The Official SupportShow Command Reference Guide

Table 1-3 Fabric OS v 3.1 v3.1.0Switch:admin> supportshow

Fabric OS v 4.1 V4.1.0Switch:admin> supportshow

Exception Command Group

Exception Command Group

Port Command Group (for each port)

Port Command Group (Repeats for all slots or blades)

The Official SupportShow Command Reference Guide

Table 1-3 Fabric OS v 3.1 v3.1.0Switch:admin> supportshow Fabric Command Group

Fabric OS v 4.1 V4.1.0Switch:admin> supportshow Fabric Command Group

Services Command Group

Services Command Group

Security Command Group

Security Command Group

Note: Subsequent outputs only displayed if secmode is enabled:

Network Command Group

Network Command Group

The Official SupportShow Command Reference Guide

Table 1-3 Fabric OS v 3.1 v3.1.0Switch:admin> supportshow System Command Group

Fabric OS v 4.1 V4.1.0Switch:admin> supportshow System Command Group

The Official SupportShow Command Reference Guide

Extend Command Group

Extended Command Group

Filter Command Group

Filter Command Group

Performance Command Group

Performance Command Group

The Official SupportShow Command Reference Guide

1.4. Fabric OS v3.1.2 and 4.2.x SupportShow

The Official SupportShow Command Reference Guide

The Official SupportShow Command Reference Guide

The Official SupportShow Command Reference Guide

The Official SupportShow Command Reference Guide

Fabric OS SupportShow Information

The Official SupportShow Command Reference Guide

Fabric OS SupportShow Information

The Official SupportShow Command Reference Guide

Fabric OS SupportShow Information

yet yet yet yet yet yet

The Official SupportShow Command Reference Guide