Date created: Tuesday, November 17, 2015 9:03:19 AM. Last modified: Friday, April 6, 2018 5:14:59 PM
Explicit Path for Pseudowires (IOS-XR)
Example of how to define two explicit paths for a pseudowire between two PE nodes in IOS-XR. In this example two explicit paths are defined as primary and secondary:
mpls traffic-eng reoptimize 300 mpls traffic-eng optimize timers delay installation 300 explicit-path name PE1-PE2-Clockwise index 1 next-address strict ipv4 unicast 10.0.1.2 index 2 next-address strict ipv4 unicast 10.0.1.6 index 3 next-address strict ipv4 unicast 10.0.1.10 index 4 next-address strict ipv4 unicast 10.0.1.14 index 5 next-address strict ipv4 unicast 10.0.0.2 explicit-path name PE1-PE2-Anti-Clockwise index 1 next-address strict ipv4 unicast 10.0.2.2 index 2 next-address strict ipv4 unicast 10.0.2.6 index 3 next-address strict ipv4 unicast 10.0.2.10 index 4 next-address strict ipv4 unicast 10.0.2.14 index 5 next-address strict ipv4 unicast 10.0.0.2 interface tunnel-te100 ipv4 unnumbered Loopback0 signalled-name te1-Static-L2-LSP logging events lsp-status state logging events lsp-status reroute logging events lsp-status switchover logging events lsp-status insufficient-bandwidth priority 1 1 signalled-bandwidth 100000 destination 10.0.0.2 record-route path-option 1 explicit name PE1-PE2-Clockwiselockdown path-option 2 explicit name PE1-PE2-Anti-Clockwiselockdown l2vpn autodiscovery bgp signaling-protocol bgp mtu mismatch ignore ! ! pw-class PWE3-Fixed-TE-LSP encapsulation mpls protocol ldp preferred-path interface tunnel-te 100 ! ! xconnect group blah p2p 123 interface TenGigE0/0/0/0 neighbor ipv4 10.0.0.2 pw-id 123 pw-class PWE3-Fixed-TE-LSP ! ! !
Previous page: Explicit Path for VRF (IOS)
Next page: Explicit Path for Pseudowires (IOS)