Policy Based Routing Configurations 6500 and 4948 Switches

[pduffany]

Hi!

I am searching for good Polciy Based Routing Configuration examples for the 6509 and 4948.

I have basic PBR setup, but cannot find good IPSLA configurations to pair with them.

The 4948 has IPSLA, but does not seem to have the commands to tie it to the PBR route map.

I am not finding effective IPSLA configurations for the 6500 as well.

My hope is that someone has the IPSLA config that I can use, or direct me to a completed configuration example.

This is for redirection to a WAN Accelerator that must be monitored.

What I have so far for the 4948:

interface GigabitEthernet1/11
 description to_dis_pri:g2/0/11
 no switchport
 ip address 11.11.11.10 255.255.255.252
 ip policy route-map Silverpeak
 speed 1000
 duplex full

ip access-list extended SilverpeakACL
 permit ip any 12.12.12.0 0.0.0.255

ip sla 99
 icmp-echo 14.14.14.14
 timeout 2000
 frequency 10
ip sla schedule 99 life forever start-time now

route-map Silverpeak permit 10
 match ip address SilverpeakACL
 set ip next-hop 14.14.14.14

I don't see how this will stop Policy Based Routing in the event that the WAN accelerator dies.

If you know of where I can get the config, or provide it here, I would be very Happy!

[Ganesh Hariharan]

Hi,

Have you applied Track configuration on global mode

track 99 ip sla reachabilty

and what is the output of show track 99 is showing , is it reachable...

Hope it Helps..

-GI

Rate if it Helps..

[pduffany]

Hi Ganesh,

When I try that command I get this:

track 99 ip sla ?
  <1-2147483647>  Entry number

Not sure which entry number this is asking for.

[Ganesh Hariharan]

Hi Ganesh,

When I try that command I get this:

track 99 ip sla ?
  <1-2147483647>  Entry number

Not sure which entry number this is asking for.

Hi,

It should be track 99 ip sla 99 reachability..

-GI

[pduffany]

Hi Ganesh,

It did take that command, and this is the output::

#sho track 99
Track 99
  IP SLA 99 reachability
  Reachability is Up
    1 change, last change 00:00:16
  Latest operation return code: OK
  Latest RTT (millisecs) 1

Will this tie it all together?

Also, will this be the same config for the 6509?

[Ganesh Hariharan · Accepted solution]

Hi Ganesh,

It did take that command, and this is the output::


#sho track 99
Track 99
  IP SLA 99 reachability
  Reachability is Up
    1 change, last change 00:00:16
  Latest operation return code: OK
  Latest RTT (millisecs) 1


Will this tie it all together?

Also, will this be the same config for the 6509?

Hi,

I believe you are applying IP SLA on edge device where you want automatic failover, if it 6509 then apply there.

Once this output is ok then apply the track command with route map as per early post.

Hope it helps..

-GI

Rate if it Helps..

[pduffany]

Hi Ganesh,

Actually I am trying to supplant WCCP on the 6509 as it seems to hang even when implemented in hardware.

In the 6509 I don't see the IP SLA options with this code:

(s3223_rp-IPBASE_WAN-M), Version 12.2(18)SXF17, RELEASE SOFTWARE (fc1)

Do you know the minimum license to enable it?

If not, thats ok I'll try and get that from Cisco.

[Ganesh Hariharan]

Hi Ganesh,

Actually I am trying to supplant WCCP on the 6509 as it seems to hang even when implemented in hardware.

In the 6509 I don't see the IP SLA options with this code:

(s3223_rp-IPBASE_WAN-M), Version 12.2(18)SXF17, RELEASE SOFTWARE (fc1)

Do you know the minimum license to enable it?

If not, thats ok I'll try and get that from Cisco.

Hi,

Check out the below link from cisco which gives the best practice to implement WCCP with 6509 along with prerequisite software requirement .

http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-6500-series-switches/white_paper_c11-629052.html

Hope it Helps..

-GI

Rate if it Helpss..

[pduffany]

Hi Ganesh,

Thats a great article for WCCP, but I am replacing WCCP with PBR, and need to know the requirements for PBR on the 6500.

If you have any direction at all for those requirements, I would be very grateful.

Thank you again,

Paul

[krahmani323]

Hi Paul,

About the support on PbR 6500 with ipsla tracking association, I searched on the Cisco feature navigator and indeed just like you were suspecting the feature does not seem to be supported on your current release. I understand that you are using a 6500 SUP32 - 12.2(18)SXF17 in IP BASE.

On the 'Cisco feature navigator' you can search on the option "PBR Support for Multiple Tracking Options" and the first release listed is 12.3(33)SXH1

The 12.2(33) release notes confirm that point under the new softwre feature section for 12.2(33)SXH.

http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/12-2SX/release/notes/ol_14271/features.html#pgfId-3766871

I am also wondering, in case of you decide to upgrade to 12.2(33)SX to implement a release different from IP BASE. Indeed, the PBR feature is not checked under the feature set description (ip services minimum).

http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/12-2SX/release/notes/ol_14271/features.html#pgfId-4783221

I see that you are using a modular IOS ?? Wow good luck if you need to upgrade.

A similar lookup for the Pbr sla tracking on the 4948 could be done.

Hope that helps.

Thank you!

Karim

[paul driver]

Hello

track 10 rtr 99 eachability

route-map Silverpeak permit 10
 match ip address SilverpeakACL
 set ip next-hop verify-availability 14.14.14.14 track 10

Res

paul

[pduffany]

Thanks Paul,

However in this command, I do not have "verify-availability" as an option, that command doesn't exist in my 4948

set ip next-hop verify-availability 14.14.14.14 track 10

(cat4500-ENTSERVICESK9-M), Version 15.0(2)SG1, RELEASE SOFTWARE (fc4)