2-networking and planning

31
Networking and Planning

Upload: mel-jr-valencia

Post on 12-Apr-2016

20 views

Category:

Documents


0 download

DESCRIPTION

2-Networking and Planning

TRANSCRIPT

Page 1: 2-Networking and Planning

Networking and Planning

Page 2: 2-Networking and Planning

2

Contents

1. Network Building Requirements

2. Networking and Planning

3. Experimental Network Planning Examples

Page 3: 2-Networking and Planning

3

Changes from 3G Network to LTE RAN

The EPC+eNB without RNCs is adopted, making the network structure flattened.

The network evolves into an all IP network, with the uplink and downlink rates increasing

greatly. The common rate is 30 Mbit/s and the maximum rate is 50 Mbit/s on a 3G network.

The required bandwidth is about 150 Mbit/s on an LTE network.

The eNB capabilities have been boosted obviously in comparison with 2G/3G base stations.

Dynamic connections need to be configured for interfaces on eNBs.

Page 4: 2-Networking and Planning

4

Service Requirements

FTTH user

OTN network

10GE

GE

RNC

Backbone layer

Distribution layer

Access layer

Service control

layer

Termination layer

NodeB

NodeB NodeB

SR

10 11 10

OLT

OLT FTTH user

OLT FTTH user

FTTH user

QinQ

10

11

10

Enterprise

VPLS

Key account services

VLAN IDs on the PON

network

2G/3G base stations

Page 5: 2-Networking and Planning

5

Contents

1. Network Building Requirements

2. Networking and Planning

3. Experimental Network Planning Examples

Page 6: 2-Networking and Planning

6

NodeB

BTS

NodeB

FE

PWE3

FE

R

R R

R

R

R

RNC

GE POS

GE POS

R

R R

R

Core

layer

Distribution

layer Access

layer

RNC

Access

layer

Core layer: accesses traffic from the distribution layer. It serves as the service system gateway and schedules

entire traffic comprehensively. A few network nodes exist at this layer and the bandwidth pressure is large.

Recommended network mode: dual-uplink, mesh, or rectangle-shape network

Access layer: accesses services from base stations. Numerous network nodes exist at this layer and the

bandwidth pressure is small.

Recommended network mode: ring, chain, or dual-uplink network

Distribution layer: converges traffic and ports, with powerful dynamic scheduling capability. Many network nodes

exist at this layer and the bandwidth pressure is relatively large.

Recommended network mode: ring or dual-uplink network

Hierarchical Architecture of METRO-E

Page 7: 2-Networking and Planning

7

Network Topology Planning for the

Access Layer of METRO-E

R845 R860 R845

R860

R860

R860

R845

R845

Ring network Dual-homing

network

Ring and chain

network

Chain

network

Page 8: 2-Networking and Planning

8

Staged Bandwidth Requirement

Calculation for the Access Layer

Assume that each access chain or ring contains 10 access points and each 3G node provides the access

service for 3000-5000 users. It can be calculated that the capacity of each NodeB is 30 Mbit/s and will be

expanded to 50 Mbit/s at the later stage based on the CS 16.4 kbit/s, CS 64 kbit/s, PS, and relevant

overheads. The analysis is as follows:

Early stage: Each access point is connected to only one 3G NodeB. The bandwidth usage is 30%

(that is, 30 x 10/GE) and the interfaces are 1FE+2E1s.

Middle stage: One 3G NodeB, one 2G BTS (4 Mbit/s), and 2 private lines (or NGN AGs) will be

connected. The bandwidth usage is 74%, that is, (30M + 4 + 20 x 2) x 10/1 GE, and the interfaces are

3FEs+4E1s.

Later stage: The network will be expanded to a 10G ring network, which covers four 3G NodeBs, two

2G BTSs, three private line services, and three Ethernet services. The bandwidth usage is 33%, that

is, (50 x 4 + 2 x 4 + 3 x 20 + 3 x 30M x 50%) x 10/10G, and the interfaces are 10 FEs+12E1s.

Service

Type

3G NodeB 2G BTS Private Line

(AG)

Ethernet

Capacity 30 (50) Mbit/s 4 Mbit/s 20 Mbit/s 30 Mbit/s

Interface 1FE+2E1s 2E1s 1FE 1FE

Convergence N/A N/A N/A 50%

Page 9: 2-Networking and Planning

9

Network Topology Planning for the Distribution

Layer of METRO-E

Dual-homed core devices will be used for network building at the later stage if the capital

resource is sufficient. The purpose is to reduce the network load and enhance network security.

Page 10: 2-Networking and Planning

10

Staged Bandwidth Requirement

Calculation for the Distribution Layer

Stage I

Service Quantity Bandwidth

(Gbit/s)

Convergence

Ratio

Total

Bandwidth

(Gbit/s)

Access ring GE ring 10 1 0.5 5

Ethernet

private line

(EPL)

FE 6 0.1 0.5 0.3

OLT 2 * GE 6 2 0.1 1.2

Total

bandwidth 6.5

Stage 2

Service Quantity Bandwidth

(Gbit/s)

Convergence

Ratio

Total

Bandwidth

(Gbit/s)

Access ring GE ring 10 1 0.5 5

EPL FE 12 0.1 0.5 0.6

OLT 2 * GE 12 2 0.1 2.4

Total

bandwidth 8

Stage 3

Service Quantity Bandwidth

(Gbit/s)

Convergence

Ratio

Total

Bandwidth

(Gbit/s)

Access ring 10GE ring 4 10 0.5 20

EPL FE 12 0.1 0.5 0.6

OLT 10GE 12 10 0.1 12

Total

bandwidth 32.6

Bandwidth

usage: 65%

Assume that each convergence ring accommodates a maximum of six nodes.

Bandwidth

usage: 80%

Bandwidth

usage: 50%

Page 11: 2-Networking and Planning

11

Network Topology Planning for

the Core Layer

MESH

Ring

The ring networking mode is recommended at the initial stage. The network can be upgraded to a mesh network based on

the optical fiber laying status to enhance the network robustness and security. It is recommended that the distribution layer

and core layer be integrated into one layer to form a mesh or rectangle-shape network if conditions permit.

RNC

RNC

RNC

Dual-homing

network

Page 12: 2-Networking and Planning

12

Basic Principles for IP Address Planning

No address can be duplicated

with other addresses on the

same network.

Certain addresses need to be reserved for future device expansion.

IP addresses must be fully used based on the

minimum use principle to avoid wastes. For

example, interface interconnection addresses

can use 30-bit mask addresses.

The counterclockwise allocation mode

and the principle of allocating IP

addresses from the core layer to the

access layer ensure the continuity and

aggregation of IP addresses.

IP address allocation conforms

to certain principles and useful

information can be obtained

from IP addresses.

Uniqueness

Continuity Expansibility

Economization Meaningfulness

Page 13: 2-Networking and Planning

13

IP Address Classification in Network Planning

The system administrator creates one loopback interface for each router and allocates a

separate IP address for the interface as the management address to facilitate management.

Interconnection addresses refer to the addresses used by interfaces for connecting two or

more network devices.

Service addresses refer to the addresses used by connected servers and hosts on the

Ethernet and gateway addresses.

Loopback addresses

Service addresses

Interconnection addresses

Page 14: 2-Networking and Planning

14

Example of Device Address Allocation

(Loopback Addresses)

Allocate IP addresses to devices based

on the network hierarchy, for example,

allocate IP addresses to devices at the

co re l aye r , distribution layer , and

access layer from small to large.

Allocate addresses by ring number (ring

1, ring 2, ...) and allocate addresses in

counterclockwise direction in rings.

Adopt the principle of rings first and

then chains.

Make reservations during address

allocation.

Use 32-bit masks for device addresses.

In principle, device addresses are

determined during network design

planning.

R1 R4

R3 R2

R5

R9

R6

R10 R7

R8

10.229.0.1/32 10.229.0.4/32

10.229.0.3/32 10.229.0.2/32

10.229.1.1/32 10.229.1.2/32

10.229.2.4/32

10.229.2.3/32 10.229.2.2/32

10.229.2.1/32

Core

layer

Distribution

layer

Access

layer

Page 15: 2-Networking and Planning

15

Example of Interconnection

Address Allocation

Allocate interconnection addresses based

on the network hierarchy and allocate IP

addresses to interconnection interfaces

from small to large.

Allocate addresses by ring number and

allocate addresses in counterclockwise

direction in rings. Adopt the principle of

rings first and then chains.

Make reservations during address

allocation.

Use 30-bit masks for interconnection

addresses.

R1 R4

R3 R2

R5

R9

R6

R10 R7

R8

10.254.0.1/30 10.254.0.10/30

10.254.0.9/30 10.254.0.2/30

10.254.2.1/30

10.254.8.1/30

Core

layer

Distribution

layer

Access

layer

10.254.0.13/30 10.254.0.14/30

10.254.2.2/30 10.254.2.9/30

10.254.2.10/30

10.254.8.2/30

10.254.8.5/30

10.254.8.6/30

10.254.8.9/30 10.254.8.10/30

10.254.8.13/30

10.254.8.14/30

10.254.8.17/30

10.254.8.18/30

Page 16: 2-Networking and Planning

16

Example of Service Address Allocation

RNC addresses and NodeB

addresses must be in different IP

address network segments in the

service address allocation.

Use 30-bit masks for service

addresses.

In principle, service addresses are

provided by the service side.

R1 R4

R3 R2

R5

R9

R6

R10 R7

R8

Core

layer

Distribution

layer

Access

layer

172.21.202.5/30

172.21.209.25/30

172.21.209.26/30

172.21.209.29/30

172.21.209.30/30

172.21.202.6/30

RNC

Node B

Page 17: 2-Networking and Planning

17

Service Application Provisioning and Planning

Service Planning — Service IP Address Planning

L3 throughout

the network

IP address planning:

Allocate IP addresses by ring and follow the principle of

rings first and then chains. Allocate IP addresses in

counterclockwise direction in rings and adopt the mode

of odds up and evens down, odds on the left and evens

on the right for address allocation in rings. Increase IP

addresses from the near to the distant in tributary

chains.

Use 30-bit masks for IP addresses of ports (minimum

subnet).

Make reservations during address allocation.

The principles of IP address allocation in a single ring

are as follows:

Allocate address blocks to loopback interfaces.

Allocate 30-bit IP addresses in counterclockwise

direction in each ring. Ensure the continuity of IP

addresses for route convergence under address

conservation.

Allocate at least one network segment and two IP

addresses to each base station.

IP:

20.1.1.1/29

IP:

10.1.1.1/30

IP:

10.1.1.5/30

IP:

10.1.1.9/30

IP:

10.1.1.2/30

IP:

10.1.1.10/30

IP:

10.1.1.6/30

Each base station uses one

independent network segment

Page 18: 2-Networking and Planning

18

Example of IP Address Allocation in

NE Management

Core layer

Distribution

layer

Access layer

R2 R1

R3 R4 R5

R6 R8

R7

R13

R12

R10

R9

R14 R16

R17

R15

R18

R20

R11

R19

12.3.254.1

12.2.254.1 12.1.254.1

12.4.254.1

12.6.254.1

12.5.254.1

12.7.254.1

12.8.254.1

12.9.254.1

12.10.254.1

12.11.254.1

12.6.1.1

12.6.2.1

12.6.3.1

12.8.1.1

12.8.2.1

12.8.3.1

12.10.1.1

12.10.2.1

12.10.3.1

Page 19: 2-Networking and Planning

19

IP Routing Protocol Planning Principles

The core layer and distribution layer are configured as the backbone area (L2 router).

Each ring at the access layer is configured as an AS domain.

Objective: To make the network hierarchy clear for network convergence and

ease of network operation.

ISIS 1000

ISIS 1

ISIS 100 ISIS160

Page 20: 2-Networking and Planning

20

SMART CEN PROJECT

Page 21: 2-Networking and Planning

21

Page 22: 2-Networking and Planning

22

BTS Services Using TDM — End to End PWE3

BSC BTS

E1

GE 10GE

E1

L2VPN

Access layer Distribution

layer

Convergence at the

backbone layer

MPLS-TP OAM

LSP1:1 + PW FRR

Service bearer

OAM

Protection

technologies

TDM Data TDM Data

PW Label

Tunnel Label

Ethernet Header

Control Word

RTP Header

(optional)

TDM Data

Page 23: 2-Networking and Planning

23

Service Bearer on Ethernet NodeBs

— 3G NodeBs

RNC

FE

GE 10GE

FE

L3VPN L3VPN

NodeB

VPN FRR+LDP FRR/CR-

LSP 1:1+(TE FRR)

VPN FRR+LDP FRR/

CR-LSP 1:1+(TE FRR) VRRP/IP FRR

Service

bearer

Protection

technologies

Access layer Distribution

layer

Convergence at the

backbone layer

Payload

Ethernet header

Ethernet header

Payload

VRF label

VP label

Ethernet header

Payload

VRF label

VP label

Ethernet header

Payload

Page 24: 2-Networking and Planning

24

LSP 1:1 Protection

Services are transmitted through the active LSP in normal cases. When the active LSP is

faulty, services are switched to the standby LSP for transmission.

BFD or MPLS OAM is used as the fault detection mechanism.

LSP protection can be understood as one group of bidirectional protection composed of

two groups of unidirectional protection.

Active path

Active path

Standby path

Standby path

a) Normal working status

b) Fault status

Subnet

Subnet

Subnet

Subnet

Page 25: 2-Networking and Planning

25

PW Protection

BFD is used to detect PW faults quickly to implement OAM mapping between PWs

and ACs.

In this way, when a PW or PE is faulty, CEs can switch services to the standby path

to enable end-to-end fault detection for the PW and implement PW backup, greatly

enhancing the reliability of the L2 VPN.

Active

Backbone

network

Standby

Page 26: 2-Networking and Planning

26

Contents

1. Network Building Requirements

2. Networking and Planning

3. Experimental Network Planning Examples

Page 27: 2-Networking and Planning

27

Network Topology Planning — Topology of the

Experimental Network

A total of 19 ring systems are built in this project, including three 10GE rings

at the distribution layer and 16 GE rings at the access layer. Some tributary

chains are built and no more than 2 nodes exist on each tributary chain.

Networking idea for the core distribution layer: Three core equipment rooms

and nine convergence equipment rooms form three 10GE core convergence

rings, to improve the bandwidth usage of rings and enhance network

security.

Networking idea for the access layer: The access layer is connected to the

core convergence rings in dual-uplink mode to enhance the network

security. Reorganize the network if the line routes and logic structure are

unreasonable.

Core

Distribution

Layer

CiTRANS R860

Access Layer

CiTRANS

R845

Quantity 17 114

Gaode

Dianchang Shixian ring

10GE Dual-node

ring ZhangwuDual-node

ring

Xinqiu

South ring

10GE

Shiju 2

Shiju 1Yingbinju 1

Yingbinju 2

Xiyuan 1

Xiyuan 2

Qinghemen

Shibei

North Central

10GEdongyuan 2

Fuxinxian

Zhanqian

Page 28: 2-Networking and Planning

28

IP Address and Routing Protocol Planning — IP Address Allocation

Allocate one address segment 10.229.0.0/17 to loopback interfaces on network devices in the Fuxin

office.

Allocate the smallest four address segments 10.229.0.0/22 to the core layer and distribution layer.

Use the IP addresses 10.229.0.0/30 to 10.229.1.255/30.

Reserve the IP addresses 10.229.2.0/30 to 10.229.3.255/30.

Allocate four address segments to each converged access device.

Use the IP addresses 10.229.4.0/22 to 10.229.124.0/22.

Reserve the IP addresses 10.229.125.0 to 10.229.127.0.

City IP Address

Segment

Number of IP

Addresses

Number of Physical Sites

on the Live Network

City A 10.229.0.0/17 32768 391

Configuration requirements of service IP addresses: 1. Service-side IP addresses of devices are allocated by the access side system.

2. It is recommended that 30-bit mask addresses be used as interconnection addresses.

3. Loopback addresses are allocated by carriers.

Page 29: 2-Networking and Planning

29

IP Address and Routing Protocol Planning — Example

Dianchang Yingbinju

Shiju

Xinqiu

Gaode

Xiyuan Zhanqian

RNC2

RNC1

Node B1

Node B2

IP Address Planning

• Core distribution layer:

Allocation: 10.229.0.0-10.229.1.255/30

Reservation: 10.229.2.0-10.229.3.255

Loopback address: 10.229.0.0/32

Yingbinju office: 10.229.0.1/32

Xiyuan office: 10.229.0.2/32

Qinghemen office: 10.229.0.3/32

...

• Access layer: Allocation: 10.229.4.0/22-10.229.61.0/22

Reservation: 10.229.62.0/22-

10.229.127.0/22

Loopback address: 10.229.62.0/22-

10.229.127.0/22

Access point A: 10.229.4.1/32

Access point B: 10.229.4.2/32

Access point C: 10.229.4.3/32

...

A B

C

Routing protocol planning

• IGP: OSPF Domain division: core distribution layer: Area 0; access

layer: Area 1/2/3/4...

Router ID/Cost/Priority/Loopback/CIDR

• EGP: BGP: RSVP: LDP Use loopback addresses to set up the BGP neighbor

relationship.

Set RR on bridge nodes such as Xinqiu and Gaode.

Page 30: 2-Networking and Planning

30

Service Provisioning — Service IP Address Planning (with METRO-E of Fuxin as an Example)

Liangku

R845 10.229.4.4/32

Kuangjidianzongchang

R845

10.229.4.3/32

Gongchengchu

R845 10.229.4.5/32

Jixiuchang

R845 10.229.4.2/32

Zhanqian

R860 10.229.4.1/32

Xiyuan

R860 10.229.0.2/32

Yingbinju-1

R860 10 .229.0.1/32

XGE0/11/2

10.254.0.2/30

XGE0/8/2

10.254.0.1/30

XGE0/12/2

10.254.0.5/30

XGE0/7/2

10.254.0.6/30

XGE0/12/1

10.254.8.1/30

GE0/12/3

10.254.8.21/30

XGE0/8/1

10.254.8.2/30

GE0/11/3

10.254.8.6/30

GE0/10/1

10.254.8.10/30

GE0/10/1

10.254.8.13/30

GE0/10/1

10.254.8.17/30

GE0/11/1

10.254.8.22/30

GE0/11/1

10.254.8.18/30

GE0/11/1

10.254.8.14/30

GE0/11/1

10.254.8.9/30

Shibei

R860 10.229.0.4/32

Shiju-1

R860 10.229.0.6/32

Qinghemen

R860 10.229.0.3/32

Shibeimiaopu

R845 10.229.5.1/32

XGE0/11/2

10.254.0.10/30

XGE0/8/1

10.254.0.9/30

XGE0/11/1

10.254.0.18/30

XGE0/12/2

10.254.0.26/30

XGE0/7/2

10.254.0.25/30

GE0/8/3

10.254.9.1/30

GE0/10/1

10.254.9.2/30

XGE0/8/1

10.254.0.17/30

XGE0/8/2

10.254.0.21/30

GE0/10/1

10.254.8.5/30

Dongyuan

R860 10.229.0.5/32

XGE0/11/1

10.254.0.22/30

Yingbinju-2

R860 10 .229.0.7/32

Shiju-2

R860 10 .229.0.8/32

XGE0/11/1

10.254.0.38/30

XGE0/8/1

10.254.0.37/30

XGE0/8/1

10.254.0.42/30

XGE0/11/1

10.254.0.41/30

XGE0/11/1

10.254.0.30/30

XGE0/8/1

10.254.0.29/30

XGE0/8/1

10.254.0.34/30

XGE0/11/1

10.254.0.33/30

Shibeimiaopu

Base station 172.21.205..30/30

10.9.11.33/32

FE1/24/1 172.21.205.29/30

Jixiuchang

Base station 172.21.205..38/30

10.9.11.34/32

FE0/8/1 172.21.205.37/30

Liangku

Base station 172.21.205..34/30

10.9.11.26/32 FE0/8/1 172.21.205.33/30

Gongchengchu

Base station 172.21.205..42/30

10.9.11.5/32

FE0/8/1 172.21.205.41/30

Yingbinju

RNC 172.21.202.30/30

10.9.1.145/28

Loopback address planning:

Core distribution layer:

10.229.0.0/32----10.229.1.255/32

10.229.2.0/32----10.229.3.255/32(reserved)

Access layer

10.229.4.0/22----10.229.61.0/22

10.229.62.0/22----10.229.127.0/22(reserved)

Interface IP address planning:

Core distribution layer:

10.254.0.0/32----10.254.3.255/32

10.254.4.0/32----10.254.7.255/32(reserved)

Access layer

10.254.8.0/21----10.254.120.0/21

10.254.128.0/17(reserved)

XGE0/11/1

10.254.0.14/30

XGE0/8/1

10.254.0.13/30

Service IP address planning:

RNC:172.21.202.30/30

Base stations (even number), METRO-E(odd number):

172.21.205.0/30----172.21.205.255/30

XGE0/8/2

10.254.10.2/30

XGE0/8/2

10.254.10.1/30

GE0/11/3 172.21.202.25/30

GE0/11/3 172.21.202.29/30

Hengye'erqi

Base station 172.21.205..46/30

10.9.11.28/32

FE1/24/1 172.21.205.45/30

Hengye'erqi

R845 10.229.6.1/32

Page 31: 2-Networking and Planning

31

THANK YOU