Avaya 8800 Troubleshooting Manual page 182

Software troubleshooting tool configuration using CLI
Method 2
In solution 1, the number of packets that are captured is quite large. In this solution, PCAP is
configured to refine the type of packets to be captured so that fewer packets are captured. This
solution uses IP traffic filters to capture only packets with a source IP address of 10.10.10.10
and a destination IP address of 10.10.20.20. In addition to procedures followed in method 1,
perform the following steps:
Procedure steps
1. Configure an IP traffic filter:
2. Create a filter set:
3. Apply a filter set to the port:
Method 3
If the amount of traffic flowing between client 1 and client 2 is still too large for analysis, define
a filter by protocol-type as shown in this solution. In this solution, PCAP filters are configured
on the PCAP engine to drop all IP packets that are not protocol type 6 and are not FTP packets.
In effect, this captures all TCP/FTP packets. When used in conjunction with IP filters, this
narrows down the number of packets captured to TCP/FTP packets flowing from client 2 to
client 1.
In addition to procedures followed in method 1 and 2, perform the following steps.
Procedure steps
Configure a capture filter:
config diag pcap capture-filter 7 create
config diag pcap capture-filter 7 action drop
config diag pcap capture-filter 7 protocol-type 6 not
config diag pcap capture-filter 7 tcp-port 20 to 21 not
182 Troubleshooting
config ip traffic-filter create global src-ip 10.10.10.10/32
dst-ip 10.10.20.20/32 id 5
config ip traffic-filter filter 5 action mode forward
config ip traffic-filter global-set 5 create name pcap_set
config ip traffic-filter global-set 5 add-filter 5
config eth 2/10 pcap add set 5
config eth 2/10 pcap enable true mode rxFilter
Comments? infodev@avaya.com
July 2013