Information gathered
Information gathered with LLDP can be stored in the device management information base (MIB) and queried with the Simple Network Management Protocol (SNMP) as specified inApplications
The Link Layer Discovery Protocol may be used as a component in network management and network monitoring applications. One such example is its use in data center bridging requirements. The (DCBX) is a discovery and capability exchange protocol that is used for conveying capabilities and configuration of the above features between neighbors to ensure consistent configuration across the network. LLDP is used to advertise power over Ethernet capabilities and requirements and negotiate power delivery.Media endpoint discovery extension
''Media Endpoint Discovery'' is an enhancement of LLDP, known as LLDP-MED, that provides the following facilities: * Auto-discovery of LAN policies (such as VLAN, Layer 2 Priority and Differentiated services (Diffserv) settings) enabling plug and play networking. * Device location discovery to allow creation of location databases and, in the case of Voice over Internet Protocol (VoIP), Enhanced 911 services. * Extended and automated power management of Power over Ethernet (PoE) end points. * Inventory management, allowing network administrators to track their network devices, and determine their characteristics (manufacturer, software and hardware versions, serial or asset number). The LLDP-MED protocol extension was formally approved and published as the standard ANSI/TIA-1057 by the Telecommunications Industry Association (TIA) in April 2006.System Capability Codes
Frame structure
LLDP information is sent by devices from each of their interfaces at a fixed interval, in the form of an Ethernet frame. Each frame contains one LLDP Data Unit (LLDPDU). Each LLDPDU is a sequence of type–length–value (TLV) structures. The Ethernet frame used in LLDP typically has its destination MAC address set to a special multicast address that 802.1D-compliant bridges do not forward. Other multicast and unicast destination addresses are permitted. The EtherType field is set to 0x88cc. Each LLDP frame starts with the following mandatory TLVs: ''Chassis ID'', ''Port ID'', and ''Time-to-Live''. The mandatory TLVs are followed by any number of optional TLVs. The frame optionally ends with a special TLV, named ''end of LLDPDU'' in which both the ''type'' and ''length'' fields are 0.IEEE 802.1AB-2016 chapter 8.4 Accordingly, an Ethernet frame containing an LLDPDU has the following structure: Each of the TLV components has the following basic structure: Custom TLVsTermed ''Organizationally Specific TLVs'' by IEEE 802.1AB are supported via a TLV type 127. The value of a custom TLV starts with a 24-bit organizationally unique identifier and a 1 byte organizationally specific subtype followed by data. The basic format for an organizationally specific TLV is shown below: According to IEEE Std 802.1AB, §9.6.1.3, "The Organizationally Unique Identifier shall contain the organization's OUI as defined in IEEE Std 802-2001." Each organization is responsible for managing their subtypes.Notes
References
{{reflistExternal links