incorrect LLDP information on procurve 2524

[Baudin Maxime]

Hello,
While trying to create a network map, I found that lldp infos on procurve 2524 are wrong.

Lots of my 2524 are connected to 4108 or 4104 switchs and a 'sh lldp info remote device' tells me that 2524 is connected to 4108 on port number 184....instead of H16.

I don't have this problem with other switchs (2650, 2824, 2510).

All switchs have been upgraded with last firmware available.

This issue is for every 2524 switch on my network.

Did I miis an option ? I this a bug ?

Regards,
Maxime

[cenk sasmaztin]

hi Maxime
this is not bug bucause
2524 and 2512 only transmit lldp not recieve lldp packet

please look feature for 2500 switch family
you see not support lldp protocol on switch

http://www.hp.com/rnd/products/switches
/switch2524-2512/features.htm

and please read this guide page 8
http://cdn.procurve.com/training/Manuals/2300-2500-RelNotes-F0565-59903102.pdf
this switch only for procurve manager support lldp

cenk

[Baudin Maxime]

Thanks for your answer.

The documentation says :

"With version F.05.60, LLDP advertisements from remote neighbor devices can be received. Use the
show lldp info remote-device command to display information received from LLDP remote devices."

So it's working, but the information is incorrect.

Maxime

[cenk sasmaztin]

please read page 8 note:
Note
Selected LLDP information (such as system name, port description, port type, chassis type) received
by a Series 2500 switch from a remote neighbor is not viewable.

because connect now my costumer site for you and test 4200 switch on lldp command and I see all 2524 -2512 switch lldp info

my costumer 2524 switch frimware F.05.61

please check commnad

#sh lldp info remote-device

and trun around your 2524 switch frimware F_05_61
please retest

cenk

cenk

[Baudin Maxime]

I didn't said that lldp info wasn't here, I said that lldp information was wrong on 2524 side and right on 4108 side.

from 2524 (in 5_65 firmware version) :

LLDP Remote Device Information

LocalPort | ChassisId PortId PortDescr SysName
--------- + ------------------------- ------ --------- ----------------------
24 | 0001e7-cac900 184


look at the "PortId" : 184 !! which is not possible, there is no such port on a 4108 switch, the real port is : H16 (it's the 184'th port on the 4108 but it should appears as H16 and not 184).


here is the info on 4108 side :

sh lldp info remote-device :

H16 | 00 08 83 96 d8 80 24 24 swcopsm2

which is the right info.

And all my 2524 (with 5_65 firmware) give me wrong lldp informations.

[cenk sasmaztin]

hi Maxime
each info true

because port number H16 port id 184
port id number not switch port number ,port id number on backplane port number
A24+B24+C24+D24+E24+F24+G24+H16= <184>

2524 switch see sum port number other all chassis switch very normal.

cenk

[Matt Hobbs]

Maxime,

You've discovered a definite bug. The bug is the PortDescr and SysName is missing.

The PortId is correct (184), but you should also get a friendly name such as H16 (PortDescr).

You should open a case with HP Support and report this.

Matt


HP ProCurve Switch 2524# show lldp info remote-device

LLDP Remote Device Information

LocalPort | ChassisId PortId PortDescr SysName
--------- + ------------------------- ------ --------- ----------------------
24 | 0014c2-10dbc0 11
25 | 001185-d05780 46
26 | 0001e7-5f1100 26

[Baudin Maxime]

Thanks, I understand more clearly now.

I'll contact HP support.

regards,
Maxime

[Richard Brodie_1]

The LLDP support in the 2500 is limited;
it's an old model, and has smaller flash memory than the others. There probably wasn't room to fit the full LLDP code in. You may just have to live with it, unfortunately.

"Selected LLDP information (such as system name, port description, port type, chassis type) received by a Series 2500 switch from a remote neighbor is not viewable."

[Matt Hobbs]

Nice one Richard.

It is not a bug after all, it is expected behaviour as per the release notes - http://cdn.procurve.com/training/Manuals/2300-2500-RelNotes-F0565-59903102.pdf

Maybe you can try 'show cdp n d' instead as it is cross populated with the LLDP information.