Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Tunnel Layer and Layer 3 Routing Interaction

 

Modifications to the network model (e.g. tunnels, demands/flows, network elements, design options) usually require tunnels or flows to be rerouted. In Paragon Planner, this rerouting occurs in the following order:

  • If you are in Layer 3 and a reroute is triggered, tunnels will be rerouted first, followed by demands/flows.

  • If you are in Tunnel Layer and a reroute is triggered, then only tunnels will be rerouted while in Tunnel layer. The moment you switch into Layer 3, however, the Layer 3 demands/flows will then be rerouted.



Additional Information



Table 1: Commands Modeled Using Affinity and Mask Feature

 

Corresponding Cisco Commands

Setting link attributes

mpls traffic-eng attribute-flags attributes

Setting tunnel affinity and mask

tunnel mpls traffic-eng affinity affinity [ mask mask ]

 

Corresponding Juniper Commands for the mpls protocol

Defining

Administrative

Groups

admin-groups {

group-name 1;

group-name 2;

...

}

Selecting admin groups for a link

interface interface name {

admin-group [ group-name group-name ... ];

}

Setting admin groups for a tunnel

label-switched-path lsp-path-name {

to address;

...

primary path-name {

admin-group {

exclude [ group-name group-name ... ];

include [ group-name group-name ... ];

include-all [ group-name group-name ... ];

include-any [ group-name group-name ... ];

}

}