Cisco Data Collection Best Practices
smo_ 100000NR1V Visits (1365)
The following command outputs should be gathered via CLI. Please log the (printable!) session output into one text file per switch per data collection round. On each switch start with setting the terminal length to zero to avoid pagewise output:
Switch# terminal length 0
2) Collecting data
Switch# show tech-support details For performance cases
That should give us most of the expected commands. To include internal counter tables and allow the analysis of historical data, please also run:
Switch# show logging onboard
If the problem could be related to the fiber optics (SFPs), like all physical problems incl. CRC errors, invalid transmission words, etc. please include:
Switch# show interface transceiver details
By having them all in one text file per switch you ensure them to be processed together properly. If you upload this data for IBM support I recommend to use the following naming convention for the text files.
The really important part is "_showtechSAN_" (including the underscores) but I recommend to use the full pattern to allow an easy identification of the proper data.
The text files of all switches can then be backed together in the same zip-file and uploaded to IBM (see the end of the article).
3) Clearing the counters
For ongoing problems it makes sense to clear the counters now. There are 3 major commands for that:
Regular interface counters:
Switch# clear counters interface all
Internal ASIC counters:
Switch# debug system internal clear-counters all
Switch# clear ips stats all
The first two should be done in any case, the third of course only if you have FCIP.