authentication-key (Protocols RSVP)
Syntax
authentication-key key;
Hierarchy Level
[edit logical-systems logical-system-name protocols rsvp interface interface-name], [edit logical-systems logical-system-name protocols rsvp peer-interface peer-interface-name], [edit protocols rsvp], [edit protocols rsvp interface interface-name], [edit protocols rsvp peer-interface peer-interface-name]
Description
Authentication key (password). Neighboring routers use the password to verify the
authenticity of packets sent from this interface or peer interface.
To authenticate node hellos or remote messages between
the Point of Local Repair (PLR) to the Merge Point (MP), enable
authentication-key at the [edit protocols
rsvp] hierarchy level.
It is recommended to use the authentication-key configuration at the
[edit protocols rsvp] hierarchy level for the RSVP
node-neighbor. Because non-RSVP interfaces do not have RSVP authentication key, the
authentication-key configuration allows the packets to arrive
at any interface regardless of RSVP interfaces configuration being enabled or
not.
To avoid fxp inheriting the authentication-key configuration
statement, use specific physical interfaces such as <ge-*> and <ae*>
in the group configuration. We don't recommend to use wildcard pattern
<*>.
RSVP uses HMAC-MD5 authentication, which is defined in RFC 2104, HMAC: Keyed-Hashing for Message Authentication.
All routers that are connected to the same IP subnet must use the same authentication scheme and password.
Options
key—Authentication
password. It can be 1 through 16 contiguous digits or letters. Separate
decimal digits with periods. Separate hexadecimal digits with periods
and precede the string with 0x. If you include spaces in the password,
enclose the entire password in quotation marks (" ").
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced before Junos OS Release 7.4.