<?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 Some confusion with trunking in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/some-confusion-with-trunking/m-p/4425426#M18587</link>
    <description>Coming from a Cisco background, I find the HP implementation a bit counter-intuitive. It is my understanding that ports set up as trunks (in this case LACP trunks) should be "tagged" for ALL VLANs, including the "default" VLAN1.&lt;BR /&gt;&lt;BR /&gt;But I have seen configurations in which to HP switches are connected and configured with 3 vlans. The default and two others. The client machines (workstations and servers) are assigned to vlans 2 &amp;amp; 3, and the trunk between the switches is tagged for these vlans.&lt;BR /&gt;&lt;BR /&gt;However, the same trunk is not carrying tagged traffic for vlan1 (the default). Example:&lt;BR /&gt;&lt;BR /&gt;vlan 1 &lt;BR /&gt;   name "DEFAULT_VLAN" &lt;BR /&gt;   untagged B1-B4 &lt;BR /&gt;   ip address dhcp-bootp &lt;BR /&gt;   no untagged A1-A24 &lt;BR /&gt;   no untagged C1-C24 &lt;BR /&gt;   exit &lt;BR /&gt;&lt;BR /&gt;So here is my question ... If client machines are assigned to vlan 1 on both switches, should the trunk be tagged for these frames? In other words, should the above config look something like this:&lt;BR /&gt;&lt;BR /&gt;vlan 1 &lt;BR /&gt;   name "DEFAULT_VLAN" &lt;BR /&gt;   untagged B1-B4 &lt;BR /&gt;   ip address dhcp-bootp &lt;BR /&gt;   no untagged A1-A24 &lt;BR /&gt;   no untagged C1-C24 &lt;BR /&gt;   tagged Trk1&lt;BR /&gt;   exit &lt;BR /&gt;&lt;BR /&gt;Any info would help greatly!&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Sun, 24 May 2009 01:19:59 GMT</pubDate>
    <dc:creator>Colin Higgins</dc:creator>
    <dc:date>2009-05-24T01:19:59Z</dc:date>
    <item>
      <title>Some confusion with trunking</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/some-confusion-with-trunking/m-p/4425426#M18587</link>
      <description>Coming from a Cisco background, I find the HP implementation a bit counter-intuitive. It is my understanding that ports set up as trunks (in this case LACP trunks) should be "tagged" for ALL VLANs, including the "default" VLAN1.&lt;BR /&gt;&lt;BR /&gt;But I have seen configurations in which to HP switches are connected and configured with 3 vlans. The default and two others. The client machines (workstations and servers) are assigned to vlans 2 &amp;amp; 3, and the trunk between the switches is tagged for these vlans.&lt;BR /&gt;&lt;BR /&gt;However, the same trunk is not carrying tagged traffic for vlan1 (the default). Example:&lt;BR /&gt;&lt;BR /&gt;vlan 1 &lt;BR /&gt;   name "DEFAULT_VLAN" &lt;BR /&gt;   untagged B1-B4 &lt;BR /&gt;   ip address dhcp-bootp &lt;BR /&gt;   no untagged A1-A24 &lt;BR /&gt;   no untagged C1-C24 &lt;BR /&gt;   exit &lt;BR /&gt;&lt;BR /&gt;So here is my question ... If client machines are assigned to vlan 1 on both switches, should the trunk be tagged for these frames? In other words, should the above config look something like this:&lt;BR /&gt;&lt;BR /&gt;vlan 1 &lt;BR /&gt;   name "DEFAULT_VLAN" &lt;BR /&gt;   untagged B1-B4 &lt;BR /&gt;   ip address dhcp-bootp &lt;BR /&gt;   no untagged A1-A24 &lt;BR /&gt;   no untagged C1-C24 &lt;BR /&gt;   tagged Trk1&lt;BR /&gt;   exit &lt;BR /&gt;&lt;BR /&gt;Any info would help greatly!&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 24 May 2009 01:19:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/some-confusion-with-trunking/m-p/4425426#M18587</guid>
      <dc:creator>Colin Higgins</dc:creator>
      <dc:date>2009-05-24T01:19:59Z</dc:date>
    </item>
    <item>
      <title>Re: Some confusion with trunking</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/some-confusion-with-trunking/m-p/4425427#M18588</link>
      <description>Colin,&lt;BR /&gt;&lt;BR /&gt;There are three possible options for Trk1:&lt;BR /&gt;&lt;BR /&gt;vlan 1 - send no traffic on VLAN 1&lt;BR /&gt;name "DEFAULT_VLAN" &lt;BR /&gt;no untagged Trk1&lt;BR /&gt;&lt;BR /&gt;vlan 1 - send untagged traffic on VLAN 1&lt;BR /&gt;name "DEFAULT_VLAN" &lt;BR /&gt;untagged Trk1&lt;BR /&gt;&lt;BR /&gt;vlan 1 - send tagged traffic on VLAN 1&lt;BR /&gt;name "DEFAULT_VLAN" &lt;BR /&gt;tagged Trk1&lt;BR /&gt;&lt;BR /&gt;In you case option 2 or option 3 is valid for you client systems and you chose depending on whether you have tagged VLAN 1 traffic on your client system,&lt;BR /&gt;&lt;BR /&gt;Note the LACP trunk port members do not get listed individually in the VLAN tagging configuration.&lt;BR /&gt;&lt;BR /&gt;Jed</description>
      <pubDate>Mon, 25 May 2009 06:27:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/some-confusion-with-trunking/m-p/4425427#M18588</guid>
      <dc:creator>JedE</dc:creator>
      <dc:date>2009-05-25T06:27:54Z</dc:date>
    </item>
  </channel>
</rss>

