From: khurram noor (smartcapricon82@gmail.com)
Date: Sun Nov 30 2008 - 18:19:33 ARST
Thanks pradeep... very nice elaboration.
On Mon, Dec 1, 2008 at 1:14 AM, Pradeep <chanpraddy@gmail.com> wrote:
> Keepalive messages check the health of a link. The keepalive* *timer is
> the number of seconds a router waits between sending keepalive messages to a
> peer. If no response from the peer is received, the local router retransmits
> the keepalive message up to five times. If no response is received from the
> peer, the local router brings down the link and withdraws the route from the
> routing table.
>
> **After the link is brought down, the local router continues to transmit
> keepalive messages to the peer. If a response is received from the peer, the
> link is brought up.
>
> **Use the *no keepalive *command to disable the keepalive timer.
>
> By setting no-keepalives, the link layer is forced to stay up. If the
> setting remains at keepalive, the router will recognize that the same
> link-layer keepalives are being looped back and will bring the link layer
> down.
>
>
> HTH
>
> Pradeep
>
>
> On Sun, Nov 30, 2008 at 2:58 PM, khurram noor <smartcapricon82@gmail.com>wrote:
>
>> Can anyone explains the logic behind inserting "no keepalives" in a
>> frame
>> relay interface configuration mode. i have a scenerio in which i have a
>> frame-relay point-point connectivity... but the link does not come up
>> until
>> i assign "no keepalives" under physical interface of both routers along
>> with
>> clock rate on one of the routers.
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>>
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> "Silence is the toughest argument to refute"
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Mon Dec 01 2008 - 08:18:32 ARST