From: Herbert Maosa (asawilunda@googlemail.com)
Date: Tue Jul 31 2007 - 07:52:03 ART
Ben,
EEKS do bring down the PVC when the remote side is down. I know this
for sure because we are doing this in our operational network and we
rely on it heavily for failover in order to meet some stringent SLAs.
I believe the discussion on EEKS is how to bring down the Interface if
it is multipoint. But it definitely works on point-to-point PVCs.
Herbert.
On 7/31/07, Ben <bmunyao@gmail.com> wrote:
> Hi
>
> When a question requires HSRP on LAN with R3 and R4 as active/backup, and R4
> taking over when R3 looses FR connection, how can you track the FR
> interface?
>
> Here is an example:
>
> .3
> |-------------------------------R3 \
> | \
> |10.10.1.0/24 FR cloud
> | /
> |-------------------------------R4 /
>
> Assume FR is configured on physical interface. Would the following qualify
> as a solution?
>
> R3
> int f0/0
> ip add 10.10.1.3 255.255.255.0
> stand 1 priority 105
> stand 1 preempt
> stand 1 track s0/0
> stand 1 ip 10.10.1.254
>
> R4
> int f0/0
> ip add 10.10.1.4 255.255.255.0
> stand 1 preempt
> stand 1 ip 10.10.1.254
>
> I presume this use of the track keyword only tracks the line-protocol on
> s0/0, and will therefore not detect when R3 looses IP connectivity to the
> other end of its DLCI. A variation of the stand 1 track s0/0 on R3 would be
>
> track 1 interface s0/0 line-protocol
> int f0/0
> stand 1 track 1
>
>
> Another recent discussion on EEK indicated that EEK will not bring down the
> interface when the other end is not reachable. How can we then meet the
> requirements of the question? Do we have do use a GRE tunnel with keepalive
> over the FR link, and track that? Is there any other alternative?
>
> TIA
> Ben
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
-- Kindest regards, hm
This archive was generated by hypermail 2.1.4 : Sat Aug 18 2007 - 08:17:42 ART