CISCO-WAN-AXIPOP-MIB :: cesConnServiceType

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-WAN-AXIPOP-MIBcesConnServiceType

cesConnServiceType

Module: CISCO-WAN-AXIPOP-MIB

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

OID (numeric): 1.3.6.1.4.1.351.110.5.3.2.1.1.1.35

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This specifies the service type 1 ==> Constant Bit Rate 2 ==> Variable Bit Rate 3 ==> Not used 4 ==> Unspecified Bit Rate 5 ==> ATM frame relay 6 ==> standard ABR 7 ==> foresight ABR Note that this is used by PXM card, SV+ doesn't need to set it, if not set in the connection setup request, it'll be defaulted to CBR type for CESM. Also to make it compatible with existing AUSM MIB definition, value 3 is not used.

The following types are being added for PNNI support and are based on UNI 4.0. cbr1 (21) - CBR.1 vbr1rt (22) - Real time VBR.1 vbr2rt (23) - Real time VBR.2 vbr3rt (24) - Real time VBR.3 vbr1nrt(25) - Non Real time VBR.1 vbr2nrt(26) - Non Real time VBR.2 vbr3nrt(27) - Non Real time VBR.3 ubr1 (28) - UBR.1 ubr2 (29) - UBR.2 stdabr (30) - TM 4.0 compliant standard ABR cbr2 (31) - CBR.2 cbr3 (32) - CBR.3

Note that for CESM, the only valid connection type for PNNI support is cbr1(21). Other enumerations have been added for the sake of consistency across Narrow-Band service modules.

What is cesConnServiceType?

This read-write value specifies the ATM service category, such as Constant Bit Rate, Variable Bit Rate, Unspecified Bit Rate, ATM frame relay, or one of the ABR variants, that PXM uses when routing and provisioning this connection, defaulting to CBR if left unset for a CESM channel. An administrator generally leaves this at its CBR default for circuit-emulation channels, since CES traffic is inherently constant-bit-rate by nature, only overriding it in unusual provisioning scenarios. For example, an unset cesConnServiceType on a new CESM connection is automatically treated as cbr(1) by PXM without the operator needing to configure it explicitly.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.5.3.2.1.1.1.35
snmpwalk -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::cesConnServiceType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.351.110.5.3.2.1.1.1.35.1
snmpget -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::cesConnServiceType.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.351.110.5.3.2.1.1.1.35.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::cesConnServiceType 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.3circuitEmulationBASIS-MIB
1.3.6.1.4.1.351.110.5.3.2cesmChanBASIS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.351.110.5.3.2.1cesmChanCnfGrpCISCO-WAN-AXIPOP-MIB
1.3.6.1.4.1.351.110.5.3.2.1.1cesmChanCnfGrpTableCISCO-WAN-AXIPOP-MIB
1.3.6.1.4.1.351.110.5.3.2.1.1.1cesmChanCnfGrpEntryCISCO-WAN-AXIPOP-MIB
1.3.6.1.4.1.351.110.5.3.2.1.1.1.35cesConnServiceTypeCISCO-WAN-AXIPOP-MIB