Services Architecture v3.2 Student Guide Download

Full text

(1)Alcatel-Lucent Services Architecture. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Module 0 — Course Introduction. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 0 – Page 1.

(2) Module Overview.  Alcatel-Lucent Career Certification  General Course Information  Timeline  Prerequisites  Introduction  Goal  Administration. Alcatel-Lucent Services Architecture v3.2. Module 0 |. 2. All rights reserved © 2012 Alcatel-Lucent. Alcatel-Lucent Services Architecture This course is part of the Alcatel-Lucent Service Routing Certification (SRC) Program. See www.alcatellucent.com/src for more information on the SRC program. To locate additional information relating to the topics presented in this manual, refer to the following:  Technical Practices for the specific product  Internet Standards documentation such as protocol standards bodies, RFCs, and IETF drafts  Technical support pages of the Alcatel-Lucent website located at: http://www.alcatel-lucent.com/support. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 0 – Page 2. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  Objectives.

(3) ALCATEL-LUCENT NETWORK ROUTING SPECIALIST I. ALCATEL-LUCENT NETWORK ROUTING SPECIALIST II. 4 DAYS / 1 COURSE / 1 WRITTEN EXAM. 18 DAYS / 4 COURSES / 4 WRITTEN EXAMS / 1 PRACTICAL LAB EXAM. ALCATEL-LUCENT ALCATEL-LUCENT TRIPLE PLAY ROUTING PROFESSIONAL MOBILE ROUTING PROFESSIONAL 36 DAYS / 8 COURSES / 8 WRITTEN EXAMS / 1 PRACTICAL LAB EXAM. 32 DAYS/ 7 COURSES / 7 WRITTEN EXAMS / 2 PRACTICAL LAB EXAMS. ALCATEL-LUCENT SERVICE ROUTING ARCHITECT 49 DAYS / 11 COURSES / 11 WRITTEN EXAMS / 2 PRACTICAL LAB EXAMS. Alcatel-Lucent Services Architecture v3.2. Alcatel-Lucent Services Architecture v3.2. Module 0 |. 3. All rights reserved © 2012 Alcatel-Lucent. All rights reserved © 2012 Alcatel-Lucent. Module 0 – Page 3. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Alcatel-Lucent Service Routing Certification Program ― Four Certifications.

(4) Alcatel-Lucent Services Architecture v3.2. Alcatel-Lucent Services Architecture v3.2. Module 0 |. 4. All rights reserved © 2012 Alcatel-Lucent. All rights reserved © 2012 Alcatel-Lucent. Module 0 – Page 4. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. SRC Program ― Courses and Exams.

(5) Exam Number. Exam Pre-requisites (4A0-XXX). Alcatel-Lucent Scalable IP Networks. 4A0-100. NA. Alcatel-Lucent Interior Routing Protocols. 4A0-101. NA. Alcatel-Lucent Border Gateway Protocol. 4A0-102. NA. Exam Name. Alcatel-Lucent Multiprotocol Label Switching. 4A0-103. NA. Alcatel-Lucent Services Architecture. 4A0-104. NA. Alcatel-Lucent Virtual Private LAN Services. 4A0-105. NA. Alcatel-Lucent Virtual Private Routed Networks. 4A0-106. NA. Alcatel-Lucent Quality of Service. 4A0-107. NA. Alcatel-Lucent Multicast Protocols. 4A0-108. NA. Alcatel-Lucent Triple Play Services. 4A0-109. NA. Alcatel-Lucent Advanced Troubleshooting. 4A0-110. NA. Alcatel-Lucent IP/MPLS Mobile Backhaul Transport. 4A0-M01. NA. Alcatel-Lucent Mobile Gateways for the LTE Evolved Packet Core. 4A0-M02. NA. Alcatel-Lucent Network Routing Specialist II Lab Exam. NRSII4A0. 100, 101, 103, 104. Alcatel-Lucent Mobile Routing Professional Lab Exam. MRP4A0. 100, 101, 103, 104, 107, M01, M02, NRSII4A0. Alcatel-Lucent Service Routing Architect Lab Exam. ASRA4A0. 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, NRSII4A0. Alcatel-Lucent Services Architecture v3.2. Alcatel-Lucent Services Architecture v3.2. Module 0 |. 5. All rights reserved © 2012 Alcatel-Lucent. All rights reserved © 2012 Alcatel-Lucent. Module 0 – Page 5. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. SRC Program ― Exam Profile.

(6) Exam Delivery. Written Exams  Delivered by Prometric  Global provider of testing services  5000+ test sites worldwide. Lab Exams  Written at Alcatel-Lucent sites  NRS II Certification • Half-day lab exam  SRA Certification • Full-day lab exam. Alcatel-Lucent Services Architecture v3.2. Alcatel-Lucent Services Architecture v3.2. Module 0 |. 6. All rights reserved © 2012 Alcatel-Lucent. All rights reserved © 2012 Alcatel-Lucent. Module 0 – Page 6. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  Register at: www.prometric.com/alcatel-lucent.

(7) SRC Program Global Reach, Flexible Delivery Options. . On-site delivery at your business location anywhere in the world. . Delivery from any of fifteen Alcatel-Lucent University locations globally  APAC ― Shanghai, China  Americas ― Sydney, Australia. ― Plano, USA. ― Wellington, New Zealand ― Bangalore, Chennai, Gurgaon, Mumbai, India.  Europe. ― Ottawa, Canada ― Mexico City, Mexico ― Sao Paulo, Brazil. ― Antwerp, Belgium ― Newport, UK ― Paris, France  Class schedules posted @ www.alcatel-lucent.com/src  Registration online @ www.alcatel-lucent.com/srcreg. Alcatel-Lucent Services Architecture v3.2. Alcatel-Lucent Services Architecture v3.2. Module 0 |. 7. All rights reserved © 2012 Alcatel-Lucent. All rights reserved © 2012 Alcatel-Lucent. Module 0 – Page 7. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. ― Melbourne, Australia.

(8) Your Own Service Router Lab – Now you can have one. Need access to a lab to help you:  Prepare for your NRS II and SRA exams?  Practice and build your service routing knowledge and configuration skills?  Remote, private access (7×24) to an Alcatel-Lucent service router lab: six-node fully meshed network – three-hour time slots available  Access to a suite of over 30 lab “practice” scenarios with optimal solutions  Access to traffic simulation and analysis tools  To find out more and sign up visit http://www.alcatellucent.com/src/examprep. Alcatel-Lucent Services Architecture v3.2. Alcatel-Lucent Services Architecture v3.2. Module 0 |. 8. All rights reserved © 2012 Alcatel-Lucent. All rights reserved © 2012 Alcatel-Lucent. Module 0 – Page 8. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. The Alcatel-Lucent Exam Preparation service provides:.

(9) Credit for Other IP Certifications Cisco or Juniper certified?.  Certifications must be valid to receive exemptions  Submit your request for exemptions at: http://www.alcatellucent.com/srcexemptions. Alcatel-Lucent Services Architecture v3.2. Alcatel-Lucent Services Architecture v3.2. Module 0 |. 9. All rights reserved © 2012 Alcatel-Lucent. All rights reserved © 2012 Alcatel-Lucent. Module 0 – Page 9. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  You can receive exemptions from some of the SRC exams, if you hold any one of the Cisco or Juniper certifications identified.

(10) This course will provide course participants with foundation knowledge of Layer 2 services (VPWS and VPLS), Layer 3 services (IES and VPRN), and mirroring service and how to implement these services in an Alcatel-Lucent environment.. Alcatel-Lucent Services Architecture v3.2. Alcatel-Lucent Services Architecture v3.2. Module 0 |. 10. All rights reserved © 2012 Alcatel-Lucent. All rights reserved © 2012 Alcatel-Lucent. Module 0 – Page 10. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Alcatel-Lucent Services Architecture ― Goal.

(11) Alcatel-Lucent Services Architecture ― Course Objectives. Upon successful completion of this course, you should be able to:  Demonstrate the significance of Alcatel-Lucent services  List the different service types available and their components  Explain the encapsulation of service data with a service label and transport label  Describe the operation of VPWS services  Configure, verify and troubleshoot an epipe service  Recognize the interworking capabilities of the different VPWS  Explain the operation of Virtual Private LAN Service (VPLS)  Configure and verify a VPLS. Alcatel-Lucent Services Architecture v3.2. Alcatel-Lucent Services Architecture v3.2. Module 0 |. 11. All rights reserved © 2012 Alcatel-Lucent. All rights reserved © 2012 Alcatel-Lucent. Module 0 – Page 11. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  Explain the concept of SAP and SDP and how they are used.

(12) Alcatel-Lucent Services Architecture ― Course Objectives.  Explain the operation of Internet enhanced services (IES)  Describe the operation of the basic VPRN architecture  Configure, verify, and troubleshoot an IPv4 VPRN  Configure, verify, and troubleshoot an IPv6 VPRN. Alcatel-Lucent Services Architecture v3.2. Alcatel-Lucent Services Architecture v3.2. Module 0 |. 12. All rights reserved © 2012 Alcatel-Lucent. All rights reserved © 2012 Alcatel-Lucent. Module 0 – Page 12. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Upon successful completion of this course, you should be able to:  Use the correct operations, administration and maintenance (OAM) tools to analyze, manage, and troubleshoot IP/MPLS service networks  Describe mirror services and differentiate between local and distributed mirror services.

(13) Alcatel-Lucent Services Architecture ― Course Timeline.  Day 1  Module 0 — Course Introduction  Module 1 — Services Overview and Implementation  Lab 1 – IP/MPLS Infrastructure  Lab 2 - Distributed Epipe Service.  Day 2  Module 2 — Virtual Private Wire Service – section 2 and 3  Module 3 — Virtual Private LAN Service  Lab 3 – VPLS Service  Lab 4 – Spoke Termination to a VPLS. Alcatel-Lucent Services Architecture v3.2. Alcatel-Lucent Services Architecture v3.2. Module 0 |. 13. All rights reserved © 2012 Alcatel-Lucent. All rights reserved © 2012 Alcatel-Lucent. Module 0 – Page 13. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  Module 2 — Virtual Private Wire Service – section 1.

(14) Alcatel-Lucent Services Architecture ― Course Timeline (cont’d). Day 3  Module 4 — OAM Tools and Mirroring Service  Lab 5 — OAM Tools  Module 5 — Layer 3 Services (Sections 1 and 2)  Lab 7 — IES  Lab 8 — VPLS Spoke Termination on IES. Day 4  Module 5 — Layer 3 Services (Sections 3-6)  Lab 9 — IPv4 VPRN  Lab 10 — IPv6 VPRN. Alcatel-Lucent Services Architecture v3.2. Alcatel-Lucent Services Architecture v3.2. Module 0 |. 14. All rights reserved © 2012 Alcatel-Lucent. All rights reserved © 2012 Alcatel-Lucent. Module 0 – Page 14. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  Lab 6 — Mirror Service.

(15) Alcatel-Lucent Services Architecture ― Course Prerequisites Suggested Prerequisites  Alcatel-Lucent Scalable IP Networks  Alcatel-Lucent Interior Routing Protocols. Alcatel-Lucent Services Architecture Exam  To ensure full comprehension of the material covered in this course, it is recommended that, upon successful completion of the Services Architecture course, the student register for and take this exam.. Alcatel-Lucent Services Architecture v3.2. Module 0 |. 15. All rights reserved © 2012 Alcatel-Lucent. Notice that the BGP section of the ASIN course is one of the important topics required as a prerequisite for the Virtual Private Routed Network sections of module 5.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 0 – Page 15. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  Alcatel-Lucent Multiprotocol Label Switching.

(16) Alcatel-Lucent Services Architecture ― Symbols and Icons. Alcatel-Lucent 7750 SR. Customer sites. Generic switch. Internet. MP-BGP Update. Pipe. Alcatel-Lucent Services Architecture v3.2. Alcatel-Lucent Services Architecture v3.2. Network cloud (various colors). Encapsulated Ethernet Frame. Module 0 |. 16. All rights reserved © 2012 Alcatel-Lucent. All rights reserved © 2012 Alcatel-Lucent. Module 0 – Page 16. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. IP router.

(17) Registration Facility information Restrooms Communications Materials Schedule Introductions  Name and company  Experience  Familiarity with Services Architecture  Questions.       . Alcatel-Lucent Services Architecture v3.2. Alcatel-Lucent Services Architecture v3.2. Module 0 |. 17. All rights reserved © 2012 Alcatel-Lucent. All rights reserved © 2012 Alcatel-Lucent. Module 0 – Page 17. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Administration.

(18) Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. www.alcatel-lucent.com. 3HE-02770-AAAA-WBZZA Edition 01.

(19) Alcatel-Lucent Services Architecture. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Module 1 — Services Overview & Implementation. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 1.

(20) Module Objectives. After successfully completing this module, you will be able to:.  Describe the different service types offered on the AlcatelLucent 7750 SR  Explain the components required to support these services. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 2. All rights reserved © 2012 Alcatel-Lucent. Alcatel-Lucent Services Architecture This course is part of the Alcatel-Lucent Service Routing Certification (SRC) Program. Visit the AlcatelLucent web site at www.alcatel-lucent.com/src for more information on the SRC program. To locate additional information related to the topics presented in this manual, refer to the following:  Technical Practices for the specific product  Internet Standards documentation such as protocol standards bodies, RFCs and IETF drafts  Technical support pages of the Alcatel-Lucent web site located at http://www.alcatellucent.com/support This module provides an introduction to the concept of a service router; the service configuration model will be described along with various service entities such as customer, SAP and SDP. In addition, a brief overview of service policies will also be covered. We will also examine how Alcatel-Lucent implements the services concept, and steps are provided for deploying a services tunnel in a service provider’s core MPLS backbone.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 2. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  Describe a service router and how it differs from a traditional router.

(21) Services Overview & Implementation. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Section 1 — Introduction to Services. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 3.

(22) Section Objectives After successfully completing this section, you will be able to:  Describe the features of a service router  List the differences between a service router and a traditional router. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  Define the concept of a “service”  Describe the types of services offered by the Alcatel-Lucent service router. Alcatel-Lucent Services Architecture v 3.2. Alcatel-Lucent Services Architecture v3.2. Module 1 |. 4. All rights reserved © 2012 Alcatel-Lucent. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 4.

(23) Telecommunication Services Technologies Service Providers Telecommunications Networks  Time division multiplexing (TDM) technologies for real-time voice  Frame Relay and ATM for private network services with specific service levels Requirement is to offer all types of services on one platform. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 5. All rights reserved © 2012 Alcatel-Lucent. Historically, telecommunications service providers have deployed completely separate networks to provide different types of services, such as time division multiplexing (TDM) technologies for real-time voice, Frame Relay and ATM for private network services with specific service levels and IP for best effort data services.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 5. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  IP for best effort data services.

(24) Converged Network Infrastructure Requirements. Service providers consolidate the delivery of multiple service types onto a single networking technology because of:  High cost of maintaining and operating discrete legacy networks.  Consumer demand for new services that require higher bandwidth service at decreasing prices. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 6. All rights reserved © 2012 Alcatel-Lucent. A number of factors are driving service providers to evolve to a single network infrastructure that supports the delivery of a wide variety of telecommunications services. These include: •High cost of maintaining and operating discrete legacy networks. •Service provider desire to continue to support high-revenue legacy services such as Frame Relay and TDM. •Consumer demand for new services such as wireless data and streaming video. •Competitive market creating consumer expectations of higher bandwidth service at decreasing prices. One approach to building a common infrastructure for deploying a wide range of telecommunication services uses a core IP/MPLS network that supports a range of virtual private network (VPN) services.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 6. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  The need to continue to support the high revenue legacy services such as Frame Relay and TDM.

(25) A single network infrastructure using a core IP/MPLS network that supports a range of virtual private network (VPN) services. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 7. All rights reserved © 2012 Alcatel-Lucent. The Alcatel-Lucent 7750 SR product family was specifically designed to build a single network infrastructure using a core IP/MPLS network that supports a range of virtual private network (VPN) services The Alcatel-Lucent 7750 SR has the ability to collapse separate overlay networks onto one platform while still supporting an overlay model. Before we get into the details of the Alcatel-Lucent Service Router, we need to understand what is meant by virtual private network (VPN). Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 7. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Alcatel-Lucent Solution: Alcatel-Lucent 7750 Service Router.

(26) Virtual Private Network (VPN) Service VPN is a network in which a shared infrastructure is used to provide private services to its users Virtual - A VPN to the service provider is a virtual network Private - A VPN to the customer is a private network. Service:  A logical entity that refers to a type of connectivity (Internet, Layer 2 or Layer 3 VPN)  Each service is uniquely identified by a service ID. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 8. All rights reserved © 2012 Alcatel-Lucent. VPN is a network in which a service provider shared infrastructure is used to provide private services to its customers. It is virtual since it does not require separate dedicated circuits between various locations, and it is based on the logical as opposed to physical separation of the facilities. It is private in the sense that customers can maintain their own addressing and routing schemes fully independent of and transparent to other customers. A service is a logical globally unique entity that provides a uniform, end-to-end configuration, management, and billing model for provisioning either Internet or VPN connectivity between customer access points; it can be either local or distributed.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 8. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Network – A collection of devices that communicate with each other.

(27) The Alcatel-Lucent Service Router A scalable IP router that offers best-effort IP routing and supports data services using a service-oriented architecture. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 9. All rights reserved © 2012 Alcatel-Lucent. A service router is a scalable Internet router that offers best-effort Internet services as well as enables the migration of traditional data services to a service-oriented architecture. Existing Layer 3 switches and Internet routers were designed around interfaces or physical ports for besteffort packet forwarding. It is often the case that edge routers are old core/Internet routers with channelized interfaces; traditional IP service platforms were designed for low-speed, best-effort consumer services. Alternately, the Alcatel-Lucent service router is designed primarily for use as a service router. The service router delivers service-level-agreement-based services, also known as SLA-based services. A service router such as the 7750 SR must support additional functionality including: Quality of Service (QoS) - The ability to provide distinct levels of service depending on the customer, application or service level agreement. Accounting - The ability to measure the traffic and service delivered based on a specific customer or service and perform logging and billing accordingly Filtering — The ability to restrict or monitor specific traffic, based on customer or service Troubleshooting — The ability to analyze and troubleshoot problems from the perspective of a specific service These capabilities are supported to a varying degree in traditional IP routers, but generally they are oriented around the router’s interfaces or physical ports. It can be difficult to apply these functions to a specific service instance since many services may use the same port.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 9. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. .

(28) Typical IP/MPLS Service Network Components  A service router functions as the Provider Edge (PE) router in a service network. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 10. All rights reserved © 2012 Alcatel-Lucent. The key component in a service network is the provider edge (PE) router that provides the interface between the customer network and the core service provider network. All the service-specific functions are found in the PE router The service router functions as the PE router in a service network. It is a scalable, full function IP/MPLS router that supports the full range of service types and customers and the additional service management capabilities described earlier. Access Routers typically support low-speed Internet access services and are not equipped to provide the higher bandwidth required to meet future customer needs. Core or Provider (P) routers support high-speed interfaces and are primarily designed to provide the capacities for forwarding large quantities of data. Core routers are not well-suited for supporting the QoS, bandwidth management and accounting functions needed by a service-edge router. These devices can be connected to other PE or P routers. They will run a routing protocol for the purposes of internal routing in the provider core using the provider’s choice of IP addressing. Layer 2 or IP Service Switches were created in an attempt to enhance core routers; by increasing the processing power, IP service switches provide services such as subscriber management and encryption. However, the IP service switch does not support complete Internet routing functionality, nor does it provide the same variety of routing policies that are available in a service edge router.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 10. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  A PE router provides the interface between the customer network and the core service provider network.

(29) Alcatel-Lucent 7750 SR Service Types The following types of service are offered on the Alcatel-Lucent 7750 SR:  VPN services.  Virtual private LAN service (VPLS) — provides a multipoint Ethernet service similar to an Ethernet switch  Virtual private routed network service (VPRN) — provides a multipoint IP routed service.  Internet Enhanced Service (IES)  Provides the customer with a Layer 3 IP interface to send and receive Internet traffic.  Mirroring services. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 11. All rights reserved © 2012 Alcatel-Lucent. A variety of different service types are supported in a service network of Alcatel-Lucent 7750 SRs, based on a common core of IP/MPLS technology. The different possible VPN services are: Virtual Private Wire Service (VPWS) also known as Virtual Leased Lines (VLL)– Layer 2 point-to-point service. Virtual Private LAN Service (VPLS) - Layer 2 multipoint-to-multipoint VPN Virtual Private Routed Network (VPRN) - Layer 3 IP multipoint-to-multipoint VPN service as defined in RFC 4364 (formerly RFC 2547bis) In addition to the VPN based services, the 7750 SR supports the Internet Enhanced Service. IES is a Layer 3 direct Internet access service where the customer is assigned an IP interface for Internet connectivity. Mirroring services - allows an operator to see the actual traffic on a customer’s service with a sniffer. Mirror service be will be discussed later in module 4.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 11. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  Virtual private wire service (VPWS) — provides a point-to-point service that emulates a leased line.

(30) Virtual Private Wire Service (VPWS)  VPWS is a Layer 2 point-to-point service  VPWS defines a virtual point-to-point service that emulates a private leased line connection. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 12. All rights reserved © 2012 Alcatel-Lucent. Virtual Private Wire Service (VPWS) The Alcatel-Lucent 7750 SR supports a Layer 2 point-to-point service commonly known as a Virtual Private Wire Service (VPWS). The VPWS encapsulates customer data and transports it across a service provider’s IP or MPLS network in a GRE or MPLS tunnel. VPWS is sometimes referred to as Layer 1 VPN, since there is no MAC learning required. The Alcatel-Lucent service router is able to provide point-to-point Ethernet, Frame Relay, ATM (Asynchronous Transfer Mode) or TDM (Time Division Multiplexing) service. In the slide figure a service provider network provides an epipe (point-to-point Ethernet) service. A pseudowire is an emulated, Layer 2 circuit built across an MPLS network that can transport Layer 2 PDUs (protocol data units) as if they were transmitted on their native media. Epipes (Ethernet), apipes (ATM), fpipes (Frame Relay), ipipes (IP Interworking) and cpipes (TDM circuit emulation) are all examples of pseudowire technologies and are described in more detail in Module 2.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 12. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  VPWS encapsulates customer data and transports it across the service provider’s network in a GRE (generic routing encapsulation) or MPLS tunnel.

(31) Types of VPWS. . VPWS service supported on the Alcatel-Lucent 7750 SR  EPipe - emulates a point-to-point Ethernet service  Apipe - emulates a point-to-point ATM service.  Cpipe - emulates a point-to-point TDM circuit  Ipipe - provides IP interworking capabilities between different Layer 2 technologies. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 13. All rights reserved © 2012 Alcatel-Lucent. The types of VPWS service supported on the Alcatel-Lucent 7750 SR include: Epipe - emulates a point-to-point Ethernet service. VLAN tagged Ethernet frames are supported. Interworking with other Layer 2 technologies is also supported. Apipe - emulates a point-to-point ATM service. A number of sub-types are provided to support different ATM service types. Fpipe - emulates a point-to-point Frame Relay circuit. Some features for interworking with ATM are also supported. Cpipe - emulates a point-to-point TDM circuit. Ipipe - provides IP interworking capabilities between different Layer 2 technologies. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 13. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  Fpipe - emulates a point-to-point Frame Relay circuit.

(32) VPWS Advantages Customer’s perspective:  Supports ATM, Frame Relay, TDM or Ethernet  Service provider (SP) network appears as a leased line between the two customer locations. Service provider’s perspective:  Only the PE device is aware of the service  Scalability  Flexibility  The service provider can apply QoS, billing, ingress/egress traffic shaping and policing on a per-service basis. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 14. All rights reserved © 2012 Alcatel-Lucent. Scalability – the service provider can support thousands of customers per router Flexibility – many different services for different customers can be provided over a single core IP/MPLS network. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 14. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  Transparent to customer data.

(33) Virtual Private LAN Service (VPLS). Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 15. All rights reserved © 2012 Alcatel-Lucent. Alcatel-Lucent supports Virtual Private LAN Service (VPLS) multipoint switched services. A VPLS is a multipoint Layer 2 service that allows multiple customer sites to be connected in a single-switched domain contained within a provider-managed IP/MPLS network. Customer sites in the VPLS appear to be on the same LAN, even if the sites are geographically dispersed. VPLS services switch traffic based on MAC addresses.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 15. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  VPLS is an Ethernet service that connects multiple sites in a single switched domain over a provider-managed IP/MPLS network.

(34) VPLS Advantages Customer’s perspective:  It looks as if all sites appear to be connected to a single-switched VLAN  Can operates over a single, local site or over multiple, geographically-dispersed sites  Frames are only forwarded across the required links in the network Service provider’s perspective:  The advantages to the service provider are similar to those of a VPWS service. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 16. All rights reserved © 2012 Alcatel-Lucent. The VPLS advantages from the customer’s perspective are: •The VPLS is transparent to the customer’s data and higher layer protocols, •The VPLS can operate over a single local site or at multiple, geographically dispersed sites •The VPLS performs MAC learning so that frames are forwarded only across the required links in the network The advantages to the service provider are the same advantages as for a VPWS service. The SP can reuse the IP/MPLS infrastructure to offer multiple services.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 16. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  Transparent to the customer’s data.

(35) Virtual Private Routed Network (VPRN). Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 17. All rights reserved © 2012 Alcatel-Lucent. Virtual Private Routed Network (VPRN) IETF RFC 4364 (formerly RFC 2547bis) details a method of distributing routing information and forwarding data to provide a Layer 3 Virtual Private Networks (VPN) service to end-customers. Each Virtual Private Routed Network (VPRN) consists of a set of customer sites connected to one or more PE routers. Each associated PE router maintains a separate IP forwarding table for each VPRN. The diagram shows three VPRN services (Red, Yellow, and Green). The details of VPRN service operation will be explained later in the course.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 17. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  VPRN is a Layer 3 service that connects multiple sites in a routed domain over a provider-managed IP/MPLS network.

(36) VPRN Advantages Customer’s perspective:  Sites are connected to a private routed network administered by the service provider for that customer only  The VPRN can operate over a single local site or over multiple geographically-dispersed sites Service provider’s perspective:  The advantages to the service provider are the same advantages as for a VPWS or VPLS service. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 18. All rights reserved © 2012 Alcatel-Lucent. The VPRN advantages from the customer perspective are: •To the customer it appears as if all sites are connected to a private, routed IP network. The PE router maintains a separate, virtual routing and forwarding (VRF) table for each VPRN •The IP address plan used by the customer is completely separate and independent of any address plan used by the provider or any of its other customers. •The VPRN can operate over a single, local site or at multiple, geographically-dispersed sites The advantages to the service provider are the same advantages as for a VPWS or VPLS service. The service provider uses MP-BGP to distribute the routes for the different customer networks.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 18. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  Separate and independent IP address plan per VPRN.

(37) Internet Enhanced Service (IES)  IES provides customers with direct Internet access via a Layer 3 IP interface  From the customer’s perspective, IES provides a direct connection to the Internet. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 19. All rights reserved © 2012 Alcatel-Lucent. An Internet enhanced service (IES) is a routed connectivity service where the subscriber communicates with a Layer 3 IP interface to send and receive Internet traffic. The difference between the IES and a basic network interface is that the service provider can apply all QoS, billing, ingress/egress shaping and policing available within a service to the IES interface.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 19. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  The service provider can apply all billing, ingress/egress shaping and policing to the customer.

(38) Services Overview & Implementation. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Section 2 — Transport and Service Label Signaling. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 20.

(39) Section Objectives After successfully completing this section, you will be able to:  Explain how customer data is transmitted across the service provider network (MPLS vs. GRE tunnels)  Explain the encapsulation of service data with a service label and transport label. Alcatel-Lucent Services Architecture v 3.2. Alcatel-Lucent Services Architecture v3.2. Module 1 |. 21. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  Explain how service labels are signaled. All rights reserved © 2012 Alcatel-Lucent. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 21.

(40) . MPLS or GRE tunnels are used to transmit customer data across the service provider network. . Multiple service tunnels can be carried within a transport tunnel. . Multiple transport tunnels can be configured on a single network port. . Inner service label defines the service tunnel; outer transport label defines the transport tunnel. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 22. All rights reserved © 2012 Alcatel-Lucent. All the IP/MPLS VPN services described in section one use MPLS or GRE tunnels to transmit customer data across the service provider network. When MPLS is used, customer data is encapsulated with two MPLS labels; an outer transport label and an inner service label. Alcatel-Lucent routers are connected to physical links that are used to carry traffic. When a service is set up using MPLS, transport LSP tunnels are set up between provider edge, or PE, routers. Each service or customer sends traffic through a service tunnel within the transport LSP tunnel. Transport tunnel LSPs are identified by MPLS labels that are swapped at each intermediate router, also known as a transit LSR, along the LSP from the ingress to the egress of the MPLS network. The service label, or VC label, is used to identify which service or customer owns the packet. In the identification process, the label is attached at the ingress point and does not change value as the packet travels from ingress to egress.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 22. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Transport Tunnels and Service Tunnels.

(41) Transport Tunnels and Service Tunnels (continued) Transport tunnels:  RSVP-TE or LDP signaled LSP  Labels are signaled using RSVP-TE or LDP  The MPLS-encapsulated data is forwarded to the egress PE for the service.  The data is encapsulated with an IP header  The source IP address is the ingress PE router and the destination address is the egress PE router  Typically used when there are routers in the transport network that do not support MPLS label switching. Service tunnels:  MP-BGP or T-LDP are used to set up per-VPN service tunnels. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 23. All rights reserved © 2012 Alcatel-Lucent. Typically the transport tunnel is an RSVP-TE or LDP signaled LSP although it may also be a GRE tunnel. Because the customer data is MPLS-encapsulated, forwarding across the network is not based at all on the customer data. The encapsulated data is simply forwarded to the tunnel egress, which is the egress PE for the service. In GRE the data is encapsulated with an IP header. The source IP address is the ingress PE router and the destination address is the egress PE router. This header is used to route the packet across the network. The customer’s data has no influence on forwarding while the packet is in the GRE tunnel. GRE does not support traffic engineering futures that are available in MPLS Our focus here is on the use of MPLS for transport tunnels.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 23. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  GRE tunnel.

(42) Transport and Service Label Encapsulation. . DLC header — Layer 2 header used to transport the MPLS packet. . MPLS transport (outer) label — The label signaled by the next-hop PE. . Service (inner) label — The service, or virtual circuit (VC) label that identifies the service the packet belongs to. . Control word — Optional and primarily used for ATM or Frame Relay services. . Service packet —The customer data being transported by the service. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 24. All rights reserved © 2012 Alcatel-Lucent. Services over MPLS In an IP/MPLS service network, data is encapsulated with at least two labels, the transport label and the service label. Data Link Control Header (DLC Header) - a Layer 2 header used to transport the MPLS packet. In many cases, the data link, or Layer 2, header in use is Ethernet. In this case, all of the following apply: a 14-byte DLC header, a 6-byte destination MAC address, a 6-byte source MAC address and a 2-byte Ethertype field (0x8847 for MPLS or 0x0800 for IP/GRE). The 7750 SR also supports packet over SONET/SDH (POS). When services are configured over MPLS, customer traffic is encapsulated in MPLS frames and sent over MPLS tunnels. A service label, or VC label, that indicates a specific customer connection, such as a Frame Relay DLCI, is pushed into the label stack between the transport tunnel label and the packet data. An optional service-specific control word may be placed between the packet data and the service label. The control word is used for frame sequencing and/or carrying service-specific information, such as Frame Relay forward explicit congestion notification (FECN) and backward explicit congestion notification (BECN) information. At the tunnel-end, the service label is used to find the customer interface over which the traffic is sent. The control word, if present, is used to convert the encapsulated customer traffic into its native format. Note: do not confuse VC Label with the VC ID that is used for service provisioning.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 24. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. MPLS encapsulation of VPN service traffic.

(43) Transport and Service Label Encapsulation (continued). . IP header and the GRE header are used instead of the MPLS transport label. . A service label is still required to demultiplex the packet to the appropriate service. . The service provider routers use the GRE header to route the packet across the network. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 25. All rights reserved © 2012 Alcatel-Lucent. Services over GRE When GRE is used to transport services, an MPLS transport label is not used. Instead, an IP header is used, where the source IP address is the local PE router and the destination IP address is the far-end PE router. The minimum GRE header consists of 4 bytes: 2 for the flags, and 2 are used as protocol type files (contains the protocol ID of the payload packet). The MPLS protocol ID, which identifies the MPLS service label, is 0x8847. It is important to note that in this case, even though GRE is used for transport, an MPLS service label still exists so that the far-end PE can de-multiplex the service correctly. Therefore, unlike with MPLS transport labels, there is no label swapping at each router in the service provider’s network. Rather, the outer IP header is used to forward the packet through the service provider network; as such, the IP header is not swapped at each router. The GRE IP header is stripped at the far-end provider edge router, which then uses the service label to demultiplex the service. At this point, the service label is stripped before the frame is passed to the customer. The main application of GRE would be in the case that a service provider has transport routerss (P routers) that are not MPLS-capable. In this case, GRE could be used to encapsulate the frame and only MPLS would be required on the service endpoint routers (PE routers). In general, if MPLS-capable routers are available, the MPLS will be utilized for the transport tunnel.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 25. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. GRE encapsulation of VPN service traffic.

(44) MPLS Transport and Service Label Signaling  MPLS transport tunnel signaling protocols:  LDP or RSVP-TE are used to set up LSPs  Provide a means to set up label-switched paths, also known as LSPs, that can carry many other service tunnels.  Service labels, or VC labels, are used to encapsulate and identify customer traffic that belongs to a particular service  A service label is applied to the customer traffic before the transport label, or LSP label, is applied  VPLS and VPWS services are signaled using targeted LDP, also known as T-LDP  VRPN service is signaled by MP-BGP, based on RFC 4364 (formerly RFC 2547bis) Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 26. All rights reserved © 2012 Alcatel-Lucent. Signaling protocols use LDP and/or RSVP-TE to set up LSPs, which can then be used for various service tunnels. Service labels are used to encapsulate and identify customer traffic belonging to a particular service. This label is applied to the customer traffic before the transport label is applied. Service labels for VPLS and VPWS services are signaled using T-LDP. T-LDP is the same protocol as link LDP used for signaling transport labels with a few additional capabilities added. Sessions are LDP sessions between non-directly connected peers. When a service distribution point (SDP) is configured (SDP will be explained in the next section), automatic ingress and egress labeling is enabled by default, and ingress and egress service labels are signaled over a T-LDP connection. If signaling is turned off on an SDP, ingress and egress service labels must be manually configured when the SDP is bound to a service. In a VPRN service, MP-BGP is used to exchange customer routes across the VPRN. The BGP updates also include a label for these routes. Signaling is required between the PE routers in order to provide the necessary connectivity information throughout the VPN. Two approaches exist to provide this end-to-end signaling information. One approach is known as Martini Signaling and uses LDP, while the second approach is known as Kompella Signaling and uses BGP. The Draft-Martini uses T-LDP between the PE routers to distribute VC labels. This mechanism contains information such as the unique VC ID, the specific interface parameters and the VC Type, such as ATM, Frame Relay and Ethernet. The PE routers use this information to build the forwarding tables and set up the VC LSPs. The Draft-Kompella approach makes use of BGP between the PE routers to advertise route distinguishers and route targets. This enables the receiving PE to determine if the incoming BGP update is relevant for its VPN clients. If so, the receiving PE accepts the update and populates the forwarding tables accordingly. Currently the Martini approach is more commonly used than the Kompella Draft for signaling purposes. Martini draft was standardized under RFC 4096. Draft-Kompella is obsolete and was not standardized.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 26. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  Service tunnel signaling protocols:.

(45) TLDP/MP‐BGP. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 27. All rights reserved © 2012 Alcatel-Lucent. The physical topology of the base is made up of four routers set up in series-form. The routers presented in this slide are two PE routers, representing the edge of the service provider network, and two P routers, representing the service provider core. The service provider makes use of an IGP to propagate routing knowledge for PE-PE connectivity. Either LDP or RSVP-TE is used for label propagation. Once each router has advertised its label knowledge to the neighboring routers, a complete LSP will have been created. Targeted (targeted) LDP or MP-BGP is then used to establish an end-to-end connection-oriented session, providing the inner label. The inner label is used for service tunnel signaling. Once we have signaled service labels and created a transport tunnel between the two PE endpoints, we have created a service. The difference between link LDP and T-LDP is that T-LDP is used for exchanging service label information and the T-LDP peers do not need to be directly connected. Because they may not be directly connected, a router must know the IP address of its T-LDP peer. It then sends its Hello messages to its peer’s unicast address instead of the multicast address. Otherwise the process for establishing adjacencies and the messages exchanged are the same as for link LDP. LDP must be enabled to configure VPWS or VPLS services so that T-LDP can signal the service labels, even if RSVP-TE is used for signaling the transport labels.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 27. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. MPLS Transport and Service Label Signaling (continued).

(46) MPLS Transport and Service Label Signaling (continued) . The exchange of service labels occurs when the pseudowire is created. . The following outlines the service label signaling process: 1. PE2 sends PE1 a service label (11350) 2. PE1 sends PE2 a service label (21350) 3. Unidirectional service tunnels are created 4. PE1 uses the label (11350) to send traffic towards PE2. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 28. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. 5. Likewise, PE2 uses label (21350) to send traffic towards PE1. All rights reserved © 2012 Alcatel-Lucent. The exchange of service labels occurs when the service is created.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 28.

(47) Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 29. All rights reserved © 2012 Alcatel-Lucent. The core LSRs use information from the top label when switching the labeled frame across the MPLS domain. It is possible that during this process, additional labels can be also be pushed along the way. The egress LER infers from the VC label how to process the frame and then forwards it to the appropriate outgoing port; however, the VC label is not visible until the frame reaches the egress LER due to the MPLS tunneling hierarchy. This slide shows the order of events that occur when signaling transport and service labels for a service and then subsequently forwarding a packet. The control plane is right to left, while the data plane is left to right (the traffic is sent from PE1 to PE2). It is important to note that the control and data planes are always in opposite directions. For the purpose of this discussion it is assumed that IGP convergence has already occurred.  LDP is enabled, which creates the outer service tunnel label. It should be noted that RSVP could also have been used in this case. PE1 receives LDP label 217 from P1 and, therefore, uses label 217 as the label representing the LSP to PE2  T-LDP or MP-BGP is enabled, which creates an end-to-end connection-oriented session between PE1 and PE2, and propagates the service label  A data packet arrives at PE1 and is encapsulated with both the outer label, learned through LDP, as well as the service label, learned through T-LDP or MP-BGP  As the data packet traverses the P routers, the outer label is swapped while the inner label remains unchanged  Upon receiving the data packet, the receiving PE, in this case PE2, removes the outer LDP label. Then, prior to removing the inner label, the receiving PE maps it to the appropriate service.  The result is the original data packet, which is then forwarded to correct interface for the service, and then on to the CE (not shown).. Note: the control plane / dataplane would be in the opposite direction for sending traffic from PE2 to PE1 Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 29. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. MPLS Transport and Service Label Signaling (continued).

(48) Services Overview & Implementation. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Section 3 ― Service Components. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 30.

(49) Section Objectives After successfully completing this section, you will be able to:  Describe the main components required to configure Alcatel-Lucent services (SAP, service ID, VC-ID, SDP)  Explain the concept of SAP and encapsulation identifier. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  Describe the operation of a local service  Configure and verify a local service  Describe the operation of a distributed service  Define a service distribution point (SDP) and list its characteristics  Configure and verify a distributed service. Alcatel-Lucent Services Architecture v 3.2. Alcatel-Lucent Services Architecture v3.2. Module 1 |. 31. All rights reserved © 2012 Alcatel-Lucent. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 31.

(50) Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 32. All rights reserved © 2012 Alcatel-Lucent. The Alcatel-Lucent router is based on the service model where service edge routers are deployed at the provider edge. Services are provisioned on the router and transported across an IP and/or IP/MPLS provider core network in encapsulation tunnels, created using GRE or MPLS LSPs. The service model uses logical service entities to construct a service. The logical service entities are designed to provide a uniform, service-centric configuration, management and billing model for service provisioning. The service model is based on the following components: . Subscriber - describes the user of the service. . Service access point (SAP) - The subscriber’s point of interface to the service network. . Customer ID - A value associated with the service that can be used to group together a number of services for reporting purposes. . Service ID - The numeric value used on the 7750 SR to identify the service. . Service Type – The type of the service that is configured on the 7750 SR (VPWS, VPLS, VPRN, IES). . VC ID - Identifies the service when signaling the service labels. This value must match at both ends of the service. The VC ID is usually the same as the service ID. . Service distribution point (SDP) - A logical representation of the transport tunnel that will be used to deliver the service data to the egress PE. . Transport tunnel - This is the LSP used to transport the service data, typically signaled with RSVP-TE or LDP. An SDP is associated with the transport tunnel. . Service tunnel - This is the tunnel represented by the service labels signaled end-to-end by the two PEs that are the service endpoints. . Demultiplexer - Represents the operation of delivering the data arriving at the egress router to the appropriate service based on the service label. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 32. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Service Components.

(51) . The terms ‘customers’ and ‘subscribers’ are used synonymously here. . The customer ID is assigned when the customer account is created. . To provision a service, a customer ID must be associated with the service at the time of service creation. . Multiple services can be associated with one customer. . The customer ID for the service cannot be changed once the service is created. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 33. All rights reserved © 2012 Alcatel-Lucent. Once a service has been created with a customer association, it is not possible to edit the customer association; the service must be deleted and recreated with a new customer association. Once a service is created, the use of the customer ID is optional for navigating into the service configuration context. Attempting to edit a service with the incorrect customer ID specified will result in an error. The customer must be created before the service is created. The customer ID for the service cannot be changed once the service is created. Although it is recommended that a globally consistent value be used for the customer ID, it is never signaled to other PEs and has no effect on the service.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 33. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Customers and Subscribers.

(52) Customer Creation. *A:PE-1# configure service customer 100 create *A:PE-1>config>service>cust$ description "VPWS_Customer" *A:PE-1>config>service>cust$ phone "1-111-111-1111" *A:PE-1>config>service>cust$ exit. *A:PE-1# show service customer =============================================================================== =============================================================================== Customer-ID. : 1. Contact. : (Not Specified). Description. : Default customer. Phone. : (Not Specified). Customer-ID. : 100. Contact. : (Not Specified). Description. : VPWS_Customer. Phone. : 1-111-111-1111. ------------------------------------------------------------------------------Total Customers : 2. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 34. All rights reserved © 2012 Alcatel-Lucent. When using the CLI to configure services, a customer ID of 1 is used by default, but it is good practice to configure specific customer IDs. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 34. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Customers.

(53) Service Identifiers  Service ID - The numeric value used on the 7750 SR to identify the service  A service is associated with a customer ID. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 35. All rights reserved © 2012 Alcatel-Lucent. Service The Alcatel-Lucent 7750 service router is a service-based router. All functionality revolves around the concept of a service, where a service is a unique entity that refers to the type of connectivity for either Internet (Layer 3), or VPN (Layer 2 or Layer 3) connectivity. A service is considered to be any of the following:  VPWS, including apipe, epipe and fpipe  VPLS  VPRN  IES  Mirroring, which is used for management and troubleshooting A service can be either a local service, in which case it must be defined and associated with two local SAPs; or it can be distributed, in which case it must be defined and associated with a SAP and an SDP. Local and distributed service will be explained in more details in the following slides.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 35. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  A service must be created using a unique service ID on that router.

(54) Service Creation. *A:PE-1# configure service epipe 50 customer 100 create. *A:PE-1# show service id 50 base =============================================================================== Service Basic Information =============================================================================== Service Id : 50 Vpn Id : 0 Service Type : Epipe Name : (Not Specified) Description : (Not Specified) Customer Id : 100 Last Status Change: 01/30/2012 16:55:09 Last Mgmt Change : 01/31/2012 11:48:48 Admin State : Up Oper State : Down MTU : 1514 Vc Switching : False SAP Count : 0 SDP Bind Count : 0 Per Svc Hashing : Disabled Force QTag Fwd : Disabled ------------------------------------------------------------------------------Service Access & Destination Points ------------------------------------------------------------------------------Identifier Type AdmMTU OprMTU Adm Opr ------------------------------------------------------------------------------No Matching Entries. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 36. All rights reserved © 2012 Alcatel-Lucent. The slide shows the creating of an epipe service. The service is operationally down because it is not completely configured. Service ID identifies the service on the local router. A service must be created using a unique service ID. Once a value is used for one service it cannot be used for another on that router. Note: the vpn id is used to specify the VPN ID number, allowing you to identify virtual private networks (VPNs) by a VPN ID. If this parameter is not specified, the VPN ID uses the same service ID number. Values 1 — 2147483647 Default null (0). Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 36. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. *A:PE-1>config>service>epipe$ no shutdown.

(55) Service Access Point (SAP)  A SAP is the subscriber’s point of interface to the service network  A SAP is specified as a physical port and an encapsulation identifier. SAP 1/2/3. Alcatel-Lucent Services Architecture v 3.2. Service. Module 1 |. 37. All rights reserved © 2012 Alcatel-Lucent. Service Access Point (SAP) A SAP is a logical entity that serves as the customer’s point of access into a service. Each subscriber service is configured with at least one SAP. A SAP can only be configured on a port that has been configured specifically as an ‘access’ port. The default configuration for a port is ‘network,’ which means that you may need to reconfigure a port before you can configure a SAP onto it. SAPs for IES and VPRN services are configured on IP interfaces. A SAP is the subscriber-side entry and exit point for a service.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 37. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  To be used as a SAP, a port must be configured as an access port.

(56) SAP Configuration Considerations  A SAP ID is locally unique — the same SAP ID value can be used on another service router  A SAP is associated with a single service and can only be configured on an access port  A port or channel can have more than one SAP configured on it. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  All SAPs must be explicitly created and are administratively enabled at the time of creation — there are no default SAPs  VLAN IDs have local port significance  A SAP can be configured with any of the following:  Ingress and egress filter policy  Ingress and egress QoS policy  Ingress and egress scheduler policy  Accounting policy. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 38. All rights reserved © 2012 Alcatel-Lucent. VLAN ID is the encapsulation ID that is used to distinguish services.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 38.

(57) SAP ID  A SAP is a local entity to the service router and is uniquely identified by the following:  The physical Ethernet port or SONET/SDH or TDM port and channel.  Depending on the encapsulation, a physical port or channel can have more than one SAP associated with it  SAPs can only be created on ports or channels designated as “access” in the physical port configuration  SAPs cannot be created on ports designated as core-facing “network” ports. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 39. All rights reserved © 2012 Alcatel-Lucent. SAP Encapsulation Types and Identifiers A SAP is local to the router and is uniquely identified by the following:  Physical Ethernet port or packet-over-SONET/SDH (POS) port and channel  Encapsulation identifier (ID). The encapsulation identifier depends on the type of port used as the SAP. For example, if the SAP is an Ethernet port, the encapsulation identifier can be a VLAN tag or a Q-in-Q tag. The encapsulation identifier may be null in which case the SAP is simply the port. The encapsulation type is an access property of a service Ethernet port or SONET/SDH or TDM channel. The appropriate encapsulation type for the port or channel depends on whether it is required to support multiple services on a single port/channel on the associated SAP, and the capabilities of the downstream equipment connected to the port/channel. For example, a port can be tagged with IEEE 802.1Q encapsulation, referred to as dot1Q encapsulation, in which each individual tag can be identified with a service. A SAP is created on a given port or channel by identifying the service with a specific encapsulation ID. Depending on the encapsulation used, a physical port or POS channel can have more than one SAP associated with it. Using dot1Q encapsulation or POS channels, the router can support either multiple services for one customer, or one service for multiple customers. SAPs cannot be created on ports designated as core-facing network ports bacause these ports have a different set of features enabled in software.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 39. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  The encapsulation identifier (ID).

(58) Ethernet Encapsulations  Null — supports a single service on the port  Dot1Q — supports multiple services for one customer or multiple services for multiple customers.  Ethernet port encapsulation can be set using the following command: config>port>ethernet encap-type where encap-type: dot1q|null|qinq. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 40. All rights reserved © 2012 Alcatel-Lucent. Null — supports a single service on the port; for example, where a single customer with a single service customer edge (CE) device is attached to the port, the encapsulation ID is always zero. For example: sap 1/1/3 Dot1Q — supports multiple services for one customer or multiple services for multiple customers. . For example: the port is connected to a multi-tenant unit (MTU) device with multiple downstream customers.. . The encapsulation ID used to distinguish an individual service is the VLAN ID in the IEEE 802.1Q header. For example: sap 1/1/3:50. Q-in-Q — The Q-in-Q encapsulation type adds an IEEE 802.1Q tag to the 802.1Q-tagged packets entering the network in order to expand the VLAN space by tagging tagged packets. For example: sap 1/1/3:10:100 On SONET ports the following encapsulation types are supported: Internet Protocol Control Protocol (IPCP) . IPCP supports a single IP service on SONET/SDH for each port or for each channel.. . This is typically used for router interconnection that uses point-to-point protocol (PPP).. Bridging Control Protocol (BCP-null) . . BCP-null supports a single service. •. SONET/SDH port. •. SONET/SDH port for each channel — if the interface is channelized.. BCP-null is used for bridging a single service between two devices using PPP over SONET/SDH. The encapsulation ID is always zero.. Bridging Control Protocol (BCP-Dot1Q) . BCP-Dot1Q supports multiple services on the SONET/SDH port or channel.. . BCP-Dot1Q is used for bridging multiple services between two devices using PPP over SONET/SDH.. . The encapsulation ID that is used to distinguish services is the VLAN ID in the IEEE 802.1Q header found in the BCP-encapsulated frame.. SONET port encapsulation can be configured from the following menu: config>port# sonet-sdh path encap-type {atm|bcp-null|bcp-dot1q|ipcp|ppp-auto|frame-relay|wan-mirror|cisco-hdlc Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 40. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute.  Q-in-Q — The Q-in-Q encapsulation type adds an IEEE 802.1Q tag to the 802.1Q-tagged packets entering the network to expand the VLAN space by tagging tagged packets. This produces a double-tagged frame.

(59) SAP Configuration. *A:PE-1# show port =============================================================================== Ports on Slot 1 =============================================================================== Port Admin Link Port Cfg Oper LAG/ Port Port Port SFP/XFP/ Id State State MTU MTU Bndl Mode Encp Type MDIMDX ------------------------------------------------------------------------------1/1/1 Up Yes Up 1578 1578 - netw null gige 1/1/2 Down No Down 1578 1578 - netw null gige 1/1/3 Up Yes Up 1518 1518 - accs dotq gige 1/1/4 Down No Down 1578 1578 - netw null gige 1/1/5 Down No Down 1578 1578 - netw null gige 1/1/6 Down No Down 1578 1578 - netw null gige 1/1/7 Down No Down 1578 1578 - netw null gige 1/1/8 Down No Down 1578 1578 - netw null gige 1/1/9 Down No Down 1578 1578 - netw null gige 1/1/10 Down No Down 1578 1578 - netw null gige ===============================================================================. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 41. All rights reserved © 2012 Alcatel-Lucent. To be used as a SAP, a port must be configured as an access port. Ports are configured as network ports by default. Note: when the ports are configured as Ethernet access ports with dot1q encapsulation, they are automatically changed to an MTU (maximum transmission unit) of 1518. This defines the maximum size of frame that will be accepted for a service using this port as a SAP. By default the 7750 SR configures an Ethernet access port to accept a standard-sized Ethernet frame. Since this port is configured for dot1q encapsulation, the MTU is 1518. MTU consideration will be explained in detail in Module 2. Many other encapsulation types are possible. These depend on the MDA type of the port and the type of service being provisioned. SAP encapsulations are described in more detail in Module 2.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 41. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. *A:PE-1# configure port 1/1/3 *A:PE-1>config>port# shutdown *A:PE-1>config>port# ethernet *A:PE-1>config>port>ethernet# mode access *A:PE-1>config>port>ethernet# encap-type dot1q *A:PE-1>config>port>ethernet# exit *A:PE-1>config>port# no shutdown *A:PE-1>config>port# exit.

(60) Local Service. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 42. All rights reserved © 2012 Alcatel-Lucent. A service can be either local or distributed. A local service involves two SAPs and provides a connection path between two sites. A local service provides a point-to-point logical connection from the customer’s perspective.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 42. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. In a local service, all components of the service are on a single router..

(61) Local Service Configuration Local epipe service configuration on a single router:. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 43. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. *A:PE-1# configure service epipe 50 customer 100 create *A:PE-1>config>service>epipe# sap 1/1/1 create *A:PE-1>config>service>epipe>sap$ exit *A:PE-1>config>service>epipe# sap 1/1/2 create *A:PE-1>config>service>epipe>sap$ exit. All rights reserved © 2012 Alcatel-Lucent. Note: the CE routers are configured with IP interfaces as shown below: *A:CE-1# configure port 1/1/1 no shutdown *A:CE-1# configure router interface "toCE2" *A:CE-1>config>router>if# port 1/1/1 *A:CE-1>config>router>if# address 192.168.1.1/24 *A:CE-1>config>router>if# show router interface. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 43.

(62) *A:PE-1>config>service>epipe# show service id 50 base =============================================================================== Service Basic Information =============================================================================== Service Id : 50 Vpn Id : 0 Service Type : Epipe Name : (Not Specified) Description : (Not Specified) Customer Id : 100 Last Status Change: 01/30/2012 16:55:09 Last Mgmt Change : 01/31/2012 15:15:21 Admin State : Up Oper State : Up MTU : 1514 Vc Switching : False SAP Count : 2 SDP Bind Count : 0 Per Svc Hashing : Disabled Force QTag Fwd : Disabled ------------------------------------------------------------------------------Service Access & Destination Points ------------------------------------------------------------------------------Identifier Type AdmMTU OprMTU Adm Opr ------------------------------------------------------------------------------sap:1/1/1 q-tag 1514 1514 Up Up sap:1/1/2 q-tag 1514 1514 Up Up ===============================================================================. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 44. All rights reserved © 2012 Alcatel-Lucent. As shown in the slide, the epipe service is up and the CE routers should be able to reach each other over the Ethernet connection, as shown in the ping test below: *A:CE-1> ping 192.168.1.2 count 1 PING 192.168.1.2 56 data bytes 64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=4.45ms.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 44. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Local Service Verification.

(63) . A distributed service has components on multiple routers and uses the IP/MPLS network to connect the service and deliver data. . SDP binding is required to signal the service labels and define the transport to the remote router. Alcatel-Lucent Services Architecture v 3.2. Module 1 |. 45. All rights reserved © 2012 Alcatel-Lucent. A distributed service has components on multiple routers and uses the IP/MPLS network to connect the service and deliver data. Distributed service spans more than one router. It uses SDPs to direct traffic to another router; traffic is transported by a transport tunnel through a service tunnel.. Alcatel-Lucent Services Architecture v3.2. All rights reserved © 2012 Alcatel-Lucent. Module 1 – Page 45. Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute. Distributed Service.

No results found