Reference record for OID 1.3.6.1.4.1.9.9.188.1.2.7

Parent
1.3.6.1.4.1.9.9.188.1.2 (cGtpStatus)
Node code
7
Node name
cGtpPathTable
Numeric OID
1.3.6.1.4.1.9.9.188.1.2.7
URN notation
urn:oid:1.3.6.1.4.1.9.9.188.1.2.7
Type
OBJECT-TYPE
ASN.1 notation

{1 3 6 1 4 1 9 9 188 1 2 7}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) cGtpMIB(188) cGtpMIBObjects(1) cGtpStatus(2) cGtpPathTable(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) cGtpMIB(188) cGtpMIBObjects(1) cGtpStatus(2) cGtpPathTable(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) cGtpMIB(188) cGtpMIBObjects(1) cGtpStatus(2) cGtpPathTable(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) cGtpMIB(188) cGtpMIBObjects(1) cGtpStatus(2) cGtpPathTable(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) cGtpMIB(188) cGtpMIBObjects(1) cGtpStatus(2) cGtpPathTable(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) cisco(9) ciscoMgmt(9) cGtpMIB(188) cGtpMIBObjects(1) cGtpStatus(2) cGtpPathTable(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) cGtpMIB(188) cGtpMIBObjects(1) cGtpStatus(2) cGtpPathTable(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) cGtpMIB(188) cGtpMIBObjects(1) cGtpStatus(2) cGtpPathTable(7)}
  • ...skipped...
OID-IRI notation
  • /1/3/6/1/4/1/9/9/188/1/2/7
  • /ISO/Identified-Organization/6/1/4/1/9/9/188/1/2/7
  • /ISO/3/6/1/4/1/9/9/188/1/2/7
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/cGtpMIB/cGtpMIBObjects/cGtpStatus/cGtpPathTable
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/cGtpMIB/cGtpMIBObjects/cGtpStatus/cGtpPathTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/cGtpMIB/cGtpMIBObjects/cGtpStatus/cGtpPathTable
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/cGtpMIB/cGtpMIBObjects/cGtpStatus/cGtpPathTable
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/cGtpMIB/cGtpMIBObjects/cGtpStatus/cGtpPathTable
  • /iso/org/dod/internet/private/ldap-enterprise/cisco/ciscoMgmt/cGtpMIB/cGtpMIBObjects/cGtpStatus/cGtpPathTable
  • /iso/iso-identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/cGtpMIB/cGtpMIBObjects/cGtpStatus/cGtpPathTable
  • /iso/iso-identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/cGtpMIB/cGtpMIBObjects/cGtpStatus/cGtpPathTable
  • ...skipped...
All recorded component names

Each component can use any of its recorded names. The examples above show up to eight combinations. ASN.1 names do not necessarily have registered OID-IRI labels.

  • 1: iso
  • 1.3: identified-organization, org, iso-identified-organization, iso-organization
  • 1.3.6: dod
  • 1.3.6.1: internet
  • 1.3.6.1.4: private
  • 1.3.6.1.4.1: enterprise, enterprises, ldap-enterprise
  • 1.3.6.1.4.1.9: cisco
  • 1.3.6.1.4.1.9.9: ciscoMgmt
  • 1.3.6.1.4.1.9.9.188: cGtpMIB
  • 1.3.6.1.4.1.9.9.188.1: cGtpMIBObjects
  • 1.3.6.1.4.1.9.9.188.1.2: cGtpStatus
  • 1.3.6.1.4.1.9.9.188.1.2.7: cGtpPathTable

Descriptions may differ between sources. The primary description is shown first.

Primary description: OID Repository

cGtpPathtable
View at oid-base.com

Alternative description: Circitor

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

Source file: Download CISCO-GTP-MIB.mib SHA-256: 70f926202d3b842bc6819110f6324ecde53e0f83a73d877bec3b0596071c0fd1

Alternative description: Cisco

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.

Source file: Download CISCO-GTP-MIB.my · Publisher's file SHA-256: 2f3708b7ef7c39dcf0943b859e5e17d096dc8d9b570e02efc77fbd775318582a

Alternative description: Cisco SMIv1

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.

Source file: Download CISCO-GTP-MIB-V1SMI.my · Publisher's file SHA-256: 5fecf01b9698cd53af5704ad0593351bc5215ad8bc6789297439f7226d36b1b6

Source file: Download cisco/CISCO-GTP-MIB-V1SMI.my.txt SHA-256: d2bb41253423e80c0add8dbe96877630bba9f958c9e3d820774f684c4dd0c3de

Alternative description: MIBdepot

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.

Source file: Download cisco/CISCO-GTP-MIB.my.txt SHA-256: 70f926202d3b842bc6819110f6324ecde53e0f83a73d877bec3b0596071c0fd1

Information from Circitor

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 }

Information from Cisco SMIv1

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 }

Information from OID Repository

Vendor: Cisco
Module: CISCO-GTP-MIB

[Automatically extracted from oidview.com]

Information from MIBdepot

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 }

Information from Cisco

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 }

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)

Greg Satz

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.9)

Cisco Systems, Inc.

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.9.188.1.2.7.1 cGtpPathEntry66 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…

Siblings (8)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.9.9.188.1.2.1 cGtpLastNoRespToEchoGSNIpAddrTyp11 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 cGtpLastNoRespToEchoGSNIpAddr11 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 cGtpPremiumQosMeanThroughput11 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 cGtpNormalQosMeanThroughput11 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 cGtpBestEffortQosMeanThroughput11 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 cGtpGSNTable14 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 cGtpTotalActivePaths00 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 cGtpTotalActiveGtpv1DataPaths00 This object represents the total number of GTPv1-U data
paths currently active on the gateway.