This Presentation covers the introduction for the seamless MPLS, beside some comparison between Unified MPLS and Traditional MPLS/VPN.

1. Prepared by: Sherif Saleh

2. Agenda
 Traditional MPLS benefits
 Expansion challenges
 Seamless MPLS Architect
 Seamless MPLS benefits

3. Traditional MPLS
benefits

4. MPLS Benefits
 MPLS Fast Switching
(Label Switching)
 Easy service Provisioning
(PE Configuration)
 Different Services Overlay
(VPNL3 , VPN L2 ,
Internet..)
 Total Services Isolation.
 Topology Customizations
 Easy Operation and
Trouble Shooting

5. MPLS Benefits
 Fast Conversion.
 End To End Service Level
Calculation.
 Core Utilization by Path
Design by TE

6. Large Deployment
Problems

7. Large Deployments Problems
 Core Link State IGP
Headache:
 Single instance
 Large Number of LSAs
 Huge processing
Consumptions
 Hard Troubleshooting.
 Hard Customization.

8. Large Deployments Problems
 Adding New Services:
 Need a Dedicated
Network to Network
Interface (NNI).
 Difficult to Ensure End
to End LSA.
 Reduce conversion time.
 Add New
Troubleshooting node

9. Large Deployments Problems
 Losing Fast conversion:
 Multiple NNIs
 No Single LSP
 Hard Troubleshooting:
 Core Routers and NNI
Are involved in the
Troubleshooting.
 Special configuration is
needed in each
Interconnection

11. Seamless MPLS Architect
 Hierarchical Design for
Easy Expansion
 Core
 Aggregation
 Access
 IGP Domain Separation
 Each segment runs its own
IGP
 LDP LSP paths within the
IGP domain
 no redistribution between
domains
 Single BGP AS

12. Routers Roles
 Access Node:
 CE Router
 IGP session to the pre-Aggregation Node
 Pre-aggregation Node:
 Responsible to Create Connectivity with
the Access Router
 First Point for the MPLS Traffic
 Create service Labels
 Create LDP Session with Aggregation
Nodes
 Create IBGP Session With CoreABR
 Aggregation Node
 Act as an MPLS Switch Forwarding Labeled
Traffic
 Have IGP and LDP Session between Pre
Aggregation and the Core ABR
 Core ABR
 Inline route-reflectors (Next Hop Self)
 Have BGP Session between Core ABR and
Pre Aggregation
 Inter domain Label distribution (RFC 3107)
between Different Core ABR
 Gateway
 Interconnection with 3rdparties

13. Service Labels distribution
 Service Labels are
Distributed Between all
Pre-aggregation Nodes
 Core ABR are used as
Route reflectors to
Enable the reachability
of the BGP Updates.
X

14. Routing inside Single Domain
 IGP Is enabled inside
Each Domain to ensure
reachability between
Routers inside Domain
 LDP is Enabled Between
the Routers to distribute
Labels

15. Far End pre-Aggregation Nodes
Reachability
 Each Core-ABR make him the
Next hop self for his aggregation
domain.
 Core-ABR advertise his own label
to reach his domain Pre-
Aggregation to all other Core-
ABR
 This advertisement is not the
usual one by the LDP, in the
Seamless MPLs it use BGP with
enabled option RFC 3107
 by using BGP-4 (RFC 3107) all the
pre aggregation routers will have
a Label to reach other pre
aggregation passing throw the
Core ABRs.
 Labels is used to ensure
Interdomain Label reachability

16. IBGP Hierarchical LSP
Source : Cisco.com

17. Seamless MPLS Provides
 Reduced number of operational points.
 Possibility to provision Same service : Layer 3 (L3)
VPN, Layer 2 (L2) VPN or InterAS mechanisms.
 Provide end-to-end MPLS transport.
 Keep Interior Gateway Protocol (IGP) areas separated
and small routing tables.
 Fast convergence.
 Easy to configure and troubleshoot.
 Ability to integrate with any access technology.

18. Thanks
 Contact Details:
 Mail: Sherifm.hussein@gmail.com