capture can be performed on inbound traffic, outbound traffic, or both directions
simultaneously. The default behavior is to capture both directions.
Prior to release 10.2, filters on packet capture worked only on IP packets. With the
implementation
of the PCAP over VLAN feature, ACL rules can be applied on both IP and non-
IP interfaces. Also, MAC rules can be specified; packets are captured based on destination/
source MAC addresses. Prior to release 10.2 PCAP was supported only on CPU ports. The
PCAP over VLAN feature now supports Packet capture on Marvell/Broadcom LAN ports.
The number of packets to be captured can be specified, up to 10000, with the default behavior
being to capture all packets (value of 0). The maximum capture length for a packet can also
be specified, with a default value of 0 which captures the entire packet. The maximum (and
default) memory that can be used by a packet capture session is 5 MB, but can be configured
to a lower value. Captured packets can be saved both locally and as a remote file using FTP/
TFTP.
Note:
Packet capture is not supported on loopback interfaces.
Example of Packet Capture configuration
Configure the interface
configure terminal
vlan database
vlan 100
vlan 200
exit
Configure Ethernet 1
interface ethernet 6/1
switchport mode trunk
switchport trunk allowed vlan all
exit
Configure PPP 1
interface bundle wan1
link t1 1/1
encap ppp
switchport mode trunk
switchport trunk allowed vlan all
exit
Configure packet capture
access-list acc1
add permit mac any any vlan 100
add permit mac any any vlan 200
add permit ip any 30.30.30.2
add permit ip any 50.50.50.2
exit
capture cap1
attach ethernet 6/1
Global troubleshooting tasks
30 Troubleshooting August 2013
Comments? infodev@avaya.com
To Next Page
Loading...
