SaMOG Packet Capture (PCAP) Trace Support

Feature Information

Summary Data

Status

New Feature

Introduced-In Release

21.2

Modified-In Release(s)

Not Applicable

Applicable Product(s)

SaMOG

Applicable Platform(s)

ASR 5500

vPC-SI

vPC-DI

Default Setting

Disabled

Related CDETS ID(s)

CSCva99100

Related Changes in This Release

Not Applicable

Related Documentation

SaMOG Administration Guide

Command Line Interface Reference Guide

Revision History


Important
Revision history details are not provided for features introduced before release 21.2.

Revision Details

Release

Release Date

New in this release.

21.2

April 27, 2017

Feature Description

The PCAP trace output of the monitor subscriber and monitor protocol commands can be exported as a hexdump file for SaMOG sessions. The hexdump capture can be stored in a text file in a hard disk, and later transferred to an external server through SFTP using a PUSH or PULL method.

PCAP trace and hexdump file collection can be enabled or disabled under the monitor protocol and monitor subscriber commands.

For SaMOG, hexdump captures can be enabled for the following protocols:

  • GTPv1

  • GTPv2

  • GTPU

  • User L3

  • Diameter

  • Radius

  • EoGRE

  • PMIPv6

SaMOG subscriber information for PCAP trace can be specified using the following filters:

  • By MSID/IMSI

  • By callid

  • By username

  • Next-Call

  • By IMEI

  • By MSISDN

  • Next-SAMOG Call

For more information on PCAP Trace, Refer the Packet Capture (PCAP) Trace chapter in the ASR5500 System Administration Guide.