Using a troubleshooting methodology

Once all relevant information is collected, success is improved significantly with a sound troubleshooting approach.

1. Check whether the device has all of the relevant licenses.
2. After adding or modifying a POD or port-upgrade license, re-enable the ports.
3. Verify the topology and switch configuration as conveyed by the switch
4. Enter the copy support command.
5. Run other relevant show commands (for example, show logging raslog) to look for clues or triggers of the reported failure.
6. Check the utilization of various resources.
   1. Enter the show process cpu command to determine CPU use.
   2. Enter the show process memory command to determine memory use.
   3. Enter the show mac-address-table count command to determine the number of MAC addresses used.
   4. Enter the show media command to investigate any optics issues.
7. Conduct data-path fabric continuity tests:
   1. Issue pings from and to the end-stations or devices.
   2. Check the counters in the output of the show interface command to detect if packets are coming in or are being dropped as errors.
   3. Verify that optics used are certified. Enter the show media interface command and verify that the Vendor name field shows BROCADE or EXTREME.
   4. Verify that the MAC address table learns the MAC addresses.
   5. Check whether LLDP reports neighbors.
8. 

   Caution

   The following step affects configuration and should be used with care.
   To track certain flows within the network, use permit ACLs and monitor the hit increments.