IP route not working

[ozydave_1999]

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. I have no access to the config onn this 3560

 Now on port 3 my 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 (which is the link to port3)

I have also 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 F20
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

From my client PC with ip address 10.130.144.11 I can ping 10.130.254.10 no packet loss. If I ping 10.130.254.9 I get Reply From 10.130.254.9: Destination Host Unreachable with 0% loss

From my 5406 if I ping 10.130.254.9 I get 'Request timed out'

If I connect direct to port 3 on the 3560 and give my laptop 10.130.254.10 with the DG as 10.130.254.9 I can get out on the internet

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

[Vince-Whirlwind]

Yes, you're being a plank: IP routing commands mean:
ip route <destination> <target>

What you've tried to do is:

ip route <source subnet> <target>

The switch doesn't interpret it the way you are thinking of it...

What you want is eomething like:

class ipv4 Source_Subnet_144
  match ip 10.130.144.0/22 any
policy pbr Route_Subnet_144
  class ipv4 Source_Subnet_144
    action ip next-hop 10.130.254.9
vlan 100
  service-policy Route_Subnet_144 in