OptiX OSN 1800V Packet Service Configuration Practice Guide

Revision Record
Course Code Product Product Version Course Version ISSUE

OTC115255 OSN1800 V V100R005C20 1.00
Developer/Modifier Time Approver New/Update

yinhuale 2015-6 songrui New
OptiX OSN 1800 V （Packet）Service
Configuration Practice Guide
ISSUE1.00
Table of Contents
Course Description.......................................................................................................................1
Course Introduction.................................................................................................................1
Course objectives....................................................................................................................1
Reference...............................................................................................................................1
Chapter 1 Basic Configuration On Packet..................................................................................2
1.1 Configure LSR ID............................................................................................................2
1.2 Setting Attributes for Ethernet Ports....................................................................................2
1.3 Configuring PKT Virtual Ports for Universal Line Boards..................................................5
1.4 Configuring a Bidirectional MPLS Tunnel.......................................................................6
Chapter 2 Configuring ETH PWE3 Services.............................................................................10
2.1 E-Line Services Carried by PWs.......................................................................................10
2.2 E-LAN Services Carried by PWs......................................................................................20
Chapter 3 Configuring Native Ethernet Services on the Packet Plane........................................32
3.1 Point-to-Point Transparently Transmitted E-Line Services..................................................32
3.2 VLAN-Based E-Line Services..........................................................................................34
3.3 QinQ-Based E-Line Services............................................................................................36
3.4 E-LAN Services Based on 802.1q Bridge..........................................................................39
Chapter 4 Network Level Protection (Packet).......................................................................41
4.1 Tunnel APS....................................................................................................................41
4.2 PW APS.........................................................................................................................43
Confidential Information of Huawei. No Spreading without Permission

OptiX 1800V (Packet) Service Configuration Practice Guide 1
Course Introduction
This course is applicable to OptiX OSN 1800V products.
This course helps the trainees to accumulate configuration and application experience of Packet
features.
Course objectives
Upon completion of this course, you will be able to:
 Master the configuration of E-Line services and E-LAN services
 Outline the configuration of protection for OSN 1800 V (packet)
Reference

Chapter 1 Basic Configuration On Packet
1.1 Configure LSR ID
Step Action
1 In the NE Explorer, select the desired NE and choose Configuration > Packet
Configuration > MPLS Management > Basic Configuration from the Function
Tree.
2
Set LSR ID
3 NOTE:
In a packet switched network (PSN), one NE must be allocated with a unique LSR
ID.
When planning the LSR ID for an NE, adhere to the following principles:
The IP address of an NNI port can be an IP address of standard class A, B, or C
(namely, an IP address within the range from 1.0.0.1 to 223.255.255.254). The IP
address of an NNI port cannot be a broadcast address (*.*.*.255), multicast
address (224.0.0.0 to 239.255.255.255), reserved address (240.0.0.0 to
255.255.255.255), network address (*.*.*.0), zero address (0.*.*.*), loopback
address (127.*.*.*). The address of the network segment used with priority:
172.16.0.0-172.31.255.255. In this network segment, the number of the available
IP address is 1048574 (the 172.16.0.0 and 172.31.255.255 are exceptional).
Each NE must have an independent and globally unique LSR ID on a network.
The LSR ID of an NE and the IP address of the NE must be different from each
other and must be in different network segments.
The SLR ID of an NE must be in a different network segment from the IP address
of any service port on the NE.
After setting LSR IDs, enable the MPLS function. Otherwise, other functions of
the MPLS network cannot be set.
1.2 Setting Attributes for Ethernet Ports

An Ethernet port can be used to carry Ethernet packets or tunnels, depending on
different settings of the port attributes. The attributes of an Ethernet port include the
general attributes, Layer 2 attributes, Layer 3 attributes, advanced attributes, and
flow control.
Application scenario of an Ethernet port:
Step Application Scenario Required Port Attribute

1 Accessing the Ethernet service General attributes, Layer 2 attributes
2 Carrying the QinQ Link General attributes, Layer 2 attributes
3 Carrying the tunnel General attributes, Layer 3 attributes
4 NOTE:
When the Ethernet port is used to carry a QinQ Link, the configuration
procedure is similar to the configuration procedure when the Ethernet port is
used to carry an Ethernet service. However, the encapsulation types are
different. For details, see Setting Layer 2 Attributes for Ethernet Ports.

5
Procedure for configuring an Ethernet port
1.2.1 Setting General Attributes for Ethernet Ports
Step Action
Configuration > Interface Management > Ethernet Interface from the
Function Tree.
2 Click the Basic Attributes tab.
3 Select the desired board and set parameters as required.
NOTE:
 When Port Mode is set to Layer 2, Encapsulation Type can be set to Null,
802.1Q, or QinQ.
 When Port Mode is set to Layer 3, Encapsulation Type can be set to 802.1Q
only. In this case, the port can be used to carry a tunnel.
4 Click Apply. Then, the Operation Result dialog box is displayed, indicating that
the operation is successful.
5 Click Close.

1.2.2 Setting Layer 2 Attributes for Ethernet Ports
Step Action
Function Tree.
2 Click the Layer 2 Attributes tab.
3 Select the port and set parameters as required.
NOTE:
 QinQ Type Domain can be set only when Encapsulation Type is QinQ or
802.1Q.
 TAG can be set only when Encapsulation Type is 802.1Q.
 Default VLAN ID and VLAN Priority can be set only when Encapsulation
Type is 802.1Q.
 SVLANs: This parameter can be set only when Encapsulation Type is set to
802.1Q. When C-VLANs and S-VLANs are configured on the same port, this
parameter must be set. A VLAN configured with this parameter is an S-
VLAN. The other VLANs are C-VLANs.
5 Click Close.
1.2.3 Setting Layer 3 Attributes for Ethernet Ports
Step Action
Function Tree.
NOTE:
When changing the IP address of a port, ensure that the IP address of the port and
the IP addresses of the other ports configured with services are not in the same
subnet.
5 Click Close.
1.2.4 Setting Advanced Attributes for Ethernet Ports

Step Action
Function Tree.
2 Click the Advanced Attributes tab.
5 Click Close.
1.2.5 Configuring Flow Control
Step Action
Function Tree.
5 Click Close.
1.3 Configuring PKT Virtual Ports for Universal Line Boards

Step Action
1 In the NE Explorer, select the desired universal line board and choose
Configuration > Virtual Port Mapping Management from Function Tree.
2 On the New Virtual Port tab page, add a virtual PKT port according to the
service plan, and click Add.

3 Click Mapped ODUk and select the desired ODUk mapping path.
5 Click Close.
1.4 Configuring a Bidirectional MPLS Tunnel

1.4.1 Configuring an MPLS Tunnel on a Per-NE Basis
Step Action
1 In the NE Explorer, select the source NE of the MPLS tunnel and choose
Configuration > Packet Configuration > MPLS Management > Unicast
Tunnel Management from the Function Tree.
2 Click the Static Tunnel tab and click New > Bidirectional Tunnel. Then, the
New Unicast Bidirectional Tunnel dialog box is displayed.

3 Set the parameters of the bidirectional MPLS tunnels.
NOTE:
 When Node Type is set to Transit, the In port, Out port, Forward In
Label, Forward Out Label, Reverse In Label, Reverse Out Label,
Forward Next Hop Address, Reverse Next Hop Address, Source Node
and Sink Node parameters need to be set for the tunnel.
 When Node Type is set to Egress, the In port, Forward In Label, Reverse
Out Label, Reverse Next Hop Address and Source Node parameters need
to be set for the tunnel.
 When LSP Mode is set to Pipe: Indicates that the CoS policy of packets
does not need to be restored after tunnel labels are peeled off.
 When LSP Mode is set to Uniform: Indicates that the CoS policy of packets
needs to be restored after tunnel labels are peeled off.
4 Click OK to complete the configuration of the static MPLS tunnel.
5 Refer to steps 1-4 to configure the static MPLS tunnels on the intermediate NEs
and sink NE.
1.4.2 Configuring an MPLS Tunnel in End-to-End Mode

Step Action
1 Choose Service > Tunnel > Create Tunnel from the Main Menu. Then, the
Create Tunnel window is displayed.
2 Set the basic information about the MPLS tunnel.

 Protocol Type: MPLS.
 Signaling Type: Static CR.
 Service Direction: Bidirectional.
3 Set the information in NE List of the MPLS tunnel.

4 Click the Details button and set the information about the tunnel.
NOTICE:
 Click Auto-Assign following the Tunnel ID field box. Then, Tunnel ID is
automatically allocated.
 Click the blank cell under Out Interface of an Ingress node and then click
. Select the output port of the ingress node in the list box that is
displayed. Use the same method to select the input and output ports of the
transit node and the input port of the egress node.
 After the output port is added at the ingress node and transit node, the next-
hop address is generated automatically.
 After the input port is added at the egress node and transit node, the reverse
next-hop address is generated automatically.
 Click Auto-Assign Label at lower right of the window. Then, Out Label and
Reverse In Label of the ingress node, In Label, Out Label, Reverse In
Label and Reverse Out Label of the transit node, and In Label and Reverse
Out Label of the egress node are allocated automatically.
5 Click OK. The configuration for tunnel is complete.

Chapter 2 Configuring ETH PWE3 Services
2.1 E-Line Services Carried by PWs

2.1.1 Networking diagram of E-Line services carried by PWs (based on VLANs)
The service requirements of User A and User B are as follows:

User A1 and User B1 are connected to NE1 through the 4-EM20-3 and 4-EM20-4 ports
respectively.
User A2 and User B2 are connected to NE4 through the 4-EM20-3 and 4-EM20-4 ports
respectively.
The service between User A1 and User A2 is a common Internet access service of which the CIR
is 10 Mbit/s and the PIR is 30 Mbit/s.
The service between User B1 and User B2 is a data service of which the CIR is 30 Mbit/s and the
PIR is 50 Mbit/s.
The services of User A and User B each are carried on one PW.
The two PW links that carry the services of User A and User B share the bandwidth of one tunnel.
The service between User A and User B is configured with Tunnel APS.
Working path: NE1-NE2-NE4
Protection path: NE1-NE3-NE4
NE information:
NE IP Address IP Mask LSR ID

NE1 4-EM20-1 18.1.1.1 255.255.255.252 130.0.0.1
4-EM20-2 18.1.2.1 255.255.255.252
NE2 4-EM20-1 18.1.1.2 255.255.255.252 130.0.0.2
4-EM20-2 18.1.1.5 255.255.255.252
NE3 4-EM20-1 18.1.2.2 255.255.255.252 130.0.0.3
4-EM20-2 18.1.2.5 255.255.255.252
NE4 4-EM20-1 18.1.1.6 255.255.255.252 130.0.0.4
4-EM20-2 18.1.2.6 255.255.255.252

2.1.2 Service Planning
2.1.2.1 Basic attributes of Tunnels
Parameter Tunnel Name Tunnel Protocol Signaling Direction Protection

ID Type Type Type
Parameter NE1_NE4_working 10 MPLS Static CR Bidirectio Unprotected
Planning nal
NE1_NE4_protectio 20 MPLS Static CR Bidirectio Unprotected
n nal
2.1.2.2 Parameters of Tunnels
Tunnel ID Node Node Type In Interface In Label Reverse In Label Out Interface
10 NE1 Ingress - - 103 4-EM20-1
NE2 Transit 4-EM20-1 100 102 4-EM20-2
NE4 Egress 4-EM20-1 101 - -
20 NE1 Ingress - - 203 4-EM20-2
NE3 Transit 4-EM20-1 200 202 4-EM20-2
NE4 Egress 4-EM20-2 201 - -
Tunnel Node Out Reverse Out Next Reverse Source Sink Node
ID Label Label Hop Next Hop Node
10 NE1 100 - 18.1.1.2 - - 130.0.0.4

NE2 101 103 18.1.1.6 18.1.1.1 130.0.0.1 130.0.0.4
NE4 - 102 - 18.1.1.5 130.0.0.1 -
20 NE1 200 - 18.1.2.2 - - 130.0.0.4
NE3 201 203 18.1.2.6 18.1.2.1 130.0.0.1 130.0.0.4
NE4 - 202 - 18.1.2.5 130.0.0.1 -
2.1.2.3 Parameters of MPLS-TP tunnel OAM
Parameter Parameter Planning

Tunnel ID 10 20
OAM Status Enabled Enabled
MEG ID Type IP Based IP Based
MEG Level 7 7
Detection Mode Adaptive Adaptive
CC Packet Priority 7 7
CC Packet Interval 1s 1s
Lock Status Unlock Unlock
AIS Status Disabled Disabled
SD Threshold(%) 0 0
SF Threshold(%) 0 0

2.1.2.4 Parameters of Tunnel APS

Protection Type 1:01
Switching Mode Dual-Ended
Working Tunnel ID 10
Tunnel Name NE1_NE4_working
Protection Tunnel ID 20
Tunnel Name NE1_NE4_protection
Revertive Mode Revertive
WTR Time (min) 5
Hold-off Time (100 ms) 0
NOTE:
The services are not protected by multiple

protection schemes. Therefore, Hold-off
Time (100ms) takes the default value 0.
Protocol State Enabled
2.1.2.5 Planning information of the PWs
Parameter PW of User A PW of User B

PW ID 35 45
PW Signaling Type Static Static
PW Type Ethernet Tagged Mode Ethernet Tagged Mode
PW Direction Bidirectional Bidirectional

PW Incoming 20 30
Label/Source Port
PW Outgoing Label/Sink 20 30
Port
Peer IP NE 130.0.0.4 130.0.0.4
1
NE 130.0.0.1 130.0.0.1
4
Tunnel No. NNE1_NE4_working NE1_NE4_working
Bandwidth Limit Enabled Enabled

CIR(kbit/s) 10240 30720
PIR(kbit/s) 30720 51200
CBS(bytes) 30720 51200
PBS(bytes) 30720 51200

Request VLAN 10 20
2.1.2.6 Parameters of E-Line services carried by the PWs from the user side to the
network side
Parameter User A User B

Service ID 1 2
Name E-Line-1 E-Line-2
Direction UNI-NNI UNI-NNI
UNI 4-EM20-3 4-EM20-4
VLANs 100 100

Bearer Type PW PW
PW ID 35 45
BPDU Not Transparently Not Transparently Transmitted
Transmitted
MTU(bytes) - -
2.1.3 Configuration Process (in End-to-End Mode)
Step Action
1 Prerequisites:
 You are familiar with the networking requirements and service planning information of
the UNI-NNI E-Line services carried by PWs.
 You must be an NM user with Administrators authority or higher.
 If a port needs to be occupied exclusively, you need to disable the DCN function of the
port.

2 Configure the working tunnels that carry the PWs and configure MPLS-TP Tunnel OAM
for the tunnels.
3 See Service Planning and 2 to configure protection tunnels and MPLS-TP Tunnel OAM for
the tunnels.

4 Configure tunnel APS.

5 Configure the common Internet access service between User A1 and User A2 in end-to-end
mode.
6 See Service Planning and 5 to configure the data service between User A1 and User A2 in
end-to-end mode.
2.1.4 Configuration Process (on a Per-NE Basis)

Step Action
1 Prerequisites:
 You are familiar with the networking requirements and service planning
information of the UNI-NNI E-Line services carried by PWs.
 If a port needs to be occupied exclusively, you need to disable the DCN
function of the port.

2 On NE1, NE2, and NE4, configure the working tunnels that carry the PWs.
NE1:
NE2:
NE4:

3 See Service Planning and 2 to configure protection tunnels on NE1, NE3, and
NE4.
4 See Service Planning to configure MPLS-TP tunnel OAM on NE1 and NE4.
5 See Service Planning to configure Tunnel APS on NE1 and NE4.

NE1 is used as an example.

6 On NE1, configure the E-Line services of User A1.
7 See Service Planning and 6 to configure the E-Line services of User B1 on NE1.
8 See Service Planning and 6 to configure the E-Line services of User A2 and User
B2 on NE4.
2.2 E-LAN Services Carried by PWs

2.2.1 Networking diagram of E-LAN services carried by PWs

The network shown in Figure above uses an end-to-end virtual private LAN service (VPLS)
solution, which implements VPLS at both access nodes and the convergence node. This
reduces configuration workload required for NodeB expansion or reparenting. The service
requirements are as follows:
 NE1 receives NodeB1's common Internet access services through 4-EM20-3 and NodeB2's
data services through 4-EM20-4, and NE2 receives NodeB3's common Internet access
services through 4-EM20-3 and NodeB4's data services through 4-EM20-4.
 NE4 converges and transmits services from NodeBs to the radio network controller (RNC).
 Services from NodeB1 and NodeB3 have the same VLAN ID (100), the same CIR (10
Mbit/s) and the same PIR (30 Mbit/s). CIR is short for committed information rate, and PIR
for peak information rate.
 Services from NodeB2 and NodeB4 have the same VLAN ID (200), the same CIR (30
Mbit/s) and the same PIR (50 Mbit/s).
 Services from NodeBs 1 to 4 are protected by tunnel automatic protection switching (APS).
 For services from NodeB1 and NodeB2, the working path is NE1 -> NE2 -> NE4, and the
protection path is NE1 -> NE3 -> NE4.
 For services from NodeB3 and NodeB4, the working path is NE2 -> NE4, and the
protection path is NE2 -> NE1 -> NE3 -> NE4.
NE information:
NE IP Address Mask LSR ID
NE1 4-EM20-1 18.1.1.1 255.255.255.252 130.0.0.1
4-EM20-2 18.1.2.1 255.255.255.252
NE2 4-EM20-1 18.1.1.2 255.255.255.252 130.0.0.2
4-EM20-2 18.1.1.5 255.255.255.252
NE3 4-EM20-1 18.1.2.2 255.255.255.252 130.0.0.3

4-EM20-2 18.1.2.5 255.255.255.252
NE4 4-EM20-1 18.1.1.6 255.255.255.252 130.0.0.4
4-EM20-2 18.1.2.6 255.255.255.252
2.2.2 Service Planning
2.2.2.1 Basic attributes of Tunnels
Parameter Tunnel Name Tunnel Protocol Signaling Direction Protected

ID Type Type Type
Plan NE1_NE4_working 10 MPLS Static CR Bidirectional Unprotected
NE1_NE4_protection 20 MPLS Static CR Bidirectional Unprotected
NE2_NE4_working 30 MPLS Static CR Bidirectional Unprotected
NE2_NE4_protection 40 MPLS Static CR Bidirectional Unprotected
2.2.2.2 Parameters of Tunnels
Tunnel Node Node In Interface In Label Reverse In Out Interface Out Label
ID Type Label
10 NE1 Ingress - - 103 4-EM20-1 100
NE2 Transit 4-EM20-1 100 102 4-EM20-2 101
NE4 Egress 4-EM20-1 101 - - -
20 NE1 Ingress - - 203 4-EM20-2 200
NE3 Transit 4-EM20-1 200 202 4-EM20-2 201
NE4 Egress 4-EM20-2 201 - - -
30 NE2 Ingress - - 301 4-EM20-2 300
NE4 Egress 4-EM20-1 300 - - -
40 NE2 Ingress - - 405 4-EM20-1 400
NE1 Transit 4-EM20-1 400 404 4-EM20-2 401
NE3 Transit 4-EM20-1 401 403 4-EM20-2 402
NE4 Egress 4-EM20-1 402 - - -
Tunnel Node Reverse Next Hop Reverse Next Source Node Sink Node
ID Out Label Hop
10 NE1 - 18.1.1.2 - - 130.0.0.4
NE2 103 18.1.1.6 18.1.1.1 130.0.0.1 130.0.0.4
NE4 102 - 18.1.1.5 130.0.0.1 -
20 NE1 - 18.1.2.2 - - 130.0.0.4
NE3 203 18.1.2.6 18.1.2.1 130.0.0.1 130.0.0.4
NE4 202 - 18.1.2.5 130.0.0.1 -
30 NE2 - 18.1.1.6 - - 130.0.0.4
NE4 301 - 18.1.1.5 130.0.0.1 -
40 NE2 - 18.1.1.1 - - 130.0.0.4

NE1 405 18.1.2.2 18.1.1.2 - 130.0.0.4

NE3 404 18.1.2.6 18.1.2.1 - 130.0.0.4
NE4 403 - 18.1.2.5 130.0.0.2 -
2.2.2.3 Parameters of MPLS-TP tunnel OAM

Tunnel ID 10 20 30 40
OAM Status Enabled Enabled Enabled Enabled
MEG ID Type IP Based IP Based IP Based IP Based
MEG Level 7 7 7 7
Detection Mode Adaptive Adaptive Adaptive Adaptive
CC Packet Priority 7 7 7 7
CC Packet Interval 1s 1s 1s 1s
Lock Status Unlock Unlock Unlock Unlock
AIS Status Disabled Disabled Disabled Disabled
SD Threshold(%) 0 0 0 0
SF Threshold(%) 0 0 0 0
2.2.2.4 Parameters of Tunnel APS

Protection Type 1:01 1:01
Switching Mode Dual-Ended Dual-Ended
Working Tunnel ID 10 30
Tunnel Name NE1_NE4_working NE2_NE4_working
Protection Tunnel ID 20 40
Tunnel Name NE1_NE4_protection NE2_NE4_protection
Revertive Mode Revertive Revertive
WTR Time (min) 5 5
Hold-off Time (100 ms) 0 0
NOTE:
Services are protected by

a single protection
scheme. Therefore, retain
the default value 0 for
Hold-off Time (100 ms).
Protocol State Enabled Enabled
2.2.2.5 Parameters for configuring E-LAN services carried by PWs
Parameter NE1 NE2 NE4

Service ID 1 2 3

Service Name E-LAN-1 E-LAN-2 E-LAN-3

Tag Type C-Aware C-Aware C-Aware
Self-Learning Enabled Enabled Enabled
MAC Address
MAC Address SVL SVL SVL
Learning Mode
2.2.2.6 UNI parameters

Interface 4-EM20-3 4-EM20-4 4-EM20-3 4-EM20-4 4-EM20-3
VLAN ID 100 200 100 200 100, 200
2.2.2.7 PW parameters

PW ID 10 20 10 20
PW Signaling Static Static Static Static
Type
PW Type Ethernet Ethernet Ethernet Ethernet
PW Direction Bidirectional Bidirectional Bidirectional Bidirectional
PW Incoming 20 30 20 30
Label
PW Outgoing 20 30 20 30
Label
Ingress Tunnel NE1_NE4_workin NE2_NE4_working NE1_NE4_workin NE2_NE4_workin
g g g
Peer LSR ID 130.0.0.4 130.0.0.4 130.0.0.1 130.0.0.2
Egress Tunnel NE1_NE4_workin NE2_NE4_working NE1_NE4_workin NE2_NE4_workin
g g g

2.2.3 Configuration Process (in End-to-End Mode)
Step Action
1 Configure a working tunnel (NE1_NE4_working) carrying PWs and MPLS-TP
Tunnel OAM for the tunnel by following instructions in Configuring an MPLS
Tunnel in End-to-End Mode.
2 See Service Planning and 1 to configure a working tunnel (NE2_NE4_working),

protection tunnels, and MPLS-TP Tunnel OAM for the tunnels.

3 Configure Tunnel APS from NE1 to NE4 .
4 See Service Planning and 3 to configure Tunnel APS from NE2 to NE4.

5 Configure E-LAN services carried by PWs in end-to-end mode.

2.2.4 2.2.4 Configuration Process (on a Per-NE Basis)
Step Action
1 Configure a working tunnel (NE1_NE4_working) that carries PWs on NE 1, NE2,
and NE 4 by following instructions in Configuring an MPLS Tunnel on a Per-NE
Basis.
NE1:
NE2:
NE4:

2 See Service Planning and 1 to configure a working tunnel (NE2_NE4_Working)

that carry PWs on NE1, NE2, NE3, and NE4 and a protection tunnel.
3 See Service Planning to configure MPLS-TP tunnel OAM on NE1, NE2 and NE4
by following instructions in Configuring MPLS-TP Tunnel OAM.
NE1 is used as an example:
4 See Service Planning to configure Tunnel APS on NE1, NE2 and NE4.
NE1 is used as an example:

5 Configure an E-LAN service on NE4.

a. In the NE Explorer of NE4, choose Configuration > Packet Configuration >
Ethernet Service Management > E-LAN Service from the Function Tree.
b. Click New. In the displayed New E-LAN Service dialog box, set the
parameters for an E-LAN service carried by a PW.
c. Click the UNI tab and click Configuration on the tab page. Set UNI
parameters in the displayed Configure Port dialog box. Click OK
d. Click the NNI tab and then the PW tab. Click Add. Set PW parameters in the
displayed Configure PW dialog box. Click OK.

5 Configure the other PW on NE4 in the same way.

e. Click the Split Horizon Group tab and click New on the tab page. Set
parameters for the split horizon group in the displayed New Split Horizon
Group dialog box.
Configure an E-LAN service carried by a PW on NE1 by referring to step 5.
Configure an E-LAN service carried by a PW on NE2 by referring to 5.

Chapter 3 Configuring Native Ethernet

Services on the Packet Plane
3.1 Point-to-Point Transparently Transmitted E-Line Services

3.1.1 Networking Diagram
On the network shown in Figure above, NE1 is located at the edge of the backhaul network and
it needs to transparently transmit Ethernet services from the NodeB to NE2.To meet the
requirement, it is advisable to configure transparently transmitted point-to-point E-Line services.
3.1.2 Configuration Procedure (on a Per-NE Basis)
Step Action
1 Set basic attributes for Ethernet ports.
NOTE:
a. For a port that carries transparently transmitted point-to-point services,
Encapsulation Type takes the fixed value of Null.
b. In this example, the GE port on the NodeB works in auto-negotiation mode.
Therefore, the peer GE port must also work in auto-negotiation mode. If the
peer Ethernet port works in another mode, the local Ethernet port must work
in a consistent mode. The working modes of the Ethernet ports within the
backhaul network are uniformly planned as auto-negotiation.

2 Configure E-Line services.
NOTE:
a. The source VLAN ID and sink VLAN ID for a transparently transmitted
point-to-point E-Line service need to be left empty.
3.2 VLAN-Based E-Line Services


Configure Ethernet services according to the following requirements:

 NodeB1 and NodeB2 provide FE ports whose port rate is 100 Mbit/s.
 Services transmitted by each NodeB carry VLAN IDs, and VLAN IDs on the entire
network are uniformly planned.
To meet these requirements, it is advisable to configure VLAN-based E-Line services on these NEs.
Step Action
1 Configuring Ethernet Ports(NE1 is used as an example).
a. Set basic attributes for Ethernet ports.
b. Query the Layer 2 attributes of the Ethernet ports and ensure that the Tag
attribute is Tag Aware.
c. Refer to the configuration of NE1 and repeat steps a through b to configure

Ethernet ports on NE2 to NE4. Ensure that the encapsulation type is set to
802.1Q for all ports.

2 Configuring Service Information.
a. Configure E-Line services,NE1 is used as an example.
b. Repeat a to configure E-Line services on NE2 to NE4
3.3 QinQ-Based E-Line Services



 NodeB1 and NodeB2 provide FE ports whose port rate is 100 Mbit/s.
 The VLAN ID used by the services on an NodeB is allocated by the RNC that manages the
NodeB. Therefore, the VLAN IDs of services on NodeBs that are managed by different
RNCs may be the same. To solve this problem, an RNC must allocate a unique S-VLAN ID
to services on each managed NodeB, and S-VLAN IDs on the entire network must be
uniformly planned. If NodeB1 uses C-VLAN IDs 1-100 and NodeB2 uses C-VLAN IDs 1-
200 for their respective services, different S-VLAN IDs must be added on the network side to
separate the services from the two NodeBs. For example, S-VLAN ID 201 is added for
NodeB1, and S-VLAN ID 200 is added for NodeB2.
To meet these requirements, it is advisable to configure QinQ-based E-Line services on these NEs.

Step Action
1 Configuring Ethernet Ports.
a. Query the Layer 2 attributes of the Ethernet ports and ensure that the Tag
attribute is Tag Aware. NE1 is used as an example.
attribute is Tag Aware. NE1 is used as an example.
c. Repeat steps 1 through 2 to configure Ethernet ports on NE2 to NE4.

2 Configuring Service Information.

a. Configure a QinQ link. NE1 is used as an example.
b. Configure E-Line services.NE1 is used as an example.
c. Repeat steps 1 through 2 to configure E-Line services on NE2 to NE4.

3.4 E-LAN Services Based on 802.1q Bridge


 NodeB1, NodeB2, and NodeB3 provide FE ports whose port rate is 100 Mbit/s.
 NodeB3 is located in domain 1, and NodeB1 and NodeB2 are located in domain 2.
 NodeBs in the same domain use the same VLAN ID, and the services from different
domains are separated by VLAN ID.
The network needs to provide the broadcast packet suppression function.
To meet these requirements, it is advisable to configure IEEE 802.1q bridge-based E-LAN services on
these NEs and enable the broadcast packet suppression function.

Step Action
1 Configuring Ethernet Ports.
a. Set basic attributes for Ethernet ports.NE1 is used as an example.
attribute is Tag Aware.NE1 is used as an example.
c. Set advanced attributes for Ethernet ports.NE1 is used as an example.
d. Repeat steps a through c to configure Ethernet ports on NE2 to NE4.

2 Configuring Service Information
a. Configure E-LAN services.NE1 is used as an example.
b. Repeat a to configure E-LAN services on NE2 to NE4.

c. Set Tag Type to C-Aware for 802.1q Bridge-based E-LAN Services.
Chapter 4 Network Level Protection (Packet)
4.1 Tunnel APS
Step Action
1 Prerequisites:
 The working and protection MPLS tunnels have been created.
 MPLS-TP OAM of each MPLS tunnel in the protection group has been
enabled.
NOTE:
The protection MPLS tunnel cannot carry any extra services.
2 In the NE Explorer, select the source NE of the MPLS tunnel and choose
Configuration > Packet Configuration > APS Protection Management from
the Function Tree.

3 Click New. Then, the New Tunnel Protection Group dialog box is displayed.
4 Set the parameters for the MPLS tunnel protection group. Select the working and
protection MPLS tunnels.
NOTE:
 Protection Type: You can set Protection Type to 1:1.
 Switching Mode: You can set Switching Mode to Dual-Ended.
 BDI Status: If Switching Mode is set to Single-Ended, set BDI Status to
Enabled so that BDI packets will be sent to the ingress node to trigger
protection switching on the ingress node when the egress node detects a fault.
 Revertive Mode: You can set Revertive Mode to Non-Revertive or
Revertive. If you set Revertive Mode to Revertive, you can specify the
WTR time.
 Hold-off Time (100ms): The unit is 100 ms. You can set Hold-off Time
(100ms) to be an integer from 0 to 100, namely, 0 to 10 seconds.
5 Click OK. The MPLS tunnel protection group is configured successfully.

6 Refer to steps 1-4 to configure the protection group on the sink NE.
Enable the protocol of the MPLS APS protection group.
A. In the NE Explorer, select the

source NE of the MPLS tunnel and
choose
Configuration > Packet
Configuration > APS Protection
Management from the Function
Tree.
B. Right-click a created APS
protection group and choose Start
Protocol from the shortcut menu.
C. A dialog box is displayed,
indicating that the operation is
successful.
Protocol Status of the APS
protection group changes to
Enabled.
4.2 PW APS
Step Action
1 In the NE Explorer, select the required NE, and choose Configuration > Packet
Configuration > Ethernet Service Management > E-Line Service from the
Function Tree.
2 Click the UNI tab, and then click New.
3 In the New E-Line Service dialog box that is displayed, set the E-Line service
parameters according to the service plan. To be specific, set Direction to UNI-
NNI, and Protection Type to PW APS.

4 Click Configure PW. In the Configure PW dialog box, click the General
Attributes tab. In the General Attributes dialog box, set the parameters of the
working and protection PWs according to the network plan.
5 In the Protection Group tab, set the parameters of the PW APS protection group.
NOTICE:
When you create a PW APS protection group, it is recommended that you set
Enabling Status to Disabled. Start the protocol only when the PW APS protection
group is successfully created on NEs at both ends. If the APS protocol is first
enabled at the local NE and then at the opposite NE, the opposite NE may receive
services abnormally.

6 In the MPLS-TP OAM tab, set PW OAM parameters for the working and
protection PWs. To be specific, set CC Packet Interval(ms) to 3.33.
NOTICE:
CC Packet Interval(ms) is set to 3.33 ms to ensure that the protection switching
time is within 50 ms. When the delay jitter is large on a live network, the packet
detection period of PW OAM needs to be larger than the maximum value of the
network delay jitter. Otherwise, PW APS switching may occur frequently.
7 Click OK.
8 Perform the preceding operations to create a PW APS protection group on the
opposite NE. Then, enable the APS protocol at both ends.

OptiX OSN 1800V Packet Service Configuration Practice Guide

Uploaded by

Copyright:

Available Formats

OptiX OSN 1800V Packet Service Configuration Practice Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OptiX OSN 1800V Packet Service Configuration Practice Guide

Uploaded by

Copyright:

Available Formats

Revision Record

Course Code Product Product Version Course Version ISSUE

Developer/Modifier Time Approver New/Update

Confidential Information of Huawei. No Spreading without Permission

Confidential Information of Huawei. No Spreading without Permission

Chapter 1 Basic Configuration On Packet

1.1 Configure LSR ID

1.2 Setting Attributes for Ethernet Ports

Step Application Scenario Required Port Attribute

Confidential Information of Huawei. No Spreading without Permission

1.2.1 Setting General Attributes for Ethernet Ports

Confidential Information of Huawei. No Spreading without Permission

1.2.2 Setting Layer 2 Attributes for Ethernet Ports

1.2.3 Setting Layer 3 Attributes for Ethernet Ports

1.2.4 Setting Advanced Attributes for Ethernet Ports

Confidential Information of Huawei. No Spreading without Permission

1.2.5 Configuring Flow Control

1.3 Configuring PKT Virtual Ports for Universal Line Boards

Confidential Information of Huawei. No Spreading without Permission

1.4 Configuring a Bidirectional MPLS Tunnel

Confidential Information of Huawei. No Spreading without Permission

3 Set the parameters of the bidirectional MPLS tunnels.

1.4.2 Configuring an MPLS Tunnel in End-to-End Mode

Confidential Information of Huawei. No Spreading without Permission

2 Set the basic information about the MPLS tunnel.

Confidential Information of Huawei. No Spreading without Permission

5 Click OK. The configuration for tunnel is complete.

Confidential Information of Huawei. No Spreading without Permission

Chapter 2 Configuring ETH PWE3 Services

2.1 E-Line Services Carried by PWs

The service requirements of User A and User B are as follows:

NE IP Address IP Mask LSR ID

Confidential Information of Huawei. No Spreading without Permission

2.1.2 Service Planning

2.1.2.1 Basic attributes of Tunnels

Parameter Tunnel Name Tunnel Protocol Signaling Direction Protection

2.1.2.2 Parameters of Tunnels

10 NE1 100 - 18.1.1.2 - - 130.0.0.4

2.1.2.3 Parameters of MPLS-TP tunnel OAM

Parameter Parameter Planning

Confidential Information of Huawei. No Spreading without Permission

2.1.2.4 Parameters of Tunnel APS

Parameter Parameter Planning

The services are not protected by multiple

Protocol State Enabled

2.1.2.5 Planning information of the PWs

Parameter PW of User A PW of User B

PW Direction Bidirectional Bidirectional

Bandwidth Limit Enabled Enabled

Confidential Information of Huawei. No Spreading without Permission

Parameter User A User B

VLANs 100 100

2.1.3 Configuration Process (in End-to-End Mode)

Confidential Information of Huawei. No Spreading without Permission

Confidential Information of Huawei. No Spreading without Permission

4 Configure tunnel APS.

Confidential Information of Huawei. No Spreading without Permission

2.1.4 Configuration Process (on a Per-NE Basis)

Confidential Information of Huawei. No Spreading without Permission