Руководство По Устранению Ошибки для Cisco Cisco Nexus 5010 Switch

Contributed by Prashanth Krishnappa, Vinayak Sudame, and Shelley
Bhalla, Cisco TAC Engineers.
Jul 01, 2013

Introduction
Prerequisites
     Requirements
     Components Used
Ethanalyzer

This document describes how to use the built−in packet capture tool, Ethanalyzer, on the Nexus
3000/5000/7000 switches.

There are no specific requirements for this document.

The information in this document is based on Nexus 3000, Nexus 5000, and Nexus 7000 switches.

The information in this document was created from the devices in a specific lab environment. All of the
devices used in this document started with a cleared (default) configuration. If your network is live, make sure
that you understand the potential impact of any command.

Ethanalyzer is a useful tool to troubleshoot control plane and traffic destined to switch CPU. Mgmt is the
interface to troubleshoot packets that hit the mgmt0 interface. Inbound−low (eth3) is for low priority (ping,
telnet, Secure Shell) CPU−bound traffic, and inbound−hi (eth4) is for high priority (Spanning Tree Protocol
(STP), Bridge Protocol Data Units, FIP) CPU−bound traffic.

Note: You can use the Display Filter or the Capture Filter as an option. The Display filter option is preferred
on the Nexus 5000, and the Capture Filter is preferred on the Nexus 3000 and Nexus 7000.

Commonly used Display Filters can be found at Wireshark 

Commonly used Capture Filters can be found at Wireshark 

Note: Since Nexus 5000 uses internal VLANs to forward frames, Ethanlyzer has internal VLANs. Nexus
5000 forwards frames based on internal VLANs and Ethanalyzer displays the internal VLAN. When you