From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Thu Dec 28 2006 - 19:04:53 ART
Assuming that LMI is end-to-end then yes if there is a failure
anywhere in the cloud it will affect the local VC status. However there
are many cases where LMI is not end-to-end, such as in the case of
provider handoffs, protocol translations, etc. In these cases you are
better off relying on something like Frame Relay EEK instead of LMI to
see if the circuit is actually up end-to-end.
HTH,
Brian McGahan, CCIE #8593 (R&S/SP)
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Mohamed Saeed
> Sent: Thursday, December 28, 2006 3:01 PM
> To: ccielab@groupstudy.com
> Subject: Frame Relay End-to-End Keepalive - Backup scenario
>
> Hi All,
>
>
>
> When a task asks for a PPP link to act as a backup to a frame relay
link
> using the "backup interface" command we have to use subinterface. That
> is because the physical interface retains its "up up" status even if
the
> other end is down.
>
>
>
> My question is should we use frame relay end-to-end keepalive feature
> too?
>
>
>
> By testing, when subinterface is used, the subinterface becomes down
if
> the other end is down. So, I do not think that frame relay EEK is
needed
> here. In IEWB, one of the tasks asked to activate the backup link if
the
> frame relay circuit got down at any point in the frame relay provider
> (Lab 17 task 3.1). The question wording pushing towards using EEK but
I
> really do not why it is must here. If the frame relay circuit got down
> at any point in the frame relay provider the subinterface on the local
> router will be down and thus the backup link will be activated.
>
>
>
> Any comments will be appreciated.
>
>
>
> Kind Regards
>
>
This archive was generated by hypermail 2.1.4 : Tue Jan 02 2007 - 07:50:39 ART