Main page
OID Repository
https://oid-base.com
Display OID:

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 353 atmForumNetworkManagement(5) atmfLanEmulation(3) leClientMIB(1) leClientMIBObjects(1) lecTlvTable(13) lecTlvEntry(1) lecTlvSetIndex(1)}

lecTlvSetIndex(1)

 
 

OID description



 
OID: (ASN.1 notation)
(dot notation)
(OID-IRI notation)

Description:

lecTlvSetIndex OBJECT-TYPE
SYNTAX INTEGER {layer3Tlvs(1), actualRegTlvs(2), configRegTlvs(3), leArpTlvs(4), queryTlvs(5)}
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"An index which helps to identify a set of TLVs, and to
indicate their purpose.
The value of this index defines the interpretation and
use of corresponding table rows as follows:
layer3Tlvs(1)
-------------
This index provides access to Layer-3-Address
TLVs (Initial State variable C36) used during
the Initialization phase.
TLVs are stored in rows
( lecIndex, 1,
LAN_Destination( all '00's ),
* )
These rows may be read / created / written /
deleted.
actualRegTlvs(2)
----------------
This index provides access to TLVs which were
used to register LAN Destinations.
These TLVs are associated with entries in the
lecMacAddressTable and lecRouteDescrTable and
stored in rows
( lecIndex, 2,
LAN_Destination( lecMacAddress ),
* )
( lecIndex, 2,
LAN_Destination(
lecRouteDescrSegmentID,
lecRouteDescrBridgeNumber ),
* )
These rows may be read or deleted, but cannot
be created or modified. Most implementations
are expected to make them read-only.
Note that TLVs that have their own objects in
the associated tables SHOULD NOT appear here.
LLC-Muxed-ATM-Address & Service-Category TLVs
are two examples.
configRegTlvs(3)
----------------
This index provides a way to set registration
TLVs for unregistered LAN Destinations.
Hopefully this is not something that managers
will need to do a lot.
TLVs are stored in rows
( lecIndex, 3,
LAN_Destination( the_LAN_destination ),
* )
Note that the agent might restrict the set of
LAN Destinations and TLVs that it allows; for
instance, to screen out the 'V2 Capable' TLV.
leArpTlvs(4)
------------
This index provides access to TLVs associated
with the LE_ARP cache.
These TLVs are associated with leArpTable and
leRDArpTable, and stored in rows
( lecIndex, 4,
LAN_Destination( leArpMacAddress ),
* )
( lecIndex, 4,
LAN_Destination(
leRDArpSegmentID,
leRDArpBridgeNumber ),
* )
Agents may allow write/create access to TLVs
when the type of the associated LE_ARP entry
is 'staticVolatile', 'staticNonVolatile', or
'other'.
Note that TLVs that have their own objects in
the associated tables SHOULD NOT appear here.
LLC-Muxed-ATM-Address & Service-Category TLVs
are two examples.
queryTlvs(5)
------------
This index provides access to TLVs associated
with the last MAC Address or Route Descriptor
query.
TLVs are associated with lecMacQueryObjects &
lecRDQueryObjects, and stored in rows
( lecIndex, 5,
LAN_Destination( lecMacQueryAddress ),
* )
( lecIndex, 5,
LAN_Destination(
lecRDQuerySegmentID,
lecRDQueryBridgeNumber ),
* )
Note that TLVs that have their own objects in
the associated tables SHOULD NOT appear here.
LLC-Muxed-ATM-Address & Service-Category TLVs
are two examples.
Additional indices may be defined by the ATM Forum as
needed."



Classification:

Deprecated or obsolete OID

 
See classes of OIDs
 
 
Short link:


Parent OID: lecTlvEntry(1) Next sibling OID: lecTlvLanDestination(2) Last sibling OID: lecTlvRowStatus(6)