Cisco Cisco Nexus 5010 Switch Guida Alla Risoluzione Dei Problemi

Pagina di 2
Nexus 5000 Switch Packet Drop Identification
Document ID: 116172
Contributed by Vinayak Sudame, Colby Beam, and Somasundaram
Jayaraman, Cisco TAC Engineers.
Sep 05, 2013
Contents
Introduction
Identify Packet Drops
     Check for Queuing Drops
     Check for Forwarding Manager (FwM) Drops
Introduction
This document provides helpful tips to view the initial set of hardware drop counters on a Nexus 5000 switch.
This document is primarily for engineers who need immediate assistance in order to troubleshoot connectivity
and/or performance problems on a Nexus 5000 switch.
Identify Packet Drops
Note: Gatos is a 50x0 ASIC. Carmel is a 55xx ASIC.
Determine if the end devices are in the process of flowcontrol. If so, enter the show interface
flowcontrol
 and show interface priority−flow−control commands multiple times in order to check for
any link−level pause. Frames or PPP frames are generated on the interfaces.
1. 
Enter the show hardware internal gatos/carmel event−history errorscommand. This shows you any
errors recorded on Gatos or Carmel. If there are any pause frames in the network, check for
oq_timestamp interrupts that are fired on Gatos. Carmel does not implement pause rate limits, so
these interrupts are only shown for Gatos.
2. 
Determine if the MAC address is correctly recorded in the software and hardware for the end devices.
If there is an issue with connectivity over the VLAN Switch Virtual Interface (SVI), then look for the
respective MAC address on both Virtual Port Channel (vPC) peer switches in the hardware and
software.
3. 
Enter these commands:
show mac address−table address
◊ 
show platform fwm info hw−stm | inc <mac>
◊ 
If the entry is not present in the hardware, then there is a problem. It causes a flood of MAC addresses
on all ports and causes performance problems. It might also lead to connectivity issues.
4. 
Check for Queuing Drops
Enter the show queuing interface ethernet x/y command, and determine if there are ingress queuing discards: