so that older information is overwritten when the buffer fills up, and specify a maximum number
of bytes to capture for each packet.
Related topics:
What can be captured on page 383
Roadmap for configuring packet sniffing on page 384
Configuring capture lists on page 386
Analyzing captured packets on page 396
About simulating packets on page 400
Summary of packet sniffing commands on page 400
What can be captured
The Branch Gateway packet sniffing service captures only the packets handled by the Branch
Gateway and delivered to the device CPU (“non-promiscuous” mode). This is unlike regular
sniffer applications that pick up all traffic on the network.
See
Roadmap for configuring packet sniffing on page 384 for a description of how to configure
packet sniffing and analyze the resulting capture file.
Related topics:
Streams that can always be captured on page 383
Streams that can never be captured on page 383
Streams that can sometimes be captured on page 384
Streams that can always be captured
• H.248 registration
• RTP from the Branch Gateway
• ARP on the LAN (broadcast)
• All packets that traverse the WAN
• All traffic to/from the Branch Gateway
Streams that can never be captured
The following streams can never be captured because they are switched by the internal
Ethernet switch and not by the CPU:
• H.323 Signaling from an IP phone on the LAN to an ICC on the LAN
• RTP stream between IP phones on the LAN
Monitoring applications
Administering Avaya G430 Branch Gateway October 2013 383
To Next Page
Loading...
