<?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: VLAN on switch -- Do client machines need to be tagged for VLAN? in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-on-switch-do-client-machines-need-to-be-tagged-for-vlan/m-p/4793624#M26115</link>
    <description>Dear sierradump,&lt;BR /&gt;&lt;BR /&gt;192.168.1.x , 192.168.2.x these are two different networks Not a different subnets.&lt;BR /&gt;&lt;A href="http://welcome.hp-ww.com/img/s.gif" target="_blank"&gt;http://welcome.hp-ww.com/img/s.gif&lt;/A&gt;&lt;BR /&gt;After creating the vlans in a switch we should assign those interfaces to the particular vlan.&lt;BR /&gt;You can add interface to more than one vlan is possible.&lt;BR /&gt;&lt;BR /&gt;Cheers..!&lt;BR /&gt;Arun&lt;BR /&gt;</description>
    <pubDate>Wed, 01 Jun 2011 03:15:46 GMT</pubDate>
    <dc:creator>ARUNPRAKASH</dc:creator>
    <dc:date>2011-06-01T03:15:46Z</dc:date>
    <item>
      <title>VLAN on switch -- Do client machines need to be tagged for VLAN?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-on-switch-do-client-machines-need-to-be-tagged-for-vlan/m-p/4793622#M26113</link>
      <description>I am planning a network to support 500+ PCs in an office environment. In order to minimize noise on the network - I plan to split the office up into subnets.  (i.e. Marketing, Sales, Accounting, etc...).  Each Dept. will have it's own subnet (192.168.1.x , 192.168.2.x , etc...). &lt;BR /&gt;&lt;BR /&gt;Since all traffic is in the same building, I wish to utilize VLANS on my switch to limit noisy broadcasts... Each subnet will have it's own VLAN.  i.e. 192.168.1.x would be VLAN 1, 192.168.2.x would be VLAN 2 etc... &lt;BR /&gt;&lt;BR /&gt;I have the VLANs configured on the router, and corresponding ports on the switch.  &lt;BR /&gt;&lt;BR /&gt;My question is, say I have a PC that needs to be plugged into port 13 (tagged VLAN 4) on my switch -- do I have to set the NIC on the PC to be on VLAN 4?  (port 13 would ONLY be tagged for that SINGLE VLAN.)</description>
      <pubDate>Tue, 31 May 2011 02:54:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-on-switch-do-client-machines-need-to-be-tagged-for-vlan/m-p/4793622#M26113</guid>
      <dc:creator>sierradump</dc:creator>
      <dc:date>2011-05-31T02:54:44Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN on switch -- Do client machines need to be tagged for VLAN?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-on-switch-do-client-machines-need-to-be-tagged-for-vlan/m-p/4793623#M26114</link>
      <description>Generally, device ports (computers, printers, cameras, etc) are 'untagged' into a vlan.&lt;BR /&gt;&lt;BR /&gt;Switch-to-switch connections have their ports 'tagged' into all the vlans necessary in order to distribute the vlans throughout the network.&lt;BR /&gt;&lt;BR /&gt;When ports are assigned to a vlan (untagged &amp;amp; tagged) that is an isolated broadcast domain, hence the "splitting up" the network. Even though a port may be assigned to multiple vlans (tagged) it keeps the traffic isolated due to the knowledge it has of the vlan's traffic (the "tag"). &lt;BR /&gt;&lt;BR /&gt;Port memebership rules for vlans:&lt;BR /&gt;1) a port must be assigned to a vlan (tag or untag)&lt;BR /&gt;2) a port can only be "untagged" into a max of 1 vlan at a time&lt;BR /&gt;3) a port can be "tagged" into many vlans&lt;BR /&gt;&lt;BR /&gt;hth...Jeff</description>
      <pubDate>Tue, 31 May 2011 03:53:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-on-switch-do-client-machines-need-to-be-tagged-for-vlan/m-p/4793623#M26114</guid>
      <dc:creator>Jeff Carrell</dc:creator>
      <dc:date>2011-05-31T03:53:29Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN on switch -- Do client machines need to be tagged for VLAN?</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-on-switch-do-client-machines-need-to-be-tagged-for-vlan/m-p/4793624#M26115</link>
      <description>Dear sierradump,&lt;BR /&gt;&lt;BR /&gt;192.168.1.x , 192.168.2.x these are two different networks Not a different subnets.&lt;BR /&gt;&lt;A href="http://welcome.hp-ww.com/img/s.gif" target="_blank"&gt;http://welcome.hp-ww.com/img/s.gif&lt;/A&gt;&lt;BR /&gt;After creating the vlans in a switch we should assign those interfaces to the particular vlan.&lt;BR /&gt;You can add interface to more than one vlan is possible.&lt;BR /&gt;&lt;BR /&gt;Cheers..!&lt;BR /&gt;Arun&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Jun 2011 03:15:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-on-switch-do-client-machines-need-to-be-tagged-for-vlan/m-p/4793624#M26115</guid>
      <dc:creator>ARUNPRAKASH</dc:creator>
      <dc:date>2011-06-01T03:15:46Z</dc:date>
    </item>
  </channel>
</rss>

