CPIWF-MIB :: isdnBriPortTestType

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCPIWF-MIBisdnBriPortTestType

isdnBriPortTestType

Module: CPIWF-MIB

OID (symbolic): CPIWF-MIB::isdnBriPortTestType

OID (numeric): 1.3.6.1.4.1.353.5.10.1.1.4.1.7

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: This object is used to specify the type of test to run for ISDN-BRI ports. There are no results stored locally for a loopback test. Loopback of the whole ISDN-BRI physical user port is supported where all the D, B1 and B2 channels are looped back simultaneously, along with individual loopback of the D, B1 and B2 channels. AAL2 Loopback is also supported on a per sub-channel basis. In order to run these tests, the CO-IWF must first set the value of this object appropriate to the test that needs to be run. The CO-IWF should then set the value of ifAdminStatus in the corresponding ifEntry to 'testing'. The CO-IWF should verify that the test is in progress by checking that the value of ifOperStatus in the corresponding ifEntry is equal to 'testing'. Once testing is complete the CO-IWF must set the ifAdminStatus to a value other than 'testing'. Note that the LES device must not allow a CO-IWF to manipulate the ifAdminStatus of physical user ports that do not belong to its managed CP-IWF.

What is isdnBriPortTestType?

This read-write enumerated value specifies which loopback test to run on an ISDN BRI port, including a whole-port loopback covering D, B1, and B2 channels simultaneously, or individual loopbacks per channel, as well as AAL2 loopback on a per-sub-channel basis. It gives an admin a granular way to isolate a fault to a specific channel within the ISDN port rather than testing the whole port at once. Running a b1ChannelPhysicalPortLoopback(3) test in isolation would let the admin confirm whether a reported problem is specific to the B1 channel rather than affecting the whole ISDN BRI port.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.353.5.10.1.1.4.1.7
snmpwalk -v2c -c public <target> CPIWF-MIB::isdnBriPortTestType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.353.5.10.1.1.4.1.7.1
snmpget -v2c -c public <target> CPIWF-MIB::isdnBriPortTestType.1

Set instance 1 (SNMPv2c):

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

Start monitoring ATM access/carrier equipment (Loop Emulation Service CP-IWF) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CPIWF-MIB::isdnBriPortTestType OID value, configure state conditions and alerts, and monitor any ATM access/carrier equipment (Loop Emulation Service CP-IWF) 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.353atmForumATM-FORUM-ILMI40-MIB
1.3.6.1.4.1.353.5atmForumNetworkManagementATM-FORUM-SNMP-M4-MIB
Numeric OIDNameModule
1.3.6.1.4.1.353.5.10atmfLoopEmulationServiceCPIWF-MIB
1.3.6.1.4.1.353.5.10.1cpIwfMIBCPIWF-MIB
1.3.6.1.4.1.353.5.10.1.1cpIwfMIBObjectsCPIWF-MIB
1.3.6.1.4.1.353.5.10.1.1.4cpIwfIsdnBriPortTableCPIWF-MIB
1.3.6.1.4.1.353.5.10.1.1.4.1cpIwfIsdnBriPortEntryCPIWF-MIB
1.3.6.1.4.1.353.5.10.1.1.4.1.7isdnBriPortTestTypeCPIWF-MIB