<?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 Re: Tagged vs. Untagged in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/4004334#M11397</link>
    <description>Disregard the last question.  I read the last response again and now I am clear.  &lt;BR /&gt;&lt;BR /&gt;Thanks to all who responded.</description>
    <pubDate>Tue, 22 May 2007 07:00:44 GMT</pubDate>
    <dc:creator>Robert Peirce</dc:creator>
    <dc:date>2007-05-22T07:00:44Z</dc:date>
    <item>
      <title>Tagged vs. Untagged</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/4004330#M11393</link>
      <description>Can anyone explain the true purpose of tagged vs. untagged members of a VLAN?  A real world example would be very helpful.  I have read the documentation, but it is not really clear.   &lt;BR /&gt;&lt;BR /&gt;Any help with this will be greatly appreciated.</description>
      <pubDate>Mon, 21 May 2007 13:29:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/4004330#M11393</guid>
      <dc:creator>Robert Peirce</dc:creator>
      <dc:date>2007-05-21T13:29:09Z</dc:date>
    </item>
    <item>
      <title>Re: Tagged vs. Untagged</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/4004331#M11394</link>
      <description>The terminology of tagging is confusing if you don't have some understanding of how the protocol works. Have a look and see whether this clears up anything for you:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://en.wikipedia.org/wiki/IEEE_802.1Q" target="_blank"&gt;http://en.wikipedia.org/wiki/IEEE_802.1Q&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;But anyways, an untagged port in a VLAN is a physical member of that VLAN, ie. when you plug your host into that port it is physically connected to that VLAN (also known as an "access port" in Cisco terminology).&lt;BR /&gt;&lt;BR /&gt;A tagged port will normally carry traffic for multiple VLANs from the switch to other network devices such as an upstream router or an edge switch (In Cisco terminology this is called trunking, HP have no specific term for it).&lt;BR /&gt;&lt;BR /&gt;Hope this clears any confusion for you!&lt;BR /&gt;</description>
      <pubDate>Mon, 21 May 2007 17:32:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/4004331#M11394</guid>
      <dc:creator>Joel Belizario</dc:creator>
      <dc:date>2007-05-21T17:32:21Z</dc:date>
    </item>
    <item>
      <title>Re: Tagged vs. Untagged</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/4004332#M11395</link>
      <description>Hi Robert,&lt;BR /&gt;&lt;BR /&gt;In the simplest form, I used to remember a 'Tagged' port as an inter-switch link and an 'Untagged' port as a host port.&lt;BR /&gt;&lt;BR /&gt;Basically, its all about the VLAN information that gets 'tagged'into the Ethernet frame. &lt;BR /&gt;&lt;BR /&gt;When you configure a port as 'Tagged' you are telling the switch to place an 802.1q tag in the frame that can identify the VLAN that the frame came from.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;That way, the switch that receives the frame knows which VLAN to send the Frame to.&lt;BR /&gt;&lt;BR /&gt;So if you have 2 switches, each with ports 1-10 in VLAN 10 and ports 11-22 in VLAN 20.&lt;BR /&gt;&lt;BR /&gt;You want PC's to be in VLAN 10 and Servers to be in VLAN 20, so you would :&lt;BR /&gt;&lt;BR /&gt;VLAN10 untag ports 1-10 on each switch&lt;BR /&gt;VLAN20 untag ports 11-22 on each switch&lt;BR /&gt;&lt;BR /&gt;This sets your hosts up. You want to use interface 24 to connect the switches. &lt;BR /&gt;&lt;BR /&gt;VLAN10 tag port 24&lt;BR /&gt;VLAN20 tag port 24&lt;BR /&gt;&lt;BR /&gt;So, the Interswitch links are TAGGED and the hosts are UNTAGGED...&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 22 May 2007 02:18:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/4004332#M11395</guid>
      <dc:creator>Jonathan Axford</dc:creator>
      <dc:date>2007-05-22T02:18:30Z</dc:date>
    </item>
    <item>
      <title>Re: Tagged vs. Untagged</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/4004333#M11396</link>
      <description>Thank you for taking the time to respond.  &lt;BR /&gt;&lt;BR /&gt;I just want to be clear.  &lt;BR /&gt;&lt;BR /&gt;Are you saying that a physical ethernet cable is needs to be connected from port 20 to port 10 on the same switch to enable communication between VLAN 10 and VLAN 20?  If so, I am assuming a physical cable would only be needed if IP Routing was not enabled on the switch?    &lt;BR /&gt;&lt;BR /&gt;Thank you for your help.</description>
      <pubDate>Tue, 22 May 2007 06:56:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/4004333#M11396</guid>
      <dc:creator>Robert Peirce</dc:creator>
      <dc:date>2007-05-22T06:56:43Z</dc:date>
    </item>
    <item>
      <title>Re: Tagged vs. Untagged</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/4004334#M11397</link>
      <description>Disregard the last question.  I read the last response again and now I am clear.  &lt;BR /&gt;&lt;BR /&gt;Thanks to all who responded.</description>
      <pubDate>Tue, 22 May 2007 07:00:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/4004334#M11397</guid>
      <dc:creator>Robert Peirce</dc:creator>
      <dc:date>2007-05-22T07:00:44Z</dc:date>
    </item>
    <item>
      <title>Re: Tagged vs. Untagged</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/4004335#M11398</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;if you want that a port only belongs to one VLAN, set the port to UNTAGGED. If you want a port in more then one VLAN, you need to set it to TAGGED. If a host should belong to more than one VLAN, the port must be TAGGED (for example an VMware ESX Server with guests that belongs to different VLANs). If you want to uplink a switch to another, you need to set the uplink port to TAGGED, for each VLAN which should be acccessable over the uplink.&lt;BR /&gt;&lt;BR /&gt;Kind regards,&lt;BR /&gt;Patrick</description>
      <pubDate>Tue, 22 May 2007 08:29:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/4004335#M11398</guid>
      <dc:creator>Patrick Terlisten</dc:creator>
      <dc:date>2007-05-22T08:29:04Z</dc:date>
    </item>
    <item>
      <title>Re: Tagged vs. Untagged</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/6642694#M32385</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Please I have a problem of inter-vlan routing, I have a core and two switches in each room floor. &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I created a vlan 11 and I give him an IP address and i enabled the ip routing in the core and in the switches in each room floor and I can not have the router with another VLAN and most all other vlan are not router, please how do ??? &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Below config core and a switch to floor, &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Please, I'am blocked, plz i need help &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I can not have access to the other sub networks &amp;nbsp;with the ip 11.11.1.25 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;======================================== &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;show running-config &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Running configuration: &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;; J4819A Configuration Editor; Created on release #E.11.38 &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;hostname "HP ProCurve Switch 5308xl" &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;snmp-server contact "test" &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;mirror-port D11 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;module 6 type J4907A &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;module 5 type J4907A &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;module 4 type J4907A &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;module 1 type J4878B &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;module 2 type J4878B &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;module 3 type J4878B &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ip routing &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;snmp-server community "public" Unrestricted &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;vlan 1 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;name "DEFAULT_VLAN" &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;untagged A1-A4,B1-B4,C1-C4,D15-D16,E1-E16,F3-F4,F6-F9,F11-F16 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ip address 172.16.X.1 255.255.0.0 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ip address 10.10.X.250 255.255.255.0 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;no untagged D1-D14,F1-F2,F5,F10 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;exit &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;vlan 2 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;name "WIFI" &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;untagged F1-F2,F5,F10 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;tagged A4,B4 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;exit &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;vlan 100 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;name "DMZ" &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;untagged D6-D7,D13-D14 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ip address 192.168.X.254 255.255.255.0 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;exit &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;vlan 200 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;name "INTERNET" &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;untagged D1-D5,D8-D12 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ip address 192.168.X.254 255.255.255.0 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;monitor &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;exit &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;vlan 3 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;name "MANAGEMENT" &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ip address 172.17.X.1 255.255.0.0 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;exit &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Vlan 11 &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;name "test" &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;11.11.1.254 255.255.255.0 &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;exit &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;banner motd "This is a private system maintained by the Allied Widget Corporatio &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;n. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Unauthorized use of this system can result in civil and criminal penalities !" &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;spanning-tree &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;spanning-tree priority 2 &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;router rip &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;exit &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;vlan 1 &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ip rip &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ip rip receive V1-only &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ip rip send V1-only &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;exit &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;vlan 100 &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ip rip &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ip rip receive V1-only &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ip rip send V1-only &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;exit &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;============================================ &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;floor switch: &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ProCurve 2910al-48G-1E-2# &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ProCurve 2910al-48G-1E-2# &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ProCurve 2910al-48G-1E-2# &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ProCurve 2910al-48G-1E-2# sh running-config &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Running configuration: &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;; J9147A Configuration Editor; Created on release #W.14.70 &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;hostname "ProCurve 2910al-48G-1E-2" &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;module 1 type J9147A &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ip routing &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;vlan 1 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;name "DEFAULT_VLAN" &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;untagged 1-48 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ip address 172.16.X.5 255.255.0.0 &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;exit &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;gvrp &amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;banner motd "This is a private system maintained by the Allied Widget Corporation.\nUnauthorized use of this system can result in ci &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;vil and criminal penalities !" &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;snmp-server community "public" unrestricted &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;spanning-tree force-version rstp-operation &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;password manager &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;password operator &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ProCurve 2910al-48G-1E-2 &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;plz help me&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Oct 2014 17:43:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/6642694#M32385</guid>
      <dc:creator>splouxe</dc:creator>
      <dc:date>2014-10-09T17:43:54Z</dc:date>
    </item>
    <item>
      <title>Re: Tagged vs. Untagged</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/6654354#M32397</link>
      <description>&lt;P&gt;Well this no secret :9&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Its just like this:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;tagged - means that packets that have a valid vlan tag for this vlan id will be accepted on this port. packets without vlan tag will not be accepted. The Switch will not change anything on the vlan tagging of the packet.&lt;/P&gt;&lt;P&gt;This means that the client is responsible for the tagging.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;untagged - means that if there is packets on this port that have no vlan id set will have their vlan id tag set to this vlan by the switch. Packets that do have a vlan tag with this vlan id will bei ignored.&lt;/P&gt;&lt;P&gt;This means that the client must not tag packets for this vlan.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;no/forbid means that any packets tagged for this vlan will be ignored. Packets without tag will be handled by the untagged vlan on this port like said above.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Due to this any Port must be untagged in one vlan!&lt;/P&gt;&lt;P&gt;Thus any port can be tagged in various vlans!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;hth&lt;/P&gt;&lt;P&gt;Sebastian&lt;/P&gt;</description>
      <pubDate>Thu, 23 Oct 2014 15:56:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/6654354#M32397</guid>
      <dc:creator>sw2090</dc:creator>
      <dc:date>2014-10-23T15:56:34Z</dc:date>
    </item>
    <item>
      <title>Re: Tagged vs. Untagged</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/6747477#M32645</link>
      <description>&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;I have some more questions about this.&lt;/P&gt;&lt;P&gt;Here is the configuration I have :&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;vlan 1&lt;/P&gt;&lt;P&gt;&amp;nbsp;name "DATA"&lt;/P&gt;&lt;P&gt;&amp;nbsp;untagged 1-28&lt;/P&gt;&lt;P&gt;vlan 2&lt;/P&gt;&lt;P&gt;&amp;nbsp;name "TEL"&lt;/P&gt;&lt;P&gt;&amp;nbsp;tagged 1-28&lt;/P&gt;&lt;P&gt;vlan 3&lt;/P&gt;&lt;P&gt;&amp;nbsp;name "GUEST"&lt;/P&gt;&lt;P&gt;&amp;nbsp;tagged 25-28&lt;/P&gt;&lt;P&gt;vlan 4&lt;/P&gt;&lt;P&gt;&amp;nbsp;name "INTERCO"&lt;/P&gt;&lt;P&gt;&amp;nbsp;tagged 25-28&lt;/P&gt;&lt;P&gt;vlan 5&lt;/P&gt;&lt;P&gt;&amp;nbsp;name "INTERNET"&lt;/P&gt;&lt;P&gt;&amp;nbsp;tagged 25-28&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Which port is in Cisco access mode ?&lt;/P&gt;&lt;P&gt;Which port is is Cisco trunk mode ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your answers&lt;/P&gt;</description>
      <pubDate>Thu, 21 May 2015 10:33:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/6747477#M32645</guid>
      <dc:creator>PierrotMoto</dc:creator>
      <dc:date>2015-05-21T10:33:37Z</dc:date>
    </item>
    <item>
      <title>Re: Tagged vs. Untagged</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/6747705#M32646</link>
      <description>&lt;P&gt;In your case, they are all trunk ports with a native VLAN 1.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;An access port is a port that only carries untagged traffic. It could be untagged traffic in any VLAN.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A trunk port is a port that carries more than one VLAN. All VLANs can be tagged on the port or you can have a up to one untagged VLAN, called the native VLAN in Cisco.&lt;/P&gt;</description>
      <pubDate>Thu, 21 May 2015 15:57:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/6747705#M32646</guid>
      <dc:creator>EricAtHP</dc:creator>
      <dc:date>2015-05-21T15:57:38Z</dc:date>
    </item>
    <item>
      <title>Re: Tagged vs. Untagged</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/6819136#M32907</link>
      <description>&lt;P&gt;Real World Example :&lt;/P&gt;&lt;P&gt;I think of it as baggage at an airport, if you only have one destination you don't need a luggage tag, therefore untagged. If it needs to transit through then it will need a label to show the destination and therefore tagged. Switches are your airports, so every uplink or downlink transits between airports and therefore will have tagged vlans. Every switch to switch link generally has the default vlan untagged and all others tagged for transit.&lt;/P&gt;&lt;P&gt;Computers rarely understand vlans (not servers) and so their ports will untagged in a single vlan. IP Phones and other smart devices generally know about vlans so if you have a daisy chain of an IP phone and then a computer the port will most likely have a tagged VoiP vlan and an untagged computer vlan. I generally use the default vlan as a management vlan with it's own separate IP range, in our case 192.168.xxx.xxx and the work vlans in a class B subnet, if you use a flat IP range for all then you are wasting the power of the HP Procurve.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Dec 2015 08:15:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/6819136#M32907</guid>
      <dc:creator>TheRoyalSchool</dc:creator>
      <dc:date>2015-12-17T08:15:46Z</dc:date>
    </item>
    <item>
      <title>Re: Tagged vs. Untagged</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/6821696#M32911</link>
      <description>&lt;P&gt;In your reply you say "&lt;SPAN&gt;untagged - means that if there is packets on this port that have no vlan id set will have their vlan id tag set to this vlan by the switch. Packets that do have a vlan tag with this vlan id will bei ignored." Do you mean dropped when you say ignored or passed on as received with the VLAN tagging intact?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Jan 2016 16:46:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/6821696#M32911</guid>
      <dc:creator>Kroger_HP_rep</dc:creator>
      <dc:date>2016-01-04T16:46:03Z</dc:date>
    </item>
    <item>
      <title>Re: Tagged vs. Untagged</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/6841354#M32965</link>
      <description>&lt;P&gt;Hi. Ignored packets will be DROP without communication.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Mar 2016 14:19:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/6841354#M32965</guid>
      <dc:creator>lucsis</dc:creator>
      <dc:date>2016-03-14T14:19:07Z</dc:date>
    </item>
    <item>
      <title>Re: Tagged vs. Untagged</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/6852834#M33006</link>
      <description>&lt;P&gt;So, a followup clarification, Eric:&lt;BR /&gt;&lt;BR /&gt;Any given physical switchport can have&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Zero to many tagged VLANs&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;*and*&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Zero or one untagged VLANs&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;at the same time; that is correct?&lt;/P&gt;</description>
      <pubDate>Thu, 21 Apr 2016 17:55:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/6852834#M33006</guid>
      <dc:creator>Baylink</dc:creator>
      <dc:date>2016-04-21T17:55:19Z</dc:date>
    </item>
    <item>
      <title>Re: Tagged vs. Untagged</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/7034753#M33967</link>
      <description>&lt;P&gt;Can some one please explain this.&amp;nbsp;&lt;/P&gt;&lt;P&gt;int range fa0/1-22&lt;/P&gt;&lt;P&gt;Switchprot mode access&amp;nbsp;&lt;/P&gt;&lt;P&gt;switchport access vlan 10&lt;/P&gt;&lt;P&gt;switchport voice vlan 20&lt;/P&gt;&lt;P&gt;int fa0/23&lt;/P&gt;&lt;P&gt;switchmode mode turnk&lt;/P&gt;&lt;P&gt;switchport trunk allowed vlan 10, 20&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can some one please help me it's equivlant in HP switches.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Feb 2019 15:41:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/7034753#M33967</guid>
      <dc:creator>malkana</dc:creator>
      <dc:date>2019-02-14T15:41:51Z</dc:date>
    </item>
    <item>
      <title>Re: Tagged vs. Untagged</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/7056635#M34040</link>
      <description>&lt;P&gt;1- int fa 0/23........ means you have entered into port configuration(port 23 on switch ) of switch.&lt;/P&gt;&lt;P&gt;2- switchport model access.......means you have activited access mode on port.&lt;/P&gt;&lt;P&gt;3-switchport access vlan 10....... means you have configured vlan 10 on port 0/23.&lt;/P&gt;&lt;P&gt;4-switchport voice vlan 20.......means now you have configured vlan 20 for VOIP(Voice Over IP) phones on same port(0/23).&lt;/P&gt;</description>
      <pubDate>Sat, 27 Jul 2019 08:00:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/7056635#M34040</guid>
      <dc:creator>hamza-123</dc:creator>
      <dc:date>2019-07-27T08:00:12Z</dc:date>
    </item>
    <item>
      <title>Re: Tagged vs. Untagged</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/7056637#M34041</link>
      <description>&lt;P&gt;1- int fa 0/23 means you have entered into port configuration of switch.&lt;/P&gt;&lt;P&gt;2- switchport mode trunk...means now u are using trunk port and u are configuring trunk mode on port 23(trunk mode allow more than 1 vlan to pass through 1 port of swtich to pc(computer))..&lt;/P&gt;&lt;P&gt;3 switchport trunk allowed vlan 10 ,20.......means now u are configuring vlan 10 and vlan 20 on port 23 of switch...and allow the port to send two vlans(10,20) to another switch.....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-&amp;gt;&amp;gt;&amp;gt;&amp;nbsp; must go through the trunk and access mode on google....make your concepts clear before start of this&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 27 Jul 2019 08:07:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/7056637#M34041</guid>
      <dc:creator>hamza-123</dc:creator>
      <dc:date>2019-07-27T08:07:06Z</dc:date>
    </item>
    <item>
      <title>Re: Tagged vs. Untagged</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/7056640#M34043</link>
      <description>&lt;P&gt;Moreover.....&lt;/P&gt;&lt;P&gt;int fa0/23 stands for.....interface fastethernet 0/23..&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;explaination.....infaceface means which bport on switch......fastethernet means you are using port of fastethernet which gives u speed of 100mpbs means normal speed not more than GigabitEthernet port.........0/23 means 0 means nothing here but 23 means swtich port number ....like now u have switch of cisco that having 24 lan ports...and u are using 23 port no for configuration.....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Glad to help u ,If further help needed&lt;/P&gt;&lt;P&gt;contact here,&lt;/P&gt;&lt;P&gt;I will delight to help u.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 27 Jul 2019 09:19:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/tagged-vs-untagged/m-p/7056640#M34043</guid>
      <dc:creator>hamza-123</dc:creator>
      <dc:date>2019-07-27T09:19:55Z</dc:date>
    </item>
  </channel>
</rss>

