VNP2 Network High Level Design

High Level Design for Transit RoutersVNP2 3G Project--Version 1.0--

HCM, Apr 2015Revision historyVersionDateStatusEditorChange

1.029AprDraftSVTech teamInitial document

TABLE OF CONTENTS1About document42List of equipments and configuration42.1Juniper MX96042.2Juniper BoQ83Network topologies113.1Network topology for Thanh Thai113.2Network topology for Binh Phuoc113.3Network topology for Tay Ninh124Connect from nodeB to transit router124.1Redundant gateway for nodeB using VRRP technology.124.2Connect nodeB to transit router using STM|STM4135Connect RNC to transit router146Time synchronization from nodeB to TP5000 system157Routing protocols for uplink connections167.1IGP routing using ospf167.2BGP routing177.3MPLS198Class-of-service199Operations & maintenance with Junos Space system21

About documentDocument describes solutions for transit routers and O&M for VNP2 3G project: Physical connectivities Routing solutions: IGP, BGP, MPLS Class-of-service solutions O&M solutions Network redundancyList of equipments and configurationJuniper MX960MX960 will be used in VNP to provide a proper transport of 2G and 3G network. The network consists of MX960 and one set of NMS. The MX960 router is 16 rack units (U) tall. The size is 44.11cm x 58,42cm x 70,49cm (Width x Depth x Height).

Figure: MX960 routerBackplaneMX960 router uses backplane architecture. This means that all the cards are of front access type. The backside of the subrack has just metal cover and all the interface connectors are located on the front side. The backplane itself is passive and only provides connectors and signal paths for data packet transfer and power distribution among cards. The backplane data transmission architecture is based on differential, point-to-point signals where each card is a center point for star topology. The main advantage is that there is no need for a traditional switch card. There is no separate internal communication bus between the cards in the NE but the control traffic is transferred like any data packet between two cards. The other buses are the power bus, synchronization (clock) bus, fan module control bus and card presence bus.Card SlotsThe 14 open slots on the MX960 router holds 12 line cards and two SCBs in a non-redundant configuration or three SCBs and 11 line cards in a redundant configuration. All cards are hot-removable and hot-insertable. To change or install an interface module, the line card needs to be removed from the subrack.SCBSwitch control board(SCB) is a basic element of the MX960 router.

Switch control board (SCB)Each SCB consists of the following components:-Chassis management Ethernet switch-I2C bus logic, used for low-level communication with each component-Component redundancy circuitry-Control Board/Routing Engine mastership mechanism-Gigabit Ethernet switch that is connected to the embedded CPU complex on all components-Switch fabricProvides the switching functions for the DPCs, FPCs, and MPCs-Control field-programmable gate array (FPGA)Provides the Peripheral Component Interconnect (PCI) interface to the Routing Engine-1000Base-T Ethernet controllerProvides a 1-Gbps Ethernet link between the Routing Engines-Ethernet switchProvides 1-Gbps link speeds between the Routing Engine and the DPCs, FPCs, and MPCs-Circuits for chassis management and control-Power circuits for the Routing Engine and SCB-LEDsProvide statusYou can install up to three. The SCBs install vertically into the front of the chassis in the slots labeled 0, 1, and 2/6. If any slots are empty, you must install a blank panel.Line CardRouter MX960 uses 2 types of line card:Modular Port Concentrator (MPC): Second-generation high-density and high-speed Ethernet line cards supporting modulesModule Interface Card (MIC): Second-generation Ethernet and optical modules that are inserted into MPCsMPCModular Port Concentrators (MPCs) provide packet forwarding services. The MPCs are inserted into a slot in a router. Modular Interface Cards (MICs) provide the physical interfaces and install into the MPCs. You can install up to two MICs of different media types on the same MPC as long as the MPC supports those MICs. The MX960 router supports up to 12 MPCs. MPCs are hot-removable and hot-insertable. When you install an MPC in an operating router, the Routing Engine downloads the MPC software, the MPC runs its diagnostics, and the Packet Forwarding Engines housed on the MPC are enabled. Forwarding on other MPCs continues uninterrupted during this process.Each MPC consists of the following components:-MPC card carrier, which includes two MIC slots (excludes the fixed onfiguration MPC).-Fabric interfaces.-Two Gigabit Ethernet interfaces that allow control information, route information, and statistics to be sent between the Routing Engine and the CPU on the MPCs.-Two interfaces from the SCBs that enable the MPCs to be powered on and controlled.-Physical MPC connectors.-Up to four Junos Trio chipsets, which perform control functions tailored to the MPCs media type.-Midplane connectors and power circuitry.-Processor subsystem, which includes a 1.5-GHz CPU, system controller, and 1 GB of SDRAM.-Online button which takes the MPC online or offline when pressed.-OK/Fail LED on the MPC faceplate.MICModular Interface Cards (MICs) install into Modular Port Concentrators (MPCs) and provide the physical connections to various network media types. MICs allow different physical interfaces to be supported on a single line card. You can install MICs of different media types on the same MPC as long as the MPC supports those MICs.

MICs receive incoming packets from the network and transmit outgoing packets to the network. During this process, each MIC performs framing and high-speed signaling for its media type. Before transmitting outgoing data packets through the MIC interfaces, the MPCs encapsulate the packets received.

MICs are hot-removable and hot-insertable. You can install up to two MICs in the slots in each MPC.

Juniper BoQ ITEM CODETransport NodeQuantityTotal quantity

MX960Hardware1212

Juniper MX960

MX960-PREMIUM3-DCMX960 Premium Bundle with redundant components, DC Power112

RE-S-1800X4-16G-BBRouting Engine - Quad Core 1.8GHz with 16G Memory, Base Bundle, for MX224

PWR-MX960-4100-DC-BB4100W DC Power Supply, configurable option in base bundle448

FFANTRAY-MX960-HC-BBMX960 High Capacity fantray (upper or lower), configurable option in base bundle224

FFILTER-MX960-HC-BBMX960 Filter tray for high-capacity fantray, configurable option in base bundle112

Line cards and Optics

SCBE2-MX-BBEnhanced MX Switch Control Board, Base Bundle336

MX-MPC1E-3D-R-BMX-MPC1E-3D line card bundle, price includes full scale L3, L2 and L2.5 features112

MX-MPC1E-3D-Q-R-BMX-MPC1E-3D-Q line card bundle, price includes full scale L3, L2 and L2.5 features224

MIC-3D-20GE-SFP-EMIC-3D-20GE-SFP, enhanced (MAC SEC & TIMING PHY)112

MIC-3D-4CHOC3-2CHOC12Low density multirate MIC - Channelized, 4 port channelized OC3 / 2 port channelized OC12 (down to DS0) MIC, (Requires a pluggable SFP optics module); Requires license S-MX80-Q when used on MX80 platform336

SFP-OC3-IRSmall Form Factor Pluggable OC3 Inermediate Reach (IR) SM Optic Module - 15Km 12144

SFP-1GE-TSmall Form Factor Pluggable 1000Base-T Gigabit Ethernet Module (uses Cat 5 cable)12144

Software1212

JUNOS-WW-64JUNOS 64-bit Internet Software Worldwide Version112

JS-IPv6IPv6 Support on JUNOS112

S-LSSL-64Link Services Software License - up to 64 ML bundles per Chassis for AS PIC, MS PIC and MS DPC112

Management System11

Junos SpaceHardware11

JA2500-A-BSEJunos Space 2500 - Large appliance; Requires one JS-PLATFORM software SKU per appliance11

JS-PLATFORMJunos Space Network Management Platform with 4 Cores11

UNIV-2U-UNIMNT-GUniversal Rack Mount 11

UNIV-250W-PS-ACAC Power Supply (250W) for NSMXpress Series II, NSM3000, NSM4000, SPC1500, STRM 500/2500 (A2), JA250011

Software11

UNIV-2U-RAILKITRail Kit for NSM 3000. SPC 150011

JS-SVADIR-100JS Svc Activation Dir for 100 devices11

MX960 & Junos Space BoQ in VNP2

Network topologiesNetwork topology for Thanh Thai

Network topology for Binh Phuoc

Network topology for Tay Ninh

Connect from nodeB to transit routerRedundant gateway for nodeB using VRRP technology.VRRP (Virtual Router Redundancy Protocol) is an Internet protocol that provides a way to have one or more backup routers when using a statically configured router on a local area network (LAN). The most common arrangement is to specify one router to serve as the router for forwarding packets. If that router fails, however, there is no way to use another router as a backup.A virtual IP address is shared among the routers, with one designated as the master router and the others as backups. In case the master fails, the virtual IP address is mapped to a backup router's IP address. (This backup becomes the master router). The router with higher priority ( from 1 to 255) configured will become master router. By default, master router will send an advertisement message in 1-second interval for tracking vrrp-state from other backup routers.In this design, NodeBs connect to both Router MX960-01 and MX960-02. These routers assume the role of gateway for NodeBs. Mx960-01 is master, MX960-02 is backup for a half number of nodeBs. The same, MX960-02 is master, MX960-01 is backup for other nodeBs.

Figure: VRRP for NodeB and transit routerConnect nodeB to transit router using STM|STM4NodeB can be connected to one transit router using STM1|STM4 connections on router MX960 as topology below. One nodeB can have multiple e1 connections in a bundle to connect to transit routers.In MX960 transit node, one STM1 connection can be used for many nodeB. Each nodeB will use a range of time-slot on this STM1 port depending on number of e1 connections that be used on nodeB.

Connect nodeB to transit router using STM1|STM4Connect RNC to transit routerFor IUB, we use three links with three different layer-3 connections from one RNC to one transit router for active and three links to other router for standby.For IUPS, IUCS, IUR, we use three links with three different layer-3 connections from RNC to one transit router for active and three links to other router for standby.For O&M, we use one link with one layer-3 connections from RNC to one transit router for active and one link to other router for standby.

Figure: RNC to transit routersTime synchronization from nodeB to TP5000 systemTP5000 timing system connects to transit routers at Thanh Thai based on layer-3 connections. Based on dynamic routing, all nodeB devices on Vinaphone network can connect to TP5000 to set up client/server sessions for timing synchronization.All nodeBs in Binh Phuoc and Tay Ninh province will primarily connect to Hcm-ToP-02 and backup connect to Hcm-ToP-01.All nodeBs in Ninh Thuan, Binh Thuan and Lam Dong will primarily connect to Hcm-ToP-01 and backup connect to Hcm-ToP-02.

Figure: Time synchronization from nodeB to TP5000 system Routing protocols for uplink connectionsIGP routing using ospfOSPF Routing protocol is implemented to all Routers MX960 at Ty Ninh, Bnh Phc, HCM and the Core. The convergence of OSPF is necessary to configure BGP and MPLS. All router run OSPF area 0. OSPF neighbors are established between 2 router connect directly.

BGP routing Router MX960 at s Binh Phuoc, Tay Ninh, HCM, a Nang create a BGP peer to 2 Route Reflector Router in Core VNP. Routing informations were sent from router at remote site to RR and the RR will reflect to all their clients. Enable BGP multipath feature to optimized traffic load sharing.

MPLS

MPLS/LDP will be enable on all interfaces connecting directly between all routers. Routers will generate label and use label to switch traffic site to site.Class-of-serviceClass-of-service (CoS) is configured on all transport nodes. Different CoS functions are configured on transport nodes based on their positions on network.Juniper CoS funtions includes:+ Classification: static | multi-field classification, dscp-exp-ippre based classifications+ Scheduling: define how traffic is processed for different forwarding-classes, different interface queues+ Rewrite: after traffic out of router interfaces, it will be rewritten cos values like mpls_exp, dscp, so other routers behind this transport node will do classification based on these values

Figure: Class-of-service for VNP2 networkFor VNP2 network, ingress packets on transport nodes are classified by DSCP.The following table contains the QoS configuration in mcRNC and transport nodes..

VNP2 needs to provide percent ratios that is nessessary to be guaranteed for each type of traffic class above.Operations & maintenance with Junos Space systemJunos Space is an O&M system for transit router, that will be installed at Ha Noi OMC. Communication between Junos Space system with transit router is based on loopback interface on transit router. That mean Junos Space system must can be reached to loopback addresses on transit router based on VNPs global routing. The topology is as below: Page 10 of 21