CISCO-WAN-AXIPOP-MIB :: chanServType

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-WAN-AXIPOP-MIBchanServType

chanServType

Module: CISCO-WAN-AXIPOP-MIB

OID (symbolic): CISCO-WAN-AXIPOP-MIB::chanServType

OID (numeric): 1.3.6.1.4.1.351.110.5.1.2.1.1.1.55

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This indicates the class of the connection 1-High priority (typically CBR connections) 2- real-time VBR 3- non-real time VBR 4- Available Bit Rate 5- Unspecified Bit Rate 9- Standard ABR There are 8 queues actually but only 4 are currently being used (the 4 queues are for CBR, VBR-rt, , UBR traffic). This object is currently suuported only in FRSM-VHS and FRSM-8T1E1. For FRSM-8T1E1, a 0 indicates that the connections are of old model type where chanServType object is unused. Note that chanServType is not modifiable after a channel has been enabled For FRSM12 Card: The types aBR, queue6, queue7, queue8 are not supported

What is chanServType?

This read-write enumeration classifies the connection into a traffic class: highpriority(1, typically CBR), rtVBR(2), nrtVBR(3), aBR(4), uBR(5), or stdABR(9), among queue6-8 placeholders; although 8 queues exist, the description notes only 4 are actually used (for CBR, VBR-rt, VBR-nrt/ABR, and UBR traffic), and this object is currently supported only on FRSM-VHS and FRSM-8T1E1 cards. An administrator sets chanServType to place a connection into the correct service queue so it receives appropriate scheduling priority relative to other traffic classes on the same card. For example, a voice-sensitive connection on an FRSM-VHS card would be set to highpriority(1) to land in the CBR queue, while a bulk-data connection on the same card might be set to uBR(5) to share the lowest-priority queue.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.5.1.2.1.1.1.55
snmpwalk -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::chanServType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.351.110.5.1.2.1.1.1.55.1
snmpget -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::chanServType.1

Set instance 1 (SNMPv2c):

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

Start monitoring Cisco MGX 8000-series ATM WAN switches (AXIPOP processor, legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-WAN-AXIPOP-MIB::chanServType OID value, configure state conditions and alerts, and monitor any Cisco MGX 8000-series ATM WAN switches (AXIPOP processor, legacy) from a single console.

OID Breakdown

Upper-level ancestors (11 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.110basisBASIS-MIB
1.3.6.1.4.1.351.110.5basisServicesBASIS-MIB
1.3.6.1.4.1.351.110.5.1frameRelayBASIS-MIB
1.3.6.1.4.1.351.110.5.1.2frChanBASIS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.351.110.5.1.2.1frChanCnfGrpCISCO-WAN-AXIPOP-MIB
1.3.6.1.4.1.351.110.5.1.2.1.1frChanCnfGrpTableCISCO-WAN-AXIPOP-MIB
1.3.6.1.4.1.351.110.5.1.2.1.1.1frChanCnfGrpEntryCISCO-WAN-AXIPOP-MIB
1.3.6.1.4.1.351.110.5.1.2.1.1.1.55chanServTypeCISCO-WAN-AXIPOP-MIB