<?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: Almost have vlanning going .... in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/almost-have-vlanning-going/m-p/4248914#M15178</link>
    <description>Ok, I am working to make the changes, and after putting in the ip routing statement, I am working to add the ip route 10.16.0.0 255.255.0.0 10.16.1.10 statement.&lt;BR /&gt;&lt;BR /&gt;The switch throws back to me:&lt;BR /&gt;&lt;BR /&gt;10.16.1.10 can not be switch IP address and route gateway at the same time.&lt;BR /&gt;</description>
    <pubDate>Fri, 08 Aug 2008 21:36:52 GMT</pubDate>
    <dc:creator>Randy Saeks</dc:creator>
    <dc:date>2008-08-08T21:36:52Z</dc:date>
    <item>
      <title>Almost have vlanning going ....</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/almost-have-vlanning-going/m-p/4248911#M15175</link>
      <description>I am almost there .... &lt;BR /&gt;&lt;BR /&gt;I have two switches, each with a vlan 9 setup.  I am able to ping the other device from each switch (can ping 10.16.1.10 from 10.16.1.11 and vice versa)  If I am on the 10.15.0.0 network, I can ping 10.16.1.10, but I can not ping 10.16.1.11.&lt;BR /&gt;&lt;BR /&gt;Ports G24 and 52 link the two switches together.&lt;BR /&gt;&lt;BR /&gt;Here are the two run files.  Any ideas what I am missing?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 08 Aug 2008 15:32:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/almost-have-vlanning-going/m-p/4248911#M15175</guid>
      <dc:creator>Randy Saeks</dc:creator>
      <dc:date>2008-08-08T15:32:39Z</dc:date>
    </item>
    <item>
      <title>Re: Almost have vlanning going ....</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/almost-have-vlanning-going/m-p/4248912#M15176</link>
      <description>Hi Randy,&lt;BR /&gt;&lt;BR /&gt;Looking at the two show runs, I see that you have a routing statement on the 4208.  However, I do not see an IP routing entry indicating that routing has been enabled on the 4208.&lt;BR /&gt;&lt;BR /&gt;Were you intending to route on the 4208 and the 2610?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Jarret</description>
      <pubDate>Fri, 08 Aug 2008 16:55:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/almost-have-vlanning-going/m-p/4248912#M15176</guid>
      <dc:creator>Jarret Workman</dc:creator>
      <dc:date>2008-08-08T16:55:34Z</dc:date>
    </item>
    <item>
      <title>Re: Almost have vlanning going ....</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/almost-have-vlanning-going/m-p/4248913#M15177</link>
      <description>hi Randy I make new config for you &lt;BR /&gt;plaese test and you be carefull read in config my note&lt;BR /&gt;&lt;BR /&gt;cenk&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;------------------------&lt;BR /&gt;| 4208vl Configuration: |&lt;BR /&gt;-------------------------&lt;BR /&gt;&lt;BR /&gt;Running configuration:&lt;BR /&gt;&lt;BR /&gt;; J8773A Configuration Editor; Created on release #L.11.12&lt;BR /&gt;&lt;BR /&gt;hostname "Maple MDF" &lt;BR /&gt;snmp-server contact "Randy Saeks" &lt;BR /&gt;module 1 type J8765A &lt;BR /&gt;module 2 type J8765A &lt;BR /&gt;module 3 type J8765A &lt;BR /&gt;module 4 type J8765A &lt;BR /&gt;module 5 type J8765A &lt;BR /&gt;module 7 type J9033A &lt;BR /&gt;module 8 type J8776A &lt;BR /&gt;interface G3 &lt;BR /&gt;   name "SAN_Port_1" &lt;BR /&gt;exit&lt;BR /&gt;interface G4 &lt;BR /&gt;   name "SAN_Port_1" &lt;BR /&gt;exit&lt;BR /&gt;trunk G3-G4 Trk2 LACP &lt;BR /&gt;ip routing***********neccessary&lt;BR /&gt;timesync sntp &lt;BR /&gt;snmp-server community "public" Unrestricted &lt;BR /&gt;snmp-server host 10.15.100.202 "public" &lt;BR /&gt;vlan 1 &lt;BR /&gt;   name "DEFAULT_VLAN" &lt;BR /&gt;   untagged A2-A24,B1-B24,C1-C24,D1-D24,E1-E24,G1-G2,G5-G24,H1-H4,Trk2  ********connect for test pc (vlan 1 member ip address 10.15.1.81/16 dg:10.15.1.10)*****&lt;BR /&gt;   no untagged A1&lt;BR /&gt;   ip address 10.15.1.10 255.255.0.0 &lt;BR /&gt;   ip igmp &lt;BR /&gt;   exit &lt;BR /&gt;vlan 9 &lt;BR /&gt;   name "storage" &lt;BR /&gt;   ip address 10.16.1.10 255.255.0.0 &lt;BR /&gt;   untagged A1   *******connect for test pc (vlan 2 member ip address 10.16.1.81/16 dg:10.16.1.10)****&lt;BR /&gt;   tagged G24,Trk2 &lt;BR /&gt;   exit &lt;BR /&gt;fault-finder bad-driver sensitivity high &lt;BR /&gt;fault-finder bad-transceiver sensitivity high &lt;BR /&gt;fault-finder bad-cable sensitivity high &lt;BR /&gt;fault-finder too-long-cable sensitivity high &lt;BR /&gt;fault-finder over-bandwidth sensitivity high &lt;BR /&gt;fault-finder broadcast-storm sensitivity high &lt;BR /&gt;fault-finder loss-of-link sensitivity high &lt;BR /&gt;fault-finder duplex-mismatch-HDx sensitivity high &lt;BR /&gt;fault-finder duplex-mismatch-FDx sensitivity high &lt;BR /&gt;ip route 0.0.0.0 0.0.0.0 10.15.1.1 *********(to internet router)***********&lt;BR /&gt;*******************************************************************************************&lt;BR /&gt;and you can must be write routing on internet router ip route 10.15.0.0 255.255.0.0 10.15.1.10 &lt;BR /&gt;and ip route 10.16.0.0 255.255.0.0 10.16.1.10&lt;BR /&gt;*************************************************&lt;BR /&gt;spanning-tree&lt;BR /&gt;spanning-tree Trk2 priority 4&lt;BR /&gt;password manager&lt;BR /&gt;&lt;BR /&gt;------------------------&lt;BR /&gt;|  2610 Configuration: |&lt;BR /&gt;------------------------&lt;BR /&gt;&lt;BR /&gt;Running configuration:&lt;BR /&gt;&lt;BR /&gt;; J9088A Configuration Editor; Created on release #R.11.16&lt;BR /&gt;&lt;BR /&gt;hostname "Do.IDF1" &lt;BR /&gt;snmp-server contact "Randy Saeks" &lt;BR /&gt;interface 49 &lt;BR /&gt;   name "SAN_Port_1" &lt;BR /&gt;exit&lt;BR /&gt;interface 50 &lt;BR /&gt;   name "SAN_Port_2" &lt;BR /&gt;exit&lt;BR /&gt;trunk 49-50 Trk1 LACP &lt;BR /&gt;snmp-server community "public" Unrestricted &lt;BR /&gt;vlan 1 &lt;BR /&gt;   name "DEFAULT_VLAN" &lt;BR /&gt;   untagged 2-48,51-Trk1 ********connect for test pc (vlan 1 member ip address 10.15.1.80/16 dg:10.15.1.10)*****&lt;BR /&gt;   no untagged 1&lt;BR /&gt;   ip address 10.15.1.11 255.255.0.0 (this ip address only managemet not for routing)&lt;BR /&gt;   exit &lt;BR /&gt;vlan 9 (no need ip address this vlan )&lt;BR /&gt;   name "storage" &lt;BR /&gt;   untagged 1   *******connect for test pc (vlan 2 member ip address 10.16.1.80/16 dg:10.16.1.10)****&lt;BR /&gt;   tagged 52-Trk1 &lt;BR /&gt;   exit &lt;BR /&gt;spanning-tree&lt;BR /&gt;spanning-tree Trk1 priority 4&lt;BR /&gt;password manager&lt;BR /&gt;</description>
      <pubDate>Fri, 08 Aug 2008 17:35:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/almost-have-vlanning-going/m-p/4248913#M15177</guid>
      <dc:creator>cenk sasmaztin</dc:creator>
      <dc:date>2008-08-08T17:35:59Z</dc:date>
    </item>
    <item>
      <title>Re: Almost have vlanning going ....</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/almost-have-vlanning-going/m-p/4248914#M15178</link>
      <description>Ok, I am working to make the changes, and after putting in the ip routing statement, I am working to add the ip route 10.16.0.0 255.255.0.0 10.16.1.10 statement.&lt;BR /&gt;&lt;BR /&gt;The switch throws back to me:&lt;BR /&gt;&lt;BR /&gt;10.16.1.10 can not be switch IP address and route gateway at the same time.&lt;BR /&gt;</description>
      <pubDate>Fri, 08 Aug 2008 21:36:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/almost-have-vlanning-going/m-p/4248914#M15178</guid>
      <dc:creator>Randy Saeks</dc:creator>
      <dc:date>2008-08-08T21:36:52Z</dc:date>
    </item>
    <item>
      <title>Re: Almost have vlanning going ....</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/almost-have-vlanning-going/m-p/4248915#M15179</link>
      <description>Hi Randy,&lt;BR /&gt;&lt;BR /&gt;It looks like the switch is complaining that you are entering 10.16.1.10 as a destination on the switch when that IP address is already present on the switch.&lt;BR /&gt;&lt;BR /&gt;Cenk's configuration only uses the 4208 for routing, so you should only need the following:&lt;BR /&gt;&lt;BR /&gt;The 10.16.x.x traffic should go to 10.16.1.10 as long as that is the IP address assigned to the clients NIC as their default gateway.&lt;BR /&gt;&lt;BR /&gt;You should only need a route of last resort to your upstream router for unknown destinations.  Something like (ip route 0.0.0.0 0.0.0.0 10.15.1.1).&lt;BR /&gt;&lt;BR /&gt;As long as your clients are pointing to the correct local default gateway (10.16.1.10 or 10.15.1.10 on the 4208) then the routing should work between these two subnets.  The 0.0.0.0/0 route would be for unknown destinations such as the internet.&lt;BR /&gt;&lt;BR /&gt;Looking at Cenk's configuration, I believe the intent is to have the 10.15.0.0/16 10.15.1.10 and the 10.16.0.0/16 10.16.1.10 configured on your internet router as return routes (the 10.15.1.1 router).  This would enable traffic coming back in from the internet to make it back to the edge device.  The internet router (10.15.1.1) needs to have return routes telling where to send traffic destined for the 10.15.x.x and the 10.16.x.x networks.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Jarret</description>
      <pubDate>Fri, 08 Aug 2008 21:58:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/almost-have-vlanning-going/m-p/4248915#M15179</guid>
      <dc:creator>Jarret Workman</dc:creator>
      <dc:date>2008-08-08T21:58:39Z</dc:date>
    </item>
    <item>
      <title>Re: Almost have vlanning going ....</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/almost-have-vlanning-going/m-p/4248916#M15180</link>
      <description>Ok, that sounds like it makes sense.&lt;BR /&gt;&lt;BR /&gt;I am really only going to have two devices in that vlan, our iSCSI SAN.  I can manually configure those to use the 10.16.1.10 gateway.&lt;BR /&gt;&lt;BR /&gt;Since the 4208 will know about the 10.16 network, the servers connected to the storage network should be fine, right?  Or, would I want to also tag the ports as a member of the storage vlan as well?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 08 Aug 2008 22:08:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/almost-have-vlanning-going/m-p/4248916#M15180</guid>
      <dc:creator>Randy Saeks</dc:creator>
      <dc:date>2008-08-08T22:08:03Z</dc:date>
    </item>
    <item>
      <title>Re: Almost have vlanning going ....</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/almost-have-vlanning-going/m-p/4248917#M15181</link>
      <description>Hi Randy,&lt;BR /&gt;&lt;BR /&gt;The servers should be fine living in just one vlan as they will be routed to the storage vlan via the 4208.  &lt;BR /&gt;&lt;BR /&gt;If the servers are in the 10.15.0.0 network, then they would have a default gateway of 10.15.1.10.</description>
      <pubDate>Fri, 08 Aug 2008 22:15:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/almost-have-vlanning-going/m-p/4248917#M15181</guid>
      <dc:creator>Jarret Workman</dc:creator>
      <dc:date>2008-08-08T22:15:47Z</dc:date>
    </item>
    <item>
      <title>Re: Almost have vlanning going ....</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/almost-have-vlanning-going/m-p/4248918#M15182</link>
      <description>Jarret,&lt;BR /&gt;&lt;BR /&gt;Thanks!&lt;BR /&gt;&lt;BR /&gt;I'll plug in a laptop or two and test out the IP changes with those devices having the numbers I want to use with oru production system and see how it goes.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 08 Aug 2008 22:26:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/almost-have-vlanning-going/m-p/4248918#M15182</guid>
      <dc:creator>Randy Saeks</dc:creator>
      <dc:date>2008-08-08T22:26:17Z</dc:date>
    </item>
    <item>
      <title>Re: Almost have vlanning going ....</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/almost-have-vlanning-going/m-p/4248919#M15183</link>
      <description>ok sory Randy ip route must be &lt;BR /&gt;**********************************&lt;BR /&gt;internet router/server to switch &lt;BR /&gt;10.15.0.0 255.255.0.0 10.15.1.10&lt;BR /&gt;10.16.0.0 255.255.0.0 10.15.1.10&lt;BR /&gt;**********************************&lt;BR /&gt;switch to internet router/server&lt;BR /&gt;0.0.0.0 0.0.0.0 10.15.1.1&lt;BR /&gt;&lt;BR /&gt;cenk</description>
      <pubDate>Sat, 09 Aug 2008 06:57:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/almost-have-vlanning-going/m-p/4248919#M15183</guid>
      <dc:creator>cenk sasmaztin</dc:creator>
      <dc:date>2008-08-09T06:57:25Z</dc:date>
    </item>
  </channel>
</rss>

