Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2-1

Full text

(1)Version 2.1 Nov 24, 2011. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Alcatel-Lucent Multiprotocol Label Switching (MPLS) Lab Guide.

(2) TABLE OF CONTENTS. 3.1. 3.2. 3.3. 3.4. LAB 3 LAB 4 LAB 4 LAB 5 5.1. 5.2. 5.3. 5.4. 5.5. LAB 5 LAB 6 6.1. 6.2. 6.3. 6.4. LAB 6. MPLS INFRASTRUCTURE AND LDP CONFIGURATION.....................................................4 MPLS Infrastructure Verification and IGP Configuration.................................................................6 Configuring and Verifying the Provide Core for LDP .......................................................................9 Section 3.3 – Enabling LDP ECMP..................................................................................................13 Applying Export Policy for Label Distribution.................................................................................17 REVIEW QUESTIONS ..........................................................................................................................19 IGP-BASED RSVP LSP ESTABLISHMENT .............................................................................20 REVIEW QUESTIONS ..........................................................................................................................23 ENABLING RSVP-TE LSP TUNNELS.......................................................................................24 Configure Link Coloring for Constraint-Based LSP Tunnels...........................................................26 DiffServ TE LSP – Maximum Allocation Method (MAM) ................................................................36 DiffServ TE LSP – Russian Doll Model (RDM)................................................................................45 Configure LDP over RSVP across OSPF Areas...............................................................................50 Configure RSVP for IP Routing........................................................................................................54 REVIEW QUESTIONS ..........................................................................................................................57 RSVP-TE RESILIENCY FEATURES .........................................................................................59 Enabling Primary and Secondary LSP Tunnels ...............................................................................61 Using SRLG for Path Resiliency.......................................................................................................66 FRR Facility Backup Protection.......................................................................................................72 FRR One-to-One Protection .............................................................................................................79 REVIEW QUESTIONS ..........................................................................................................................83. LAB SOLUTIONS AND ANSWERS ...............................................................................................................84. 2/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. LAB 3.

(3) FIGURE 3-1: LAB TOPOLOGY OVERVIEW ................................................................................................................4 FIGURE 3-2: IMPLEMENTING PROVIDER CORE LDP ................................................................................................9 FIGURE 3-3: ENABLING LDP ECMP .....................................................................................................................13 FIGURE 3-4: APPLYING EXPORT POLICY FOR LABEL DISTRIBUTION ....................................................................17 FIGURE 4-1: IGP BASED LSPS ..............................................................................................................................20 FIGURE 5-1: ENABLING LINK COLORING CONSTRAINT-BASED LSP TUNNELS......................................................26 FIGURE 5-2: DIFFSERV TE LSP – MAXIMUM ALLOCATION METHOD (MAM).....................................................36 FIGURE 5-3: DIFFSERV TE LSP – RUSSIAN DOLL MODEL (RDM)........................................................................45 FIGURE 5-4: ENABLING LDP TUNNELS OVER RSVP .............................................................................................50 FIGURE 5-5: ENABLING LDP TUNNELS OVER RSVP .............................................................................................54 FIGURE 6-1: ENABLING PRIMARY AND SECONDARY LSP TUNNELS ......................................................................61 FIGURE 6-2: ENABLING SRLG STANDBY LSPS .....................................................................................................66 FIGURE 6-3: ENABLING FRR FACILITY BYPASS PROTECTION ...............................................................................72 FIGURE 6-4: ENABLING PRIMARY AND SECONDARY LSP TUNNELS ......................................................................79 LIST OF TABLES TABLE 3-1: LAB 3 CONFIGURATION AND VERIFICATION COMMANDS .....................................................................5 TABLE 3-2: REMOTE LAB ADDRESSING ..................................................................................................................7 TABLE 3-3: INTERFACE IP ADDRESSING..................................................................................................................8 TABLE 4-1: LAB 4 CONFIGURATION AND VERIFICATION COMMANDS ..................................................................21 TABLE 5-1: LAB 5 CONFIGURATION AND VERIFICATION COMMANDS ...................................................................24 TABLE 6-1: LAB 6 CONFIGURATION AND VERIFICATION COMMANDS ..................................................................59. Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2.1 | All rights reserved © 2011 Alcatel-Lucent. 3/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. LIST OF FIGURES.

(4) Lab 3. MPLS Infrastructure and LDP Configuration. Objective. Once we have the routed core in place, we will begin exploring LDP operations. First, we will enable and verify LDP operation on the CORE and EDGE routers. We will identify the labels that the routers exchange and use to populate their LFIBs, mapping out the labels that an LSP uses for a given FEC. We will configure export policies to allow the routers to generate labels for prefixes other than /32 prefixes and, finally, enable ECMP and view the impact that it has on the LFIBs. Figure 3-1 shows the lab topology. Additional connection details will be provided by the instructor, if required.. Figure 3-1: Lab Topology Overview The Alcatel Multiprotocol Label Switching (MPLS) course labs use 7750 Service Routers for the core infrastructure, as shown in Figure 3-1. The 7750 SR Edge (EDGE) routers and the 7750 SR Core (CORE) routers form the Service Provider Core backbone.. 4/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. This lab prepares the routed domain to support the MPLS infrastructure that we will build as we progress through the course. Here, we will verify the operation and physical connectivity between the pods and the routers in the pods. We will verify and, if necessary, configure the interfaces and IGP..

(5) Syntax Table 3-1 provides the configuration and verification commands required for this Lab. Each command may require additional parameters other than those shown in the table. Use the ‘?’ character for help and to explore all command line options. In addition to the commands shown, you may need to use commands learned in previous courses.. A:MPLS_R1# telnet <management ip address> A:MPLS_R1# configure router interface <interface name> <address/mask>. address. A:MPLS_R1# configure router interface <interface name> port <iom/mda/port> A:MPLS_R1# configure router ospf area <area #> A:MPLS_R1# configure router ospf area <area #> interface <interface name> interface-type <point-to-point> A:MPLS_R1# show port A:MPLS_R1# show router interface A:MPLS_R1# show router ospf status A:MPLS_R1# show router ospf interface A:MPLS_R1# show router ospf neighbor A:MPLS_R1#. show router route-table. A:MPLS_R1#. ping <ip-address>. A:MPLS_R1#. traceroute <ip-route>. A:MPLS_R1# configure router ldp interface-parameters interface <interfacename> A:MPLS_R1# configure router ldp export <export-policy-name> A:MPLS_R1# configure>router>policy-options# begin A:MPLS_R1# configure>router>policy-options# policy-statement <policy-name> A:MPLS_R1# configure>router>policy-options>policy-statement# entry <entry index> A:MPLS_R1# configure>router>policy-options>policy-statement>entry# action accept A:MPLS_R1# configure>router>policy-options# commit A:MPLS_R1# clear router ldp session <neighbor-ip-address> A:MPLS_R1# show router status A:MPLS_R1# show router route-table A:MPLS_R1# show router ldp status A:MPLS_R1# show router ldp parameters Table 3-1: Lab 3 Configuration and Verification Commands. Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2.1 | All rights reserved © 2011 Alcatel-Lucent. 5/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Lab 3 Command list.

(6) Lab 3 Command list (cont’d) A:MPLS_R1# show router ldp discovery [detail] A:MPLS_R1# show router ldp interface A:MPLS_R1# show router ldp session A:MPLS_R1# show router ldp bindings A:MPLS_R1# show router ldp tunnel-table A:MPLS_R1# oam lsp-ping prefix <ip-address> A:MPLS_R1# oam lsp-trace prefix <ip-address> A:MPLS_R1>..# info (from all contexts) A:MPLS_R1>..# exit [all] (from all contexts) A:MPLS_R1# admin save <file-name> Table 3-1: Lab 3 Configuration and Verification Commands (cont’d). 3.1. MPLS Infrastructure Verification and IGP Configuration NOTE: Ask your instructor if the training center pre-configures the lab equipment. If so, you only need to verify the routing topology with the appropriate show commands. If they have not preconfigured the equipment, you will need to provision the physical cards and ports, the network interfaces, and the routing protocols, using the commands shown in Table 3-1.. Exercise 1. Record your Pod’s router management interface addresses in Table 3-2 below. Use these addresses to establish a telnet connection to your CORE, EDGE, and CE routers. All routers use the default SR OS username and password, admin. If you cannot connect or log in to any of the routers, notify your instructor. Please do not change the admin password unless instructed to do so.. 6/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. A:MPLS_R1# show router ldp bindings active.

(7) Pod Number. Management Address. Pod 1 – CORE (R1) EDGE (R5) CUSTOMER EDGE (R9) Pod 2 – CORE (R2). CUSTOMER EDGE (R10) Pod 3 – CORE (R3) EDGE (R7) CUSTOMER EDGE (R11) Pod 4 – CORE (R4) EDGE (R8) CUSTOMER EDGE (R12) Table 3-2: Remote Lab Addressing 2. Familiarize yourself with lab topology, shown in Figure 3-1 and on the lab topology handout. 3. Verify the cards, MDAs, and physical ports, using the appropriate show commands. If your routers are not pre-configured, configure the cards, MDAs, and physical ports, as shown in the diagram. 4. Use the appropriate show commands to verify each interface’s IP addresses, as shown in Table 3-3. For consistency, the last octet of a router’s IP address equals the router number shown in Table 3-2. If not yet configured, configure the interface name, port, and IP addresses, as shown in Figure 3-1 and Table 3-3. 5. Verify that all interfaces are operationally up. If not yet configured, configure the OSPF area 0 and place all but the CE system and CE-EDGE interfaces in OSPF area 0; we will configure the CE interfaces in Lab 5. 6. Verify the routing tables. The CORE and EDGE routers need routes to all subnetworks, including the system IDs, EXCEPT the CE networks. Refer to Table 3-3 for a list of subnet addresses. With all 4 pods in use, the route table contains: a. 10 Ethernet segments b. 8 system addresses c. CORE - 13 OSPF routes d. EDGE – 16 OSPF routes e. CE – 0 OSPF routes 7. If you do not see all that you expect, ask your instructor for help or clarification. 8. You may want to annotate the diagram with the configured addresses or other parameters.. Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2.1 | All rights reserved © 2011 Alcatel-Lucent. 7/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. EDGE (R6).

(8) 9. Verify the routing topology, using available tools such as ping or traceroute; if all is working as designed, you will be able to successfully ping each OSPF area 0 interface from any CORE or EDGE location. Parameter. Value toRy = where y is the opposite router’s router number. Addressing Format. 10.x.y.z/27. 1st router number. x = 1 (R1), 2 (R2), 3 (R3), 4 (R4), etc.. 2nd router number. y = opposite router number. For the last octet of the interface address use the router number from Figure 3-1. z= local interface router number; that is, 10.10.10.1/32= R1’s system IP address. System IP address. 10.10.10.z/32. R1 to R2 subnet. 10.1.2.z/27. R1 to R3 subnet. 10.1.3.z/27. R1 to R4 subnet. 10.1.4.z/27. R2 to R3 subnet. 10.2.3.z/27. R2 to R4 subnet. 10.2.4.z/27. R3 to R4 subnet. 10.3.4.z/27. R1 to R5 subnet. 10.1.5.z/27. R2 to R6 subnet. 10.2.6.z/27. R3 to R7 subnet. 10.3.7.z/27. R4 to R8 subnet. 10.4.8.z/27. R5 to R9 subnet. 10.5.9.z/27. R6 to R10 subnet. 10.6.10.z/27. R7 to R11 subnet. 10.7.11.z/27. R8 to R12 subnet. 10.8.12.z/27. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Interface name. Table 3-3: Interface IP Addressing. 8/104.

(9) Figure 3-2: Implementing Provider Core LDP. Exercise 1. On your CORE and EDGE routers, enable LDP on all but the EDGE-CE interfaces. 2. Verify that the base IGP and LDP processes are up on your EDGE and CORE routers, and that LDP has been enabled on all the appropriate network interfaces. The example below shows the LDP adjacencies between neighbors. a. How many LDP neighbors should each CORE router have? b. How many should each EDGE router have? A:MPLS_R1# show router ldp discovery =============================================================================== LDP Hello Adjacencies =============================================================================== Interface Name Local Addr Peer Addr AdjType State ------------------------------------------------------------------------------toR2 10.10.10.1 10.10.10.2 Link Estab toR3 10.10.10.1 10.10.10.3 Link Estab toR4 10.10.10.1 10.10.10.4 Link Estab toR5 10.10.10.1 10.10.10.5 Link Estab ------------------------------------------------------------------------------No. of Hello Adjacencies: 4 ===============================================================================. Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2.1 | All rights reserved © 2011 Alcatel-Lucent. 9/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. 3.2. Configuring and Verifying the Provide Core for LDP.

(10) 3. Verify that your router’s LDP sessions show “Established.” An example of the output is shown below. a. How many LDP sessions does your CORE router have? b. How many sessions does your EDGE router have? c. What types of adjacencies do your routers form? Why?. ============================================================================= LDP Sessions ============================================================================= Peer LDP Id Adj Type State Msg Sent Msg Recv Up Time ----------------------------------------------------------------------------10.10.10.2:0 Link Established 110 111 0d 00:04:48 10.10.10.3:0 Link Established 85 86 0d 00:03:38 10.10.10.4:0 Link Established 71 72 0d 00:02:58 10.10.10.5:0 Link Established 126 126 0d 00:05:33 ----------------------------------------------------------------------------No. of Sessions: 4 =============================================================================. 4. Verify the Label Information Base (LIB) of your CORE and EDGE routers. An example is shown on the next page. a. How many prefixes should be present? Explain. b. Should the CORE and EDGE routers have the same number of prefix bindings? c. What label does your CORE router generate for its system address FEC? d. On your CORE router, find the label that the diagonally connected CORE router supplies for its directly connected EDGE router. e. Why does your CORE router show some labels as “not in use”? A:MPLS_R1# show router ldp bindings =============================================================================== LDP LSR ID: 10.10.10.1 =============================================================================== Legend: U - Label In Use, N - Label Not In Use, W - Label Withdrawn S - Status Signaled Up, D - Status Signaled Down E - Epipe Service, V - VPLS Service, M - Mirror Service A - Apipe Service, F - Fpipe Service, I - IES Service, R - VPRN service P - Ipipe Service, WP - Label Withdraw Pending, C - Cpipe Service TLV - (Type, Length: Value) =============================================================================== LDP Prefix Bindings =============================================================================== Prefix Peer IngLbl EgrLbl EgrIntf/ EgrNextHop LspId ------------------------------------------------------------------------------10.10.10.1/32 10.10.10.2 131071U ---10.10.10.1/32 10.10.10.3 131071U ---10.10.10.1/32 10.10.10.4 131071U ---10.10.10.1/32 10.10.10.5 131071U ---10.10.10.2/32 10.10.10.2 -131071 1/1/2 10.1.2.2 10.10.10.2/32 10.10.10.3 131069U 131069 --10.10.10.2/32 10.10.10.4 131069U 131069 --10.10.10.2/32 10.10.10.5 131069U 131069 ---. 10/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. A:MPLS_R1# show router ldp session.

(11) =============================================================================== LDP Service FEC 128 Bindings =============================================================================== Type VCId SvcId SDPId Peer IngLbl EgrLbl LMTU RMTU ------------------------------------------------------------------------------No Matching Entries Found =============================================================================== LDP Service FEC 129 Bindings .... ============================================================================== AGI SAII TAII Type SvcId SDPId Peer IngLbl EgrLbl LMTU RMTU -----------------------------------------------------------------------------No Matching Entries Found ============================================================================== ==============================================================================. 5. Verify that your CORE and EDGE routers’ Label Forwarding Information Base (LFIBs) contains the active labels used by the router for MPLS forwarding. An example is shown below. a. What are the differences between the show router ldp bindings and the show router ldp bindings active commands? Why does the LFIB contain fewer prefix bindings than the FIB? b. Why does your CORE router both PUSH and SWAP labels for your EDGE router’s prefix? Why does it not POP labels for your EDGE router’s prefix? c. Based on the show router ldp bindings active command output, can you identify the system address of the router on which you executed the command? d. Verify each label PUSHed, SWAPed, and POPed along the LSP path from your EDGE router to the diagonally connected EDGE router.. Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2.1 | All rights reserved © 2011 Alcatel-Lucent. 11/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. 10.10.10.3/32 10.10.10.2 131068U 131068 --10.10.10.3/32 10.10.10.3 -131071 1/1/3 10.1.3.3 10.10.10.3/32 10.10.10.4 131068U 131068 --10.10.10.3/32 10.10.10.5 131068U 131068 --10.10.10.4/32 10.10.10.2 131067U 131067 --10.10.10.4/32 10.10.10.3 131067U 131067 --10.10.10.4/32 10.10.10.4 -131071 1/1/4 10.1.4.4 10.10.10.4/32 10.10.10.5 131067U 131067 --10.10.10.5/32 10.10.10.2 131070U 131069 --10.10.10.5/32 10.10.10.3 131070U 131068 --10.10.10.5/32 10.10.10.4 131070U 131067 --10.10.10.5/32 10.10.10.5 -131071 1/1/1 10.1.5.5 10.10.10.6/32 10.10.10.2 131065N 131065 1/1/2 10.1.2.2 10.10.10.6/32 10.10.10.3 131065U 131065 --10.10.10.6/32 10.10.10.4 131065U 131065 --10.10.10.6/32 10.10.10.5 131065U 131065 --10.10.10.7/32 10.10.10.2 131064U 131064 --10.10.10.7/32 10.10.10.3 131064N 131064 1/1/3 10.1.3.3 10.10.10.7/32 10.10.10.4 131064U 131064 --10.10.10.7/32 10.10.10.5 131064U 131064 --10.10.10.8/32 10.10.10.2 131066U 131066 --10.10.10.8/32 10.10.10.3 131066U 131066 --10.10.10.8/32 10.10.10.4 131066N 131066 1/1/4 10.1.4.4 10.10.10.8/32 10.10.10.5 131066U 131066 --------------------------------------------------------------------------------No. of Prefix Bindings: 32.

(12) =============================================================================== Legend: (S) - Static =============================================================================== LDP Prefix Bindings (Active) =============================================================================== Prefix Op IngLbl EgrLbl EgrIntf/LspId EgrNextHop ------------------------------------------------------------------------------10.10.10.1/32 Pop 131071 ---10.10.10.2/32 Push -131071 1/1/2 10.1.2.2 10.10.10.2/32 Swap 131069 131071 1/1/2 10.1.2.2 10.10.10.3/32 Push -131071 1/1/3 10.1.3.3 10.10.10.3/32 Swap 131068 131071 1/1/3 10.1.3.3 10.10.10.4/32 Push -131071 1/1/4 10.1.4.4 10.10.10.4/32 Swap 131067 131071 1/1/4 10.1.4.4 10.10.10.5/32 Push -131071 1/1/1 10.1.5.5 10.10.10.5/32 Swap 131070 131071 1/1/1 10.1.5.5 10.10.10.6/32 Push -131065 1/1/2 10.1.2.2 10.10.10.6/32 Swap 131065 131065 1/1/2 10.1.2.2 10.10.10.7/32 Push -131064 1/1/3 10.1.3.3 10.10.10.7/32 Swap 131064 131064 1/1/3 10.1.3.3 10.10.10.8/32 Push -131066 1/1/4 10.1.4.4 10.10.10.8/32 Swap 131066 131066 1/1/4 10.1.4.4 ------------------------------------------------------------------------------No. of Prefix Bindings: 15. 6. Verify that the LSPs that are present. An example is shown below. a. For which FECs has your router created LSPs? b. What does the metric value represent for each FEC? A:MPLS_R1# show router tunnel-table protocol ldp =============================================================================== Tunnel Table (Router: Base) =============================================================================== Destination Owner Encap TunnelId Pref Nexthop Metric ------------------------------------------------------------------------------10.10.10.2/32 ldp MPLS 9 10.1.2.2 100 10.10.10.3/32 ldp MPLS 9 10.1.3.3 100 10.10.10.4/32 ldp MPLS 9 10.1.4.4 100 10.10.10.5/32 ldp MPLS 9 10.1.5.5 100 10.10.10.6/32 ldp MPLS 9 10.1.2.2 200 10.10.10.7/32 ldp MPLS 9 10.1.3.3 200 10.10.10.8/32 ldp MPLS 9 10.1.4.4 200 ===============================================================================. 7. On your CORE router, shut down the network interface leading to the diagonally connected neighbor CORE router. 8. View your CORE and EDGE router LIBs. How did shutting down the interface change the LIB contents? 9. View your CORE and EDGE router LFIBs. a. How did shutting down the interface change the LFIB contents? b. What path will packets follow when your EDGE router forwards them to the diagonally connect EDGE router?. 12/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. A:MPLS_R1# show router ldp bindings active.

(13) c. With what label will your CORE router forward a packet sent from your EDGE router to your diagonally connected EDGE router? 10. Use the oam lsp-trace command to verify the path taken to your diagonal EDGE router. NOTE: So that the next exercise succeeds, keep the interface from your CORE router to the diagonally connected CORE router shut down.. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. 3.3. Section 3.3 – Enabling LDP ECMP. Figure 3-3: Enabling LDP ECMP. Exercise 1. Verify that you have shut down the diagonal paths in the core. 2. Enable ECMP for 4 equal cost paths. A:MPLS_R1# configure router ecmp 4. 3. View your CORE router’s route table. What next-hop does your CORE router use to reach the diagonally connected EDGE router?. Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2.1 | All rights reserved © 2011 Alcatel-Lucent. 13/104.

(14) 4. View your CORE and EDGE router LIBs. An example is shown below. a. How does this differ from the LIB entries you saw before you enabled ECMP? b. How many prefix bindings should you see in your CORE and EDGE router LIBs? Explain.. =============================================================================== LDP LSR ID: 10.10.10.1 =============================================================================== Legend: U - Label In Use, N - Label Not In Use, W - Label Withdrawn S - Status Signaled Up, D - Status Signaled Down E - Epipe Service, V - VPLS Service, M - Mirror Service A - Apipe Service, F - Fpipe Service, I - IES Service, R - VPRN service P - Ipipe Service, WP - Label Withdraw Pending, C - Cpipe Service TLV - (Type, Length: Value) =============================================================================== LDP Prefix Bindings =============================================================================== Prefix Peer IngLbl EgrLbl EgrIntf/ EgrNextHop LspId ------------------------------------------------------------------------------10.10.10.1/32 10.10.10.2 131071U ---10.10.10.1/32 10.10.10.3 131071U ---10.10.10.1/32 10.10.10.5 131071U ---10.10.10.2/32 10.10.10.2 -131071 1/1/2 10.1.2.2 10.10.10.2/32 10.10.10.3 131069U 131069 --10.10.10.2/32 10.10.10.5 131069U 131069 --10.10.10.3/32 10.10.10.2 131068U 131068 --10.10.10.3/32 10.10.10.3 -131071 1/1/3 10.1.3.3 10.10.10.3/32 10.10.10.5 131068U 131068 --10.10.10.4/32 10.10.10.2 131067N 131067 1/1/2 10.1.2.2 10.10.10.4/32 10.10.10.3 131067N 131067 1/1/3 10.1.3.3 10.10.10.4/32 10.10.10.5 131067U 131067 --10.10.10.5/32 10.10.10.2 131070U 131069 --10.10.10.5/32 10.10.10.3 131070U 131068 --10.10.10.5/32 10.10.10.5 -131071 1/1/1 10.1.5.5 10.10.10.6/32 10.10.10.2 131065N 131065 1/1/2 10.1.2.2 10.10.10.6/32 10.10.10.3 131065U 131065 --10.10.10.6/32 10.10.10.5 131065U 131065 --10.10.10.7/32 10.10.10.2 131064U 131064 --10.10.10.7/32 10.10.10.3 131064N 131064 1/1/3 10.1.3.3 10.10.10.7/32 10.10.10.5 131064U 131064 --10.10.10.8/32 10.10.10.2 131066N 131066 1/1/2 10.1.2.2 10.10.10.8/32 10.10.10.3 131066N 131066 1/1/3 10.1.3.3 10.10.10.8/32 10.10.10.5 131066U 131066 --------------------------------------------------------------------------------No. of Prefix Bindings: 24 =========================================================================== . .. 5. View the LFIBs. An example is shown on the next page. a. How does this differ from the LFIB entries you saw before you enabled ECMP? b. How many equal cost LSPs originate on your CORE router and terminate on the diagonally connected EDGE router?. 14/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. A:MPLS_R1# show router ldp bindings.

(15) =============================================================================== Legend: (S) - Static =============================================================================== LDP Prefix Bindings (Active) =============================================================================== Prefix Op IngLbl EgrLbl EgrIntf/LspId EgrNextHop ------------------------------------------------------------------------------10.10.10.1/32 Pop 131071 ---10.10.10.2/32 Push -131071 1/1/2 10.1.2.2 10.10.10.2/32 Swap 131069 131071 1/1/2 10.1.2.2 10.10.10.3/32 Push -131071 1/1/3 10.1.3.3 10.10.10.3/32 Swap 131068 131071 1/1/3 10.1.3.3 10.10.10.4/32 Push -131067 1/1/2 10.1.2.2 10.10.10.4/32 Swap 131067 131067 1/1/2 10.1.2.2 10.10.10.4/32 Push -131067 1/1/3 10.1.3.3 10.10.10.4/32 Swap 131067 131067 1/1/3 10.1.3.3 10.10.10.5/32 Push -131071 1/1/1 10.1.5.5 10.10.10.5/32 Swap 131070 131071 1/1/1 10.1.5.5 10.10.10.6/32 Push -131065 1/1/2 10.1.2.2 10.10.10.6/32 Swap 131065 131065 1/1/2 10.1.2.2 10.10.10.7/32 Push -131064 1/1/3 10.1.3.3 10.10.10.7/32 Swap 131064 131064 1/1/3 10.1.3.3 10.10.10.8/32 Push -131066 1/1/2 10.1.2.2 10.10.10.8/32 Swap 131066 131066 1/1/2 10.1.2.2 10.10.10.8/32 Push -131066 1/1/3 10.1.3.3 10.10.10.8/32 Swap 131066 131066 1/1/3 10.1.3.3 ------------------------------------------------------------------------------No. of Prefix Bindings: 19 ===============================================================================. 6. View all the LSPs present on your CORE and EDGE routers. An example is shown below. a. How many LSPs do you see connecting your routers to the diagonally connected Pod’s CORE and EDGE routers? b. How many LSPs do you see connecting your routers to the other routers? A:MPLS_R1# show router tunnel-table protocol ldp =============================================================================== Tunnel Table (Router: Base) =============================================================================== Destination Owner Encap TunnelId Pref Nexthop Metric ------------------------------------------------------------------------------10.10.10.2/32 ldp MPLS 9 10.1.2.2 100 10.10.10.3/32 ldp MPLS 9 10.1.3.3 100 10.10.10.4/32 ldp MPLS 9 10.1.2.2 200 10.10.10.4/32 ldp MPLS 9 10.1.3.3 200 10.10.10.5/32 ldp MPLS 9 10.1.5.5 100 10.10.10.6/32 ldp MPLS 9 10.1.2.2 200 10.10.10.7/32 ldp MPLS 9 10.1.3.3 200 10.10.10.8/32 ldp MPLS 9 10.1.2.2 300 10.10.10.8/32 ldp MPLS 9 10.1.3.3 300 ===============================================================================. 7. Issue an LSP trace from your CORE router to the diagonally connected neighbor’s CORE router’s system address. Which LSP path does the CORE router choose? 8. Issue an LSP trace from your CORE router to the diagonally connected neighbor’s EDGE router’s system address. Which LSP path does the CORE router choose?. Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2.1 | All rights reserved © 2011 Alcatel-Lucent. 15/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. A:MPLS_R1# show router ldp bindings active.

(16) 9. Issue an LSP trace from your EDGE router to the diagonally connected neighbor’s CORE router’s system address. Which LSP path does the EDGE router choose? 10. Issue and LSP trace from your EDGE router to the diagonally connected neighbor’s EDGE router’s system address. Which LSP path does the EDGE router choose?. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. 11. Turn up the core interfaces with a no shutdown command and disable ECMP, configure router no ecmp.. 16/104.

(17) Figure 3-4: Applying Export Policy for Label Distribution. Exercise 1. Configure an Export policy with a single entry set to “action accept”. An example is shown below. A:MPLS_R2# configure router policy-options A:MPLS_R2>config>router>policy-options# begin A:MPLS_R2>config>router>policy-options# policy-statement ldp-export A:MPLS_R2>config>router>policy-options>policy-statement$ entry 10 A:MPLS_R2>config>router>policy-options>policy-statement>entry$ action accept A:MPLS_R2>config>router>policy-options>policy-statement>entry>action$ back A:MPLS_R2>config>router>policy-options>policy-statement>entry$ back A:MPLS_R2>config>router>policy-options>policy-statement# back A:MPLS_R2>config>router>policy-options# commit A:MPLS_R2>config>router>policy-options# exit all. 2. Apply the Export policy to your CORE and EDGE routers’ LDP instances. 3. View the LIBs. An example is shown below, truncated for clarity.. Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2.1 | All rights reserved © 2011 Alcatel-Lucent. 17/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. 3.4. Applying Export Policy for Label Distribution.

(18) a. What additional FECs do your routers now generate labels for? b. How many prefix bindings do you expect to see? Explain. c. On your CORE routers, why do you see a prefix binding for your Pod’s EDGE to the CE interface? Does this prefix appear in the other CORE router LIBs? Why?. =============================================================================== LDP LSR ID: 10.10.10.1 =============================================================================== ... =============================================================================== LDP Prefix Bindings =============================================================================== Prefix Peer IngLbl EgrLbl EgrIntf/ EgrNextHop LspId ------------------------------------------------------------------------------10.1.2.0/27 10.10.10.2 131062U 131061 --10.1.2.0/27 10.10.10.3 131062U 131062 --10.1.2.0/27 10.10.10.4 131062U 131062 --10.1.2.0/27 10.10.10.5 131062U 131068 --10.1.3.0/27 10.10.10.2 131061U 131060 --10.1.3.0/27 10.10.10.3 131061U 131061 --10.1.3.0/27 10.10.10.4 131061U 131057 --10.1.3.0/27 10.10.10.5 131061U 131067 --10.1.4.0/27 10.10.10.2 131069U 131068 --10.1.4.0/27 10.10.10.3 131069U 131060 --10.1.4.0/27 10.10.10.4 131069U 131071 --10.1.4.0/27 10.10.10.5 131069U 131066 --10.1.5.0/27 10.10.10.2 131064U 131062 --10.1.5.0/27 10.10.10.3 131064U 131067 --10.1.5.0/27 10.10.10.4 131064U 131063 --10.1.5.0/27 10.10.10.5 131064U 131069 --10.2.3.0/27 10.10.10.2 131060N 131059 1/1/2 10.1.2.2 10.2.3.0/27 10.10.10.3 131060U 131057 --10.2.3.0/27 10.10.10.4 131060U 131056 --10.2.3.0/27 10.10.10.5 131060U 131065 --10.2.4.0/27 10.10.10.2 131068N 131065 1/1/2 10.1.2.2 10.2.4.0/27 10.10.10.3 131068U 131059 --10.2.4.0/27 10.10.10.4 131068U 131069 --10.2.4.0/27 10.10.10.5 131068U 131064 --10.2.6.0/27 10.10.10.2 131057N 131054 1/1/2 10.1.2.2 10.2.6.0/27 10.10.10.3 131057U 131054 --10.2.6.0/27 10.10.10.4 131057U 131053 --10.2.6.0/27 10.10.10.5 131057U 131063 --10.3.4.0/27 10.10.10.2 131067U 131064 --10.3.4.0/27 10.10.10.3 131067N 131058 1/1/3 10.1.3.3 10.3.4.0/27 10.10.10.4 131067U 131068 --10.3.4.0/27 10.10.10.5 131067U 131062 --10.3.7.0/27 10.10.10.2 131058U 131057 --10.3.7.0/27 10.10.10.3 131058N 131055 1/1/3 10.1.3.3 10.3.7.0/27 10.10.10.4 131058U 131054 --10.3.7.0/27 10.10.10.5 131058U 131061 --10.4.8.0/27 10.10.10.2 131059U 131058 --10.4.8.0/27 10.10.10.3 131059U 131056 --10.4.8.0/27 10.10.10.4 131059N 131064 1/1/4 10.1.4.4 10.4.8.0/27 10.10.10.5 131059U 131060 --10.5.9.0/27 10.10.10.5 -131054 --10.10.10.1/32 10.10.10.2 131071U ---10.10.10.1/32 10.10.10.3 131071U ---... ------------------------------------------------------------------------------No. of Prefix Bindings: 73 .... 18/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. A:MPLS_R1# show router ldp bindings.

(19) 4. View the LFIBs. An example is shown below, truncated for clarity.. =============================================================================== Legend: (S) - Static =============================================================================== LDP Prefix Bindings (Active) =============================================================================== Prefix Op IngLbl EgrLbl EgrIntf/LspId EgrNextHop ------------------------------------------------------------------------------10.1.2.0/27 Pop 131062 ---10.1.3.0/27 Pop 131061 ---10.1.4.0/27 Pop 131069 ---10.1.5.0/27 Pop 131064 ---10.2.3.0/27 Swap 131060 131059 1/1/2 10.1.2.2 10.2.4.0/27 Swap 131068 131065 1/1/2 10.1.2.2 10.2.6.0/27 Swap 131057 131054 1/1/2 10.1.2.2 10.3.4.0/27 Swap 131067 131058 1/1/3 10.1.3.3 10.3.7.0/27 Swap 131058 131055 1/1/3 10.1.3.3 10.4.8.0/27 Swap 131059 131064 1/1/4 10.1.4.4 10.10.10.1/32 Pop 131071 ---... ------------------------------------------------------------------------------No. of Prefix Bindings: 25 ===============================================================================. Lab 3. Review Questions. 1. Under normal circumstances, over what paths do the EDGE routers route traffic between each other? Issue a traceroute between EDGE routers to verify these paths. Do you have alternate paths available? 2. What router serves as the next-hop between your CORE router and router R5? 3. What metric value does OSPF assign to each link? 4. Which command may be used to view the details of each LDP peer? 5. For which FECs are labels advertised by default? How can additional FECs be advertised? 6. How does a router determine which LSP to use when ECMP LDP is enabled?. Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2.1 | All rights reserved © 2011 Alcatel-Lucent. 19/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. A:MPLS_R1# show router ldp bindings active.

(20) Lab 4. IGP-Based RSVP LSP Establishment. Objective. Figure 4-1: IGP based LSPs. Syntax Table 4-1 provides the configuration and verification commands required for this Lab. Each command may require additional parameters other than those shown in the table. Use the ‘?’ character for help and to explore all command line options. In addition to the commands shown, you may need to use commands learned in previous courses.. 20/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. In this lab we will build loose hop, IGP-based LSPs, using RSVP signaling. We will use the routers’ OAM tools to verify the LSP’s operation and path..

(21) Lab 4 Command List A:MPLS_R1# configure router mpls no shutdown A:MPLS_R1# configure router rsvp no shutdown A:MPLS_R1# configure router mpls path <path-name> A:MPLS_R1# configure router mpls lsp <lsp-name> A:MPLS_R1# show router mpls path A:MPLS_R1# show router mpls lsp [detail] A:MPLS_R1# show router mpls lsp <lsp-name> path detail A:MPLS_R1# show router ospf area detail A:MPLS_R1# show router rsvp session A:MPLS_R1# show router rsvp interface detail A:MPLS_R1# tools perform router mpls cspf to <ip-address> [from <ip-addr>] [bandwidth <bandwidth>] [include-bitmap <bitmap>] [exclude-bitmap <bitmap>] [hop-limit <limit>] [exclude-address <excl-addr> [<excl-addr>...(up to 8 max)]] A:MPLS_R1# oam lsp-ping lsp <lsp-name> A:MPLS_R1# oam lsp-trace lsp <lsp-name> A:MPLS_R1>..# info (from all contexts) A:MPLS_R1>..# exit [all] (from all contexts) A:MPLS_R1# admin save <file-name> Table 4-1: Lab 4 Configuration and Verification Commands. Exercise 1. Enable MPLS for all interfaces on your CORE and EDGE routers. Remember to globally turn up both MPLS and RSVP, as SR OS shuts down both by default. 2. Verify that MPLS is enabled on your interfaces and that the relevant interfaces are administratively and operationally up. An example is shown below. A:MPLS_R1# show router mpls interface =============================================================================== MPLS Interfaces =============================================================================== Interface Port-id Adm Opr TE-metric ------------------------------------------------------------------------------system system Up Up None Admin Groups None Srlg Groups None R1-R5 1/1/1 Up Up None Admin Groups None Srlg Groups None R1-R2 1/1/2 Up Up None Admin Groups None Srlg Groups None. Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2.1 | All rights reserved © 2011 Alcatel-Lucent. 21/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. A:MPLS_R1# configure router mpls lsp <lsp-name> to <system-id>.

(22) R1-R3 1/1/3 Up Up None Admin Groups None Srlg Groups None R1-R4 1/1/4 Up Up None Admin Groups None Srlg Groups None ------------------------------------------------------------------------------Interfaces : 5 ===============================================================================. A:MPLS_R1# show router rsvp interface =============================================================================== RSVP Interfaces =============================================================================== Interface Total Active Total BW Resv BW Adm Opr Sessions Sessions (Mbps) (Mbps) ------------------------------------------------------------------------------system Up Up toR2 0 0 1000 0 Up Up toR3 0 0 1000 0 Up Up toR4 0 0 1000 0 Up Up toR5 0 0 1000 0 Up Up ------------------------------------------------------------------------------Interfaces : 5 ===============================================================================. 6. On both your CORE and EDGE routers, configure a path named “loose” and do not specify any hops (that is, make it “totally loose”). 7. On your CORE router, configure an LSP to your EDGE router, using the loose path as the primary path. 8. On your EDGE router, configure an LSP to your CORE router, using the loose path as the primary path. 9. Verify each router’s LSP’s operational state, using the show router mpls lsp command. An example is shown below. A:MPLS_R1# show router mpls lsp =============================================================================== MPLS LSPs (Originating) =============================================================================== LSP Name To Fastfail Adm Opr Config ------------------------------------------------------------------------------toR5-1 10.10.10.5 No Up Up ------------------------------------------------------------------------------LSPs : 1 ===============================================================================. 10. Use the show router rsvp session command to obtain the LSPs’ full names. The full LSP name takes the form lsp-name::path-name. Also note the LSPs’ Tunnel and LSP IDs. An example is shown on the following page.. 22/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. 5. Verify that RSVP is enabled on your interfaces. An example is shown below..

(23) A:MPLS_R1# show router rsvp session. 11. Configure another LSP from your EDGE router to the clockwise Pod’s EDGE router, again using the loose path you created in step 4. a. Can the new LSP use the same path as the first you configured? b. Over what path will your router signal this LSP? c. What determines the path that the head-end router uses to signal this LSP path? 12. Verify the LSPs’ operation and paths using the oam lsp-ping <lsp-name> and oam lsptrace <lsp-name> commands. Examples are shown below. A:MPLS_R1# oam lsp-ping "toR5-1" LSP-PING toR5-1: 92 bytes MPLS payload Seq=1, send from intf toR5, reply from 10.10.10.5 udp-data-len=32 ttl=255 rtt=1.26ms rc=3 (EgressRtr) ---- LSP toR5-1 PING Statistics ---1 packets sent, 1 packets received, 0.00% packet loss round-trip min = 1.26ms, avg = 1.26ms, max = 1.26ms, stddev = 0.000ms A:MPLS_R1# oam lsp-trace "toR5-1" lsp-trace to toR5-1: 0 hops min, 0 hops max, 116 byte packets 10.10.10.5 rtt=1.23ms rc=3(EgressRtr) A:MPLS_R5# oam lsp-ping "toR6-2" LSP-PING toR6-2: 92 bytes MPLS payload Seq=1, send from intf toR1, reply from 10.10.10.6 udp-data-len=32 ttl=255 rtt=2.69ms rc=3 (EgressRtr) ---- LSP toR6-2 PING Statistics ---1 packets sent, 1 packets received, 0.00% packet loss round-trip min = 2.69ms, avg = 2.69ms, max = 2.69ms, stddev = 0.000ms A:MPLS_R5# oam lsp-trace "toR6-2" lsp-trace to toR6-2: 0 hops min, 0 hops max, 116 byte packets 1 10.10.10.1 rtt=1.55ms rc=8(DSRtrMatchLabel) 2 10.10.10.2 rtt=1.96ms rc=8(DSRtrMatchLabel) 3 10.10.10.6 rtt=2.60ms rc=3(EgressRtr). Lab 4. Review Questions. 1. Over what path does traffic travel when the head end router forwards it toward the LSP’s tail end? 2. Can the head end router recover the LSP if a failure occurs on the primary path? 3. What must be in place in the network before the head end router can signal the LSP requirements to the tail end?. Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2.1 | All rights reserved © 2011 Alcatel-Lucent. 23/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. =============================================================================== RSVP Sessions =============================================================================== From To Tunnel LSP Name State ID ID ------------------------------------------------------------------------------10.10.10.1 10.10.10.5 1 1536 toR5-1::loose Up ------------------------------------------------------------------------------Sessions : 1 ===============================================================================.

(24) Lab 5. Enabling RSVP-TE LSP Tunnels. Objective. Lab 5 Command list A:MPLS_R1# configure router interface shutdown A:MPLS_R1# configure router interface no shutdown A:MPLS_R1# configure router ldp targeted-session peer <peer-ip> tunneling A:MPLS_R1# configure router mpls admin-group <group-name> <group-value> A:MPLS_R1# configure router mpls interface <interface-name> A:MPLS_R1# configure router mpls interface <interface-name> admin-group <group-name> A:MPLS_R1# configure router mpls interface <interface-name> srlg-group <groupname> A:MPLS_R1# configure router mpls lsp <lsp-name> A:MPLS_R1# configure router mpls lsp <lsp-name> cspf A:MPLS_R1# configure router mpls lsp <lsp-name> no igp-shortcut A:MPLS_R1# configure router mpls lsp <lsp-name> path <path-name> include <group-name> exclude <group-name> A:MPLS_R1# configure router mpls lsp <lsp-name> primary <path-name> A:MPLS_R1# configure router mpls lsp <lsp-name> secondary <path-name> A:MPLS_R1# configure router mpls lsp <lsp-name> secondary <path-name> srlg A:MPLS_R1# configure router mpls lsp <lsp-name> secondary <path-name> standby A:MPLS_R1# configure router mpls lsp <lsp-name> to <system-id> A:MPLS_R1# configure router mpls no shutdown A:MPLS_R1# configure router mpls path <path-name> A:MPLS_R1# configure router mpls path <path-name> hop <index> [strict | loose] A:MPLS_R1# configure router mpls srlg-group <group-name> value <group-value> A:MPLS_R1# configure router ospf area <area-id> interface <interface-name> interface-type point-to-point A:MPLS_R1# configure router ospf ldp-over-rsvp Table 5-1: Lab 5 Configuration and Verification Commands. 24/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. In this lab, we will use link coloring techniques to build constraint-based LSPs. Then, we will configure RSVP-TE support over multiple OSPF areas, using LDP over RSVP for multi-area forwarding. We will explore DiffServ-TE LSP behavior based on the Maximum Allocation Model (MAM) and Russian Doll Model (RDM). Finally, we will build RSVP-TE signaled LSPs for tunneling IGP routed traffic from edge-to-edge..

(25) Lab 5 Command list (cont’d) A:MPLS_R1# configure router ospf rsvp-shortcut A:MPLS_R1# configure router ospf traffic-engineering A:MPLS_R1# configure router rsvp no shutdown A:MPLS_R1# show router mpls path A:MPLS_R1# show router mpls lsp <lsp-name> path detail A:MPLS_R1# show router mpls lsp terminate detail A:MPLS_R1# show router mpls lsp transit detail A:MPLS_R1# show router ospf area detail A:MPLS_R1# show router ospf status A:MPLS_R1# show router rsvp session A:MPLS_R1# show router ospf opaque-database A:MPLS_R1# show router ospf opaque-database adv-router <router-id> detail A:MPLS_R1# tools dump router ospf route-table <prefix> detail Table 5-1: Lab 5 Configuration and Verification Commands (cont’d). Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2.1 | All rights reserved © 2011 Alcatel-Lucent. 25/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. A:MPLS_R1# show router mpls lsp [detail].

(26) Figure 5-1: Enabling Link Coloring Constraint-Based LSP Tunnels. Exercise In this exercise, you will enable traffic-engineering and CSPF on LSPs, connecting your CORE router to the clockwise CORE router. You will create two admin groups, red and green, and to assign each of your core interfaces to the appropriate admin group. On your LSPs, you will include green and exclude red links, and observe the LSP’s behavior as you shut down the direct links between the core routers. Phase I – Enable and verify CSPF 1. On both of your routers, use the show router ospf status command to verify that Traffic Engineering is currently disabled. a. Do your routers support Opaque LSAs by default? b. Why do your routers support Opaque LSAs, though TE support is disabled? 2. Verify that your router’s opaque database is empty. View the opaque database on your CORE router. An example of the output is shown below. Note: If others have already enabled TE on their routers, you may see Opaque LSAs in your routers’ opaque databases.. 26/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. 5.1. Configure Link Coloring for Constraint-Based LSP Tunnels.

(27) A:MPLS_R1# show router ospf opaque-database. 3. View the number of Type 10 Area Opaque LSAs on your CORE router. An example is shown below. a. How many Type 10 LSAs do your routers report? b. Why would your router report type 10 LSAs if you have not yet enabled TE? A:MPLS_R1# show router ospf area detail =============================================================================== OSPF Areas (Detailed) =============================================================================== ------------------------------------------------------------------------------Area Id: 0.0.0.0 ------------------------------------------------------------------------------Area Id : 0.0.0.0 Type : Standard Key Rollover Int.: 10 Virtual Links : 0 Total Nbrs : 4 Active IFs : 5 Total IFs : 5 Area Bdr Rtrs : 0 AS Bdr Rtrs : 0 SPF Runs : 37 Last SPF Run : 06/23/2010 07:36:18 Router LSAs : 8 Network LSAs : 0 Summary LSAs : 0 Asbr-summ LSAs : 0 Nssa ext LSAs : 0 Area opaque LSAs : 0 Total LSAs : 8 LSA Cksum Sum : 0x324be Blackhole Range : True Unknown LSAs : 0 ===============================================================================. 4. For now, enable Traffic Engineering only on your EDGE router. 5. Again, view the number of Type 10 Area Opaque LSAs on your CORE router. An example output is shown below. a. How many Type 10 LSAs do you see? b. Why has this value increased although you have not enabled TE on this router? A:MPLS_R1# show router ospf area detail =============================================================================== OSPF Areas (Detailed) =============================================================================== ------------------------------------------------------------------------------Area Id: 0.0.0.0 ------------------------------------------------------------------------------Area Id : 0.0.0.0 Type : Standard Key Rollover Int.: 10 Virtual Links : 0 Total Nbrs : 4 Active IFs : 5 Total IFs : 5 Area Bdr Rtrs : 0 AS Bdr Rtrs : 0 SPF Runs : 37 Last SPF Run : 06/23/2010 07:36:18 Router LSAs : 8 Network LSAs : 0. Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2.1 | All rights reserved © 2011 Alcatel-Lucent. 27/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. =============================================================================== OSPF Opaque Link State Database (Type : All) =============================================================================== Type Id Link State Id Adv Rtr Id Age Sequence Cksum ------------------------------------------------------------------------------------------------------------------------------------------------------------No. of Opaque LSAs: 0.

(28) Summary LSAs : 0 Asbr-summ LSAs : 0 Nssa ext LSAs : 0 Area opaque LSAs : 8 Total LSAs : 16 LSA Cksum Sum : 0x33da9 Blackhole Range : True Unknown LSAs : 0 ===============================================================================. 6. Enable Traffic Engineering on your CORE router. Confirm that Traffic Engineering is now enabled.. A:MPLS_R1# show router ospf opaque-database =============================================================================== OSPF Opaque Link State Database (Type : All) =============================================================================== Type Id Link State Id Adv Rtr Id Age Sequence Cksum ------------------------------------------------------------------------------Area 0.0.0.0 1.0.0.1 10.10.10.1 95 0x80000001 0x12fe Area 0.0.0.0 1.0.0.2 10.10.10.1 95 0x80000001 0x81ca Area 0.0.0.0 1.0.0.3 10.10.10.1 95 0x80000001 0x6be3 Area 0.0.0.0 1.0.0.4 10.10.10.1 95 0x80000001 0x4afe Area 0.0.0.0 1.0.0.5 10.10.10.1 95 0x80000001 0xde5e Area 0.0.0.0 1.0.0.1 10.10.10.2 10 0x80000001 0x16f8 Area 0.0.0.0 1.0.0.2 10.10.10.2 10 0x80000001 0x5dee Area 0.0.0.0 1.0.0.3 10.10.10.2 10 0x80000001 0x4ef4 Area 0.0.0.0 1.0.0.4 10.10.10.2 10 0x80000001 0xc27b Area 0.0.0.0 1.0.0.5 10.10.10.2 10 0x80000001 0xb57f Area 0.0.0.0 1.0.0.1 10.10.10.3 77 0x80000001 0x1af2 Area 0.0.0.0 1.0.0.2 10.10.10.3 77 0x80000001 0xb790 Area 0.0.0.0 1.0.0.3 10.10.10.3 77 0x80000001 0x2a19 Area 0.0.0.0 1.0.0.4 10.10.10.3 77 0x80000001 0x90b1 Area 0.0.0.0 1.0.0.5 10.10.10.3 77 0x80000001 0x8ca0 Area 0.0.0.0 1.0.0.1 10.10.10.4 60 0x80000001 0x1eec Area 0.0.0.0 1.0.0.2 10.10.10.4 60 0x80000001 0x1232 Area 0.0.0.0 1.0.0.3 10.10.10.4 60 0x80000001 0x84ba Area 0.0.0.0 1.0.0.4 10.10.10.4 60 0x80000001 0xf643 Area 0.0.0.0 1.0.0.5 10.10.10.4 60 0x80000001 0xd854 Area 0.0.0.0 1.0.0.1 10.10.10.5 380 0x80000001 0x22e6 Area 0.0.0.0 1.0.0.2 10.10.10.5 380 0x80000001 0xe166 Area 0.0.0.0 1.0.0.1 10.10.10.6 52 0x80000001 0x26e0 Area 0.0.0.0 1.0.0.2 10.10.10.6 52 0x80000001 0x43f4 Area 0.0.0.0 1.0.0.1 10.10.10.7 41 0x80000001 0x2ada Area 0.0.0.0 1.0.0.2 10.10.10.7 55 0x80000001 0x1a16 Area 0.0.0.0 1.0.0.1 10.10.10.8 46 0x80000001 0x2ed4 Area 0.0.0.0 1.0.0.2 10.10.10.8 46 0x80000001 0xf037 ------------------------------------------------------------------------------No. of Opaque LSAs: 28 ===============================================================================. 8. On your CORE router, use the show router ospf opaque-database adv-router <router-id> detail command, where <router-id> belongs to your CORE router, for a more detailed description of the opaque LSA for your router. An example output is shown on the following page. a. Why do you not see opaque LSAs generated by the other routers? b. Why is 0.0.0.0 the Area ID shown? c. Which top-level TLV sub-types do the LSAs contain, and what do they specify?. 28/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. 7. Verify that your CORE router now has opaque LSAs in the database. An example output is shown below..

(29) =============================================================================== OSPF Opaque Link State Database (Type : All) (Detailed) =============================================================================== ------------------------------------------------------------------------------Opaque LSA ------------------------------------------------------------------------------Area Id : 0.0.0.0 Adv Router Id : 10.10.10.1 Link State Id : 1.0.0.1 LSA Type : Area Opaque Sequence No : 0x80000001 Checksum : 0x12fe Age : 186 Length : 28 Options : E. Advertisement : ROUTER-ID TLV. (0001) Len. 4 : 10.10.10.1. ------------------------------------------------------------------------------Opaque LSA ------------------------------------------------------------------------------Area Id : 0.0.0.0 Adv Router Id : 10.10.10.1 Link State Id : 1.0.0.2 LSA Type : Area Opaque Sequence No : 0x80000001 Checksum : 0x81ca Age : 186 Length : 124 Options : E Advertisement :. LINK INFO TLV. (0002) Len 100 :. Sub-TLV: 1 Len: 1 LINK_TYPE : 1 Sub-TLV: 2 Len: 4 LINK_ID : 10.10.10.2 Sub-TLV: 3 Len: 4 LOC_IP_ADDR : 10.1.2.1 Sub-TLV: 4 Len: 4 REM_IP_ADDR : 10.1.2.2 Sub-TLV: 5 Len: 4 TE_METRIC : 100 Sub-TLV: 6 Len: 4 MAX_BDWTH : 1000000 Kbps Sub-TLV: 7 Len: 4 RSRVBL_BDWTH : 1000000 Kbps Sub-TLV: 8 Len: 32 UNRSRVD_CLS0 : P0: 1000000 Kbps P1: 1000000 Kbps P2: 1000000 Kbps P3: 1000000 Kbps P4: 1000000 Kbps P5: 1000000 Kbps P6: 1000000 Kbps P7: 1000000 Kbps Sub-TLV: 9 Len: 4 ADMIN_GROUP : 0 None. 9. Again, verify the number of Type 10 Area Opaque LSAs now discovered. An example is shown below. a. Write down the number of Type 10 LSAs now reported. b. How many Type 10 LSAs should be discovered when everyone in the class has finished enabling Traffic Engineering? A:MPLS_R1# show router ospf area detail =============================================================================== OSPF Areas (Detailed) =============================================================================== ------------------------------------------------------------------------------Area Id: 0.0.0.0 ------------------------------------------------------------------------------Area Id : 0.0.0.0 Type : Standard Key Rollover Int.: 10 Virtual Links : 0 Total Nbrs : 4 Active IFs : 5 Total IFs : 5 Area Bdr Rtrs : 0 AS Bdr Rtrs : 0 SPF Runs : 80 Last SPF Run : 06/26/2010 00:17:55 Router LSAs : 8 Network LSAs : 0 Summary LSAs : 0 Asbr-summ LSAs : 0 Nssa ext LSAs : 0 Area opaque LSAs : 28 Total LSAs : 36 LSA Cksum Sum : 0x112590 Blackhole Range : True Unknown LSAs : 0===============================================================================. Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2.1 | All rights reserved © 2011 Alcatel-Lucent. 29/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. A:MPLS_R1# show router ospf opaque-database adv-router 10.10.10.1 detail.

(30) Phase II – Configure link coloring 10. On your CORE routers, configure two administrative groups: one called “green” with a group value of 1, and the other called “red” with a group value of 2. Assign group green to all CORE outer ring MPLS interfaces, and assign groups green and red to the diagonally CORE interfaces.. 11. Verify that the admin groups are on your CORE router, and that you have applied them to the correct interfaces. An example output is shown below. A:MPLS_R1# show router mpls admin-group ================================================= MPLS Administrative Groups ================================================= Group Name Group Value ------------------------------------------------green 1 red 2 -------------------------------------------------No. of Groups: 2 ==================================================. A:MPLS_R1# show router mpls interface =============================================================================== MPLS Interfaces =============================================================================== Interface Port-id Adm Opr TE-metric ------------------------------------------------------------------------------system system Up Up None Admin Groups None Srlg Groups None P1-PE1 1/1/1 Up Up None Admin Groups None Srlg Groups None P1-P2 1/1/2 Up Up None. Admin Groups. green. Srlg Groups P1-P3. None 1/1/3. Up. Up. None. Srlg Groups P1-P4. None 1/1/4. Up. Up. None. Admin Groups Admin Groups. green green. red Srlg Groups None ------------------------------------------------------------------------------Interfaces : 5 ===============================================================================. 12. On your CORE router, use the show router ospf opaque-database adv-router <router-id> detail command, where <router-id> is the router ID of your CORE router, for a more detailed description of the opaque LSAs for your router. An example is shown below. a. Why are the ADMIN_GROUP values shown not equal to the admin group values you set in the configure router mlps admin-group command?. 30/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. For example: If you work with router R2, assign the router R1 and R4 interfaces to the green group, and the router R3 interface to both the green and the red group. See Figure 5-1 for clarification..

(31) b. Which ADMIN_GROUP value represents the green group? Which value represents the red and green groups? c. Why do you see all bandwidth available on the links? Admin-group mapping to bitmap table: 31. 28 27. 24 23. 20 19. 16. 15. 12 11. 8. 7. 4. 3. 0. Admin Group Sub TLV: 00000006 (6) Decimal (2^1 + 2^2) Hexadecimal 0110 A:MPLS_R1# show router ospf opaque-database adv-router 10.10.10.1 detail =============================================================================== OSPF Opaque Link State Database (Type : All) (Detailed) =============================================================================== ------------------------------------------------------------------------------Opaque LSA ------------------------------------------------------------------------------Area Id : 0.0.0.0 Adv Router Id : 10.10.10.1 Link State Id : 1.0.0.1 LSA Type : Area Opaque Sequence No : 0x80000002 Checksum : 0x10ff Age : 716 Length : 28 Options : E Advertisement : ROUTER-ID TLV (0001) Len 4 : 10.10.10.1 ------------------------------------------------------------------------------Opaque LSA ------------------------------------------------------------------------------Area Id : 0.0.0.0 Adv Router Id : 10.10.10.1 Link State Id : 1.0.0.2 LSA Type : Area Opaque Sequence No : 0x80000004 Checksum : 0x50f6 Age : 1316 Length : 124 Options : E Advertisement : LINK INFO TLV (0002) Len 100 : Sub-TLV: 1 Len: 1 LINK_TYPE : 1 Sub-TLV: 2 Len: 4 LINK_ID : 10.10.10.2 Sub-TLV: 3 Len: 4 LOC_IP_ADDR : 10.1.2.1 Sub-TLV: 4 Len: 4 REM_IP_ADDR : 10.1.2.2 Sub-TLV: 5 Len: 4 TE_METRIC : 100 Sub-TLV: 6 Len: 4 MAX_BDWTH : 1000000 Kbps Sub-TLV: 7 Len: 4 RSRVBL_BDWTH : 1000000 Kbps Sub-TLV: 8 Len: 32 UNRSRVD_CLS0 : P0: 1000000 Kbps P1: 1000000 Kbps P2: 1000000 Kbps P3: 1000000 Kbps P4: 1000000 Kbps P5: 1000000 Kbps P6: 1000000 Kbps P7: 1000000 Kbps Sub-TLV: 9 Len: 4 ADMIN_GROUP : 00000002 (2) ------------------------------------------------------------------------------Opaque LSA ------------------------------------------------------------------------------- Area Id : 0.0.0.0 Adv Router Id : 10.10.10.1 Link State Id : 1.0.0.3 LSA Type : Area Opaque Sequence No : 0x80000004 Checksum : 0xc47d. Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2.1 | All rights reserved © 2011 Alcatel-Lucent. 31/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 00 0 0 11 0.

(32) 13. On your CORE router, configure a loose hop LSP that terminates on the clockwise CORE router. Use the existing loose path for the primary path. Enable CSPF on the LSP, and include admin group “green” and exclude admin group “red” under the primary path context. Use the show router mpls lsp <lsp-name> path detail command to verify the path that the LSP takes. An example is shown below. a. Does the LSP follow the IGP chosen best path? Why? b. How does the head end router inform the downstream routers of the path it chose for the LSP? A:MPLS_R1# show router mpls lsp "toR2-lsp1" path detail =============================================================================== MPLS LSP toR2-lsp1 Path (Detail) =============================================================================== Legend : @ - Detour Available # - Detour In Use b - Bandwidth Protected n - Node Protected s - Soft Preemption =============================================================================== ------------------------------------------------------------------------------LSP toR2-lsp1 Path loose ------------------------------------------------------------------------------LSP Name : toR2-lsp1 Path LSP ID : 39424 From : 10.10.10.1 To : 10.10.10.2 Adm State : Up Oper State : Up Path Name : loose Path Type : Primary Path Admin : Up Path Oper : Up OutInterface: 1/1/2 Out Label : 131071 Path Up Time: 0d 00:00:16 Path Dn Time: 0d 00:00:00 Retry Limit : 0 Retry Timer : 30 sec RetryAttempt: 0 NextRetryIn : 0 sec SetupPriori*: 7 Hold Priori*: 0 Preference : n/a Bandwidth : No Reservation Oper Bw : 0 Mbps Hop Limit : 255 Class Type : 0 Backup CT : None MainCT Retry: n/a MainCT Retry: 0 Rem : Limit : Oper CT : 0 Record Route: Record Record Label: Record Oper MTU : 9198 Neg MTU : 9198 Adaptive : Enabled Oper Metric : 100 Include Grps: Exclude Grps: green red Path Trans : 1 CSPF Queries: 1. 32/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Age : 1316 Length : 124 Options : E Advertisement : LINK INFO TLV (0002) Len 100 : Sub-TLV: 1 Len: 1 LINK_TYPE : 1 Sub-TLV: 2 Len: 4 LINK_ID : 10.10.10.3 Sub-TLV: 3 Len: 4 LOC_IP_ADDR : 10.1.3.1 Sub-TLV: 4 Len: 4 REM_IP_ADDR : 10.1.3.3 Sub-TLV: 5 Len: 4 TE_METRIC : 100 Sub-TLV: 6 Len: 4 MAX_BDWTH : 1000000 Kbps Sub-TLV: 7 Len: 4 RSRVBL_BDWTH : 1000000 Kbps Sub-TLV: 8 Len: 32 UNRSRVD_CLS0 : P0: 1000000 Kbps P1: 1000000 Kbps P2: 1000000 Kbps P3: 1000000 Kbps P4: 1000000 Kbps P5: 1000000 Kbps P6: 1000000 Kbps P7: 1000000 Kbps Sub-TLV: 9 Len: 4 ADMIN_GROUP : 00000002 (2) ....

(33) NOTE: In the next steps, work together to ensure that each pod successfully completes the procedures given, and verify that the head end router chooses the best path to the tail end router. We recommend working through steps 14 -16 one pod at a time. 14. On your CORE router, shut down the interface facing the clockwise CORE router. After a few seconds, view the LSP path with the show router mpls lsp <lsp-name> path detail command. An example is shown below. a. Is the head end router able to resignal the LSP over a new path? Why or why not? b. Does the new path follow the IGP path? Why or why not? HINT: Use the traceroute and oam lsp-trace commands and compare the results. c. Did the CSPF metric change? Why or why not? A:MPLS_R1# show router mpls lsp "toR2-lsp1" path detail =============================================================================== MPLS LSP toR2-lsp1 Path (Detail) =============================================================================== Legend : @ - Detour Available # - Detour In Use b - Bandwidth Protected n - Node Protected s - Soft Preemption =============================================================================== ------------------------------------------------------------------------------LSP toR2-lsp1 Path loose ------------------------------------------------------------------------------LSP Name : toR2-lsp1 Path LSP ID : 39432 From : 10.10.10.1 To : 10.10.10.2 Adm State : Up Oper State : Up Path Name : loose Path Type : Primary Path Admin : Up Path Oper : Up OutInterface: 1/1/3 Out Label : 131071 Path Up Time: 0d 00:01:55 Path Dn Time: 0d 00:00:00 Retry Limit : 0 Retry Timer : 30 sec RetryAttempt: 0 NextRetryIn : 0 sec SetupPriori*: 7 Hold Priori*: 0 Preference : n/a Bandwidth : No Reservation Oper Bw : 0 Mbps Hop Limit : 255 Class Type : 0 Backup CT : None MainCT Retry: n/a MainCT Retry: 0 Rem : Limit : Oper CT : 0 Record Route: Record Record Label: Record Oper MTU : 9198 Neg MTU : 9198 Adaptive : Enabled Oper Metric : 300 Include Grps: Exclude Grps: green red. Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2.1 | All rights reserved © 2011 Alcatel-Lucent. 33/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Failure Code: noError Failure Node: n/a ExplicitHops: No Hops Specified Actual Hops : 10.1.2.1(10.10.10.1) Record Label : N/A -> 10.1.2.2(10.10.10.2) Record Label : 131071 ComputedHops: 10.1.2.1 -> 10.1.2.2 ResigEligib*: False LastResignal: n/a CSPF Metric : 100 =============================================================================== * indicates that the corresponding row element may have been truncated..

(34) 15. On the same CORE router, shut down the interface facing the counter-clockwise CORE router. After a few seconds, view the LSP path with the show router mpls lsp <lsp-name> path detail command. An example is shown below. a. Is the head end router able to resignal the LSP over a new path? Why? b. Does the show command output provide any indication as to whether or not the LSP recovered? c. Use the trace commands and compare the results. Is there still an IGP route to the tail end router? A:MPLS_R1# show router mpls lsp "toR2-lsp1" path detail =============================================================================== MPLS LSP toR2-lsp1 Path (Detail) =============================================================================== Legend : @ - Detour Available # - Detour In Use b - Bandwidth Protected n - Node Protected s - Soft Preemption =============================================================================== ------------------------------------------------------------------------------LSP toR2-lsp1 Path loose ------------------------------------------------------------------------------LSP Name : toR2-lsp1 Path LSP ID : 39434 From : 10.10.10.1 To : 10.10.10.2 Adm State : Up Oper State : Down Path Name : loose Path Type : Primary Path Admin : Up Path Oper : Down OutInterface: n/a Out Label : n/a Path Up Time: 0d 00:00:00 Path Dn Time: 0d 00:00:57 Retry Limit : 0 Retry Timer : 30 sec RetryAttempt: 1 NextRetryIn : 4 sec SetupPriori*: 7 Hold Priori*: 0 Preference : n/a Bandwidth : No Reservation Oper Bw : 0 Mbps Hop Limit : 255 Class Type : 0 Backup CT : None MainCT Retry: n/a MainCT Retry: 0 Rem : Limit : Oper CT : None Record Route: Record Record Label: Record Oper MTU : 0 Neg MTU : 0 Adaptive : Enabled Oper Metric : 65535 Include Grps: Exclude Grps: green red Path Trans : 9 CSPF Queries: 30 Failure Code: noCspfRouteToDestination Failure Node: 10.10.10.1. 34/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Path Trans : 8 CSPF Queries: 29 Failure Code: noError Failure Node: n/a ExplicitHops: No Hops Specified Actual Hops : 10.1.3.1(10.10.10.1) Record Label : N/A -> 10.1.3.3(10.10.10.3) Record Label : 131071 -> 10.3.4.4(10.10.10.4) Record Label : 131067 -> 10.2.4.2(10.10.10.2) Record Label : 131059 ComputedHops: 10.1.3.1 -> 10.1.3.3 -> 10.3.4.4 -> 10.2.4.2 ResigEligib*: False LastResignal: n/a CSPF Metric : 300 =============================================================================== * indicates that the corresponding row element may have been truncated..

(35) 16. Turn up the interfaces and verify that the routers move the LSP back to the original path. You can use the tools perform router mpls resignal lsp <lsp-name> path <pathname> command to make the head end resignal the LSP more quickly.. Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2.1 | All rights reserved © 2011 Alcatel-Lucent. 35/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. ExplicitHops: No Hops Specified Actual Hops : No Hops Specified ComputedHops: No Hops Specified ResigEligib*: False LastResignal: n/a CSPF Metric : 0 =============================================================================== * indicates that the corresponding row element may have been truncated..

(36) Figure 5-2: DiffServ TE LSP – Maximum Allocation Method (MAM). Exercise In this exercise, we will build four loose path LSPs from our CORE router to the diagonally opposite CORE router. Two LSPs will carry data, and two will carry voice over IP traffic. We will define two Class Types, CT0 for data and CT1 for voice, and then assign and allocate bandwidth based on these CTs. We will observe the routers’ behavior as we use up allocated bandwidth on the shortest path, and so force the routers to adjust to the changing conditions by resignaling LSPs as necessary. Phase I 1. On your CORE router, shut down MPLS. Configure RSVP to support DiffServ-TE with the configure router rsvp diffserv-te {mam/rdm} command. We will use MAM to begin. 2. Give CT0 20 percent and CT1 20 percent of the maximum reservable bandwidth. The commands required are shown below. A:MPLS_R1>config>router>rsvp# diffserv-te mam A:MPLS_R1>config>router>rsvp>diffserv-te# class-type-bw ct0 20 ct1 20 ct2 0 ct3 0 ct4 0 ct5 0 ct6 0 ct7 0 A:MPLS_R1>config>router>rsvp>diffserv-te#. 36/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. 5.2. DiffServ TE LSP – Maximum Allocation Method (MAM).

(37) 3. On your CORE routers, set the te-classes as shown below. A:MPLS_R1>config>router>rsvp>diffserv-te# A:MPLS_R1>config>router>rsvp>diffserv-te# A:MPLS_R1>config>router>rsvp>diffserv-te# A:MPLS_R1>config>router>rsvp>diffserv-te# A:MPLS_R1>config>router>rsvp>diffserv-te#. te-class te-class te-class te-class exit. 0 1 2 3. class-type class-type class-type class-type. 0 0 1 1. priority priority priority priority. 1 0 1 0. 5. View the opaque database and verify the bandwidth allocation information passed in the opaque LSAs. An example is shown below. a. How much bandwidth does your router allocate to CT0? b. How much does it allocate to CT1? c. How much does it allocate to the other CTs? A:MPLSv2_R1# show router ospf opaque-database detail =============================================================================== OSPF Opaque Link State Database (Type : All) (Detailed) =============================================================================== ------------------------------------------------------------------------------Opaque LSA ------------------------------------------------------------------------------Area Id : 0.0.0.0 Adv Router Id : 10.10.10.1 Link State Id : 1.0.0.1 LSA Type : Area Opaque Sequence No : 0x8000002f Checksum : 0xb52d Age : 799 Length : 28 Options : E Advertisement : ROUTER-ID TLV (0001) Len 4 : 10.10.10.1 ------------------------------------------------------------------------------Opaque LSA ------------------------------------------------------------------------------Area Id : 0.0.0.0 Adv Router Id : 10.10.10.1 Link State Id : 1.0.0.2 LSA Type : Area Opaque Sequence No : 0x80000002 Checksum : 0x547b Age : 818 Length : 164 Options : E Advertisement : LINK INFO TLV (0002) Len 140 : Sub-TLV: 1 Len: 1 LINK_TYPE : 1 Sub-TLV: 2 Len: 4 LINK_ID : 10.10.10.2 Sub-TLV: 3 Len: 4 LOC_IP_ADDR : 10.1.2.1 Sub-TLV: 4 Len: 4 REM_IP_ADDR : 10.1.2.2 Sub-TLV: 5 Len: 4 TE_METRIC : 100 Sub-TLV: 6 Len: 4 MAX_BDWTH : 1000000 Kbps Sub-TLV: 7 Len: 4 RSRVBL_BDWTH : 1000000 Kbps Sub-TLV: 8 Len: 32 UNRSRVD_CLS0 : P0: 200000 Kbps P1: 200000 Kbps P2: 200000 Kbps P3: 200000 Kbps P4: 0 Kbps P5: 0 Kbps P6: 0 Kbps P7: 0 Kbps Sub-TLV: 9 Len: 4 ADMIN_GROUP : 00000002 (2) Sub-TLV: 17 Len: 36 TELK_BW_CONST: BW Model : MAM BC0: 200000 Kbps BC1: 200000 Kbps BC2: 0 Kbps BC3: 0 Kbps BC4: 0 Kbps BC5: 0 Kbps BC6: 0 Kbps BC7: 0 Kbps. 6. View the TE classes currently defined on the router. An example is shown on the following page.. Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2.1 | All rights reserved © 2011 Alcatel-Lucent. 37/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. 4. Turn MPLS back up..

(38) =============================================================================== RSVP Status =============================================================================== Admin Status : Up Oper Status : Up Keep Multiplier : 3 Refresh Time : 30 sec Message Pacing : Disabled Pacing Period : 100 msec Max Packet Burst : 650 msgs Refresh Bypass : Disabled Rapid Retransmit : 5 hmsec Rapid Retry Limit : 3 Graceful Shutdown : Disabled SoftPreemptionTimer: 300 sec Implicit Null Label: Disabled DiffServTE AdmModel: Mam Percent Link Bw CT0: 20 Percent Link Bw CT4: 0 Percent Link Bw CT1: 20 Percent Link Bw CT5: 0 Percent Link Bw CT2: 0 Percent Link Bw CT6: 0 Percent Link Bw CT3: 0 Percent Link Bw CT7: 0 TE0 -> Class Type : 0 Priority : 1 TE1 -> Class Type : 0 Priority : 0 TE2 -> Class Type : 1 Priority : 1 TE3 -> Class Type : 1 Priority : 0 IgpThresholdUpdate : Disabled Up Thresholds(%) : 0 15 30 45 60 75 80 85 90 95 96 97 98 99 100 Down Thresholds(%) : 100 99 98 97 96 95 90 85 80 75 60 45 30 15 0 Update Timer : N/A Update on CAC Fail : Disabled ===============================================================================. 7. On your CORE router, view the reserved and unreserved bandwidth values on your interfaces. How much of the bandwidth that you allocated is currently available? A:MPLS_R1# show router rsvp interface "toR2" detail =============================================================================== RSVP Interface (Detailed) : toR2 =============================================================================== ------------------------------------------------------------------------------Interface : toR2 ------------------------------------------------------------------------------Interface : toR2 Port ID : 1/1/2 Admin State : Up Oper State : Up Active Sessions : 0 Active Resvs : 0 Total Sessions : 0 Subscription : 100 % Port Speed : 1000 Mbps Total BW : 1000 Mbps Aggregate : Dsabl Hello Interval : 3000 ms Hello Timeouts : 1 Authentication : Disabled Auth Rx Seq Num : n/a Auth Key Id : n/a Auth Tx Seq Num : n/a Auth Win Size : n/a Refresh Reduc. : Disabled Reliable Deli. : Disabled Bfd Enabled : No Graceful Shut. : Disabled ImplicitNullLabel : Disabled* Percent Link Bw Link Bw Link Bw Link Bw. Link Bandwidth for Class Types* CT0 : 20 Link Bw CT4 CT1 : 20 Link Bw CT5 CT2 : 0 Link Bw CT6 CT3 : 0 Link Bw CT7. Bandwidth Constraints for Class Types (Kbps) BC0 : 200000 BC4 BC1 : 200000 BC5 BC2 : 0 BC6 BC3 : 0 BC7. : : : :. 0 0 0 0. : : : :. 0 0 0 0. 38/104. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. A:MPLS_R1# show router rsvp status.

No results found