Routing Between Two Subnets

[neilault]

We currently have two IP ranges as follows:

 

10.3.80/22

10.3.79.0/22

 

We need to setup a system to route between the two ranges as our previous SWGfL router was capped.

 

We have one HP ProCurve 2650 switch with IP of 10.3.11.253 and configured with the following VLANS:

VLAN 1 - DEAFULT_VLAN

IP: 10.3.11.253

Subnet: 255.255.252.0

VLAN 3 – SECONDARY

IP: 10.3.79.253

Subnet: 255.255.252.0

 

This switch has IP routing enabled and has one connection on port 50 which has been set to Tagged on both VLANs and connects to a HP ProCurve 2910al with IP of 10.3.11.248 via port 22 which also has been set to Tagged on both VLANs. The 10.3.11.248 switch has its default gateway set to 10.3.11.253.

 

We then have two laptops configured as follows:

 

IP: 10.3.11.20

Subnet: 255.255.252.0

Gateway: 10.3.11.253

10.3.79.250

Subnet: 255.255.252.0

Gateway: 10.3.79.253

 

When these laptops are connected directly to the 10.3.11.248 switch they can ping each other and all gateways fine.

 

Adding a HP ProCurve 2900 with IP of 10.3.11.247 and default gateway of 10.3.11.253 connected via port A3 (10GB) to port B1 (10GB) on 10.3.11.248 with both ports set to Tagged on both VLANs.

 

When the laptop with the 10.3.79.250 address is connected to the 10.3.11.247 switch it cannot ping the other laptop connected to 10.3.11.248 switch or any of the gateways. Swap the laptops around and they work ok.

 

It seems there is no route back for a device on the 10.3.76.0/22 range when connected to another switch other than the 10.3.11.248 one.

 

Routes on the main routing switch 10.3.11.253 are as follows:

ProCurve Switch 2650(config)# show ip route

 

IP Route Entries

 

Destination Gateway VLAN Type Sub-Type Metric Dist.

------------------ --------------- ---- --------- ---------- ---------- -----

10.3.8.0/22 DEFAULT_VLAN 1 connected 0 0

10.3.76.0/22 SECONDARY 3 connected 0 0

127.0.0.0/8 reject static 0 250

127.0.0.1/32 lo0 connected 0 0

And the routes on the other switches are as follows:

NSR-MAIN-02(config)# show ip route

 

IP Route Entries

 

Destination Gateway VLAN Type Sub-Type Metric Dist.

------------------ --------------- ---- --------- ---------- ---------- -----

0.0.0.0/0 10.3.11.253 1 static 250 1

10.3.8.0/22 DEFAULT_VLAN 1 connected 1 0

127.0.0.0/8 reject static 0 0

127.0.0.1/32 lo0 connected 1 0

Any ideas on what we are missing?

[keithu]

When the laptop with the 10.3.79.250 address is connected to the 10.3.11.247 switch it cannot ping the other laptop connected to 10.3.11.248 switch or any of the gateways. Swap the laptops around and they work ok.

 

I'm not quite following this. If you swap them they'll be on the wrong vlans won't they? Are you making sure that the laptop with address 10.3.11.20 is connected to a port in vlan 1 and the one with address 10.3.79.250 is connected to a port in vlan 3?

[cpjitservices]

can you flush the CAM Table, see if both MACS are in the databases ? I've seen it where we have taken PC's off of a VLAN and put them in another on the same switch and it has no worked due to the mac address already being "known" on another port on another vlan - so flushed the tables and it seemed to work. Also double check that the right ports are in the right VLANS.

[neilault]

Sorry about this, quite new to VLANS and switching.

 

So what you are saying is that we would have to configure each port on every switch on our network to either be part of DEFAULT_VLAN or SECONDARY depending on what is connected to that particular port? Thus when moving patch cable we woul dhave to make sure the port was configured to the right VLAN each time?

[cpjitservices]

Yes this is what we had to do - if we moved rooms around (regular occurrence) depending on what room they moved into it would correspond on the Patch Panel then go to a switchport - but that switchport would have to be on the right VLAN - f it was a class room or IT Suite then it would have to go on then STUDENT Vlan or if it was an office / admin it would go into the ADMIN VLAN we'd just configure those ports to be on the right VLAN.