Re: InterVLAN routing not working - New to Procurves (582 Views)
Reply
Occasional Visitor
MDU0306
Posts: 2
Registered: ‎09-05-2013
Message 1 of 3 (605 Views)

InterVLAN routing not working - New to Procurves

Hello!

 

I'm hoping someone could give me some direction.  Basically my problem boils down to the fact that I can't go anywhere outside of my VLAN 200.  I have a new 2920 Procurve that is connected to a Netgear switch.  The Netgear switch only has the default VLAN 1 setup with an IP of 10.1.1.3.  I have set up VLAN 200 with IP of 10.1.200.1 /24 on the 2920 and have one port Untagged for 200.  This port is 3/2.  The port connected to the Netgear switch is port 3/48.  I can ping our DNS server (10.1.1.125) from the Procurve which is connected to the Netgear switch but when I connect my laptop to port 3/2 (VLAN 200) and manually assign an IP address to my laptop I cannot ping the server.  Here is my config:

 

ip routing

 

vlan 1
   name "DEFAULT_VLAN"
   no untagged 3/1-3/3,3/20,3/47
   untagged
 1/1-1/48,1/A1-1/A2,1/B1-1/B2,2/1-2/48,2/A1-2/A2,2/B1-2/B2,3/4-3/19,3/21-3/46,3/
48,3/A1-3/A2,3/B1-3/B2
   ip address 10.1.1.250 255.255.255.0
   exit

vlan 200
   name "Servers_Printers"
   untagged 3/2
   tagged 3/48
   ip address 10.1.200.1 255.255.255.0
   ip helper-address 10.1.1.125
   exit

interface 3/2 (connected to my laptop)
   untagged vlan 200
   exit

interface 3/48 (connection to Netgear switch)
   tagged vlan 200
   untagged vlan 1
   exit

 

Basically I can't get over to my Netgear switch on VLAN 200.

Trusted Contributor
Vince_Whirlwind
Posts: 401
Registered: ‎02-25-2013
Message 2 of 3 (596 Views)

Re: InterVLAN routing not working - New to Procurves

Trace the layer-3 path of the packet:

Source: 10.1.200.3

Dest.:10.1.1.3

 

1/ Leaves your laptop, goes to its default gateway, which is the VLAN 200 interface on the 2920, 10.1.200.1

2/ From the VLAN200 interface, the 2920 is direct-connected to the destination subnet, therfore it knows to send out an ARP, find the destination device and switch the packet to it.

3/ The destination device replies by sending its packet to its default gateway. Where is that?

4/ The default gateway will look up its routing table to find the 10.1.200.0 subnet. Can it find it?

Occasional Visitor
MDU0306
Posts: 2
Registered: ‎09-05-2013
Message 3 of 3 (582 Views)

Re: InterVLAN routing not working - New to Procurves

I wanted to thank you for your response as it helped me to wrap my head around it and correct my issue.  I had to create a static route on two routers one of which was the Netgear L3 switch that pointed back to that VLAN.  I'm in the middle of implementing a new core which will remove the need for these routers but needed to get the InterVLAN routing functioning in the mean time.  Again, thank you!

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.