CISCO-DS0BUNDLE-EXT-MIB :: cdsx0BundleExtEncapType

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-DS0BUNDLE-EXT-MIB › cdsx0BundleExtEncapType

cdsx0BundleExtEncapType

Module: CISCO-DS0BUNDLE-EXT-MIB

OID (symbolic): CISCO-DS0BUNDLE-EXT-MIB::cdsx0BundleExtEncapType

OID (numeric): 1.3.6.1.4.1.9.10.33.1.1.1.1.3

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: The type of encapsulation for this bundle. A ds0 bundle is a logical serial port. Setting this object defines the type of the serial port.

If not specified, the value is none(1), indicating that the encapsulation type on this serial port is not defined.

If the value is changed to atmFuni(2), the agent will create an entry in the ifTable with ifType equal to atmFuni(106). If the value is changed to frameRelay(3), the agent will create an entry in the ifTable with ifType equal to frameRelayService(44).

The new atmFuni or frameRelayService interface is layered on top of the ds0 bundle interface. This layering will be represented in the ifStackTable.

The value of this object can be changed only if the ifOperStatus of the associated atmFuni or frameRelayService interface is down.

When the value is changed, the agent removes all existing connections on the interface, and also deletes the ifEntry that was created because of the previous value.

What is cdsx0BundleExtEncapType?

This object sets the Layer 2 encapsulation type used on this DS0 bundle's logical serial port, either none, ATM FUNI, or Frame Relay. The encapsulation choice determines how the router formats and interprets frames on this bundle, and per the description, changing it to atmFuni(2) causes the agent to create a corresponding ifTable entry with an ATM-FUNI interface type, meaning this single setting actually changes what kind of logical interface exists on top of the bundle. An admin migrating a fractional T1 circuit from legacy Frame Relay to ATM FUNI encapsulation would change this object to atmFuni(2), which would then cause a new ATM-type interface entry to appear that needs its own ATM-specific configuration.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.10.33.1.1.1.1.3
snmpwalk -v2c -c public <target> CISCO-DS0BUNDLE-EXT-MIB::cdsx0BundleExtEncapType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.10.33.1.1.1.1.3.1
snmpget -v2c -c public <target> CISCO-DS0BUNDLE-EXT-MIB::cdsx0BundleExtEncapType.1

Set instance 1 (SNMPv2c):

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

Start monitoring Cisco routers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-DS0BUNDLE-EXT-MIB::cdsx0BundleExtEncapType OID value, configure state conditions and alerts, and monitor any Cisco routers from a single console.

OID Breakdown

Upper-level ancestors (8 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.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.10ciscoExperimentCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.10.33ciscoDs0BundleExtMIBCISCO-DS0BUNDLE-EXT-MIB
1.3.6.1.4.1.9.10.33.1ciscoDs0BundleExtMIBObjectsCISCO-DS0BUNDLE-EXT-MIB
1.3.6.1.4.1.9.10.33.1.1cdsx0BundleConfigCISCO-DS0BUNDLE-EXT-MIB
1.3.6.1.4.1.9.10.33.1.1.1cdsx0BundleExtTableCISCO-DS0BUNDLE-EXT-MIB
1.3.6.1.4.1.9.10.33.1.1.1.1cdsx0BundleExtEntryCISCO-DS0BUNDLE-EXT-MIB
1.3.6.1.4.1.9.10.33.1.1.1.1.3cdsx0BundleExtEncapTypeCISCO-DS0BUNDLE-EXT-MIB