DOCSLIB.ORG

SSR System Description

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
SSR System Description SSR System Description DESCRIPTION 1/221 02-CRA 119 1364/1-V2 Uen D Copyright © Ericsson AB 2011–2013. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner. Disclaimer The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document. Trademark List NetOp NetOp is a trademark of Telefonaktiebolaget LM Ericsson. 1/221 02-CRA 119 1364/1-V2 Uen D | 2013-03-25 Contents Contents 1 Overview 1 1.1 Scope 1 1.2 Audience 2 2 Introduction 2 3 SSR Use Cases 3 3.1 Layer 2 Solutions 3 3.2 Layer 3 Solutions 4 3.3 BNG Solutions 7 3.4 SSR in Other Ericsson Solutions 8 3.5 Multi-Service Edge Routing Solution 10 4 System Architecture 11 4.1 Hardware Architecture 11 4.2 Software Architecture 16 4.3 Forwarding 28 5 Features 30 5.1 Synchronous Ethernet 30 5.2 Layer 2 Features 31 5.3 Tunnels 32 5.4 Routing 33 5.5 BNG Features 38 5.6 IP Protocol Support 39 5.7 IP Services 41 5.8 SSC Services 42 5.9 Quality of Service 43 5.10 Connectivity Fault Management (CFM) 45 5.11 System Redundancy and Synchronization (High Availability) 46 6 User Interface 48 6.1 Using the SSR CLI 48 7 Administration 51 1/221 02-CRA 119 1364/1-V2 Uen D | 2013-03-25 SSR System Description 7.1 Managing Security 51 7.2 Managing Performance 54 7.3 Monitoring and Reporting Tools 55 Glossary 59 Reference List 63 1/221 02-CRA 119 1364/1-V2 Uen D | 2013-03-25 Overview 1 Overview This document describes the Ericsson SSR 8000 family and its usage, services, and architecture. 1.1 Scope This description covers the logical and functional aspects of the product, and it includes a brief overview of the hardware architecture. For more information, see the following documents: SSR 8000 Routers • Hardware Overview for the SSR 8010 • Hardware Overview for the SSR 8020 Interface Cards • 10-Port 10 Gigabit Ethernet Card (10 X 10 Gigabit Ethernet (GE) line card) • 40-Port Gigabit Ethernet Card (4 X 1GE line card) • 1-Port 100 Gigabit Ethernet or 2-Port 40 Gigabit Ethernet Card (1 X 100GE or 2 X 40GE line card) • 4-Port 10 Gigabit Ethernet, or 20-Port Gigabit Ethernet and 2-Port 10 Gigabit Ethernet Card (2 X 10GE or 4 X 10GE and 20 X 1GE card for Broadband Network Gateway (BNG) and Multi-service Edge Routing (MSER) services Controller Cards • RPSW (Controller) Card • ALSW (Alarm) Card • SW (Switch) Card Service Cards • Smart Services Card (SSC) Other Components • SSR 8000 Power Entry Modules • SSR 8000 Fan Trays 1/221 02-CRA 119 1364/1-V2 Uen D | 2013-03-25 1 SSR System Description 1.2 Audience This document provides an introduction to the SSR platform, including its architecture and SSR concepts, to anyone who is unfamiliar with the product. 2 Introduction The SSR combines multiple functions into a single platform that provides Layer 3 (IP) routing, Layer 2 (Ethernet) network aggregation, and BNG services, as well as advanced services for applications. The SSR provides carrier-class reliability, scalability, performance, and an optimal power footprint. It also provides a flexible and high-performance platform for Ericsson applications, such as Evolved Packet Gateway (EPG). The SSR platform supports the following functions: • Comprehensive range of interior and exterior gateway routing protocols and multicast routing. • Peering, edge aggregation, and core route reflection. • End-to-end Ethernet transport services with direct connection to the access layer of the network. • Advanced traffic management with Hierarchical Quality of Service (H-QoS) and comprehensive traffic shaping. • Direct connection to the access layer of the network, which eliminates unnecessary network layers and reduces complexity. • Support for up to 748,000 subscribers per physical device and all methods of subscriber encapsulation for Dynamic Host Configuration Protocol (DHCP) or IP access clients, including Point-to-Point Protocol (PPP) over Ethernet (PPPoE). The SSR in combination with other Ericsson products provides a complete end-to-end solution for the following: • BNG—Layer 2 and Layer 3 • EPG—Layer 3 • IP Radio Access Network (IP RAN)—Layer 3 • Mobile Backhaul (MBH)—Layer 2 and Layer 3 2 1/221 02-CRA 119 1364/1-V2 Uen D | 2013-03-25 SSR Use Cases • Mobile Packet Backbone Network (MPBN)—Layer 2 and Layer 3 For a description of these solutions, including diagrams and the configuration requirements, see Layer 2 Solutions, Layer 3 Solutions, BNG Solutions, and SSR Router in Other Ericsson Solutions. Figure 1 illustrates the possible combinations and shows how other Ericsson solutions fit with the SSR platform. Figure 1 Possible Service Combinations 3 SSR Use Cases 3.1 Layer 2 Solutions You can use the SSR platform to provide services for Ethernet traffic. For example: • Layer 2 Virtual Private Networks (L2VPNs) based on Virtual Private Wire Service (VPWS)—Provides end-to-end Layer 2 cross-connected circuits over IP/Multiprotocol Label Switching (MPLS) core networks • Ethernet to Ethernet Layer 2 cross-connects (XCs) 1/221 02-CRA 119 1364/1-V2 Uen D | 2013-03-25 3 SSR System Description • XC VPWS-based transport, including tagged and untagged frames as part of the VPWS (does not support medium access control (MAC) learning) • Link aggregation groups (LAGs) provide increased bandwidth and availability. The SSR supports up to 800 802.1AX link groups, with 8 ports per link group. • Multichassis LAGs (MC-LAGs) provide node-level redundancy on top of the link-level redundancy provided by a regular link group. In an MC-LAG configuration, identical link groups are configured on separate nodes. The Ericsson SSR platform supports two nodes, and therefore two link groups, in an MC-LAG cluster. • Mirror policies allow an operator to create a copy of all the traffic entering or leaving a specified physical port to troubleshoot network problems. Figure 2 illustrates the SSR 8000 in a Layer 2 network. Figure 2 SSR in a Layer 2 Network Table 1 lists the features that you can configure for Layer 2 solutions. Table 1 Layer 2 Solution Features Business Application Layer 2 Transport Routing and Label Distribution Services Method Options L2VPN (Business VPN) L2VPN VPWS LDP or RSVP VPN pseudowire VPWS IS-IS or OSPF QoS Propagation L2VPN (Business VPN) Layer 2 XC Ethernet-to-Ethernet Local XC QoS Propagation XC 3.2 Layer 3 Solutions The SSR can provide Layer 3 Virtual Private Network (L3VPN) services and IPv4 and IPv6 routing and transport services. 4 1/221 02-CRA 119 1364/1-V2 Uen D | 2013-03-25 SSR Use Cases 3.2.1 L3VPNs The router can provide the following Layer 3 services: • End-to-end Layer 3 connection over an IP/MPLS core network • Business VPNs, such as Border Gateway Protocol (BGP)/MPLS Layer 3 VPNs, IP Security (IPsec) VPNs, or Generic Routing Encapsulation (GRE) VPNs • Multicast routing supporting broadcast TV and video-on-demand solutions • Core routing solutions, such as P router and route reflector, in an IP/MPLS core network • BNG with Layer 3 VPN services, such as remote business VPNs and wholesale service offerings (requires at least one 4-port 10GE or 20-port Gigabit Ethernet and 2-port 10GE card) Figure 3 illustrates the router in a Layer 3 network with VPNs. Figure 3 L3VPNs Table 2 lists the features that you can configure for Layer 3 solutions. 1/221 02-CRA 119 1364/1-V2 Uen D | 2013-03-25 5 SSR System Description Table 2 Configurable Features for Layer 3 Solutions Business Circuit Options Routing Options Services Application Integrated PTA One of the following combinations: QoS BNG/L3VPN L2TP BGP, MPLS, LDP, ISIS Filter and Policy ACLs CLIPS BGP, MPLS, LDP, OSPF CE-PE Routing Options DHCP BGP, MPLS, RSVP, ISIS Route Filters Static Circuits BGP, MPLS, RSVP, OSPF BGP, MPLS, LDP over 1-hop RSVP, ISIS BGP, MPLS, LDP over 1-hop RSVP, OSPF L3VPN CLIPS Static routes or an IGP or eBPG for CE QoS to PE connectivity DHCP Filter and Policy ACLs Combinations of the following: Static circuits CE-PE Routing options BGP Route filters MPLS LDP or RSVP IS-IS or OSPF Mobile applications, Static circuits Combinations of the following: QoS such as MPBN BGP Filter and Policy ACLs MPLS LDP or RSVP IS-IS or OSPF Layer 3 PE Router Static circuits CE-PE routing options: QoS Static Filter and Policy ACLs OSPF or IS-IS Route Filters eBGP IPSec RIP GRE Core routing options: LAG or ECMP BGP Multicast MPLS LDP or RSVP IS-IS or OSPF Layer 3 P Router Not applicable Core routing options: Route Reflector BGP LAG or ECMP MPLS LDP or RSVP IS-IS or OSPF 6 1/221 02-CRA 119 1364/1-V2 Uen D | 2013-03-25 SSR Use Cases 3.3 BNG Solutions The router can provide the following BNG services: • Broadband Remote Access Server PTA: PPP Terminated Access PPP (over Ethernet) • Layer 2 Tunneling Protocol (L2TP) terminated access L2TP L2TP Access Concentrator (LAC) L2tp Network Server (LNS) L2TP Tunnel Switch (LTS) • DHCP PTA DHCP Clientless IP Service Selection (CLIPS) • Triple-Play service model Broadcast TV, video-on-demand, Voice Over IP (VoIP), high speed Internet • Dedicated Virtual LAN (VLAN) per subscriber – Service-based VLANs Figure 4 illustrates a router in a network providing BNG services.
Load more

Recommended publications
  • TR-221: Technical Specifications for MPLS in Mobile Backhaul Networks
    TECHNICAL REPORT TR-221 Technical Specifications for MPLS in Mobile Backhaul Networks Issue: 1 Amendment 2 Issue Date: September 2017 © The Broadband Forum. All rights reserved. Technical Specifications for MPLS in Mobile Backhaul Networks TR-221 Issue 1 Amendment 2 Notice The Broadband Forum is a non-profit corporation organized to create guidelines for broadband network system development and deployment. This Technical Report has been approved by members of the Forum. This Technical Report is subject to change. This Technical Report is copyrighted by the Broadband Forum, and all rights are reserved. Portions of this Technical Report may be copyrighted by Broadband Forum members. Intellectual Property Recipients of this Technical Report are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of this Technical Report, or use of any software code normatively referenced in this Technical Report, and to provide supporting documentation. Terms of Use 1. License Broadband Forum hereby grants you the right, without charge, on a perpetual, non-exclusive and worldwide basis, to utilize the Technical Report for the purpose of developing, making, having made, using, marketing, importing, offering to sell or license, and selling or licensing, and to otherwise distribute, products complying with the Technical Report, in all cases subject to the conditions set forth in this notice and any relevant patent and other intellectual property rights of third parties (which may include members of Broadband Forum). This license grant does not include the right to sublicense, modify or create derivative works based upon the Technical Report except to the extent this Technical Report includes text implementable in computer code, in which case your right under this License to create and modify derivative works is limited to modifying and creating derivative works of such code.
    [Show full text]
  • MPLS Layer-2 Vpns • MPLS Traffic Engineering • Summary
    Understanding MPLS BRKMPL - 1101 Khurram Waheed Systems Engineer #clmel Session Goals • Understand the problems MPLS is addressing • Understand major MPLS technology components • Understand typical MPLS applications • Understand benefits of deploying MPLS BRKMPL-1101 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public Agenda • Introduction • MPLS Basics • MPLS Layer-3 VPNs • MPLS Layer-2 VPNs • MPLS Traffic Engineering • Summary BRKMPL-1101 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public Introduction Why Multi-Protocol Label Switching? • SP/Carrier perspective – Reduce costs (CAPEX/OPEX); consolidate networks and maximise utilisation of resources. – Consolidated network for multiple Layer-2/3 services over same infrastructure – Support increasingly stringent SLAs (Voice + Video etc.) • Enterprise/end-user perspective – Campus/LAN – Need for network segmentation (users, applications, etc.) BRKMPL-1101 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public What is MPLS? Brief Summary • It’s all about labels … • Use the best of both worlds – Layer-2: efficient forwarding and traffic engineering – Layer-3: flexible and scalable • MPLS forwarding plane – Use of labels for forwarding Layer-2/3 data traffic – Labeled packets are switched; instead of routed • Leverage layer-2 forwarding efficiency • MPLS control/signalling plane – Use of existing IP control protocols extensions + new protocols to exchange label information • Leverage layer-3 control protocol flexibility and scalability BRKMPL-1101 © 2015 Cisco and/or its affiliates. All rights reserved. Cisco Public MPLS Basics Topics Basics of MPLS Signalling and Forwarding • MPLS Reference Architecture Service (Clients) • MPLS Labels Layer-3 VPNs Layer-2 VPNs • MPLS Signalling and Forwarding Operations Transport IP/MPLS (LDP/RSVP-TE/BGP) MPLS Forwarding BRKMPL-1101 © 2015 Cisco and/or its affiliates.
    [Show full text]
  • MPLS FAQ: Does "No Mpls Ip Propagate-Ttl" on the Ingress PE Router Also Apply to Ipv6 Packets in 6PE Or 6VPE Networks?
    MPLS FAQ: Does "no mpls ip propagate−ttl" on the ingress PE router also apply to IPv6 packets in 6PE or 6VPE networks? Document ID: 118697 Contributed by Luc De Ghein, Cisco TAC Engineer. Dec 23, 2014 Contents Introduction Does "no mpls ip propagate−ttl" on the ingress PE router also apply to IPv6 packets in 6PE or 6VPE networks? Introduction This document describes the impact of the command "mpls ip propagate−ttl" on IPv6 traffic. Does "no mpls ip propagate−ttl" on the ingress PE router also apply to IPv6 packets in 6PE or 6VPE networks? Answer: Yes, it does. This command hides the P routers from both an IPv4 and an IPv6 traceroute. Here is an IPv6 traceroute with "no mpls ip propagate−ttl" configured on the ingress Provider Edge (PE) router. CE1#trace Protocol [ip]: ipv6 Target IPv6 address: 2001:10:100:1::7 Source address: 2001:10:100:1::5 Insert source routing header? [no]: Numeric display? [no]: Timeout in seconds [3]: Probe count [3]: Minimum Time to Live [1]: Maximum Time to Live [30]: Priority [0]: Port Number [0]: Type escape sequence to abort. Tracing the route to 2001:10:100:1::7 1 2001:10:1:5::1 1 msec 1 msec 1 msec 2 2001:10:1:7::2 [AS 1] [MPLS: Label 23 Exp 0] 2 msec 1 msec 1 msec 3 2001:10:1:7::7 [AS 1] 2 msec 1 msec 2 msec The P routers are not present in the output of the traceroute. This proves that the propagation of Time To Live (TTL) from the IPv6 header to the Multiprotocol Label Switching (MPLS) header does not occur on the ingress PE router for IPv6 packets.
    [Show full text]
  • Copyrighted Material
    Index addresses Numbers & Symbols duplicate address detection, 89 ::/0 unicast address, 81 link-local, 285 ::1/28 unicast address, 81 addressing ::/128 unicast address, 81 classful addressing, 59 10 Gigabit Ethernet, 29 classless addressing, 59–60 10/100Base Ethernet, 29 Ethernet, 25–26 5620 SAM (Service Aware Manager), 7, 14 IPv6 7210 SAS (Service Access Switch), 12–13 anycast addresses, 80, 83–84 7450 ESS (Ethernet Service Switch), 11–12 multicast, 79, 82–83 7705 SAR (Service Aggregation unicast addresses, 79, 80–82 Router), 10–11 IPv4 address structure, 58–59 7750 SR (Service Router), 7, 9–10 IS-IS, 330–331 IP interface, configuration, 66–70 ND (Neighbor Discovery), 89 IS-IS behavior, 343 NSAP, 330 ports unicast addresses, 26, 58 access, 975 adjacencies network, 975 DR, 189–191 routing table, 121 IS-IS, establishing, 333–350 service components, 970 LDP peers, 535, 537 services configuration RSVP-TE Hello message, 623–629 components, 970–971 adjacency database, 124 customers, 971 administrative groups service identifiers, 971–972 CSPF algorithm and, 720–725 subscribers, 971 interfaces, 724 topologies recognized, 163 labs, 752–754 6over4 MPLS, 721 IPv6 packets and, 97–103 ring topology, 725–738 PE1 configuration, 99–100 Type 10 LSAs, 721–722 PE2 configuration, 102 administrative route tags, IS-IS, 421–428 6PE-IPv6 tunneling over MPLS, 648–656 advertising routers, 90 6VPE (IPv6 on VPN Router), 1191–1200 AFI (area format and identifier), 330 labs, 1208–1209 aggregate-prefix-match command, 587 AH (Authentication Header), 303 IPv6 header,
    [Show full text]
  • Release Notes for Cisco IOS Release 11.2(11) Software Feature Packs for Cisco 2500 Series Routers
    Doc. No. 78-4265-02 Release Notes for Cisco IOS Release 11.2(11) Software Feature Packs for Cisco 2500 Series Routers January 26, 1998 These release notes describe the Cisco Internetwork Operating System (Cisco IOS) Release 11.2(11)P feature packs for Cisco 2500 series routers. This document contains the following sections: • Platforms Supported on page 1 • What Is a Feature Pack? on page 2 • Using Cisco Feature Packs on page 2 • Loading Cisco IOS Release 11.2 Software on CiscoPro Routers on page 16 • Installation Tips on page 17 • Installing the Router Software Using a TFTP Server Application on page 18 • Related Documentation on page 22 • Cisco Connection Online on page 24 Platforms Supported The RSL supports the following Cisco 2500 series routers: • CiscoPro CPA2501, CPA2502, CPA2503, CPA2504, CPA2505, CPA2507, CPA2509, CPA2511, CPA2513, CPA2514, CPA2516, CPA2520, CPA2521, CPA2522, CPA2523, and CPA2524 • Cisco 2501, 2502, 2503, 2504, 2505, 2507, 2509, AS2509-RJ, 2510, 2511, AS2511-RJ, 2512, 2513, 2514, 2515, 2516, 2520, 2521, 2522, 2523, 2524, and 2525 Note The Cisco AS2509-RJ and AS2511-RJ only support software images for Cisco IOS Release 11.2(5)P or later. Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA Copyright © 1998 Cisco Systems, Inc. All rights reserved. 1 What Is a Feature Pack? What Is a Feature Pack? The heart of a Cisco IOS software feature pack is a CD-ROM that contains a software image and the Router Software Loader (RSL), a Windows 95 application that loads the image onto the access router or server.
    [Show full text]
  • Deliverable D6.3 White Box Evaluation
    30-10-2019 Deliverable D6.3 White Box Evaluation Deliverable 6.3 Contractual Date: 31-10-2019 Actual Date: 30-10-2019 Grant Agreement No.: 856726 Work Package WP6 Task Item: Task 1 Nature of Deliverable: R (Report) Dissemination Level: PU (Public) Lead Partner: RENATER Document ID: GN4-3-19-23B128 Authors: Xavier Jeannin (RENATER), Mauro Campanella (GARR), Frederic Loui (RENATER), Edin Salguero (RENATER), Maxime Wisslé (RENATER), Christos Argyropoulos (GRNET), Jani Myyry (FUNET), Ivana Golub (PSNC), Tomasz Szewczyk (PSNC), Damian Parniewicz (PSNC) , Bojan Jakovljevic (AMRES), Pavel Benacek (CESnet), Marco Savi (GARR), Susanne Naegele Jackson (FAU/DFN), Tim Chown (Jisc) © GÉANT Association on behalf of the GN4-3 project. The research leading to these results has received funding from the European Union’s Horizon 2020 research and innovation programme under Grant Agreement No. 856726 (GN4-3). Abstract This deliverable reviews whether new types of white box devices can be used by the research and education community and for which use cases. The ability to program the data plane thanks to a high abstract level language (P4) opens the door to new applications for research and education. Two use cases are presented here: In-band Network Telemetry and Distributed Denial of Service attack mitigation. The Router for Academia, Research and Education project (RARE) investigates also if it is possible to use open source Network Operating System (NOS). Table of Contents Executive Summary 1 1 Introduction 2 2 White Box 3 2.1 White Box for Research
    [Show full text]
  • Multiprotocol Label Switching Oneriot Yahoo Amazon Twitter Del.Icio.Us from Wikipedia, the Free Encyclopedia
    Multiprotocol Label Switching - Wikipedia, the free encyclopedia Page 1 of 8 Multiprotocol Label Switching OneRiot Yahoo Amazon Twitter del.icio.us From Wikipedia, the free encyclopedia Multiprotocol Label Switching (MPLS) is a Internet Protocol Suite mechanism in high-performance telecommunications networks which directs and carries data from one Application Layer network node to the next with the help of labels. MPLS makes it easy to create "virtual links" between BGP · DHCP · DNS · FTP · HTTP · IMAP · distant nodes. It can encapsulate packets of various IRC · LDAP · MGCP · NNTP · NTP · POP · RIP · RPC · RTP · SIP · SMTP · SNMP · network protocols. SSH · Telnet · TLS/SSL · XMPP · MPLS is a highly scalable, protocol agnostic, data- (more) carrying mechanism. In an MPLS network, data packets are assigned labels. Packet-forwarding Transport Layer decisions are made solely on the contents of this label, without the need to examine the packet itself. TCP · UDP · DCCP · SCTP · RSVP · ECN · This allows one to create end-to-end circuits across any type of transport medium, using any protocol. (more) The primary benefit is to eliminate dependence on a Internet Layer particular Data Link Layer technology, such as ATM, frame relay, SONET or Ethernet, and eliminate the IP (IPv4, IPv6) · ICMP · ICMPv6 · IGMP · need for multiple Layer 2 networks to satisfy IPsec · different types of traffic. MPLS belongs to the family of packet-switched networks. (more) MPLS operates at an OSI Model layer that is Link Layer generally considered to lie between traditional ARP/InARP · NDP · OSPF · definitions of Layer 2 (Data Link Layer) and Layer 3 Tunnels (L2TP) · PPP · Media Access (Network Layer), and thus is often referred to as a Control (Ethernet, DSL, ISDN, FDDI) · "Layer 2.5" protocol.
    [Show full text]
  • ETSI TS 102 856-1 V1.1.1 (2011-07) Technical Specification
    ETSI TS 102 856-1 V1.1.1 (2011-07) Technical Specification Satellite Earth Stations and Systems (SES); Broadband Satellite Multimedia (BSM); Multi-Protocol Label Switching (MPLS) interworking over satellite; Part 1: MPLS-based Functional Architecture 2 ETSI TS 102 856-1 V1.1.1 (2011-07) Reference DTS/SES-00306 Keywords architecture, broadband, IMS, internet, interworking, IP, MPLS, multimedia, satellite ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission.
    [Show full text]
  • The VPN Overview VPN1 6/9/03 6:00 PM Page 2 VPN1 6/9/03 6:00 PM Page 3
    VPN1 6/9/03 6:00 PM Page 1 Part 1 The VPN Overview VPN1 6/9/03 6:00 PM Page 2 VPN1 6/9/03 6:00 PM Page 3 Chapter 1 VPN-in-Brief 1.1 VPN Overview This is the information age. We no longer have to commute physically from one place to another to complete a set of tasks or to gather pieces of information. Everything can be done virtually with a mouse click on an online host. In a way, everything we do in our daily lives is related in one way or another to infor- mation access. This has made information sharing almost mandatory and indis- pensable. These days, a customer can retrieve and compare products or services information promptly online, anytime, anywhere. For competitive reasons, organizations that provide this information have to make the information readily available online. In other words, the concept of a shared infrastructure is undisputedly important. A shared infrastructure is none other than a public network. At present, the biggest public network is the Internet, which has over 100,000 routes and is still growing rapidly. As more and more companies link up their corporate network to the Inter- net, we are faced with an inevitable issue—information security. Sharing infor- mation on a public network also implies giving access and visibility to everyone who wants to retrieve these data. What if the person who has the accessibility and visibility to the information decides to create havoc? Some of the general threat types that are posed by malicious hackers include eavesdropping, denial of service, unauthorized access, data manipulation, masquerade, session replay, and session hijacking.
    [Show full text]
  • Ipv6 Over MPLS (Cisco 6PE)
    Application Note IPv6 over MPLS (Cisco 6PE) Introduction Provider Edge Router over There are multiple techniques available to MPLS—(Cisco 6PE) to meet all of those integrate IPv6 services over Service requirements. Providers core backbones: dedicated IPv6 Service Providers that already deploy network running over various data link MPLS, or plan to do so, can garner the layers, dual stack IPv4-IPv6 backbone, or following benefits from Cisco 6PE: leveraging of an existing MPLS backbone. • Minimal operational cost and risk These solutions [IPv6_Deploy] are – No impact on existing IPv4 and deployed on Service Providers backbones MPLS services when the amount of IPv6 traffic and the • Provider Edge routers upgrade only revenue generated are in line with the – 6PE router can be an existing PE necessary investments and the risks router or a new one dedicated to consented. IPv6 traffic Conditions are favorable for the • No impact on IPv6 customer edge introduction of native IPv6 service, from routers the edge, in a scalable way, without any – The ISP can connect to any IPv6 addressing restrictions and without Customer CE running Static, IGP putting a well-controlled IPv4 backbone in or EGP jeopardy. Backbone stability is key for Service Providers, which recently stabilized • Ready for production services their IPv4 infrastructure. – An ISP can delegate IPv6 prefixes from its own to the customers Service Providers running an MPLS/IPv4 infrastructure follow the same trends, as • Non-disruptive IPv6 introduction into several integration scenarios are possible to an existing MPLS service offer IPv6 services on an MPLS network. – 6PE routers can be added at any time Cisco Systems specially developed IPv6 • Switching up to OC-192 speed is possible in the core Cisco Systems, Inc.
    [Show full text]
  • MPLS VPN Cable Enhancements
    MPLS VPN Cable Enhancements This feature module describes the Multiprotocol Label Switching Virtual Private Network (MPLS VPN) and cable interface bundling features. It explains how to create a VPN using MPLS protocol, cable interfaces, bundle interfaces and sub bundle interfaces. VPNs can be created in many ways using different protocols. • Finding Feature Information, page 1 • Hardware Compatibility Matrix for Cisco cBR Series Routers, page 2 • Feature Overview, page 2 • Prerequisites, page 7 • Configuration Tasks, page 8 • Configuration Examples, page 12 • Additional References, page 16 • Feature Information for MPLS VPN Cable Enhancements, page 17 Finding Feature Information Finding Feature Information Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://tools.cisco.com/ITDIT/CFN/. An account on http:// www.cisco.com/ is not required. Cisco Converged Broadband Routers Software Configuration Guide For DOCSIS 1 MPLS VPN Cable Enhancements Hardware Compatibility Matrix for Cisco cBR Series Routers Hardware Compatibility Matrix for Cisco cBR Series Routers
    [Show full text]
  • Introduction to MPLS DGTL-BRKMPL-1100 Travis Jones Systems Architect CCIE #4603 – DC, R&S, SP, Security, & Voice CCDE 2013::60
    #CiscoLive Introduction to MPLS DGTL-BRKMPL-1100 Travis Jones Systems Architect CCIE #4603 – DC, R&S, SP, Security, & Voice CCDE 2013::60 #CiscoLive Agenda • Introduction • MPLS Technology Basics • MPLS Layer-3 VPNs • MPLS Layer-2 VPNs • Advanced Topics • Summary #CiscoLive DGTL-BRKMPL-1100 © 2020 Cisco and/or its affiliates. All rights reserved. Cisco Public 3 Session Goals Objectives • Definition and history of MPLS • Learn about MPLS customer and market segments • Understand the problems MPLS is addressing • Understand the major MPLS technology components • Understand typical MPLS applications • Understand benefits of deploying MPLS • Learn about MPLS futures; where MPLS is going #CiscoLive DGTL-BRKMPL-1100 © 2020 Cisco and/or its affiliates. All rights reserved. Cisco Public 4 Introduction What Is MPLS? Most Painful Learn Study #CiscoLive DGTL-BRKMPL-1100 © 2020 Cisco and/or its affiliates. All rights reserved. Cisco Public 6 What Is MPLS? Most Painful Learn Study #CiscoLive DGTL-BRKMPL-1100 © 2020 Cisco and/or its affiliates. All rights reserved. Cisco Public 7 What Is MPLS? Definition Multi-Protocol: The ability to carry any Multi payload Have: IPv4, IPv6, Ethernet, ATM, FR Protocol Uses Labels to tell a node what to do Label with a packet; separates forwarding (hop by hop behavior) from routing (control plane) Routing based on IPv4 or IPv6 lookup. Switching Everything else is Switching. #CiscoLive DGTL-BRKMPL-1100 © 2020 Cisco and/or its affiliates. All rights reserved. Cisco Public 8 What is MPLS? Brief Summary • It’s all about labels … • Use the best of both worlds • Layer-2 (ATM/FR): efficient forwarding and traffic engineering • Layer-3 (IP): flexible and scalable • MPLS forwarding plane • Use of labels for forwarding Layer-2/3 data traffic • Labeled packets are being switched instead of routed • MPLS control/signaling plane • Use of existing IP control protocols extensions + new protocols to exchange label information #CiscoLive DGTL-BRKMPL-1100 © 2020 Cisco and/or its affiliates.
    [Show full text]