CISCO-WAN-MG-MIB :: mgEndpointState

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-WAN-MG-MIBmgEndpointState

mgEndpointState

Module: CISCO-WAN-MG-MIB

OID (symbolic): CISCO-WAN-MG-MIB::mgEndpointState

OID (numeric): 1.3.6.1.4.1.351.150.10.1.3.1.1.5

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: Indicates the state of the endpoint. 'mgEndpointActive' - the endpoint is in service and operational. 'mgEndpointFailed' - the endpoint is in service but not operational, e.g. because a line that the endpoint belongs to is in a state of service affecting alarm. 'mgEndpointDegraded' - the endpoint is in service but not fully operational, e.g. in cases with endpoints with channels on multiple lines, when one of the lines is in a state of service affecting alarm

If MGCP is used as the control protocol, the following transitions will generally trigger an RSIP command: from 'mgEndpointActive'/'mgEndpointDegraded' to 'mgEndpointFailed' or from 'mgEndpointFailed' to 'mgEndpointDegraded'/'mgEndpointActive'. Transitions between 'mgEndpointActive' and 'mgEndpointDegraded' will generally not trigger emission of RSIP.

What is mgEndpointState?

This read-only INTEGER reports the endpoint's operational state as mgEndpointActive(1), mgEndpointFailed(2), or mgEndpointDegraded(3), with failed meaning in service but not operational (e.g., due to a service-affecting alarm on its line) and degraded meaning in service but not fully operational. An admin uses this as the primary per-endpoint health check to distinguish a genuinely working endpoint from one that's provisioned but unusable due to an underlying line alarm. Seeing several endpoints flip to mgEndpointFailed(2) at once would point an admin straight to a shared underlying line alarm rather than treating each endpoint as an isolated problem.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.150.10.1.3.1.1.5
snmpwalk -v2c -c public <target> CISCO-WAN-MG-MIB::mgEndpointState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.351.150.10.1.3.1.1.5.1
snmpget -v2c -c public <target> CISCO-WAN-MG-MIB::mgEndpointState.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> mgEndpointState.1

Start monitoring Cisco WAN Media Gateway (VoIP-to-PSTN, legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-WAN-MG-MIB::mgEndpointState OID value, configure state conditions and alerts, and monitor any Cisco WAN Media Gateway (VoIP-to-PSTN, legacy) from a single console.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.351stratacomCISCOWAN-SMI
1.3.6.1.4.1.351.150ciscoWanCISCOWAN-SMI
Numeric OIDNameModule
1.3.6.1.4.1.351.150.10ciscoWanMgMIBCISCO-WAN-MG-MIB
1.3.6.1.4.1.351.150.10.1ciscoWanMgMIBObjectsCISCO-WAN-MG-MIB
1.3.6.1.4.1.351.150.10.1.3mediaGatewayEndpointCISCO-WAN-MG-MIB
1.3.6.1.4.1.351.150.10.1.3.1mgEndpointTableCISCO-WAN-MG-MIB
1.3.6.1.4.1.351.150.10.1.3.1.1mgEndpointEntryCISCO-WAN-MG-MIB
1.3.6.1.4.1.351.150.10.1.3.1.1.5mgEndpointStateCISCO-WAN-MG-MIB