There are 2 types of Data Collection associated with Brocade switches, “supportshow” and “supportsave”.
If the problem is related to basic “port issues”, a “supportshow” is sufficient. However, a more complex problem that involves Zoning, Performance, Reboots, CP Failovers, Fabric wide problems etc, requires a “SupportSave” type of collection. If the problem is multiswitch related (ISL connections, long distance configurations etc.) we need the supportsave from all relevant switches in the fabric.
The amount and type of information displayed in a supportshow output is depending on the type of switch as well as the collection options enabled in the switch configuration. This can be configured with the “supportshowcfgenable [option]” and “supportshowcfgdisable [option]”.
The output from the “supportshowcfgshow” command shows which subscripts will be enabled. The default groups are always enabled. Only on special occasions you will be asked to enable additional groups if necessary.
Performance and Intermittent Error Related Issues
If there is no sign of any obvious physical issue there might be link related problems which can identify performance problems and/or protocol related errors. Brocade counters are cumulative and keep doing so until a certain counter wraps, a switch reboots or the statistics are manually cleared.
Storage vendors for example require in these circumstances that a new baseline is created, a certain run-time has been achieved and separate commands are submitted against the suspected switch or switches.
To create a new baseline with cleared counters do the following:
- Log in to the switch via Telnet or SSH
- Submit the “statsclear” command
- Submit the “slotstatsclear” command
After the agreed (mostly around one hour) run-time capture a new supportsave and upload this to the vendor’s service request.
SupportSave Data Collection (CLI Method)
When the problem is more sophisticated a supportsave from the switch is required. The supportsave command is available as of Fabric OS version 4.4 however, Fabric OS versions (> 6.2.x) provide a significant better collection of logs which represent the status overview of the switch and fabric. If you have a director class switch with two CP’s and/or core plus function blades it will also collect information from all the blades.
The supportsave will upload between 25 and 80 files depending on platform, Fabric OS level and enabled features to an FTP or SCP server. These will not be tarred or zipped into one file so it is important you create such an archive with a meaningful name. (ie. switchname-domainid-fabricid.zip)
switch:admin> supportsave -u anonymous -p password -h xxx.xxx.xxx.xxx -d /directory -l ftp
This command collects RASLOG, TRACE, supportShow, core file, FFDC data and then transfer them to a FTP/SCP server or a USB device. You could also simply type the “supportsave” command without any parameters and you will be asked for the extra information before the command is actually executed. The operation will usually take several minutes to complete.
NOTE: supportSave will transfer existing trace dump file first, then automatically generate and transfer latest one. There will be two trace dump files transferred after this command.
OK to proceed? (yes, y, no, n): [no] y
Saving support information for switch:BR4100_IP127, module:RAS…
Saving support information for switch:BR4100_IP127, module:CTRACE_OLD…
Saving support information for switch:BR4100_IP127, module:CTRACE_NEW…
To upload the files you can specify the FTP parameters inline (as modeled above) or through the supportftp command (see Fabric OS V5.1 command Reference guide) .
- Host IP: XXX.XXX.X.X (example 192.168.1.1)
- User Name: admin
- Remote Directory: tmp (example: tmp)
- Saving support information
SupportShow Data Collection
This is a non disruptive procedure and can be performed by the CE or the customer.
You can use your favorite terminal emulation utility. Refer to the respective documentation how to turn on capturing output to a file.
Telnet or SSH
- Telnet or SSH into Brocade switch
- Enter username and password
- Start logging to file on the Telnet session.
NOTE: For Windows standard telnet, this is under the terminal pulldown menu.
- Enter command: supportShow
- Upload the telnet log to TUF.