PCAP feature support
PCAP uses the secondary CPU as the PCAP engine. It supports activating packet capture on
one or multiple ports. PCAP can also capture packets on ingress, egress, or both directions
(R and RS/8800 modules).
You can use PCAP with
• existing IP traffic filters so that only packets that match this filter criteria are captured
• existing MAC (fdb) filters so that only packets that match this filter criteria are captured
• PCAP supports software filters, which provides a way to filter the packets in the PCAP
engine.
PCAP supports software filters, which provide a way to filter the packets in the PCAP engine.
Captured packets can be stored on a PCMCIA device (or on external flash on the 8895 SF/
CPU) or on the network. The packets are stored in Sniffer Pro file format.
PCAP, IP, and MAC filter sets
IP traffic filter sets limit data traffic sent to the PCAP engine, the device that actively captures
data packets.
Using IP filter sets affect data network traffic depending on the action taken at the filter and
port level. Applying IP filter sets has the same affect on network traffic as configuring filter sets
to ports using PCAP parameters. For routed IP traffic, use Source/Destination IP filter sets; for
bridged IP traffic use Global IP filter sets.
You can use PCAP to capture packets that match criteria based on MAC address filters. Avaya
recommends that you use PCAP with MAC filters because it reduces traffic flow on the PCAP
engine.
PCAP filters
Use PCAP filters to selectively configure match criteria to capture or drop frames. The
configured parameters determine which filter to apply to a given frame. The default behavior
is to accept the frame. You can also set trigger filters to globally start and stop packet
capturing.
PCAP limitations and considerations
This section describes the limitations and considerations of the PCAP tool.
• PCAP is not compatible with HA-CPU. Disable HA-CPU prior to using this feature.
• PCAP is supported with SuperMezz.
Troubleshooting
Packet Capture Tool
July 2013
39