<?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 Routing Problem in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-routing-problem/m-p/5021453#M27345</link>
    <description>Hi&lt;BR /&gt;&lt;BR /&gt;The 2650 can easily route between its Vlans without any problems.&lt;BR /&gt;&lt;BR /&gt;Usually, for a Vlan has internet connectivity (Vlan1 i assume in your case), a default route command should be entered on the 2650 switch global configuration, and on the router side, you should add 3 Static routes to your Vlan2,3 and 4 (Route Back).&lt;BR /&gt;Example, if you have 4 Vlans with these IP addresses, &lt;BR /&gt;Vlan1: 10.1.1.1&lt;BR /&gt;Vlan2: 10.1.2.1&lt;BR /&gt;Vlan3: 10.1.3.1&lt;BR /&gt;Vlan4: 10.1.4.1&lt;BR /&gt;&lt;BR /&gt;In your case, Vlan1 has the router and Servers ...., so if this router for internet or WAN connectivity, add the following static routes:&lt;BR /&gt;&lt;BR /&gt;ip route 10.1.2.0 255.255.255.0 10.1.1.1&lt;BR /&gt;ip route 10.1.3.0 255.255.255.0 10.1.1.1&lt;BR /&gt;ip route 10.1.4.0 255.255.255.0 10.1.1.1&lt;BR /&gt;&lt;BR /&gt;or you can summarize:&lt;BR /&gt;ip route 10.1.0.0 255.255.0.0 10.1.1.1&lt;BR /&gt;&lt;BR /&gt;This will guarantee your route back, but, say you disconnected this router from the 2650, and you want simple to route between a station on Vlan4 and another on Vlan3, then you should be able to do that when you enable routing on the 2650 switch.&lt;BR /&gt;&lt;BR /&gt;Good Luck !!!</description>
    <pubDate>Sat, 06 Jan 2007 23:47:01 GMT</pubDate>
    <dc:creator>Mohieddin Kharnoub</dc:creator>
    <dc:date>2007-01-06T23:47:01Z</dc:date>
    <item>
      <title>VLAN Routing Problem</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-routing-problem/m-p/5021452#M27344</link>
      <description>I have 2650 series switches and in a mess trying to configure VLAN routing.&lt;BR /&gt;&lt;BR /&gt;Scenario&lt;BR /&gt;&lt;BR /&gt;VLAN1 - Infra VLAN&lt;BR /&gt;VLAN2 - Project1&lt;BR /&gt;VLAN3 - HR&lt;BR /&gt;VLAN4 - Rest of Organization&lt;BR /&gt;&lt;BR /&gt;VLAN1 should be able to talk to VLAN2,3 &amp;amp; 4 and vice versa since the infra VLAN will have the router, Domain controllers etc&lt;BR /&gt;&lt;BR /&gt;VLAN2 ,3 and 4 should not be able to talk to each other.&lt;BR /&gt;&lt;BR /&gt;I have been trying this on a single physical switch by segreggating the ports and unable to successfully route between the VLANs.&lt;BR /&gt;&lt;BR /&gt;Is this scenario possible without having to buy a router?&lt;BR /&gt;&lt;BR /&gt;Note* I have a single physical network.&lt;BR /&gt;&lt;BR /&gt;Eventually I will have 5 2650 48 port switches catering to 240 LAN points altogether.&lt;BR /&gt;</description>
      <pubDate>Sat, 06 Jan 2007 08:47:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-routing-problem/m-p/5021452#M27344</guid>
      <dc:creator>Rajiv Dodderi</dc:creator>
      <dc:date>2007-01-06T08:47:05Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN Routing Problem</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-routing-problem/m-p/5021453#M27345</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;The 2650 can easily route between its Vlans without any problems.&lt;BR /&gt;&lt;BR /&gt;Usually, for a Vlan has internet connectivity (Vlan1 i assume in your case), a default route command should be entered on the 2650 switch global configuration, and on the router side, you should add 3 Static routes to your Vlan2,3 and 4 (Route Back).&lt;BR /&gt;Example, if you have 4 Vlans with these IP addresses, &lt;BR /&gt;Vlan1: 10.1.1.1&lt;BR /&gt;Vlan2: 10.1.2.1&lt;BR /&gt;Vlan3: 10.1.3.1&lt;BR /&gt;Vlan4: 10.1.4.1&lt;BR /&gt;&lt;BR /&gt;In your case, Vlan1 has the router and Servers ...., so if this router for internet or WAN connectivity, add the following static routes:&lt;BR /&gt;&lt;BR /&gt;ip route 10.1.2.0 255.255.255.0 10.1.1.1&lt;BR /&gt;ip route 10.1.3.0 255.255.255.0 10.1.1.1&lt;BR /&gt;ip route 10.1.4.0 255.255.255.0 10.1.1.1&lt;BR /&gt;&lt;BR /&gt;or you can summarize:&lt;BR /&gt;ip route 10.1.0.0 255.255.0.0 10.1.1.1&lt;BR /&gt;&lt;BR /&gt;This will guarantee your route back, but, say you disconnected this router from the 2650, and you want simple to route between a station on Vlan4 and another on Vlan3, then you should be able to do that when you enable routing on the 2650 switch.&lt;BR /&gt;&lt;BR /&gt;Good Luck !!!</description>
      <pubDate>Sat, 06 Jan 2007 23:47:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-routing-problem/m-p/5021453#M27345</guid>
      <dc:creator>Mohieddin Kharnoub</dc:creator>
      <dc:date>2007-01-06T23:47:01Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN Routing Problem</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-routing-problem/m-p/5021454#M27346</link>
      <description>With the 2600 Series you will not be able to achieve this goal: "VLAN2 ,3 and 4 should not be able to talk to each other." &lt;BR /&gt;&lt;BR /&gt;Usually you would do this through ACL's which the 2600 does not support, or source-port filtering - which does not work on the 2600 when using routing. &lt;BR /&gt;&lt;BR /&gt;I would recommend you look into something like the 5300xl as your core switch instead.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 08 Jan 2007 00:26:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-routing-problem/m-p/5021454#M27346</guid>
      <dc:creator>Matt Hobbs</dc:creator>
      <dc:date>2007-01-08T00:26:19Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN Routing Problem</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-routing-problem/m-p/5021455#M27347</link>
      <description>Thanks for letting me know.Can I achieve the same scenarion by placing a firewall between the VLAN ? or another switch which can act as a router and also have ACL ?&lt;BR /&gt;&lt;BR /&gt;we have already purchased 5 of these switches and re investing in new switches may not go well with the execs.&lt;BR /&gt;&lt;BR /&gt;What other alternatives do I have ?&lt;BR /&gt;&lt;BR /&gt;Thanks in Advance.&lt;BR /&gt;</description>
      <pubDate>Mon, 08 Jan 2007 03:24:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-routing-problem/m-p/5021455#M27347</guid>
      <dc:creator>Rajiv Dodderi</dc:creator>
      <dc:date>2007-01-08T03:24:43Z</dc:date>
    </item>
    <item>
      <title>Re: VLAN Routing Problem</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-routing-problem/m-p/5021456#M27348</link>
      <description>Answer Received to my queries</description>
      <pubDate>Sat, 20 Jan 2007 06:11:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/vlan-routing-problem/m-p/5021456#M27348</guid>
      <dc:creator>Rajiv Dodderi</dc:creator>
      <dc:date>2007-01-20T06:11:23Z</dc:date>
    </item>
  </channel>
</rss>

