All MIBs › CISCO-WAN-AXIPOP-MIB › chanTestType
chanTestType
Module: CISCO-WAN-AXIPOP-MIB
OID (symbolic): CISCO-WAN-AXIPOP-MIB::chanTestType
OID (numeric): 1.3.6.1.4.1.351.110.5.1.2.1.1.1.22
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 chanTestType?
This read-write enumeration (testcon(1), testdelay(2), notest(3), default notest) starts a continuity or delay test on a connection by sending specific cell patterns toward the network, which the receiving node (an AXIS or ASI on a BPX) must loop back, with the test completing in about a couple of seconds. An administrator uses testcon to confirm the connection is intact end-to-end and testdelay to additionally measure round-trip timing, both requiring a compatible terminating device. For example, an engineer suspecting a connection to a BPX is down would set chanTestType to testcon and then check chanTestState for the pass/fail result a couple of seconds later.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.5.1.2.1.1.1.22 snmpwalk -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::chanTestType
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.22.1 snmpget -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::chanTestType.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.351.110.5.1.2.1.1.1.22.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::chanTestType 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 OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.351 | stratacom | CISCOWAN-SMI |
| 1.3.6.1.4.1.351.110 | basis | BASIS-MIB |
| 1.3.6.1.4.1.351.110.5 | basisServices | BASIS-MIB |
| 1.3.6.1.4.1.351.110.5.1 | frameRelay | BASIS-MIB |
| 1.3.6.1.4.1.351.110.5.1.2 | frChan | BASIS-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.351.110.5.1.2.1 | frChanCnfGrp | CISCO-WAN-AXIPOP-MIB |
| 1.3.6.1.4.1.351.110.5.1.2.1.1 | frChanCnfGrpTable | CISCO-WAN-AXIPOP-MIB |
| 1.3.6.1.4.1.351.110.5.1.2.1.1.1 | frChanCnfGrpEntry | CISCO-WAN-AXIPOP-MIB |
| 1.3.6.1.4.1.351.110.5.1.2.1.1.1.22 | chanTestType | CISCO-WAN-AXIPOP-MIB |