All MIBs › CISCO-WAN-AXIPOP-MIB › bbChanTestType
bbChanTestType
Module: CISCO-WAN-AXIPOP-MIB
OID (symbolic): CISCO-WAN-AXIPOP-MIB::bbChanTestType
OID (numeric): 1.3.6.1.4.1.351.110.5.2.7.1.1.1.40
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: 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 chanTestResult 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
tstconseg is performed on the port side, i.e, towards the CPE
What is bbChanTestType?
This read-write control initiates an active on-demand test on this connection by writing testcon(1) for a continuity test or testdelay(2) for a round-trip delay test, requiring the far end to be an AXIS or ASI card on a BPX switch that loops the test cells back; writing notest(3) is the idle default state. It's a diagnostic tool an admin invokes directly against a live connection to verify it's actually passing traffic end-to-end, distinct from passive counters. An admin suspecting a specific PVC is silently broken would set bbChanTestType to testcon(1) and then check bbChanTestState for a pass or fail result within a couple of seconds.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.351.110.5.2.7.1.1.1.40 snmpwalk -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::bbChanTestType
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.351.110.5.2.7.1.1.1.40.1 snmpget -v2c -c public <target> CISCO-WAN-AXIPOP-MIB::bbChanTestType.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.351.110.5.2.7.1.1.1.40.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::bbChanTestType 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 (12 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.2 | atm | BASIS-MIB |
| 1.3.6.1.4.1.351.110.5.2.7 | bbChan | BASIS-MIB |
| 1.3.6.1.4.1.351.110.5.2.7.1 | bbChanCnfGrp | BASIS-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.351.110.5.2.7.1.1 | bbChanCnfGrpTable | CISCO-WAN-AXIPOP-MIB |
| 1.3.6.1.4.1.351.110.5.2.7.1.1.1 | bbChanCnfGrpEntry | CISCO-WAN-AXIPOP-MIB |
| 1.3.6.1.4.1.351.110.5.2.7.1.1.1.40 | bbChanTestType | CISCO-WAN-AXIPOP-MIB |