7. At the FTP login prompt, enter
anonymous
.
8. At the FTP password prompt, enter your e-mail address.
9. Optionally, enter
show upload status 10
to view upload status.
For example:
Gxxx-001(super)# show upload status 10
Module #10
===========
Module : 10
Source file : sniffer
Destination file : pub/capfile.cap
Host : 149.49.43.96
Running state : Executing
Failure display : (null)
Last warning : No-warning
Capture file analysis
The uploaded capture file is in libpcap format and can therefore be viewed by most sniffer
applications, including tcpdump, Ethereal and Tethereal.
If you uploaded the capture file to an S3800 server, view the file using Tethereal, a command-
line version of Ethereal available on the S3800. See the Tethereal man pages for more
information about the Tethereal application.
If you uploaded the capture file to a remote server, you can view the file using the industry
standard Ethereal application. The latest version of Ethereal for Windows, Linux, UNIX, and
other platforms can be downloaded from
Note:
Ethereal allows you to create filter expressions to filter the packets in the capture file and
display desired files only. For example, you can display only packets with a specific source
address, or only those received from a specific interface. See
page 399.
Related topics:
on page 399
Interface identification
The Branch Gateway’s packet sniffing service can capture also non-Ethernet packets, such
as frame-relay and PPP, into the capture file. This is achieved by wrapping non-Ethernet
packets in a dummy Ethernet header to allow the packets to be stored in a libpcap format. This
enables you to analyze packets on all the device interfaces.
The dummy Ethernet headers are allocated according to the original packet type. Dummy
Ethernet headers start with 00:00. Therefore, if the source or destination address of a packet
you are viewing in Ethereal starts with 00:00, this indicates the packet is a non-Ethernet
packet.
The dummy Ethernet header is identified by special MAC addresses. Packets sent from a non-
Ethernet interface are identified with an SA address in the format 00:01:00:00:xx and a DA
Monitoring applications
Administering Avaya G430 Branch Gateway
October 2013 399
Summary of Contents for G430
Page 1: ...Administering Avaya G430 Branch Gateway Release 6 3 03 603228 Issue 5 October 2013 ...
Page 12: ...12 Administering Avaya G430 Branch Gateway October 2013 ...
Page 246: ...VoIP QoS 246 Administering Avaya G430 Branch Gateway October 2013 Comments infodev avaya com ...
Page 556: ...IPSec VPN 556 Administering Avaya G430 Branch Gateway October 2013 Comments infodev avaya com ...