cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
870
Views
0
Helpful
5
Replies

PBR and 4500 VSS pair

glsparks
Level 1
Level 1

I have 2 4500s configured as a VSS pair.

I am using VRF-Lite

I want to do PBR for a vrf with a failover to another IP should the first IP become unreachable.

However the documentation states:

The set next-hop verify-availability and the set ip next hop recursive commands are not supported within VRF instances

So what are my alternatives?

5 Replies 5

M02@rt37
VIP
VIP

Hello @glsparks,

Alternative:

--IP SLA with Object Tracking: You can configure IP SLA with object tracking to monitor the reachability of the primary IP address. If the primary IP becomes unreachable, the object tracking feature can trigger a failover action, such as modifying the routing table or updating a static route, to use the secondary IP address as the next hop. This allows you to achieve failover functionality without relying on PBR.

 

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.

A little more context is probably needed. So the VSS pair is peering to 3 routers. A default route is in the routing table via the routing protocol.

I'd like traffic to use one of the routers, then the other, finally failing back to the router advertising the default route. The Interfaces to these routers are LACP trunks carrying multiple VRFs inside a SVI 

The issue i'm experiencing without being able to check next hop availability is the SVI I am peering on will not go down unless the ethernet interface physically goes down.

balaji.bandi
Hall of Fame
Hall of Fame

what version of code - how is your config looks like for now ?

may be simple sla tracking should resolve the issue using EEM Script may be (if the VRF have limitation)

check some guide lines :

https://www.cisco.com/c/en/us/td/docs/ios/12_2sr/12_2srb/feature/guide/srb2mvrf.html

 

BB

=====Preenayamo Vasudevam=====

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Code is 02.11.04 E. See reply to MO2@rt37 for a bit more context.

Sorry that should be 03.11.04E