110Step Command Remarks1. Enter system view. system-view N/A2. Enter interface view of MPLSTE link.interface interface-typeinterface-number N/A3. Enable the reliabilitymechanism of RSVP-TE. mpls rsvp-te reliability Optional.Disabled by default.4. Enable retransmission.mpls rsvp-te timer retransmission{ increment-value[ increment-value ] |retransmit-value[ retrans-timer-value ] } *Optional.Disabled by default.5. Enable summary refresh. mpls rsvp-te srefresh Optional.Disabled by default.Configuring the RSVP hello extensionRSVP hello extension tests the reachability of RSVP neighboring nodes. It is defined in RFC 3209.To configure the RSVP hello extension:Step Command Remarks1. Enter system view. system-view N/A2. Enter MPLS view. mpls N/A3. Enable global RSVP helloextension. mpls rsvp-te hello Disabled by default.4. Configure the maximumnumber of consecutive hellosthat must be lost before thelink is considered failed.mpls rsvp-te hello-lost timesOptional.By default, the link is consideredfailed if three consecutive hellosare lost.5. Configure the hello interval. mpls rsvp-te timer hello timevalue Optional.The default is 3 seconds.6. Exit to system view. quit N/A7. Enter interface view of MPLSTE link.interface interface-typeinterface-number N/A8. Enable interface RSVP helloextension. mpls rsvp-te hello Disabled by default.Configuring RSVP-TE resource reservation confirmationReservation confirmation is initiated by the receiver, which sends the Resv message with an objectrequesting reservation confirmation.Receiving the ResvConf message does not mean resource reservation is established. It only indicates thatresources are reserved on the farthest upstream node where the Resv message arrived and the resourcescan be preempted.
