Configuring rsvp authentication, Configuring rsvp-te gr – H3C Technologies H3C S7500E Series Switches User Manual
Page 108

3-26
z
Reservation confirmation is initiated by the receiver, which sends the Resv message with an
object requesting reservation confirmation.
z
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.
Follow these steps to configure RSVP authentication:
To do…
Use the command...
Remarks
Enter system view
system-view
––
Enter interface view of MPLS TE
link
interface
interface-type
interface-number
––
Enable RSVP authentication
mpls rsvp-te authentication
{ cipher | plain } auth-key
Required
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.
Follow these steps to configure RSVP-TE GR on each device to act as the GR restarter or a GR
helper:
To do…
Use the command...
Remarks
Enter system view
system-view
—
Enter MPLS view
mpls
—
Enable global RSVP hello
extension
mpls rsvp-te hello
Required
Disabled by default