HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem Virtual Connect
cancel
Showing results for 
Search instead for 
Did you mean: 

Virtual Connect Link Layer Discovery Protocol(LLDP question.

 
chuckk281
Trusted Contributor

Virtual Connect Link Layer Discovery Protocol(LLDP question.

Paul had a question regarding Virtual Connect's use of LLDP:

 

********************************************************

 

The Virtual Connect guide for Cisco Admins recommends enabling LLDP ports on the Cisco core that the VC is connect to.

 

What would be the impact of not enabling LLDP? 

 

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01386629/c01386629.pdf

 

****************************************************

 

Chris answered his question:

 

******************************************************

 

Without LLDP, VC can’t discover what the connected device is. VC uses this info to determine if the port should be used for stacking or an uplink.

You also get additional info about the upstream device (eg. MAC and port number of the upstream switch).

 

**********************************************

 

Comments? Does this help your situation?

 

 

1 REPLY
chuckk281
Trusted Contributor

Re: Virtual Connect Link Layer Discovery Protocol(LLDP question.

Mark also joined the conversation.

 

***********************************

 

Virtual Connect works the same without LLDP enabled on the external switch, it just doesn’t discover the device and report it on the Statistic page for that port.

However; if enabled, it is really useful when you want to determine what port/switch a particular VC uplink is connected to, for troubleshooting purposes.

 

************************************************