<?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: Help with VLAN and Routing Issues in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/help-with-vlan-and-routing-issues/m-p/4028846#M11879</link>
    <description>1. Decide which switch is going to do routing for your intranet, and only assign IP addys to the VLAN interfaces of that one; also routing should be started only on that switch (including default gateway and routing protocol - I don't see the need for two routers in the intranet; maybe you use the routing protocol with the outside). - I would decide in favor of the 5412zl&lt;BR /&gt;&lt;BR /&gt;2. port 50 is "no LACP". Do the same for port E3. See that the speeds, duplex and flow control also match for these two.&lt;BR /&gt;&lt;BR /&gt;3. If you only have one physical link between the switches (port 5412zl#E3 to 2650PWR#50), you don't need trunking: trunking is used for 2+ physical uplinks in the HP world. For Cisco, trunking means 802.1Q. Don't get confused by the definition of trunking HP vs. Cisco.&lt;BR /&gt;&lt;BR /&gt;4. Use 802.1Q tagging only for 2 of the VLANs (the VOIP ones), leave the other one VLAN (the PC one) Untagged for 5412zl#E3 and 2650PWR#50&lt;BR /&gt;&lt;BR /&gt;Should work.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 29 Jun 2007 04:00:13 GMT</pubDate>
    <dc:creator>OLARU Dan</dc:creator>
    <dc:date>2007-06-29T04:00:13Z</dc:date>
    <item>
      <title>Help with VLAN and Routing Issues</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/help-with-vlan-and-routing-issues/m-p/4028844#M11877</link>
      <description>Hi, been looking around for a bit of advice. To describe the scenario. We have a 5412zl Core switch in one building, linked together by fibre to a 2650-PWR switch in another. &lt;BR /&gt;&lt;BR /&gt;On the core switch all VLAN and routing works perfectly. I have 3 VLAN's as follows:&lt;BR /&gt;&lt;BR /&gt;VLAN 1 - 10.1.0.0/16&lt;BR /&gt;VLAN 2 - 10.2.0.0/16&lt;BR /&gt;VLAN 3 - 10.3.0.0/16&lt;BR /&gt;&lt;BR /&gt;I have trunked the fibre ports (E3 on the core and port 50 on the edge) into Trk1.&lt;BR /&gt;&lt;BR /&gt;VLAN 2 and 3 are used for the VoIP systems and VLAN 1 is purely for computers and servers (at the moment)&lt;BR /&gt;&lt;BR /&gt;I had this working on the 2650 but then all of a sudden it stopped. Can someone have a blast over the configs and if needed point me right please? Probably something stupid but it has been bugging me all day.&lt;BR /&gt;&lt;BR /&gt;For reference:&lt;BR /&gt;MACAD-CORE01 = 5412zl&lt;BR /&gt;MACAD-EDGE01 = 2650 PWR&lt;BR /&gt;&lt;BR /&gt;Many thanks!</description>
      <pubDate>Thu, 28 Jun 2007 11:50:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/help-with-vlan-and-routing-issues/m-p/4028844#M11877</guid>
      <dc:creator>CDTi</dc:creator>
      <dc:date>2007-06-28T11:50:57Z</dc:date>
    </item>
    <item>
      <title>Re: Help with VLAN and Routing Issues</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/help-with-vlan-and-routing-issues/m-p/4028845#M11878</link>
      <description>Right after a glass of wine and a relax for a bit I think I might of sussed this...&lt;BR /&gt;&lt;BR /&gt;I have spanning tree enabled and obviously this is going to be enabled on all ports at present. So I really need to disable these for all uplinks etc. arn't I?&lt;BR /&gt;&lt;BR /&gt;Also on the 2650 switches I don't need all those IP's on the VLAN's either do I? I only need 1 per switch ideally on the VLAN1 PC and Server VLAN....&lt;BR /&gt;&lt;BR /&gt;Any thoughts appreciated thanks!</description>
      <pubDate>Thu, 28 Jun 2007 15:01:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/help-with-vlan-and-routing-issues/m-p/4028845#M11878</guid>
      <dc:creator>CDTi</dc:creator>
      <dc:date>2007-06-28T15:01:06Z</dc:date>
    </item>
    <item>
      <title>Re: Help with VLAN and Routing Issues</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/help-with-vlan-and-routing-issues/m-p/4028846#M11879</link>
      <description>1. Decide which switch is going to do routing for your intranet, and only assign IP addys to the VLAN interfaces of that one; also routing should be started only on that switch (including default gateway and routing protocol - I don't see the need for two routers in the intranet; maybe you use the routing protocol with the outside). - I would decide in favor of the 5412zl&lt;BR /&gt;&lt;BR /&gt;2. port 50 is "no LACP". Do the same for port E3. See that the speeds, duplex and flow control also match for these two.&lt;BR /&gt;&lt;BR /&gt;3. If you only have one physical link between the switches (port 5412zl#E3 to 2650PWR#50), you don't need trunking: trunking is used for 2+ physical uplinks in the HP world. For Cisco, trunking means 802.1Q. Don't get confused by the definition of trunking HP vs. Cisco.&lt;BR /&gt;&lt;BR /&gt;4. Use 802.1Q tagging only for 2 of the VLANs (the VOIP ones), leave the other one VLAN (the PC one) Untagged for 5412zl#E3 and 2650PWR#50&lt;BR /&gt;&lt;BR /&gt;Should work.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 29 Jun 2007 04:00:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/help-with-vlan-and-routing-issues/m-p/4028846#M11879</guid>
      <dc:creator>OLARU Dan</dc:creator>
      <dc:date>2007-06-29T04:00:13Z</dc:date>
    </item>
    <item>
      <title>Re: Help with VLAN and Routing Issues</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/help-with-vlan-and-routing-issues/m-p/4028847#M11880</link>
      <description>Cheers Dan.&lt;BR /&gt;&lt;BR /&gt;Set that now and will see if that works. &lt;BR /&gt;&lt;BR /&gt;Will let you know.&lt;BR /&gt;&lt;BR /&gt;Trunking is done as I will have some more ports to do shortly, just haven't had them yet.&lt;BR /&gt;&lt;BR /&gt;Cheers for the advice!</description>
      <pubDate>Fri, 29 Jun 2007 04:50:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/help-with-vlan-and-routing-issues/m-p/4028847#M11880</guid>
      <dc:creator>CDTi</dc:creator>
      <dc:date>2007-06-29T04:50:54Z</dc:date>
    </item>
    <item>
      <title>Re: Help with VLAN and Routing Issues</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/help-with-vlan-and-routing-issues/m-p/4028848#M11881</link>
      <description>Still no joy...&lt;BR /&gt;&lt;BR /&gt;My Core is working perfectly. All VLANs are working correctly.&lt;BR /&gt;&lt;BR /&gt;Messed around with this 2650PWR switch and it seems to get connection. Then lose it when I don't make any config changes. Tried factory defaults and reconfigure but then it struggles to get connectivity. The only way it gets connectivity again is if I assign IP addresses to each VLAN on the edge. And then it drops. If I set a management address then leave the others as disabled it doesn't even connect.&lt;BR /&gt;&lt;BR /&gt;Really stuck now ready to hoy it ooot the window!</description>
      <pubDate>Sun, 01 Jul 2007 14:12:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/help-with-vlan-and-routing-issues/m-p/4028848#M11881</guid>
      <dc:creator>CDTi</dc:creator>
      <dc:date>2007-07-01T14:12:18Z</dc:date>
    </item>
    <item>
      <title>Re: Help with VLAN and Routing Issues</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/help-with-vlan-and-routing-issues/m-p/4028849#M11882</link>
      <description>Based on your original configurations, they look pretty much right to me. &lt;BR /&gt;&lt;BR /&gt;I would be checking your spanning-tree to make sure it's not blocking ports you don't expect it to be. (show span).&lt;BR /&gt;&lt;BR /&gt;Also, you probably want to make the 5412 the spanning-tree root:&lt;BR /&gt;&lt;BR /&gt;e.g.&lt;BR /&gt;spanning-tree priority 1.&lt;BR /&gt;&lt;BR /&gt;If you're still not having any luck, I'd suggest you collect 'show tech' reports from them, draw up a quick network map and open a case with support.</description>
      <pubDate>Sun, 01 Jul 2007 21:04:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/help-with-vlan-and-routing-issues/m-p/4028849#M11882</guid>
      <dc:creator>Matt Hobbs</dc:creator>
      <dc:date>2007-07-01T21:04:39Z</dc:date>
    </item>
    <item>
      <title>Re: Help with VLAN and Routing Issues</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/help-with-vlan-and-routing-issues/m-p/4028850#M11883</link>
      <description>Thanks Matt will do.&lt;BR /&gt;&lt;BR /&gt;Glad it isn't something painfully obvious in a way, and shame it isn't.&lt;BR /&gt;&lt;BR /&gt;Might be a faulty switch. Got a spare one going to patch in today so will go from there.&lt;BR /&gt;&lt;BR /&gt;Cheers for your help guys.</description>
      <pubDate>Mon, 02 Jul 2007 01:07:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/help-with-vlan-and-routing-issues/m-p/4028850#M11883</guid>
      <dc:creator>CDTi</dc:creator>
      <dc:date>2007-07-02T01:07:29Z</dc:date>
    </item>
  </channel>
</rss>

