Non-Router Id Addresses As Destinations And Hops - Nokia 7705 SAR-W Series Manual

MPLS and RSVP-TE
For a key entry to be valid, it must include a valid key, the current system clock value
must be within the begin and end time of the key entry, and the algorithm specified
must be supported by RSVP-TE.
RSVP-TE supports the following authentication algorithms:
Keychain errors are handled as follows.
3.3.1.5
The address of a configured loopback interface, other than the router ID, can be used
as the destination of an RSVP LSP. For a constrained-path LSP, CSPF searches for
the best path that matches the constraints across all areas or levels of the IGP where
this address is reachable. If the address is the router ID of the destination node, then
CSPF selects the best path across all areas or levels of the IGP for that router ID,
regardless of which area or level the router ID is reachable for as an interface.
The address of a loopback interface other than the router ID can also be configured
as a hop in the LSP path hop definition. If the hop is "strict" and corresponds to the
router ID of the node, the CSPF path may use any TE-enabled link to the
downstream node based on best cost. If the hop is "strict" and does not correspond
to the router ID of the node, CSPF will fail.
42
• HMAC-MD5
• HMAC-SHA-1-96
• HMAC-SHA-1
• HMAC-SHA-256
• If a keychain exists but there are no active key entries with an authentication
type that matches the type supported by RSVP-TE, inbound RSVP-TE packets
will not be authenticated and will be discarded and no outbound RSVP-TE
packets will be sent.
• If a keychain exists but the last key entry has expired, a log entry will be raised
indicating that all keychain entries have expired.
RSVP-TE requires that the protocol continue to authenticate inbound and
outbound traffic using the last valid authentication key.

Non-Router ID Addresses as Destinations and Hops

Use subject to Terms available at: www.nokia.com
© 2022 Nokia.
MPLS Guide
3HE 18686 AAAB TQZZA