Network convergence ethernet applications and next generation packet transport architectures

NETWORK CONVERGENCE NETWORK CONVERGENCE Ethernet Applications and Next Generation Packet Transport Architectures VINOD JOSEPH and SRINIVAS MULUGU AMSTERDAM • BOSTON • HEIDELBERG • LONDON NEW YORK • OXFORD • PARIS • SAN DIEGO SAN FRANCISCO • SINGAPORE • SYDNEY • TOKYO Morgan Kaufmann is an imprint of Elsevier Publisher: Steve Elliot Editorial Project Manager: Kaitlin Herbert Project Manager: Malathi Samayan Designer: Mark Rogers Morgan Kaufmann is an imprint of Elsevier 225 Wyman Street, Waltham, MA 02451, USA Copyright # 2014 Elsevier Inc All rights reserved No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or any information storage and retrieval system, without permission in writing from the publisher Details on how to seek permission, further information about the Publisher’s permissions policies and our arrangements with organizations such as the Copyright Clearance Center and the Copyright Licensing Agency, can be found at our website: www.elsevier.com/permissions This book and the individual contributions contained in it are protected under copyright by the Publisher (other than as may be noted herein) Notices Knowledge and best practice in this field are constantly changing As new research and experience broaden our understanding, changes in research methods or professional practices, may become necessary Practitioners and researchers must always rely on their own experience and knowledge in evaluating and using any information or methods described herein In using such information or methods they should be mindful of their own safety and the safety of others, including parties for whom they have a professional responsibility To the fullest extent of the law, neither the Publisher nor the authors, contributors, or editors, assume any liability for any injury and/or damage to persons or property as a matter of products liability, negligence or otherwise, or from any use or operation of any methods, products, instructions, or ideas contained in the material herein Library of Congress Cataloging-in-Publication Data Joseph, Vinod Network convergence : Ethernet applications and next generation packet transport architectures / Vinod Joseph, Srinivas Mulugu pages cm Includes bibliographical references and index ISBN 978-0-12-397877-6 (pbk.) Ethernet (Local area network system) Packet transport networks Computer network architectures Convergence (Telecommunication) Internetworking (Telecommunication) I Mulugu, Srinivas II Title TK5105.383.J68 2013 004.6–dc23 2013025197 British Library Cataloguing-in-Publication Data A catalogue record for this book is available from the British Library ISBN: 978-0-12-397877-6 For information on all MK publications visit our website at http://store.elsevier.com Printed and bound in USA 14 15 16 13 12 11 10 INTRODUCTION Over the years, Ethernet has become the de facto vehicle for deploying Internet communication transport infrastructures at the access, aggregation, and even the core aspects Because of the simplicity, capacity for scalability, availability, and levels of integration that Ethernet offers across the various networking layers, it has been adopted widely across the industry The objective of the book is to highlight the convergence of new developments, applications, and services that are emerging in Ethernet transport The book discusses various applications and services that can be deployed using Ethernet as a converged infrastructure linking multiple carrier and/or enterprise infrastructures In the book we examine several services, such as MPLS Layer VPNs, Point-toPoint and Multi-Point Ethernet over MPLS PWs, and provider backbone bridging, which is an option available for scaling Ethernet layer services We then move on to look at how MPLS can be used in all Ethernet access, aggregation, and core aspects to offer services such as mobility and still retain operational scale and control We also examine MPLS-TP, a trend that is applicable in certain Ethernet access environments, before moving on to discuss how packet and optical layers can be integrated Please note that among all the graphics and figures appearing in this book, all symbols of routers and switches are purely generic to illustrate a device or concept None of them represents any actual vendor Some of the configuration templates provided are from actual vendors, such as Juniper, Cisco, and AlcatelLucent This is to provide diversity and also help the reader relate to specific topics It is by no means an endorsement of any vendors or their respective technologies Finally, this book is written by the two authors in their own capacities It has no affiliation to any organizations they are directly or indirectly involved with ix DEPLOYING ETHERNET MULTI-POINT SERVICES USING VPLS Introduction In this chapter we take a look at virtual private LAN services (VPLS) and the various building blocks of deploying multipoint Ethernet services using VPLS Virtual Private LAN Service (VPLS) Although our topic is VPLS, let us begin by taking a quick look at MPLS Layer VPNs, also referred to as point-to-point services A point-to-point L2 VPN circuit, as defined by the pseudowire encapsulation edge to edge working group (PWE3) of the Internet Engineering Task Force (IETF), is a provider service that offers a point-to-point service infrastructure over an IP/MPLS packet switched network The PWE3 working group describes mechanisms for delivering L2 VPN services across this kind of network The basic reference model is shown in Figure 1.1 A pseudowire (PW) is a connection between two provider edge (PE) devices, which connects two attachment circuits (ACs) An AC can be a Frame Relay DLCI, an ATM VPI/VCI, an Ethernet port, a VLAN, a HDLC, a PPP connection on a physical interface, a PPP session from an L2TP tunnel, an MPLS LSP, etc During the setup of a PW, the two PE routers are configured or automatically exchange information about the service to be emulated so that later they know how to process packets coming from the other end The PE routers use Targeted LDP (T-LDP) sessions for setting the PW After a PW is set up between two PE routers, frames received by one PE from an AC are encapsulated and sent over the PW to the remote PE, where native frames are re-constructed and forwarded to the other CE Chapter DEPLOYING ETHERNET MULTI-POINT SERVICES USING VPLS Figure 1.1 From a data-plane perspective, different PWs in the same packet-switched network (PSN) tunnel are identified using a multiplexing field This multiplexing field is an MPLS label, and the encapsulation of the customer frames over these (MPLS) connections or PWs is defined by the PWE3 working group PSN tunnels are implemented in the provider’s network as MPLS LSPs (RSVP, LDP), or using IP-in-IP (GRE) Figure 1.2 shows the protocol stack in the core of the provider’s network for Ethernet frames Ethernet is particularly appealing to enterprise networkers: It is mature, reliable, cheap, scalable, and well understood Common networking practice is to connect local sites (subnets, floors, or buildings of a campus) with an Ethernet backbone switch, managing and scoping the network with layer VLANs So it comes as no surprise that such network operators would like to be able to connect sites across a wider area using the same Ethernet backbones Nor is this interest new; as much as 15 years ago many local providers were offering metropolitan-area Ethernet services such as Transparent LAN Service (TLS), based on proprietary technologies, and LAN Emulation (LANE), based on ATM backbones But such service offerings were not ideal for the provider due to factors such as dependency on a single vendor, for a proprietary TLS solution, and prohibitive complexity, for a LANE solution As Ethernet technology itself advanced, permitting greater speeds at greater transmission distances, more recent metropolitan Ethernet offerings have been built around Ethernet switches But these switchbased infrastructures have their own limitations, primarily lack of scalability due to the numeric limitations on VLAN IDs In recent years, VPLS has arisen as a practical, economical, and scalable alternative for creating metro Ethernet services VPLS, in Chapter DEPLOYING ETHERNET MULTI-POINT SERVICES USING VPLS Figure 1.2 turn, has been made possible by the advent of MPLS, which has seen accelerating deployment in carrier and service provider networks beginning in the late 1990s MPLS provides a means of creating virtual circuits, similar to Frame Relay DLCIs and ATM VCI/ VPIs, over IP networks Its appeal is its ability to eliminate Frame Relay and ATM infrastructures while moving the services provided by those infrastructures to an IP network, thereby reducing the overall capital and operational costs of the network These MPLS virtual circuits—called label-switched paths (LSPs)—have for many years been used to provide Layer IPv4 VPNs and Layer point-topoint VPNs More recently, the technology has been extended to support Layer IPv6 VPNs, Layer Multicast VPNs, and VPLS The advantage of VPLS for the service provider is in building on the capital and operational cost savings of an MPLS VPN network: a Chapter DEPLOYING ETHERNET MULTI-POINT SERVICES USING VPLS common IP/MPLS infrastructure with no Ethernet switches required to support the VPLS, and a common set of standardsbased protocols to support all services, simplifying the management of the network Supplying the desired service to the customer is a simple matter of installing and configuring the correct interface While the advantages of VPLS described here benefit the service provider, from the customer’s perspective there is nothing to differentiate VPLS from any other metro Ethernet solution, beyond possibly having some of the provider’s cost savings passed along as a less expensive service However, service providers who add an inter-provider element to their VPLS offering, can differentiate themselves from competitors by providing their customers with an expanded “service footprint.” Figure 1.3 shows the VPLS reference model In Figure 1.3 an IP/MPLS backbone network (the packetswitched network, PSN) operated by a service provider offers a VPLS service to two VPN customers: an Orange customer and a Red Figure 1.3 Chapter DEPLOYING ETHERNET MULTI-POINT SERVICES USING VPLS customer Each customer has private sites that it wants to interconnect at the Ethernet layer Customer sites are connected to the SP’s backbone via attachment circuits (AC) between customer edge (CE) devices and provider edge (PE) devices As such, a VPN can be represented by a collection of CE devices In this illustration, the Orange L2VPN N consists of < CE11, CE12, CE21, CE31, CE41 > while the Red L2VPN M consists of < CE22, CE31, CE32, CE42, CE43 > As with all PE-based VPNs, with VPLS, the CE devices are unaffected by the service: a VPLS CE can be a standard router, or an Ethernet bridge or host It is the PE device that implements VPLS-specific functions Indeed, the PE device needs to implement a separate virtual forwarding instance (VFI)–also known as virtual switched instance (VSI), the equivalent of VRF tables for MPLS Layer VPNs)–for every VPLS it is attached to This VFI has physical direct interfaces to attached CE devices that belong to the VPLS, and virtual interfaces or pseudowires that are point-to-point connections to remote VFIs belonging to the same VPLS and located in other PE devices These PWs are carried from one PE to another PE via PSN tunnels From a data-plane perspective, different PWs in the same PSN tunnel are identified using a multiplexing field This multiplexing field is an MPLS label The encapsulation of the customer Ethernet frames over these MPLS connections or PWs is defined by the PWE3 working group PSN tunnels are implemented in the provider’s network as MPLS LSPs (RSVP, LDP) or using IP-in-IP (GRE) Figure 1.4 shows the protocol stack in the core of the provider’s network A Draft-Rosen MVPN represents itself as an emulated LAN Each MVPN has a logical PIM interface and will form an adjacency to every other PIM interface across PE routers within the same MVPN This is illustrated in Figure 1. Note that with VPLS, a full mesh of PSN tunnels between the network’s PE devices is assumed, and for every VPLS instance there is a full mesh of pseudowires between the VFIs belonging to that VPLS The IETF Layer VPN working group has produced two separate VPLS standards,0 documented in RFC 4761 and RFC 4762 (see Kompella and Rekhter, Jan 2007, and Lasserre and Kompella, Jan 2007) These two RFCs define almost identical approaches with respect to the VPLS data plane, but they specify significantly different approaches to implementing the VPLS control planes VPLS Control Plane The VPLS control plane has two primary functions: autodiscovery and signaling Discovery refers to the process of finding all PE routers that participate in a given VPLS instance A PE router can be Chapter DEPLOYING ETHERNET MULTI-POINT SERVICES USING VPLS Figure 1.4 configured with the identities of all the other PE routers in a given VPLS instance, or the PE router can use a protocol to discover the other PE routers The latter method is called autodiscovery After discovery occurs, each pair of PE routers in a VPLS network must be able to establish pseudowires to each other, and in the event of membership change, the PE router must be able to tear down the established pseudowires This process is known as signaling Signaling is also used to transmit certain characteristics of the pseudowire that a PE router sets up for a given VPLS BGP-VPLS Control Plane The BGP-VPLS control plane, as defined by RFC 4761, is similar to that for Layer and Layer (see Kompella, Jan 2006, and Rosen and Rekhter, Feb 2006) It defines a means for a PE router to 570 Chapter MPLS TRANSPORT PROFILE Figure 7.16 many LDP sessions In other words, it cannot realize a full-mesh LDP session At this moment, the access device can be used as TPE, and the high-performance device S-PE is used as the switching point of the LDP session Then set more PW S-PEs (switching PE) as the switching point of the LDP to converge with the bearer PW in the tunnel The multi-segment pseudowire allows multiple PWs between the source and the destination PEs The PW switching device S-PE is used to connect the single PW at both sides together and to implement the PW-layer label switching at the S-PE site Helping the user out of the scenario in which single-end PW cannot be built between the source and destination PEs, the multi-segment pseudowire technology satisfies different application requirements in cross-local network, crossoperator, and cross-control platform scenarios In addition, this technology can meet the requirements of deploying the network in a static, dynamic, or hybrid way In the peer-to-peer scenario, if the multi-segment pseudowire is used, that is, one tunnel is built in the two networks respectively, the boundary node message will first pop up tunnel labels for PW label switching, then the labels will be encapsulated to another network tunnel In this process, the IP/MPLS boundary node and the MPLS boundary node need to implement PW label switching LSP Stitching As shown in Figure 7.17, the LSP stitching means there are multiple-segment LSPs between the T-PEs Each section of LSP in the LSP stitching is an average LSP The only task is to connect the single LSP at both sides via the LSP S-PE in the LSP stitching and implement the LSP-layer label switching at the S-PE LSP stitching differs from MS-PW only in different levels The LSP stitching connects the single LSPs at both sides on the S-PE Chapter MPLS TRANSPORT PROFILE Figure 7.17 However, the MS-PW connects the single PW at both sides on the S-PE As shown in the peer-to-peer scenario, if LSP stitching is used, which means one tunnel passes through two networks at the same time, then the boundary node is used only for tunnel label switching In this method, the IP/MPLS boundary node, the MPLS boundary node, and the service X/Y should interconnect their protocols The encapsulation efficiency is great The entire process equates to an independent SS-PW process with a changing PSN tunnel Besides, the tunnel label switching is required at the two PSN network boundary nodes OAM When using MS-PW and LSP stitching in the peer-to-peer operating models of MPLS-TP and IP/MPLS, the definitions of OAM are different When using the MS-PW peer-to-peer operating model, OAM refers to: Direct-connected OAM There can be many sorts of OAM, including but not limited to the physical layer OAM and the link layer OAM mechanisms The end-to-end OAM on the LSP layer, including end-to-end LSP OAM on the MPLS-TP network and end-to-end LSP OAM on the IP/MPLS network The end-to-end OAM on the PW layer; that is, MS-PW OAM in the MPLS-TP and IP/MPLS networks When using the LSP stitching peer-to-peer operating model, OAM refers to: Direct-connected OAM There can be many sorts of OAM, including but not limited to the physical layer OAM and the link layer OAM mechanisms The end-to-end OAM on each sub-LSP layer, including the OAM on the end-to-end LSP of the MPLS-TP network and the OAM on the end-to-end LSP of the IP/MPLS network 571 572 Chapter MPLS TRANSPORT PROFILE The end-to-end OAM on the LSP layer; that is, the LSP stitching OAM crossing the MPLS-TP and IP/MPLS networks The end-to-end OAM on the PW layer The OAMs on different layers may interact with each other But the standards of the announcement from the LSP OAM to the PW OAM in the MS-PW mechanism and the announcement from the sub-LSP layer OAM to the LSP stitching OAM in the LSP stitching mechanism are still under research In the peer-to-peer model, the interaction between the MPLSTP network and the IP/MPLS network includes the following steps: Create LSP: First, build intra-segment LSP in the networks respectively If the LSP stitching mechanism is used, the administrator should stitch two LSPs (sub-LSP) at both networks to one LSP manually at the network boundary node (SPE); that is, build an LSP stitching relationship on the SPE In this way, the end-to-end LSP stitching crossing the MPLS-TP network and the IP/MPLS network can be built Create PW: If the MS-PW mechanism is used, the administrator should stitch two PWs (PW fragment) at both networks to one PW manually at the network boundary node (SPE); that is, build a PW stitching relationship on the SPE In this way, the end-to-end MS-PW crossing the MPLS-TP network and the IP/MPLS network can be built If the LSP stitching mechanism is used, the administrator can keep using this LSP stitching to build the end-to-end PW crossing the MPLS-TP network and the IP/MPLS network Besides, this PW is a single-segment PW Configure OAM and protection: Build the proper OAM and the protection relationship according to the requirements The protection in the peer-to-peer model usually keeps the regular fast route convergence mechanism and the FRR mechanism In addition, to avoid S-PE single-point failure, one PW/LSP for protection can be configured This protection PW/LSP does not pass the S-PE mentioned above Application Scenario: The Overlapping Interconnection Scenario of the L2/L3 VPN Bridging in the LTE Environment In most LTE scenarios, the access aggregation deploys the MPLS-TP and the core layer deploys the IP/MPLS The L2/L3 VPN bridging mode can be used to realize the interconnection of two networks Chapter MPLS TRANSPORT PROFILE Figure 7.18 As Figure 7.18 shows, the access layer and the aggregation layer use EVPL service to access and converge the S1 and X2 services to the core node (9008-N in the figure) Then core layer devices use the L2/L3 VPN bridging technology to map the EVPL service to one VRF entity At the same time, the L3VPN in the core layer is used to realize flexible scheduling of the S1 and X2 services to satisfy the LTE bearer requirements In the entire forwarding process, the message encapsulation format is as shown in Figure 7.19 The access convergence services are encapsulated via the L2VPN PW They are forwarded via the L3VPN Implement the L2/L3 bridging on the aggregation core boundary node 9008-N, and finish the interconnection between MPLS-TP and IP/MPLS Application Scenario: The Peer-to-Peer Interconnection Scenario in the MS-PW Environment If MS-PW is used for implementing the MPLS-TP and the IP/ MPLS network interconnection, the ZTE MS-PW mechanism includes a DHI PW 3-point bridge solution and an MS-PW 573 574 Chapter MPLS TRANSPORT PROFILE Figure 7.19 Figure 7.20 all-connection redundant protection solution It gives comprehensive support to the dynamic, static, and hybrid application scenarios As Figure 7.20 shows, the access convergence layer deploys MPLS-TP, the core layer deploys IP/MPLS, and MS-PW is used Chapter MPLS TRANSPORT PROFILE to interconnect the two networks In other words, build the corresponding PW fragment in the MPLS-TP and the IP/MPLS networks respectively Use the aggregation core boundary node 9008 as S-PE to stitch the PW fragments at both sides of the S-PW to one MS-PW In the PW fragment, the messages can only be sent according to the outer LSP label On the S-PE, the inner PW label is distributed to the next PW fragment Check the corresponding LSP information In this way, the messages are transferred by another network after implementing two-layer label switching on the S-PE In the dynamic MS-PW and redundant protection scenarios, MC-APS/MC-LAG, ICCP, and MC-PW APS protocols can be configured on the corresponding devices 575 INDEX Note: Page numbers followed by f indicate figures and t indicate tables A ABR See Area border router (ABR) Alcatel-Lucent implementation, 325 Alert-based exception mechanism, 555–556 Amplification, 544–545 Any Transport over MPLS (AToM), 482–483 Area border router (ABR), 405 ASBR 200, 118f, 119f, 120f, 121f, 129, 129f, 147–149, 149f, 150f, 151f, 168–172, 170f, 171f ASBR 300, 122f, 123f, 150–151, 151f ASBRs in AS200, 107, 117–121 in AS300, 121–123 configuration, 149, 170–172 VPNv4 routes distribution, 104–105 AToM See Any Transport over MPLS (AToM) Attenuation, 544 Autodiscovery for LDP-VPLS, 12–16 B Back-to-back VRF connections, 103–104, 172 Base station subsystem (BSS), 466–467 Base transmission station (BTS), 466–467 Bearer service attributes, 498 BGP AD configuration, 15, 26f information model, 15 BGP control plane integrated core and aggregation design, 457–458 inter-AS design, 454–457 LTE MPLS VPN service, 453 seamless MPLS transport, 452–453 BGP IPv4 table, 148, 149f, 150, 151f, 162, 166, 168–170, 170f BGP/MPLS layer 3, 12 BGP/MPLS VPN topologies full-mesh site connectivity, 85–86 hub and spoke site connectivity, 86–87 BGP MVPN routes NG-MVPN control plane, 180–186 and PE1, 275f, 277f, 284f, 296f and PE2, 276f, 279f and PE3, 276f, 280f Type and Type routes, 182–186, 184f, 185f, 186f Type and Type S-PMSI routes, 181, 181f Type autodiscovery routes, 180–181, 180f, 181f Type source active routes, 181–182, 182f BGP protocol, 13–14 BGP routes method advantages and disadvantages, 137 description, 136 inter-AS operation, 151–172 operation, 136–137 BGP-VPLS control plane, 6–9 BGP VPNv4 table, 114–115, 115f, 120, 120f, 122–123, 130, 131f, 144–145, 144f, 146, 147f, 162, 163f, 167, 167f Broadcast containment mechanism, 374 Broadcast/unknown unicast/ multicast (BUM), 354 Broadcast video/IPTV, 322–323 BSS See Base station subsystem (BSS) BTS See Base transmission station (BTS) BUM See Broadcast/unknown unicast/multicast (BUM) B-VPLS FDB management features, 371–372 C Call signaling and voice flow, 467, 467f CapEx See Capital expenses (CapEx) Capital expenses (CapEx), 474 CDMA See Code Division Multiple Access (CDMA) CEF table, 115–116, 115f, 124–125, 125f, 145, 145f, 162–164, 164f, 166, 167f CEoP See Circuit emulation over packet (CEoP) CE4’s forwarding table, 102, 102f Channel space, 527–528 Circuit emulation over packet (CEoP), 413, 487 Circuit-Switched Domain Network Protocol Stacks, 506–508 Cisco Any Transport over MPLS (AToM), 478 577 578 INDEX Cisco IP Next-Generation Network (IP NGN), 474–475 C-multicast MVPN routes, 182, 186 Code Division Multiple Access (CDMA), 466 Commands for PW binding, 19, 19f Configuration analysis, 113–126, 143–151 Converged NGN infrastructure, mobile transport, 474–475 Conversational traffic class, 515–516 “Create-new-ucast-tunnel”, 320 CSG and MTG IGP/LDP access, 442–444 multi-area IGP design and labeled BGP access, 440–442 Customer edge (CE) routers, 74, 90–91, 96–98, 100 Customer multicast routing information, 186–189, 300f, 307f, 308f D Data plane-S-PMSI setup configurations, 282 on PE1, 282–284 on PE2, 285–286 on PE3, 286–287 Dense wavelength division multiplexing (DWDM) fiberoptic transmission technique, 527 system, 527 transponders, 528–529 DiffServ QoS domain, 459–460 Digital transmission techniques, 466 Dispersion, 545 Draft-balus, PBB, 362–364 Draft-Rosen to NG-MVPNs BGP support, 301–306 broadcast video/IPTV, 322–323 forwarding plane, 299–301 infrastructure, 297–299 migration process, 295–297, 299f vendor support, 323 DWDM See Dense wavelength division multiplexing (DWDM) E Egress PE route, 94–95, 96–98, 177–178, 182f, 209f Egress PE router PE2, 219–220, 233–234, 253–260, 274f Egress PE router PE3, 220–221, 234, 260, 275f Encapsulation, 563–565, 564f Encapsulation identifier (ID), 325 End-to-end mobile transport and service architecture, 401–402 E-Pipe service, PBB encapsulation flooding considerations, 384–385 LSPs, 383 PBB-tunnel attributes, 382, 383f Ethernet networks, 526 Ethernet technologies, 362 EV-DO See Evolution data-only optimized (EV-DO) Evolution data-only optimized (EV-DO), 397 Evolution, 3G, 471 “Existing-unicast-tunnel”, 320 Extranet connectivity, MVPN, 306–313 F FA See Forwarding adjacent (FA) FAS See Frame alignment signal (FAS) FDB See Forwarding data base (FDB) FEC See Forward error correction (FEC) FEC 128 and FEC 129 configurations, 28–33 Fiber optic networks, 542–546 First Generation Mobile Network, 465 Fixed mobile convergence (FMC), 404, 484 Fixed OADM technology, 531–533 Flooding optimization, 374–375 Flooding trees, 375, 376f FMC See Fixed mobile convergence (FMC) Forward error correction (FEC), 540–541 Forwarding adjacent (FA), 563, 563f Forwarding data base (FDB), 354 Frame alignment signal (FAS), 539 Full-mesh VPLS, 25–27 Full-mesh VPN, 85–86 G G-ACh See Generic associated channel (G-ACh) 2G and 3G model, 435–436 GARP See Generic Attribute Registration Protocol (GARP) Gateway GPRS support node (GGSN), 469 Gateway MSC (G-MSC), 467 Generic associated channel (G-ACh), 556 Generic Attribute Registration Protocol (GARP), 376–377 Global System for Mobile (GSM), 466 3GPP specifications, IPv6, 491–493 3G Radio network controller (RNC), 476 3G Release 99 and Release GPRS Protocol Stacks, 503–504 3G Release 99 convergence 3GPP Release framework (R4), 480–483 INDEX IP/MPLS, 482–483 metro Ethernet, 487 packet-based Node B capabilities, 487 transport technology, 485–486, 486f 3G Release GPRS Protocol Stacks, 505–506 3G Release 99 specified RAN, 476, 477f GSM See Global System for Mobile (GSM) GSM 2.5G GPRS Protocol Stacks, 502–503 3G Traffic classes, 496–497 H Hierarchical LSPs CSG and MTG, 440–442 remote PANs and multi-area IGP design, 439–440 Hierarchical-VPLS (H-VPLS) BGP routes, 36, 41f configurations, 33–36 control and data planes, 327 hub and spoke devices, 23 layer technology, 329, 330f LDP bindings check, 36, 40f logical ports, 327, 327f and L2VPN routes, 41–43, 46f MTU, 327 redundancy, 329 scaling VPLS, 327–331 second spoke pseudowire, 329, 330f service ID, 41–43, 44f service provider domains, 328, 328f High-capacity requirements, 397, 397f High speed data packet access (HSDPA), 473 High speed packet access (HSPA), 394 HSDPA See High speed data packet access (HSDPA) HSPA See High speed packet access (HSPA) Hub and spoke VPLS configurations, 36–48 Hub and spoke VPN topology, 86–87 H-VPLS See Hierarchical-VPLS (H-VPLS) I ID See Encapsulation identifier (ID) IGP routes method advantages and disadvantages, 136 description, 131–135 operation, 135–136 IMS See IP multimedia subsystem (IMS) IMT-2000 framework envisions coverage, 470 IM-2000 Vision, 470 Inclusive tunnel P2MP LSP setup, 195–204 Ingress PE router and CE router, 90–91 forwarding, 98, 99 RSVP-TE LSP outputs, 198f Type and routes, 181f Type routes, 182f Ingress PE router–PE1, 208–218, 227–232, 244–253 “Ingress-replication”, 320–321 Instance Information, MVPN, 278f, 280f, 281f, 285f, 286f, 287f, 288f, 296f, 297f, 298f Integrated core and aggregation design LTE MPLS VPN service, 458 seamless MPLS transport, 457–458 Interactive traffic classes, 516 Inter-AS design, BGP control plane end-to-end-labeled BGP, 456–457 LTE MPLS VPN service, 455–456 seamless MPLS transport, 454–455 579 Inter-AS operation-BGP routes method advantages, 151 test setup, 153–157 VPNv4 route distribution process, 157–160 Inter-AS operation-IGP routes method description, 137 LSP forwarding, 142–143 operational examples, 138–140 VPNv4 route distribution process, 141–142 Inter-AS procedures option A, 67–68 option B, 69, 70f option C, 69, 71f Inter-domain hierarchical LSPs integrated core and aggregation design, 450–451 and inter-AS design, 444–449 multi-area IGP design, 439–444 Inter-domain interfaces (IrDI), 536 Inter-domain LSPs CSG and MTG, 446–447, 446f hierarchical LSPs, remote PANs, 444–445, 445f IGP/LDP access, 448–449, 448f International Telecommunication Union (ITU), 469 Internet Engineering Task Force (IETF), 482 Internet multicast, NG-BGP control plane behaviors, 319 description, 315 “ingress-replication”, 319–320 intra-AS AD routes, 318 IR provider tunnel, 320 “mpls-internet-multicast”, 318–319 topology, 320–321, 321f unicast tunnels, 320 VPN label, 317–318 Inter-provider VPLS, 66–69 580 INDEX Intra-domain interfaces (IaDI), 536–540 IP-based Signaling System (SS7), 482 IP/Ethernet/TDM Access, 406 IP explosion, 548 IP/MPLS access coreỵaggregation network, 427, 427f IGP domains, 427, 428f and MTGs, 429 multi-area IGP organization, 427 IP/MPLS backbone network, 4–5 IP/MPLS inter-operability models, 560–561 IP multimedia subsystem (IMS), 483–484 IPoDWDM See IP over DWDM (IPoDWDM) IP over DWDM (IPoDWDM) core network, 547–548 requirements, 546–547 traditional core architecture, 550–551 IP pool management, 469 IP radio access network (IPRAN), 474 IPV6, 3G Networks, 490–493 IrDI See Inter-domain interfaces (IrDI) ITU See International Telecommunication Union (ITU) ITU-T G.709 standard, 536 Iu Interface, Circuit-Switched Domain, 508–509 I-VPLS and B-VPLS FDB management, 369, 372f B-VPLS services, 372, 373f changes and MMRP behavior, 381–382 FDB management features, 369–371 J JUNOS, 8, 8f, 179, 193 L Label Distribution Protocol (LDP) bindings verification, 21, 22f session, 20, 21f Labeled BGP access and LDP core aggregation, 407–408, 408f access network IGP, 411–412, 411f core access and aggregation, 409–411, 410f core and aggregation, 408–409, 409f Label forwarding information base (LFIB), 116, 116f, 118–119, 118f, 120f, 122f, 123f, 126f, 127f, 146, 146f, 148, 149f, 165–166, 165f, 166f, 170, 171f Label-switched paths (LSPs) establishment, 77 forwarding, 111–113, 142–143, 160–172 inclusive tunnel P2MP, 195–204 point-to-multipoint, 193 RSVP-TE, 198f RSVP-TE-based P2MP, 222–260 RSVP-TE P2MP, 199f, 201–204, 213f, 214f L3 and L2 transport virtualization, 402–403 LDP See Label Distribution Protocol (LDP) LDP-BGP VPLS interworking BGP and LDP interworking, 57, 60f LDP- and BGP-VPLS metro domains, 52–60, 53f PE1 configuration, 54–56, 59f router PEB configuration, 54–56, 57f scaling, 48–52, 50f LDP core and aggregation, 406–407, 407f LDP-VPLS control plane, 9–10 autodiscovery, 12–16 characteristics, 22–25 implementation, 17–21 LFIB See Label forwarding information base (LFIB) Linear effects of optical transmission, 546 L2/L3 VPN bridging, 572–573, 573f Loopback distribution methods remote AS, 131 VPNv4 route distribution, route reflectors, 131 LSPs See Label-switched paths (LSPs) LTE deployments, 397–398 L2VPN AD routes, 27 L3VPN MPLS service model BGP address family, 433, 434f 3G and 4G services, 431 3G UMTS/IP and 4G LTE, 430 LTE backhaul, 432 LTE X2 interface, 432, 432f RAN access region, 433 S1-c/S1-MME interface, 430 S1-u interface, 431 M Management VPLS (M-VPLS), 330–331, 331f MCAST-VPN, 177, 182 MD5 See Message digest (MD5) Media gateway (MGW), 476 Message digest (MD5), 23 Metro networks, P Routers with M-VPLS Capability infrastructure, 343–345 L2VPN data services, 345–346 network topology, 351 OAM, 351 packet flow, 347–350, 348f, 350f redundancy, 351, 352f, 353f troubleshooting, metro network service, 351 MGW See Media gateway (MGW) INDEX Microwave infrastructure, 467 MLDP provider tunnels configurations, 267–268 definition, 260 I-PMSI and S-PMSI tunnels, 260 P2MP LSP, 260–261 RSVP-TE, 261–266 Mobile network evolution, 465 2.5G, 468–469 infrastructure, 478–479 protocol stacks, 498–508 Mobile Network RAN Access ATM encapsulation, 487–488 CEoP, 487 data traffic, 489 2G and 3G infrastructure, 487, 488f IP-based data applications, 487 MPLS, 488, 489f MToP, 487 multiple node Bs, 488 QoS parameters, 489, 490f standard broadband access types, 489 transport paths, 489 voice and signaling traffic, 488 Mobile network transport framework interface names and associated types, 510, 513t layer VPN-based transport, 509 MSC server and GMSC servers, 509–510, 511f Mobile packet core (MPC), 398–400, 399f Mobile switching center (MSC), 467 Mobile transport gateways (MTG) See CSG and MTG Mobile transport industry, 393–396, 394f MPC See Mobile packet core (MPC) “MPLS-internet-multicast”, 318–319 MPLS Layer inter-AS VPNs back-to-back VRF connections, 103–104 carrier networks, 103 definition, 103 MPLS Layer VPNs BGP/MPLS VPNs benefits, 79 community attributes, BGP, 84 generic configuration, PE1, PE2 and PE3, 90f, 91f inter-site connectivity, 88–89, 89f issues, 79–80 multiple forwarding tables, 82–84 multiprotocol extensions, BGP, 82 router’s forwarding table, 82 MPLS packet access, 405 MPLS-TP See MPLS transport profile (MPLS-TP) MPLS transport profile (MPLS-TP) and IP/MPLS inter-operability, 559–561 vs MPLS, 558–559, 558f OAM procedures, 557 protection switching and restoration, 557 static and dynamic signaling, 556–557 TDM and SONET/SDH transport, 553–554 testing, 559 MRPDU format and decoding broadcast trees, 379, 379f flooded packet, 379f, 380 group membership information, 378 PDU format, 377, 378f virtual port, 378–379 MSC See Mobile switching center (MSC) MS-PW system, 568–570, 568f MTU configuration, 23, 36f Multi-area IGP design IGP/LDP access, 417–419 labeled BGP access, 415–417 581 Multicast Forwarding Information, 277f, 279f, 281f, 287f, 289f, 298f, 299f, 300f, 304f Multicast Forwarding Table, 201f, 222f, 225f, 233f, 234f, 239f, 244f, 253f, 259f, 260f, 265f, 266f Multicast traffic, VPLS PE routers, 63, 63f selective trees, 64–65 VPLS P2MP configuration, 61, 62f Multimedia communications, 470 Multiple and mixed topologies, 398 Multiple Forwarding Tables, 82–84 Multiplexers and demultiplexers, 529 M-VPLS See Management VPLS (M-VPLS) N Network components, MPLS Layer VPNs BGP/MPLS VPN, 74, 74f customer edge (CE) routers, 74 provider edge (PE) routers, 74–75 provider (P) routers, 75 service provider network, 73–74 Network layer reachability information (NLRI), 14–15 Network management system (NMS), 554 Networks, optical, 526–527 Next Generation Multicast VPN (NG-MVPN) address family, 301–306 BGP control plane, 176, 177 control plane, 176–191 data plane–provider tunnels, 192–295 Draft-Rosen, 295–323 functions, 176 582 INDEX Next Generation Multicast VPN (NG-MVPN) (Continued) online and C-JOIN messages, 191 PIM-SM P-tunnel, 190–192, 191f Next-hop-self method, 107, 109–110, 111–112, 117 NG-MVPN See Next Generation Multicast VPN (NG-MVPN) NLRI See Network layer reachability information (NLRI) NMS See Network management system (NMS) Non-IP/MPLS access and interAS design and IGP/LDP access, 422–424, 423f and IP/MPLS access, 419–424, 419f labeled BGP access, 420–422, 420f and non-IP/MPLS access, 424–426, 425f Non-linear effects of optical transmission, 546 Optical channel transport unit (OTU), 539 Optical signal-to-noise ratio (OSNR), 545 Optical time domain reflectometer (OTDR), 543 Optical transmission, 527–528 Optical transport network (OTN), 536–542 Optimizing flooding, B-VPLS domain, 373–375, 374f OSNR See Optical signal-tonoise ratio (OSNR) OTDR See Optical time domain reflectometer (OTDR) OTN See Optical transport network (OTN) OTU See Optical channel transport unit (OTU) Overlay model encapsulation, 563–565, 564f IP/MPLS over MPLS-TP, 561–562, 562f L2/L3 VPN bridging, 566–567 MPLS-TP over IP/MPLS model, 566 OAM, 565–566 O P OADM See Optical add/drop multiplexer (OADM) OAM M-VPLS capability, P routers, 351 P routers without M-VPLS capability, 341–342 Operating expenses (OpEx), 474 Operational complexity, 395 Operational model, MPLS layer VPNs, 75–79, 84–85 Operational network models metro networks, 333–343 segmented metro networks, 332, 333f OpEx See Operating expenses (OpEx) Optical add/drop multiplexer (OADM), 529 Packet data network gateways (PGW), 431 Packet-optical transport systems (P-OTS), 525 Packet processing resources, PE, 88 Packet-Switched Domain Network Protocol Stacks, 500–502 Pass-through traffic patterns, 549–550 PBB See Provider backbone bridging (PBB) PDUs See Protocol data units (PDUs) PE2 allocation, 8, 10f Peer model MS-PW, 568–570, 569f OAM, 571–572 Peer-to-peer interconnection, 573–575 PERs configuration, 23, 31f, 37f PGW See Packet data network gateways (PGW) Physical Ethernet port, 325 PIM-SM provider tunnels configurations, 289–290 on PE1, 290–292 on PE2, 293 on PE3, 293 S-PMSI, 293–295 PIM-SSM provider tunnels configurations, 269–281 control and data planes after traffic generation, 273–276 control plane prior to traffic generation, 271–272 on PE2, 276–278 on PE3, 278–281 P2MP LSP–I-PMSI setup configurations, 205–208, 206f, 208f, 209f, 210f, 212f egress PE router PE2, 219–220, 219f, 220f, 222f, 223f egress PE router PE3, 219f, 220–221, 223f, 224f, 225f, 226f ingress PE router PE1, 208–218, 212f, 213f, 214f, 215f, 216f, 218f topology, 204, 205f P2MP LSP–S-PMSI setup advantages, 222–226 C-Source and C-Group pair, 226–227, 228f, 234–243 egress PE router PE2, 233–234, 235f, 236f, 239f, 240f, 253–260 egress PE router PE3, 234, 240f, 241f, 244f, 260 ingress PE router PE1, 227–232, 229f, 230f, 233f, 234f, 244–253 PMSI See Provider Multicast Service Interface (PMSI) P-OTS See Packet-optical transport systems (P-OTS) INDEX Power budget, 544 Protocol data units (PDUs), 469 P router forwarding, 99–100 P routers without M-VPLS capability, metro networks data traffic, 337, 337f infrastructure, 334–335, 336f loop-free topology, 341, 342f L2VPN data services, 335–337, 347f OAM, 341–342 packet flow, 337–339 redundancy, 339–341 split horizon capabilities, 339 spoke pseudowires, 335, 336f Provider backbone bridging (PBB) Alcatel-Lucent implementation, 325 Draft-balus, 362–364 E-trees, 385–388 ID, 325 IEEE 802.1ah Frame Format, 359–362 IEEE Model, 358–359 and MAC scaling issue, 354–355 and OAM, 388–389 and QoS, 390–392 service creation, 325 and service/PW aggregation, 355–357 spoke redundancy, M-VPLS, 330–331, 331f Virtual private LAN service, 353–354 Provider edge (PE) routers, 74–75 Provider Multicast Service Interface (PMSI), 178–179 Provider router configurations, 212f, 309–313, 313f Provider (P) routers, 75 Provider tunnels MVPN routing tables, JUNOS, 193, 194f NG-MVPN framework, 192, 192f point-to-multipoint LSPs, 193, 194f Pseudowires (PWE), 353–354 PSN tunnels, 5, 6f PSTN See Public-switched telephone network (PSTN) P-Tunnel Information, 218f, 223f, 226f Public-switched telephone network (PSTN), 467 PWE See Pseudowires (PWE) PWid FEC element, 30 PW-template command, 19, 20f Q QOS See Quality of service (QOS) QoS concept and architecture control mechanisms, 493 core network bearer service, 496 end-to-end service, 495 3G network infrastructure, 493 network architecture, 494 radio access bearer service, 496 RAN access bearer service, 496 UMTS bearer service, 495–496 QoS framework alternative models, 517–518 classification guidelines, 512, 514f 3GPP classification, 523 3G Release 5, mapping, 520–523, 523t GSMA PRD IR.34 recommendations, 514–515 Iu-PS user plane interface, 523 mapping, 2.5G and 3G Release 9, 518–519, 520t mapping, 3G Release 4, 519–520, 521t mobile network equipment, 512 traffic management, mobile, 515–517 583 QoS policy enforcement, 460–461 Quality of service (QOS), 458–461 R RAN access layer, 478–479 RAN backhaul, 395–396 3rd Generation Partnership Project (3GPP) evolution of CMDA, 469–470 3GPP2, 469–470 GSM, 471–473 mobile networks, 473 reference architecture, 3G Release 99, 476, 477f UMTS evolution, 469–470 RDs See Route distinguishers (RDs) Receiver PE at VPN-RED, 311f, 312f Receiver sensitivity, 543–544 Reconfigurable OADM (ROADM), 533–535 Redistribute connected subnets method, 107, 110–111, 112–113, 121 Reference model for GSM 2G, 466, 466f of VPLS, 4, 22–25 Reflectors (RR), 428–429 Resource Reservation Protocol (RSVP), 77 RFC 5586, 555 RFC 5654, 555 RFC 2547bis, 73, 76, 79–80, 82, 84 RFC-3107 hierarchical-labeled BGP LSPs, 403–404 RNC See 3G Radio network controller (RNC) ROADM See Reconfigurable OADM (ROADM) Route distinguishers (RDs), 81, 103 Router configuration, PE MPLS provider, 228f and PE1, 206f, 245f, 247f, 272f and PE2, 209f, 274f 584 INDEX Router configuration, PE (Continued) and PE3, 210f, 275f provider, 309–313, 313f, 314f, 316f VPNs, 309 Route reflector RR-200 BGP IPv4 table, 166, 166f BGP VPNv4 table, 146, 147f, 167, 167f, 168f CEF table, 166, 167f configuration, 167–168, 169f OSPF and BGP configuration, 146–147, 148f Router PE-200 BGP VPNv4 table, 114–115, 144–145 CEF table, 115–116, 145 exporting routes, 116–117 routing table, 145–146 VRF configuration, 146 Router PE-300 CEF table, 124–125 IGP routing table, 124 label forwarding information base, 126 Router PE-200 VPN BGP IPv4 table, 162, 163f BGP VPNv4 table, 162, 163f CEF table, 162–164, 164f routing table, 164–165, 164f Router-terminated IP traffic, 548–549 Routing Information BGP MVPN, 275f, 276f, 277f, 279f, 280f, 284f, 296f customer multicast, 186–189 Multicast, 300f, 307f, 308f Routing table ASBR-A300, 121, 122f PE-300, 124, 125f router PE-200, 145–146, 145f router PE-200 VPN, 164–165, 164f RR See Reflectors (RR) RSVP See Resource Reservation Protocol (RSVP) RSVP-TE-based P2MP LSP–IPMSI setup, 204–221 RSVP-TE-based P2MP LSP–SPMSI setup, 222–260 RSVP-TE P2MP LSPs, 193–195, 199f, 201–204 RSVP-TE provider tunnels functions, 193 inclusive tunnel P2MP LSP setup, 195–204 P2MP LSPs, 193–195 S Scaling packet (SP), 393 SDP See Service distribution path (SDP) Second generation mobile network, 465–467 SEF See Service exchange framework (SEF) Service architecture, 430–439 Service distribution path (SDP), 18 Service exchange framework (SEF), 475 Service level agreements (SLAs), 553–554 Service provider network, 325 Service/PW aggregation, 355–357 Signal direction, 528 SLAs See Service level agreements (SLAs) SONET/SDH transport, 553–554 Source CE router, 98 SP See Scaling packet (SP) S-PMSI configuration, 226–227, 234–260, 270f, 283f Static and dynamic signaling, 556–557 Stream Control Transmission Protocol (SCTP), 482 Streaming traffic class, 516 Synchronization distribution, 461–464, 463f T Tag control information (TCI), 361 TCI See Tag control information (TCI) TDM See Time division multiplexing (TDM) TDM-based backhaul infrastructure, 474 TE See Terminal equipment (TE) Terminal equipment (TE), 494, 495f Time division multiplexing (TDM), 553–554 TLS See Transparent LAN service (TLS) Traceoptions output, 246f Traffic generation, PIM-SSM provider tunnels, 271–272, 273–281 Transmitter power, 543 Transparent LAN service (TLS), Transponders, 528–529 Transport and service control plane, 451 Transport architecture models, 412 Transportation, 400–401 Transport layer elements, 548–550 U UCA See Use customer addresses (UCA) UMTS See Universal mobile telephone service (UMTS) UMTS terrestrial radio access network (UTRAN), 485 Universal mobile telephone service (UMTS), 469 Use customer addresses (UCA), 361 UTRAN See UMTS terrestrial radio access network (UTRAN) V VCID See Virtual circuit identifier (VCID) VFI See Virtual forwarding instance (VFI) Virtual circuit identifier (VCID), 9–10 INDEX Virtual forwarding instance (VFI), Virtual private LAN service (VPLS) autodiscovery, LDP-VPLS, 12–16 BGP-VPLS control plane, 6–9 LDP-VPLS and BGP-VPLS, 10–12 Virtual switching instances (VSI), 353–354 VPLS See Virtual private LAN service (VPLS) VPLS constructs and frame formats, PBB backbone component-BVPLS, 366 frame formats, 366 service component-I-VPLS, 365 VPLS-ID, 14 VPLS scalability factors, 326–327 VPN200, 25 VPN-IPv4 address family, 80–82 VPN routing and forwarding (VRF) Red and Pink, 108 VPNv4 LFIB entries, 119 VPN routing information BGP route, 87–88 CE router to ingress PE route distribution, 90–91 customer site, 89 egress PE route installation, 96 egress PE router to CE route distribution, 96–98 router PE1, 92, 92f router PE2, 92–93, 93f router PE3, 93, 94f VPNv4 LFIB entries remote AS, 119 VRFs in local PEs, 119 VPNv4 route distribution advertise remote IPv4 addresses, 172 ASBR 200 configurations, 129 ASBRs, 105–106, 172 authoritative control, 172 back-to-back VRF connections, 172 backup path check, 126–127 configuration analysis, 113–126 585 eBGP peering, 104, 104f, 105 inter-AS operation, 106, 109–113 load-balancing, 127–130 PE-200 configuration, 129–130 PE router loopback addresses, 105 test setup, 106–108 VPNv4 and IPv4 routes, 130–131 VPNv4 routes BGP, 114–115, 115f inter-AS operation, 109–111 inter-AS operation–BGP routes method, 151–172 inter-AS operation–IGP routes method, 141–142 VRF See VPN routing and forwarding (VRF) VSI See Virtual switching instances (VSI) VSI-ID, 14 W WiMAX, 484 .. .NETWORK CONVERGENCE Ethernet Applications and Next Generation Packet Transport Architectures VINOD JOSEPH and SRINIVAS MULUGU AMSTERDAM • BOSTON • HEIDELBERG... Joseph, Vinod Network convergence : Ethernet applications and next generation packet transport architectures / Vinod Joseph, Srinivas Mulugu pages cm Includes bibliographical references and index... ISBN 978-0-12-397877-6 (pbk.) Ethernet (Local area network system) Packet transport networks Computer network architectures Convergence (Telecommunication) Internetworking (Telecommunication)