Anda di halaman 1dari 3

Some Useful links Our Website: http://inecert.com/ Our Blogs http://inecert.com/Blogs.html Our Study Groups http://inecert.com/Cisco_Study_Groups.

html

MPLS TE (Traffic Engineering)


Glossary: TE= Traffic Engineering

MPLS TE is used To guarantee the bandwidth for specific traffic Better resources management and fast convergence Efficient use of all the bandwidth available in service provider cloud Help to ensure the desired path is selected through the network TE is done using CSPF (Constrained-Based Shortest Path First) Backup link in the tunnel is also called PLR (point Link repair ) TE tunnel are unidirectional RSVP is used to map whole topology and to reserve the bandwidth o Path Message It checks the every node that the required bandwidth is available o Reserve + label It replys that the requested bandwidth is reserved for the tunnel throughout the path TE select the link using one of the below option o Bandwidth o Affinity o Administrative Weight o Explicit Path How to enable? In OSPF o Mpls traffic-engineering area o MPLS traffic-engineering router-id IN ISIS o Metric-style must be wide o Mpls traffic-engineering Level 1 or Level 2 o Mpls Router id

CSPF Path has following option to build tunnel o Dynamic (Uses the IGP routing protocol countings to build tunnel) o Explicit ( Static path selection) Routing could be done across TE using Static or policy based routing RSVP can exchange labels instead of MPLS LDP BGP also could exchange labels using vpnv4 or ipv4 ipv6 and vpnv6 IN RSVP bandwidth is reserved in 7 types 1 for each priority value like precedence Administrative weight could be used to re-route the dynamic tunnels Show mpls traffic-engineering tunnel command to see the complete path of the tunnel Show mpls traffic-engeering topology command to see the bandwidth available at each node How to enable in IOS-XR there could be lose routing or strict next hope address. If we are going to do the lose routing we can just define the loopback address of the router o Explicit path name Index 1 next-address strict ipv4 unicast (ip address) Index 2----o Inter tunnel-te 0 Ipv4 unnumbered lo 0 Path-option 10 explicit name Commit Show config commit changes to check what was the last configuration before your last commit Rollback configuration to roll back the specific commit changes. Tunnel mpls traffic-eng AutoRoute announce command uses the IGP RIB to reach the destination if we dont want to configure static route to the destination but this command could create inefficient traffic flow for the network MPLS LDP Discovery targeted-hello accept this command I will accept multihop unicast packet from Tunel head end If in the core area there are two areas running then the tunnel cannot be established from end to end we need to establish tunnel first to ABR then to the end this is called stitching IN ISIS the tunnel could be level 1 or level 2 not both types MPLS LDP Auto-config under ISIS turns on LDP neighbor ship on the interfaces where ISIS is running Head end is the router from where the tunnel is initiated it is shown in T in lDP. MPLS Fast reroute (FRR) has two options o Link protection also called NHOP(next hope protection) o Node Protection also called NNHOP We can use Bi-directional link detection protocol or sonnet packets to detect the next hope is alive In FRR Fast RR command will be at head all other commands will be at FRR link protector router If the interface is a sub interface then the convergence time of FRR gets delayed so we need to use ip rsvp signaling hello bfd in global and on interface to reroute fastly and bfd interval command For ios backup path command is (mpls traffic engineering backup-path)

Troubleshooting: If the tunnel is not coming up use show mpls TE tunnel and check if the signaling is up if not then the issue could be at own router and or on the next router

IP cef must be enabled and metric style wide must be their The best way to troubleshoot is to change the tunnel to dynamic and then check if the tunnel is coming up If the administrative metric in TE is used somewhere in the path and the metric is infinite then the tunnel will not come up IP ospf cost could also effect during static TE Router static to configure static routing on XR o Address family ipv4 unicast Destination and next hope Debug rsvp signaling could be used to check where is the issue in between the path of explicit TE Dont use announce command under Dynamic tunnel it is not required it doesnt work properly with backup tunnels

Anda mungkin juga menyukai