04-04-2013 09:28 AM - edited 03-04-2019 07:29 PM
I have a pair of circuits from a vendor to our MPLS cloud.
The primary is a straight MPLS circuit at 1Gb
The secondary is now being provided on the vendors next generation network with includes local routing within the metro area.
They are provided to separate locations that are linked with private fibre. My equipment at each site sits on OSPF area 1 for the neighbor ship to the vendors CPE.
they both also have a neighborship with each other in the same process and area.
I am attempting to send traffic to a specific site through the secondary link however the secondary router prefers the rpimary for all it's routes.
I've tried using route maps to change the metrics or even remove routes from the primary CPE but nothing seems to be working, what am I doing wrong or is this even possible?
RTR1 Config
interface Vlan300
description WAN Routing to Vendor MPLS
ip address 10.172.5.17 255.255.255.240
ip ospf cost 100
interface Vlan451
description MAN Routing to Backupsite
ip address 10.170.147.117 255.255.255.252
ip ospf cost 200
router ospf 1
router-id 209.53.232.217
auto-cost reference-bandwidth 100000
network 10.170.147.116 0.0.0.3 area 1
network 10.172.5.16 0.0.0.15 area 1
default-information originate always
RTR2 Config
interface Vlan300
description Backup Site Vendor MPLSv2
ip address 10.163.0.6 255.255.255.252
interface vlan 451
description Man Routing to Primary
ip address 10.170.147.118 255.255.255.252
ip ospf cost 200
router ospf 1
auto-cost reference-bandwidth 100000
network 10.163.0.4 0.0.0.3 area 1
network 10.170.147.116 0.0.0.3 area 1
distribute-list route-map MPLSv2_Site in
ip access-list standard MPLSv2_Site
permit 10.171.128.96
permit 10.52.145.85
permit 10.173.14.0 0.0.0.255
route-map MPLSv2_Site deny 10
match ip address Highland_CE
match interface Vlan451
!
route-map MPLSv2_Site permit 20
Any ideas?
04-04-2013 11:01 AM
Hello Bruce,
I would try these two scenarios, it is up to you which better suits your needs:
1) configure Policy Based routing, but it has to be done on both sites so interesting traffic will be routed via backup link and not via lower cost connection (requests and also responses).
There can be problem with placing route map on interface, if desired networks are reachable via multiple interfaces, route map has to be applied to all possible interfaces.
2) I would use probably this one. Configure static routes on RTR1 and RTR2 with lower AD than OSPF (static routes will be prefered). Then I would configure IP SLA to track if backup link is working, if yes, static routes will be installed into routing table and this path will be used, if not, regular path will be used.
- with this scenario you can manipulate which traffic will take which path and with IP SLA and TRACKing you do not have to worry about failover if backup link fail.
Best Regards
Please rate all helpful posts and close solved questions
04-04-2013 11:56 AM
hello
There seems to be some anomalies with your config
1) Your are permanently advertising a default on R1
2) same ospf cost for vlan 451 on each router
3) You are filtering on R2
4) auto cost ref bandwidth for 1gb links is giving 1gb links a cost of 10
Are these settings the result of trying to manipulate the paths?
Res
Paul
Sent from Cisco Technical Support iPad App
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: