A (conceptual) table representing all the instantiations
of BUSs on the designated device. This table may or may not
allow the creation of rows depending on whether the LANE
service elements allow the separate creation of LES and BUS
components. In the event that separate components are not
allowed then the MINIMUM-ACCESS detailed in the
MODULE-COMPLIANCE should be used by those BUS implementations
A unique identifier for this particular BUS on this
ELAN. This value must remain constant while the entry
is in existence and during the operation of the agent
(i.e. It is allowed to change after reboot). For
implementations that do not support more than one BUS
entity per ELAN per device, it is sufficient to always
report 1 for this object and only to accept the value
1 for row creation.
The specified ATM address of the BUS on the interface
of interest. Note that setting this object will have
the side effect of reinitializing the BUS and
consequently dropping all clients connected to it. If
this object is not specified at row creation time then
the BUS will choose a value for itself and attempt to
register with the switch with that value. If an
address is specified which is not acceptable to the
switch then the busOperStatus will remain inactive
until an acceptable address is set.
An address mask that when used with the
busAtmAddrSpec, specifies the portion of the BUS' ATM
address that is desired to be configured. Note that
setting this object will result in the
reinitialization of the BUS, consequently dropping all
clients connected to it. At row creation time this
object cannot be set without also supplying a value
for the busAtmAddrSpec. If the BUS ATM address is
omitted at creation time then this object defaults to
the value of all zeros (none of the busAtmAddrSpec
value is relevant). If the BUS ATM address is
specified at creation time but this object omitted,
then this object defaults to the value of all ones
(all of the busAtmAddrSpec is relevant).
The interface that a BUS will forward traffic over.
The value specified for this object must equate to a
value of ifIndex in the ifTable. The interface will
be for that particular ATM port (the physical
interface, not a logical layer on top of it). This
object can only be specified upon row creation and
cannot be altered there after.
Specifies the sub-interface number that the BUS
will reside on. This sub-interface may be shared with
a LEC or BUS of the same ELAN but is not required to
do so. If no value is specified for this object at
row creation time, then a sub-interface will be chosen
by the agent. This object may only be specified at
row creation time and cannot be altered thereafter.
This object reflects the actual state of the BUS
which may differ from that of the busAdminStatus
object. This can occur when the interface
ifOperStatus is 'down' but the corresponding
busAdminStatus is 'active'.
The status of the BUS entry. This object cannot be
set to active until the busIfIndex object has an
appropiate value. Note that implementations that
do not support separate LES/BUS entities may
refuse row creation in this table. Creation of
BUS entities for those implementation is facilitated
in the LES MIB.
A (conceptual) table listing the clients associated
with a BUS. Note that the local or network management
will not create or destroy rows in this table but
may only inspect what LECs are currently joined
with the BUS.
A unique identifier for a LEC which is establishing/
has-established a multicast send VC to the BUS. The
identifier only persists for as long as the LEC is
associated with this particular BUS. If the LEC is
dropped and rejoins the ELAN then a new identifier may
be attributed to it.
Those implementations that do not support separately
configured broadcast/unknown and LAN emulation servers
are not required to provide write access to the
busAdminStatus object. The BUS's administrative status
should be controlled via access to the lesAdminStatus.
Refer to CISCO-LES-MIB for details.