Discovery 21: Implementing CSC in a Native IP EnvironmentIt is common for lower-tier Internet service providers (ISPs) to interconnect their POPs through a higher-tier ISP. In the past this task has been accomplished by using an EBGP session to pass routing information. With the advent of higher-level services, however, this method has started to suffer from severe limitations. The CSC feature was introduced to overcome these limitations. In this exercise, carrier Yellow needs to provide connections for its customers, Green and Orange. To do this, Yellow has contracted with the carrier Blue to provide a connection between its POP sites. |
Discovery 22: Implementing CSC Using LDP Label DistributionIn this exercise, carrier Yellow has decided to convert its network to an MPLS core. This conversion will allow LDP to be used to distribute established connectivity. |
Discovery 23: Implementing CSC Using MP-BGP Label DistributionIn this exercise, carrier Blue has decided to convert the label exchange from LDP to I3GP on the interface that is supporting carrier Yellow. |
Discovery 24: Implementing CSC Using MPLS VPNsIn this exercise, the carrier Blue has decided to convert its network to provide MPLS VPN support. |
Discovery 41: Implementing MPLS Traffic EngineeringIn this lab carrier Yellow has a network that consists of five routers: R5, R6, R7, R8, and R9. R7, R8, and R9 have been configured to provide an MPLS core. This core supports two PE routers (R5 and R6). The PE routers are located at separate POP sites: POP 1 and POP 2, iespectively. The PE routers have been configured to provide MPLS VPN support to the two customers of carrier Yellow: customers Green and Orange. |
Discovery 42: Implementing Link Protection for MPLS Traffic EngineeringIf the link to R9 fails, normal IGP and MPLS processing will declare the tunnel that was created in the last lab to be down and reroute the traffic over the direct R7-to-R8 link. When the failed link recovers, the tunnel will be re-established and become active. However, the time-frame for these transfers can be unacceptable. To address this issue, carrier Yellow has decided to enable link protection with FRR. |
Discovery 51: Implementing MPLS QoSThe service provider has decided to implement MPLS QoS in the core in order to meet its SLAs. In this exercise, you will implement MPLS QoS in the core. After completing this exercise, you will be able to meet these objectives: Implement an inbound PE QoS policy; Implement an outbound PE QoS policy; Implement an outbound QoS policy from a local P router toward a remote P router; Implement an outbound QoS policy on a P router toward a PE router; Implement an outbound QoS policy on the PE router toward a CE router. Team A will configure the QoS parameters on the path from R5 to R6. Team B will configure the QoS parameters on the path from R6 to R5. |
Discovery 52: Implementing MPLS QoS and DS-TEThe customer has activated a new application that runs between servers on its sites. The service provider has discovered that it cannot meet the service agreement by routing the premium traffic through P1. To correct this issue, the service provider has decided to implement DS-TE and route this traffic over the direct Pwg-to-Pwg router link. The QoS policies remain the same; only the traffic routing must be changed. |