IBM-LES-BUS-MIB :: use2MulticastForwardVccs

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › IBM-LES-BUS-MIB › use2MulticastForwardVccs

use2MulticastForwardVccs

Module: IBM-LES-BUS-MIB

OID (symbolic): IBM-LES-BUS-MIB::use2MulticastForwardVccs

OID (numeric): 1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.7

Node type: OBJECT-TYPE

Type: TruthValue

Access: read-write

Description: When TRUE: - proxy clients are placed on one Point-to-Multipoint Multicast Forward VCC and all other clients are placed on another Point-to-Multipoint Multicast Forward VCC, - all 'unknown' unicast frames and all unicast frames for LAN Destinations registered by proxy clients are forwarded on the Proxy Multicast Forward VCC ('unknown' unicast frames are not forwarded to non-proxy clients), - all unicast frames for LAN Destinations registered by non-proxy clients are forwarded on the Multicast Send VCC to that client, and - multicast and broadcast frames are transmitted on both Multicast Forward VCCs. When FALSE: - all clients are placed on a single Point-to-Multipoint Multicast Forward VCC, and - the BUS functions as a simple forwarding device (efficient, but 'dumb') with respect to unicast frames. One advantage of enabling this option is a reduction in client pertubation due to 'nuisance' unicast frames (i.e., unicast frames not destined for the client); proxy clients do not receive unicast frames destined for non-proxy clients, and non-proxy clients never receive nuisance unicast frames. Another advantage is the reduction in network bandwidth devoted to nuisance frames. The potential disadvantage is that the increased processing requirements result in a degradation of overall system performance.

What is use2MulticastForwardVccs?

When true, proxy and non-proxy clients are placed on separate Multicast Forward VCCs so unicast frames meant for one group don't reach the other, cutting nuisance traffic and bandwidth use at the cost of extra BUS processing; when false, all clients share a single VCC and the BUS forwards more simply.

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.7
snmpwalk -v2c -c public <target> IBM-LES-BUS-MIB::use2MulticastForwardVccs

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.7.1
snmpget -v2c -c public <target> IBM-LES-BUS-MIB::use2MulticastForwardVccs.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.7.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::use2MulticastForwardVccs 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 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.2ibmATM-ADAPTER-MIB
1.3.6.1.4.1.2.6ibmProdATM-ADAPTER-MIB
1.3.6.1.4.1.2.6.118nwaysMSSFECLIENT827x-MIB
1.3.6.1.4.1.2.6.118.1mssCommonNWAYSMSS-MIB
1.3.6.1.4.1.2.6.118.1.2mssCmnSrvrsNWAYSMSS-MIB
1.3.6.1.4.1.2.6.118.1.2.1mssServerLanENWAYSMSS-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2.6.118.1.2.1.1ibmLesBusMIBIBM-LES-BUS-MIB
1.3.6.1.4.1.2.6.118.1.2.1.1.1ibmLesBusConfGroupIBM-LES-BUS-MIB
1.3.6.1.4.1.2.6.118.1.2.1.1.1.1ibmLesBusConfTableIBM-LES-BUS-MIB
1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1ibmLesBusConfEntryIBM-LES-BUS-MIB
1.3.6.1.4.1.2.6.118.1.2.1.1.1.1.1.7use2MulticastForwardVccsIBM-LES-BUS-MIB