Configuring rsvp hello extension, Configuring rsvp authentication – H3C Technologies H3C S6800 Series Switches User Manual

Page 157

Advertising
background image

144

Step Command

Remarks

5.

Configure the retransmission

interval for reliable RSVP
message delivery.

rsvp reduction retransmit interval
retrans-timer-valu
e

By default, the RSVP message
retransmission interval is 500
milliseconds.
This command takes effect after
reliable RSVP message delivery is

enabled by using the rsvp
reduction srefresh reliability

command.

Configuring RSVP hello extension

When RSVP hello extension is enabled on an interface, the device receives and sends hello messages
through the interface to detect the neighbor's status.
If the device receives a hello request from the neighbor, the device replies with a hello ACK message. If

the device receives no hello request from the neighbor within the interval specified by the hello interval

command, the device sends hello requests to the neighbor.
When the number of consecutive lost hellos or erroneous hellos from the neighbor reaches the maximum
(specified by the hello lost command), the device determines the neighbor is in fault. If GR is configured,

the device serves as a GR helper to help the neighbor to restart. If FRR is configured, the device performs

an FRR. For more information about FRR, see "

Configuring MPLS TE

."

To configure RSVP hello extension:

Step Command

Remarks

1.

Enter system view.

system-view

N/A

2.

Enter RSVP view.

rsvp

N/A

3.

Configure the maximum
number of consecutive lost or

erroneous hellos.

hello lost times

By default, the maximum number is
4.

4.

Configure the interval for

sending hello requests.

hello interval interval

By default, hello requests are sent
every 5 seconds.

5.

Return to system view.

quit

N/A

6.

Enter interface view.

interface interface-type
interface-number

N/A

7.

Enable RSVP hello extension. rsvp hello enable

By default, RSVP hello extension is
disabled.

Configuring RSVP authentication

RSVP adopts hop-by-hop authentication to prevent fake resource reservation requests from occupying

network resources. The interfaces at the two ends of a link must use the same authentication key.
RSVP authentication can be configured in the following views:

RSVP view—Configuration applies to all RSVP security associations.

Advertising