Using Unnumbered Point-to-Point Interface in RSVP
Page 58 7450 ESS MPLS Guide
When the MP node receives the PATH message over the bypass LSP, it will create the merge-point
context for the protected LSP and associate it with the existing state if any of the following is
satisfied:
• Change in C-Type of the RSVP_HOP object, or
• C-Type is IF_ID RSVP_HOP and did not change but IF_ID TLV is different, or
• Change in IPv4 Next/Previous Hop Address in RSVP_HOP object regardless of the C-
Type value.
These procedures at PLR and MP nodes are followed in both link-protect and node-protect FRR.
Note that if the MP node is running a pre-R11 implementation, it will reject the new IF_ID C-Type
and will drop the PATH over bypass. This will result in the protected LSP state expiring at the MP
node, which will tear down the path. This will be the case in general when node-protect FRR is
enabled and the MP node does not support unnumbered RSVP interface.
To Next Page
Loading...
