802.1ab Link Layer Discovery Protocol
802.1ab Link Layer Discovery Protocol (LLDP) is a standard for discovering the physical topology
between neighboring devices. 802.1ab LLDP defines a standard method for Ethernet network
devices, such as switches, routers, and IP Deskphones to advertise information about themselves to
other nodes on the network and to store the information they discover in a Management Information
Base (MIB).
802.1ab (LLDP) takes advantage of the VLAN Name and Network Policy TLVs, and provides an
automatic configuration of the IP Deskphone network policy parameters. Key parameters, such as
VLAN ID, L2 priority, and DSCP values are received from the switch and are automatically
configured in the IP Deskphone.
802.1ab Link Layer Discovery Protocol (LLDP) provides the following functionality
• Periodic transmission of advertisements containing device information, device capabilities and
media specific configuration information to neighbors attached to the same network.
• Reception of LLDP advertisements from its neighbors.
• Implementation of behavioral requirements specified by Link Layer Discovery Protocol Media
Endpoint Discovery (LLDP-MED).
• Storage of received data in local data structures, for example, in MIB modules.
TLVs
The information fields in each MIB are contained in a Link Layer Discovery Protocol Data Unit
(LLDPDU) as a sequence of short, variable-length, information elements known as TLVs that each
include type, length, and value fields. Each LLDPDU includes several mandatory TLVs plus optional
TLVs. Optional TLVs may be inserted in any order.
The IP Deskphone supports both the transmit and receive LLDP mode.
Transmit direction:
An LLDPDU transmitted by the IP Deskphone supports the following TLVs:
1. Chassis ID
2. Port ID
3. Time To Live
4. End of LLDPPDU
5. Port Description
6. System Description
7. System Capabilities
8. Port VLAN ID
9. Port And Protocol VLAN ID
Device Settings on the IP Deskphone with SIP Software
148 SIP Software for Avaya 1200 Series IP Deskphones-Administration March 2015
Comments? infodev@avaya.com