EasyManuals Logo
Home>Juniper>Software>BGP - CONFIGURATION GUIDE V 11.1.X

Juniper BGP - CONFIGURATION GUIDE V 11.1.X User Manual

Juniper BGP - CONFIGURATION GUIDE V 11.1.X
748 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #324 background imageLoading...
Page #324 background image
The receiver uses the key ID and the sender’s address to determine the relevant
security association. The key ID is extracted from the received integrity object. The
address of the sending interface is extracted from the rsvp_hop object, if present,
or from the packet header if the message does not include the rsvp_hop object. The
receiver then recomputes the message digest using the association key and algorithm
and compares it to the digest received from the peer.
If the digests match, RSVP checks the received sequence number. Every message
received from a sender after the first authenticated message must have a sequence
number greater than the number from a previously authenticated message from that
sender. Messages with invalid sequence numbers are discarded.
If the sequence number is valid, then the RSVP message is authenticated and
forwarded for normal RSVP processing. Unauthenticated messages are discarded.
To configure RSVP-TE MD5 authentication:
1. Assign a key to the interface for MD5 authentication between RSVP peers.
host1(config-if)#mpls rsvp authentication key 34udR973j
2. Enable MD5 authentication on the RSVP-TE interface.
host1(config-if)#mpls rsvp authentication
To clear the security association on a receiving peer for the specified sending peer:
â–  Issue the clear mpls rsvp authentication command:
host1#clear mpls rsvp authentication 10.3.5.1
Related Topics â–  Basic MPLS Configuration Tasks on page 268
â–  Additional RSVP-TE Configuration Tasks on page 286
â–  clear rsvp authentication
â–  mpls rsvp authentication
â–  mpls rsvp authentication key
Configuring RSVP-TE Fast Rerouting with RSVP-TE Bypass Tunnels
The fast reroute extensions to RSVP-TE enable you to create a single LSP, known as
a bypass tunnel, to back up a set of LSPs by bypassing specific links in the LSP. In
the event of a failure in any link of the protected RSVP-TE LSP (the primary LSP),
MPLS redirects traffic to the associated bypass tunnel in tens of milliseconds.
You must statically configure the bypass tunnel for each link that you want to protect
on each router in the LSP. The bypass tunnel must intersect the protected LSP at two
locations. The start of the bypass tunnels is the point of local repair (PLR), which is
the head end of the protected link. The bypass tunnel terminates downstream of the
PLR on the node that represents the end of the bypassed link on the primary LSP.
288 â–  Configuring RSVP-TE Fast Rerouting with RSVP-TE Bypass Tunnels
JUNOSe 11.1.x BGP and MPLS Configuration Guide

Table of Contents

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the Juniper BGP - CONFIGURATION GUIDE V 11.1.X and is the answer not in the manual?

Juniper BGP - CONFIGURATION GUIDE V 11.1.X Specifications

General IconGeneral
BrandJuniper
ModelBGP - CONFIGURATION GUIDE V 11.1.X
CategorySoftware
LanguageEnglish

Related product manuals