<?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: ProCurve 6120XG and variable length subnets in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-6120xg-and-variable-length-subnets/m-p/5238044#M29535</link>
    <description>closing thread.</description>
    <pubDate>Wed, 05 May 2010 11:04:09 GMT</pubDate>
    <dc:creator>J.J. McDaniel</dc:creator>
    <dc:date>2010-05-05T11:04:09Z</dc:date>
    <item>
      <title>ProCurve 6120XG and variable length subnets</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-6120xg-and-variable-length-subnets/m-p/5238037#M29528</link>
      <description>Hi.&lt;BR /&gt;&lt;BR /&gt;I'm trying to use variable length subnets on a ProCurve 6120XG in a BladeSystem c7000.&lt;BR /&gt;&lt;BR /&gt;We have divided a Class C network up in to 8 subnets, 255.255.255.224.  If I go back to a plain Class C it works but does not when using variable length subnets. &lt;BR /&gt;&lt;BR /&gt;Does the 6120XG support variable length subnets?&lt;BR /&gt;&lt;BR /&gt;Thanks!&lt;BR /&gt;&lt;BR /&gt;J.J.&lt;BR /&gt;</description>
      <pubDate>Mon, 03 May 2010 18:44:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-6120xg-and-variable-length-subnets/m-p/5238037#M29528</guid>
      <dc:creator>J.J. McDaniel</dc:creator>
      <dc:date>2010-05-03T18:44:06Z</dc:date>
    </item>
    <item>
      <title>Re: ProCurve 6120XG and variable length subnets</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-6120xg-and-variable-length-subnets/m-p/5238038#M29529</link>
      <description>Are you assigning that IP address to an specific vlan or to the OOBM interface through the OA?</description>
      <pubDate>Mon, 03 May 2010 20:29:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-6120xg-and-variable-length-subnets/m-p/5238038#M29529</guid>
      <dc:creator>Lmm_1</dc:creator>
      <dc:date>2010-05-03T20:29:54Z</dc:date>
    </item>
    <item>
      <title>Re: ProCurve 6120XG and variable length subnets</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-6120xg-and-variable-length-subnets/m-p/5238039#M29530</link>
      <description>Given the 6120XG is a Layer-2 (Ethernet data-link) switch, apart from its management interface I don't see how it could care one way or another about how you subnetted the IP (Layer-3) address space used by the blades, all it is doing is switching Ethernet frames among the ports.  Can you be a bit more specific about what you are trying to do and how?</description>
      <pubDate>Mon, 03 May 2010 23:33:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-6120xg-and-variable-length-subnets/m-p/5238039#M29530</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2010-05-03T23:33:09Z</dc:date>
    </item>
    <item>
      <title>Re: ProCurve 6120XG and variable length subnets</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-6120xg-and-variable-length-subnets/m-p/5238040#M29531</link>
      <description>Question: Are you using all 8 subnets within the same network / (V)LAN? (this is called a multinet)&lt;BR /&gt;Or are this seperate networks/VLAN's?&lt;BR /&gt;&lt;BR /&gt;In both cases the switch can forward data between ports in the same subnet. This is a layer-2 (switching) communication and has nothing to do with TCP/IP adresses (layer-3).&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;In the multinet situation you should allready have a router to forward traffic between VLAN's/subnets, else the subnets are isolated and cannot talk to eachother.&lt;BR /&gt;If not then the only way to make the switch reachable from all subnets is to give it an adress+subnetmask that matches all subnets.&lt;BR /&gt;&lt;BR /&gt;The normal way to set things up it to create separate VLAN's for each subnet and configure a router to forward traffic between VLAN's/subnets.&lt;BR /&gt;&lt;BR /&gt;As the previous poster mentioned this is a L2 switch you will need an additional router to forward traffic between subnets.&lt;BR /&gt;</description>
      <pubDate>Tue, 04 May 2010 06:34:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-6120xg-and-variable-length-subnets/m-p/5238040#M29531</guid>
      <dc:creator>Pieter 't Hart</dc:creator>
      <dc:date>2010-05-04T06:34:37Z</dc:date>
    </item>
    <item>
      <title>Re: ProCurve 6120XG and variable length subnets</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-6120xg-and-variable-length-subnets/m-p/5238041#M29532</link>
      <description>Yes, I have a VLAN for each subnet.  Here is my show config:&lt;BR /&gt;&lt;BR /&gt;hostname "net1001.mckesson.com" &lt;BR /&gt;interface 23 &lt;BR /&gt;   disable&lt;BR /&gt;   lacp Active &lt;BR /&gt;exit&lt;BR /&gt;interface 24 &lt;BR /&gt;   disable&lt;BR /&gt;   lacp Active &lt;BR /&gt;exit&lt;BR /&gt;trunk 18-19 Trk1 Trunk &lt;BR /&gt;ip default-gateway 10.97.221.62 &lt;BR /&gt;vlan 1 &lt;BR /&gt;   name "DEFAULT_VLAN" &lt;BR /&gt;   untagged 1-17,20-24,Trk1 &lt;BR /&gt;   no ip address &lt;BR /&gt;   exit &lt;BR /&gt;vlan 131 &lt;BR /&gt;   name "Citrix_Console" &lt;BR /&gt;   ip address 10.97.221.61 255.255.255.224 &lt;BR /&gt;   tagged 1-17,20-24,Trk1 &lt;BR /&gt;   exit &lt;BR /&gt;vlan 132 &lt;BR /&gt;   name "Citrix_McKHost" &lt;BR /&gt;   tagged 1-17 &lt;BR /&gt;   no ip address &lt;BR /&gt;   exit &lt;BR /&gt;vlan 133 &lt;BR /&gt;   name "Citrix_D9H11" &lt;BR /&gt;   tagged 1-17 &lt;BR /&gt;   no ip address &lt;BR /&gt;   exit &lt;BR /&gt;vlan 134 &lt;BR /&gt;   name "Citrix_Customer" &lt;BR /&gt;   tagged 1-17 &lt;BR /&gt;   no ip address &lt;BR /&gt;   exit &lt;BR /&gt;vlan 135 &lt;BR /&gt;   name "Citrix_Open1" &lt;BR /&gt;   tagged 1-17 &lt;BR /&gt;   no ip address &lt;BR /&gt;   exit &lt;BR /&gt;vlan 136 &lt;BR /&gt;   name "Citrix_open2" &lt;BR /&gt;   tagged 1-17 &lt;BR /&gt;   no ip address &lt;BR /&gt;   exit &lt;BR /&gt;vlan 137 &lt;BR /&gt;   name "Citrix_AD_DC" &lt;BR /&gt;   tagged 1-17 &lt;BR /&gt;   no ip address &lt;BR /&gt;   exit &lt;BR /&gt;vlan 130 &lt;BR /&gt;   name "MGMT" &lt;BR /&gt;   tagged 1-17,20-24,Trk1 &lt;BR /&gt;   no ip address &lt;BR /&gt;   exit &lt;BR /&gt;vlan 220 &lt;BR /&gt;   name "VLAN220" &lt;BR /&gt;   tagged 1-17,20-24,Trk1 &lt;BR /&gt;   no ip address &lt;BR /&gt;   exit&lt;BR /&gt;</description>
      <pubDate>Tue, 04 May 2010 12:36:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-6120xg-and-variable-length-subnets/m-p/5238041#M29532</guid>
      <dc:creator>J.J. McDaniel</dc:creator>
      <dc:date>2010-05-04T12:36:17Z</dc:date>
    </item>
    <item>
      <title>Re: ProCurve 6120XG and variable length subnets</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-6120xg-and-variable-length-subnets/m-p/5238042#M29533</link>
      <description>can you specify "If I go back to a plain Class C it works but does not when using variable length subnets"&lt;BR /&gt;what does work, what doesn't?&lt;BR /&gt;- can the switch ping this gateway and vice-versa?&lt;BR /&gt;- can the switch telnet to this gateway (vv)?&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt;&amp;gt;&lt;BR /&gt;ip default-gateway 10.97.221.62 &lt;BR /&gt;vlan 131 &lt;BR /&gt;ip address 10.97.221.61 255.255.255.224&lt;BR /&gt;tagged 1-17,20-24,Trk1  &lt;BR /&gt;&amp;lt;&amp;lt;&amp;lt;&lt;BR /&gt;looks basically allright&lt;BR /&gt;&lt;BR /&gt;- what is this default gateway?&lt;BR /&gt;- on which port is it connected&lt;BR /&gt; (possibly somewhere at Trk1?)&lt;BR /&gt;- what's the subnet mask on this gateway?&lt;BR /&gt;- what's the vlan config of this gateway?&lt;BR /&gt;</description>
      <pubDate>Wed, 05 May 2010 06:44:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-6120xg-and-variable-length-subnets/m-p/5238042#M29533</guid>
      <dc:creator>Pieter 't Hart</dc:creator>
      <dc:date>2010-05-05T06:44:05Z</dc:date>
    </item>
    <item>
      <title>Re: ProCurve 6120XG and variable length subnets</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-6120xg-and-variable-length-subnets/m-p/5238043#M29534</link>
      <description>Hey guys.&lt;BR /&gt;&lt;BR /&gt;Thanks for the help.  We found the issue.&lt;BR /&gt;My network guy forgot to put the Layer-2 switch in the route of the up stream switch.&lt;BR /&gt;&lt;BR /&gt;IT (Layer 2) --&amp;gt; Brocade TurboIron 24x (Layer 3)--&amp;gt; ProCurve&lt;BR /&gt;&lt;BR /&gt;once he put that switch from our IT deptartment in there the subnets were able to forward and resolve eachother.&lt;BR /&gt;&lt;BR /&gt;We're working on getting a Layer 2 switch in the lab so we won't have to go so far up to resolve.&lt;BR /&gt;&lt;BR /&gt;Thanks again!&lt;BR /&gt;&lt;BR /&gt;J.J.&lt;BR /&gt;</description>
      <pubDate>Wed, 05 May 2010 11:03:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-6120xg-and-variable-length-subnets/m-p/5238043#M29534</guid>
      <dc:creator>J.J. McDaniel</dc:creator>
      <dc:date>2010-05-05T11:03:30Z</dc:date>
    </item>
    <item>
      <title>Re: ProCurve 6120XG and variable length subnets</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-6120xg-and-variable-length-subnets/m-p/5238044#M29535</link>
      <description>closing thread.</description>
      <pubDate>Wed, 05 May 2010 11:04:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-6120xg-and-variable-length-subnets/m-p/5238044#M29535</guid>
      <dc:creator>J.J. McDaniel</dc:creator>
      <dc:date>2010-05-05T11:04:09Z</dc:date>
    </item>
  </channel>
</rss>

