SNMP MIB Search

This object indicates the type of GPRS service that will be
enabled on the device:
undefined - the GPRS service functionality is turned off.
ggsn - the device will function as a GGSN.
sgsn - the device will function as SGSN.
gtpdirector - the device will function as GDM.
When the device is configured to function as GDM, all the other
objects in this MIB will not be accessible and the
CISCO-GTP-DIRECTOR-MIB should be used for managing the device.

The highest gtp version supported by the GSN.
When the value is,
version0 - GTP v0 is supported,
version1 - GTP v1 and GTP v0 are supported.

When the GSN behaves as SGSN, the T3-TUNNEL timer is used
for mobility management. When a roaming MS moves from one
SGSN(Old SGSN) to a another SGSN(New SGSN), this timer is
started by the 'Old SGSN'. While the timer is running, the
T-PDUs received by the 'Old SGSN' (from the GGSN), and any
buffered T-PDUs are forwarded to the 'New SGSN'.
When the GSN behaves as GGSN, the GGSN starts this timer
after receiving a Update PDP Context request message from
'New SGSN'. An Update PDP context request shall be sent by
SGSN as part of mobility management intimating that MS has
moved to this SGSN. While the timer is running, the GGSN will
not be forwarding any PDUs to the requesting 'New SGSN'.

The T3-RESPONSE timer for retransmission. This timer
is started by a GSN, upon the transmission of a signalling
request message; it is used for message retransmission
purposes, in the event that no response is received by
the time the timer expires.

Maximum number of retransmissions for a signalling
request message if no corresponding response message
is received for a request in cGtpT3ResponseTimer time.

Maximum size of the receive buffer for G-PDUs and
signalling request messages. If a packet arrives with
more data bytes than the receive buffer can contain,
the packet will be discarded.

This object indicates whether Echo Request timer
is used by the GGSN.
- true  : will enable the Echo Request timer.
- false : will disable the Echo Request timer.

The time interval to transmit 'Echo Request' message.
'Echo Response' message is normally received in response
to 'Echo Request' message. In the event of no response to
the 'Echo Request' message, a notification is generated
identifying the peer GSN (i.e. cGtpGSN Address), which
fails to respond.
This object can be retrieved only if
cGtpEchoRequestTimerEnable is set to 'true'.

The total amount of bandwidth resource on the GSN,
this total depends on various factors like system
throughput, memory size, maximum number of PDP contexts
supported.  A portion of the total resources will be
allocated to a user at the PDP context activation time
based on the Qos class the user is assigned to.

The maximum number of PDP contexts that can be activated
on the GSN.

Indicates whether cGtpNotifications notification will
be sent when a notification is generated by the device.
- 'true',  it will enable the device to send a notification.
- 'false', it will prevent the device from sending out a
notification.

This object indicates whether dynamic echo timer is used
by the GGSN.
- true  : will enable the dynamic echo timer.
- false : will disable the dynamic echo timer.

This object specifies the minimum time used by the
dynamic echo timer. This object should be ignored
if cGtpDynamicEchoTimerEnable is set to 'false'.

This object specifies the smooth factor by which dynamic
echo timer can be adjusted. This object should be ignored
if cGtpDynamicEchoTimerEnable is set to 'false'.

This object indicates the type of Internet address
by which cGtpLastNoRespToEchoGSNIpAddr is reachable.

The IP address of the last peer GSN device that did not
reply to an GTP 'Echo Request' message from the local GSN
device.

The sum of the mean throughput for premium class QOS
users on the GSN.

The sum of the mean throughput for normal class QOS
users on the GSN.

The sum of the mean throughput for best-effort class
QOS users on the GSN.

GSN entry. The entry is created when a path between a GGSN
and SGSN is setup and the corresponding peer is not yet listed
in the GSN peer table. The entry is deleted when the path
is released, or echo test message on the path times out
after certain retry number defined as cGtpN3Request.

The entry is created:
1. When a path between a GGSN and SGSN is setup.
2. Or, when a path between the GGSN and the charging
gateway is setup.
3. Or, when a path between GGSN and the MAP converting GSN
is setup.
The entry is deleted when the path is released, or echo
test message on the path times out after certain retry number
defined as cGtpN3Request.

The number of times that any one of this GSN's peers
failed to respond to an GTP 'Echo Request' messages
during the waiting intervals.

The current amount of bandwith resource used on the GSN.

The total number of received GTP packets that could not
be processed and are dropped since system started.

The type of Internet address by which cGtpGSNAddress
is reachable.

Ip address that uniquely identify a GSN node.

This object represents the GTP version supported by the
GSN node, identified by cGtpGSNAddressType and cGtpGSNAddress.
The value:
version0 - represents GTP version0 and
version1 - represents GTP version1.

The type of Internet address by which cGtpPathAddress
is reachable.

An address that uniquely identifies a remote node to which
this path is established.

This object identifies the port on the remote node.
The value of zero is invalid.

This object represents the GTP version of the path
identified by cGtpPathEntry.
The value:
version0 - represents GTP version0 and
version1 - represents GTP version1.

GSN peer table. The SGSN-GGSN peer relationship is established
as given in the following series of steps:
1. When Mobile System (MS) wants service, it sends packets
to a SGSN  with specific APN.
2. SGSN uses the DNS to resolve this APN to the IP address
of the GGSN which is the designated as the gateway to
this APN.
3. SGSN establishes a path to the GGSN using GTP protocol.
4. The SGSN and GGSN peer maintains path by sending echo
request message to each other. If one side fails in echo
reply for certain times, the other side will send a
notification to NMS. A SGSN can have multiple GGSN as
peers, while a GGSN can have multiple SGSN peers,
depending on routing path.

This table identifies the paths established on a GSN. The
path may be established between a GGSN and SGSN or GGSN
and charging gateway or GGSN and MAP converting GSN.
The path between GGSN and charging gateway is established
when the charging gateway is configured on the GGSN.
The path between GGSN and MAP converting GSN is established
when the MAP converting GSN is configured on the GGSN.
The path between a GGSN and SGSN is established in the
following series of steps:
1. When Mobile System (MS) wants service, it sends packets
to a SGSN with specific APN.
2. SGSN uses the DNS to resolve this APN to the IP address
of the GGSN which is the designated as the gateway to
this APN.
3. SGSN establishes a path to the GGSN using GTP protocol.
4. The SGSN and GGSN peer maintains path by sending echo
request message to each other. If one side fails in echo
reply for certain times, the other side will send a
trap to NMS. A SGSN can have multiple GGSN as peers,
while a GGSN can have multiple SGSN peers, depending
on routing path. Moreover, a GSN can have more than one
path to a peer, each of which will have a unique port.

This notification is sent when one of this GSN's peers
failed to respond to the GTP 'Echo Request' message for
the waiting interval.

This MIB module manages the GPRS Tunnelling Protocol
(GTP) on GGSN and SGSN.
GPRS provides wireless access to packet data network on
the GSM infrastructure.
The following diagram illustrates a simplified GPRS
logical architecture with the name of inter-node
interface:
+---------------------------------------------+
|                         +======+   a PLMN   |
|                         | SGSN |            |
|                         +======+            |
|                            |                |
|                            Gn               |
|                            |                |
|+====+   +====+ +=====+ +======+    +======+ |    +===+
|| TE |-R-| MT |-| BSS |-| SGSN |-Gn-| GGSN |-|-Gi-|PDN|
|+====+   +====+ +=====+ +======+    +======+ |    +===+
|                                        |    |
|                                        |    |
+----------------------------------------|----+
Gp
|
+-----------------------------+
| +====+   +=====+   +======+ |
| | MS |---| BSS |---| SGSN | |
| +====+   +=====+   +======+ |
|                             |
|                other PLMN   |
+-----------------------------+
GTP is the protocol between GSN nodes (GSN peers) in
the GPRS backbone network. It includes both the GTP
signalling and data transfer procedures.
GTP is used both on the Gn interface, i.e. the interface
between GSN peers with in a PLMN, and the Gp
interface between GSN peers in different PLMNs.
SGSN is the serving GPRS support node, it responsible
for the delivery of data packets from and to the MS
within its service area.
GGSN is the gateway GPRS support node, it provides
interworking with external PDN and is connected with
SGSNs via an IP-based GPRS backbone network.
The GTP protocol is implemented only by SGSNs and GGSN.
A PDP Context is an information set maintained by MS
and GSNs which describes the mobile wireless service
call or session.
A Qos Profile is associated with each PDP context which
defines multiple attributes like precedence, delay,
reliability, peak throughput and mean throughput.
Based on the precedence, delay and mean throughput an
user is classified into one of the three Qos classes:
Best Effort, Normal and Premium.
Mean throughput is measured at the Gi and R reference
points in units of octets per second. It specifies the
average rate at which data is expected to be
transferred across the GPRS network during the
remaining lifetime of an activated PDP context.
A MAP converting GSN is responsible for converting GTP
messages to and from MAP messages.  This helps in the
communication with HLR.
Acronyms and terms:
APN    Access Point Name
BSS    Base Station Subsystem
ETSI   European Telecommunications Standards Institute
GDM    GTP Director Module
Gi     Reference point between GPRS and an external
packet data network.
Gn     the interface between GSNs within a PLMN
Gp     the interface between GSNs in different PLMNs
GGSN   Gateway GPRS Support Node
GPRS   General Packet Radio Service
GSM    Global System for Mobile communication
GSN    GPRS Support Node
G-PDU  GTP PDU
HLR    Home Location Register
MAP    Mobile Application Protocol
MS     Mobile Station = TE + MT
MT     Mobile Termination
NMS    Network Management System
PDN    Public Data Network
PDP    Packet Data Protocol
PDU    Protocol Data Unit
PLMN   Public Land Mobile Network
R      Reference point between a non-ISDN compatible
TE and MT.
SGSN   Serving GPRS Support Node
TE     Terminal Equipment
T-PDU  the payload of G-PDU

 A collection of GTP configurations.

 A collection of GTP Status.

 A collection of GTP statistics .

 A collection of GTP configurations.

 A collection of GTP Status.

 A collection of GTP statistics .

A collection of GTP notifications.

 A collection of GTP configurations.

 A collection of GTP status.  This is deprecated by
cGtpStatusGroupRev3.

 A collection of GTP status.