Every interface in the path that is required to pass the TE tunnel needs to have the mpls traffic-eng tunnels configured.. PE1-RACK1config#int fastEthernet 0/0 PE1-RACK1config-if#mpls t
Trang 1Before starting this task, make sure MPLS is disabled on all physical interfaces between PE1, PE2, and PE3 MPLS labels should depend
on MPLS traffic engineering tunnels
♦ Task 17.1:
The mpls traffic-eng tunnels is a global command It will allow
activating MPLS Traffic-Eng commands Without activating globally you won’t be able to configure any traffic engineering parameters
PE1-RACK1(config)#mpls traffic-eng tunnels
PE2-RACK1(config)#mpls traffic-eng tunnels
PE3-RACK1(config)#mpls traffic-eng tunnels
PE4-RACK1(config)#mpls traffic-eng tunnels
ASBR1-RACK1(config)#mpls traffic-eng tunnels
RR1-RACK1(config)#mpls traffic-eng tunnels
♦ Enable Traffic Engineering on each interface where possible
Similar command will activate MPLS traffic engineering per interface Every interface in the path that is required to pass the TE
tunnel needs to have the mpls traffic-eng tunnels configured
Otherwise, TE won’t pass any traffic from end to end
PE1-RACK1(config)#int fastEthernet 0/0 PE1-RACK1(config-if)#mpls traffic-eng tunnels PE1-RACK1(config-if)#int fastEthernet 0/1 PE1-RACK1(config-if)#mpls traffic-eng tunnels
PE2-RACK1(config)#int e 0/0.20 PE2-RACK1(config-subif)#mpls traffic-eng tunnels PE2-RACK1(config-subif)#int e 0/0.21
PE2-RACK1(config-subif)#mpls traffic-eng tunnels PE2-RACK1(config-subif)#int e 0/0.123
PE2-RACK1(config-subif)#mpls traffic-eng tunnels
PE3-RACK1(config)#int e 0/0.30 PE3-RACK1(config-subif)#mpls traffic-eng tunnels PE3-RACK1(config-subif)#int e0/0.31
PE3-RACK1(config-subif)#mpls traffic-eng tunnels
Trang 2PE3-RACK1(config-subif)#int e0/0.123 PE3-RACK1(config-subif)#mpls traffic-eng tunnels
RR1-RACK1(config-subif)#int e 0/0.20 RR1-RACK1(config-subif)#mpls traffic-eng tunnels RR1-RACK1(config-subif)#int e 0/0.30
RR1-RACK1(config-subif)#mpls traffic-eng tunnels
♦ Configure reserved bandwidth on all serial interfaces to 1158K
Traffic engineering is depending on RSVP to pass TE labels end to end Similar to MPLS, we use IGP to pass labels end to end In Traffic Engineering configuration, TE depends on RSVP to pass the
TE labels, so RSVP is required to run for each interface in data path
forwarding of TE ip-rsvp bandwidth is used to specify allocated
bandwidth that you reserved for TE over specific interface
PE1-RACK1(config)#int ser 0/0.101 PE1-RACK1(config-subif)#ip rsvp bandwidth 1158 PE1-RACK1(config-subif)#mpls traffic-eng tunnels
PE1-RACK1#sho ip rsvp interface serial 0/0.101 interface allocated i/f max flow max sub max Se0/0.101 0 1158K 1158K 0
♦ Configure reserved bandwidth on all FastEthernet links to 75M kbps
interface FastEthernet0/0 description to PE3 VLAN31
ip address 172.16.13.1 255.255.255.0
ip rsvp bandwidth 75000
! interface FastEthernet0/1 description to PE2 VLAN21
ip address 172.16.12.1 255.255.255.0
ip rsvp bandwidth
PE1-RACK1#sho ip rsvp interface fastEthernet 0/0 interface allocated i/f max flow max sub max Fa0/0 0 75M 75M 0
♦ Configure reserved bandwidth on all Ethernet interfaces to 7500K without specifying optional commands in the RSVP mode
This task does not require the bandwidth to be specified because the default behavior of 10MB is set to 7500K
Trang 3PE2-RACK1(config)#interface Ethernet0/0.20 PE2-RACK1(config-subif)# description to RR - VLAN 20 PE2-RACK1(config-subif)# encapsulation dot1Q 20 PE2-RACK1(config-subif)# ip address 172.16.20.2 255.255.255.0 PE2-RACK1(config-subif)# ip rsvp bandwidth
PE2-RACK1(config-subif)#interface Ethernet0/0.21 PE2-RACK1(config-subif)# description to PE1 - VLAN 21 PE2-RACK1(config-subif)# encapsulation dot1Q 21 PE2-RACK1(config-subif)# ip address 172.16.12.2 255.255.255.0 PE2-RACK1(config-subif)# ip rsvp bandwidth
PE2-RACK1(config-subif)#interface Ethernet0/0.123 PE2-RACK1(config-subif)# description to PE3 - VLAN 123 PE2-RACK1(config-subif)# encapsulation dot1Q 123 PE2-RACK1(config-subif)# ip address 172.16.123.2 255.255.255.0 PE2-RACK1(config-subif)# ip rsvp bandwidth
PE2-RACK1#sho ip rsvp interface interface allocated i/f max flow max sub max Et0/0.20 0 7500K 7500K 0 Et0/0.21 0 7500K 7500K 0 Et0/0.123 0 7500K 7500K 0
♦ Configure IS-IS as the routing protocol for Traffic Engineering support
This task is very important for TE to work TE is depending on IGP
to build the routing topology and pass this routing topology to the
TE database Today TE is only supported by OSPF and IS-IS
In IS-IS it is required to run metric-style wide This is a new
format for ISIS to support new features like TE, for example As soon as you apply the TE commands in IS-IS, TE and RSVP will try
to send this RSVP topology down to IS-IS
PE1-RACK1(config-router)# net 48.0000.0001.0001.00 PE1-RACK1(config-router)# metric-style wide
PE1-RACK1(config-router)# log-adjacency-changes all PE1-RACK1(config-router)# mpls traffic-eng router-id Loopback0 PE1-RACK1(config-router)# mpls traffic-eng level-1
PE1-RACK1(config-router)# passive-interface Loopback0
PE2-RACK1(config-router)# net 48.0000.0002.0002.00 PE2-RACK1(config-router)# metric-style wide
PE2-RACK1(config-router)# log-adjacency-changes all PE2-RACK1(config-router)# mpls traffic-eng router-id Loopback0 PE2-RACK1(config-router)# mpls traffic-eng level-1
PE2-RACK1(config-router)# passive-interface Loopback0
PE3-RACK1(config-router)# net 48.0000.0003.0003.00
Trang 4PE3-RACK1(config-router)# metric-style wide PE3-RACK1(config-router)# log-adjacency-changes all PE3-RACK1(config-router)# mpls traffic-eng router-id Loopback0 PE3-RACK1(config-router)# mpls traffic-eng level-1
PE3-RACK1(config-router)# passive-interface Loopback0
RR1-RACK1(config-router)# net 48.0000.0254.0254.00 RR1-RACK1(config-router)# metric-style wide
RR1-RACK1(config-router)# log-adjacency-changes all RR1-RACK1(config-router)# mpls traffic-eng router-id Loopback0 RR1-RACK1(config-router)# mpls traffic-eng level-1
RR1-RACK1(config-router)# passive-interface Loopback0
PE2-RACK1#sho isis mpls traffic-eng advertisements System ID: PE2-RACK1.00
Router ID: 10.1.1.2 Link Count: 2 Link[1]
Neighbor System ID: RR1-RACK1.01 (broadcast link) Interface IP address: 172.16.20.2
Neighbor IP Address: 0.0.0.0 Admin Weight te: 10 igp: 10 Physical BW: 10000 kbits/sec Reservable Global Pool BW: 7500 kbits/sec Reservable Sub Pool BW: 0 kbits/sec Global Pool BW unreserved:
[0]: 7500 kbits/sec, [1]: 7500 kbits/sec [2]: 7500 kbits/sec, [3]: 7500 kbits/sec [4]: 7500 kbits/sec, [5]: 7500 kbits/sec [6]: 7500 kbits/sec, [7]: 7500 kbits/sec Sub Pool BW unreserved:
[0]: 7500 kbits/sec, [1]: 7500 kbits/sec [2]: 7500 kbits/sec, [3]: 7500 kbits/sec [4]: 7500 kbits/sec, [5]: 7500 kbits/sec [6]: 7500 kbits/sec, [7]: 7500 kbits/sec Affinity Bits: 0x00000000
Link[2]
Neighbor System ID: PE1-RACK1.00 (P2P link) Interface IP address: 172.16.12.2
Neighbor IP Address: 172.16.12.1 Admin Weight te: 10 igp: 10 Physical BW: 10000 kbits/sec Reservable Global Pool BW: 7500 kbits/sec Reservable Sub Pool BW: 0 kbits/sec Global Pool BW unreserved:
[0]: 7500 kbits/sec, [1]: 7500 kbits/sec [2]: 7500 kbits/sec, [3]: 7500 kbits/sec [4]: 7500 kbits/sec, [5]: 7500 kbits/sec [6]: 7500 kbits/sec, [7]: 7500 kbits/sec Sub Pool BW unreserved:
[0]: 7500 kbits/sec, [1]: 7500 kbits/sec [2]: 7500 kbits/sec, [3]: 7500 kbits/sec [4]: 7500 kbits/sec, [5]: 7500 kbits/sec [6]: 7500 kbits/sec, [7]: 7500 kbits/sec
Trang 5Affinity Bits: 0x00000000
PE2-RACK1#sho mpls traffic-eng link-management igp-neighbors Link ID:: Tu101
Link ID:: Et0/0.20 Neighbor ID: 0000.0254.0254.01 (area: isis level-1, IP: 0.0.0.0) Link ID:: Et0/0.21
Neighbor ID: 0000.0001.0001.00 (area: isis level-1, IP: 172.16.12.1) Link ID:: Et0/0.123
Task 17.2: Configure Tail End and Head End for TE:
♦ CORRECTIONS!!! Configure dynamic tunnel 101 from PE2 to PE3
There are multiple ways in which TE can be configured to select a path In our case, we want to use a path based on IGP instead of
TE Dynamic options allow TE to figure out the best path to tail end
and head end on each side You need to enable traffic-eng
tunnels per interface and specify each tunnel point
As you can see, under path-options you have the ability to assign a number which can be used only in case of failure to switch to the manual path (which we will cover in Lab 18)
PE2-RACK1(config-if)#interface Tunnel101 PE2-RACK1(config-if)# description to PE3 PE2-RACK1(config-if)# ip unnumbered Loopback0 PE2-RACK1(config-if)# mpls traffic-eng tunnels PE2-RACK1(config-if)# tunnel destination 10.1.1.3 PE2-RACK1(config-if)# tunnel mode mpls traffic-eng PE2-RACK1(config-if)# tunnel mpls traffic-eng path-option 1 dynamic
PE3-RACK1(config-if)#interface Tunnel101 PE3-RACK1(config-if)# description to PE2 PE3-RACK1(config-if)# ip unnumbered Loopback0 PE3-RACK1(config-if)# mpls traffic-eng tunnels PE3-RACK1(config-if)# tunnel destination 10.1.1.2 PE3-RACK1(config-if)# tunnel mode mpls traffic-eng PE3-RACK1(config-if)# tunnel mpls traffic-eng path-option 1 dynamic
♦ Configure TE to instruct the IGP to use the tunnel in its enhanced SPF calculation.
PE2-RACK1(config-if)#interface Tunnel101 PE2-RACK1(config-if)# tunnel mpls traffic-eng autoroute announce PE3-RACK1(config-if)#interface Tunnel101
PE3-RACK1(config-if)# tunnel mpls traffic-eng autoroute announce
Trang 6After this task you should see the tunnel attempt to come up using auto-route This feature announces that it will advertise itself in to the IGP to attempt to bring the TE tunnel
PE2-RACK1#sho mpls traffic-eng autoroute MPLS TE autorouting enabled
destination 0000.0003.0003.00 has 1 tunnels Tunnel101 (load balancing metric 0, nexthop 10.1.1.3, absolute metric 1)
♦ Configure tunnel 101 with reservation priorities of the tunnel to
be set at 0 0
This feature is used to allow TE tunnels to toggle between multiple
TE tunnels in case of failure You would use it when you have multiple tunnels and you want to have different path selection and
behavior for each tunnel in the path priority 0 0 would be the
first active tunnel If you have another tunnel with a different path, with priority 1 1, it will be the next option to select
PE2-RACK1(config)#int tun 101 PE2-RACK1(config-if)#tunnel mpls traffic-eng priority 0 0
PE3-RACK1(config)#int tun 101 PE3-RACK1(config-if)#tunnel mpls traffic-eng priority 0 0
♦ Configure tunnel 101 with the record route function
PE2-RACK1(config)#int tunnel 101 PE2-RACK1(config-if)#tunnel mpls traffic-eng record-route
PE3-RACK1(config)#int tunnel 101 PE3-RACK1(config-if)#tunnel mpls traffic-eng record-route
PE3-RACK1#sho mpls traffic-eng tunnels tunnel 101 Name: to PE2 (Tunnel101) Destination: 10.1.1.2 Status:
Admin: up Oper: up Path: valid Signalling: connected path option 1, type dynamic (Basis for Setup, path weight 20)
Config Parameters:
Bandwidth: 0 kbps (Global) Priority: 0 0 Affinity: 0x0/0xFFFF Metric Type: TE (interface)
AutoRoute: enabled LockDown: disabled Loadshare: 0 bw-based auto-bw: (86400/0) 0 Bandwidth Requested: 0
InLabel : - OutLabel : Ethernet0/0.31, 65
Trang 7RSVP Signalling Info:
Src 10.1.1.3, Dst 10.1.1.2, Tun_Id 101, Tun_Instance 2 RSVP Path Info:
My Address: 172.16.13.3 Explicit Route: 172.16.13.1 172.16.12.2 10.1.1.2 Record Route:
Tspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits RSVP Resv Info:
Record Route: 172.16.13.1 172.16.12.2 Fspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits Shortest Unconstrained Path Info:
Path Weight: 20 (TE) Explicit Route: 172.16.13.3 172.16.13.1 172.16.12.2 10.1.1.2 History:
Tunnel:
Time since created: 7 days, 7 hours, 49 minutes Time since path change: 8 hours, 51 minutes Current LSP:
Uptime: 8 hours, 51 minutes Prior LSP:
ID: path option 1 [1]
Removal Trigger: router ID changed
♦ Configure tunnel 101 to support the TE traffic metric instead of depending on an IGP
This task shows you how to specify the metric type to use for PE2 – PE3 calculation when you are determining a tunnel path direction
PE2-RACK1(config)#int tun 101 PE2-RACK1(config-if)#tunnel mpls traffic-eng path-selection metric te
PE3-RACK1(config)#int tun 101 PE3-RACK1(config-if)#tunnel mpls traffic-eng path-selection metric te
PE2-RACK1# sho mpls traffic-eng tunnels tunnel 101 Name: to PE3 (Tunnel101) Destination: 10.1.1.3 Status:
Admin: up Oper: up Path: valid Signalling: connected path option 1, type dynamic (Basis for Setup, path weight 20)
Config Parameters:
Bandwidth: 0 kbps (Global) Priority: 0 0 Affinity: 0x0/0xFFFF Metric Type: TE (interface)
AutoRoute: enabled LockDown: disabled Loadshare: 0 bw-based auto-bw: (86400/0) 0 Bandwidth Requested: 0
InLabel : - OutLabel : Ethernet0/0.21, 64 RSVP Signalling Info:
Src 10.1.1.2, Dst 10.1.1.3, Tun_Id 101, Tun_Instance 517 RSVP Path Info:
My Address: 10.1.1.2 Explicit Route: 172.16.12.1 172.16.13.1 172.16.13.3 10.1.1.3
Trang 8Record Route:
Tspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits RSVP Resv Info:
Record Route: NONE Fspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits Shortest Unconstrained Path Info:
Path Weight: 20 (TE) Explicit Route: 172.16.12.1 172.16.13.1 172.16.13.3 10.1.1.3 History:
Tunnel:
Time since created: 11 hours, 25 minutes Time since path change: 27 minutes, 52 seconds Current LSP:
Uptime: 27 minutes, 52 seconds Prior LSP:
ID: path option 1 [30]
Removal Trigger: tunnel shutdown
♦ Configure TE tunnel’s bandwidth to suit the traffic flow such that
it constantly tracks the average use of the MPLS TE tunnel
PE2-RACK1(config)#int tunnel 101 PE2-RACK1(config-if)#tunnel mpls traffic-eng auto-bw
PE3-RACK1(config)#int tunnel 101 PE3-RACK1(config-if)#tunnel mpls traffic-eng auto-bw
This command allows the tunnel bandwidth to be adjusted automatically.
♦ Verify if the tunnel is up and traffic is being passed across tunnel 101
PE2-RACK1#sho interfaces tunnel 101 Tunnel101 is up, line protocol is up Hardware is Tunnel
Description: to PE3 Interface is unnumbered Using address of Loopback0 (10.1.1.2) MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec,
reliability 255/255, txload 1/255, rxload 1/255 Encapsulation TUNNEL, loopback not set
Keepalive not set Tunnel source UNKNOWN, destination 10.1.1.3 Tunnel protocol/transport Label Switching, key disabled, sequencing disabled
Checksumming of packets disabled, fast tunneling enabled Last input never, output never, output hang never
Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo
Output queue: 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
Trang 90 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
173 packets output, 9397 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
PE3-RACK1#sho interfaces tunnel 101 Tunnel101 is up, line protocol is up Hardware is Tunnel
Description: to PE2 Interface is unnumbered Using address of Loopback0 (10.1.1.3) MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec,
reliability 255/255, txload 28/255, rxload 1/255 Encapsulation TUNNEL, loopback not set
Keepalive not set Tunnel source UNKNOWN, destination 10.1.1.2 Tunnel protocol/transport Label Switching, key disabled, sequencing disabled
Checksumming of packets disabled, fast tunneling enabled Last input never, output never, output hang never
Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo
Output queue: 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 1000 bits/sec, 1 packets/sec
0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
164 packets output, 9786 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
PE2-RACK1#sho mpls traffic-eng tunnels tunnel 101 brief Signalling Summary:
LSP Tunnels Process: running RSVP Process: running Forwarding: enabled Periodic reoptimization: every 60 seconds, next in 17 seconds Periodic auto-bw collection: disabled
TUNNEL NAME DESTINATION UP IF DOWN IF STATE/PROT
to PE3 10.1.1.3 - Et0/0.21 up/up
PE3-RACK1#sho mpls traffic-eng tunnels tunnel 101 brief Signalling Summary:
LSP Tunnels Process: running RSVP Process: running Forwarding: enabled Periodic reoptimization: every 60 seconds, next in 29 seconds Periodic auto-bw collection: disabled
TUNNEL NAME DESTINATION UP IF DOWN IF STATE/PROT
to PE2 10.1.1.2 - Et0/0.31 up/up
Trang 10PE2-RACK1#sho mpls traffic-eng tunnels tunnel 101 Name: to PE3 (Tunnel101) Destination: 10.1.1.3 Status:
Admin: up Oper: up Path: valid Signalling: connected path option 1, type dynamic (Basis for Setup, path weight 20)
Config Parameters:
Bandwidth: 0 kbps (Global) Priority: 0 0 Affinity: 0x0/0xFFFF Metric Type: TE (interface)
AutoRoute: enabled LockDown: disabled Loadshare: 0 bw-based auto-bw: (86400/0) 0 Bandwidth Requested: 0
InLabel : - OutLabel : Ethernet0/0.21, 64 RSVP Signalling Info:
Src 10.1.1.2, Dst 10.1.1.3, Tun_Id 101, Tun_Instance 11 RSVP Path Info:
My Address: 10.1.1.2 Explicit Route: 172.16.12.1 172.16.13.1 172.16.13.3 10.1.1.3 Record Route:
Tspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits RSVP Resv Info:
Record Route: 172.16.12.1 172.16.13.3 Fspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits Shortest Unconstrained Path Info:
Path Weight: 20 (TE) Explicit Route: 172.16.12.1 172.16.13.1 172.16.13.3 10.1.1.3 History:
Tunnel:
Time since created: 2 hours, 45 minutes Time since path change: 11 minutes, 45 seconds Current LSP:
Uptime: 11 minutes, 45 seconds Selection: reoptimation
Prior LSP:
ID: path option 1 [6]
Removal Trigger: configuration changed
PE3-RACK1#sho mpls traffic-eng tunnels tunnel 101 Name: to PE2 (Tunnel101) Destination: 10.1.1.2 Status:
Admin: up Oper: up Path: valid Signalling: connected path option 1, type dynamic (Basis for Setup, path weight 20)
Config Parameters:
Bandwidth: 0 kbps (Global) Priority: 0 0 Affinity: 0x0/0xFFFF Metric Type: TE (interface)
AutoRoute: enabled LockDown: disabled Loadshare: 0 bw-based auto-bw: (86400/0) 0 Bandwidth Requested: 0
InLabel : - OutLabel : Ethernet0/0.31, 65 RSVP Signalling Info: