Cisco Data Collection

Hitachi Global Support (GSC) recommends gathering your first set of log(s) and then clearing the switch statistics after the first set of logs have been collected. This allows GSC to see the current status of the equipment then set a reference baseline, in case a second set of logs need to be used to verify counters. The reference baseline establishment is only done after the first log collection for a specific switch and is not to be repeated in subsequent collections (unless instructed by GSC). If possible, GSC recommends clearing the stats and waiting a minimum of 2 hours before another log collection though normally a 24 hour run after clearing statistics is a good approach to provide an overall health check of the equipment.

GSC recommends clearing the following statistics:

1. clear counters interface all
2. debug system internal clear-counters all
3. Clear ips-stats all

Normal method

Collect the results of the show tech-support details.

This can be done by turning on capture text, to record the results of the command with a Hyperterminal session. This can also be done by using Putty:

In order to enable a PuTTY Session.

1. To capture a session with PuTTY, open up a PuTTY.
2. Look for Category Session → Logging.
3. Under Session Logging, choose «Printable output» and key in your desire log filename (default is putty. log).

The syntax for the commands is:

• # terminal length 0
• # show tech-support details | no-more
• # show logging onboard | no-more

Please ensure that the output of each switch and command is logged into a separate file where the filename starts with the switch name. Compress each individual file into ZIP format  and upload these to the Hitachi TUF portal.

Troubleshooting SFP and Port issues:

SFP troubleshooting on Cisco switches require an additional command in order to review receive and transmit decibels. 
'show interface fcX/X transceiver details' -- this information is not available in some 'show tech-support details'. 
Collect both commands for troubleshooting port/SFP issues.

Performance related issues:

When performance related issues are encountered a separate set of logs is required.

Capture PuTTY (or similar) session and collect following output (Keep each show output and switches output in separate file.)

1. To capture a session with PuTTY, open up a PuTTY.
2. Look for Category Session → Logging.
3. Under Session Logging, choose «Printable output» and key in your desire log filename (default is putty. log).

configure terminal width at least 300 columns

• # terminal width 300
• # show tech-support details | no-more
• # show tech-support slowdrain | no-more
• # show logging onboard | no-more

Alternative method

Telnet to the switch and use the command tac-pac.

Cisco_syd9509# tac-pac bootflash:
Cisco_syd9509# dir bootflash:
451887 Jul 24 13:45:21 2008 show_tech_out.gz

tac-pac will automatically zip the show tech. You will need a ftp server to download the data from bootflash.

Data Collection via Fabric Manager

Open Fabric Manager. Select Tools > Show Tech Support

A window will open containing all the switches in the fabric. Select the relevant switches, then click "OK".

Select the following options:

• select the folder to save the show tech detail
• include a map of the fabric (JPEG or Visio),
  • This is only useful if you hide end devices to show only the switches in the fabric.
• automatically compress the support files

Data Collection for Cisco Fabric/Device Manager

Collect the following files from the Fabric Manager server:

1. C:\Program Files\Cisco Systems\dcm\fm\logs (Please collect and zip all files from this folder)
2. C:\Documents and Settings\\.cisco_mds9000\logs (Please collect and zip all files from this folder)
3. C:\Documents and Settings\\.cisco_mds9000\install.log (Please collect this file)

If possible, please provide screen captures of the problem.

Data Collection for Cisco Data Center Network Manager (DCNM) server

Collect the following files from the Data Center Network Manager server:

1. Technical Support Files

Run commands on the DCNM server

• • On Microsoft Windows: $INSTALLDIR/dcm/fm/bin/techsupport.bat
  • On Linux: $INSTALLDIR/dcm/fm/bin/techsupport.sh

2. Log Files

Zip up the files on following locations

• • On Microsoft Windows:C:\Program Files\Cisco Systems
  • On Linux: /usr/local/cisco

For more information see Cisco Data Center Network Manager Troubleshooting Guide, Release 11.x 

3. Alternative method via Cisco DCNM Web UI

• • Go to Administration > DCNM Server > Logs
  • Select Generate Techsupport to generate technical support and log files.

For more information see Cisco DCNM SAN Management Configuration Guide, Release 11.5(x)

4. Provide screen captures of the problem.