5406 static routes

[ozydave]

We have a cisco 3560 (our broadband connection via local authority).

I have various VLANs setup all going out to the internet via the default route ip route 0.0.0.0 0.0.0.0 10.6.151.254 on port 2 on the 3560.

Now on port 3 the local authority have provided ip address 10.130.254.9 255.255.255.252 (for transparent proxy) and told me to use 10.130.254.10 255.255.255.252 on my switch (5406zl)

 

I have setup VLAN 8 with 10.130.254.10 255.255.255.252

I have now setup VLAN 100 with another IP range 10.130.144.0 /22

So now I want anything on the 10.130.144.0 /22 range to route out via VLAN 8

Portions of the show run below which shows the new ip route

 

ip route 0.0.0.0 0.0.0.0 10.6.151.254

ip route 10.130.144.0 255.255.252.0 10.130.254.9

vlan 8

name "TX-Link"

untagged F30

tagged B21-B22,C1-C7,Trk1

ip address 10.130.254.10 255.255.255.252

exit

vlan 100

name "TxProxy"

untagged F19

tagged B21-B22,C1-C7,Trk1

ip address 10.130.144.1 255.255.252.0

ip helper-address 10.80.1.35

exit

 

This doesn’t seem to work.

If I do a ‘show ip route static’ I get the below, no new ip route. The command I used to add the new route was ip route 10.130.144.0 255.255.252.0 10.130.254.9

I have done a write mem command

 

Destination Gateway VLAN Type Sub-Type Metric Dist.

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

0.0.0.0/0 10.6.151.254 10 static 1 1

127.0.0.0/8 reject static 0 0

 

Am I being a complete plank? Does the switch need a reboot for the rout to take effect?

[CSE_Sumit]

Hi,

 

When you add an IP Route to the switch, you are asking the switch to look at the destination address of the packet and then forward it to the next hop address, or the next router it needs to go to. The IP Route command does not look at the source address. So when you are adding the route for VLAN 100, you are actually saying that anything going to 10.130.144.0 255.255.252.0 needs to go to be routed through 10.130.254.9. This won't work as the network you are specifying is already configured locally on the switch.

 

To achieve what you require, you need to use policy based routing, which is able to look at the source address of the packet and then making a routing decision based on that. This is only supported on HPs v2 modules. Have a look at it on chapter 11 of HP's Advanced Traffic Management guide.

 

Thanks,