RE: OSPF Failover to another Router

From: Lloyd Ardoin (Lloyd@TheWizKid.biz)
Date: Wed Mar 25 2009 - 17:51:36 ART

Use IP SLA on R5 to either ping it's own IP address on s0/0 or it's neighbor's
address and use as a tracked object. Build a host based access-list to match
OSPF traffic between R5 and R4. Build a route map to match the access-list and
set the next hop towards R2 as long as their is reach ability towards R2 the
OSPF adjacency between R5 and R4 will not come up. If the link between R5 and
R2 go down the policy route will not longer route towards R2 which will allow
the OSPF traffic from R5 to go towards R4 and the adjacency will come up. If
you regain reach ability towards R2 the PBR kicks back in and the adjacency
between R5 and R4 comes down.

Had this in a lab and it was an eye opener!

HTH,
Lloyd

From: Wouter Prins
Sent: Wed 3/25/2009 3:05 PM
To: naveen M S
Cc: CCIE R/S, Groupstudy
Subject: Re: OSPF Failover to another Router

Smells like the backup command?

2009/3/25 naveen M S <navin.ms@gmail.com>

> Group,
>
> This is the task I have.
>
> R5 (S0/0)-----(FrameRelay)------R2
> | E0/0
> |
> |
> R4
>
> 1. R5 should maintain adjacency with R2 as long as FrameRelay is Up.
> 2. If FrameRelay link goes down, form a new adjacency with R4 on Ethernet
> link.
> 3. Solution should be dynamic. When FR link is Up, no adjacency should
> exist b/n R5 and R4.
> 4. The Ethernet interface b/n R5 and R4 should be always up.
> 5. Neighbor statements are permitted.
>
> All ideas are welcome.
> Naveen.
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
> 

--
Wouter Prins
wp@null0.nl
0x301FA912

Blogs and organic groups at http://www.ccie.net

This archive was generated by hypermail 2.1.4 : Mon Apr 06 2009 - 06:44:07 ART