TERAWAVE-teraCon-MIB :: requestedCONBW

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsTERAWAVE-teraCon-MIBrequestedCONBW

requestedCONBW

Module: TERAWAVE-teraCon-MIB

OID (symbolic): TERAWAVE-teraCon-MIB::requestedCONBW

OID (numeric): 1.3.6.1.4.1.4513.2.1.2.11

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

What is requestedCONBW?

This selects the requested bandwidth/circuit interface type for this connection: atm, vlan-c, t1, e1, ds3, e3, oc3, stm1, or atm-vpi. Admins set this to specify what kind of transport (e.g. a T1/E1 TDM line versus an OC3/STM1 optical circuit) the connection should be provisioned over.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4513.2.1.2.11
snmpwalk -v2c -c public <target> TERAWAVE-teraCon-MIB::requestedCONBW

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.4513.2.1.2.11.1
snmpget -v2c -c public <target> TERAWAVE-teraCon-MIB::requestedCONBW.1

Set instance 1 (SNMPv2c):

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

Start monitoring Terawave teraAccess DSL/ATM access platform (circuit-to-VPI/VCI provisioning status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TERAWAVE-teraCon-MIB::requestedCONBW OID value, configure state conditions and alerts, and monitor any Terawave teraAccess DSL/ATM access platform (circuit-to-VPI/VCI provisioning status) from a single console.

OID Breakdown

Upper-level ancestors (7 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.4513terawaveTERAWAVE-teraces-MIB
Numeric OIDNameModule
1.3.6.1.4.1.4513.2connectionsTERAWAVE-teraCon-MIB
1.3.6.1.4.1.4513.2.1conTableTERAWAVE-teraCon-MIB
1.3.6.1.4.1.4513.2.1.2conTableEntryTERAWAVE-teraCon-MIB
1.3.6.1.4.1.4513.2.1.2.11requestedCONBWTERAWAVE-teraCon-MIB