All MIBs › LLDPPRIVATE-MIB
Organization: admin Inc.
Last Updated: 2006-07-27
Category: LAN Management
Description: Extends LLDP with vendor-specific TLVs for enhanced neighbor discovery.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is LLDPPRIVATE-MIB?
LLDPPRIVATE-MIB is a vendor-specific extension to the standard IEEE 802.1AB LLDP MIB, adding proprietary TLVs to enhance neighbor discovery beyond what the base LLDP-MIB provides; the specific vendor is not identifiable from the available data, as this pattern of a 'private LLDP' extension appears across multiple switch vendors. Based on the one sampled object, lldpAdminStatus, it at minimum tracks whether LLDP (and its private extensions) is administratively enabled on the device or a given port. Its monitoring value, in line with LLDP's purpose generally, is neighbor-discovery/topology status: confirming LLDP is active so connected-device information (and any vendor-specific TLV data layered on top) can be discovered and validated, which helps detect cabling or topology mismatches. It has a direct and explicit dependency on the standard IEEE 802.1AB LLDP-MIB, since it extends that base module's framework with additional private TLVs rather than replacing it. It would be deployed on managed switches wherever LLDP-based neighbor discovery is used for topology mapping or IP telephony/PoE device identification, making this LLDPPRIVATE-MIB reference useful whenever a vendor's private LLDP TLVs need to be identified alongside the standard neighbor table.
IPNetwork Monitor allows you to monitor SNMP objects defined in LLDPPRIVATE-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- managed Ethernet switch (vendor-specific LLDP extension, specific vendor unknown from available data)
Monitoring Examples
An administrator would poll lldpAdminStatus to confirm LLDP is enabled (transmit, receive, or both) on the device before relying on neighbor-discovery data; a value indicating LLDP is disabled on a port that should be participating in topology discovery would explain why an expected neighbor isn't appearing in the standard LLDP-MIB's remote-systems table. Beyond this single sampled object, the module's private TLV-specific tables were not included in the sample, so further detail can't be given honestly here.
What Can Be Monitored
- LLDP administrative status (enabled/disabled)
Imported Objects
From ADMIN-MASTER-MIB
| gbnL2 | OBJECT-IDENTITY |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Counter32 | |
| Integer32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| TimeTicks |
OIDs
RFC description
LLDP private module MIB for Link Layer Discovery Protocol configuration management.
Start monitoring Managed Ethernet switch (vendor-specific LLDP extension, vendor unidentified) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.