Link Layer Discovery Protocol (LLDP) - Extreme Networks
Link Layer Discovery Protocol (LLDP) - Extreme Networks
Link Layer Discovery Protocol (LLDP) - Extreme Networks
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Organizationally-Specific TLVs<br />
<strong>Extreme</strong> <strong>Networks</strong> implementation of organizationallyspecific<br />
TLVs represent a commitment to fully enabling the<br />
network for converged applications and provide level of<br />
functionality beyond that of most equipment vendors.<br />
Organizationally-specific TLV extensions simplify the<br />
integration of multi-vendor access networks by assisting in<br />
the detection and configuration of IEEE 802.1 and IEEE<br />
802.3 information. Additionally, standards organizations as<br />
well as vendors such as <strong>Extreme</strong> <strong>Networks</strong> will help to drive<br />
new functionality in <strong>LLDP</strong> extensions. New standards, such<br />
as <strong>LLDP</strong>-Media Endpoint <strong>Discovery</strong> (MED), will provide<br />
extensibility to fully standardized solutions to other reasonably<br />
predictable needs in this area, as well as allowing for<br />
vendor-specific extensions.<br />
802.1 Extensions<br />
IEEE 802.1 extensions deal primarily with describing VLAN<br />
attributes. They will also be supported in the first release of<br />
<strong>LLDP</strong> support on <strong>Extreme</strong> <strong>Networks</strong> switches. Supported<br />
802.1 extensions are the TLVs shown in Table 2.<br />
TLV<br />
Port VLAN ID<br />
Port & <strong>Protocol</strong><br />
VLAN ID<br />
VLAN Name<br />
<strong>Protocol</strong> Identity<br />
802.3 Extensions<br />
The IEEE 802.3 TLV extensions describe various attributes<br />
associates with the operation of an 802.3 LAN interface. The<br />
defined TLVs supported in the first implementation of <strong>LLDP</strong><br />
are shown in Table 3.<br />
TLV<br />
MAC/PHY<br />
Configuration<br />
and Status<br />
Power-via-MDI<br />
<strong>Link</strong> Aggregation<br />
Maximum Frame<br />
Size<br />
DESCRIPTION<br />
Identifies the VLAN identifier associated<br />
with an untagged VLAN. Only one Port<br />
VLAN ID can exist in an <strong>LLDP</strong> PDU.<br />
Allows the port to advertise if it supports<br />
port/protocol based VLANs, and there<br />
associated VLAN ID.<br />
Allows a device to advertise the textual name<br />
of any VLAN with which it is configured.<br />
Provides the protocols that are accessible<br />
through the <strong>LLDP</strong> port.<br />
Table 2: <strong>LLDP</strong> 802.1 Extensions<br />
DESCRIPTION<br />
Determines more about the auto negotiation<br />
settings of the port, as well as the type of<br />
physical interface used.<br />
Advertises the power-via-MDI implementations<br />
supported by the port. Power Information<br />
allows for improved power management<br />
for endpoints utilizing IEEE 802.3af Power<br />
over Ethernet (PoE).<br />
Allows the port to send information about its<br />
configured link aggregation (whether the link<br />
is capable of being aggregated, whether it is<br />
currently in an aggregation and if in an ag-gregation,<br />
the port of the aggregation).<br />
Reports the maximum supported frame size<br />
for the port.<br />
Table 3: <strong>LLDP</strong> 802.3 Extensions<br />
<strong>LLDP</strong>-MED<br />
<strong>Extreme</strong> <strong>Networks</strong> Technical Brief<br />
<strong>LLDP</strong>-MED is a new set of standards enhancing the basic<br />
<strong>LLDP</strong> protocol, which applies to increased discovery of end-<br />
point devices. In the future, <strong>Extreme</strong> <strong>Networks</strong> will implement<br />
many of the new <strong>LLDP</strong>-MED standards under development<br />
by the Telecommunications Industry Association (TIA).<br />
Management Components<br />
EPICenter Management<br />
<strong>LLDP</strong> provides detailed <strong>Layer</strong> 2 network information for<br />
connected access devices, exposing the entire LAN to the<br />
EPICenter management system. <strong>Layer</strong> 2 discovery drills<br />
down to the port that access devices are connected to and<br />
gives a complete understanding of connectivity and device<br />
properties. This granularity of detail is necessary to configure<br />
and maintain end-to-end networks from a network management<br />
system—“End-to-end,” meaning that network administrators<br />
should not have to manually audit a network to<br />
discover third-party vendor devices. Instead, <strong>LLDP</strong> allows for<br />
centralized management and automated discovery of all<br />
wired and wireless devices. This is achieved through flexible<br />
management views, with options that can be selected per<br />
device, user, action, time or location.<br />
Using <strong>LLDP</strong> in <strong>Extreme</strong> <strong>Networks</strong> devices, EPICenter<br />
manager is able to build a complete topology of the network<br />
and make automation a reality. Because <strong>LLDP</strong> messages are<br />
stored in the MIB of an <strong>Extreme</strong> <strong>Networks</strong> switch, EPICenter<br />
is able to obtain complete access to the information through<br />
SNMP advertisements. Having this control and information<br />
availability through EPICenter allows centralized access to<br />
accurate and timely network data, enabling simplified device<br />
management and troubleshooting. For example, it becomes<br />
possible for EPICenter management to discover configuration<br />
inconsistencies or malfunctions that can result in impaired<br />
communication at higher layers. Most importantly, EPICenter<br />
can obtain this information from all network devices, not just<br />
<strong>Extreme</strong> <strong>Networks</strong> devices.<br />
Command Line Interface (CLI)<br />
CLI is an optional method of configuration for <strong>LLDP</strong>. CLI<br />
can send configuration information per port to<br />
<strong>Extreme</strong> <strong>Networks</strong> switches via SNMP. CLI can also be<br />
used to maintain a list of <strong>LLDP</strong> enabled ports and the<br />
port mode (i.e. transmit only, receive only or transmit<br />
and receive).<br />
© 2006 <strong>Extreme</strong> <strong>Networks</strong>, Inc. All rights reserved. <strong>Link</strong> <strong>Layer</strong> <strong>Discovery</strong> <strong>Protocol</strong>—Page 4