LLDP-MIB Table View

The table that controls LLDP frame transmission on individual
ports.

The table that controls selection of LLDP management address
TLV instances to be transmitted on individual ports.

A table containing LLDP transmission statistics for
individual ports.  Entries are not required to exist in
this table while the lldpPortConfigEntry object is equal to
'disabled(4)'.

A table containing LLDP reception statistics for individual
ports.  Entries are not required to exist in this table while
the lldpPortConfigEntry object is equal to 'disabled(4)'.

This table contains one or more rows per port information
associated with the local system known to this agent.

This table contains management address information on the
local system known to this agent.

This table contains one or more rows per physical network
connection known to this agent.  The agent may wish to ensure
that only one lldpRemEntry is present for each local port,
or it may choose to maintain multiple lldpRemEntries for
the same local port.
          
The following procedure may be used to retrieve remote
systems information updates from an LLDP agent:
          
   1. NMS polls all tables associated with remote systems
      and keeps a local copy of the information retrieved.
      NMS polls periodically the values of the following
      objects:
         a. lldpStatsRemTablesInserts
         b. lldpStatsRemTablesDeletes
         c. lldpStatsRemTablesDrops
         d. lldpStatsRemTablesAgeouts
         e. lldpStatsRxPortAgeoutsTotal for all ports.
          
   2. LLDP agent updates remote systems MIB objects, and
      sends out notifications to a list of notification
      destinations.
          
   3. NMS receives the notifications and compares the new
      values of objects listed in step 1.  
          
      Periodically, NMS should poll the object
      lldpStatsRemTablesLastChangeTime to find out if anything
      has changed since the last poll.  if something has
      changed, NMS will poll the objects listed in step 1 to
      figure out what kind of changes occurred in the tables.
          
      if value of lldpStatsRemTablesInserts has changed,
      then NMS will walk all tables by employing TimeFilter
      with the last-polled time value.  This request will
      return new objects or objects whose values are updated
      since the last poll.
          
      if value of lldpStatsRemTablesAgeouts has changed,
      then NMS will walk the lldpStatsRxPortAgeoutsTotal and
      compare the new values with previously recorded ones.
      For ports whose lldpStatsRxPortAgeoutsTotal value is
      greater than the recorded value, NMS will have to
      retrieve objects associated with those ports from
      table(s) without employing a TimeFilter (which is
      performed by specifying 0 for the TimeFilter.)
          
      lldpStatsRemTablesDeletes and lldpStatsRemTablesDrops
      objects are provided for informational purposes.

This table contains one or more rows per management address
information on the remote system learned on a particular port
contained in the local chassis known to this agent.

This table contains information about an incoming TLV which
is not recognized by the receiving LLDP agent.  The TLV may
be from a later version of the basic management set.
          
This table should only contain TLVs that are found in
a single LLDP frame.  Entries in this table, associated
with an MAC service access point (MSAP, the access point
for MAC services provided to the LCC sublayer, defined
in IEEE 100, which is also identified with a particular
lldpRemLocalPortNum, lldpRemIndex pair) are overwritten with
most recently received unrecognized TLV from the same MSAP,
or they will naturally age out when the rxInfoTTL timer
(associated with the MSAP) expires.

This table contains one or more rows per physical network
connection which advertises the organizationally defined
information.
          
Note that this table contains one or more rows of
organizationally defined information that is not recognized
by the local agent.
          
If the local system is capable of recognizing any
organizationally defined information, appropriate extension
MIBs from the organization should be used for information
retrieval.