<?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 switch routing and vlan in Network Architecture &amp; Design</title>
    <link>https://community.extremenetworks.com/t5/network-architecture-design/switch-routing-and-vlan/m-p/13465#M869</link>
    <description>Hello everyone I have two Network Switches (AT) and one firewall (Sonicwall Tz600). i have configured 10 different vlans on the both switches. assign ip on vlans. now my question is if i configure vlan same ip on both switch like vlan20 ip 192.168.20.1 same on the other? i configured and i am able to ping but want to ask as confusion. second i configured trunk between switches and LACP Trunk means 2 ports lacp trunk on both switches. what is the best practice.? also if i want internet on client with switch gatway.</description>
    <pubDate>Fri, 22 Jan 2016 17:35:00 GMT</pubDate>
    <dc:creator>umair</dc:creator>
    <dc:date>2016-01-22T17:35:00Z</dc:date>
    <item>
      <title>switch routing and vlan</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/switch-routing-and-vlan/m-p/13465#M869</link>
      <description>Hello everyone I have two Network Switches (AT) and one firewall (Sonicwall Tz600). i have configured 10 different vlans on the both switches. assign ip on vlans. now my question is if i configure vlan same ip on both switch like vlan20 ip 192.168.20.1 same on the other? i configured and i am able to ping but want to ask as confusion. second i configured trunk between switches and LACP Trunk means 2 ports lacp trunk on both switches. what is the best practice.? also if i want internet on client with switch gatway.</description>
      <pubDate>Fri, 22 Jan 2016 17:35:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/switch-routing-and-vlan/m-p/13465#M869</guid>
      <dc:creator>umair</dc:creator>
      <dc:date>2016-01-22T17:35:00Z</dc:date>
    </item>
    <item>
      <title>RE: switch routing and vlan</title>
      <link>https://community.extremenetworks.com/t5/network-architecture-design/switch-routing-and-vlan/m-p/13466#M870</link>
      <description>Hi Umair&lt;BR /&gt;
&lt;BR /&gt;
Just to clarify. Are you assigning the same IP address ie 192.168.20.1/xx on 2 different switches? If yes, you'd need to change that. Use one switch as routing mechanism with the other as only a layer 2 extension. Are you attempting to build a redundant topology? If yes, consider MSTP. Do the switches support VRRP?&lt;BR /&gt;
&lt;BR /&gt;
Looking at the LACP trunks. What specific switch model  are you using?&lt;BR /&gt;
&lt;BR /&gt;
As for the routing. You'll have routing interface configured on the switch. Ie &lt;BR /&gt;
&lt;BR /&gt;
VLAN10=192.168.10.1/xx&lt;BR /&gt;
VLAN20=192.168.20.1/xx&lt;BR /&gt;
VLAN30=192.168.30.1/xx &lt;BR /&gt;
&lt;BR /&gt;
and so on&lt;BR /&gt;
&lt;BR /&gt;
You can then create a final VLAN=Internet and configure a port as access (untagged) that will connect to your firewall. Let's say the firewall's IP address is 10.10.10.254/24. Configure a routing interface on the switch as 10.10.10.1/24 as the default next-hop needs to be in the same subnet. &lt;BR /&gt;
&lt;BR /&gt;
You'll next configure a default route as follows:&lt;BR /&gt;
0.0.0.0/0 10.10.10.254 to match all outbound traffic.&lt;BR /&gt;
&lt;BR /&gt;
On the firewall you'd need reverse route to each of the internal subnets. The next hop from the firewall's perspective would the routing interface in the internet VLAN.&lt;BR /&gt;
&lt;BR /&gt;
192.168.10.0/xx 10.10.10.1&lt;BR /&gt;
192.168.20.0/xx 10.10.10.1&lt;BR /&gt;
192.168.30.0/xx 10.10.10.1&lt;BR /&gt;
&lt;BR /&gt;
And so on.  &lt;BR /&gt;
&lt;BR /&gt;
Hope this helps. Please send me answer to questions above and I'll provide more detailed configuration. &lt;BR /&gt;
&lt;BR /&gt;
Regards,&lt;BR /&gt;
Francois&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Fri, 22 Jan 2016 18:15:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/network-architecture-design/switch-routing-and-vlan/m-p/13466#M870</guid>
      <dc:creator>Francois_Scheun</dc:creator>
      <dc:date>2016-01-22T18:15:00Z</dc:date>
    </item>
  </channel>
</rss>

