Cisco Cisco Packet Data Gateway (PDG)
show egtp
▀ show egtpc statistics verbose
▄ Statistics and Counters Reference, StarOS Release 18
3628
notifications, as described in the tables above. In addition, it tracks PDN session handling for invalid IMEI and
IMSI-less devices.
IMSI-less devices.
Table 331.
show egtpc statistics verbose
Command Output Descriptions -- IMSI/IMEI Statistics
Field
Description
IMSI/IMEI Statistics:
IMSI Invalid Length
The total number of IMSI with invalid length.
IMSI All Zero
The total number of invalid value IMSI with all 0 content.
IMSI Not BCD
The total number of invalid IMSI with value violating 3GPP defined format.
IMEI Invalid Length
The total number of valid IMSI but Invalid IMEI with Protocol violations.
IMEI All Zero
The total number of valid IMSI but Invalid value IMEI with all 0 content.
IMEI Not BCD
The total number of valid IMSI but Invalid IMEI with value violating 3GPP defined
format.
format.
IMEI All Zero (unauthenticated imsi)
The total number of Emergency PDN connections with missing IMSI and invalid value
IMEI with all 0 content.
IMEI with all 0 content.
IMEI Not BCD (unauthenticated imsi)
The total number of Emergency PDN connections with missing IMSI and Invalid IMEI
with value violating 3GPP defined format.
with value violating 3GPP defined format.
IMEI All Zero (unauthenticated imsi
and context replacement)
and context replacement)
The total number of Emergency PDN connections with missing IMSI and IMEI session
replacements because of invalid value IMEI with all 0 content.
replacements because of invalid value IMEI with all 0 content.
IMEI Not BCD (unauthenticated imsi
and context replacement)
and context replacement)
The total number of Emergency PDN connections with missing IMSI and IMEI session
replacements because of invalid IMEI with value violating 3GPP defined format.
replacements because of invalid IMEI with value violating 3GPP defined format.
Collision Counter Support in the GTP Layer
GTPv2 message collisions occur in the network when a node is expecting a particular procedure message from a peer
node but instead receives a different procedure message from the peer. The SAEGW software has been enhanced so that
these collisions are now tracked by statistics and handled based on a pre-defined action for each message collision type.
node but instead receives a different procedure message from the peer. The SAEGW software has been enhanced so that
these collisions are now tracked by statistics and handled based on a pre-defined action for each message collision type.
If the SAEGW is configured as a pure P-GW or a pure S-GW, operators will still see the respective collision statistics if
they occur.
they occur.
The output of this command has been enhanced to provide information on GTPv2 message collisions, including:
Interface: The interface on which the collision occurred: SGW (S4/S11), SGW (S5), or PGW (S5).
Old Proc (Msg Type): Indicates the ongoing procedure at eGTP-C when a new message arrived at the interface
which caused the collision. The Msg Type in brackets specifies which message triggered this ongoing
procedure.
procedure.
New Proc (Msg Type): The new procedure and message type.
Action: The pre-defined action taken to handle the collision. The action can be one of:
No Collision Detected