The MPLS WG Archive

[George Swallow <swallow@cisco.com>]

Ping -

> > If you have multiple LSPs between two nodes then it may be hard to
> > determine that an LSP has failed, since you will get Echo-Reply
> > messages from the other tunnels.  The draft should recommend use of
> > the Identifier field in the Echo message in this case.
> >
> 
> When using LSP-ping, as we mentioned in 5.1, the echo message should
> have enough information to identify an LSP. That implies, the message
> will have RSVP Session and Sender-Template objects. I will articulate it
> more explicitly soon.

As I understand the draft you monitor tunnels with normal ICMP pings
and only use the LSP-ping when something appears awry.  Right?  What I
was referring to in the above comment is the *normal* ICMP ping.  

> > There needs to be a means of clearing the LSP-echo object from the
> > RESV message.  (So that the test can be repeated at a later point).
> > I would simply add a timer that gets set when you first insert the
> > LSP-ping object in the RESV message and renewed each time you receive
> > a subsequent LSP-ping message.  Once the messages cease, the timer
> > will fire and you then send a RESV message without the LSP-ping
> > object.
> > 
> 
> Interesting. How do I inform the egress about the timer? 

I was just thinking of a default (perhaps configurable) say 1 minute?

> In the first
> LSP-ping message, or Path? And how do I turn it off?

Keep sending LSP-pings.

...George

==================================================================
George Swallow       Cisco Systems                   (978) 244-8143
                     250 Apollo Drive
                     Chelmsford, Ma 01824