OSPF between PAN devices

cancel
Showing results for 
Search instead for 
Did you mean: 

OSPF between PAN devices

L2 Linker

Hi all,

I have the following scenario:

CPD 1: Internet ISP1 -- PAN1 -- ROUTER1

CPD 2: Internet ISP2 - PAN 2 -- ROUTER2

And a layer 2 connection between CPD1 and CPD2 (in different locations). Initially, there were only router1 and router2 (with their respective ISP Internet connections) with OSPF area 0; now,  I've added a PAN device to each CPD, including them in OSPF area 0, but not in HA.

My first idea was to:

- Each location uses their ISP internet access, located in the same building.

- In case of failure, a location will use the other ISP internet access, using OSPF routing.

These scenario could be possible if the failure point are the PAN devices. But if the failure is in any of the Internet ISP routers (not talking OSPF and controlled by the ISP provider), how can I modify the OSPF path costs to use the other ISP router? Is there any possibility of OSPF track?

1 ACCEPTED SOLUTION

Accepted Solutions

L6 Presenter

Cant you just use route health injection/IP-SLA on ROUTER1/ROUTER2 instead?

So each PAN devices will just have their physical linknets along with default route to each ISP.

This way you can withdraw the route going through each PA when you fail to ping Internet ISPx or the next hop from there (make sure that you define egress interface when you setup the ip-tracking so it wont track by routingtable but by physical interface)?

Edit: The result would be:

ROUTER1: ping Internet ISP1, if ping fails remove default route pointing to PA1.

ROUTER2: ping Internet ISP2, if ping fails remove default route pointing to PA2.

and OSPF (or whatever) between ROUTER1 and 2 will handle metric/costs and where each client can find the best way out.

View solution in original post

2 REPLIES 2

L6 Presenter

Cant you just use route health injection/IP-SLA on ROUTER1/ROUTER2 instead?

So each PAN devices will just have their physical linknets along with default route to each ISP.

This way you can withdraw the route going through each PA when you fail to ping Internet ISPx or the next hop from there (make sure that you define egress interface when you setup the ip-tracking so it wont track by routingtable but by physical interface)?

Edit: The result would be:

ROUTER1: ping Internet ISP1, if ping fails remove default route pointing to PA1.

ROUTER2: ping Internet ISP2, if ping fails remove default route pointing to PA2.

and OSPF (or whatever) between ROUTER1 and 2 will handle metric/costs and where each client can find the best way out.

Yes, good idea... I'll try it. But it would be great that PA could track routes for dynamic routing; PBF is very useful, but not enough for this kind of scenarios.

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!