ODD010010 IP Backbone Network Planning ISSUE 1 - 2

Internal
ODD010010 IP Backbone Network Planning

ISSUE 1.2
www.huawei.com
HUAWEI TECHNOLOGIES CO., LTD.
All rights reserved
PDF created with FinePrint pdfFactory Pro trial version www.pdffactory.com
With telecom services transferred to the IP network, the IP network bears more and more services. It is obviously more and more important to build a stable IP core network that can bear multiple services and ensure the Quality of Service (QoS).
All rights reserved
Page 1
This course helps you to: [ Learn the backbone network architecture of the current main operators. [ Master the traffic models of backbone network. [ Master major points of backbone networking planning. [ Learn typical IP backbone network networking instances.
All rights reserved
Page 2
Chapter 1 Overview of Backbone Network Planning Chapter 2 Backbone Network Architecture Chapter 3 Backbone Network Planning Chapter 4 Typical Case Analysis for Backbone Network
All rights reserved
Page 3
Overview of Backbone Network

Introduction to Backbone Network
l The IP backbone network, as the core of the whole network and upper-
level network of the metropolitan area network (MAN), serves as the egress for the MAN to visit external networks and the hinge for interworking between MANs.
l Because the IP network bears more and more services, the network
traffic is becoming large and the network is becoming more and more important. In addition to the traditional Internet access service, large operators are actively engaged in developing value-added services such as NGN services, 3G service, and key account interconnection. To bear the value-added services, some operators start to build a second backbone network such as CN2 of China Telecom, IP private network of China Mobile, and CRNET Stage 2 of China Tietong.
HUAWEI TECHNOLOGIES CO., LTD. All rights reserved Page 4
Backbone Network Planning Principles

l High reliability
[ The reliability of backbone network devices is the key for the whole network to run reliably. Therefore, the network architecture must be designed properly and reliable network backup strategies must be developed to ensure that the network can recover by itself upon failure.
l Flexibility and scalability
[ Based on the requirements of future network service development, capacity can be expanded smoothly and the network can be upgraded easily so as to reduce the impact of network architecture adjustment.
l Flat
[ Decrease the network hierarchy and hops and facilitate network management.
Backbone Network Planning Principles (Continued)

l Proper QoS planning
[ The services borne by the current IP network cover not only the pure Internet access service but also VoIP service, video service, key account service, and other services. These services have high requirements for the QoS. Therefore, the support for QoS is a necessary condition for network transition from the telecom network to IP network. The QoS must be properly planned.
l Operability and manageability
[ Monitor the network on an integrated basis, manage the network based on authority, and allocate bandwidth resources on a uniform basis so that the network can be in the management scope.
All rights reserved
Page 7
Network Architecture of Backbone Network

Network Architecture of Backbone Network
l The architecture of the backbone network falls into:
[ Plane hierarchical structure [ Plane and space hierarchical structure

l The traditional backbone network often uses the plane hierarchical structure, that
is, build a network using the hierarchy structure, for example, the current core layer and convergence layer structure. This network structure enables subscribers to access networks quickly and stably.
l The difference of the plane and space hierarchical structure from the above
structure is that the backbone network is divided into multiple planes (two planes in most cases). The planes are still in the hierarchical structure and run services of their own. When the network is faulty, the planes can serve as backup devices of each other.
IP Backbone Network Traffic Model Analysis

AR
link
BR
BR
link link
AR
External network traffic Longitudi nal traffic
4 3
Internal network traffic Core layer/transit layer

IP backbone network
IP provincial network
Transverse traffic Access layer
2 1
Access layer
BR - core router/transit router

VoIP, Video, BT, QQ, or MPLS VPN Local IDC visit (news, games, or downloading)
AR
access router
National and international Internet access, or international VoIP Access of local network IDC by external networks
All rights reserved
Page 9
Plane Hierarchical Structure Model

AR
link
BR
link
BR
link
AR
External network traffic Longitudi nal traffic Internal network traffic Access layer
4 3 2 1
Transverse traffic Core layer/transit layer

IP backbone network
Access layer

AR
access router
All rights reserved
Page 10
Plane Hierarchical Structure Model

National backbone IP network
GZ egress BJ egress SH egress
GZ IDC
BJ IDC
SH IDC
XA
SY
BJ
CD
GZ
SH
WH
NJ
Provincial IP network Region/City IP network

Plane Hierarchical Structure

l The plane hierarchical network is common in early backbone network. l At present, most national operators use this network. The network
consists of the core backbone layer, core convergence layer, and core access layer.
l The core backbone layer is divided into the regional centers based on
regions. Regional centers are all connected or partially connected to make the network more robust.
l The dual-homing mode is used for networking of the core convergence
layer. Two uplinks are connected to the backbone devices of the regional center or to different backbone devices of two regional centers.
All rights reserved
Page 12
Typical Plane Hierarchical Network CRC CRNET Stage 2
China
All rights reserved
Page 13
Plane and Space Hierarchical Structure Model 1 (External Network/Internal Network)

AR
link
BR
link
BR
link
AR
Longitudi nal traffic
External network traffic
4 3
Transverse traffic
Internal network traffic Access layer Core layer/transit layer

IP backbone network
2 1
Access layer

AR
access router
All rights reserved
Page 14
Plane and Space Hierarchical Structure Model 2 (Longitudinal/Transverse)

AR
link
BR
link
BR
link
AR
4
Longitudi nal traffic External network traffic
3 2 1
Transverse traffic
Internal network traffic Access layer Core layer/transit layer

IP backbone network
Access layer

AR
access router
All rights reserved
Page 15
Plane and Space Hierarchical Network

National Backbone IP Network
BJ egress BJ IDC
GZ egress
GZ
BJ SH
SH IDC SH egress
GZ IDC
XA
BJ
SY
CD
GZ
WH
SH
NJ
Provincial IP network Municipal IP network

Plane Hierarchical Network Structure

l For the plane and space hierarchical structure, the plane is divided
during hierarchy. Different planes bear different services.

l In normal cases, the services in two planes do not affect each other.
When one plane is faulty, the other plane serves as the backup device of the plane.
l Based on network design, each plane can bear all service volume by
design.
l When multiple services need to be borne currently, the plane
hierarchical network model shows its advantages of clear structure, good backup function, and high security.
IP MAN Dual-Plane Structure

Backbone network 2 (carrier-class service) Backbone network 1 (network access and data services)
1+1>2
B: carrier-class service plane A: Internet service plane
MAN
All rights reserved
Page 18
IP Bearer Network in T Office of China Mobile

BJ1 XA1 SY1 NJ1 CR1
A forwarding plane
CD1 GZ1
AR
SH1 BJ2 XA2
WH1 SY2 NJ2
B forwarding plane
CD2 SH2 WH2
GZ2
All rights reserved
Page 19
All rights reserved
Page 20
Chapter 3 Backbone Network Planning

3.1 IP Address Planning 3.2 Routing Protocol Planning 3.3 MPLS VPN Planning 3.4 QoS Planning
All rights reserved
Page 21
IP Address Planning
IP Address Planning
l Proper IP address planning is an important part in the network
design. IP addresses must be planned and implemented on a uniform basis for large networks.
l
IP address planning affects the efficiency of network protocol algorithm, network performances, network scalability, network management, and further development of network application.
All rights reserved
Page 22
IP Address Planning Principles

IP Address Planning Principles
l
Unique: [ In an IP network, the same IP address cannot be set for two hosts. Do not set the same IP address for different hosts even if the MPLS/VPN technology that supports address overlapping is used.
Continuous: [ Continuous addresses facilitate path overlapping in the hierarchical network, thus cutting the size of the routing table and improving the efficiency of routing algorithms.
Scalable: [ Excessive addresses must be reserved for each layer so as to meet requirements of network expansion.
Meaningful: [ Each IP address shall have concrete meaning, and it is easy to find the device of an IP address.
All rights reserved
Page 23

All rights reserved
Page 24
Routing Protocol Planning

Routing Protocol Planning
l Routing protocol planning directly affects network stability, recovery
duration upon network failure, and workload of network maintenance. Therefore, routing protocol planning is the key of network planning.
l Routing protocol planning covers Interior Gateway Protocol (IGP)
and Exterior Gateway Protocol (EGP).

l In dynamic protocols of IGP, the protocols that are open and can
support large networks include OSPF and IS-IS.

l BGP4 and MP-BGP are commonly used as the EGP currently.
All rights reserved
Page 25
Routing Protocol Planning Principles

Routing Protocol Planning Principles
l
Shortest path: Try to make the shortest path of IGP be the short transmission distance because the end-to-end delay comes from transmission delay in the backbone network. Try to use the second shortest transmission distance as other backup paths to reduce the delay jitter caused by active/standby switchover. Fast convergence: Detect faults quickly and respond to them so that the system can recover as soon as possible and black hole routes and route loop can be avoided. Controllable and predictable routes: Use clear, specific, and simple routing strategies to avoid possible difficulties in operation and deployment. Reliability: Judge network faults correctly and avoid frequent route calculation and update. Load sharing: Improve network resource utilization and system reliability.
All rights reserved Page 26
Selection of IGP Routing Protocol

Selection of IGP Routing Protocol
l Both OSPF and IS-IS are used in the current large networks. l To select a routing protocol of IGP, take the following into
account: [ Features of protocols [ Application degree [ Technology continuity
All rights reserved
Page 27
Selection of IGP Routing Protocol (Continued)

In terms of protocol features
l The OSPF protocol is based on the IP layer and can support the IP network only.
The IS-IS protocol is running in the link layer directly and can support multiple types of network.
l
Both OSPF and IS-IS cover the concepts of hierarchy and area. The OSPF has the backbone area 0 and branch areas. The IS-IS has two levels: level 1 and level 2. When visiting other networks, level 1 uses the nearest routerL2. In this case, routes need to be optimized. The route penetration must be used to solve this problem. network and is mature. The IS-IS is precise in structure and runs stably. The IS-IS router can belong to one area only and does not support networks such as FR, ATM, and X.25 network.
l The OSPF protocol, based on interface, is very flexible. It supports all types of
The IS-IS protocol is more scalable because it is based on TLV.


In terms of application degree
l The OSPF is widely used in the MAN, and early network
maintenance personnel are familiar with this protocol.

l In recent years, the IS-IS protocol is frequently used in the
backbone networks of large operators. However, network maintenance personnel are less familiar with this protocol, which may affect subsequent network maintenance.
All rights reserved
Page 29

In terms of technology continuity
l When selecting a protocol, you need to check the protocol that
is running in the original network. For example, some operators use the IS-IS protocol in the core layer and the OSPF protocol in the MAN. To protect network continuity, you must take the cases into account when selecting a protocol.
All rights reserved
Page 30
IGP Selection Principle

IGP Selection Principle
l Backbone network
[ In the backbone network, focus on stability of protocols and convergence speed. In the backbone network, the IGP needs to bear loopback addresses and interconnection addresses of the backbone network only. There are no special networking requirements, and the size of network is large. It is recommended to use the IS-IS protocol.
l MAN
[ In the MAN, focus on the flexibility of protocols and networking and whether a large number of user demands can be satisfied. The OSPF protocol can meet the requirements. It is recommended to use this protocol.
OSPF Routing Protocol Planning

Major Points of OSPF Planning
l Router id
[ It is unique in the OSPF area. It is recommended to use loopback addresses.

l Area division
[ Division of areas is of great significance in the OSPF design. [ It is recommended that no more than 50 routers are running in each area. [ If the OSPF protocol is used in the backbone network, use area 0 by preference. [ If a non-backbone area needs to be used, divide the area based on physical area.
OSPF Routing Protocol Planning (Continued)

l Area type
[ The areas of OSPF can be divided into common area, Stub area, Totally Stub area, and NSSA area. [ Stub: It is not allowed to introduce external routes of AS. Set a default route for the area. [ Totally Stub: External routes of AS and the area are not introduced. Set a default route for the area. [ NSSA: External routes are introduced during running. Others are the same as that of the Stub.
l The above three special areas are used to decrease the number of routes and
reduce the performance requirements on equipment. Common backbone networks are used to transfer routes of interconnected links only. Therefore, the areas are not used in most cases.
OSPF Routing Protocol Planning (Continued)

l COST
To ensure that the router selects the best path, the value of !COST" must be set uniformly. At present, the value is set in the following ways: [ 1. Set this value according to the bandwidth of links: Select a reference bandwidth and compare the actual link bandwidth with the reference bandwidth. COST = reference value / actual link bandwidth (if the maximum bandwidth GE is selected) # 40 GE links COST = 1 # 10 GE links COST = 4 # GE links COST = 40 # FE links COST = 400COST # 155 M links COST = 258 2 [ 2. Set the value of COST based on the designed traffic model so as to control routing:
IS-IS Routing Protocol Planning

Major Points of IS-IS Planning
l Network hierarchy
[ The IS-IS is designed with L2 and L1. Therefore, the router in the IS-IS domain can play the roles of L1, L2, and L1/L2. Considering scalability, it is recommended that the IS-IS equipment is placed in L2 in the backbone network. L2 of the IS-IS must be continuous. At the border of the backbone network, you can set the router to L1/L2 so as to facilitate subsequent expansion of the IS-IS domain.
l Area division
[ IS-IS, the concept of area is almost the same as that in the OSPF. Currently, the OSPF protocol is used for L2 in most cases, but areas do not play an important role. Only when routers L1 and L1/L2 exist, areas can restrict routes and traffic. If areas are identified through the local telephone area codes, they must be planned uniformly.
IS-IS Routing Protocol Planning (Continued)

l NET (network entity ID)
[ NET, converted by the NSAP by setting NSEL to 0, is used to identify an IS device in the IP network. Its structure is as follows:
AFI 1 byte Area ID Variable Length Area Address 1~12 bytes Sys ID System ID 6 bytes NESL NSEL 1 byte
l AFI: AFI can be applied officially or be set to the private value !49". The value plays
the role of identification in the IP network only. # AREA ID: It is planned in advance. For the backbone network, you can set this parameter to a local telephone area code or the AS No. of the system. # System ID: ID of a device in an area. It is unique in an area. This parameter is often set to an MAC address or IP address. It is recommended to set this parameter to the loopback address of equipment. # NSEL: It is set to the fixed value !00".
NET Planning Example

NET Planning Example
l Suppose the area of a device is 49.0001 and the loopback
address is !192.168.3.25 ", the NET can be in the following forms:
192.168.3.25 192.168.003.025 1921.6800.3025 : System ID 49.0001.1921.6800.3025.00: NET
All rights reserved
Page 37
IS-IS Routing Protocol Planning (Continued)

l Metric
[ Metric The functions and settings of Metric are the same as those of COST of the OSPF. Metric is used to control the shortest path of a route. IS-IS Metric consists of basic Metric and extended Metric. In Huawei, it is set to basic Metric by default. In large networks, extended Metric is used frequently. The value ranges of Metric are as follows: # Basic Metric: 1 63
# Extended Metric: 1 - 16777215
All rights reserved
Page 38
BGP Routing Protocol Planning

Major Points of BGP Planning
l
AS Number & BGP Neighbor
The BGP is the most widely used and complicated protocol in the backbone network. The major points of BGP route planning are as follows: [ AS Number # AS numbers consist of public numbers and private numbers. Public AS numbers are allocated by CNNIC and need not be planned. Private AS numbers are in the range 64512 to 65535. Private AS numbers can be used inside operators, and the numbers can be filtered at the egress of network. [ IBGP & EBGP # BGP neighbor covers IBGP and EBGP. The EBGP is running between operators and other networks, and the IBGP is used internally.
All rights reserved
Page 39
BGP Routing Protocol Planning (Continued)

Major Points of BGP Planning
l RR
RR Planning
[ In an AS, IBGP neighbors must be fully connected. Because the number of IBGP neighbors is large, the router reflector (RR) is used for networking.
A: RR
R R
B: RR
Cluster
Client
R R R
Client
R
All rights reserved
Page 40

RR Planning Principles
l Select an independent RR to ensure stability of the RR. l If an independent RR cannot be selected, choose the router in the core
position as the RR and ensure that the router can meet performance requirements.
l Use the RR redundancy configuration, that is, configure two RRs in a
cluster and run the two RRs on the client.

l Set the same cluster-id for multiple RRs in a same cluster to avoid loop.
It is recommended to select the bigger router id of RR as the cluster-id.

l If the network is large and is in the regular 2-level structure, use multi-
level RR form to plan the RR.
All rights reserved
Page 41
RR Networking Instances
City B CityCity C D City E City A City E City D City C City B City A Province A2 Province A1 Level-2 RR2
Level-2 RR1
ZONE Province A2 1 City A City B City C City D City E

Level-2 RR2
..
Xi an
Level-2 RR1
Province A1
Level-1 RR2
Beijin
Level-1 RR1 Level-2 RR1
Guan Province A1 gzhou Level-1 RR1 Province A2

Level-2 RR2 Level-1 RR2 Level-2 RR1
Shang hai RR1 Level-1
Level-2 RR2
Province A2
City E City D City C City B
Province A1
Level-2 RR1
City A
..
Province A1 City A City B City C City D City E HUAWEI TECHNOLOGIES CO., LTD.
. ..
Wuhan Province A2
Level-2 RR2
Level-1 RR2
Nanjin Province A1
Level-2 RR1
Province A2
Level-2 RR2
ZONE 3
ZONE 2 City C City A City B Page 42
City E City D
All rights reserved

Major Points of BGP Planning Route Attributes and Strategy
l The major feature of the BGP is the route attribute. Planning of
the BGP covers: [ Local-preference [ MED [ AS-Path [ Community [ Load-balancing
All rights reserved
Page 43
Local-preference
Local-preference
l Local Preference
[ To control the router in the AS to select outgoing routes, set the parameter local-preference. By default, this parameter is set to !100". The bigger value indicates higher priority. Local-preference is often used in the backbone network to boot outgoing traffic. It must be set during networking planning.
A
R
10.0.0.1 /24 Pre:100
10.0.0.1 /24 Pre:200
R
MED
MED
l MED is used to control the direction of incoming traffic of the AS. It is set to
!0" by default. The smaller value indicates higher priority. To make the MED value indicate the internal topology of AS, replicate the COST value of IGP routes in the next hop of IBGP routes to the MED in EBGP routes. However, it needs support of devices.
10.0.0.1 /24 MED:100 10.0.0.1 /24 MED:200
R R
C
All rights reserved
Page 45
AS-Path
AS-Path
l As-Path is used to prevent loops and control routing (that is, modify the
length of As-Path through the !AS-Path Prepend" mode to implement routing). As-Path differs from MED in that the MED helps control incoming traffic of neighbor Ass, whereas the Prepend can control routing of remote ASs.
AS 200 As-p: 200 100 AS 500 As-p: 400 300 100 AS 400 AS 300
Import route 10.0.0.0/24
AS 100
All rights reserved
Page 46
Community
Community
l Community attribute
[ You can apply a group of strategies to a group of neighbors so as to simplify configuration. Through the community attribute, a group of strategies can be applied to a group of routes to control routes. In large networks, the community attribute is planned uniformly to identify and control some types of route. [ Known community attribute: # no-export: not inform the EBGP peer entity # no-advertise: not inform any peer entity
All rights reserved
Page 47
Load-Balancing
Load-Balancing
l Load sharing mode 1:
[ Use the command Balance BGP to change the preference strategy and form the equal-cost route.
Router A AS100 Router B
R
1.1.1.1 Serial1/0/ 0 1.1.1.2 Serial2/0/ 0 2.1.1.2 3.1.1.1 2.1.1.1
R
Router C
3.1.1.2
R
Router D
Page 48
AS200
All rights reserved
Load-Balancing
Load-Balancing
l Load sharing mode 2:
[ There are many routes between ASBRs. Use the loopback interface to create EBGP connections and share load for BGP routes through iteration of the IGP equal-cost route of loopback.
Loopback1 30.0.0.1/8
Ethemet1/0/0 10.0.0.1/8
Loopback1 30.0.0.1/8
Ethemet1/0/0 10.0.0.2/8 Router B Ethemet2/0/0 20.0.0.2/8
AS 100
Router A Ethemet2/0/0 20.0.0.1/8
AS 200
Loopback0 30.0.0.1/8 HUAWEI TECHNOLOGIES CO., LTD. All rights reserved
Loopback0 30.0.0.1/8 Page 49

All rights reserved
Page 50
MPLS VPN Planning

MPLS VPN Planning Clue
l VPN demand analysis
[ Number of VPNs and VPN service types [ Determine the network scope of VPNs, number of subscribers, and number of routes. [ Determine VPN mutual visit demands and networking structure. [ Determine the demands of VPNs to access public networks. [ Determine VPN cross-domain demands and implementation basis.
l Selection of device roles
[ Determine devices P, PE, and CE. In the backbone network, most devices serve as the device P, and device P must support basic protocols such as MBGP, MPLS, and LDP.
MPLS VPN Planning (Continued)

l Planning of VPN-Instance, RD, and RT
[ The above parameters are planned and implemented on the device PE.
l MBGP Planning
[ The planning of MBGP is basically the same as that of common BGP. It is recommended to use an independent RR that is different from common BGP devices for the MBGP. Do not overlap the RR and ASBR.
l PE-CE Protocol Planning
[ Currently, the commonly used protocols include RIP, static protocols, OSPF, and EBGP. Select a protocol based on the network conditions and support of devices.
MPLS VPN Planning (Continued)

l Inter-AS implementation mode l The cross-AS MPLS VPN can be implemented in the following
modes: [ VRF-to-VRF [ MP-EBGP [ Multi-Hop MP-EBGP
All rights reserved
Page 53
Inter-AS implementation mode

Cross-AS MPLS VPN
l
VRF-to-VRF! [ Advantage: The MPLS need not be running between ASBRs. [ Disadvantage: Each VPN site must be bound with a sub-interface, and the ASBR needs to maintain vpn routes.
MP-EBGP [ Advantage: It is unnecessary to configure a sub-interface for each VPN site at the ASBR. [ Disadvantage: VPN routes must be maintained at the ASBR. A complete LSP is required between the PE ingress and PE egress, and ASBRs need mutual trust.
Multi-Hop MP-EBGP [ Advantage: It is easy to expand, and VPN routes need not be maintained by the ASBR. It is suitable for large networks. [ Disadvantage: The PEs of both ASs need to know the PE host address of peer AS, which may cause security problems.
All rights reserved
Page 54

All rights reserved
Page 55
IP QoS Planning
IP QoS IntServ Model
l IntServ model: Services request specific QoS service from the
network through signaling messages, and the network reserves resources within the range defined by the traffic parameter.
e serv width. ve e r . r e h t s o nt t o f band to re bandwid a I want to reserve t w I want to reserve n I ps of I wa 20 Mbps of bandwidth. 20 Mb 20 Mbps of bandwidth. 0 Mbps 2
OK!
OK!
OK!
OK!
l The IntServ model requires that end-to-end devices support this protocol. Network units
save status information for each application. This model is not easy to expand, and the overhead of protocol messages is large due to regular information exchange with neighbor units. This model is not suitable for large networks.
IP QoS Planning (Continued)

IP QoS DiffServ model
l DiffServ model: When the network is congested, remove congestion by controlling the
traffic and forwarding according to different QoS levels. DiffServ network

Internal node Border node Border node SLA/TCA Border node
DiffServ network
Internal node Border node
Traffic control User network User network
l For the DiffServ model, multiple service streams are converged into a Behavior
Aggregate (BA), and the same PHB is used in network units for forwarding, thus simplifying service processing and storage. This model is easy to be expanded. Currently, the QoS is implemented based on the DiffServ model in most cases.
MPLS QoS Planning

MPLS QoS E-LSP
l At the LER, map the IP DS bytes to the EXP bit of the MPLS Label and indicate the
packet QoS requirement for the LSR through the EXP bit. In this case, an LSP can support up to eight service levels. The LSR dispatches queues for packets based on label and EXP and discards messages based on EXP. The packets in the same LSP may be dispatched to different queues. E-LSP is a common LSP created through the LDP.
LER
LSR
E-LSP
AF1 EF
LER
All rights reserved
Page 58
MPLS QoS Planning (Continued)

MPLS QoS L-LSP
l At the LER, map the IP DS bytes to an LSP and indicate the packet QoS
requirement for the LSR through the label and EXP bit. The LSR dispatches queues for packets based on the label and discards messages based on EXP. The packets in a same LSP are dispatched to a same queue.
LER
LSR
L-LSP
AF1 EF
LER
All rights reserved
Page 59
MPLS QoS Planning (Continued)

Selection of E-LSP&L-LSP
l Selection of E-LSP or L-LSP depends on the number of service types,
packet discard value, and MPLS running mode (frame mode or cell mode) planned by the network.
l When the cell mode is used as the MPLS running mode, the label
corresponds to VPI/VCI. In this case, only L-LSP can be used. Map the EXP of label to the CLP of cells.
l When the frame mode is used as the MPLS running mode, E-LSP or L-LSP
can be used. Currently, most operators use up to four service levels (voice, video, VPN and high-quality network access, and common network access). Therefore, E-LSP can meet requirements of application and implement interworking with IP Precedence and 802.1p. It is recommend to use the ELSP mode.
MPLS TE
MPLS TE
l MPLS TE helps optimize network resources of the backbone network and
avoid congestion or idleness of some nodes.

l By extending the IGP routing protocol (OSPF or IS-IS), the MPLS TE
enables the IGP to collect network traffic information (including maximum link bandwidth, maximum reserved bandwidth, currently reserved bandwidth, and link types) and stores the information in the traffic database (TED). Each TE router obtains displayed routes based on its TED and route calculation according to strategies. The finally displayed routes are deployed through the signaling protocol CR-LDP or extension of RSVP. The MPLS TE technology is not used in a large scale because its deployment is complicated and need support of devices.
QoS Planning
Service Analysis
Service Analysis
l Currently, the requirements on the network quality fall into the following categories:
[ The delay, jitter, packet loss ratio are low, and the bandwidth can be ensured. The typical services for these requirements include NGN voice services and video services. [ The bandwidth can be ensured, and the real-time requirement is not high. The typical services for these requirements include key account service and NM service. [ The requirements for real-time performance and bandwidth are not high. The typical service for these requirements is the common network access service.
l In the current backbone network, the QoS models frequently used are DifferServ and
MPLS E-LSP. Based on the above analysis, the EF stream is for the first type of service, the AF stream for the second type of service, and BE stream for the third type of service.
QoS Planning
Service level
Service type Control management 3G/NGN voice stream Real-time video service Key account VPN (gold medal) Key account VPN (silver medal), Vnet high priority Key account VPN (bronze medal), Vnet low priority, 3G data services Internet access
Service Levels
Priority Highest EF EF AF4 AF2
DSCP code 0b111xxx 0b110xxx 0b101110 0b100xxx 0b010xxx
MPLS EXP code 7 6 5 4 2
Congestion avoidance None None None WRED WRED
AF1
0b001xxx
WRED
BE
0b000000
WRED
All rights reserved
Page 63
All rights reserved
Page 64
Typical Cases of T Office of China Mobile

1
Xi$an 1 Xi$an 2 Beijing 2
Shijiazhuang H!h!h$ot'
National network management center
Taiyuan Tianjin Shenyang1 Shenyang2 Changchun
Urumchi Lanzhou Yinchuan Sining Chengdu1 Chengdu2 Chongqing
Xi an
Beijing
Haerbing
Shenyang
Shanghai1
Shanghai Chengdu
Shanghai2 Nanchang Hangzhou Fuzhou
Guangzhou
Kunming Lasa
Nanjing 1
Wuhan
Nanjing
Nanjing 2 Hefei Jinan
Guangzhou 2 Nanling Haikou Changsha Wuhan Wuhan 1 2 Guangzhou 1 Zhengzhou

l l
T office of China Mobile is the IP private backbone network that bears the softswitch service and VPN service especially. " Beijing, Shanghai, Guangzhou, Wuhan, Nanjing, Shenyang, Xi $an, and Chengdu are eight transit nodes, used to converge traffic of the areas.
All rights reserved
Page 65
Typical Cases of T Office of China Mobile

Forwarding plane A
Forwarding plane B
l
The backbone network of T office is divided into two planes: A and B. Each plane can bear all data traffic by design. In normal cases, plane A is responsible for the softswitch services, and plane B bears the key account VPN service. When a plane is faulty, the traffic in the plane will be switched to the other plane. All rights reserved Page 66
Thank You
www.huawei.com

ODD010010 IP Backbone Network Planning ISSUE 1 - 2

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

ODD010010 IP Backbone Network Planning ISSUE 1 - 2

Transféré par

Droits d'auteur :

Formats disponibles

Internal

ODD010010 IP Backbone Network Planning

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

PDF created with FinePrint pdfFactory Pro trial version www.pdffactory.com

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

PDF created with FinePrint pdfFactory Pro trial version www.pdffactory.com

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

PDF created with FinePrint pdfFactory Pro trial version www.pdffactory.com

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

PDF created with FinePrint pdfFactory Pro trial version www.pdffactory.com

Overview of Backbone Network

PDF created with FinePrint pdfFactory Pro trial version www.pdffactory.com

Backbone Network Planning Principles

PDF created with FinePrint pdfFactory Pro trial version www.pdffactory.com

Backbone Network Planning Principles (Continued)

PDF created with FinePrint pdfFactory Pro trial version www.pdffactory.com

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

PDF created with FinePrint pdfFactory Pro trial version www.pdffactory.com

Network Architecture of Backbone Network

[ Plane hierarchical structure [ Plane and space hierarchical structure

PDF created with FinePrint pdfFactory Pro trial version www.pdffactory.com

IP Backbone Network Traffic Model Analysis

External network traffic Longitudi nal traffic

Internal network traffic Core layer/transit layer

Transverse traffic Access layer

BR - core router/transit router

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

PDF created with FinePrint pdfFactory Pro trial version www.pdffactory.com

Plane Hierarchical Structure Model

Transverse traffic Core layer/transit layer

BR - core router/transit router

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

PDF created with FinePrint pdfFactory Pro trial version www.pdffactory.com

Plane Hierarchical Structure Model

Provincial IP network Region/City IP network

PDF created with FinePrint pdfFactory Pro trial version www.pdffactory.com

Plane Hierarchical Structure

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

PDF created with FinePrint pdfFactory Pro trial version www.pdffactory.com

Typical Plane Hierarchical Network CRC CRNET Stage 2

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

PDF created with FinePrint pdfFactory Pro trial version www.pdffactory.com

Plane and Space Hierarchical Structure Model 1 (External Network/Internal Network)

Longitudi nal traffic

External network traffic

Internal network traffic Access layer Core layer/transit layer

BR - core router/transit router

HUAWEI TECHNOLOGIES CO., LTD.

All rights reserved

PDF created with FinePrint pdfFactory Pro trial version www.pdffactory.com

Plane and Space Hierarchical Structure Model 2 (Longitudinal/Transverse)

Internal network traffic Access layer Core layer/transit layer

BR - core router/transit router

HUAWEI TECHNOLOGIES CO., LTD.