Nortel-MsCarrier-MscPassport-DcmeMIB :: mscDclVsLCoReasonForNoRoute

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › Nortel-MsCarrier-MscPassport-DcmeMIB › mscDclVsLCoReasonForNoRoute

mscDclVsLCoReasonForNoRoute

Module: Nortel-MsCarrier-MscPassport-DcmeMIB

OID (symbolic): Nortel-MsCarrier-MscPassport-DcmeMIB::mscDclVsLCoReasonForNoRoute

OID (numeric): 1.3.6.1.4.1.562.36.2.1.130.4.3.10.1.20

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: This attribute is the route selection's reasonForNoRoute and provides a brief reason for which a route was not selected. The reasons are essentially self-explanatory. Perhaps two reasons for no route require some explanation. The reason unknownRemoteNodeName is issued when the remote node name is not in the topological database. The reason plcAttributesNotMet is issued when there is no network connectivity at a level specified by the PLC attributes. This reason is also issued when there is no physical connectivity between two end nodes.

What is mscDclVsLCoReasonForNoRoute?

The reason the most recent route selection attempt for this connection failed, e.g. unknownDestinationName(3), routeCostTooMuch(9), routesDelayTooLong(10), or attributesNotMet(11) (no connectivity meeting the PLC's required attributes), defaulting to none(0) when there's no failure to report. Gives an admin a specific, actionable reason when a connection can't establish a path, rather than just a generic failure.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.562.36.2.1.130.4.3.10.1.20
snmpwalk -v2c -c public <target> Nortel-MsCarrier-MscPassport-DcmeMIB::mscDclVsLCoReasonForNoRoute

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.562.36.2.1.130.4.3.10.1.20.1
snmpget -v2c -c public <target> Nortel-MsCarrier-MscPassport-DcmeMIB::mscDclVsLCoReasonForNoRoute.1

Start monitoring Nortel MSC Passport mobile carrier switch (DCME voice compression trunk) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Nortel-MsCarrier-MscPassport-DcmeMIB::mscDclVsLCoReasonForNoRoute OID value, configure state conditions and alerts, and monitor any Nortel MSC Passport mobile carrier switch (DCME voice compression trunk) from a single console.

OID Breakdown

Upper-level ancestors (10 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.562nortelCPM-NORTEL-MIB
1.3.6.1.4.1.562.36msCarrierNortel-MsCarrier-MscPassport-UsefulDefinitionsMIB
1.3.6.1.4.1.562.36.2mscPassportNortel-MsCarrier-MscPassport-UsefulDefinitionsMIB
1.3.6.1.4.1.562.36.2.1mscComponentsNortel-MsCarrier-MscPassport-UsefulDefinitionsMIB
Numeric OIDNameModule
1.3.6.1.4.1.562.36.2.1.130mscDclNortel-MsCarrier-MscPassport-DcmeMIB
1.3.6.1.4.1.562.36.2.1.130.4mscDclVsNortel-MsCarrier-MscPassport-DcmeMIB
1.3.6.1.4.1.562.36.2.1.130.4.3mscDclVsLCoNortel-MsCarrier-MscPassport-DcmeMIB
1.3.6.1.4.1.562.36.2.1.130.4.3.10mscDclVsLCoPathDataTableNortel-MsCarrier-MscPassport-DcmeMIB
1.3.6.1.4.1.562.36.2.1.130.4.3.10.1mscDclVsLCoPathDataEntryNortel-MsCarrier-MscPassport-DcmeMIB
1.3.6.1.4.1.562.36.2.1.130.4.3.10.1.20mscDclVsLCoReasonForNoRouteNortel-MsCarrier-MscPassport-DcmeMIB