<?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 Distributed Trunking in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/distributed-trunking/m-p/4417163#M18495</link>
    <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;I am facing a strange situation.&lt;BR /&gt;I have just bought two new 3500yl switches in order to implement the new distributed trunking feature on a SAN network.&lt;BR /&gt;&lt;BR /&gt;Both switchs are linked with 2ports trunk LACP set as the ISC link.&lt;BR /&gt;&lt;BR /&gt;A 2ports LACP trunk is setup from an HP server 380 G4 and linked to both switches, one server port linked to one switch and the other port linked the secondary switch.&lt;BR /&gt;&lt;BR /&gt;The problem is that when linking the ports to the switches, one of the ports become blocked and the other . Hence i suspected the Spanning Tree for blocking LACP trunk, but even after disabling ST. The ports still revert to Blocked state after plugging cables??&lt;BR /&gt;&lt;BR /&gt;Can someone help me on this, that new feature is relatively new and is not largely explained on the web.&lt;BR /&gt;&lt;BR /&gt;Did someone get the same problem?? &lt;BR /&gt;&lt;BR /&gt;Juste to notice, I have setup a dedicated VLAN for the SAN network. Server ports are Untagged and the ISC link have been automatically made tagged member of all vlans (as stated on the Management Guide).&lt;BR /&gt;&lt;BR /&gt;***********************************&lt;BR /&gt;&lt;BR /&gt;BEFORE LINKING SERVER (port 25 on each switch)&lt;BR /&gt;&lt;BR /&gt;Local Port Status:&lt;BR /&gt;&lt;BR /&gt;PORT LACP TRUNK PORT LACP LACP&lt;BR /&gt;NUMB ENABLED GROUP STATUS PARTNER STATUS&lt;BR /&gt;----- -------- ------- -------- -------- -------&lt;BR /&gt;3 Active Trk3 Up Yes Success&lt;BR /&gt;4 Active Trk4 Up Yes Success&lt;BR /&gt;5 Active Trk5 Up Yes Success&lt;BR /&gt;6 Active Trk6 Up Yes Success&lt;BR /&gt;25 Active Trk25 Down Yes Success&lt;BR /&gt;&lt;BR /&gt;Remote Port Status:&lt;BR /&gt;&lt;BR /&gt;PORT LACP TRUNK PORT LACP LACP&lt;BR /&gt;NUMB ENABLED GROUP STATUS PARTNER STATUS&lt;BR /&gt;---- ------- ------- ------- ------- -------&lt;BR /&gt;3 Active Trk3 Down No Success&lt;BR /&gt;4 Active Trk4 Down No Success&lt;BR /&gt;5 Active Trk5 Down No Success&lt;BR /&gt;6 Active Trk6 Down No Success&lt;BR /&gt;25 Active Trk25 Down No Success&lt;BR /&gt;&lt;BR /&gt;*****************************************&lt;BR /&gt;&lt;BR /&gt;AFTER LINKING SERVER's LACP trunk&lt;BR /&gt;&lt;BR /&gt;Local Port Status:&lt;BR /&gt;&lt;BR /&gt;PORT LACP TRUNK PORT LACP LACP&lt;BR /&gt;NUMB ENABLED GROUP STATUS PARTNER STATUS&lt;BR /&gt;----- -------- ------- -------- -------- -------&lt;BR /&gt;3 Active Trk3 Up Yes Success&lt;BR /&gt;4 Active Trk4 Up Yes Success&lt;BR /&gt;5 Active Trk5 Up Yes Success&lt;BR /&gt;6 Active Trk6 Up Yes Success&lt;BR /&gt;25 Active Trk25 Blocked No Failure&lt;BR /&gt;&lt;BR /&gt;Remote Port Status:&lt;BR /&gt;&lt;BR /&gt;PORT LACP TRUNK PORT LACP LACP&lt;BR /&gt;NUMB ENABLED GROUP STATUS PARTNER STATUS&lt;BR /&gt;---- ------- ------- ------- ------- -------&lt;BR /&gt;3 Active Trk3 Down No Success&lt;BR /&gt;4 Active Trk4 Down No Success&lt;BR /&gt;5 Active Trk5 Down No Success&lt;BR /&gt;6 Active Trk6 Down No Success&lt;BR /&gt;25 Active Trk25 Up Yes Success</description>
    <pubDate>Mon, 11 May 2009 09:25:09 GMT</pubDate>
    <dc:creator>O.H.M</dc:creator>
    <dc:date>2009-05-11T09:25:09Z</dc:date>
    <item>
      <title>Distributed Trunking</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/distributed-trunking/m-p/4417163#M18495</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;I am facing a strange situation.&lt;BR /&gt;I have just bought two new 3500yl switches in order to implement the new distributed trunking feature on a SAN network.&lt;BR /&gt;&lt;BR /&gt;Both switchs are linked with 2ports trunk LACP set as the ISC link.&lt;BR /&gt;&lt;BR /&gt;A 2ports LACP trunk is setup from an HP server 380 G4 and linked to both switches, one server port linked to one switch and the other port linked the secondary switch.&lt;BR /&gt;&lt;BR /&gt;The problem is that when linking the ports to the switches, one of the ports become blocked and the other . Hence i suspected the Spanning Tree for blocking LACP trunk, but even after disabling ST. The ports still revert to Blocked state after plugging cables??&lt;BR /&gt;&lt;BR /&gt;Can someone help me on this, that new feature is relatively new and is not largely explained on the web.&lt;BR /&gt;&lt;BR /&gt;Did someone get the same problem?? &lt;BR /&gt;&lt;BR /&gt;Juste to notice, I have setup a dedicated VLAN for the SAN network. Server ports are Untagged and the ISC link have been automatically made tagged member of all vlans (as stated on the Management Guide).&lt;BR /&gt;&lt;BR /&gt;***********************************&lt;BR /&gt;&lt;BR /&gt;BEFORE LINKING SERVER (port 25 on each switch)&lt;BR /&gt;&lt;BR /&gt;Local Port Status:&lt;BR /&gt;&lt;BR /&gt;PORT LACP TRUNK PORT LACP LACP&lt;BR /&gt;NUMB ENABLED GROUP STATUS PARTNER STATUS&lt;BR /&gt;----- -------- ------- -------- -------- -------&lt;BR /&gt;3 Active Trk3 Up Yes Success&lt;BR /&gt;4 Active Trk4 Up Yes Success&lt;BR /&gt;5 Active Trk5 Up Yes Success&lt;BR /&gt;6 Active Trk6 Up Yes Success&lt;BR /&gt;25 Active Trk25 Down Yes Success&lt;BR /&gt;&lt;BR /&gt;Remote Port Status:&lt;BR /&gt;&lt;BR /&gt;PORT LACP TRUNK PORT LACP LACP&lt;BR /&gt;NUMB ENABLED GROUP STATUS PARTNER STATUS&lt;BR /&gt;---- ------- ------- ------- ------- -------&lt;BR /&gt;3 Active Trk3 Down No Success&lt;BR /&gt;4 Active Trk4 Down No Success&lt;BR /&gt;5 Active Trk5 Down No Success&lt;BR /&gt;6 Active Trk6 Down No Success&lt;BR /&gt;25 Active Trk25 Down No Success&lt;BR /&gt;&lt;BR /&gt;*****************************************&lt;BR /&gt;&lt;BR /&gt;AFTER LINKING SERVER's LACP trunk&lt;BR /&gt;&lt;BR /&gt;Local Port Status:&lt;BR /&gt;&lt;BR /&gt;PORT LACP TRUNK PORT LACP LACP&lt;BR /&gt;NUMB ENABLED GROUP STATUS PARTNER STATUS&lt;BR /&gt;----- -------- ------- -------- -------- -------&lt;BR /&gt;3 Active Trk3 Up Yes Success&lt;BR /&gt;4 Active Trk4 Up Yes Success&lt;BR /&gt;5 Active Trk5 Up Yes Success&lt;BR /&gt;6 Active Trk6 Up Yes Success&lt;BR /&gt;25 Active Trk25 Blocked No Failure&lt;BR /&gt;&lt;BR /&gt;Remote Port Status:&lt;BR /&gt;&lt;BR /&gt;PORT LACP TRUNK PORT LACP LACP&lt;BR /&gt;NUMB ENABLED GROUP STATUS PARTNER STATUS&lt;BR /&gt;---- ------- ------- ------- ------- -------&lt;BR /&gt;3 Active Trk3 Down No Success&lt;BR /&gt;4 Active Trk4 Down No Success&lt;BR /&gt;5 Active Trk5 Down No Success&lt;BR /&gt;6 Active Trk6 Down No Success&lt;BR /&gt;25 Active Trk25 Up Yes Success</description>
      <pubDate>Mon, 11 May 2009 09:25:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/distributed-trunking/m-p/4417163#M18495</guid>
      <dc:creator>O.H.M</dc:creator>
      <dc:date>2009-05-11T09:25:09Z</dc:date>
    </item>
    <item>
      <title>Re: Distributed Trunking</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/distributed-trunking/m-p/4417164#M18496</link>
      <description>You can find distributed trunking explained in the training of the 6600 Datacenter switch:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://cdn.procurve.com/training/technicaltraining/DataCenter6600/coursedata/controller.htm" target="_blank"&gt;http://cdn.procurve.com/training/technicaltraining/DataCenter6600/coursedata/controller.htm&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 12 May 2009 06:41:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/distributed-trunking/m-p/4417164#M18496</guid>
      <dc:creator>Sietze Reitsma</dc:creator>
      <dc:date>2009-05-12T06:41:38Z</dc:date>
    </item>
  </channel>
</rss>

