Knowledge Search


×
 

How to debug GPRS:

  [KB3968] Show Article Properties


Summary:
How to debug GPRS:
Symptoms:

Solution:

Use the following CLI commands to log GTP message processing information:

set gtp log rate-limited extended

set gtp log tunnel-limited extended

set gtp log prohibited extended

set gtp log state-invalid extended

 

Use the following command to view the logged information:

get log system

Interpret the logged failures as follows.

*** Packet dropped due to bad direction
The gtp response message is dropped because it should be in the opposite direction with the preceding request message.

*** Packet dropped due to disallowed message type for v0
The gtp message is dropped because this v0 message type is prohibited.

*** Packet dropped due to disallowed message type for v1
The gtp message is dropped because this v1 message type is prohibited.

*** Packet dropped due to disallowed TID prefix
The gtp message is dropped because the TID prefix is prohibited.

*** Packet dropped due to missing mandatory IE(s)
The gtp message is dropped because some mandatory IE of this message type is missing.

*** Packet dropped due to missing spared '1111'
The gtp message is dropped because the mandated ''1111'' field is missing.

*** Packet dropped due to non-ascending order IEs
The gtp message is dropped because the IEs are out of the ascending order in this message.

*** Packet dropped due to non-digit TID
The gtp message is dropped because the TID consists of some octet which is neither digit nor padding ''F''.

*** Packet dropped due to non-existent TID
This gtp response message is dropped because there has not been any preceding request message of this TID.

*** Packet dropped due to non-zero TID
The gtp message is dropped because the TID is not zero in this path, location or mobility management message.

*** Packet dropped due to NSAPI being not 'F' in TID
The gtp message is dropped because the NSAPI in TID is not a padding ''F'' in this pdu-notification message.

*** Packet dropped due to out of new GSNs
The gtp message is dropped because the system fails to allocate a new GSN.

*** Packet dropped due to out of new paths
The gtp message is dropped because the system fails to allocate a new path.

*** Packet dropped due to out of new tunnels
The gtp message is dropped because the system fails to allocate a new tunnel.

*** Packet dropped due to rate limiting
The gtp message is dropped because the rate limit is exceeded.

*** Packet dropped due to too short
The gtp message is dropped because the message length is too short.

*** Packet dropped due to too long
The gtp message is dropped because the message length is too long.

*** Packet dropped due to tunnel limit
The gtp message is dropped because the tunnel limit is exceeded.

*** Packet dropped due to unknown message type
The gtp message is dropped because of undefined GTP message type.

*** Packet dropped due to unknown GTP IE
The gtp message is dropped because of undefined GTP IE.

*** Packet dropped due to wrong GTP message length
The gtp message is dropped because its length field is inconsistent with UDP length field.

*** Packet dropped due to wrong GTP version message for port 3386
The gtp message is dropped because the message is received from the v0 port but its GTP version is not 0.

*** Packet dropped due to wrong GTP version message for v1 port
The gtp message is dropped because the message is received from the v1 port but its GTP version is not 1.

*** Packet dropped due to wrong state
The gtp message is dropped because the current state of tunnel or path is not expecting this message.


Related Links: