<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Virtual Connect Link Layer Discovery Protocol(LLDP question. in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-link-layer-discovery-protocol-lldp-question/m-p/1162068#M33252</link>
    <description>&lt;P&gt;&lt;STRONG&gt;&lt;FONT color="#000000"&gt;Paul had a question regarding Virtual Connect's use of LLDP:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;********************************************************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The Virtual Connect guide for Cisco Admins recommends enabling LLDP ports on the Cisco core that the VC is connect to.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What would be the impact of not enabling LLDP?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01386629/c01386629.pdf" rel="nofollow" target="_blank"&gt;http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01386629/c01386629.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;****************************************************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;FONT color="#000000"&gt;Chris&amp;nbsp;answered his question:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;******************************************************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;You also get additional info about the upstream device (eg. MAC and port number of the upstream switch).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;**********************************************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;STRONG&gt;Comments? Does this help your situation?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 23 Aug 2010 14:42:59 GMT</pubDate>
    <dc:creator>chuckk281</dc:creator>
    <dc:date>2010-08-23T14:42:59Z</dc:date>
    <item>
      <title>Virtual Connect Link Layer Discovery Protocol(LLDP question.</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-link-layer-discovery-protocol-lldp-question/m-p/1162068#M33252</link>
      <description>&lt;P&gt;&lt;STRONG&gt;&lt;FONT color="#000000"&gt;Paul had a question regarding Virtual Connect's use of LLDP:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;********************************************************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The Virtual Connect guide for Cisco Admins recommends enabling LLDP ports on the Cisco core that the VC is connect to.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What would be the impact of not enabling LLDP?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01386629/c01386629.pdf" rel="nofollow" target="_blank"&gt;http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01386629/c01386629.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;****************************************************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;FONT color="#000000"&gt;Chris&amp;nbsp;answered his question:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;******************************************************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;You also get additional info about the upstream device (eg. MAC and port number of the upstream switch).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;**********************************************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;STRONG&gt;Comments? Does this help your situation?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 23 Aug 2010 14:42:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-link-layer-discovery-protocol-lldp-question/m-p/1162068#M33252</guid>
      <dc:creator>chuckk281</dc:creator>
      <dc:date>2010-08-23T14:42:59Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Connect Link Layer Discovery Protocol(LLDP question.</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-link-layer-discovery-protocol-lldp-question/m-p/1162090#M33253</link>
      <description>&lt;P&gt;Mark also joined the conversation.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;***********************************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;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.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;************************************************&lt;/P&gt;</description>
      <pubDate>Mon, 23 Aug 2010 18:12:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-link-layer-discovery-protocol-lldp-question/m-p/1162090#M33253</guid>
      <dc:creator>chuckk281</dc:creator>
      <dc:date>2010-08-23T18:12:48Z</dc:date>
    </item>
  </channel>
</rss>

