Source routing

From: Robert J. Adams (radams@siscom.net)
Date: Wed Jan 23 2002 - 13:15:47 EST


Hello,

I'm currently using a routing policy to force anything from 209.251.30.20 to
next-hop "Sprint", and anything from 209.251.30.21 to next-hop "UUnet". Once
we got up to about 60Meg/sec on a 300Mhz VXR I'm at around 80% CPU. Is there
a better way of doing this? See below for our current config.

I noticed with traceroute that I can use the -g switch to "loose source
route gateway", letting me choose the gw I want to use. This seems to work
for a few hops and then the traceroute dies. Is it possible to tell the
cisco to use the gateway I specify (with the -g option), rip out any special
header info that the -g put in the packet, and send it upstream? That way I
could get rid of the route policies and bring the CPU back down to something
usable?

Thanks,
Jason

interface FastEthernet0/0
 ip route-cache policy
 ip policy route-map selectout

route-map selectout permit 10
 match ip address 121
 set ip next-hop xx.xx.xx.165
!
route-map selectout permit 20
 match ip address 122
 set ip next-hop xx.xx.xx.37
!
route-map selectout permit 30
 match ip address 123 124
 set ip next-hop xx.xx.xx.150
!

access-list 121 deny ip any 209.251.0.0 0.0.31.255
access-list 121 permit ip host 209.251.30.21 any
access-list 121 permit ip host 209.251.30.31 any
access-list 121 deny ip any any
access-list 122 deny ip any 209.251.0.0 0.0.31.255
access-list 122 permit ip host 209.251.30.22 any
access-list 122 permit ip host 209.251.30.32 any
access-list 122 deny ip any any
access-list 123 deny ip any 209.251.0.0 0.0.31.255
access-list 123 permit ip host 209.251.30.23 any
access-list 123 permit ip host 209.251.30.33 any
access-list 123 deny ip any any
access-list 124 deny ip any 209.251.0.0 0.0.31.255
access-list 124 deny ip any 10.0.0.0 0.255.255.255
access-list 124 permit ip host 209.251.18.170 any



This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:29 EDT