12.11.2012 Views

Link Layer Discovery Protocol (LLDP) - Extreme Networks

Link Layer Discovery Protocol (LLDP) - Extreme Networks

Link Layer Discovery Protocol (LLDP) - Extreme Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Link</strong> <strong>Layer</strong> <strong>Discovery</strong> <strong>Protocol</strong> (<strong>LLDP</strong>)<br />

A New Standard for Discovering and Managing Converged Network Devices<br />

If there is any certainty in the access layer of a network, it is<br />

that the number and the complexity of devices that reside<br />

in this layer will continue to experience rapid growth.<br />

Ethernet access ports are expected to more than triple from<br />

2004 to 2007 (IDC Research, 2004). This exponential<br />

growth in the number of devices requiring LAN connectivity<br />

is due largely to the proliferation of new applications such<br />

as IP Telephony and wireless access.<br />

From a network management perspective, there are direct<br />

implications that come from these changes. In the past,<br />

many network equipment vendors have developed proprietary<br />

discovery methods in order to incorporate new access<br />

devices that they develop. In addition, key infrastructure<br />

vendors have developed proprietary discovery protocols,<br />

storing the data in an enterprise extension of the Management<br />

Information Base (MIB) used with Simple Network<br />

Management <strong>Protocol</strong> (SNMP). Today’s network management<br />

solutions are required to add expanded functionality<br />

and, at the same time, reduce complexity. Deployment,<br />

configuration, monitoring and other management disciplines<br />

must accommodate new technologies and network changes<br />

that are necessary to support new applications. Further,<br />

management systems must incorporate features that meet<br />

or exceed existing TDM voice solutions while providing<br />

advanced functionality to take advantage of the data<br />

infrastructure.<br />

<strong>Extreme</strong> <strong>Networks</strong> ® simplifies today’s expanding network<br />

environment and management challenges by improving<br />

intelligence and automation throughout the network.<br />

<strong>Extreme</strong> <strong>Networks</strong> now incorporates the recently finalized<br />

<strong>LLDP</strong>—IEEE standard, 802.1AB into its infrastructure<br />

products. <strong>LLDP</strong> was recently accepted as the standard open<br />

protocol for discovering network topologies and information<br />

concerning devices on the network.<br />

<strong>LLDP</strong> promises to simplify troubleshooting of enterprise<br />

networks and enhance the ability of network management<br />

tools to discover and maintain accurate network topologies<br />

in multi-vendor environments. It serves to reduce the<br />

complexities and expenses involved with convergence<br />

driven network changes by greatly simplifying management<br />

and connectivity issues. The new standard sets the stage for<br />

convergence applications by allowing enterprises to add<br />

new access devices in a non-disruptive Plug-and-Play<br />

fashion. Voice and wireless services can be easily implemented<br />

without major network upgrades.<br />

.<br />

<strong>Extreme</strong> <strong>Networks</strong> Technical Brief<br />

Today’s networks must incorporate best-of-breed solutions<br />

at every layer of the network, regardless of which vendor<br />

you choose. <strong>LLDP</strong> allows enterprises to build a best-ofbreed<br />

open converged network that can easily accommodate<br />

new applications, such as voice, while achieving five 9’s<br />

availability. The open nature of <strong>LLDP</strong> forms a foundation for<br />

co-development of new add-on discovery features that will<br />

help enable new Ethernet-based applications and services<br />

in the future.<br />

<strong>Extreme</strong> <strong>Networks</strong> employs <strong>LLDP</strong> not only as a means to<br />

simplify deployment of access devices, but also as a<br />

troubleshooting and firmware management tool and<br />

eventually as a way to legitimize new data services. For<br />

instance, in the future, <strong>Extreme</strong> <strong>Networks</strong> plans to provide<br />

much-needed E911 emergency call services in Voice-over-IP<br />

(VoIP) applications and enable new applications such as<br />

Voice over WLAN (VoWLAN).<br />

Benefits<br />

The business level benefits that can be realized from<br />

deploying <strong>LLDP</strong> in an <strong>Extreme</strong> <strong>Networks</strong> device are<br />

far-reaching.<br />

Lower Operating Costs<br />

Increases in automation achieved through <strong>LLDP</strong> can<br />

directly contribute to lower operating costs. Management<br />

and network maintenance are greatly simplified as a result<br />

of management tool consolidation and automation of<br />

diagnostic and consistency checking procedures. Automated<br />

discovery of access devices also reduce general setup costs<br />

of new equipment. <strong>LLDP</strong> simplifies management and<br />

network deployment, and as a result, lessens the number<br />

and complexity of processes and reduces headcount.<br />

Improved Choice and Flexibility in Network<br />

Design<br />

<strong>LLDP</strong> helps create an open market and customer choice so<br />

that a business can choose the best vendor for a particular<br />

network application. <strong>LLDP</strong> helps eliminate the barriers to<br />

creating a multi-vendor best-of-breed solution, thus<br />

allowing for a more advanced network and reduced capital<br />

expenditures due to competitive bidding and increased<br />

bargaining power. Open standards benefit the end customer<br />

as a result of vendors co-developing technology. This<br />

coordination simultaneously advances development cycles<br />

on new technology and increases price competition.<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 1


How <strong>LLDP</strong> Works<br />

<strong>LLDP</strong> is essentially a neighbor discovery protocol that<br />

defines a method for network access devices using Ethernet<br />

connectivity to advertise information about them to peer<br />

devices on the same physical LAN and store information<br />

about the network. It allows a device to learn higher layer<br />

management reachability and connection endpoint information<br />

from adjacent devices. <strong>LLDP</strong> has been fully implemented<br />

in <strong>Extreme</strong> <strong>Networks</strong> switches and is accessible from the<br />

EPICenter ® management system.<br />

Using <strong>LLDP</strong>, an <strong>Extreme</strong> <strong>Networks</strong> device is able to<br />

advertise its own identification information, its capabilities<br />

and media-specific configuration information, as well as<br />

learn the same information from the devices connected to<br />

it. <strong>LLDP</strong> advertises this information over Logical <strong>Link</strong>-<strong>Layer</strong><br />

Control frames and the information received from other<br />

agents in IEEE-defined Management Information Bases<br />

(MIB) modules. Figure 1 shows this relationship.<br />

Port Device Info<br />

A13 Switch xxxx<br />

C2<br />

D2<br />

F3<br />

<strong>Discovery</strong> MIB<br />

IP Phone<br />

PC<br />

IP-PBX<br />

xxxx<br />

xxxx<br />

xxxx<br />

BlackDiamond ®<br />

10808<br />

BlackDiamond<br />

8810<br />

Intellegent Core<br />

PSTN<br />

<strong>LLDP</strong>—How it Works<br />

The IEEE 802.1ab <strong>Link</strong> <strong>Layer</strong> <strong>Discovery</strong> <strong>Protocol</strong> defines a<br />

standard way for Ethernet devices to advertise information<br />

about themselves to their network neighbors and store<br />

information they discover from other device.<br />

1.<br />

2.<br />

3.<br />

Figure 1: <strong>LLDP</strong> Peer <strong>Discovery</strong><br />

LAN switch and router advertise chassis/port ids and<br />

system descriptions to each other.<br />

The devices store the information they learn about each<br />

other in local MIB databases accessible via SNMP.<br />

A network management system (<strong>Extreme</strong> <strong>Networks</strong><br />

EPICenter) retrieves the data stored by each device that<br />

builds a network topology map.<br />

OSI Reference<br />

Model <strong>Layer</strong>s<br />

Application<br />

Presentation<br />

Session<br />

Transport<br />

Network<br />

Data <strong>Link</strong><br />

Physical<br />

IEEE 802 Model <strong>Layer</strong><br />

Higher <strong>Protocol</strong> <strong>Layer</strong>s<br />

MAC Client {Bridge Relay Entity, LLC, etc.}<br />

<strong>Link</strong> Aggregation Sublayer (Optional)<br />

<strong>LLDP</strong><br />

MAC Control<br />

(Optional)<br />

MAC<br />

<strong>Extreme</strong> <strong>Networks</strong> Technical Brief<br />

<strong>LLDP</strong> significantly aids in the deployment of any network<br />

device that supports the protocol. As a media independent<br />

protocol intended to be run on all IEEE 802 devices, <strong>LLDP</strong><br />

may be used to discover routers, bridges, repeaters, WLAN<br />

APs, IP telephones, network camera or any <strong>LLDP</strong>-enabled<br />

device, regardless of manufacturer. Since <strong>LLDP</strong> runs over the<br />

data-link layer only, an <strong>Extreme</strong> <strong>Networks</strong> switch running<br />

one network layer protocol can discover and learn about an<br />

access device running a different network layer protocol.<br />

<strong>LLDP</strong> Architecture<br />

<strong>LLDP</strong> is a data-link layer protocol, operating above the MAC<br />

service layer and, as a result, can be used in any networking<br />

device that implements a MAC service. Figure 2 shows<br />

where <strong>LLDP</strong> resides in the IEEE 802 Model <strong>Layer</strong>s.<br />

<strong>LLDP</strong> <strong>LLDP</strong><br />

MAC Control<br />

(Optional)<br />

MAC Control<br />

(Optional)<br />

MAC MAC<br />

Physical Physical Physical<br />

BlackDiamond<br />

8810<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 2<br />

Router<br />

MIB<br />

Network<br />

Management<br />

System<br />

`<br />

Figure 2: <strong>LLDP</strong> Architecture<br />

3<br />

2<br />

1<br />

LAN Switch<br />

MIB<br />

IP Phone


<strong>LLDP</strong> will advertise and store messages and will not solicit<br />

information or keep state between devices. Each<br />

<strong>Extreme</strong> <strong>Networks</strong> switch configured with an active <strong>LLDP</strong><br />

agent will send and receive messages on all physical<br />

interfaces enabled for <strong>LLDP</strong> transmission. These messages<br />

are sent periodically and are typically configured for short<br />

time intervals to ensure that accurate information is always<br />

available. These messages are then stored for a configurable<br />

period of time, determined by the time-to-live (TTL) value<br />

set by a user and contained within the received packet. The<br />

message information expires and is discarded when the TTL<br />

value is met. There is a default recommended time value for<br />

the TTL of 120 seconds. The only other time an advertisement<br />

would be sent is when a relevant change takes place<br />

in the switch. If information values change for any reason,<br />

the <strong>LLDP</strong> agent will be notified and will send out and<br />

update the new values.<br />

Basic <strong>LLDP</strong> functionality is represented in Figure 3.<br />

STACK NO<br />

STACK NO<br />

<strong>LLDP</strong><br />

Summit X450<br />

Advertisements<br />

Summit X450<br />

11 22 3 44 55 66 77 88 99 10 10 11 11 12 12 13 13 14 14 15 15 16 16 17 17 18 18 19 19 20 20 21 21 22 22 23 23 24 24<br />

11 22 33 44 55 66 77 88 99 10 10 11 11 12 12 13 13 14 14 15 15 16 16 17 17 18 18 19 19 20 20 21 21 22 22 23 23 24 24<br />

CONSOLE CONSOLE<br />

CONSOLE CONSOLE<br />

MIB MIB<br />

SNMP<br />

Advertisements<br />

In this example <strong>LLDP</strong> advertisements are exchanged<br />

between participating network devices and stored in the<br />

MIB. As a result, EPICenter is able to gain access to that<br />

information using SNMP and build a complete topology and<br />

detailed inventory of network devices. These is true even if<br />

some network devices, such as IP phones, only advertise<br />

messages and are not able to store peer information.<br />

<strong>Protocol</strong> Data Unit Format<br />

`<br />

A single <strong>LLDP</strong> <strong>Protocol</strong> Data Unit (<strong>LLDP</strong> PDU) is transmitted<br />

in a single 802.3 Ethernet frame. The basic <strong>LLDP</strong> PDU<br />

consists of a header, followed by a variable number of<br />

information elements known as TLVs that each includes fields<br />

for Type, Length, and Value. ‘Type’ identifies what kind of<br />

information is being sent. ‘Length’ indicates the length of the<br />

information string. ‘Value’ is the actual information sent.<br />

Each <strong>LLDP</strong> PDU includes three mandatory TLVs followed by<br />

optional TLVs. The three mandatory TLVs are Chassis ID,<br />

Port ID and TTL. Other TLVs are optional to advertise. For<br />

STACK NO<br />

STACK NO<br />

1 22 33 44 55 66 77 88 99 10 10 11 11 12 12 13 13 14 14 15 15 16 16 17 17 18 18 19 19 20 20 21 21 22 22 23 23 24 24<br />

11 2 3 4 5 66 7 8 9 10 10 11 11 12 12 13 13 14 14 15 15 16 16 17 17 18 18 19 19 20 20 21 21 22 22 23 23 24 24<br />

EPICenter<br />

Network Management<br />

Figure 3: Basic <strong>LLDP</strong> Functionality<br />

CONSOLE CONSOLE<br />

CONSOLE CONSOLE<br />

<strong>Extreme</strong> <strong>Networks</strong> Technical Brief<br />

<strong>Extreme</strong> <strong>Networks</strong> switch ports enabled with basic <strong>LLDP</strong>, the<br />

information shown in Table 1 can be transmitted and stored<br />

using <strong>LLDP</strong>.<br />

Chassis ID<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 3<br />

Port ID<br />

TLV<br />

Time-to-live (TTL)<br />

Port description<br />

System name<br />

System description<br />

System capabilities<br />

Management<br />

address<br />

Organizationally<br />

specific<br />

End of <strong>LLDP</strong> PDU<br />

DESCRIPTION<br />

Represents the chassis identification for the<br />

device that transmitted the <strong>LLDP</strong> frame. The<br />

receiving <strong>LLDP</strong> agent combines the Chassis ID<br />

and Port ID to represent the entity connected<br />

to the port where the frame was received.<br />

Represents the identification of the specific<br />

port that transmitted the <strong>LLDP</strong> frame. The<br />

receiving <strong>LLDP</strong> agent combines the Chassis ID<br />

and Port to represent the entity connected to<br />

the port where the frame was received.<br />

Represents the length of time that information<br />

contained in the receive <strong>LLDP</strong> frame shall<br />

be valid. If a value of zero is sent it can also<br />

identify a device that has shut down or is no<br />

longer transmitting, prompting deletion of the<br />

record from the local database.<br />

Identifies information about the interface. This<br />

will include the name of the manufacturer, the<br />

product name and the version of the interface<br />

hardware/software (per RFC2863).<br />

Identifies the administratively-assigned name<br />

for the device (per RFC3418).<br />

A textual description of the device. This value<br />

typically includes the full name and version<br />

identification of the system’s hardware type,<br />

software operating-system, and networking<br />

software (per RFC3418).<br />

Identifies the capabilities of the device and its<br />

primary function. (e.g. Repeater, Bridge, WLAN<br />

Access Point, Router, Telephone, DOCSIS cable<br />

device, Station only, etc.).<br />

Identifies the IP address or MAC address of<br />

the device.<br />

The IEEE has further enhanced the value of the<br />

<strong>LLDP</strong> protocol by making it possible for other<br />

standards organizations and vendors to create<br />

custom advertisement messages for other types<br />

of endpoints. For <strong>Extreme</strong> <strong>Networks</strong> switches, the<br />

following TLV based information is maintained:<br />

- 802.1 VLAN extensions<br />

- 802.3 LAN interface extensions<br />

- <strong>LLDP</strong>-MED extensions<br />

Marks the end of data. No further processing<br />

of TLVs after this is necessary. This is a<br />

mandatory TLV and must therefore be present<br />

at the end of the data stream.<br />

Table 1: Basic TLVs supported by <strong>Extreme</strong> <strong>Networks</strong>


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


Applications<br />

Diagnostics/Troubleshooting<br />

<strong>LLDP</strong> is a natural diagnostic tool because of its inherent<br />

ability to discover and maintain accurate and up-to-date<br />

network topologies. The TLV information exposes network<br />

mapping, inventory data and network troubleshooting<br />

information that may otherwise be unavailable. Network<br />

administrators can use this information to identify outdated<br />

hardware and software, speed and duplex mismatches and<br />

improperly configured devices. For example, using TTL<br />

values, <strong>LLDP</strong> can be used to locate ports that are no longer<br />

sending <strong>LLDP</strong> advertisements to determine endpoint devices<br />

that have gone out of service.<br />

Voice<br />

VoIP continues to demand availability standards and<br />

advanced functionality from data networks that will help put<br />

it on par with TDM systems. <strong>LLDP</strong> takes another step<br />

forward in achieving this goal by facilitating multi-vendor IP<br />

Telephony networks and enabling these networks to achieve<br />

dial-tone reliability. VoIP networks have been relatively slow<br />

to adopt voice-class features and have lacked complete<br />

integration with existing network management systems. IP<br />

telephones typically lack support of management protocols<br />

such as SNMP, prohibiting NMS systems from a complete<br />

network view. <strong>LLDP</strong> now brings discovery of VoIP topology<br />

information to <strong>Extreme</strong> <strong>Networks</strong> Management System.<br />

<strong>LLDP</strong> allows an IP phone to be dynamically and fully<br />

recognized by an <strong>Extreme</strong> <strong>Networks</strong> device. The <strong>Extreme</strong><br />

<strong>Networks</strong> device is then able to adapt to the network<br />

according to the needs of the IP telephone and MIB information<br />

becomes accessible to EPICenter.<br />

<strong>Extreme</strong> <strong>Networks</strong> acts as an industry innovator by<br />

incorporating early-standards <strong>LLDP</strong>-MED functions and by<br />

making significant headway in building Plug-and-Play IP<br />

Telephony networks.<br />

<strong>Extreme</strong> <strong>Networks</strong> <strong>LLDP</strong><br />

Implementation vs. Other<br />

<strong>Discovery</strong> <strong>Protocol</strong>s<br />

Many network equipment vendors have developed discovery<br />

protocols to operate in homogeneous networks comprised of<br />

their own equipment. Cisco Systems has Cisco <strong>Discovery</strong><br />

www.extremenetworks.com email: com info@extremenetworks.<br />

Corporate<br />

and North America<br />

<strong>Extreme</strong> <strong>Networks</strong>, Inc.<br />

3585 Monroe Street<br />

Santa Clara, CA 95051 USA<br />

Phone +1 408 579 2800<br />

<strong>Extreme</strong> <strong>Networks</strong> Technical Brief<br />

<strong>Protocol</strong> (CDP); Enterasys <strong>Networks</strong>, Cabletron <strong>Discovery</strong> <strong>Protocol</strong><br />

(CDP); and Nortel <strong>Networks</strong>, Nortel <strong>Discovery</strong> <strong>Protocol</strong> (NDP).<br />

However, many network architects building out enterprise and<br />

carrier VoIP networks would like a standard means of discovery<br />

allowing them to mix best-of-breed equipment from multiple vendors.<br />

Most network designs are moving to a best-of-breed<br />

strategy where individual components in the network are chosen<br />

for their unique ability to handle an application. A standardsbased<br />

discovery protocol readies a network for convergence<br />

applications without major dependencies concerning the<br />

manufacturer of network equipment. See Figure 4 for a comparison<br />

between discovery protocols.<br />

Industry Standards Based<br />

Multi-Vendor Network Support<br />

Chassis & Port ID<br />

Port Description<br />

System Name<br />

System Description<br />

System Capabilities<br />

Management Address<br />

VLAN ID<br />

Voice VLANs<br />

Network Policy<br />

Auto Negotiation Requirements<br />

Power Information (PoE Capable)<br />

Frame Size Requirements<br />

Location Advertisements (E911 capable)<br />

Europe, Middle East, Africa<br />

and South America<br />

Phone +31 30 800 5100<br />

Asia Pacific<br />

Phone +852 2517 1123<br />

Y N N N<br />

Y N N N<br />

Y Y Y Y<br />

Y Y Y Y<br />

Y Y Y Y<br />

Y Y N N<br />

Y Y N N<br />

Y Y Y Y<br />

Y Y N N<br />

Y N N N<br />

Y N N N<br />

Y N N N<br />

Y Y N N<br />

Y N N N<br />

Y Y N N<br />

© 2006 <strong>Extreme</strong> <strong>Networks</strong>, Inc. All rights reserved.<br />

<strong>Extreme</strong> <strong>Networks</strong>, the <strong>Extreme</strong> <strong>Networks</strong> Logo, BlackDiamond and EPICenter, are either registered trademarks or trademarks of<br />

<strong>Extreme</strong> <strong>Networks</strong>, Inc. in the United States and/or other countries.<br />

Specifications are subject to change without notice.<br />

Japan<br />

Phone +81 3 5842 4011<br />

1061_01 11/06 <strong>Link</strong> <strong>Layer</strong> <strong>Discovery</strong> <strong>Protocol</strong> Technology Brief<br />

<strong>LLDP</strong>-MED<br />

Cisco CDP<br />

Nortel NDP<br />

Figure 4: Competitive <strong>Discovery</strong> Methods<br />

Enterasys CDP

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!