<?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: Network Configuration Opinion Requested from Experts in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/network-configuration-opinion-requested-from-experts/m-p/6939004#M33514</link>
    <description>&lt;P&gt;I would have a few problems with that design, eg,&lt;/P&gt;&lt;P&gt;- Server VLAN spanned to Access switrches.&lt;/P&gt;&lt;P&gt;- Access VLANs spanned to Servers&lt;/P&gt;&lt;P&gt;- DMZ VLAN spanned to internal servers.&lt;/P&gt;&lt;P&gt;- internal VLANs spanned across the core switch out to gateway devices, eg, 40, 47, 55&lt;/P&gt;&lt;P&gt;- i don't know what the "gateway" VLAN is, but once again this VLAN is spanned across the core&lt;/P&gt;&lt;P&gt;&amp;nbsp;- you have 2 gateways, so you would normally assume some kind of resilient setup, but you have a slightly different set of VLANs trunked to each.&lt;/P&gt;&lt;P&gt;I think you need to rethink your understanding of the purpose of VLANs - a VLAN is used to manage a broadcast segment.&amp;nbsp;&lt;BR /&gt;The golden rule with VLANs is you should span each VLAN&amp;nbsp;to the least possible number of switches, and each switch should have the least possible number of VLANs spanned to it.&lt;/P&gt;&lt;P&gt;So, a server VLAN should encompass a limited number of server access switches and be spanned to the core, nowhere else.&lt;/P&gt;&lt;P&gt;An access VLAN should be restricted to one switch, stack, or wiring closet, and be spanned to the core switch for routing.&lt;/P&gt;&lt;P&gt;DMZ devices should be seperated from production devices by a firewall.&lt;/P&gt;</description>
    <pubDate>Fri, 10 Feb 2017 00:13:48 GMT</pubDate>
    <dc:creator>Vince-Whirlwind</dc:creator>
    <dc:date>2017-02-10T00:13:48Z</dc:date>
    <item>
      <title>Network Configuration Opinion Requested from Experts</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/network-configuration-opinion-requested-from-experts/m-p/6938890#M33513</link>
      <description>&lt;P&gt;Hello all I'm looking for a bit of advise.&lt;/P&gt;&lt;P&gt;Please see the attached network topology, I'm looking for opinions on the &lt;STRONG&gt;best configuration based on performance and security&lt;/STRONG&gt;. &amp;nbsp;I welcome any suggestions that the experts on the forum can provide to assist with this config.&lt;/P&gt;&lt;P&gt;I would also welcome any suggestions to avoid bottleneck or loops.&lt;/P&gt;&lt;P&gt;Thanks in Advance,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Feb 2017 18:44:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/network-configuration-opinion-requested-from-experts/m-p/6938890#M33513</guid>
      <dc:creator>MCG43</dc:creator>
      <dc:date>2017-02-09T18:44:10Z</dc:date>
    </item>
    <item>
      <title>Re: Network Configuration Opinion Requested from Experts</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/network-configuration-opinion-requested-from-experts/m-p/6939004#M33514</link>
      <description>&lt;P&gt;I would have a few problems with that design, eg,&lt;/P&gt;&lt;P&gt;- Server VLAN spanned to Access switrches.&lt;/P&gt;&lt;P&gt;- Access VLANs spanned to Servers&lt;/P&gt;&lt;P&gt;- DMZ VLAN spanned to internal servers.&lt;/P&gt;&lt;P&gt;- internal VLANs spanned across the core switch out to gateway devices, eg, 40, 47, 55&lt;/P&gt;&lt;P&gt;- i don't know what the "gateway" VLAN is, but once again this VLAN is spanned across the core&lt;/P&gt;&lt;P&gt;&amp;nbsp;- you have 2 gateways, so you would normally assume some kind of resilient setup, but you have a slightly different set of VLANs trunked to each.&lt;/P&gt;&lt;P&gt;I think you need to rethink your understanding of the purpose of VLANs - a VLAN is used to manage a broadcast segment.&amp;nbsp;&lt;BR /&gt;The golden rule with VLANs is you should span each VLAN&amp;nbsp;to the least possible number of switches, and each switch should have the least possible number of VLANs spanned to it.&lt;/P&gt;&lt;P&gt;So, a server VLAN should encompass a limited number of server access switches and be spanned to the core, nowhere else.&lt;/P&gt;&lt;P&gt;An access VLAN should be restricted to one switch, stack, or wiring closet, and be spanned to the core switch for routing.&lt;/P&gt;&lt;P&gt;DMZ devices should be seperated from production devices by a firewall.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Feb 2017 00:13:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/network-configuration-opinion-requested-from-experts/m-p/6939004#M33514</guid>
      <dc:creator>Vince-Whirlwind</dc:creator>
      <dc:date>2017-02-10T00:13:48Z</dc:date>
    </item>
  </channel>
</rss>

