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.
Parsed from file CISCO-GTP-MIB.mib
Module: CISCO-GTP-MIB
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.
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.
Parsed from file CISCO-GTP-MIB.my.txt
Company: None
Module: CISCO-GTP-MIB
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.
cGtpGSNTable OBJECT-TYPE SYNTAX SEQUENCE OF CGtpGSNEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "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." ::= { cGtpStatus 6 }
cGtpGSNTable OBJECT-TYPE SYNTAX SEQUENCE OF CGtpGSNEntry ACCESS not-accessible STATUS deprecated DESCRIPTION "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." ::= { cGtpStatus 6 }
Vendor: Cisco
Module: CISCO-GTP-MIB
[Automatically extracted from oidview.com]
cGtpGSNTable OBJECT-TYPE SYNTAX SEQUENCE OF CGtpGSNEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "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." ::= { cGtpStatus 6 }
cGtpGSNTable OBJECT-TYPE SYNTAX SEQUENCE OF CGtpGSNEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "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." ::= { cGtpStatus 6 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.188.1.2.6.1 | cGtpGSNEntry | 3 | 3 | 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 … |
| 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.7 | cGtpPathTable | 1 | 7 | cGtpPathtable |
| 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. |