All MIBs › IBM-LES-BUS-MIB › use2ControlDistributeVccs
use2ControlDistributeVccs
Module: IBM-LES-BUS-MIB
OID (symbolic): IBM-LES-BUS-MIB::use2ControlDistributeVccs
OID (numeric): 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.6
Node type: OBJECT-TYPE
Type: TruthValue
Access: read-write
Description: When TRUE, proxy clients are placed on one Point-to-Multipoint Control Distribute VCC and all other clients are placed on another Point-to-Multipoint Control Distribute VCC. When FALSE, all clients are placed on a single Point-to-Multipoint Control Distribute VCC. The advantage of using two Control Distribute VCCs is that non-proxy clients are not perturbed by LE_ARP_REQUESTs for unregistered LAN Destinations (the LES answers LE_ARP_REQUESTs for registered LAN Destinations). The disadvantage is that Control Frames destined for all clients (LE_TOPOLOGY_REQUEST, LE_NARP_REQUEST, and possibly LE_ARP_RESPONSE depending upon LES-BUS-12) must be transmitted on 2 VCCs (as a related aside, note that LE_FLUSH_RESPONSEs are sent solely to the originator of the corresponding LE_FLUSH_REQUEST over the Control Direct VCC to that client).
What is use2ControlDistributeVccs?
When true, proxy clients are split onto their own Point-to-Multipoint Control Distribute VCC separate from other clients, so non-proxy clients aren't bothered by LE_ARP_REQUESTs for unregistered destinations, at the cost of the LES having to transmit some control frames on two VCCs instead of one.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.6 snmpwalk -v2c -c public <target> IBM-LES-BUS-MIB::use2ControlDistributeVccs
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.6.1 snmpget -v2c -c public <target> IBM-LES-BUS-MIB::use2ControlDistributeVccs.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.6.1 s <value>
Start monitoring IBM ATM switch/router with LES/BUS (LAN Emulation) support with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the IBM-LES-BUS-MIB::use2ControlDistributeVccs OID value, configure state conditions and alerts, and monitor any IBM ATM switch/router with LES/BUS (LAN Emulation) support 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.2 | ibm | ATM-ADAPTER-MIB |
| 1.3.6.1.4.1.2.6 | ibmProd | ATM-ADAPTER-MIB |
| 1.3.6.1.4.1.2.6.118 | nwaysMSS | FECLIENT827x-MIB |
| 1.3.6.1.4.1.2.6.118.1 | mssCommon | NWAYSMSS-MIB |
| 1.3.6.1.4.1.2.6.118.1.2 | mssCmnSrvrs | NWAYSMSS-MIB |
| 1.3.6.1.4.1.2.6.118.1.2.1 | mssServerLanE | NWAYSMSS-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.2.6.118.1.2.1.1 | ibmLesBusMIB | IBM-LES-BUS-MIB |
| 1.3.6.1.4.1.2.6.118.1.2.1.1.1 | ibmLesBusConfGroup | IBM-LES-BUS-MIB |
| 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1 | ibmLesBusConfTable | IBM-LES-BUS-MIB |
| 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1 | ibmLesBusConfEntry | IBM-LES-BUS-MIB |
| 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.6 | use2ControlDistributeVccs | IBM-LES-BUS-MIB |