H3C SR8800 10G Mpls Configuration Manual page 79

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
1. Enter system view.
2. Enter interface view of MPLS TE link.
Enable RSVP authentication.
3.
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
1. Enter system view.
2. Enter MPLS view.
Enable global RSVP hello
3.
extension.
4. Enable MPLS RSVP-TE GR.
5. Set the RSVP-TE GR restart
timer.
6. Set the RSVP-TE GR recovery
timer.
7. Enter interface view of MPLS
TE link.
8. Enable RSVP hello extension
for the interface.
Command
system-view
interface interface-type interface-number
mpls rsvp-te authentication { cipher | plain } auth-key
Command
system-view
mpls
mpls rsvp-te hello
mpls rsvp-te graceful-restart
mpls rsvp-te timer graceful-restart
restart restart-time
mpls rsvp-te timer graceful-restart
recovery recovery-time
interface interface-type
interface-number
mpls rsvp-te hello
68
Remarks
N/A
N/A
Disabled by default
Disabled by default
Optional
120 seconds by default
Optional
300 seconds by default
N/A
Disabled by default