Uploading The Capture File - Avaya G250 Administration Manual

Configuring monitoring applications
The following is an example of the show capture-buffer hex command:
G350-001> show capture-buffer hex
Frame number: 1
Time relative to first frame (D H:M:S:Micro-S): 0, 0:0:0.0
Packet time: 14/01/1970-13:24:55.583598
Frame length: 60 bytes
Capture Length: 60 bytes
00000000:ffff ffff ffff 0040 0da9 4201 0806 0001
00000010:0800 0604 0001 0040 0da9 4201 9531 4e7a
00000020:0000 0000 0000 9531 4e7a 0000 0000 0000
00000030:0000 0000 0000 0000 0000 0000
Frame number: 2
Time relative to first frame (D H:M:S:Micro-S): 0, 0:0:0.76838
Packet time: 14/01/1970-13:24:55.660436
Frame length: 60 bytes
Capture Length: 60 bytes
00000000:ffff ffff ffff 0040 0d8a 5455 0806 0001
00000010:0800 0604 0001 0040 0d8a 5455 9531 4e6a
00000020:0000 0000 0000 9531 4e6a 0000 0000 0000
00000030:0000 0000 0000 0000 0000 0000

Uploading the capture file

Once the packet sniffing service is stopped, upload the capture file to a server for viewing and
analysis.
Note:
The capture file may contain sensitive information, such as usernames and
Note:
passwords of non-encrypted protocols. It is therefore advisable to upload the
capture file over a secure channel – via VPN or using SCP (Secure Copy).
In most cases, you can upload the capture file to a remote server. However, in cases where the
capture file is very large, or you encounter a WAN problem, you can upload the capture file to
an S8300 Server and view it using Tethereal, which is a command-line version of Ethereal.
460 Administration for the Avaya G250 and Avaya G350 Media Gateways
.......@..B.....
.......@..B..1Nz
.......1Nz......
............
.......@..TU....
.......@..TU.1Nj
.......1Nj......
............