Nortel-MsCarrier-MscPassport-VncsCallServerMIB :: mscVncsVpRequiredTrafficType

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsNortel-MsCarrier-MscPassport-VncsCallServerMIBmscVncsVpRequiredTrafficType

mscVncsVpRequiredTrafficType

Module: Nortel-MsCarrier-MscPassport-VncsCallServerMIB

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

OID (numeric): 1.3.6.1.4.1.562.36.2.1.44.3.2.1.6

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This attribute specifies the type of traffic transmitted over the path. There are eight possible traffic types, and the path can transmit only one of them. The originating end of the connection determines the type. These are arbitrary designations for traffic type. The voice, data and video traffic types are defined, and five other arbitrary traffic types can be defined by the network administration. This attribute is used in the route selection process to restrict the route to trunks that support this traffic type. The supportedTrafficType trunk attribute lists all the types of traffic allowed on the trunk. For example, if requiredTrafficType is specified as trafficType1, then only trunks that include trafficType1 in supportedTrafficType will be candidates for this connection.

What is mscVncsVpRequiredTrafficType?

Selects which of eight traffic-type designations (voice, data, video, or five network-defined types) calls on this voice profile carry, defaulting to voice. The route selection process restricts eligible trunks to those whose supportedTrafficType attribute includes this value, so an admin uses the custom trafficType1-5 slots to segregate specialized traffic onto matching trunks.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.562.36.2.1.44.3.2.1.6
snmpwalk -v2c -c public <target> Nortel-MsCarrier-MscPassport-VncsCallServerMIB::mscVncsVpRequiredTrafficType

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.6.1
snmpget -v2c -c public <target> Nortel-MsCarrier-MscPassport-VncsCallServerMIB::mscVncsVpRequiredTrafficType.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.562.36.2.1.44.3.2.1.6.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::mscVncsVpRequiredTrafficType 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.6mscVncsVpRequiredTrafficTypeNortel-MsCarrier-MscPassport-VncsCallServerMIB