Data Collection for an Outage

Perform the following data collection procedures when the switch is in an outage condition and you require Technical Support to perform a root cause analysis.

Collect Data Before You Restart

Perform this procedure before you restart the chassis.

Procedure

  1. Capture the current state of the chassis:

    terminal more disable

    show tech

    Note

    Note

    show tech is an alias for show fulltech. Both commands provide the same output.

  2. Capture Flight Recorder trace information.

    flight-recorder all {slot[-slot][,...]}

    The all command executes three separate commands: flight-recorder snapshot, flight-recorder trace, and flight-recorder archive.

  3. Reset the chassis:
    1. Reset the chassis without creating a core file:

      reset –y

    2. Create an ssio core file, a cbcp-main.x core file, skip the confirmation question, and then reset the chassis:

      reset –coredump –y

    3. Create an ssio core file, a cbcp-main.x core file, prompt for the confirmation question, and then reset the chassis:

      reset –coredump

      Note

      Note

      Create a core file only when there is a need to analyze a problem. If you reset the switch for any other reason the command is reset –y.

  4. Continue with Collecting data after you restart.

Example

The following example shows output of the flight-recorder all 1 command.

Switch:1#flight-recorder all 1 
Processing Flight-recorder snapshot for 1 ....

Flight-recorder snapshot for slot 1 complete, filename is /intflash/PMEM/1/pmem.
20111019114431.1.bin.gz.

Processing Flight-recorder trace for 1 ....

Flight-recorder trace for slot 1 complete, filename is /intflash/flrec/1/trace.2
0111019114434.1.txt.

Processing Flight-recorder archive for slot 1 ....

Flight-recorder archive for slot 1 complete, filename is /intflash/archive/1/arc
hive.20111019114446.1.tar.

Collect Data After You Restart

About this task

Perform this procedure after you restart the affected chassis.

Procedure

  1. Use FTP to transfer the following information:
    • Configuration files from each chassis: Stored on the internal flash at /intflash/.

    • Log files from each chassis: Stored on the internal flash at /intflash/.

    • Generated archive files for slot: Stored on the internal flash. For example: /intflash/archive/<slot>

    Note

    Note

    For , if the core file is not on the primary control processor (CP), you can use FTP to connect to the internal flash of the primary CP. For example, cp mnt/intflash/archive/<slot>/<file name> /intflash/<file name>

    To copy the file to internal flash or usb device in the primary CP, use the following command: cp mnt/intflash/archive/<slot>/<file name> {/intflash/<file name> | /usb/<file name>}

  2. Show core information:

    show core—files

    If the timestamp for an entry in the command output matches the time the outage first occurred, or is later than that time, transfer that core file to an FTP server. Core files are stored on the internal flash at: /intflash/coreFiles/

  3. Obtain the network diagram of the relevant nodes, down to the port level.