Skip to main content
Outside service Partner
Hitachi Vantara Knowledge

Brocade Data Collection

Brocade Data Collection

Types of Data Collections:

  • Switch/Director data collection via CLI
    • Supportsave
    • Supportshow
  • BNA data collections
    • BNA switch supportsave
    • BNA server supportsave
      • BNA Client supportsave capture via CLI
      • BNA supportsave from Windows OS CLI
      • BNA supportsave from Linux OS CLI

 

Upload facility

Hitachi Vantara requires all data collections to be uploaded to a central upload site. This is to ensure that all data is collected in a central repository only accessible to authorized Hitachi personnel.

Please upload all data to https://tuf.hitachivantara.com

Brocade Switch Logs

  1. Log into the switch via Telnet/SSH/ or BNA
  2. Collect a supportsave (10-20 minutes)

After logs are collected, clear stats to create a baseline for port statistics in case additional data is needed. (details below)

  1. ONLY after supportsave process is complete would the clearing of the stats occur.
    1. Submit the 'statsclear' command
    2. Submit the 'slotstatsclear' command
  2. If FCIP is involved, submit the 'portshow fciptunnel -c --tcp --reset' command

Details on supportsaves are defined below.

Example

Fabosv4.4switch: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. This operation can take several minutes.
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... 
etc......

To upload the files you can specify the FTP parameters inline (as modeled above) or through the supportftp command (see Fabric OS Command Reference Guide) .

  1. Host IP: XXX.XXX.X.X (example 192.168.1.1)
  2. User Name: admin
  3. Password:
  4. Remote Directory: tmp (example: tmp)
  5. Saving support information.

5. Once collected please compress any individual *.gz files into a single .zip, .tgz, or .tar file for each switch data was collected from.  Make sure the file name of each compressed switch supportsave files follows the following naming convention as well to speed up analysis of your data:  *supportsave*, *support-save*, *DCX*, or *DCB*Do NOT use archive formats other than listed above.

6. Upload the compressed switch supportsave to TUF.

SupportShow Data Collection

***Please note that SupportShow Data Collection only provides limited information for our Global Support Center. It is highly recommended that a Supportsave be uploaded to your case immediately to help expedite your requests***

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 for how to turn on capturing output to a file.

Telnet or SSH

  1. Telnet or SSH into Brocade switch
  2. Enter username and password
  3. Start logging to file on the Telnet session.
    NOTE: For Windows standard telnet, this is under the terminal pulldown menu.
  4. Enter command: supportShow
  5. Upload the telnet log to TUF.

Brocade Network Advisor (BNA)

How To Gather A Switch Technical Supportsave Using BNA

You can capture technical support and event information from within BNA, using the 'Technical SupportSave' option, which uses BNA's built-in FTP, SCP, or SFTP server. If the switch is running Fabric Operating System (FOS) 5.3.X or later, BNA uses the SCP server to save data (if configured). To make sure the built-in FTP, SCP, or SFTP server is configured correctly, refer to "Configuring an external FTP, SCP, or SFTP server" in the Brocade Network Advisor SAN Manual.

  1. Select 'Technical Support' From the 'Monitor' menu within the Network Advisor application
  2. Select the second option 'Product/Host SupportSave'  (Do not select 'Supportsave'.  'Supportsave' is for BNA specific logs only)
    1. Brocade switches are referred to as 'SAN Products'
    2. Brocade HBA's and CNA's are referred to as 'Host Product'
      1. The 'Host' SupportSave option is only for Brocade HBA's and CNA's

      NOTE: The Network Advisor Server/Client SupportSave (for the BNA server application) can be collected by selecting the 'SupportSave' option. See How to Gather a Network Advisor Server/Client Application SupportSave
     
  3. Click the 'SAN Products tab' and select the switch(es) you want to collect data for in the 'Available SAN Products' pane, and then click the right-facing arrow to move selections to the 'Selected Products and Hosts' pane on the right
  4. Click 'OK' to begin generating the SupportSave data from the switch(es). In this example, a Brocade 7800 is selected
  5. The 'Technical SupportSave Status' window will be displayed, indicating progress as the SupportSave script begins to collect data from the switch(es)
    1. Upon successful completion, click 'OK' to close the window
    2. Technical SupportSave data for 'SAN Products' is compressed and saved to the following directory as:
      1. Network Advisor 1x.x.x\data\ftproot\technicalsupport\Supportinfo-Day-mm-dd-yyyy-hh-mm-ss.zip
  6. Upload the compressed data to the Hitachi Global Support Center’s Technical Upload Facility found here:
    1. TUF
    2. Please contact the Global Support Center by phone after your upload if your data analysis is urgent!

BNA supportsave CLI Captures:

Client support save using a command line interface

Use the following procedures to capture client support save files through the command line interface (CLI).

Capturing client support save using the CLI (Windows)

To capture client support save files through the CLI, complete the following steps.

  1. Go to the following location:
    • (Local client) User_Home/Management_Application_Name/localhost
    • (Remote client) User_Home/Management_Application_Name/Server IP
  2. Run the clientsupportsave.bat file.
  3. Define a capture location by typing clientsupportsave in the CLI. If the path has spaces, enclose it in double quotes.
    By default, the capture location is one of the following:
    • (Local client) User_Home/Management_Application_Name/localhost
    • (Remote client) User_Home/Management_Application_Name/Server IP
  4. Use an archive tool to create a ZIP file of the support save.
Capture client support save using the CLI (Linux)

To capture client support save files through the CLI, complete the following steps.

  1. Go to /root /Management_Application_Name_Folder/Server IP.
  2. Run the clientsupportsave.sh file.
  3. Define a capture location by typing sh clientsupportsave in the CLI. If the path has spaces, enclose it in double quotes.
    By default, the capture location is /root /Management_Application_Name_Folder/Server IP/support.
  4. Use an archive tool to create a ZIP file of the support save.