Diagnosing Switch Problems
Configuring Destination Switch
Follow the steps given below to configure the Destination Switch:
-> vlan 1000
-> spantree vlan 1000 admin-state disable
-> vlan 1000 members port 3/1-2 tagged
Enter the following QoS commands to override source learning:
-> policy condition c_ds1 source vlan 1000
-> mac-learning vlan 1000 disable
-> policy rule r_ds1 condition c_ds1 action a_ds1
-> qos apply
Port Monitoring
An essential tool of the network engineer is a network packet capture device. A packet capture device is
usually a PC-based computer, such as the Sniffer
measuring data traffic of a network. Understanding data flow in a VLAN-based switch presents unique
challenges, primarily because traffic moves inside the switch, especially on dedicated devices.
The port monitoring feature allows you to examine packets to and from a specific Ethernet port. Port
monitoring has the following features:
•
Software commands to enable and display captured port data.
•
Captures data in Network General
•
A file called pmonitor.enc is created in the /flash memory when you configure and enable a port
monitoring session.
•
Data packets time stamped.
•
One port monitored at a time.
•
RAM-based file system.
•
Statistics gathering and display.
The port monitoring feature also has the following restrictions:
•
All packets cannot be captured. (Estimated packet capture rate is around 500 packets/second.)
•
The maximum number of monitoring sessions is limited to one per chassis.
•
You cannot configure a port mirroring and a port monitoring session on the same NI module in an
OmniSwitch chassis-based switch.
•
You cannot configure port mirroring and monitoring on the same switching ASIC on OmniSwitch 10K
switches. Each switching ASIC controls 24 ports (e.g., ports 1–24, 25–48, etc.). For example, if a port
mirroring session is configured for ports 1/12 and 1/22, then configuring a port monitoring session for
any of the ports between 1 and 24 is not allowed.
•
If a port mirroring session is configured across two switching ASICs, then configuring a monitoring
session is not allowed on any of the ports controlled by each of the ASICs involved. For example, if a
OmniSwitch AOS Release 7 Network Configuration Guide
®
, that provides a means for understanding and
®
file format.
March 2011
Port Monitoring
page 26-23