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.
Parsed from file CISCO-GTP-MIB.mib
Module: CISCO-GTP-MIB
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.
cGtpPathtable
View at oid-info.com
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.
Parsed from file CISCO-GTP-MIB.my.txt
Company: None
Module: CISCO-GTP-MIB
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.
cGtpPathTable OBJECT-TYPE SYNTAX SEQUENCE OF CGtpPathEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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." ::= { cGtpStatus 7 }
cGtpPathTable OBJECT-TYPE SYNTAX SEQUENCE OF CGtpPathEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "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." ::= { cGtpStatus 7 }
Vendor: Cisco
Module: CISCO-GTP-MIB
[Automatically extracted from oidview.com]
cGtpPathTable OBJECT-TYPE SYNTAX SEQUENCE OF CGtpPathEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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." ::= { cGtpStatus 7 }
cGtpPathTable OBJECT-TYPE SYNTAX SEQUENCE OF CGtpPathEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "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." ::= { cGtpStatus 7 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.188.1.2.7.1 | cGtpPathEntry | 6 | 6 | 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 gatewa… |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.188.1.2.1 | cGtpLastNoRespToEchoGSNIpAddrTyp | 1 | 1 | This object indicates the type of Internet address by which cGtpLastNoRespToEchoGSNIpAddr is reachable. |
| 1.3.6.1.4.1.9.9.188.1.2.2 | cGtpLastNoRespToEchoGSNIpAddr | 1 | 1 | The IP address of the last peer GSN device that did not reply to an GTP 'Echo Request' message from the local GSN device. |
| 1.3.6.1.4.1.9.9.188.1.2.3 | cGtpPremiumQosMeanThroughput | 1 | 1 | The sum of the mean throughput for premium class QOS users on the GSN. |
| 1.3.6.1.4.1.9.9.188.1.2.4 | cGtpNormalQosMeanThroughput | 1 | 1 | The sum of the mean throughput for normal class QOS users on the GSN. |
| 1.3.6.1.4.1.9.9.188.1.2.5 | cGtpBestEffortQosMeanThroughput | 1 | 1 | The sum of the mean throughput for best-effort class QOS users on the GSN. |
| 1.3.6.1.4.1.9.9.188.1.2.6 | cGtpGSNTable | 1 | 4 | GSN peer table. The SGSN-GGSN peer relationship is established as given in the following series of steps: 1. When Mobile System (… |
| 1.3.6.1.4.1.9.9.188.1.2.8 | cGtpTotalActivePaths | 0 | 0 | This object represents the total number of paths currently active on the gateway. |
| 1.3.6.1.4.1.9.9.188.1.2.9 | cGtpTotalActiveGtpv1DataPaths | 0 | 0 | This object represents the total number of GTPv1-U data paths currently active on the gateway. |