JUNIPER-MOBILITY-SGW-CHARGING-MIB

        This is Juniper Networks implementation of Mobility Charging MIB for 
SGW (Serving Gateway ) in 3GPP LTE network.
    
Source file
JUNIPER-MOBILITY-SGW-CHARGING-MIB
Last revised
Identity
jnxMbgSgwChargingMib
Base OID
1.3.6.1.4.1.2636.3.66.2.3
Imported Objects
JUNIPER-MBG-SMI jnxMobileGatewaySgw
JUNIPER-MOBILE-GATEWAYS jnxMbgGwIndex jnxMbgGwName
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Counter64 Gauge32 Integer32 IpAddress MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC DisplayString RowStatus TEXTUAL-CONVENTION (no object page) TruthValue
Net-SNMP examples using the juniper MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'JUNIPER-MOBILITY-SGW-CHARGING-MIB' -M '/opt/observium/mibs/juniper:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'JUNIPER-MOBILITY-SGW-CHARGING-MIB::jnxMbgSgwChargingMib'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'JUNIPER-MOBILITY-SGW-CHARGING-MIB' -M '/opt/observium/mibs/juniper:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'JUNIPER-MOBILITY-SGW-CHARGING-MIB::jnxMbgSgwChargingMib'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (80)
.1.3.6.1.4.1.2636.3.66.2.3
.1.3.6.1.4.1.2636.3.66.2.3.0
.1.3.6.1.4.1.2636.3.66.2.3.1
.1.3.6.1.4.1.2636.3.66.2.3.1.1
.1.3.6.1.4.1.2636.3.66.2.3.1.1.1
.1.3.6.1.4.1.2636.3.66.2.3.1.1.1.1
.1.3.6.1.4.1.2636.3.66.2.3.1.1.1.2
.1.3.6.1.4.1.2636.3.66.2.3.1.2
.1.3.6.1.4.1.2636.3.66.2.3.1.2.1
.1.3.6.1.4.1.2636.3.66.2.3.1.2.1.1
.1.3.6.1.4.1.2636.3.66.2.3.1.2.1.10
.1.3.6.1.4.1.2636.3.66.2.3.1.2.1.11
.1.3.6.1.4.1.2636.3.66.2.3.1.2.1.12
.1.3.6.1.4.1.2636.3.66.2.3.1.2.1.13
.1.3.6.1.4.1.2636.3.66.2.3.1.2.1.14
.1.3.6.1.4.1.2636.3.66.2.3.1.2.1.2
.1.3.6.1.4.1.2636.3.66.2.3.1.2.1.3
.1.3.6.1.4.1.2636.3.66.2.3.1.2.1.4
.1.3.6.1.4.1.2636.3.66.2.3.1.2.1.5
.1.3.6.1.4.1.2636.3.66.2.3.1.2.1.6
.1.3.6.1.4.1.2636.3.66.2.3.1.2.1.7
.1.3.6.1.4.1.2636.3.66.2.3.1.2.1.8
.1.3.6.1.4.1.2636.3.66.2.3.1.2.1.9
.1.3.6.1.4.1.2636.3.66.2.3.1.3
OctetString
.1.3.6.1.4.1.2636.3.66.2.3.1.3.1
.1.3.6.1.4.1.2636.3.66.2.3.1.3.10
.1.3.6.1.4.1.2636.3.66.2.3.1.3.11
.1.3.6.1.4.1.2636.3.66.2.3.1.3.12
.1.3.6.1.4.1.2636.3.66.2.3.1.3.13
.1.3.6.1.4.1.2636.3.66.2.3.1.3.14
.1.3.6.1.4.1.2636.3.66.2.3.1.3.15
.1.3.6.1.4.1.2636.3.66.2.3.1.3.16
OctetString
.1.3.6.1.4.1.2636.3.66.2.3.1.3.2
Enumeration
.1.3.6.1.4.1.2636.3.66.2.3.1.3.3
OctetString
.1.3.6.1.4.1.2636.3.66.2.3.1.3.4
Enumeration
.1.3.6.1.4.1.2636.3.66.2.3.1.3.5
Enumeration
.1.3.6.1.4.1.2636.3.66.2.3.1.3.6
.1.3.6.1.4.1.2636.3.66.2.3.1.3.7
Enumeration
.1.3.6.1.4.1.2636.3.66.2.3.1.3.8
.1.3.6.1.4.1.2636.3.66.2.3.1.3.9
.1.3.6.1.4.1.2636.3.66.2.3.1.4
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.1
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.10
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.11
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.12
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.13
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.14
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.15
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.16
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.17
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.18
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.19
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.2
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.20
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.21
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.22
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.23
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.24
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.25
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.26
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.27
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.28
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.29
Enumeration
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.3
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.30
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.4
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.5
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.6
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.7
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.8
.1.3.6.1.4.1.2636.3.66.2.3.1.4.1.9
.1.3.6.1.4.1.2636.3.66.2.3.1.5
.1.3.6.1.4.1.2636.3.66.2.3.1.5.1
.1.3.6.1.4.1.2636.3.66.2.3.1.5.1.1
.1.3.6.1.4.1.2636.3.66.2.3.1.5.1.2
.1.3.6.1.4.1.2636.3.66.2.3.1.5.1.3
.1.3.6.1.4.1.2636.3.66.2.3.1.5.1.4
.1.3.6.1.4.1.2636.3.66.2.3.1.5.1.5
.1.3.6.1.4.1.2636.3.66.2.3.1.5.1.6
Dependencies (13) 5 direct · 8 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Notifications / Traps (12)
NameOIDDescription
.1.3.6.1.4.1.2636.3.66.2.3.0.1
This notification signifies that the specified server has been
marked alive. The ServerName identifies the server and the
SPIdentfier identifies the session-pic which originated this
notification.
.1.3.6.1.4.1.2636.3.66.2.3.0.10
This trap indicates the alarm status on the node associated with the utilization of local storage space for charging records. This alarm is sent out when the utilization exceeds or falls below configured high threshold of available disk space. The alarm status (Active/Clear)is indicated by the jnxMbgSgwCgAlarmStatus variable.
.1.3.6.1.4.1.2636.3.66.2.3.0.11
This trap indicates the alarm status on the node associated with the utilization of local storage space for charging records. This alarm is sent outwhen the utilization exceeds or falls below configured medium threshold of available disk space. The alarm status (Active/Clear)is indicated by the jnxMbgSgwCgAlarmStatus variable.
.1.3.6.1.4.1.2636.3.66.2.3.0.12
This trap indicates the alarm status on the node associated with the utilization of local storage space for charging records. This alarm is sent out when the utilization exceeds or falls below configured low threshold of available disk space. The alarm status (Active/Clear)is indicated by the jnxMbgSgwCgAlarmStatus variable.
.1.3.6.1.4.1.2636.3.66.2.3.0.2
This notification signifies that the specified server has been
marked dead. The ServerName identifies the server and the
SPIdentfier identifies the session-pic which originated this
notification.
.1.3.6.1.4.1.2636.3.66.2.3.0.3
This signifies change in the destination of the CDRs
(Charging Data Record)
.1.3.6.1.4.1.2636.3.66.2.3.0.4
This signifies the Charging daemon is UP on the SP.
.1.3.6.1.4.1.2636.3.66.2.3.0.5
This indicates that the given charging profile underwent a change
in the maintenance-mode.
.1.3.6.1.4.1.2636.3.66.2.3.0.6
This indicates that the given transport profile underwent a change
in the maintenance-mode.
.1.3.6.1.4.1.2636.3.66.2.3.0.7
This trap indicates the alarm status on the node associated with the utilization of inernal memory space for charging records. This alarm is sent outwhen the utilization exceeds or falls below configured high threshold value. Thealarm status (Active/Clear)is indicated by the jnxMbgSgwCgAlarmStatus variable.
.1.3.6.1.4.1.2636.3.66.2.3.0.8
This trap indicates the alarm status on the node associated with the utilization of inernal memory space for charging records. This alarm is sent outwhen the utilization exceeds or falls below configured medium threshold value. The alarm status (Active/Clear)is indicated by the jnxMbgSgwCgAlarmStatus variable.
.1.3.6.1.4.1.2636.3.66.2.3.0.9
This trap indicates the alarm status on the node associated with the utilization of inernal memory space for charging records. This alarm is sent outwhen the utilization exceeds or falls below configured low threshold value. The alarm status (Active/Clear)is indicated by the jnxMbgSgwCgAlarmStatus variable.