Nortel-MsCarrier-MscPassport-VncsCallServerMIB :: mscVncsVpMaximumAcceptableDelay

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsNortel-MsCarrier-MscPassport-VncsCallServerMIBmscVncsVpMaximumAcceptableDelay

mscVncsVpMaximumAcceptableDelay

Module: Nortel-MsCarrier-MscPassport-VncsCallServerMIB

OID (symbolic): Nortel-MsCarrier-MscPassport-VncsCallServerMIB::mscVncsVpMaximumAcceptableDelay

OID (numeric): 1.3.6.1.4.1.562.36.2.1.44.3.2.1.12

Node type: OBJECT-TYPE

Type: Unsigned32

Access: read-write

Description: This attribute specifies an upper bound on the delay of a route, which is the sum of the delays of all trunks on the route. It should be provisioned with a reasonable maximum acceptable delay for the end to end one way delay of a 512-byte packet. Remember, that the trunk during its staging measures a measuredRoundTripDelay. This delay is divided by two and truncated to an integer number of milliseconds to provide a one way delay which is used to populate the delay in this trunk object in the topological database. The value includes emission, propagation, and queuing delays. A 512-byte packet is used to perform the measurement. If for any trunk the half of the trunk's measuredRoundTripDelay is larger than the maximumAcceptableDelay, then that trunk is not considered during the route selection. While a shortest route is being selected, the route delay is being compared with the maximumAcceptableDelay attribute, and this is done for any minimization criterion. No route is selected if the delay metric of the shortest route is larger than the maximumAcceptableDelay.

What is mscVncsVpMaximumAcceptableDelay?

Sets an upper bound, in milliseconds (0-100000, default 100000), on the total one-way trunk delay a route using this voice profile may have, based on each trunk's measured round-trip delay divided by two; any trunk exceeding this is excluded from route selection. An admin lowers this for latency-sensitive voice traffic to avoid routes with unacceptable end-to-end delay.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.562.36.2.1.44.3.2.1.12
snmpwalk -v2c -c public <target> Nortel-MsCarrier-MscPassport-VncsCallServerMIB::mscVncsVpMaximumAcceptableDelay

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.562.36.2.1.44.3.2.1.12.1
snmpget -v2c -c public <target> Nortel-MsCarrier-MscPassport-VncsCallServerMIB::mscVncsVpMaximumAcceptableDelay.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.562.36.2.1.44.3.2.1.12.1 i <value>

Start monitoring Nortel Passport/MSC carrier switching platform (VNCS call server) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Nortel-MsCarrier-MscPassport-VncsCallServerMIB::mscVncsVpMaximumAcceptableDelay OID value, configure state conditions and alerts, and monitor any Nortel Passport/MSC carrier switching platform (VNCS call server) 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.562nortelNortel-Magellan-Passport-UsefulDefinitionsMIB
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.44mscVncsNortel-MsCarrier-MscPassport-VncsCallServerMIB
1.3.6.1.4.1.562.36.2.1.44.3mscVncsVpNortel-MsCarrier-MscPassport-VncsCallServerMIB
1.3.6.1.4.1.562.36.2.1.44.3.2mscVncsVpLCOpsTableNortel-MsCarrier-MscPassport-VncsCallServerMIB
1.3.6.1.4.1.562.36.2.1.44.3.2.1mscVncsVpLCOpsEntryNortel-MsCarrier-MscPassport-VncsCallServerMIB
1.3.6.1.4.1.562.36.2.1.44.3.2.1.12mscVncsVpMaximumAcceptableDelayNortel-MsCarrier-MscPassport-VncsCallServerMIB