home

Supported platforms

Vyatta documentation

Learn how to install, configure, and operate the Vyatta Network Operating System (Vyatta NOS) and Orchestrator, which help drive our virtual networking and physical platforms portfolio.

Configuring MPLS RSVP secondary path

How to configure MPLS RSVP secondary paths

RSVP-TE must be enabled on interfaces before MPLS RSVP is supported and the MPLS RSVP tunnel must be configured.
You can configure the same attributes for an RSVP secondary path as for the primary path, such as the bandwidth, affinities to include or exclude, and so on, except for fast-reroute.

To configure an MPLS RSVP secondary path, perform one or more of the following steps in configuration mode.

  1. To configure the bandwidth to be reserved along the secondary path, enter the protocols mpls-rsvp tunnels tunnel <name> secondary bandwidth <1-10000000000> command. The interfaces must be configured with a maximum reservable bandwidth before tunnels can reserve bandwidth on them. By default, no bandwidth is reserved.
    vyatta@R1# set protocols mpls-rsvp tunnels tunnel pe1-pe2 secondary 100000000
  2. To configure the secondary path to follow the full or partial explicit path, enter the protocols mpls-rsvp tunnels tunnel <name> secondary explicit-path <name> command. The secondary path will follow the full or partial explicit path, which must be defined in the globals section. The default is to follow the CSPF calculated path.
    vyatta@R1# set protocols mpls-rsvp tunnels tunnel pe1-pe2 secondary explicit-path <name>
  3. To configure the secondary path so that it cannot be reoptimized, enter the protocols mpls-rsvp tunnels tunnel <name> secondary lockdown command.
    vyatta@R1# set protocols mpls-rsvp tunnels tunnel pe1-pe2 secondary lockdown
  4. To create a list of affinities to include for the path, enter the protocols mpls-rsvp tunnels tunnel <name> secondary path-selection affinities constraints include-any command. The path will only be able to use interfaces bound to the included administrative groups.
    vyatta@R1# set protocols mpls-rsvp tunnels tunnel pe1-pe2 secondary path-selection affinities constraints include-any
  5. To configure the name of administrative group to include for the path, enter the protocols mpls-rsvp tunnels tunnel <name> secondary path-selection affinities constraints include-any affinity-names <name> command.
    vyatta@R1# set protocols mpls-rsvp tunnels tunnel pe1-pe2 secondary path-selection affinities constraints include-any affinity-names <name>
  6. To create a list of affinities to exclude for the path, enter the protocols mpls-rsvp tunnels tunnel <name> secondary secondary path-selection affinities constraints exclude-any command. The path will not be able to use interfaces bound to the excluded administrative groups.
    vyatta@R1# set protocols mpls-rsvp tunnels tunnel pe1-pe2 secondary  path-selection affinities constraints exclude-any
  7. To configure the name of administrative group to exclude for the path, enter the protocols mpls-rsvp tunnels tunnel <name> secondary path-selection affinities constraints exclude-any affinity-names <name> command.
    vyatta@R1# set protocols mpls-rsvp tunnels tunnel pe1-pe2 secondary path-selection affinities constraints exclude-any affinity-names <name>
  8. To configure a hold priority for this session , enter the protocols mpls-rsvp tunnels tunnel <name> secondary priority hold <0-7> command. The default is 0 (highest), which means it will not be pre-empted by higher priority sessions. Priority 7 is the lowest priority.
    vyatta@R1# set protocols mpls-rsvp tunnels tunnel pe1-pe2 secondary priority hold 3
  9. To configure a setup priority for this session, enter the protocols mpls-rsvp tunnels tunnel <name> secondary priority setup <0-7> command. The default is 7 (lowest), which means it cannot pre-empt lower priority sessions.
    vyatta@R1# set protocols mpls-rsvp tunnels tunnel pe1-pe2 secondary priority setup 3