Wired Intelligent Edge

 LLDP-Med seems simple enough to get configured but Im having some problems here.  The path to the end switch that Im working on starts at a cisco 3750 to HP 2848 to another HP 2848 (ver. I.10.77).  I have lldp configured as:

lldp run

vlan 252
   name "VOICE"
   no ip address
   tagged 1-48
   voice
   exit

when I run 'show lldp info remote-device 14' it outputs:

------------------------------------------------------------------------------
  Local Port   : 14
  ChassisType  : network-address
  ChassisId    : 0.0.0.0
  PortType     : mac-address
  PortId       : 08 00 0f 59 6e 6c
  SysName      : MITEL 5320 DM
  System Descr : MITEL 5320 DM,GigE,h/w rev 0,ASIC rev 1,f/w Boot 04.00.01...
  PortDescr    : LAN port

  System Capabilities Supported  : bridge, telephone
  System Capabilities Enabled    : bridge, telephone

  Remote Management Address
     Type    : all802
     Address : 08 00 0f 59 6e 6c

------------------------------------------------------------------------------

So, it looks like its discovering it, but the device is not getting the 252 and grabbing an IP address.   The VLAN 252 tagg path back to the core is correct.  We have existing layer 2 phones which work fine.  The layer 3 int is enabled on the core and pingable.  Also, we have an enterasys c5 in the same closet (cisco 3750 to hp 2848 to enterasys c5) and the phone works fine there with lldp med.

Id appreciate any help anybody can throw my way on this.

Thanks!

-Rob

You need to configure an lldp media-policy and network policy to assign the correct VLAN, or manually configure the phones for the correct VLAN and priority. Not sure on the HP commands off the top of my head, but on Enterasys standalone switches, it should look something like this:

set lldp tx-interval 20
set lldp port tx-tlv med-pol ge.1.1
set lldp port network-policy voice state enable tag tagged vid 15 cos 6 dscp 46 ge.1.1

The vid allocates the VLAN (15 in this case) and cos the layer-2 priority (6). The above example applies only to int ge.1.1.

Sorry for the delayed response...was on vacation last week. :smileywink:

Yes, I have the enterasys switches already working.  I mentioned the enterasys just to show that the VLAN tagging for the voice vlan was correct all the way to the edge.

Everything I come across for LLDP MED on the HP swtiches only says to simply enter the voice command under the vlan to advertise lldp on it.  This is not working though.

Id appreciate if anybody can confirm this or point me in the direction of any addition config/commands that need to be put on the configuration.

Thanks!

I'm running into the same problem right now.   On my 2610's I just put in the commands:

I cant remember where I found the documentation, but the short answer is that LLDP med is not supported on the 2800 series.  I believe it is on 2600 and 2900 series though.

Thanks for the quick reply.  If you find out anything let me know, I will do the same.  

Apologies for the late reply, but given the large number of views on this topic wanted to provide some additional details for others viewers of this thread.

The prior post by Rob Yamry is correct.  The 2800 series does NOT support LLDP-MED auto configuration, while most of the other HP series switches with PoE/PoE+ do.

To verify if this feature is supported on a specific HP product, please check that the product features or data sheet specifically mentions LLDP-MED (Media Endpoint Discovery) and/or ANSI/TIA-1057.  This is because LLDP-MED is an extension to LLDP and not part of the base IEEE 802.1AB specification.

Here is a couple of application notes for how to configure HP ProVision switches with Avaya and Cisco IP phones:

http://downloads.avaya.com/css/P8/documents/100168648

http://h17007.www1.hp.com/docs/interoperability/Cisco/4AA2-2301EEE.pdf

The key cli command required to enable LLDP-MED is to assign the 'voice' attribute for a given VLAN, for example:

(config) # vlan <VID> voice

The voice vlan needs to be either statically configured on a port or dynamically provisioned using 802.1X or MAC authentication.

Hope this helps