Mstp+ network design service product v100 r001 delivery guide(20100127)

Delivery Guide (20100127)
MSTP+ Network Design Service Product
V100R001
Issue 1.0
Date 2010-03-15
INTERNAL
HUAWEI TECHNOLOGIES CO., LTD.

INTERNAL
MSTP+ Network Design Service Product V100R001
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service.
Please feel free to contact our local office or company headquarters.
Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Copyright © Huawei Technologies Co., Ltd. 2010. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Issue 1.0 (2010-03-15) HUAWEI Confidential Page 2 of 38

INTERNAL
About This Document
Author
Prepared by He Wan Date 2010-01-10
Reviewed by Date
Reviewed by Date
Approved by Date
History
Issue Details Date Author
Completed the initial draft. 2010-01-10 He Wan

INTERNAL
Contents
1 Overall Delivery Process.............................................................................................................8
2 Structure Design of the MSTP+ Network.............................................................................10
2.1 Information Collection and Analysis.....................................................................................................................10
2.1.1 Flow Chart.......................................................................................................................................................10
2.1.2 Data Collection................................................................................................................................................11
2.1.3 Data Analysis...................................................................................................................................................14
2.2 Network Object Naming Design...........................................................................................................................15
2.2.1 Flow Chart.......................................................................................................................................................15
2.2.2 Design Procedure.............................................................................................................................................15
2.3 Network Interconnection Design (NNI Interconnection Design)..........................................................................16
2.3.1 Flow Chart.......................................................................................................................................................16
2.3.3 Outputs.............................................................................................................................................................18
2.4 Network Interconnection Design (UNI Interconnection)......................................................................................19
2.4.1 Flow Chart.......................................................................................................................................................19
2.4.3 Outputs.............................................................................................................................................................21
2.5 MPLS Design (Available Tools) ...........................................................................................................................21
2.5.1 Flow Chart.......................................................................................................................................................21
2.5.3 Output..............................................................................................................................................................22
2.6 DCN Design (Optional).........................................................................................................................................22
2.6.1 Flow Chart.......................................................................................................................................................22
2.7 Clock Synchronization Design (Optional)............................................................................................................23
2.7.1 Flow Chart.......................................................................................................................................................23
3 MSTP+ Service Design..............................................................................................................26
3.1 Tunnel Design (Available Tools)...........................................................................................................................26
3.1.1 Flow Chart.......................................................................................................................................................26

INTERNAL
3.1.3 Outputs.............................................................................................................................................................28
3.2 Service Access Design...........................................................................................................................................28
3.2.1 Flow Chart.......................................................................................................................................................28
3.2.3 Outputs.............................................................................................................................................................29
3.3 Label Design (Available Tools) ............................................................................................................................30
3.3.1 Flow Chart.......................................................................................................................................................30
3.3.3 Outputs.............................................................................................................................................................30
3.4 QoS Design (Optional)..........................................................................................................................................31
3.4.1 Flow Chart.......................................................................................................................................................31
3.4.2 Design Principles.............................................................................................................................................31
3.5 Design Acceptance (Optional)...............................................................................................................................36
3.5.1 Flow Chart.......................................................................................................................................................36
3.5.2 Deliverables.....................................................................................................................................................36
4 References....................................................................................................................................37
5 Acronyms and Abbreviations..................................................................................................38

INTERNAL
Figures
Overall delivery process..................................................................................................................8
Configuration process when the SSM protocol is not started ..............................................24
Configuration process when the standard SSM protocol is started ....................................24
Configuration process when the extended SSM protocol is started....................................25

INTERNAL
Tables
Parameter description....................................................................................................................33
Acronyms and abbreviations ......................................................................................................38

INTERNAL
1 Overall Delivery Process
Figure 1.1 shows the overall delivery process of the MSTP+ network design.
Figure 1.1 Overall delivery process
On the MSTP+ network, MPLS PWs carry services and the tunnel adopts the static signaling
type. Services that are carried by the MSTP+ network are classified into E-Line services and
E-LAN services. For the detailed operations of each step, see the following contents.
 The MSTP+ network design involved in this guide only indicates the design of the packet switching
plane.
 This document does not specify the use description of the EXCEL design tool MSTP+ Design Tool
V1.0 involved in this document. For the use description, see the MSTP+ Design Tool V1.0 Use
Description.
 The outputs (PPT and EXCEL files) involved in each step need to be integrated into three complete
deliverables: MSTP+ Network Design for XX Project.ppt, Detailed Design of the MSTP+ Network
for XX Project.xls, and NE Slot Configuration List of the MSTP+ Network for XX Project.xls. The
contents in each document are as follows:
SN Deliverable Content Format
1 Detailed Design of the
MSTP+ Network for XX
01_Basic NE information Excel
2 02_NNI link Excel

INTERNAL
SN Deliverable Content Format
Project.xls3 03_NNI port Excel
4 04_MPLS OAM parameter Excel
5 05_Tunnel APS Excel
6 06_Tunnel Excel
7 07_Tunnel routing Excel
8 08_PW label planning Excel
9 09_Tunnel label planning Excel
10 10_Service parameter Excel
14 MSTP+ Network
Design for XX
Project.ppt
Network topology fiber connection diagram PPT
15 MPLS parameter design drawing PPT
16 NE UNI interconnection design drawing PPT
17 NE front panel diagram PPT
18 QoS design PPT
19 DCN design drawing PPT
20 Synchronization design (clock tracing)
drawing
PPT
21 NE Slot Configuration
List of the MSTP+
Network for XX
Project.xls
01_NE list Excel
22 02_Packet switching slot configuration Excel
23 03_Statistics on number of packet
switching boards and ports
Excel
24 04_List of packet switching ports Excel
25 05_UNI interconnection information Excel
26 MSTP+ Network
Design Report for XX
Project (Optional)
Network design report Word
27 Network design slide PPT

INTERNAL
2 Structure Design of the MSTP+ Network
2.1 Information Collection and Analysis
2.1.1 Flow Chart

INTERNAL
2.1.2 Data Collection
HLD Document
The HLD document provided by the Marketing department covers the following contents:
 HLD service requirement: indicates the end-to-end service requirements of the MSTP+
network.
HLD Ser vi ce
Requi r ement Li st . xl s
The meanings of the fields are described as follows:
− Column A: lists the Pop sites, namely, the OSN devices of the service access sites.
− Column B: lists the number of base stations, namely, the number of base stations
mounted under the Pop site.
− Column C/D: indicates the traffic between the Pop site and the RNC site. The two
RNCs are respectively in column C and column D.
 HLD networking solution: indicates the MSTP+ networking diagram. The diagram in the
PPT format is preferred.
 HLD NE board configuration list (from Quoter/BoQ): indicates the configuration
information on all NEs and boards. The formats are as follows:
HLD Sl ot
Conf i gur at i on Li st . xl s
NE Panel
Di agr am. ppt
 IP resource information: indicates the IP resources that can be used for designing the
MSTP+ network.
 Service (network) protection requirement: indicates the protection type of the MSTP+
network.
 UNI port protection requirement: indicates the port protection type adopted for
interconnection between the MSTP+ network and NodeB, RNC, and RTN.
LLD Service Requirements (UNI-UNI)
LLD service requirements indicate the end-to-end service requirements in the entire network
(instead of the MSTP+ network), for example, the traffic from a NodeB to an RNC.
Provide the LLD service requirements in the following formats (example):
OSN- NodeB
Aggr egat i on Rel at i onshi p. xl s
The meanings of the fields are described as follows:
 Column A: lists the name of an RNC site, indicating that the OSN device is
interconnected with the RNC. Services are converged into the OSN device and are
transmitted to the RNC site.
 Column B: lists the names of radio devices, indicating that the services submitted by the

INTERNAL
radio device are transmitted to the RNC listed in column A.
 Column C: lists the name of the wireless base station, indicating that the base station is
mounted under the radio device listed in column B.
 Column D: lists the VLAN ID of the wireless base station service.
 Column E: lists the VLAN ID of the OM service.
 Column F: indicates the peak bandwidth of the NodeB service requirement.
 Column G: lists the OSN device of the service access site. The radio device listed in
column B is mounted to this service access site.
 Column H: lists the Popsite port interconnected with the radio device. Field engineers
report the information about the port in two forms:
− If the port interconnected with the radio device is specified, the information format is:
"s" + slot number + "p" + port number. For example, s3p15.
− Assume that the port interconnected with the radio device is not specified. When only
the number of ports and rate level are specified and the specific port needs to be
specified by the designer, the format is as follows:
Name the port of each NE by following the naming rule and identify the ports by
different numbers. For example, the name of the port of the following DXB0053 site
interconnected with the radio device is as follows:
The file indicates that the DXB0053 site has a GE port and four FE ports that are
respectively interconnected with the radio device. Designers can specify the ports
according to the file.
 Columns I and J: list the ports of the RNC interconnected with the OSN. The information
about the ports on the OSN device is in the same format as that of the Popsite port.
The procedure is summarized as follows:
Services with VLAN ID (in column D) are transmitted to the radio device (listed in column
B) through the wireless base station (in column C). The services are accessed to Popsite (in
column G) through the Popsite port (column H). Then, the services arrive at the OSN device
(column A) of the RNC site through the MSTP+ network and are finally transmitted to the
RNC.
All the fields in the LLD service requirement table are configurable. Take the name of the radio site
listed in column B as an example. If the radio device does not exist in the network, there is no need to
collect the relevant information and column B can be ignored. Similarly, if the RNC site or base station
does not exist, the relevant columns can also be ignored.
Sometimes, the terminal device is a mobile phone or other network rather than a base station. A format
for collecting the LLD service requirements is provided. The format cannot be regarded as a template.
The follow-up contents in this document take the fields involved in the LLD service requirements table
as an example.

INTERNAL
OM Service Requirements
1. Specify the device types in the entire network, for example, NodeB, RTN, or OSN.
2. Specify the devices, whose OMs must be transmitted through the MSTP+ network.
Then, collect the relevant end-to-end service requirements of the OMs, such as NodeB.
3. For the RTN or OSN that may possibly use the in-band DCN devices, specify whether
the DCN device is in-band or out-band. If the out-band DCN device is adopted, in
addition to collecting the end-to-end service requirements, you need to confirm whether
the independent tunnel or line is required for carrying the services, and you also need to
confirm the service type (E-LAN/E-LINE), protection, and VLAN ID.
DCN Network Information
Understand the design of the MSTP+ DCN NMS and the customer DCN NMS requirements
described in the HLD.
In the specific project, the DCN design may not be involved. The DCN design may be
involved in the scope of the TDM plane design instead of the packet switching plane design.
Information About the Clock Sources
Obtain the available synchronized clock resources. This part may be excluded during the
packet switching plane design.
QoS Requirements
When conducting network design based on peak traffic of service requirements, you need not
consider QoS-related factors.
QoS requirements including that on both the base station side and the radio side:
 Service Classification
− OM services and other services (including the SIG, User Data, and Others) on the
wireless side
Adopt the different VLAN IDs.
− The OM services are not segmented into sub-categories.
− The SIG, User Data, and Others adopt the IP DSCP to identify sub-categories, as
shown in the following table.
 Service Priority
For details, see the following table:
PHB Service Class PHB Service Quality
BE Best-Effort model is the default service model in the current
Internet. This model adopts the first in first out (FIFO) technology.
The PHB service level is adopted by default. The value of DSCP is
000000.
AF1 These service levels ensure the forwarding quality of the traffic
within the specified range and downgrade the forwarding quality
of the traffic beyond the specified range. The traffic beyond the
specified range is not simply discarded.
AF2
AF3

INTERNAL
PHB Service Class PHB Service Quality
Each AF level is further classified into three discarding priorities
(colors). For example, the AF1 level can be further classified into
the following discarding priorities:
AF11: corresponds to the green priority. The traffic of this priority
can be transmitted normally.
AF12: corresponds to the yellow priority. When network
congestion occurs, the packet of this priority is discarded
according to certain rules.
AF13: corresponds to the red priority. The packet of this priority is
first discarded.
AF4
EF These service levels require that the rate of the traffic sent from
any DS node should not be less than the specified rate in any
conditions.
These service levels simulate the forwarding effect of a virtual
leased line. In this manner, the forwarding service of low packet
loss ratio, low delay, and high bandwidth can be provided. These
PHB service levels are applicable to video services and VoIP
services.
CS indicates the class selection code. The service level is the same
as the IP precedence. The value of the DSCP is XXX000.
CS6
CS7
2.1.3 Data Analysis
1. Draw the networking in PPT format according to the HLD networking. If the networking
diagram provided by the Marketing Department is in PPT format, you only need to
arrange the layout and check the NE name, ring name, and rate level. For example,
Net wor ki ng
Di agr am. ppt
2. List the configuration information about all the NEs, slots, types, and numbers according
to the "HLD NE board configuration list". For example, worksheets 03 and 04 in the
following attachment are arranged according to worksheets 01 and 02.
NE Sl ot

INTERNAL
2.2 Network Object Naming Design
2.2.1 Flow Chart
2.2.2 Design Procedure
1. Rule for naming NEs:
Name the NEs according to the customer requirements.
If the customer does not have any requirement, name the NE according to the original
NE naming rule of the customer.
2. Rule for naming tunnel APSs:
Suggested rule: "Service type:RNC site name---Access site name"
For example, 3G:DXB6004---DXB1114.
3. Rules for naming services:
Name the services according to the customer requirements or service classification.
For example, 3G, WCDMA, Voice, Video, and OM.
4. Rule for naming tunnels:
Suggested positive rule: "Service type:RNC site name---Access site
name:Working/Protection:Positive"
Suggested negative rule: "Service type:Access site name---RNC site
name:Working/Protection:Negative"
For example,
3G:DXB6004---DXB1114:Working:Positive
3G:DXB1114---DXB6004:Working:Negative
3G:DXB6004---DXB1114:Protection:Positive

INTERNAL
3G:DXB1114---DXB6004:Protection:Negative
5. Rule for naming ports:
Suggested rule: "s+Slot number+p+Port number"
For example, s3p5, indicating slot 3 and port 5.
6. Rule for naming links:
Suggested rule: "Source NE name-Port name<>Sink NE-Port name"
It is suggested that all "source NEs" are either greater or smaller than the "sink NEs" in
the EXCEL and values of source NEs and sink NEs can be compared in the EXCEL.
For example, DXB5001-s13p1<>DIC4#1-s3p1
The MSTP+ Design Tool V1.0 contains partial contents of naming rules. The names of the
"APS/Tunnel/Port" generated during the design are generated according to the previous suggested rules.
2.3 Network Interconnection Design (NNI Interconnection
Design)
2.3.1 Flow Chart

INTERNAL
The MSTP+ Design Tool V1.0 can be used for the performance measurement on the NNI
interconnection design port. For the input and result examples of the tool, see chapter 4 References and
Attachments.
Step 1 Open the MSTP+ Design Tool V1.0. On the displayed 00-Cover page, select Initial Table.
Step 2 For the fields required in the "01-NE BasicInfo" worksheet of the MSTP+ Design Tool V1.0,
copy them from the "01_NE list" worksheet in NE Slot Configuration List.xls. Columns D
and E in the MSTP+ Design Tool V1.0 can be omitted.
Step 3 For the fields required in the "02-NEBoardConfigure" worksheet of the MSTP+ Design Tool
V1.0, copy them from the "01_Packet switching slot configuration" worksheet in NE Slot
Configuration List.xls. Columns C and D in the MSTP+ Design Tool V1.0 can be omitted if
no content is involved.
Step 4 Open the "00-Cover" worksheet of the MSTP+ Design Tool V1.0, and click the following
buttons in sequence:
Information about all ports can be obtained in the "07-EthernetPortList" worksheet.
Step 5 Allocate boards and ports according to the Networking diagram.ppt file obtained through
the information analysis and the "07-EtherenetPortList" worksheet generated by the MSTP+
Design Tool V1.0. Mark the boards and ports in the networking diagram and fill in the
allocation results to the "06-Ethernet Link(NNI)" worksheet of the MSTP+ Design Tool V1.0.
"06-Ethernet Link(NNI)" is the NNI link worksheet required.
The networking of the allocated ports is as follows:
Fi ber
Connect i on- NNI Li nk. ppt
Step 6 Open the "00-Cover" worksheet of the MSTP+ Design Tool V1.0. Click the button marked in
red to obtain the information about all NNI ports from the "11-NNIPortList" worksheet.
Meanwhile, the relevant NNI ports in column H of the "07-EthernetPortList" worksheet are
labeled with "NNI".
If the number of ports of a certain type is insufficient during the NNI port allocation, you need to change
the board type or even change the NE type.
Conform to the following principles to fill in the "06-Ethernet Link(NNI)" worksheet:

INTERNAL
 Design links before rings.
 Design rings in clockwise or anti-clockwise direction.
The advantages of the previous principles are that links or rings will not be missed during the design and
the design can provide reference for the follow-up APS ring design.
Step 7 Analyze the following two scenarios according to the HLD service requirements:
 Check whether the link capacity on both ends of the convergence node (for example, the
OSN NE interconnected with the RNC) is less than the total capacity converged to the
node (after calculating the convergence rate). If the link capacity is less than the total
capacity, modify the HLD solution.
 Check the link capacity between two nodes crossing a ring. For example, node A of
Ring-1 is connected to node A' of Ring-2. Three GE links exist between node A and node
A'. Check the number of GE ports for the service capacity between Ring-1 and Ring-2.
For example, if 4G traffic is involved between X and Y, the link capacity between node A
and node A' is insufficient.
----End
2.3.3 Outputs
1. NNI Interconnection.ppt
2. NNI link list (namely, "06-Ethernet Link (NNI)" in the MSTP+ Design Tool V1.0)
3. NNI port list (namely, "11-NNI Port List" in the MSTP+ Design Tool V1.0)
4. Packet switching port statistics list (namely, "07-Ethernet Port List" in the MSTP+
Design Tool V1.0)

INTERNAL
2.4 Network Interconnection Design (UNI
Interconnection)
2.4.1 Flow Chart
Step 1 Prepare the LLD service requirement table, namely, the information about all the
interconnections with the customer equipment, such as RNC, RTN, NodeB, and Router
contained from column H to column I in the OSN NE–NodeB convergence relation
worksheet. The information covers:
 Number of interconnected ports
 Types of interconnected ports
Step 2 Because the number of ports interconnected with the RNC/Router is small, the
interconnection diagram can be drawn. According to the interconnection protection type
specified by the interconnection solution with the customer equipment, you can label the
allocated ports and the protection modes.
Example:
Fi ber
Connect i on- UNI I nt er connect i on. ppt
Step 3 Generally, the number of ports connected to the RTN or NodeB is great. Allocate the ports as
follows:
 Completely copy "OSN-NodeB convergence relation.xls" to "NE slot configuration
list.xls" obtained after the information analysis, and then name the list as "05_UNI NE
interconnection."
 Identify the NNI port of column G in the "04_List of packet switching ports" worksheet
in NE Slot Configuration List.xls. Identify other ports as "Free".

INTERNAL
 Add column H in the "04_List of packet switching ports" worksheet and name the
column with any field. (Here, "Usage" is used as the column name.) The fields that are
"NNI" in column G are still "NNI" in column H, but the fields that are "Free" in column
G are named as "Rate level-Port-Number". Ports on one NE with the same rate level are
arranged in ascending order, for example, GE-Port-1, GE-Port-2, …, GE-Port-N. After
the ports of an NE are numbered, arrange the numbers of ports of another NE whose
column G is "Free" from GE-Port-1 or FE-Port-1.
 In column I, integrate the NE name in column A and "Usage" in column H to make each
field unique.
 In column J, integrate the fields in columns D and E according to the port naming rule to
form the port fields.
 In column K of the "05_UNI NE interconnection" worksheet, run the vlookup function
to obtain the port of the OSN device interconnected with the radio device, namely, the
interconnected UNI port. For details, see:
NE Sl ot
Conf i gur at i on Li st ( Af t er UNI Al l ocat i on) . xl s
 If the number of ports is insufficient or the type of ports is improper, consider adding a board or
changing a board.
 If the ports interconnected with the RTN or NodeB exist, you need to manually find and allocate the
ports because currently no service requirement is proposed and the interconnection information is
not displayed in "OSN-NodeB convergence relation.xls."
Step 4 Collect the number of allocated UNI ports and information by using the MSTP+ Design Tool
V1.0. Copy the contents in the "05_UNI NE interconnection" worksheet to the "03-PW"
worksheet of the MSTP+ Design Tool V1.0. For details, see the following description.
 Copy the fields of "RNC" in column A to the fields of "Ingress NE" in column C.
 Copy the fields of "popsite" in column G to the fields of "Egress NE" in column H.
 Copy fields of "Vlan ID" in column D to the fields of "Vlan ID" in columns E and J.
 Copy fields of "PopSite Port(OSN)" in column K to fields of "Egress Port" in column I.
 Click the following buttons in the "00-Cover" worksheet of the MSTP+ Design Tool
V1.0 to obtain the UNI port from the "12-UNIPortList" worksheet. The UNI ports in
column H of the "07-EthernetPortList" worksheet are labeled as "UNI."
 Contents in columns A, B, and R of the "03-PW" worksheet need be filled in manually.
Number the contents in column A from 1. Field "Classification" in column B indicates
the service classification. Fill in the classification according to the customer
requirements or according to the actual condition, for example, WCDMA and OM. If the
customer does not propose any requirement, it is recommended that you use "WCDMA",
"TD-SCDMA", and "CDMA2000" to identify users and signaling services and use
"OM" to identify services used by the out-band NMS. Fill in "TrafficLoad(Mbps)" in
column R according to the actual condition. If no specific data is involved, it is
recommended that you fill in the possible peak value.

INTERNAL
The copied fields of "popsite" and "PopSite Port(OSN)" can be used to generate the "12-UNIPortList"
worksheet. Other steps previously provided are for the follow-up design. To ease the description, all the
operations in one worksheet are listed here.
----End
2.4.3 Outputs
1. UNI Interconnection.ppt
2. NE slot configuration list.xls (will UNI ports allocated)
3. UNI port list (namely, "12-UNIPortList" in the MSTP+ Design Tool V1.0)
2.5 MPLS Design (Available Tools)
2.5.1 Flow Chart
Step 1 Open "00-Cover" of the MSTP+ Design Tool V1.0. Set the start value of LSR ID and Port IP
according to the collected NODE ID and IP information.
Step 2 Click the following buttons in red to obtain the allocated LSR ID from column F in the "01-
NE BasicInfo" worksheet and obtain the allocated Port IP from columns D and G in the "06-
Ethernet Link(NNI)" worksheet.

INTERNAL
The Node ID and IP collected from the customer are segmented instead of continuous. You can only
allocate the Node ID and IP by segment. For example, allocate a segment and then copy the fields to
another worksheet to allocate the other segment.
----End
2.5.3 Output
1. LSR ID of the NE (namely, column F in "01-NE BasicInfo" of the MSTP+ Design Tool
V1.0)
2. NNI port IP (namely, columns D and G in "06-Ethernet Link(NNI)" of the MSTP+
Design Tool V1.0)
2.6 DCN Design (Optional)
If the network has the TDM plane, you may also design the DCN on the TDM plane. In this case, DCN-
related design need not be conducted on the packet switching plane.
2.6.1 Flow Chart
Step 1 The DCN design mode is not fixed and it varies with the network, but the DCN designs are
based on the DCN planning principle and specifications supported by the devices. Therefore,
you only need to understand the DCN planning principle and the specifications supported by
devices to design the DCN meeting the requirements and conforming to the actual network
design situation.

INTERNAL
Step 2 The following attachment describes the DCN design principles and contents:
 Section 1.1 describes the DCN features supported by the MSTP+ device.
 Section 1.2 describes the principles for designing various parameters required by the
DCN design.
 Section 1.3 describes the principles of the DCN network design.
DCN Pl anni ng. doc
Step 3 The procedure of configuring the DCN on the T2000 is as follows:
 Set the communication parameters for each NE.
 Configure the gateway NEs.
 Configure the bandwidth of the inband DCN of each NE.
Default value:
Ethernet board VLAN ID: 4094
Bandwidth (kbps): 512
 Set the state of the port used by each NE.
 Set the protocol stack used by the inband DCN of each NE to IP.
----End
2.7 Clock Synchronization Design (Optional)
If the network has the TDM plane, you may also design the DCN on the TDM plane. In this case, DCN-
related design need not be conducted on the packet switching plane.
2.7.1 Flow Chart

INTERNAL
Step 1 Understand the clock design principles and the specifications supported by the device. For
details, see the following attachment:
Cl ock
Pl anni ng. doc
Step 2 The procedure for configuring the clock on the T2000 varies with the situation.
Figure 1.1 Configuration process when the SSM protocol is not started
Figure 1.2 Configuration process when the standard SSM protocol is started

INTERNAL
Figure 1.3 Configuration process when the extended SSM protocol is started
----End

INTERNAL
3 MSTP+ Service Design
3.1 Tunnel Design (Available Tools)
3.1.1 Flow Chart
The previous figure shows the normal design process. The design process is simplified when the MSTP+
Design Tool V1.0 is used. The following procedure details the design process.
Step 1 Open the MSTP+ Design Tool V1.0. Click the following buttons in red to initialize the
relevant worksheets.

INTERNAL
Step 2 Manually fill in column C and columns from I to M in "04-TunnelAPS" worksheet in the
MSTP+ Design Tool V1.0. Fill contents in "TnlAPS Usage" in column C according to the
actual condition. Fill in columns from I to M according to the customer requirements. If the
customer does not propose any requirement, fill in the columns according to the following
figure:
Step 3 Design the APS ring.
The APS ring is a logical ring designed for determining the Tunnel route. An APS ring is
formed by the working tunnel and protection tunnel of each group of Tunnel APS. For
example, the parts in blue and in purple are respectively the working tunnel and protection
tunnel, which form an APS ring.
The design procedure of the APS ring is as follows:
1. Regard the source node and sink node (for example, RNC/E) of the TunnelAPS as the
explicit nodes. You can design the same APS ring (in orange dashed line) for the
TunnelAPS whose source node and sink node are the same. In addition, the ring can be
the same if the destinations of the nodes on the same ring are all RNC unless the link
capacity on the link cannot bear the services of the office direction. For example, nodes
A, B, C, and D can use the same APS ring (in green dashed line).
2. After determining the number of APS rings, you can identify the rings on the topology
according to the principles, such as link separation, node separation, and shortest path.
Record the nodes, ports, and port IPs involved with the ring in columns C to N in the
"05-APSRing" worksheet of the MSTP+ Design Tool V1.0. Because the rings in NNI
link list.xls are designed clockwise or anti-clockwise, you can effectively use the
worksheet to improve the efficiency for designing the APS ring.
Step 4 Click the buttons in red in the MSTP+ Design Tool V1.0 to generate the TunnelAPS and
Tunnel.
Step 5 In the MSTP+ Design Tool V1.0, click in turn in "09-Tunnel RoutingTable" to obtain the
Tunnel route and obtain the load of each link from columns I to K in "06-Ethernet
Link(NNI)".

INTERNAL
----End
3.1.3 Outputs
1. Tunnel APS (namely, the "04-TunnelAPS" worksheet in the MSTP+ Design Tool V1.0)
2. Tunnel (namely, the "08-Tunnel" worksheet in the MSTP+ Design Tool V1.0)
3. Tunnel route (namely, the "09-Tunnel RoutingTable" worksheet in the MSTP+ Design
Tool V1.0)
3.2 Service Access Design
3.2.1 Flow Chart
Step 1 Determine the service type according to the LLD service requirement. Generally, the E-Line
service is adopted for the point-to-point services. The E-LAN service is adopted for
multipoint-to-multipoint services.
Step 2 The design procedure for E-Line service is as follows:
E-Line service design mainly indicates the PW design, including parameters such as the UNI
port, VLAN ID, and the tunnel bore by the E-Line service.

INTERNAL
1. Open the MSTP+ Design Tool V1.0. The "03-PW" worksheet lists the described E-Line
service. Step 4 in section 2.4.2 describes how to fill in the fields in "03-PW", you only
need to fill in fields in column D (Ingress Port) here.
2. Section 2.4 describes the design and allocation of the UNI ports. You only need to copy
columns J and K in "05_UNI NE interconnection" worksheet in NE Slot Configuration
List.xls to columns D and I in the "03-PW" worksheet of the MSTP+ Design Tool V1.0.
Step 3 The design procedure for E-LAN service is as follows:
1. For the specific communication port required by the E-LAN service, the port can either
be a physical port or a PW. When the port is a PW, identify the PW with a label, for
example, s3p14 and s3pe. The two ports of the PW (label 1023) communicate with each
other, but the ports of s3p3 and PW1023 do not need to communicate with each other.
2. You can make the E-LAN service design worksheet according to the parameters
configured by the E-LAN service. For details of the field information and format, see
3.2.3 Outputs.
3. Field description:
Column A: NE name. The E-LAN service configuration is based on the NE.
Column B: service ID. Different E-LAN service has different ID.
Column C: service name, indicates the specific service type, for example, OM service,
user service, and signaling service.
Columns D to H: adopt the default value. For details, see 3.2.3 Outputs.
Column I: private network service port, indicates the ports that can communicate with
each other.
Column J: port attribute, for example, UNI port or NNI port.
Column K: split horizon group ID. Currently, for one E-LAN service, the MSTP+ device
can only configure one split horizon group. That is, the ID can only be set to 1. Ports in a
split horizon group cannot communicate with each other. Ports s3p3 and PW1023
described previously can be configured in one split horizon group.
----End
3.2.3 Outputs
1. E-Line service design (namely, the "03-PW" worksheet in the MSTP+ Design Tool
V1.0)
2. E-LAN service design
MSTP+ E- LAN
Ser vi ce Desi gn. xl s

INTERNAL
3.3 Label Design (Available Tools)
3.3.1 Flow Chart
The process shown in the previous flow chart is a standard design process. The MSTP+ Design Tool
V1.0 shields certain steps. This section specifies the design process.
Step 1 Open the "00-Cover" worksheet of the MSTP+ Design Tool V1.0. Click the button marked in
red to obtain the PW label from columns F and K in the "03-PW" worksheet and obtain the
Tunnel label from columns L and M in the "09-Tunnel RoutingTable" worksheet.
Step 2 If the PW port exists in the E-LAN service listed in the "E-LAN service design" worksheet,
fill in the allocated PW label. For details, see the part in bold and in red in E-LAN service
design of 3.2.3 Outputs.
----End
3.3.3 Outputs
1. Tunnel label (namely, columns L and M in the "09-Tunnel RoutingTable" worksheet)
2. PW label (indicates columns F and K in the "03-PW" worksheet)

INTERNAL
3.4 QoS Design (Optional)
 Many policies and mechanisms are involved in each step of the QoS design. You need to design the
QoS by referring to the features supported by the MSTP+ device. In this way, you can avoid the
unavailable solutions caused due to the incompatibility between the design solution and the device
characteristics.
 When conducting network design based on peak traffic of service requirements, you need not
consider QoS-related factors.
 The MSTP+ device supports non-hierarchical QoS and hierarchical QoS (HQoS). The differences
between the non-hierarchical QoS and hierarchical QoS are as follows:
Non-hierarchical QoS is a QoS with a large granularity. The flows of the same priority on a physical
port use the same priority queue and compete with each other for the queue. In this way, you cannot
differentiate or reset a single flow or user.
In the case of the HQoS, independent schedulers are set for different service classes. Therefore, the
traffic QoS is applied further on each service class to provide services for these classes. With
sufficient internal resources and control policies in the equipment, the carriers can also provide
guaranteed QoS for VIP users and save the overall network construction cost. With the HQoS, the
users are capable of using the leased bandwidth in a more specific and reasonable manner.
Moreover, the HQoS provides guaranteed QoS for customers.
The following process is applicable to both HQoS and non-hierarchical QoS. The configuration
processes, however, are different. For the configuration process on the T2000, see the OptiX OSN
3500 Product Documentation.
3.4.1 Flow Chart
3.4.2 Design Principles
1. Common concepts
Glossary Description
DS domain Specifies different service classes. Standards in the same domain are the
same.
Edge node Indicates the edge node in a DS domain.

INTERNAL
Internal node Indicates the internal node in a DS domain.
PHB Indicates that when the data flow passes through the device supporting the
DS, the device forwards the data flow according to the DS domain.
SLA Indicates the protocol agreed by the user and the service provider. The
SLA specifies the supported service type and the service capacity allowed
in each type. The user can be a common user or another service provider.
2. In the case of the node in the DiffServ (DS) domain (mainly the node on the core
network), do as follows:
Configure the DS domain according to the mapping relation between the packet priority
and the queue. After that, the NE schedules the packets into corresponding queues
according to their priorities (C-VLAN priority, S-VLAN priority, IP-DSCP priority, and
MPLS EXP priority).
3. In the case of the edge node in the DS domain (mainly the node interconnected with the
client equipment), comply with the following rules:
− If the MPLS is used for service transmission, it is recommended that the bandwidth
of a tunnel on the PW ingress NE should be limited.
− The private line service user generally purchases a certain bandwidth, for example,
50 Mbit/s. In this case, the bandwidth of the private line service should be limited at
the V-UNI.
− When a private line service user has differentiated requirements for the services, for
example, when the user needs to differentiate the IP telephone service, video service,
and general-purpose Internet service, the traffic classification needs to be specified in
the V-UNI ingress policy. In this manner, services are differentiated and allocated
with different priorities according to the requirements of the user. In addition, it is
recommended that the bandwidth of a queue should be limited so that the maximum
traffic of a certain type of service is determined. The guaranteed bandwidth of users
varies according to their different charges.
− When several users need to share the bandwidth, a V-UNI group is required.
Configure the V-UNI group so that the guaranteed bandwidth and peak bandwidth of
each user and the peak bandwidth of the V-UNI group can be specified. Add the
services of multiple users to the V-UNI group, and then the bandwidth sharing is
realized. The guaranteed bandwidth of users varies according to their different
charges.
1. Flow classification is to classify the data flow into multiple priorities or service classes.
In this way, you can prepare different service policies for different flows.
The following briefs the flow classification method:
 VLAN PRI: 3 bits, supports eight classes.
 IP priority: the first three bits in the type of service (TOS) field, supports eight classes.
 Differentiated services codepoint (DSCP) of the IP packet head: the first six bits in the
TOS field, supports 64 classes.
 MPLS network: three bits in the EXP field of the MPLS packet, supports eight classes;
six bits in the Label field, supports 64 classes.

INTERNAL
 The ACL is used for complex flow classification. Services can be classified by
source/destination MAC address, source/destination IP addresses, protocol IDs, and
TCP/UDP source/destination port IDs.
Figure 1.1 Parameter description
Field Value Range Description
Flow type The parameter value range differs according to
board types and product types. For details,
click the hyperlink in the note information.
Specifies the type of flow in the Ethernet data
board. This parameter determines the method
adopted to bind the flow and services.
VB ID For example: 1 Displays or specifies the VB ID for the QoS.
C-VLAN For example: 1 Displays or specifies the C-VLAN.
S-VLAN For example: 1 Displays or specifies the S-VLAN.
Port For example: PORT1 Displays the port name.
VLAN ID For example: 0 to 4095
If an EVPL (QinQ) service is created on the
basis of Port + 65532, you can enter the value
65532 for the VLAN ID when creating a flow.
Displays the VLAN ID carried in the service
that corresponds to the flow.
Priority For example: 0 to 7 Displays or specifies the required QoS priority.
Bound
CAR
Created CAR ID
Default value: none
Specifies the method of binding a flow with a
CAR ID and querying the CAR ID bound with
the flow. A flow can only be bound to one
CAR ID. The CAR ID takes effect only after
the flow is bound to the CAR ID.
Bound CoS Created CoS ID
Default value: none
Specifies the method of binding a flow with a
CoS ID and querying the CoS ID bound with
the flow. A flow can only be bound to one CoS
ID. The CoS ID can specify the priorities of
flow packets only after the flow is bound to the
CoS ID.
Bound
shaping
For example: 1 Displays the ID of the shaping that is bound
with the flow.
2. The typical function of CAR is to limit the traffic and burst of an incoming connection of
a network. When a packet meets certain conditions, for example, the traffic of a
connection is over large, the CAR can perform different processing methods, such as
abandoning the packets or resetting the packet priority.
A CAR is determined by four flow parameters, namely, CIR, extra burst size, peak
bandwidth, and extra maximum burst size.

INTERNAL
CAR ID The parameter value range differs
according to board types and
product types.
Specifies the ID of a CAR. When a CAR is
created, it needs to be specified with a CAR ID.
Enabled/Disabled Enabled, Disabled
Default value: disabled
Specifies whether a CAR can limit the traffic
volume.
Committed
information rate
The parameter value range differs
product types.
Sets the committed information rate (CIR) of
the CAR. CIR specifies the minimum guarantee
bandwidth of a flow.
When entering a parameter value, ensure that
this value is an integral multiple of 64.
Committed burst size The parameter value range differs
product types. For details, click the
hyperlink in the note information.
Sets the committed burst size (CBS) of the
CAR. It defines a maximum committed traffic
that can be transmitted for a flow in a time
interval.
Peak information rate The parameter value range differs
product types.
Sets the peak information rate (PIR) of the
CAR. It specifies the allowed maximum rate of
a flow.
When entering a parameter value, ensure that
this value is an integral multiple of 64.
Maximum burst size The parameter value range differs
product types.
Sets the peak burst size (PBS) of the CAR. It
defines a maximum extra traffic that can be
transmitted for a flow in a time interval.
3. Class of service (CoS): The CoS function classifies packets and schedules them to
queues of different priorities. Then, the packets are processed according to their queue
priorities. In this case, the packets have different QoS operations in terms of delay and
bandwidth. The Ethernet service processing boards of the OptiX OSN equipment series
provide four types of CoSs, which are the simple CoS, VLAN priority CoS, IP TOS
CoS, and differentiated services code point (DSCP) CoS. With the four types of CoSs
configured, packets can be groomed to egress port queues of different priorities.
CoS ID The parameter value range differs according to
board types and product types. For details, click
the hyperlink in the note information.
Specifies the ID of a CoS. When a CoS
is created, it needs to be specified with
a CoS ID.
CoS type The parameter value range differs according to
Specifies the type of CoS of the flow
in the Ethernet data board. This
parameter decides the method adopted
to classify the flow in the Ethernet data
board.

INTERNAL
CoS parameter The value range varies according to the CoS type
selected.
When the CoS type is set to simple, this
parameter is 0 to 7.
When the CoS type is set to VLAN Priority, this
parameter is User Priority n in the VLAN tag.
In this value, n is an integer ranges form 0 to 7.
When the CoS type is set to IPTOS, this
parameter is IPTOS(0000) to IPTOS(1111).
When the CoS type is set to DSCP, this
parameter is DSCP(000000-111111).
CoS priority The parameter value range differs according to
Classifies packets into different levels
based on the CoS type, and maps these
packets into different CoS priorities.
The packets of higher priorities are
first processed.
4. The traffic shaping can restrict the traffic and burst of a connection in a network, and
thus enables the packet to be transmitted at an even rate. Traffic shaping is usually
realized by using a buffer area and a token bucket. When the packet transmission rate is
too high, the packets are stored in the buffer area. Under the control of the token bucket,
the buffered packets are then evenly transmitted.
Port For example: PORT3 Specifies the port for traffic control.
Port queue For example: 1 Displays the port queue that can be set.
The priorities of transmitting packets
become lower and lower for the ports
that start from port 1 in sequential order.
Enabled/Disabled Enabled, Disabled Specifies whether to enable the port
queue.
Committed information
rate (kbit/s)
Enters or selects a value. Specifies the assured bandwidth of the
egress port.
Committed burst size
(kbyte)
For an OSN NE, the value ranges from
0 to 32. For a WDM NE, the value
ranges from 16 to 512.
Specifies the buffer size of the egress
port.
Peak information rate
(kbit/s)
This parameter is fixed to be 0 and
cannot be changed manually.
Specifies the peak bandwidth.
Maximum burst size
(kbyte)
This parameter is fixed to be 0 and
cannot be changed manually.
Specifies the buffer size of the CBS.
5. Binding between the flow and the CAR/CoS/Shaping

INTERNAL
3.5 Design Acceptance (Optional)
The acceptance can be classified into internal acceptance and external acceptance.
 Internal acceptance: indicates that the designer hands over the deliverables to the
implementation personnel.
 External acceptance: indicates that the customer selects whether to perform the design
acceptance. The acceptance object is determined according to the customer requirements,
for example, the implemented network, the MSTP+ design solution, or the relevant
deliverables.
3.5.1 Flow Chart
3.5.2 Deliverables
MSTP+ Net wor k
Desi gn. ppt
MSTP+ Net wor k
LLD. xl s
NE Sl ot

INTERNAL
4 References
 OptiX OSN 3500 product documentation (available at http://support.huawei.com)
 NG-SDH Network Design Service Product V100R001MSTP+ Technical Guide
 MSTP+ Network Design Tool (20091125).ppt
 Filling sample and design result sample of the MSTP+ Design Tool V1.0
MSTP+ Desi gn Tool
V1. 0( 输入填写样例) . r ar
MSTP+ Desi gn Tool
V1. 0( 设计结果样例) . r ar

INTERNAL
5 Acronyms and Abbreviations
Figure 1.5 Acronyms and abbreviations
Acronyms and Abbreviations Full Spelling
MSTP Multi Service Transport Platform
MPLS Multi-Protocol Label Switch
TUNNEL Tunnel
PW Pseudo Wire
VLAN Virtual LAN
DCN Data Communication Network
SDH Synchronous Digital Hierarchy
NNI Network-to-Network Interface
UNI User-to-Network Interface

Mstp+ network design service product v100 r001 delivery guide(20100127)

Recommended

Recommended

More Related Content

Viewers also liked

Viewers also liked (7)

Similar to Mstp+ network design service product v100 r001 delivery guide(20100127)

Similar to Mstp+ network design service product v100 r001 delivery guide(20100127) (20)

Recently uploaded

Recently uploaded (20)

Mstp+ network design service product v100 r001 delivery guide(20100127)