62
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:
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
Disabled by default
NOTE:
Do not configure both FRR and RSVP authentication on the same interface.
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 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
Enable MPLS RSVP-TE GR
mpls rsvp-te graceful-restart
Required
Disabled by default
Set the RSVP-TE GR restart timer
mpls rsvp-te timer graceful-restart
restart
restart-time
Optional
120 seconds by default
Set the RSVP-TE GR recovery timer
mpls rsvp-te timer graceful-restart
recovery
recovery-time
Optional
300 seconds by default
Enter interface view of MPLS TE link
interface
interface-type
interface-number
—
