The MPLS-OPS Archive

[Carlos Patriawan <carlos@xebeo.com>]

Right,
In some implementation 30 secs is average between 2 refresh time period.


Carlos

Rajiv Asati wrote:

> Sandeep,
>
> It is kind of confusing. :)
>
> Refresh messages are actually jittered by 50%.
> So you should expect refresh messages to arrive anywhere between 15s and 45s.
>
> Rajiv
>
> At 08:32 PM 10/15/2002, Sandeep B wrote:
> >If I have setup my RSVP refresh time to be 30 secs then all my path and
> >resvs should be refreshed approx. every 30 secs. But when I scale a box to
> >setup 2000 lsps with both Juniper and Cisco I see it not being refreshed
> >exactly at 30 secs but being done approx. within 45 secs.
> >
> >This behaviour is not consistent with the theory that a node would wait
> >keep-multiplier * refresh time before deleting a session. In this case a
> >previous hop or nexthop would expire on missing just a single refresh packet
> >if keep-multiplier is 3.
> >
> >Comments from Cisco/Juniper???
> >
> >-Sandeep
> >
> >
> >_________________________________________________________________
> >Unlimited Internet access for only $21.95/month.  Try MSN!
> >http://resourcecenter.msn.com/access/plans/2monthsfree.asp
> >
> >-------
> >The MPLS-OPS Mailing List
> >Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> >Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
>
> -------
> The MPLS-OPS Mailing List
> Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml


-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml