MPLS Traffic Engineering and Fast Reroute for MetaCentrum
CESNET technical report 11/2010
Pavel Šmrha, Josef Verich
Received 22. 11. 2010
Abstract
The paper deals with the design and implementation of MPLS Traffic Engineering (TE) and Fast Reroute (FRR) link and node protection in the CESNET2 backbone to optimize MetaCentrum traffic paths to use available bandwidth with high availability. MPLS-TE primary tunnels are defined by explicit path specifications to use otherwise underutilized but available network bandwidth. There are two sets of MPLS-TE primary tunnels: the first one for L2 VPLS traffic optimization among three MetaCentrum data centers (Prague, Brno and Pilsen) and the other one for L3 IPv4 traffic optimization among four MetaCentrum data centers (CESNET Prague, UK Prague, Brno and Pilsen). High availability of these MPLS-TE tunnels is ensured by automatically created next-hop and next-next-hop backup tunnels to be used by the Fast Reroute mechanism for link and node protection in tens of milliseconds with respect to Shared Risk Link Group (SRLG) dependencies.
Keywords: MPLS, Traffic Engineering, Fast Reroute, MetaCentrum, VPLS
1 Introduction
The main motivation of this work was to provide four MetaCentrum data centers with the best communications environment available in the current CESNET2 MPLS/IP backbone infrastructure through optimal configuration of its routers. Formerly, the internal MetaCentrum traffic among their physical sites in Prague, Brno and Pilsen have obeyed the same shortest path routing as other ordinary traffic because dynamic load balancing between more than one optimal paths is administratively prohibited. This might cause the problem of worsening latency for traffic patterns sharing some heavier utilized links while other underutilized shortest paths were available (e.g. traffic between Pilsen and Brno has been routed via Prague even if another significantly less utilized optimal 10 Gb/s shortest path with the same number of hops via Ceske Budejovice has been available). Thus we decided to implement traffic engineering with fast reroute for internal MetaCentrum traffic to ensure the least possible latency while providing sufficient fault-tolerance.
Redundant CESNET2 MPLS based network topology enables to make use of its parallel transmission paths by explicitly configured MPLS traffic engineering (MPLS TE) tunnels to optimize load balancing for some kind of traffic on the otherwise underutilized links. Moreover, MPLS TE can be combined with advanced MPLS features such as Fast Reroute (FRR) and Shared Risk Link Groups (SRLG) to achieve both super-fast convergence and high availability in case of link and/or node failures.
During the initial phase of the MPLS TE implementation for internal MetaCentrum data communications optimization among its individual data centers we created two sets MPLS-TE primary tunnels: the first one for L2 VPLS traffic optimization among three MetaCentrum data centers (Prague, Brno and Pilsen) and the other one for L3 IPv4 traffic optimization among four MetaCentrum data centers (CESNET Prague, UK Prague, Brno and Pilsen). These primary MPLS TE tunnels are preferably set up by predefined optimal explicit paths (with some constrain attributes), if they are available in the actual network topology (without failures). Otherwise (in case of failures), suboptimal dynamic primary paths (with some constrain attributes) are temporarily set up to be automatically replaced with predefined optimal explicit paths when they are available (after overcoming failure network conditions, temporary topology changes etc.). FRR is appropriately configured by automatically created backup tunnels to provide NHOP link protection and NNHOP node (and link) protection simultaneously.
2 MPLS TE optimization for MetaCentrum traffic
By using the MPLS TE optimization for internal MetaCentrum traffic, we can achieve both better utilization of the underlying communication infrastructure by explicit load balancing and less vulnerability to special kind of hardware failures, especially with respect to enhanced services (ES) 600-ES20-10G3CXL modules in the Cisco 7600 routers used for VPLS implementation in the CESNET2 network. The VPLS functionality of Cisco 7600 routers is supported only on ES interfaces which implies the need to ensure that all incoming/outgoing VPLS traffic on the redundantly connected routers goes only through these ES interfaces under all possible failure scenarios, otherwise VPLS services are not available.
Both MPLS TE tunnel sets for VPLS and IPv4 MetaCentrum traffic are logically mutually independent and are constructed in the way to preserve the former qualitative communication parameters of the shortest end-to-end paths between the individual MetaCentrum computers/nodes (to guarantee as low latency as possible) and to enable simultaneous communication through both 10 Gbps MPLS core facing ES interfaces of the Cisco 7600 routers in each CESNET2 GigaPoP through which the individual MetaCentrum data centers are interconnected.
Each MPLS TE tunnel is primarily configured to use an optimal statically defined explicit path through predefined MPLS core routers. In case of failure dynamic tunnel reconfiguration via any shortest path (with predefined constrain attributes) is temporarily allowed to achieve more robustness. To fulfill the above MPLS TE goals for the set of VPLS pseudowires in case of dynamic reconfiguration, some additional special constrains must be imposed on the tunnel attributes to achieve the requirement of using only VPLS capable ES interfaces for all incoming/outgoing traffic at the tunnel head-ends and tail-ends. It can be easily done by setting the “noVPLS” MPLS TE affinity bit to 0x1 on all non-ES (no VPLS capable) physical interfaces in the router configuration for the VPLS set of tunnel head-ends and tail-ends. Thus the VPLS set of dynamically created temporary tunnels must be compliant with the requirement of discretionary attributes for eligible paths (affinity 0x0 mask 0x1).
Table 1 contains the configuration of the symmetric one-way MPLS TE tunnels for VPLS pseudowires dedicated to MetaCentrum L2 traffic, which is also shown in Figure 1, including the inadmissible dashed lines (with configured “noVPLS” TE affinity bit 0x1) which must not be used to create temporary dynamic tunnels, because they would not have their head-ends or tail-ends on the (VPLS capable) ES interfaces of the Cisco 7600 routers.
| MetaCentrum | Router | MPLS TE tunnel | Explicit VPLS path |
|---|---|---|---|
| CESNET Prague | R92 | Tunnel 2098 | R92→R107→R119→R98 |
| CESNET Prague | R92 | Tunnel 2099 | R92→R119→R99 |
| Brno | R98 | Tunnel 2092 | R98→R119→R107→R92 |
| Brno | R98 | Tunnel 2099 | R98→R122→R100→R99 |
| Pilsen | R99 | Tunnel 2092 | R99→R119→R92 |
| Pilsen | R99 | Tunnel 2098 | R99→R100→R122→R98 |
Table 1. MPLS TE explicit VPLS pseudowire paths configuration for internal MetaCentrum traffic.
![[Image]](fig1.png)
Figure 1. MPLS TE explicit VPLS pseudowire paths configuration for internal MetaCentrum traffic.
Table 2 contains the configuration of the symmetric one-way MPLS TE tunnels for IPv4 MetaCentrum L3 traffic, which is also shown in Figure 2. All IPv4 internal MetaCentrum traffic is redirected to the appropriate TE tunnel selectively for all IPv4 destination MetaCentrum subnets by static routing configured on the head router.
| MetaCentrum | Router | MPLS TE tunnel | Explicit IPv4 path |
|---|---|---|---|
| CESNET Prague | R92 | Tunnel 1098 | R92→R119→R98 |
| CESNET Prague | R92 | Tunnel 1099 | R92→R119→R99 |
| CESNET Prague | R92 | Tunnel 1112 | R92→R107→R112 |
| UK Prague | R112 | Tunnel 1092 | R112→R107→R92 |
| UK Prague | R112 | Tunnel 1098 | R112→R119→R98 |
| UK Prague | R112 | Tunnel 1099 | R112→R119→R99 |
| Brno | R98 | Tunnel 1092 | R98→R119→R92 |
| Brno | R98 | Tunnel 1099 | R98→R122→R100→R99 |
| Brno | R98 | Tunnel 1112 | R98→R119→R112 |
| Pilsen | R99 | Tunnel 1092 | R99→R119→R92 |
| Pilsen | R99 | Tunnel 1098 | R99→R100→R122→R98 |
| Pilsen | R99 | Tunnel 1112 | R99→R119→R112 |
Table 2. MPLS TE explicit IPv4 paths configuration for internal MetaCentrum traffic.
![[Image]](fig2.png)
Figure 2. MPLS TE explicit IPv4 paths configuration for internal MetaCentrum traffic.
3 Fast Reroute
Fast Reroute (FRR) is a mechanism for protecting MPLS traffic engineering LSPs from link and node failure by locally repairing the LSPs at the point of failure. This protection allows data to continue to flow on them while their head-end routers attempt to establish end-to-end LSPs to replace them. FRR locally repairs the protected LSPs by rerouting them over backup tunnels that bypass failed links or nodes.
Backup tunnels that bypass only a single link of the LSP path provide link protection. They protect LSPs if a link along their path fails by rerouting the LSP traffic to the next hop (bypassing the failed link). These are referred to as next-hop (NHOP) backup tunnels because they terminate at the LSP next hop beyond the point of failure.
FRR can provide also node protection for LSPs. Backup tunnels that bypass next-hop nodes along LSP paths are called next-next-hop (NNHOP) backup tunnels because they terminate at the node following the next-hop node of the LSP paths, thereby bypassing the next-hop node. They protect LSPs if a node along their path fails by enabling the node upstream of the failure to reroute the LSPs and their traffic around the failed node to the next-next hop. FRR supports the use of RSVP Hellos (the state timer feature using special periodic packets to detect when a neighbor is down and to trigger faster state timeout) to accelerate the detection of node failures. NNHOP backup tunnels can also provide protection from link failures, because they bypass the failed link and the node.
Autotunnel backup is the ability of routers to create backup MPLS TE tunnels automatically. Therefore, there is no need to preconfigure each backup tunnel manually and then to assign the backup tunnel to the protected interface.
A set of links may form a Shared Risk Link Group (SRLG) if they share a common resource whose failure may affect all links in the set. If one link fails, other links in the group may fail too. A link may belong to multiple SRLGs. SRLG feature enhances backup tunnel path selection so that a backup tunnel avoids using links that are in the same SRLG as the interfaces which the backup tunnel is protecting.
In the case of CESNET2 network, a SRLG is typically a set of links represented by DWDM lambda paths within the same fiber. The current Cisco 7600 IOS version 12.2(33)SRE2 can avoid SRLGs of their protected interfaces only on automatically created backup tunnels (called autotunnel backup).
There are two ways for a backup tunnel to avoid the SRLGs of its protected interface:
-
The router does not create the backup tunnel unless it avoids SRLGs of the protected interface
mpls traffic-eng auto-tunnel backup srlg exclude force
-
The router tries to avoid SRLGs of the protected interface, but if that is not possible the router creates the backup tunnel anyway. In this case there are two explicit paths. The first explicit path tries to avoid the SRLGs of the protected interface. If that does not work, the backup tunnel uses the other path which ignores SRLGs. This is the current configuration of autotunnel backup in CESNET2.
mpls traffic-eng auto-tunnel backup srlg exclude preferred
Table 3 contains current SRLG definitions for MPLS backbone links using DWDM lambdas sharing the same fiber.
| Link | SRLG number |
|---|---|
| R99-R100 | 4099100 |
| R99-R119 | 4099119 |
| R99-R117 | 4099117 |
| R111-R117 | 4111117 |
| R100-R116 | 4100116 |
| R116-R122 | 4116122 |
| R100-R122 | 4100116, 4116122 |
| R100-R119 | 4099100, 4099119 |
| R99-R111 | 4099117, 4111117 |
Table 3. CESNET2 MPLS backbone links SRLG definitions.
The following example shows the MPLS TE FRR internal database of headend and midpoint protected tunnels on R99 and R100 respectively.
R99-PM#show mpls traffic-eng fast-reroute database
P2P Headend FRR information:
Protected tunnel In-label Out intf/label FRR intf/label Status
---------------- -------- -------------- ---------------- ------
Tunnel1092 Tun hd Te2/0/0:16075 Tu4002:implicit- Ready
Tunnel1098 Tun hd Te2/0/1:86 Tu4004:16112 Ready
Tunnel1112 Tun hd Te2/0/0:16099 Tu4001:implicit- Ready
Tunnel2092 Tun hd Te2/0/0:16061 Tu4002:implicit- Ready
Tunnel2098 Tun hd Te2/0/1:182 Tu4004:16113 Ready
P2P LSP midpoint frr information:
LSP identifier In-label Out intf/label FRR intf/label Status
-------------- -------- -------------- -------------- ------
R100-CB#show mpls traffic-eng fast-reroute database
P2P Headend FRR information:
Protected tunnel In-label Out intf/label FRR intf/label Status
------------------------- -------- -------------- -------------- ------
P2P LSP midpoint frr information:
LSP identifier In-label Out intf/label FRR intf/label Status
------------------------- -------- -------------- -------------- ------
XXX.XXX.XXX.13 1098 [208] 86 Te1/2:16112 Tu4001:implicit- Ready
XXX.XXX.XXX.13 2098 [208] 182 Te1/2:16113 Tu4001:implicit- Ready
XXX.XXX.XXX.26 1099 [200] 143 Te2/1:implicit-n Tu4002:implicit- Ready
XXX.XXX.XXX.26 2099 [200] 94 Te2/1:implicit-n Tu4002:implicit- Ready
The following example shows the MPLS TE FRR tunnel protection on R99 and R100 respectively.
R99-PM#show mpls traffic-eng tunnels protection
P2P TUNNELS:
TE IPv4: R99->R92 (METACentrum Plzen: R99->R119->R92: METACentr
LSP Head, Tunnel1092, Admin: up, Oper: up
Src XXX.XXX.XXX.13, Dest XXX.XXX.XXX.6, Instance 239
Fast Reroute Protection: Requested
Outbound: FRR Ready
Backup Tu4002 to LSP nnhop
Tu4002: out i/f: Te2/0/1, label: 183
LSP signalling info:
Original: out i/f: Te2/0/0, label: 16075, nhop: XXX.XXX.XXX.77
nnhop: XXX.XXX.XXX.6, nnhop rtr id: XXX.XXX.XXX.6
With FRR: out i/f: Tu4002, label: implicit-null
LSP bw: 0 kbps, Backup level: any-unlim, type: any pool
Path Protection: None
TE IPv4: R99->R98 (METACentrum Plzen: R99->R100->R122->R98: MET
LSP Head, Tunnel1098, Admin: up, Oper: up
Src XXX.XXX.XXX.13, Dest XXX.XXX.XXX.26, Instance 208
Fast Reroute Protection: Requested
Outbound: FRR Ready
Backup Tu4004 to LSP nnhop
Tu4004: out i/f: Te2/0/0, label: 16103
LSP signalling info:
Original: out i/f: Te2/0/1, label: 86, nhop: XXX.XXX.XXX.82
nnhop: XXX.XXX.XXX.25, nnhop rtr id: XXX.XXX.XXX.25
With FRR: out i/f: Tu4004, label: 16112
LSP bw: 0 kbps, Backup level: any-unlim, type: any pool
Path Protection: None
TE IPv4: R99->R112 (METACentrum Plzen: R99->R119->R112: METACen
LSP Head, Tunnel1112, Admin: up, Oper: up
Src XXX.XXX.XXX.13, Dest XXX.XXX.XXX.5, Instance 214
Fast Reroute Protection: Requested
Outbound: FRR Ready
Backup Tu4001 to LSP nnhop
Tu4001: out i/f: Te2/0/1, label: 117
LSP signalling info:
Original: out i/f: Te2/0/0, label: 16099, nhop: XXX.XXX.XXX.77
nnhop: XXX.XXX.XXX.5, nnhop rtr id: XXX.XXX.XXX.5
With FRR: out i/f: Tu4001, label: implicit-null
LSP bw: 0 kbps, Backup level: any-unlim, type: any pool
Path Protection: None
TE VPLS: R99->R92 (METACentrum Plzen: R99->R119->R92: METACentr
LSP Head, Tunnel2092, Admin: up, Oper: up
Src XXX.XXX.XXX.13, Dest XXX.XXX.XXX.6, Instance 237
Fast Reroute Protection: Requested
Outbound: FRR Ready
Backup Tu4002 to LSP nnhop
Tu4002: out i/f: Te2/0/1, label: 183
LSP signalling info:
Original: out i/f: Te2/0/0, label: 16061, nhop: XXX.XXX.XXX.77
nnhop: XXX.XXX.XXX.6, nnhop rtr id: XXX.XXX.XXX.6
With FRR: out i/f: Tu4002, label: implicit-null
LSP bw: 0 kbps, Backup level: any-unlim, type: any pool
Path Protection: None
TE VPLS: R99->R98 (METACentrum Plzen: R99->R100->R122->R98: MET
LSP Head, Tunnel2098, Admin: up, Oper: up
Src XXX.XXX.XXX.13, Dest XXX.XXX.XXX.26, Instance 208
Fast Reroute Protection: Requested
Outbound: FRR Ready
Backup Tu4004 to LSP nnhop
Tu4004: out i/f: Te2/0/0, label: 16103
LSP signalling info:
Original: out i/f: Te2/0/1, label: 182, nhop: XXX.XXX.XXX.82
nnhop: XXX.XXX.XXX.25, nnhop rtr id: XXX.XXX.XXX.25
With FRR: out i/f: Tu4004, label: 16113
LSP bw: 0 kbps, Backup level: any-unlim, type: any pool
Path Protection: None
R99-PM_t4001
LSP Head, Tunnel4001, Admin: up, Oper: up
Src XXX.XXX.XXX.13, Dest XXX.XXX.XXX.5, Instance 59
Fast Reroute Protection: None
Path Protection: None
R99-PM_t4002
LSP Head, Tunnel4002, Admin: up, Oper: up
Src XXX.XXX.XXX.13, Dest XXX.XXX.XXX.6, Instance 59
Fast Reroute Protection: None
Path Protection: None
R99-PM_t4004
LSP Head, Tunnel4004, Admin: up, Oper: up
Src XXX.XXX.XXX.13, Dest XXX.XXX.XXX.25, Instance 61
Fast Reroute Protection: None
Path Protection: None
R100-CB#show mpls traffic-eng tunnels protection
P2P TUNNELS:
R100-CB_t4001
LSP Head, Tunnel4001, Admin: up, Oper: up
Src XXX.XXX.XXX.15, Dest XXX.XXX.XXX.26, Instance 1
Fast Reroute Protection: None
Path Protection: None
R100-CB_t4002
LSP Head, Tunnel4002, Admin: up, Oper: up
Src XXX.XXX.XXX.15, Dest XXX.XXX.XXX.13, Instance 57
Fast Reroute Protection: None
Path Protection: None
4 Conclusion
After designing and implementing MPLS Traffic Engineering (TE) for internal MetaCentrum traffic in 2009, we have pursued the Fast Reroute (FRR) link and node protection in the CESNET2 backbone to ensure high availability. MPLS-TE primary tunnels are defined by explicit path specifications to use otherwise underutilized but available network bandwidth. There are two sets of MPLS-TE primary tunnels: the first one for L2 VPLS traffic optimization among three MetaCentrum data centers (Prague, Brno and Pilsen) and the other one for L3 IPv4 traffic optimization among four MetaCentrum data centers (CESNET Prague, UK Prague, Brno and Pilsen). High availability of these MPLS-TE tunnels is ensured by automatically created next-hop and next-next-hop backup tunnels to be used by the Fast Reroute mechanism for link and node protection in tens of milliseconds with respect to Shared Risk Link Group (SRLG) dependencies.
Backup tunnels are built automatically to enable high availability using Fast Reroute for internal MetaCentrum traffic using MPLS TE primary tunnels in a very easy and flexible way in CESNET2. This eliminates the need to manually preconfigure each backup tunnel and then assign it to the protected interface statically. Backup autotunnels thus enable a MPLS TE router to dynamically build backup tunnels only when they are needed.
At the time of writing this paper, FRR using backup autotunnels could not be implemented on CRS-1 core MPLS routers, because this features is not supported in currently used IOS-XR version 3.8.1. This restriction does not prevent MPLS TE backup autotunnels from being successfully recovered on a midpoint router along the LSP path in case of failure. We plan to extend the backup autotunnels configuration on CRS-1 core MPLS routers after upgrading to new IOS-XR v4 to spread Fast Reroute throughout the whole MPLS backbone.
References
| [1] | CISCO SYSTEMS. Cross-Platform Release Notes for Cisco IOS Release12.2SR. 2010, [cit. 2010-11-22]. Available online. |
| [2] | CISCO SYSTEMS. MPLS Traffic Engineering (TE): Fast Reroute (FRR) Link and Node Protection. 2006, [cit. 2010-11-22]. Available online. |
| [3] | CISCO SYSTEMS. MPLS Traffic Engineering: Shared Risk Link Groups (SRLG). 2007, [cit. 2010-11-22]. Available online. |
Appendix A Appendix: MetaCentrum MPLS TE/FRR configuration template
!
! CESNET2 MPLS all routers
!
mpls traffic-eng tunnels
!mpls traffic-eng reoptimize events link-up
!mpls traffic-eng reoptimize timers delay cleanup 10
!mpls traffic-eng reoptimize timers delay installation 10
!mpls traffic-eng reoptimize timers frequency 300
mpls traffic-eng tunnels
mpls traffic-eng auto-tunnel backup
mpls traffic-eng auto-tunnel backup config unnumbered-interface Loopback0
mpls traffic-eng auto-tunnel backup tunnel-num min 4000 max 4999
mpls traffic-eng auto-tunnel backup srlg exclude preferred
router ospf 200
mpls traffic-eng area 0
mpls traffic-eng router-id loopback 0
mpls traffic-eng multicast-intact
! MPLS interface template
! sh mpls interfaces
interface Te2/0/0
mpls traffic-eng tunnels
! only for non VPLS/non ES enabled MPLS links terminated/originated on/from r92, r98 and r99!!!
!mpls traffic-eng attribute-flags 0x1
! only for SRLG links
!mpls traffic-eng srlg 4099119
-----------------------------------------------------------------------
!
! L2 VPLS
!
mpls traffic-eng lsp attributes VPLS-METACentrum
affinity 0x0 mask 0x1
priority 1 1
! bandwidth 100000
! protection fast-reroute
ip explicit-path name r119 enable
next-address XXX.XXX.XXX.17
ip explicit-path name r107-r119 enable
next-address XXX.XXX.XXX.1
next-address XXX.XXX.XXX.17
ip explicit-path name r119-r107 enable
next-address XXX.XXX.XXX.17
next-address XXX.XXX.XXX.1
ip explicit-path name r122-r100 enable
next-address XXX.XXX.XXX.25
next-address XXX.XXX.XXX.15
ip explicit-path name r100-r122 enable
next-address XXX.XXX.XXX.15
next-address XXX.XXX.XXX.25
!
! R92 VPLS
!
vlan 702
name CESNET-METACentrum-VPLS
interface Vlan702
no shut
mtu 9216
no ip address
load-interval 30
xconnect vfi CESNET-METACentrum
pseudowire-class pw-r99
encapsulation mpls
preferred-path interface Tunnel2099
pseudowire-class pw-r98
encapsulation mpls
preferred-path interface Tunnel2098
l2 vfi CESNET-METACentrum manual
vpn id 702
neighbor XXX.XXX.XXX.13 pw-class pw-r99
neighbor XXX.XXX.XXX.26 pw-class pw-r98
! R92: R92-R119-R99 (Praha-Plzeň přes P Praha)
interface Tunnel2099
description TE VPLS: R92->R99 (METACentrum CESNET Praha: R92->R119->R99: METACentrum Plzen)
ip unnumbered Loopback0
tunnel destination XXX.XXX.XXX.13
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name r119 attributes VPLS-METACentrum
tunnel mpls traffic-eng path-option 20 dynamic attributes VPLS-METACentrum
tunnel mpls traffic-eng fast-reroute
! R92: R92-R107-R119-R98 (Praha-Brno přes P Praha a PE Brno)
interface Tunnel2098
description TE VPLS: R92->R98 (METACentrum CESNET Praha: R92->R107->R119->R98: METACentrum Brno)
ip unnumbered Loopback0
tunnel destination XXX.XXX.XXX.26
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name r107-r119 attributes VPLS-METACentrum
tunnel mpls traffic-eng path-option 20 dynamic attributes VPLS-METACentrum
tunnel mpls traffic-eng fast-reroute
interface TenGigabitEthernet3/3
description VPLS services for METACentrum - Force10 S2410 - ethernet 0/3
switchport
switchport access vlan 702
switchport trunk encapsulation dot1q
switchport mode dot1q-tunnel
dampening
mtu 9216
load-interval 30
udld port disable
l2protocol-tunnel drop-threshold stp 50
l2protocol-tunnel cdp
l2protocol-tunnel stp
l2protocol-tunnel vtp
no cdp enable
spanning-tree portfast
spanning-tree bpdufilter enable
!
! R98 VPLS
!
vlan 702
name CESNET-METACentrum-VPLS
interface Vlan702
no shut
mtu 9216
no ip address
load-interval 30
xconnect vfi CESNET-METACentrum
pseudowire-class pw-r99
encapsulation mpls
preferred-path interface Tunnel2099
pseudowire-class pw-r92
encapsulation mpls
preferred-path interface Tunnel2092
l2 vfi CESNET-METACentrum manual
vpn id 702
neighbor XXX.XXX.XXX.13 pw-class pw-r99
neighbor XXX.XXX.XXX.6 pw-class pw-r92
! R98: R98-R119-R107-R92 (Brno-Praha přes PE Brno a P Praha)
interface Tunnel2092
description TE VPLS: R98->R92 (METACentrum Brno: R98->R119->R107->R92: METACentrum CESNET Praha)
ip unnumbered Loopback0
tunnel destination XXX.XXX.XXX.6
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name r119-r107 attributes VPLS-METACentrum
tunnel mpls traffic-eng path-option 20 dynamic attributes VPLS-METACentrum
tunnel mpls traffic-eng fast-reroute
! R98: R98-R122-R100-R99 (Brno-Plzeň přes P Brno a P České Budějovice)
interface Tunnel2099
description TE VPLS: R98->R99 (METACentrum Brno: R98->R122->R100->R99: METACentrum Plzen)
ip unnumbered Loopback0
tunnel destination XXX.XXX.XXX.13
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name r122-r100 attributes VPLS-METACentrum
tunnel mpls traffic-eng path-option 20 dynamic attributes VPLS-METACentrum
tunnel mpls traffic-eng fast-reroute
interface TenGigabitEthernet2/2
description VPLS services for METACentrum
switchport
switchport access vlan 702
switchport trunk encapsulation dot1q
switchport mode dot1q-tunnel
dampening
mtu 9216
logging event link-status
logging event status
load-interval 30
mls qos statistics-export
mls qos vlan-based
l2protocol-tunnel drop-threshold stp 50
l2protocol-tunnel cdp
l2protocol-tunnel stp
l2protocol-tunnel vtp
no cdp enable
spanning-tree portfast
spanning-tree bpdufilter enable
!
! R99 VPLS
!
vlan 702
name CESNET-METACentrum-VPLS
interface Vlan702
no shut
mtu 9216
no ip address
load-interval 30
xconnect vfi CESNET-METACentrum
pseudowire-class pw-r98
encapsulation mpls
preferred-path interface Tunnel2098
pseudowire-class pw-r92
encapsulation mpls
preferred-path interface Tunnel2092
l2 vfi CESNET-METACentrum manual
vpn id 702
neighbor XXX.XXX.XXX.26 pw-class pw-r98
neighbor XXX.XXX.XXX.6 pw-class pw-r92
! R99: R99-R119-R92 (Plzeň-Praha přes P Praha)
interface Tunnel2092
description TE VPLS: R99->R92 (METACentrum Plzen: R99->R119->R92: METACentrum CESNET Praha)
ip unnumbered Loopback0
tunnel destination XXX.XXX.XXX.6
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name r119 attributes VPLS-METACentrum
tunnel mpls traffic-eng path-option 20 dynamic attributes VPLS-METACentrum
tunnel mpls traffic-eng fast-reroute
! R99: R99-R100-R122-R98 (Plzeň-Brno přes P České Budějovice a P Brno)
interface Tunnel2098
description TE VPLS: R99->R98 (METACentrum Plzen: R99->R100->R122->R98: METACentrum Brno)
ip unnumbered Loopback0
tunnel destination XXX.XXX.XXX.26
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name r100-r122 attributes VPLS-METACentrum
tunnel mpls traffic-eng path-option 20 dynamic attributes VPLS-METACentrum
tunnel mpls traffic-eng fast-reroute
interface TenGigabitEthernet1/3
description VPLS for METACentrum
switchport
switchport access vlan 702
switchport trunk encapsulation dot1q
switchport mode dot1q-tunnel
dampening
mtu 9216
load-interval 30
mls qos trust dscp
l2protocol-tunnel drop-threshold stp 50
l2protocol-tunnel cdp
l2protocol-tunnel stp
l2protocol-tunnel vtp
no cdp enable
spanning-tree portfast
spanning-tree bpdufilter enable
service-policy input CESNET2-IP2MPLS-CE2PE-10GE-in
-----------------------------------------------------------------------------
!
! L3 IP
!
mpls traffic-eng lsp attributes IPv4-METACentrum
priority 3 3
! bandwidth 800000
! protection fast-reroute
ip explicit-path name r107 enable
next-address XXX.XXX.XXX.1
!
! R92 IP
!
! To Plzen
ip route XXX.XXX.43.0 255.255.255.0 tunnel 1099
ip route XXX.XXX.240.0 255.255.255.0 tunnel 1099
ip route XXX.XXX.67.32 255.255.255.224 tunnel 1099
ip route XXX.XXX.52.26 255.255.255.255 tunnel 1099
ip route XXX.XXX.52.210 255.255.255.255 tunnel 1099
! To Brno
ip route XXX.XXX.3.0 255.255.255.0 tunnel 1098
ip route XXX.XXX.9.0 255.255.255.0 tunnel 1098
ip route XXX.XXX.11.0 255.255.255.128 tunnel 1098
ip route XXX.XXX.72.128 255.255.255.192 tunnel 1098
! To UK Praha
ip route XXX.XXX.0.32 255.255.255.224 tunnel 1112
! R92: R92-R119-R99 (CESNET Praha-Plzeň přes P Praha)
interface Tunnel1099
description TE IPv4: R92->R99 (METACentrum CESNET Praha: R92->R119->R99: METACentrum Plzen)
ip unnumbered Loopback0
tunnel destination XXX.XXX.XXX.13
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name r119 attributes IPv4-METACentrum
tunnel mpls traffic-eng path-option 20 dynamic attributes IPv4-METACentrum
tunnel mpls traffic-eng fast-reroute
! R92: R92-R119-R98 (CESNET Praha-Brno přes P Praha a PE Brno)
interface Tunnel1098
description TE IPv4: R92->R98 (METACentrum CESNET Praha: R92->R119->R98: METACentrum Brno)
ip unnumbered Loopback0
tunnel destination XXX.XXX.XXX.26
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name r119 attributes IPv4-METACentrum
tunnel mpls traffic-eng path-option 20 dynamic attributes IPv4-METACentrum
tunnel mpls traffic-eng fast-reroute
! R92: R92-R107-R112 (CESNET Praha-UK Praha přes PE Praha)
interface Tunnel1112
description TE IPv4: R92->R112 (METACentrum CESNET Praha: R92->R107->R112: METACentrum UK Praha)
ip unnumbered Loopback0
tunnel destination XXX.XXX.XXX.5
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name r107 attributes IPv4-METACentrum
tunnel mpls traffic-eng path-option 20 dynamic attributes IPv4-METACentrum
tunnel mpls traffic-eng fast-reroute
!
! R112 IP
!
! To Plzen
ip route XXX.XXX.43.0 255.255.255.0 tunnel 1099
ip route XXX.XXX.240.0 255.255.255.0 tunnel 1099
ip route XXX.XXX.67.32 255.255.255.224 tunnel 1099
ip route XXX.XXX.52.26 255.255.255.255 tunnel 1099
ip route XXX.XXX.52.210 255.255.255.255 tunnel 1099
! To Brno
ip route XXX.XXX.3.0 255.255.255.0 tunnel 1098
ip route XXX.XXX.9.0 255.255.255.0 tunnel 1098
ip route XXX.XXX.11.0 255.255.255.128 tunnel 1098
ip route XXX.XXX.72.128 255.255.255.192 tunnel 1098
! To CESNET Praha
ip route XXX.XXX.219.0 255.255.255.128 tunnel 1092
! R112: R112-R119-R99 (CESNET Praha-Plzeň přes P Praha)
interface Tunnel1099
description TE IPv4: R112->R99 (METACentrum UK Praha: R112->R119->R99: METACentrum Plzen)
ip unnumbered Loopback0
tunnel destination XXX.XXX.XXX.13
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name r119 attributes IPv4-METACentrum
tunnel mpls traffic-eng path-option 20 dynamic attributes IPv4-METACentrum
tunnel mpls traffic-eng fast-reroute
! R112: R112-R119-R98 (CESNET Praha-Brno přes P Praha)
interface Tunnel1098
description TE IPv4: R112->R98 (METACentrum UK Praha: R112->R119->R98: METACentrum Brno)
ip unnumbered Loopback0
tunnel destination XXX.XXX.XXX.26
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name r119 attributes IPv4-METACentrum
tunnel mpls traffic-eng path-option 20 dynamic attributes IPv4-METACentrum
tunnel mpls traffic-eng fast-reroute
! R112: R112-R107-R92 (UK Praha-CESNET Praha přes PE Praha)
interface Tunnel1092
description TE IPv4: R112->R92 (METACentrum UK Praha: R112->R107->R92: METACentrum CESNET Praha)
ip unnumbered Loopback0
tunnel destination XXX.XXX.XXX.6
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name r107 attributes IPv4-METACentrum
tunnel mpls traffic-eng path-option 20 dynamic attributes IPv4-METACentrum
tunnel mpls traffic-eng fast-reroute
!
! R98 IP
!
! To CESNET Praha
ip route XXX.XXX.219.0 255.255.255.128 tunnel 1092
! To UK Praha
ip route XXX.XXX.0.32 255.255.255.224 tunnel 1112
! To Plzen
ip route XXX.XXX.43.0 255.255.255.0 tunnel 1099
ip route XXX.XXX.240.0 255.255.255.0 tunnel 1099
ip route XXX.XXX.67.32 255.255.255.224 tunnel 1099
ip route XXX.XXX.52.26 255.255.255.255 tunnel 1099
ip route XXX.XXX.52.210 255.255.255.255 tunnel 1099
! R98: R98-R119-R92 (Brno-CESNET Praha přes PE Brno a P Praha)
interface Tunnel1092
description TE IPv4: R98->R92 (METACentrum Brno: R98->R119->R92: METACentrum CESNET Praha)
ip unnumbered Loopback0
tunnel destination XXX.XXX.XXX.6
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name r119 attributes IPv4-METACentrum
tunnel mpls traffic-eng path-option 20 dynamic attributes IPv4-METACentrum
tunnel mpls traffic-eng fast-reroute
! R98: R98-R122-R100-R99 (Brno-Plzeň přes P Brno a P České Budějovice)
interface Tunnel1099
description TE IPv4: R98->R99 (METACentrum Brno: R98->R122->R100->R99: METACentrum Plzen)
ip unnumbered Loopback0
tunnel destination XXX.XXX.XXX.13
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name r122-r100 attributes IPv4-METACentrum
tunnel mpls traffic-eng path-option 20 dynamic attributes IPv4-METACentrum
tunnel mpls traffic-eng fast-reroute
! R98: R98-R119-R112 (Brno-UK Praha přes PE Brno a P Praha)
interface Tunnel1112
description TE IPv4: R98->R112 (METACentrum Brno: R98->R119->R112: METACentrum UK Praha)
ip unnumbered Loopback0
tunnel destination XXX.XXX.XXX.5
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name r119 attributes IPv4-METACentrum
tunnel mpls traffic-eng path-option 20 dynamic attributes IPv4-METACentrum
tunnel mpls traffic-eng fast-reroute
!
! R99 IP
!
! To CESNET Praha
ip route XXX.XXX.219.0 255.255.255.128 tunnel 1092
! To UK Praha
ip route XXX.XXX.0.32 255.255.255.224 tunnel 1112
! To Brno
ip route XXX.XXX.3.0 255.255.255.0 tunnel 1098
ip route XXX.XXX.9.0 255.255.255.0 tunnel 1098
ip route XXX.XXX.11.0 255.255.255.128 tunnel 1098
ip route XXX.XXX.72.128 255.255.255.192 tunnel 1098
! R99: R99-R119-R92 (Plzeň-CESNET Praha přes P Praha)
interface Tunnel1092
description TE IPv4: R99->R92 (METACentrum Plzen: R99->R119->R92: METACentrum CESNET Praha)
ip unnumbered Loopback0
tunnel destination XXX.XXX.XXX.6
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name r119 attributes IPv4-METACentrum
tunnel mpls traffic-eng path-option 20 dynamic attributes IPv4-METACentrum
tunnel mpls traffic-eng fast-reroute
! R99: R99-R119-R112 (Plzeň-UK Praha přes P Praha)
interface Tunnel1112
description TE IPv4: R99->R112 (METACentrum Plzen: R99->R119->R112: METACentrum UK Praha)
ip unnumbered Loopback0
tunnel destination XXX.XXX.XXX.5
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name r119 attributes IPv4-METACentrum
tunnel mpls traffic-eng path-option 20 dynamic attributes IPv4-METACentrum
tunnel mpls traffic-eng fast-reroute
! R99: R99-R100-R122-R98 (Plzeň-Brno přes P České Budějovice a P Brno)
interface Tunnel1098
description TE IPv4: R99->R98 (METACentrum Plzen: R99->R100->R122->R98: METACentrum Brno)
ip unnumbered Loopback0
tunnel destination XXX.XXX.XXX.26
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng path-option 10 explicit name r100-r122 attributes IPv4-METACentrum
tunnel mpls traffic-eng path-option 20 dynamic attributes IPv4-METACentrum
tunnel mpls traffic-eng fast-reroute
-----------------------------------------------------------------------------
!
! CRS-1
!
router ospf 200
mpls traffic-eng router-id loopback 0
area 0
mpls traffic-eng
!
! R122
!
mpls traffic-eng
interface POS0/8/0/0
!
interface TenGigE0/9/0/0
!
interface TenGigE0/9/0/1
!
interface TenGigE0/9/0/2
!
interface TenGigE0/9/0/3
!
interface TenGigE0/14/1/0
!
interface TenGigE0/14/2/0
!
interface TenGigE0/14/3/0
!
interface TenGigE0/15/0/0
!
interface TenGigE0/15/0/1
!
interface TenGigE0/15/0/2
!
interface TenGigE0/15/0/3
!
interface GigabitEthernet0/14/4/0
!
!
! R119
!
mpls traffic-eng
interface POS0/8/0/0
!
interface TenGigE0/9/0/0
!
interface TenGigE0/9/0/1
!
interface TenGigE0/9/0/2
!
interface TenGigE0/9/0/3
!
interface TenGigE0/10/1/0
!
interface TenGigE0/10/2/0
!
interface TenGigE0/10/3/0
!
interface TenGigE0/10/4/0
!
interface TenGigE0/13/0/0
!
interface TenGigE0/13/3/0
!
interface TenGigE0/14/1/0
!
interface TenGigE0/14/2/0
!
interface TenGigE0/14/3/0
!
interface TenGigE0/14/4/0
!
interface TenGigE0/15/0/0
!
interface TenGigE0/15/0/1
!
interface TenGigE0/15/0/2
!
interface TenGigE0/15/0/3
!
interface GigabitEthernet0/13/1/0
!
interface GigabitEthernet0/13/1/2
!
interface GigabitEthernet0/13/1/7
!
!RP/0/RP0/CPU0:R122(config)#mpls traffic-eng interface Te0/14/1/0
!RP/0/RP0/CPU0:R122(config-mpls-te-if)#attribute-flags 0x1