CISCO-WAN-AXIPOP-MIB :: ausmChanTestType

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-WAN-AXIPOP-MIBausmChanTestType

ausmChanTestType

Module: CISCO-WAN-AXIPOP-MIB

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

OID (numeric): 1.3.6.1.4.1.351.110.5.2.2.1.1.1.34

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: The default is notest. The chanTestType starts testing the continuity or delay of a connection. It sends specific cell patterns toward the network and the terminating end of this connection has to be an AXIS or ASI of a BPX in order for this test to be working. The receiving node would loop back when it receives these cells. The test should be done in about couple of seconds. The testcon tests the continuity of the connection and testdelay uses the same test except that it measures for delay through the network. To test the delay follow this procedure: a- set chanTestType to testdelay b- read chanTestState till it is Pass or Fail c- Read chanRTDResult for the delay if it is Pass *Note that the chanTestType would go back to notest when the test is completed To test the continuity follow this procedure: a- set chanTestType to testcon b- read chanTestState till it is Pass or Fail *Note that the chanTestType would go back to notest when the test is completed You CAN NOT select 2 tests back to back, you have selcelt one and wait the result and then start the other one. SYNTAX When you select testdelay

This is the type of the test 1 = Test Continuity 2 = Test Delay 3 = No Test

What is ausmChanTestType?

This read-write enumerated value initiates a connection test toward the network by sending specific OAM cell patterns that the terminating node (which must be an AXIS or an ASI on a BPX) loops back, defaulting to notest when idle; setting it to testcon checks basic continuity while testdelay performs the same test while also measuring round-trip delay. Admins use this to verify end-to-end connectivity of a specific PVC without needing to involve the customer, useful for pre-activation testing or fault isolation. For example, an admin verifying a newly provisioned PVC before handing it to a customer would set ausmChanTestType to testdelay, then check ausmChanTestState and ausmChanRTDResult for the outcome and measured round-trip time.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.5.2.2.1.1.1.34
snmpwalk -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::ausmChanTestType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.351.110.5.2.2.1.1.1.34.1
snmpget -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::ausmChanTestType.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.351.110.5.2.2.1.1.1.34.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::ausmChanTestType 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.2atmBASIS-MIB
1.3.6.1.4.1.351.110.5.2.2ausmChanBASIS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.351.110.5.2.2.1ausmChanCnfGrpCISCO-WAN-AXIPOP-MIB
1.3.6.1.4.1.351.110.5.2.2.1.1ausmChanCnfGrpTableCISCO-WAN-AXIPOP-MIB
1.3.6.1.4.1.351.110.5.2.2.1.1.1ausmChanCnfGrpEntryCISCO-WAN-AXIPOP-MIB
1.3.6.1.4.1.351.110.5.2.2.1.1.1.34ausmChanTestTypeCISCO-WAN-AXIPOP-MIB