0% found this document useful (0 votes)
255 views7 pages

Alcatel-Lucent Omnipcx Enterprise: Lldp-Med

alcatel

Uploaded by

issa galal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
255 views7 pages

Alcatel-Lucent Omnipcx Enterprise: Lldp-Med

alcatel

Uploaded by

issa galal
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Alcatel-Lucent OmniPCX Enterprise

LLDP-MED

All Rights Reserved © 2009, Alcatel-Lucent 1

OBJECTIVE

‹ To describe the LLDP protocol implementation on IP Touch 8 Series

Alcatel-Lucent OmniPCX Enterprise – LLD-MED


Ref. ENTP0535P01TEFUS Issue 02
LLDP-MED
Generalities

„ Since R9.1, the IP Touch x8 Series extensions(1) handle the LLDP-MED protocol

z LLDP-MED: Link Layer Discovery Protocol - Media Endpoint Discovery

„ LLDP operates on data link layer. It is used to exchange some devices information
(identity, capabilities) between the network switches/routers and the connected devices.
This mechanism is based on IEEE 802.1AB(LLDP) and ANSI TIA 1057 (LLDP-MED) standards

„ With LLDP

z The device information is encapsulated in LLDPDUs(2) in the form of TLV(3)


† A device may be able to store a received information in a standard MIB (4)

z A device can operate in different modes:


† Transmission/Reception
† Only Transmission, or only Reception
† No Transmission, no Reception

z A LLDP enabled device can send information:


† At its startup (and then periodically)
† When a modification of the mode has been done locally

All Rights Reserved © 2009, Alcatel-Lucent 2

1) Fast Ethernet and Extended Edition

2) LLDPDUs: Link Layer Discovery Packet Data Units

3) TLV: Type Length Value

4) Management Information Base

Alcatel-Lucent OmniPCX Enterprise – LLD-MED


Ref. ENTP0535P01TEFUS Issue 02
LLDP-MED
IP Touch x8 Series

„ The LLDP/LLDP-MED client is activated by default in terminal side during


initialization(1)

„ With LLDP-MED protocol, the IP Touch x8 Series terminals can automatically:

z Acquire VLAN ID(2)

z Renegotiate power consumption with more accurate figure instead of only


POE class information

z Send inventory information of terminal to the adjacent LAN switch

„ For more flexibility, all the three sub functions: VLAN acquire, Power
Management and Inventory Publication can be disabled through Local MMI(3)

„ Currently, only two switches(4) have been qualified with IP Touch for LLDP-MED
† Please refer to the TC1290 for the “white list” and feature restrictions evolution

All Rights Reserved © 2009, Alcatel-Lucent 3

1) If the LAN switch does not respond, the extension continues with a normal startup

2) The terminal sends to the switch some information via a LLDP/LLDP_MED message. It then starts a “one second” timer. If the set
does not receive anything from the switch, it considers that the adjacent LAN Switch does not support VLAN Assignment, and the
terminal continues its initialization with a normal startup.

3) MMI: Man Machine Interface

4) Release “i1.605.14e”
- Cisco Catalyst 3750 (version 12.2)
- HP ProCurve 2610 (version R.11.25)

Alcatel-Lucent OmniPCX Enterprise – LLD-MED


Ref. ENTP0535P01TEFUS Issue 02
LLDP-MED
VLAN Acquirement

„ An IP Touch can acquire its VLAN Id directly from the network switch (without
setting up an AVA Server) thanks to the LLPD-MED

z From now, it is possible to provide the VLAN Id to a x8 Series extension via


three methods(1):

† Manually via the extension MMI


† Dynamically with the help of the AVA Server (DHCP Server)
† Automatically from the network Switch through LLDP/LLDP-MED

z As different VLAN Id acquirement methods are available, a selection order is


taken into account by the set(2):

† In dynamic mode: LLDP > AVA > Information from local configuration
† In static mode is: LLDP > Information from local configuration

All Rights Reserved © 2009, Alcatel-Lucent 4

1) A fourth method can be considered: the 802.1x use. But with this method, the VLAN Id is not provided to the extension, but to the
switch port ! (it is totally transparent for the terminal)

2) If the 802.1x method is considered as a fourth method, it takes place as the last possibility for both configuration types (dynamic or
static)

Alcatel-Lucent OmniPCX Enterprise – LLD-MED


Ref. ENTP0535P01TEFUS Issue 02
LLDP-MED
Power Management

„ The IP Touch is able to calculate its power consumption


z It then send this information via LLDP to the switch
z The switch can therefore optimize its power management in a more accurate
way than only with POE Class Information

z At the set startup, it calculates its maximum consumption value and notify
the switch about it via a LLDP-MED message

z The set is able to advertise its power priority to the switch. Three priority
levels are supported by the terminal:

† Low (default one)


† High
† Critical

All Rights Reserved © 2009, Alcatel-Lucent 5

When a switch can not provide the POE at 100% of the ports, the equipment requiring a medium or Max Power (or even a low power)
could notify the switch. Therefore, the switch could optimize the power overbooking [in fact by default the max power can be
provided to all the ports (in a management point of view) but some switches can not provide physically this power to all the ports]

Alcatel-Lucent OmniPCX Enterprise – LLD-MED


Ref. ENTP0535P01TEFUS Issue 02
LLDP-MED
Inventory Publication

„ The IP Touch is able to send some inventory parameters to the connected


switch

z List of transmitted information

{ Hardware Revision
{ Using hardware version stored in the flash
{ Firmware Revision
{ Using software binary version which the terminal is running on
{ Software Revision
{ Same with Firmware Revision
{ Serial Number
{ Using that stored in the flash
{ Manufacture Name
{ Using default value “Alcatel-Lucent Enterprise”
{ Model Name
{ Using the terminal type (NOE 4018/4008/4028/4038/4068 FE/EE)
{ Asset ID
{ Using the MAC address of LAN port

All Rights Reserved © 2009, Alcatel-Lucent 6

Example of LLDP inventory sent to the switch:

Remote LLDP Agents on Local Slot/Port 2/23:

Chassis 151.1.1.30, Port 00:80:9f:8d:c1:51:


Remote ID = 1,
Chassis Subtype = 5 (Network Address),
Port Subtype = 3 (MAC address),
Port Description = (null),
System Name = (null),
System Description = (null),
Capabilities Supported = Telephone,
Capabilities Enabled = Telephone,
MED Device Type = Endpoint Class III,
MED Capabilities = Capabilities | Power via MDI-PD(33),
MED Extension TLVs Present = Network Policy| Inventory,
MED Power Type = PD Device,
MED Power Source = PSE,
MED Power Priority = Low,
MED Power Value = 6.4 W,
Remote port MAC/PHY AutoNeg = Supported Enabled Capability 0xc036,
Mau Type = 1000BaseTFD - Four-pair Category 5 UTP full duplex mode

Alcatel-Lucent OmniPCX Enterprise – LLD-MED


Ref. ENTP0535P01TEFUS Issue 02
LLDP-MED
Configuration

„ Access to the configuration menu via the set MMI

z Use the navigator Page Up/down to reach the LLDP tab

Main Menu

... ...

Certificate SIP download


LLDP

z It is possible to enable/disable each proposed option

LLDP

Vlan Acquirement
Power Management ...

Power Priori Low Possible options


Low (default)
Inventory Publication
Critical
High

All Rights Reserved © 2009, Alcatel-Lucent 7

Example of LLDP message provided by the IP Touch 8 Series sets

Alcatel-Lucent OmniPCX Enterprise – LLD-MED


Ref. ENTP0535P01TEFUS Issue 02

You might also like