H3C Technologies H3C SR8800 - Manual (Page 79)

68
NOTE:
•
Reservation confirmation is initiated by the receiver, which sends the Resv message with an object
requesting reservation confirmation.
• Receiving the ResvConf message does not mean resource reservation is established. It only indicates that
resources are reserved on the farthest upstream node where the Resv message arrived and the resources
can be preempted.
Configuring RSVP authentication
RSVP adopts hop-by-hop authentication to prevent fake resource reservation requests from occupying
network resources.
It requires that the interfaces at the two ends of a link must share the same authentication key to exchange
RSVP messages.
To configure RSVP authentication:
Step Command
1. Enter system view. system-view
2. Enter interface view of MPLS TE link. interface interface-type interface-number
3. Enable RSVP authentication. mpls rsvp-te authentication { cipher | plain } auth-key
NOTE:
FRR and RSVP authentication cannot run at the same time.
Configuring RSVP-TE GR
The RSVP-TE GR function depends on the extended hello capability of RSVP-TE. Be sure to enable the
extended hello capability of RSVP-TE before configuring RSVP-TE GR.
To configure RSVP-TE GR on each router to act as the GR restarter or a GR helper:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter MPLS view. mpls N/A
3. Enable global RSVP hello
extension.
mpls rsvp-te hello Disabled by default
4. Enable MPLS RSVP-TE GR. mpls rsvp-te graceful-restart Disabled by default
5. Set the RSVP-TE GR restart
timer. mpls rsvp-te timer graceful-restart
restart restart-time Optional
120 seconds by default
6. Set the RSVP-TE GR recovery
timer. mpls rsvp-te timer graceful-restart
recovery recovery-time Optional
300 seconds by default
7. Enter interface view of MPLS
TE link. interface interface-type
interface-number
N/A
8. Enable RSVP hello extension
for the interface.
mpls rsvp-te hello Disabled by default