Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 287
  • Last Modified:

Configuring Policy Basd Routing

Hi,

As you can see in the diagram attached below, I have four links between two of my sites. Two links are 10 Mbps capacity each and I am equally load balancing my traffic between them. Two more links are there of 200 Mbps capacity each and I am using them in active/standby state i.e. if one of the link goes down then the traffic is shifted to the other 200 Mbps link. All the links are L3 links.

Currently I am using EIGRP only to route the traffic between both the sites on both the 10 Mbps links. I have configured specific static routes to use the 200 Mbps link only when the traffic is between 1.1.1.0/24 and 2.2.2.0/24 Servers.

Now I want to configure routing using all the links in EIGRP in such a way that the two 10 Mbps links work in equal load balancing, the 200 Mbps links should work in active/standby mode i.e. traffic should shift to secondary 200 Mbps link only in case the primary link goes down.

Any traffic with the destination of 2.2.2.0/24 servers should use the active 200 Mbps link and when the traffic is being generated/replied from 2.2.2.0/24 network should use the 200 Mbps active link. The traffic sourced/destined  for Y.Y.Y.Y/Y network should use the 10 Mbps links only.

 

Thanks in advance
0
Vipin Kumar
Asked:
Vipin Kumar
1 Solution
 
PredragNetwork EngineerCommented:
There are 2 ways to do what you need. PBR and static route. In both cases you need to use IP SLA.

access-list 100 permit ip any host y.y.y.y

route-map PBR permit 10
match ip address 100
set ip next-hop verify-availability a.a.a.a 1 track 1
set ip next-hop n.n.n.n

ip policy route-map PBR

And you need also do next (on L3 switch) if you want PBR to work on VLAN
(if you apply PBR to VLAN interface you will need this too)
Switch(config)# sdm prefer routing
Switch(config)# end
Switch# reload

track 1 ip sla 1 reachibility

ip sla 1
     icmp-echo z.z.z.z source-interface FastEthernetx/x
     timeout 1000
     threshold 1000
     frequency 5
ip sla schedule 1 life forever start-time now

other way:

ip route y.y.y.y 255.255.255.255 a.a.a.a track 1 <--- route is valid is track object is reachable if track object is not reachable use regular routing for destination

ip sla is the same in both cases
and of course you need to adopt all to you design IP addresses,track object etc
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now