Professional Documents
Culture Documents
Tesis Hauwei BBU 3900 PDF
Tesis Hauwei BBU 3900 PDF
System
V100R002C01
02
Date
2010-09-24
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
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.
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 02 (2010-09-24)
Version
iManager U2000
V100R002C01
Intended Audience
This document describes the operations, such as how to configure the communication, clock and
service of the RTN equipment on the U2000. This document also provides the glossary and the
acronyms and abbreviations.
This document guides the user to understand basic operations of the U2000.
This document is intended for:
l
NMS Administrators
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
DANGER
WARNING
Issue 02 (2010-09-24)
iii
Symbol
Description
CAUTION
TIP
NOTE
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
Italic
[]
{ x | y | ... }
[ x | y | ... ]
{ x | y | ... }*
[ x | y | ... ]*
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
iv
Convention
Description
Boldface
>
Issue 02 (2010-09-24)
Update History
Updates between document versions are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Issue 02 (2010-09-24)
Contents
Contents
About This Document...................................................................................................................iii
1 Creating NEs, Links, and Topology Subnets........................................................................1-1
1.1 Creating NEs...................................................................................................................................................1-2
1.1.1 Creating NEs in Batches........................................................................................................................1-2
1.1.2 Creating a Single NE..............................................................................................................................1-4
1.2 Configuring the NE Data.................................................................................................................................1-5
1.2.1 Configuring the NE Data Manually.......................................................................................................1-6
1.2.2 Replicating the NE Data.........................................................................................................................1-7
1.2.3 Uploading the NE Data..........................................................................................................................1-8
1.3 Checking Board Parameters............................................................................................................................1-8
1.4 Creating Links...............................................................................................................................................1-13
1.4.1 Creating Fibers Automatically.............................................................................................................1-13
1.4.2 Automatically Creating Radio Links....................................................................................................1-15
1.4.3 Manually Creating Radio Links...........................................................................................................1-16
1.5 Creating a Topology Subnet..........................................................................................................................1-16
2 DCN Management.....................................................................................................................2-1
2.1 DCN Overview................................................................................................................................................2-3
2.1.1 Background of DCN...............................................................................................................................2-4
2.1.2 DCN Solutions.......................................................................................................................................2-5
2.1.3 HWECC Features and Functions...........................................................................................................2-5
2.1.4 HWECC Application..............................................................................................................................2-6
2.1.5 Basic Concepts of IP over DCC.............................................................................................................2-7
2.1.6 Features and Functions of IP over DCC.................................................................................................2-8
2.1.7 Application of IP over DCC...................................................................................................................2-8
2.1.8 Basic Concepts of OSI over DCC........................................................................................................2-12
2.1.9 Features and Functions of OSI over DCC............................................................................................2-13
2.1.10 Application of OSI over DCC............................................................................................................2-13
2.2 DCN Management Flow...............................................................................................................................2-15
2.3 Configuring ECC Communication................................................................................................................2-16
2.3.1 Modifying the NE ID...........................................................................................................................2-17
2.3.2 Configuring an Extended ECC Communication..................................................................................2-18
2.3.3 Viewing the ECC Route for an NE......................................................................................................2-19
Issue 02 (2010-09-24)
vii
Contents
3 Configuring Clocks....................................................................................................................3-1
viii
Issue 02 (2010-09-24)
Contents
5 Configuring Orderwire.............................................................................................................5-1
5.1 Configuring Orderwire....................................................................................................................................5-2
5.2 Configuring F1 Data Port Services................................................................................................................. 5-2
5.2.1 F1 Data Port Services.............................................................................................................................5-2
Issue 02 (2010-09-24)
ix
Contents
Issue 02 (2010-09-24)
Contents
xi
Contents
Issue 02 (2010-09-24)
Contents
xiii
Contents
Issue 02 (2010-09-24)
Contents
xv
Contents
xvi
Issue 02 (2010-09-24)
Contents
xvii
Contents
Issue 02 (2010-09-24)
Contents
14.6.5.1 Bridge..........................................................................................................................................14-241
14.6.5.2 STP/RSTP...................................................................................................................................14-241
14.6.5.3 IGMP Snooping...........................................................................................................................14-246
14.6.6 Planning Guide...............................................................................................................................14-248
14.6.7 Configuration Guide.......................................................................................................................14-249
14.6.8 Creating the Ethernet LAN Service................................................................................................14-249
14.6.9 Modifying the Mounted Port of a Bridge.......................................................................................14-254
14.6.10 Creating the VLAN Filter Table..................................................................................................14-257
14.6.11 Creating the Entry of a MAC Address Table Manually ..............................................................14-259
14.6.12 Modifying the Aging Time of the MAC Address Table Entry....................................................14-260
14.6.13 Querying the Actual Capacity of the MAC Address Table and the Dynamic Entry...................14-261
14.6.14 Configuring the Spanning Tree Protocol ....................................................................................14-262
14.6.15 Querying the Running Information About the Spanning Tree Protocol......................................14-267
14.6.16 Configuring the IGMP Snooping Protocol...................................................................................14-267
14.6.17 Querying the Running Information About the IGMP Snooping Protocol ..................................14-269
14.6.18 Modifying the Aging Time of the Multicast Table Item..............................................................14-270
14.6.19 Querying the Multicast Router Port.............................................................................................14-271
14.6.20 Configuring the Static Multicast Table Item................................................................................14-271
14.6.21 Querying the Multicast Table Item..............................................................................................14-272
14.7 Configuring QoS.....................................................................................................................................14-272
14.7.1 Feature Description........................................................................................................................14-273
14.7.2 Basic Concepts...............................................................................................................................14-274
14.7.2.1 Flow Classification......................................................................................................................14-275
14.7.2.2 CAR.............................................................................................................................................14-275
14.7.2.3 CoS..............................................................................................................................................14-276
14.7.2.4 Traffic Shaping............................................................................................................................14-277
14.7.3 Availability.....................................................................................................................................14-278
14.7.4 Relation with Other Features..........................................................................................................14-279
14.7.5 Realization Principle......................................................................................................................14-279
14.7.5.1 CAR.............................................................................................................................................14-279
14.7.5.2 Traffic Shaping............................................................................................................................14-281
14.7.5.3 Egress Queue Scheduling............................................................................................................14-282
14.7.6 Planning Guide...............................................................................................................................14-284
14.7.7 Configuration Guide.......................................................................................................................14-285
14.7.7.1 Creating a Flow...........................................................................................................................14-286
14.7.7.2 Creating the CAR........................................................................................................................14-289
14.7.7.3 Creating the CoS.........................................................................................................................14-292
14.7.7.4 Binding the CAR/CoS.................................................................................................................14-294
14.7.7.5 Configuring the Traffic Shaping.................................................................................................14-295
14.7.7.6 Configuring the CoS of the IFH2 Board.....................................................................................14-297
14.7.7.7 Setting the Queue Scheduling Mode...........................................................................................14-298
14.7.7.8 Creating a Flow by Using a Template.........................................................................................14-299
Issue 02 (2010-09-24)
xix
Contents
Issue 02 (2010-09-24)
Contents
xxi
Contents
18.3 Availability..................................................................................................................................................18-7
18.4 Realization Principle...................................................................................................................................18-7
18.5 Configuration Guide....................................................................................................................................18-9
Issue 02 (2010-09-24)
Contents
22 Configuring an IP Tunnel....................................................................................................22-1
22.1 IP Tunnel.....................................................................................................................................................22-2
22.2 Configuring a UDP PW Port.......................................................................................................................22-2
22.3 Creating IP Tunnels.....................................................................................................................................22-3
22.4 Deleting IP Tunnels.....................................................................................................................................22-3
xxiii
Contents
29 OAM Management................................................................................................................29-1
29.1 Configuring ETH OAM..............................................................................................................................29-2
29.1.1 Feature Introduction...........................................................................................................................29-2
29.1.2 Basic Concept.....................................................................................................................................29-3
29.1.2.1 IEEE 802.1ag OAM Management..................................................................................................29-4
29.1.2.2 IEEE 802.1ag OAM Operation.......................................................................................................29-7
29.1.2.3 IEEE 802.3ah OAM Operations......................................................................................................29-8
29.1.3 Availability.........................................................................................................................................29-9
29.1.4 Function Implementation................................................................................................................. 29-10
29.1.4.1 802.1ag OAM................................................................................................................................29-10
29.1.4.2 802.3ah OAM................................................................................................................................29-14
29.1.5 Using the IEEE 802.1ag OAM.........................................................................................................29-23
29.1.5.1 Creating MDs................................................................................................................................29-24
29.1.5.2 Creating MAs................................................................................................................................29-25
29.1.5.3 Creating MPs.................................................................................................................................29-26
29.1.5.4 Performing a Continuity Check.....................................................................................................29-27
29.1.5.5 Performing a Loopback Check......................................................................................................29-28
29.1.5.6 Performing a Link Trace Check....................................................................................................29-29
29.1.5.7 Activating the AIS(RTN 600).......................................................................................................29-31
29.1.5.8 Performing a Ping Test(RTN 600)................................................................................................29-31
xxiv
Issue 02 (2010-09-24)
Contents
xxv
Contents
31.3 Availability..................................................................................................................................................31-7
31.4 Realization Principle...................................................................................................................................31-8
31.5 Configuration Guide....................................................................................................................................31-9
31.5.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port...................................31-10
31.5.2 Configuring an Alarm Group for an Ethernet Port.......................................................................... 31-10
31.5.3 Configuring a History Control Group..............................................................................................31-11
31.5.4 Browsing the Performance Data in the History Group of an Ethernet Port.....................................31-11
31.5.5 Setting Performance Monitoring Status for an Ethernet Port.......................................................... 31-12
Issue 02 (2010-09-24)
Contents
Issue 02 (2010-09-24)
xxvii
Figures
Figures
Figure 2-1 DCN network......................................................................................................................................2-3
Figure 2-2 Positions of DCC bytes in SDH overheads........................................................................................2-5
Figure 2-3 Networking that involves only Huawei equipment............................................................................2-6
Figure 2-4 Networking that involves Huawei equipment and third-party equipment..........................................2-7
Figure 2-5 Gateway NE mode..............................................................................................................................2-8
Figure 2-6 Gateway NE mode (by default gateway)............................................................................................2-9
Figure 2-7 Direct connection mode (by static routes)........................................................................................2-10
Figure 2-8 Direct connection mode through a router (by static routes).............................................................2-11
Figure 2-9 Format of a simple NSAP address....................................................................................................2-12
Figure 2-10 Format of a complicated NSAP address.........................................................................................2-12
Figure 2-11 Third-party equipment forwarding OAM information of Huawei equipment...............................2-14
Figure 2-12 Huawei equipment forwarding OAM information of third-party equipment.................................2-15
Figure 2-13 DCN management flow..................................................................................................................2-16
Figure 2-14 External clock interfaces used to transparently transmit DCC information (example)..................2-33
Figure 2-15 External clock interfaces used to transparently transmit DCC information (example)..................2-34
Figure 2-16 Inband DCN networking mode.......................................................................................................2-41
Figure 2-17 Inband networking scheme.............................................................................................................2-42
Figure 2-18 Outband networking scheme..........................................................................................................2-43
Figure 3-1 Configuration flow when SSM protocol is disabled..........................................................................3-3
Figure 3-2 Configuration flow when standard SSM protocol is enabled.............................................................3-3
Figure 3-3 Configuration flow when extended SSM protocol is enabled............................................................3-3
Figure 3-4 Clock synchronization scheme for a chain network...........................................................................3-4
Figure 3-5 Clock synchronization scheme for a tree network..............................................................................3-5
Figure 3-6 Clock synchronization scheme for a ring network (the entire ring network line is an SDH line)
...............................................................................................................................................................................3-6
Figure 3-7 Clock synchronization scheme for a ring network (not the entire ring network line is an SDH line)
...............................................................................................................................................................................3-7
Figure 3-8 Clock synchronization scheme for networking with convergence at tributary ports.........................3-8
Figure 3-9 Clock synchronization......................................................................................................................3-10
Figure 4-1 Architecture of the IEEE 1588V2 clock.............................................................................................4-4
Figure 4-2 Master-slave synchronization process................................................................................................4-5
Figure 4-3 Networking diagram for typical application of the PTP clock...........................................................4-7
Figure 4-4 Configuration flow for the PTP clock................................................................................................4-8
Figure 5-1 Configuring the F1 data port service..................................................................................................5-3
Issue 02 (2010-09-24)
xxix
Figures
Issue 02 (2010-09-24)
Figures
Figure 11-30 1+1 SD HSM realization principle (after the switching, in the receive direction).....................11-26
Figure 12-1 Multiplex section schematic diagram.............................................................................................12-4
Figure 12-2 SNCP service pair...........................................................................................................................12-7
Figure 12-3 SNCP service..................................................................................................................................12-7
Figure 12-4 N+1 protection .............................................................................................................................12-11
Figure 12-5 Realization principle of 2+1 protection (before the switching)....................................................12-14
Figure 12-6 Realization principle of 2+1 protection (after the switching).......................................................12-14
Figure 12-7 Realization principle of the 3+1 protection (before the switching)..............................................12-15
Figure 12-8 Realization principle of the 3+1 protection (after the switching).................................................12-16
Figure 12-9 Configuration flow for the N+1 protection mode.........................................................................12-18
Figure 12-10 1+1 linear MSP ..........................................................................................................................12-26
Figure 12-11 1:N linear MSP ..........................................................................................................................12-27
Figure 12-12 Realization principle of 1+1 linear MSP (before the switching)................................................12-29
Figure 12-13 Realization principle of 1+1 linear MSP (after the switching, in the single-ended mode)........ 12-30
Figure 12-14 Realization principle of 1+1 linear MSP (after the switching, in the dual-ended mode)...........12-30
Figure 12-15 Realization principle of 1:1 linear MSP (before the switching).................................................12-31
Figure 12-16 Realization principle of 1:1 linear MSP (after the switching)....................................................12-31
Figure 12-17 Two-fiber bidirectional MSP ring.............................................................................................. 12-39
Figure 12-18 Realization principle of the two-fiber bidirectional ring MSP (before the switching)...............12-40
Figure 12-19 Realization principle of the two-fiber bidirectional ring MSP (after the switching)..................12-41
Figure 12-20 Sub-Network Connection Protection..........................................................................................12-46
Figure 12-21 SNCP service pair.......................................................................................................................12-47
Figure 12-22 SNCP realization principle (before the switching).....................................................................12-48
Figure 12-23 SNCP realization principle (after the switching)........................................................................12-48
Figure 12-24 MPLS APS 1+1 protection.........................................................................................................12-62
Figure 12-25 MPLS APS 1:1 protection..........................................................................................................12-63
Figure 12-26 MPLS APS 1+1 protection.........................................................................................................12-66
Figure 12-27 MPLS APS 1:1 protection..........................................................................................................12-66
Figure 12-28 R-APS format.............................................................................................................................12-72
Figure 12-29 ERPS switching process (upon a fault not on the RPL link)......................................................12-76
Figure 12-30 ERPS switching process (upon a fault on the RPL link)............................................................12-77
Figure 12-31 Ethernet ring protection switching............................................................................................. 12-79
Figure 12-32 Link aggregation group.............................................................................................................. 12-82
Figure 12-33 Application of the LACP protocol..............................................................................................12-84
Figure 12-34 Application of the link aggregation group..................................................................................12-85
Figure 13-1 Numbering VC-12 timeslots by order............................................................................................13-3
Figure 13-2 Numbering VC-12 timeslots in the interleaved scheme ................................................................13-4
Figure 13-3 Chain network.................................................................................................................................13-7
Figure 13-4 SNCP ring with unprotected chain...............................................................................................13-19
Figure 13-5 Networking diagram.....................................................................................................................13-35
Figure 13-6 Planning the radio link..................................................................................................................13-37
Figure 13-7 IDU board configuration (NE1)....................................................................................................13-38
Issue 02 (2010-09-24)
xxxi
Figures
Issue 02 (2010-09-24)
Figures
xxxiii
Figures
Issue 02 (2010-09-24)
Figures
xxxv
Figures
xxxvi
Issue 02 (2010-09-24)
Tables
Tables
Table 1-1 SDH board parameters.........................................................................................................................1-9
Table 1-2 PDH board parameters.......................................................................................................................1-10
Table 1-3 RTN board parameters.......................................................................................................................1-10
Table 1-4 Data board parameters........................................................................................................................1-11
Table 3-1 SSM allocation...................................................................................................................................3-11
Table 3-2 Methods of selecting clock sources in different modes.....................................................................3-12
Table 5-1 Configuration of the synchronous data port.........................................................................................5-8
Table 5-2 Configuration of the synchronous data port.........................................................................................5-8
Table 5-3 Configuration of the asynchronous data services...............................................................................5-11
Table 5-4 Configuration of the asynchronous data services...............................................................................5-12
Table 6-1 Configuration of the external alarms....................................................................................................6-4
Table 6-2 Configuration of the external alarms....................................................................................................6-4
Table 7-1 SDH board parameters.........................................................................................................................7-2
Table 7-2 PDH board parameters.........................................................................................................................7-3
Table 7-3 RTN board parameters.........................................................................................................................7-3
Table 7-4 Data board parameters..........................................................................................................................7-4
Table 7-5 Methods used by ports to process data frames...................................................................................7-28
Table 7-6 Methods used by ports to process data frames...................................................................................7-35
Table 8-1 Application scenario of PDH interfaces...............................................................................................8-5
Table 8-2 Application scenario of Ethernet interfaces.......................................................................................8-10
Table 8-3 Application scenario of microwave interfaces...................................................................................8-14
Table 11-1 Availability of the 1+1 HSB feature................................................................................................11-3
Table 11-2 Availability of the 1+1 HSB feature................................................................................................11-3
Table 11-3 Availability of the 1+1 FD feature.................................................................................................11-10
Table 11-4 Availability of the 1+1 FD feature.................................................................................................11-10
Table 11-5 Availability of the 1+1 SD feature.................................................................................................11-19
Table 11-6 Availability of the 1+1 SD feature.................................................................................................11-19
Table 12-1 MSP type..........................................................................................................................................12-4
Table 12-2 Preemptible relation of priorities of MSP protection switching......................................................12-5
Table 12-3 SNCP parameters.............................................................................................................................12-8
Table 12-4 Availability of the N+1 protection feature.....................................................................................12-13
Table 12-5 Availability of the N+1 protection feature.....................................................................................12-13
Table 12-6 Description of the configuration flow of the N+1 protection mode...............................................12-18
Issue 02 (2010-09-24)
xxxvii
Tables
xxxviii
Issue 02 (2010-09-24)
Tables
xxxix
Tables
xl
Issue 02 (2010-09-24)
Tables
Issue 02 (2010-09-24)
xli
Issue 02 (2010-09-24)
1-1
Prerequisite
l
Procedure
Step 1 Choose File > Discovery > NE from the main menu. The Auto Discovery window is displayed.
Step 2 Click the Transport NE Search tab.
Step 3 Optional: Enter the network segment or IP addresses NEs to search for the NEs.
1-2
1.
Click Add and the Input Search Domain dialog box is displayed.
2.
Issue 02 (2010-09-24)
NOTE
You can repeat Steps 2 through 3 to add more search fields. You can delete the system default search
field.
l If you use IP address to search for NEs, and the IP address of the U2000 computer and that of
the GNE are within the same network segment, you can select IP Address Range of GNE or
IP Address of GNE.
l If the IP addresses are not within the same network segment, select only IP Address of GNE.
l If you use NSAP address, you can only select NSAP address.
Step 4 Optional: If you fail to enter a network segment correctly, enable IP auto discovery and enter
the User Name and Password of the NEs.
NOTE
After enabling IP auto discovery, you can obtain the IP address of the GNE and search out all the NEs
related to the GNE.
Select Search for NE. All NEs in the selected domain are searched out.
Select Create device after search, enter the NE User and Password.
NOTE
Select Upload after create. The data related to the NEs are uploaded to the U2000 after
the NEs are created.
NOTE
You can select all options in the Search for NE area to search for NEs, create NEs, and upload the NE
data at a time.
1-3
Step 7 When the search ends or if you click Stop, select the uncreated NEs in the Result list and click
Create. The Create dialog box is displayed.
Step 8 Enter the NE user name and password.
NOTE
Postrequisite
After an NE is created, if you fail to log in to the NE, possible causes are listed as follows:
l
The password for the NE user is incorrect. Enter the correct password for the NE user.
The NE user is invalid or the NE user is already logged in. Change to use a valid NE user.
Prerequisite
l
The license must be installed and the license must support creating the NE of the type.
Context
First create a GNE, and then create a non-gateway NE.
If the NE is not created properly or the communication between the NE and the U2000 is
abnormal, the NE is displayed in gray color.
Procedure
Step 1 Choose File > Create > NE from the main menu. The Create NE dialog box is displayed.
Step 2 Select the NE type from the Object Type tree.
Step 3 Complete the following information: ID, Extended ID, Name and Remarks.
Step 4 To create a GNE, proceed to Step 5. To create a non-gateway NE, proceed to Step 6.
Step 5 Choose Gateway Type, Protocol and set the IP address or serial port number and serial port
rate.
1-4
1.
2.
Issue 02 (2010-09-24)
If the U2000
communicates with
NEs through
Do...
IP protocol
OSI protocol
NOTE
The domain address that contains a maximum of 13 bytes is entered by the user. NSEL is the port
number of the network-level protocol, with a fixed value of 1d (one byte).
Step 6 Select Non-Gateway from the Gateway Type drop-down list. Select the GNE to which the NE
is associated to from the Affiliated Gateway drop-down list.
Step 7 Enter the NE User and Password.
NOTE
Step 8 Click OK. Click in the blank space of the Main Topology and the NE icon appears in the position
where you clicked.
----End
Result
After an NE is successfully created, the system automatically saves the information, such as the
IP address, NSAP address, subnet mask, and NE ID to the U2000 database.
Postrequisite
After an NE is created, if you fail to log in to the NE, possible causes are listed as follows:
l
The communication between the U2000 and the NE is abnormal. Check the settings of
communication parameters, such as the IP address of the NE and NE ID.
The password for the NE user is incorrect. Enter the correct password for the NE user.
The NE user is invalid or the NE user is already logged in. Change to use a valid NE user.
1-5
You can replicate the data of an existing NE to a new NE, if the existing NE is already
configuration and if the existing NE is of the same NE type and the same NE version as the new
NE.
1.2.3 Uploading the NE Data
By uploading the NE data, you can synchronize the current NE configuration data to the network
management system directly.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The NE must be created successfully.
Background Information
When you manually configure the NE data, the original service data is cleared from the NEs.
Therefore, the communications between the NEs and the U2000 may be interrupted and the
subsequent procedures of manually configuring the NE data cannot be performed. In the case
of the RTN NEs, this operation is used for configuring gateway NEs for the first time.
Procedure
Step 1 Select the NE whose data you want to configure. Double-click the unconfigured NE on the Main
Topology. The NE Configuration Wizard dialog box is displayed.
Step 2 Choose Manual Configuration and click Next. The Confirm dialog box is displayed indicating
that manual configuration clears the data on the NE side.
Step 3 Click OK. The Confirm dialog box is displayed indicating that manual configuration interrupts
the service on the NE.
Step 4 Click OK. The Set NE Attribute dialog box is displayed.
Step 5 Set NE Name, Equipment Type, NE Remarks and Subrack Type and then click Next. The
NE slot window is displayed.
Step 6 Optional: Click Query Logical Information to query the logical boards of the NE.
Step 7 Optional: Click Query Physical Information to query the physical boards of the NE.
NOTE
The Query Logical Information and Query Physical Information operations cannot be performed for
a preconfigured NE.
Step 8 Right-click on the slot to add a board. Click Next to display the Send Configuration window.
Step 9 Choose Verify and Run as required and click Finish.
NOTE
Verification is to run the verification command. Click Finish to deliver the configuration to NEs and the
basic configuration of the NEs is complete. After the successful verification, the NEs start to work normally.
----End
1-6
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The NE must be created successfully.
The type and NE software version of the source NE must be consistent with the type and software
version of the replicated NE.
Procedure
Step 1 Select the NE whose data you need to replicate.
NE to Be Configured
Operation
RTN equipment
Step 2 Select Copy NE Data and click Next. The NE Replication dialog box is displayed.
Step 3 Select the NE from the drop-down list and click Start. The Confirm dialog box is displayed,
indicating that the replication operation copies all the data of the source NE to overwrite all the
data of the selected NE.
NOTE
After the NE data is replicated, only the data on the U2000 side is changed, but the data on the equipment
side is not changed.
Data coping between the NEs of different equipment type is not recommended.
Step 4 Click OK. The Confirm dialog box is displayed, indicating that the replication operation results
in the loss of the original data of the NE to which the data is copied.
Step 5 Click OK to start the replication. The Operation Result dialog box is displayed after a few
seconds.
Issue 02 (2010-09-24)
1-7
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The NE must be created successfully.
Procedure
Step 1 Select the NE whose data you need to Replicate.
NE to Be Configured
Operation
RTN equipment
Step 2 Select Upload and click Next. The Confirm dialog box is displayed, indicating that the upload
may take a long time.
Step 3 Click OK to start the upload. The Operation Result dialog box is displayed when the uploading
is complete.
Step 4 Click Close.
----End
Procedure
Step 1 Select the corresponding navigation path and check the related board parameters.
1.
1-8
Check SDH board parameters. For the SDH board parameters, see Table 1-1.
Issue 02 (2010-09-24)
Parameter
Navigation Path
Application
Scenario
SDH
Laser Switch
a. In the NE
Explorer, select
a board.
b. Choose
Configuration
> SDH
Interface from
the Function
Tree.
c. Click By
Board/Port
(channel) and
select Port from
the drop-down
list.
When configuring
services on an
optical interface of
a board, enable this
parameter.
Optical(Electrical)
Interface Loopback
l Non-loopback:
It is a normal
state. When the
equipment runs
normally, set
this parameter to
non-loopback.
l Inloop: The loop
is performed
toward the local
NE.
l Outloop: The
loop is
performed
toward the
opposite NE.
Inloop and
outloop of an
optical interface
affect services.
They are used to
locate faults.
2.
Issue 02 (2010-09-24)
Check PDH board parameters. For the PDH board parameters, see Table 1-2.
1-9
Paramet
er
Navigation
Path
Tributary
Loopback
PDH
Service
Load
Indication
Retiming
Mode
Application Scenario
a. In the NE
Explorer,
select a board.
b. Choose
Configuratio
n > PDH
Interface
from
the
Function
Tree.
c. Click
By
Board/Port
(channel)
and
select
Port from the
drop-down
list.
3.
Check RTN board parameters. For the RTN board parameters, see Table 1-3.
Table 1-3 RTN board parameters
Boar
d
Type
Paramet
er
Navigation
Path
Radio
Work
Mode
a. In the NE
Explorer,
select a board.
b. Choose
Configuratio
n
>
IF
Interface
from
the
RTN
Radio
Link ID
1-10
Application Scenario
Specifies the microwave working mode. Its
formats are service capacity, working
bandwidth and modulation mode.
The transmit end and the receive end must
have the same settings of the microwave
working mode.
Radio Link ID: 1 to 4094
Issue 02 (2010-09-24)
Boar
d
Type
Paramet
er
Navigation
Path
IF Port
Loopback
Function
Tree.
c. Click
By
Board/Port
(channel)
and
select
Port from the
drop-down
list.
Application Scenario
Sets the loopback status of an intermediate
frequency interface on the equipment.
Non-Loopback refers to the normal status. It
is not required to set loopback during normal
equipment operation.
Outloop means that the input signal passes
through the ingress port and reaches the
intermediate frequency board at the local NE
and then is directly loopbacked to the service
egress end.
Inloop means that the input signal returns
from the intermediate frequency board of the
destination NE along the original trail.
This function is usually used to locate faults
for various IF interfaces. Performing loopback
on an intermediate frequency interface is a
diagnosis function which may affect services
of related ports. Exercise caution before
performing this function.
2M
Wayside
Enable
Status
ATPC
Enable
Status
4.
Check data board parameters. For the data board parameters, see Table 1-4.
Table 1-4 Data board parameters
Boar
d
Type
Ethern
et
Issue 02 (2010-09-24)
Parame
ter
Enabled/
Disabled
Navigation Path
Application Scenario
a. In the NE Explorer,
select a board.
b. Choose
Configuration >
1-11
Boar
d
Type
Parame
ter
Working
Mode
Maximu
m Frame
Length
Navigation Path
Application Scenario
Ethernet Interface
Management
>
Ethernet
Interface from the
Function Tree.
c. Click
External
Port.
d. Click the Basic
Attributes tab.
MAC
Loopbac
k
PHY
Loopbac
k
Entry
Detectio
n
1-12
a. In the NE Explorer,
select a board.
b. Choose
Configuration >
Ethernet Interface
Management
>
Ethernet
Interface from the
Function Tree.
c. Click
External
Port.
d. Click the TAG
Attributes tab.
Issue 02 (2010-09-24)
Step 2 Modify board parameters according to service planning and actual board configurations.
----End
Prerequisite
l
Issue 02 (2010-09-24)
1-13
Context
l
If conflicting fibers are found during the creation, delete the conflicting fibers on the
U2000 before you start creating fibers.
When a fiber between two SDH NEs passes through a WDM NE, if the normal fiber
between an SDH NE and a WDM NE has been created on the U2000, the fiber found by
the trail search function is created as a virtual fiber. If the WDM NE is not created on the
U2000, the fiber is created as a normal fiber.
When a fiber is created, it is usually bidirectional. But when the fiber is connected to the
ports of the REG functions or the SDH and WDM equipment, the fiber is unidirectional.
CAUTION
Fiber/Cable search may interrupt services. Exercise caution when performing this operation.
Procedure
Step 1 CChoose File > Discovery > Fiber from the main menu. The Search for Fiber/Cable window
is displayed.
Step 2 In the left pane select some ports from one or more NEs and click Search to search for the fibers
or cables. A progress bar is displayed showing the progress of the search.
NOTE
l If you check the Do not search the ports with Fiber/Cable created on NMS check box, the system
only searches for the ports that do not have fibers.
l To check if the created fiber is consistent with the actual fiber connection, leave the check box
unchecked.
l If you check the Do not search the ports with Fiber/Cable created on NMS check box, and if all
the selected ports have fibers created, the system displays a message indicating that the search field is
null.
Step 3 A prompt is displayed indicating that the operation is successful. Click Close.
Step 4 To create fibers, select one or more fibers from the Physical Fiber/Cable Link List list and
click Create Fiber/Cable.
NOTE
l When one or more fibers are selected in the Physical Fiber/Cable Link List list, fibers that conflict
with the selected fibers, are shown in the Logical Fiber/Cable Link List list. If there is any conflicting
fiber, proceed to Step 5 and delete it before creating fibers.
l During fiber creation, if all the selected fibers are in the Already created state, the system displays
the message as follows: No fiber to create.
Step 5 To delete the conflicting fibers, from the Logical Fiber/Cable Link List list select one or more
fibers whose values are Yes for the Conflict with logical link (Y/N) parameter in the
Misconnected Fiber list. Click Delete Fiber/Cable.
----End
Subsequent Handling
When the information about the fiber that is created through search is incomplete, you can
supplement the information about the fiber by modifying the fiber/cable information.
1-14
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
The IF board for each NE must be created on the U2000.
Context
The radio frequency wireless signals within the frequency range of 300 MHz to 300 GHz are
called radio signals. The links that transmit radio signals are called radio links.
Procedure
Step 1 Choose File > Discovery > Fiber from the main menu.
Step 2 In the left-hand pane, select IF interfaces for one or multiple radio NEs. Click Search. A progress
bar is displayed.
NOTE
l If you check the Do not search the ports with Fiber/Cable created on NMS check box, the system
does not search for the ports at which radio links are already created.
l If you need to check consistency between the created radio links and the actual radio links, do not check
this check box.
l If you check this check box and if all the selected ports radio links are created, a dialog box is displayed
after the search is complete, telling that the search domain is empty.
Step 3 After the search is complete, a dialog box is displayed, telling that the operation was successful.
Click Close.
Step 4 In the Physical Fiber/Cable Link List list, select one or multiple radio links. Click Create
Fiber/Cable.
NOTE
l When you select one or multiple radio links in the Physical Fiber/Cable Link List list, the radio links
that conflict with the selected ones are automatically displayed in the Logical Fiber/Cable Link
List list. In this case, refer to Step 5 to delete the conflicting radio links before the creation.
l During the creation of radio links, if the selected links are all in the Already created state, the system
prompts No fiber to create.
Step 5 In the Logical Fiber/Cable Link List list, select one or multiple conflicting radio links (the
Conflict with logical link (Y/N) value of which in the Misconnected Fiber list is displayed as
Yes), Click Delete Fiber/Cable.
----End
Subsequent Handling
When the information about the radio link that is created through search is incomplete, you can
supplement the information about the radio link by modifying the fiber/cable information.
Issue 02 (2010-09-24)
1-15
Prerequisite
l
Context
Usually, the radio frequency wireless signal within the frequency range of 300 MHz to 300 GHz
is called a radio signal. The link that transmits radio signals is called a radio link.
Procedure
Step 1 Click the
to a + sign.
shortcut icon on the toolbar of the U2000 Main Topology and the cursor changes
Step 2 Click the source NE of the radio link on the U2000 Main Topology.
Step 3 Select the source board and port in the Select Fiber/Cable Source dialog box.
Step 4 Click OK and the cursor changes to a + sign.
Step 5 Click the sink NE of the radio link on the U2000 Main Topology.
Step 6 Select the sink board and port in the Select Fiber/Cable Sink dialog box.
TIP
When selecting the wrong source or sink NE, right-click and click OK in the Object Selection dialog box
to exit.
Step 7 Click OK. Enter the information of the fiber or cable in the Create Link dialog box.
Step 8 Click OK. The created radio link appears between the source and sink NEs on the U2000 Main
Topology.
----End
Prerequisite
You must be an NM user with "NM operator" authority or higher.
Background Information
A topology subnet is created only to simplify the user interface and has no impact on the NEs.
1-16
Issue 02 (2010-09-24)
Procedure
Step 1 Right-click in the blank space of the U2000 Main Topology and choose New > Subnet from
the shortcut menu.
Step 2 On the subnet tree of the displayed dialog box, select the type of subnet to be created.
Step 3 Click the Property tab. Enter the attributes of the subnet.
Step 4 Click the Select Objects tab. Select the created NEs or subnet from the Available Objects pane
and click
to add the NEs or subnet to the Select Objects pane.
NOTE
indicates that objects on the left pane are selected one by one to the right pane.
indicates that all objects are selcted from the left pane to the right pane.
Issue 02 (2010-09-24)
1-17
2 DCN Management
DCN Management
2-1
2 DCN Management
2-2
Issue 02 (2010-09-24)
2 DCN Management
IP/OSI
DCN
External
DCN
HW ECC or
IP/OSI over
DCC
Internal DCN
OptiX NE
LAN switch
2-3
2 DCN Management
By using the D1-D3 bytes in SDH regenerator section overheads (RSOH), the SDH
provides a 192 kbit/s bandwidth for the DCN.
By using the D4-D12 bytes in SDH multiplex section overheads (MSOH), the SDH
provides a 576 kbit/s bandwidth for the DCN.
By using the D1-D12 bytes in SDH section overheads, the SDH provides a 768 kbit/s
bandwidth for the DCN.
2-4
Issue 02 (2010-09-24)
2 DCN Management
A1
A1
A2
A2
A2
J0
B1
E1
F1
D1
D2
D3
RSOH
AU PTR
B2
B2
B2
K1
K2
D4
D5
D6
D7
D8
D9
D10
D11
D12
S1
M1
MSOH
E2
HWECC
The HWECC protocol is a private protocol developed by Huawei to support the DCN networking
of OptiX equipment. The HWECC protocol features easy configuration and application. As it
is private, the HWECC protocol does not meet the management requirements for hybrid
networking with equipment from other vendors.
The TCP/IP and OSI protocols are standard communication protocols that solve the management
issue in the case of hybrid networking with equipment from other vendors. These two protocols
can also be used in a network that is composed of only Huawei equipment.
NOTE
When OptiX equipment is interconnected with other vendors' equipment that does not support the TCP/IP
and OSI standard communication protocols, Huawei provides the transparent transmission function for
DCC bytes, and provides relevant Ethernet service channels to transparently transmit the OAM information.
2-5
2 DCN Management
the OAM information of the third-party equipment. Hence, customers can use the current DCC
resources to manage all equipment.
NM
computer
Network cable
Fiber
HUB1
GNE1
NE
NE6
6
NE2
NE5
NE3
NE4
Subnet 1
HUB2
NE7
NE12
NE8
NE11
NE9
NE10
Subnet 2
Such networking requires that one gateway NE (GNE) be present for the communication
between other NEs and the U2000 through the Ethernet interface. The NEs communicate with
each other through an optical port or Ethernet interfaces. The subnetworks in Figure 2-3 perform
the extended ECC communication through Ethernet interfaces, such as NE6 and NE7.
NOTE
Extended ECC means the ECC communication by using the Ethernet when there is no connected optical
path between two or more NEs.
2-6
Issue 02 (2010-09-24)
2 DCN Management
Figure 2-4 Networking that involves Huawei equipment and third-party equipment
Third-party NM
HUB
NE
NE
NE
NE
NE
Third-party
equipment
NE
Huawei
equipment
NE
NE
NE
NE
For such networking, the OAM information of the third-party equipment should travel through
Huawei equipment, which provides the function to transparently transmit the DCC. During the
transmission, Huawei equipment does not analyze the data. For the DCC transparent
transmission, perform the corresponding configuration at each NE along the data transmitting
trail.
IP over DCC
The IP over DCC protocol follows the TCP/IP protocol and is applied to control remote NEs
through the Internet. For the IP over DCC protocol, the D bytes (D1-D3 by default) of the
overhead are used for communication. Huawei optical equipment supports dynamic and static
routing.
OSPF
The open shortest path first (OSPF) protocol is a dynamic routing protocol based on the link
state. The NEs update the route table of each NE dynamically by using the OSPF protocol. The
OSPF protocol divides an autonomous domain into different areas so that routes are updated
within an area or between areas. Normally, the gateway NE (GNE) and all the non-gateway NEs
(non-GNEs) managed by it must be within the same OSPF area.
Remote Access
l
Gateway NE mode: The ECC protocol is used. U2000 logs in to the GNE that is connected
to the computer. Then other NEs can be accessed through the NE ID. After the IP over
DCC feature is added, this mode can still be used to access remote NEs.
Direct connection mode: The IP over DCC feature is used, and the remote NE can be
connected directly through the IP address. You just need to enter the destination IP address
Issue 02 (2010-09-24)
2-7
2 DCN Management
in the login interface. For this mode, however, you need to add in advance the static route
or default gateway in the U2000 and the NE that needs to be accessed directly.
NE4
133.168.0.4
255.255.255.0
NE1
129.9.0.2
255.255.255.0
NE name
IP address
Subnet mask
2-8
NE3
133.168.0.3
255.255.255.0
NE2
133.168.0.2
255.255.255.0
Issue 02 (2010-09-24)
2 DCN Management
10.100.11.1
255.255.255.0
Router
NE4
133.168.0.4
255.255.255.0
129.9.0.254
255.255.255.0
NE name
IP address
Subnet mask
Default gateway
NE1
129.9.0.2
255.255.255.0
129.9.0.254
NE3
133.168.0.3
255.255.255.0
NE2
133.168.0.2
255.255.255.0
Issue 02 (2010-09-24)
2-9
2 DCN Management
Static routes
NE4
133.168.0.4
255.255.255.0
NE1
129.9.0.2
NE3
133.168.0.3
255.255.255.0
255.255.255.0
NE name
IP address
Subnet mask
NE2
133.168.0.2
255.255.255.0
Default gateway
Static routes
On the U2000, set the static route to the GNE and non-GNEs.
Add static routes to the U2000 on the destination station and the intermediate station.
As shown in Figure 2-8, the U2000 with the IP address of 10.100.11.12 connects to NE1 through
a router and accesses NE3 in the direct connection mode. Suppose the IP address of the
U2000 is 10.100.11.0 (subnet mask 255.255.255.0). Perform the listed operations:
2-10
Add the static route on NE2 to 10.100.11.0, with the next hop address as 129.9.0.2.
Add the static route on NE3 to 10.100.11.0, with the next hop address as 133.168.0.2.
Issue 02 (2010-09-24)
2 DCN Management
Figure 2-8 Direct connection mode through a router (by static routes)
NM computer
IP address
10.100.11.12
Subnet mask
255.255.255.0
Default gateway 10.100.11.1
Static routes
Destination:129.9.0.2
Mask:255.255.255.0
Destination:133.168.0.0
Mask:255.255.255.0
10.100.11.1
255.255.255.0
NE4
133.168.0.4
255.255.255.0
Router
129.9.0.254
255.255.255.0
NE name
IP address
Subnet mask
Default gateway
Static routes
NE1
129.9.0.2
255.255.255.0
129.9.0.254
NE2
133.168.0.2
255.255.255.0
Static routes
Destination:10.100.11.0
Mask: 255.255.255.0
Next hop:129.9.0.2
NE3
133.168.0.3
255.255.255.0
Static routes
Destination:10.100.11.0
Mask: 255.255.255.0
Next hop:133.168.0.2
Configuration Requirements
If NEs communicate with each other through IP over DCC, note the following rules for setting
the network scale. It is recommended that the number of non-gateway NEs (including the
extended ECC) that a GNE manages be no more than 50 or 60 at most.
If NEs communicate with each other through IP over DCC, note the following rules for setting
the IP address.
l
If NEs communicate through IP addresses on the network layer, each NE need to have a
unique IP address to avoid routing error due to conflict.
NEs support standard A, B, C types of IP addresses, that is, the IP address ranges from
1.0.0.1 to 223.255.255.254. The 127.x.x.x, a loopback address, cannot be used.
The IP address must be used with the subnet mask. The subnet mask supports consecutive
masks in addition to natural masks, for example, 255.255.224.0.
When the IP over DCC communication is used between a GNE and a non-GNE, the IP
addresses can be of different network sections.
Issue 02 (2010-09-24)
2-11
2 DCN Management
The GNE and non-GNEs cannot be in the same IP subnet. The NEs managed through the
same GNE can be in different IP subnets.
Do not configure one GNE and one non-GNE into the same IP subnet.
The Ethernets in the network must belong to different subnets. Otherwise, a routing error
will occur in the whole network. This is not allowed.
The priority of static routes is higher than that of dynamic routes. If there is a conflict, static
routes take priority.
NSAP
The OSI protocol takes the network service access point (NSAP) address as the protocol
identification for nodes. The format of a simple NSAP address is shown in Figure 2-9.
Figure 2-9 Format of a simple NSAP address
AREA ID
SYS ID
NSEL
1-13 bytes
6 bytes
1 byte
AREA ID: The length is adjustable and ranges from 1 to 13 bytes. The AREA ID is used for L2
routing addressing within a domain. The values should be the same in the L1 route domain and
be different in the L2 route domain.
SYS ID: The length is fixed to six bytes. The SYS ID is used for route addressing within a
domain. For Huawei optical equipment, the former three bytes are fixed to 0x08003E and the
latter three bytes are the same with the NE ID.
NSEL: The NSEL value is fixed to 0x1D.
The AREA ID of Huawei optical equipment is 47000400060001.
The ISO8348/AD2 defines a complicated format of the NSAP address, as shown in Figure
2-10.
Figure 2-10 Format of a complicated NSAP address
IDP
DSP
Higher-Order DSP
ORG
RES
RD
AREA
Area Address
1
2-12
SYS ID
9
10
11
12
13
14
15
16
17
NSEL
18
19
20
Issue 02 (2010-09-24)
2 DCN Management
This manual does not cover the naming details and functions of each character in the NSAP
address format. For the OSI protocol, only the simple NSAP address format needs to be noticed.
Huawei equipment applies the simple NSAP address format, which does not affect the
interconnection between Huawei equipment and third-party equipment. The configuration of
the NSAP address requires that the AREA ID in the same domain should be the same.
l
AFI: 47
IDI: 0005
DFI: 80
ORG: 000000
RES: 0000
RD: 0001
AREA: 0001
NSEL: 1D
When a networking involves Huawei equipment and third-party equipment within the same
domain, set the AREA ID to 4700058000000000000001 0001.
TP4
The TP4 protocol locates at the transport layer of the OSI protocol stake. The TP4 protocol is
applied to create a reliable communication connection. The TP4 protocol can handle the
problems as data packet loss, repetition and falsification, which are caused by network faults.
2-13
2 DCN Management
Third-party NM
ES
OSI LAN
OSI DCN
Level 2 Routing
Area
GNE
Legacy Network
GNE
New Network
Third-party NE
Huawei NE
2-14
Issue 02 (2010-09-24)
2 DCN Management
Huawei NM
ES
OSI LAN
OSI DCN
Level 2 Routing
Area
GNE
Legacy Network
GNE
New Network
Third-party NE
Huawei NE
Issue 02 (2010-09-24)
2-15
2 DCN Management
Configuring ECC
Communication
Common Maintenance
Operations
Modifying the NE ID
Modifying the NE ID
Modifying the NE ID
Modifying GNE
Parameters
Configuring an
Extended ECC
Communication
Setting NE
Communication
Parameters
Configuring the IP
Static Route for an
NE
Configuring Standby
GNEs for NEs
Customizing
Communication
Channels Between
NEs
Configuring the
Communication
Protocol Stack and
LAPD Role for an
Optical Port
Changing a GNE to a
Normal NE
Customizing
Communication
Channels Between
NEs
Configuring
Communication for
Third-Party
Equipment
Interconnection
Configuring
Overhead Services
Viewing the
Communication
Status of DCC
Channel
Querying the OSPF
Protocol Status
Configuring OSI
Tunnel
Customizing
Communication
Channels Between
NEs
Configuring Proxy
ARP
Changing a Normal
NE to a GNE
Checking GNE
Switching Status
Testing the
Communication
Between the NMS
and the GNE
Issue 02 (2010-09-24)
2 DCN Management
Prerequisite
l
Precautions
CAUTION
Modifying the NE ID may interrupt NE communication and reset the NE.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > NE Attribute from the Function
Tree.
Step 2 Click Modify NE ID, and the Modify NE ID dialog box is displayed.
Step 3 Enter the New ID and the New Extended ID. Click OK.
Issue 02 (2010-09-24)
2-17
2 DCN Management
Prerequisite
l
Context
CAUTION
This operation may restore the settings of communication, and may interrupt services.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > ECC Management from the
Function Tree.
Step 2 Select the ECC Extended Mode.
2-18
Issue 02 (2010-09-24)
2 DCN Management
NOTE
l Auto mode: Establish an extended ECC connection automatically. Though this mode is convenient,
extra connections will be established and the resource availability is low. It is recommended when there
are less than four NEs. No extended ECC can be established automatically unless both the NEs between
which an extended ECC is to be established are set to the automatic mode.
l Specified mode: Specifies that an extended ECC is to be established between the server and the client.
The connection is highly reliable and the bandwidth availability is high. This mode is usually used to
establish an extended ECC connection.
l For an NE, the two modes cannot be used at the same time to extend ECC.
Step 3 Click Apply and the Warning dialog box is displayed. Click OK.
----End
Postrequisite
After you complete the settings for one NE, you need to configure the settings for the opposite
NE to enable the extended ECC communication. Note the following points:
l
If you set ECC Extended Mode to Auto mode for an NE, configure the same settings for
the opposite NE.
If you set ECC Extended Mode to Specified mode for an NE, configure the same settings
for the opposite NE. In addition, the roles of the two NEs must be different. That is, if an
NE serves as the server, the opposite NE must be the client.
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Issue 02 (2010-09-24)
2-19
2 DCN Management
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > NE ECC Link
Management from the Function Tree.
Step 2 Click Refresh and the ECC route for an NE is displayed in the NE ECC Link Management
Table.
----End
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > NE ECC Link
Management from the Function Tree.
Step 2 Click Add Manual Route and the Add Manual Route dialog box is displayed. Set Destination
NE, Transfer NE, Distance and Level.
Step 3 Click OK. and then click Close in the Operation Result dialog box.
----End
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Context
The NE uses D1-D3 as the DCC by default to communicate through the DCC.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCC Management from the
Function Tree.
Step 2 Click the DCC Rate Configuration tab, click New. Set Port, Channel Type and Protocol
Type in the dialog box that is displayed.
Step 3 Click OK and then click Close in the Operation Result dialog box.
----End
2-20
Issue 02 (2010-09-24)
2 DCN Management
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Context
In the case of multi-vendor networking, the DCC bytes of the equipment from other vendors are
transmitted transparently. You can allocate the DCC bytes of Huawei's equipment through the
idle DCC bytes of the third-party's equipment so that the bytes are transmitted transparently.
This may occur in one of the following three ways:
l
Huawei's equipment is in the network center, while a third party's equipment is at the edge
of the network. The Huawei equipment and third-party equipment are managed by their
respective network management systems by using the D1 to D3 bytes. In this case, Huawei's
equipment transparently transmits the third party's DCC bytes through three consecutive
bytes between D4 and D12.
Huawei's equipment is at the edge of the network, while a third party's equipment is in the
network center. The Huawei equipment and third-party equipment are managed by their
respective network management systems by using the D1 to D3 bytes. In this case, Huawei's
equipment adjusts its own D1-D3 bytes to three consecutive bytes between D4 and D12.
Hence, Huawei's equipment transparently transmits the network management information
through the third-party's equipment.
Huawei's equipment also transparently transmits the other overhead bytes, for example,
E2, F1, or X1-X4, through the idle D bytes.
For the DCC transparent transmission, perform the corresponding configuration at each NE
along the data transmitting trail.
Procedure
Step 1 In the NE Explorer, click an NE and choose Communication > DCC Management from the
Function Tree. Click the DCC Transparent Transmission Management tab.
Step 2 Click Create and the Create DCC Transparent Transmission Byte dialog box is displayed.
Select the source and the sink timeslot, port and overhead bytes.
Step 3 Click OK. and then click Close in the Operation Result dialog box.
----End
2-21
2 DCN Management
Prerequisite
l
Context
CAUTION
Modifying the NE ID may interrupt NE communication.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > NE Attribute from the Function
Tree.
Step 2 Click Modify NE ID, and the Modify NE ID dialog box is displayed.
2-22
Issue 02 (2010-09-24)
2 DCN Management
Step 3 Enter the New ID and the New Extended ID. Click OK.
Step 4 Click OK in the Warning dialog box.
----End
Prerequisite
l
Context
CAUTION
The operation of modifying the NE communication parameters interrupts the communication
and affects the services.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > Communication
Parameters from the Function Tree.
Step 2 Set the NE communication parameters, including IP, Subnet Mask, Gateway IP, Extended
ID, NSAP Address.
Step 3 Click Apply and then click OK in the Warning dialog box that appears twice. in the Warning
dialog box that appears twice. Click Close in the Operation Result dialog box.
----End
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > IP Protocol Stack
Management from the Function Tree. Click the IP Route Management tab.
Step 2 Click New and the Create an IP Route dialog box is displayed. Set the Destination Address,
Subnet Mask and Gateway.
Issue 02 (2010-09-24)
2-23
2 DCN Management
Step 3 Click OK. and then click Close in the Operation Result dialog box.
----End
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Context
The NE uses D1-D3 as the DCC by default to communicate through the DCC.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCC Management from the
Function Tree.
Step 2 Click the DCC Rate Configuration tab, click New. Set Port, Channel Type and Protocol
Type in the dialog box that is displayed.
Step 3 Click OK and then click Close in the Operation Result dialog box.
----End
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCC Management from the
Function Tree. Click the DCC Rate Configuration tab.
Step 2 Click Query, and view the communication status of DCC channel.
----End
2-24
Issue 02 (2010-09-24)
2 DCN Management
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Context
OSPF is a link-state, hierarchical IGP routing algorithm . OSPF features include least-cost
routing, multipath routing, and load balancing. OSPF was derived from an early version of the
IS-IS protocol.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > IP Protocol Stack
Management from the Function Tree. Click the OSPF Parameter Settings tab.
Step 2 Click Query to check if the OSPF protocol status is normal.
----End
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > IP Protocol Stack
Management from the Function Tree. Click the Proxy ARP tab.
Step 2 Optional: Click Query.
Step 3 Set Value to Disabled or Enabled from the drop-down list.
Step 4 Click Apply.
----End
Postrequisite
After you enable proxy ARP, you need to create a static route for each NE.
2-25
2 DCN Management
transmits management information at the network layer. Hence, the interconnection with the
equipment that supports OSI protocol from the third party is realized.
2.5.1 Modifying the NE ID
In the commissioning or expansion process, when you need to adjust the original planning and
change the NE ID, you can use the U2000 to achieve it.
2.5.2 Setting the NSAP Address for an NE
If the U2000 sets up a TP4 connection with an NE, after you modify the NSAP address range
that was previously set according to network planning, the communication between the
U2000 and the GNE is interrupted, so you need to re-create the communication. You can use
the U2000 to create a TCP connection with an NE, set the NSAP address range for the NE, and
then modify the connection mode between the U2000 and the NE to TP4.
2.5.3 Configuring the Node Type for an NE
Based on the network planning, you can set the node type to ES, L1 IS or L2 IS for an NE. For
easy expansion of the network, avoid the ES type.
2.5.4 Configuring the Communication Protocol Stack and LAPD Role for an Optical Port
The default protocol stack enabled for optical ports on an NE depends on products. If the current
protocol stack enabled for an optical port differs from the planned one, you can configure it on
the U2000. If an optical port uses the OSI protocol stack, the link access procedure on the D
channel (LAPD) role of all optical ports is User by default. You can set the LAPD role for each
optical port based on network planning. The local LAPD role depends on the remote LAPD role.
Ensure that the two LAPD roles are different.
2.5.5 Configuring OSI Tunnel
When the OSI-protocol-based third-party equipment needs to transfer information through an
IP network that consists of Huawei equipment, you can create a virtual OSI tunnel to
transparently transmit the information.
2.5.6 Customizing Communication Channels Between NEs
NEs communicate with each other through data communications channel (DCC). To meet the
requirements of the network management in a complex network, you can configure D1-D3, D4D12, D1-D12 as DCC and multirate DCC. When configuring the DCC, you need to set the DCC
rate and allocate DCC resources according to DCC channel types.
2.5.7 Querying the Route Information of a Node
After you finish configuring and connecting the fibers, you can check whether the route
information of each node is correct. If the route information is correct, it means that the nodes
can normally communicate with each other.
2.5.8 Creating an OSI GNE
After you configure the NSAP address of an NE, you can create an OSI GNE in the TP4
connection mode.
Prerequisite
2-26
Issue 02 (2010-09-24)
2 DCN Management
Context
CAUTION
Modifying the NE ID may interrupt NE communication.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > NE Attribute from the Function
Tree.
Step 2 Click Modify NE ID, and the Modify NE ID dialog box is displayed.
Step 3 Enter the New ID and the New Extended ID. Click OK.
Step 4 Click OK in the Warning dialog box.
----End
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > Communication
Parameters from the Function Tree.
Step 2 Set the NSAP Address.
Step 3 Click Apply.
Step 4 Choose Administration > DCN Management from the main menu. Click the GNE tab.
Step 5 Right-click a GNE and choose Modify GNE from the shortcut menu.
Step 6 In the Modify GNE dialog box, select OSI Gateway from the Gateway Type drop-down list,
and enter the NSAP Address.
Issue 02 (2010-09-24)
2-27
2 DCN Management
Step 7 Click OK and then click Close in the Operation Result dialog box.
----End
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Context
CAUTION
Setting the Configuration Role of an NE may cause service interruption.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > OSI Management from the
Function Tree. Click the Network Layer Parameters tab.
Step 2 Double-click the Configuration Role and select a node type from the drop-down list.
Step 3 Click Apply and click OK in the Confirm dialog box. dialog box. Then, click Close in the
Operation Result dialog box.
----End
2-28
Issue 02 (2010-09-24)
2 DCN Management
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCC Management from the
Function Tree. Click the DCC Rate Configuration tab.
Step 2 Optional: Click Query.
Step 3 Select the optical port you want to set and click Delete.
Step 4 Click New and set parameters in the Create dialog box.
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Context
As OSI tunnel is an end-to-end function, you must configure this function at both ends of a
tunnel.
Issue 02 (2010-09-24)
2-29
2 DCN Management
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > OSI Management from the
Function Tree. Click the OSI Tunnel tab.
Step 2 Click New. In the Create OSI Tunnel window, set Remote IP Address and LAPD Actor.
NOTE
LAPD Actor refers to the LAPD role at an end. When setting this parameter, you must configure different
roles for the two ends of a tunnel.
Step 3 Click OK and then click Close in the Operation Result dialog box.
Step 4 Set the parameters in the LAPD Parameter pane.
NOTE
Step 5 Click Apply and then click Close in the Operation Result dialog box.
----End
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Context
The NE uses D1-D3 as the DCC by default to communicate through the DCC.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCC Management from the
Function Tree.
Step 2 Click the DCC Rate Configuration tab, click New. Set Port, Channel Type and Protocol
Type in the dialog box that is displayed.
Step 3 Click OK and then click Close in the Operation Result dialog box.
----End
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
2-30
Issue 02 (2010-09-24)
2 DCN Management
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > OSI Management from the
Function Tree. Click the Routing Table tab.
Step 2 Optional: Click Refresh to query the route information on the NE.
Step 3 View the information in the Link Adjacency Table and ensure that the information is correct.
Step 4 Click the L1 Routing and the L2 Routing tabs to check if the respective route information is
correct.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 Choose File > Create > NE from the main menu.
Step 2 In the Add Object dialog box, select the NE type from the Object Type tree. Enter the ID,
Extended ID, Name and Remarks.
Step 3 Select Gateway from the Gateway Type drop-down list.
Step 4 Select OSI from the Protocol drop-down list.
Step 5 Enter the NSAP Address of the GNE.
NOTE
The NSAP address consists of hexadecimal digits of up to 20 bytes, and its format is: domain address
+08003e+NE ID+NSEL. The domain address is composed of 13 bytes and is entered by the user. The
NSEL is the port number of the network-layer protocol, with a fixed value of 1d (one byte).
The default NE user of the U2000 must be root, and the default password is password.
Step 7 Click OK. Click on the Main Topology and the NE icon is displayed in the position where you
click.
NOTE
If the NE is not created properly or the communication between the NE and the U2000 is abnormal, the
NE is displayed in gray.
----End
2-31
2 DCN Management
network. The DCC information enters the service channel through the external clock interface
or the F1 data interface, and then reaches the third-party network over the related service channel.
In this way, the DCC information is transparently transmitted.
2.6.1 Configuring Communication for Third-Party Equipment Interconnection
In the case of multi-vendor networking, you need to allocate the DCC bytes of Huawei's
equipment to ensure that the bytes are transmitted transparently.
2.6.2 Configuring DCC Transparent Transmission Through External Clock Interfaces
If a third-party network exists between networks composed of Huawei equipment, the external
clock interfaces can be used to transparently transmit the DCC information. In this way, the
U2000 can uniformly manage the networks composed of Huawei equipment.
2.6.3 Configuring DCC Transparent Transmission Through F1 Data Interfaces
You can configure the F1 data interface on the SCC board, to transparently transmit the data
communication channel (DCC) information between back-to-back NEs.
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Context
In the case of multi-vendor networking, the DCC bytes of the equipment from other vendors are
transmitted transparently. You can allocate the DCC bytes of Huawei's equipment through the
idle DCC bytes of the third-party's equipment so that the bytes are transmitted transparently.
This may occur in one of the following three ways:
l
Huawei's equipment is in the network center, while a third party's equipment is at the edge
of the network. The Huawei equipment and third-party equipment are managed by their
respective network management systems by using the D1 to D3 bytes. In this case, Huawei's
equipment transparently transmits the third party's DCC bytes through three consecutive
bytes between D4 and D12.
Huawei's equipment is at the edge of the network, while a third party's equipment is in the
network center. The Huawei equipment and third-party equipment are managed by their
respective network management systems by using the D1 to D3 bytes. In this case, Huawei's
equipment adjusts its own D1-D3 bytes to three consecutive bytes between D4 and D12.
Hence, Huawei's equipment transparently transmits the network management information
through the third-party's equipment.
Huawei's equipment also transparently transmits the other overhead bytes, for example,
E2, F1, or X1-X4, through the idle D bytes.
For the DCC transparent transmission, perform the corresponding configuration at each NE
along the data transmitting trail.
2-32
Issue 02 (2010-09-24)
2 DCN Management
Procedure
Step 1 In the NE Explorer, click an NE and choose Communication > DCC Management from the
Function Tree. Click the DCC Transparent Transmission Management tab.
Step 2 Click Create and the Create DCC Transparent Transmission Byte dialog box is displayed.
Select the source and the sink timeslot, port and overhead bytes.
Step 3 Click OK. and then click Close in the Operation Result dialog box.
----End
Prerequisite
l
The 2M external clock interface signals must be accessed to the E1 tributary board through
a cable.
Context
As shown in Figure 2-14, when a third-party network exists, external clock interfaces can be
used to transmit DCC information. In this way, the U2000 can configure and manage ring 2.
Figure 2-14 External clock interfaces used to transparently transmit DCC information (example)
NMS
NE1
NE2
Third Party
Transport
network
Ring 1
DCC
Ring 2
DCC
NOTE
If the third-party network does not exist, you can use a cable to connect the external clock interfaces of NE1
and NE2 to transparently transmit the DCC information.
Figure 2-15 shows how to connect NE1 and NE2. Through the third-party network, NE1 and
NE2 can exchange E1 (DCC) signals.
Issue 02 (2010-09-24)
2-33
2 DCN Management
Figure 2-15 External clock interfaces used to transparently transmit DCC information (example)
SDH processing
board
NE1
SDH processing
board
NE2
Third-party
network
External
clock
interface
PDH processing
board
External
clock
interface
E1(DCC)
PDH processing
board
E1(DCC)
l The external clock interfaces of NE1 and NE2 are connected to the first interface of the tributary board.
l Configure a bidirectional cross-connection between the first VC-12 timeslot of the tributary board and the
first VC-12 timeslot in the first VC-4 of the line board.
l The RTN equipment can be connected to the third-party network by using the line board or intermediate
frequency (IF) board.
Procedure
Step 1 Configure the DCC transparent transmission through the external clock interface of NE 1.
1.
In the NE Explorer, click an NE and choose Communication > DCC Management from
the Function Tree.
2.
Click DCC Rate Configuration. Click Create. In the Create dialog box displayed, select
an external clock interface and set the parameters such as the channel type and protocol
type. Click OK. Then, in the Operation Result dialog box, click Close.
3.
Select the external clock interface and set its enabling status to Enabled.
4.
Click Apply. The Operation Result dialog box is displayed indicating that the operation
was successful. Click Close.
Step 2 Configure a bidirectional cross-connection between the tributary board and the line board.
Step 3 Disable the DCC communication of the line board interconnected with the third-party network.
1.
Select the port of the corresponding line board, click Enable Status, and select Disable.
The Warning dialog box is displayed.
2.
Click OK.
3.
4.
Click OK. The Operation Result dialog box is displayed indicating that the operation was
successful.
2-34
Issue 02 (2010-09-24)
2 DCN Management
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > Orderwire from the Function
Tree.
Step 2 Click the F1 tab.
Step 3 In the Available Data Channel area, select two data channels and click
Step 4 Click Apply. In the Operation Result dialog box displayed, click Close.
----End
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Precautions
CAUTION
This operation is risky, because it may interrupt the communication.
Procedure
Step 1 Choose Administration > DCN Management from the main menu. Click the GNE tab.
Step 2 Select the GNE to be modified, right-click and choose Modify GNE from the shortcut menu.
Step 3 In the Modify GNE dialog box displayed, set Gateway Type.
l
Issue 02 (2010-09-24)
2-35
2 DCN Management
NOTE
Step 4 Click OK. In the Operation Result dialog box that is displayed, click Close.
----End
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
2-36
Issue 02 (2010-09-24)
2 DCN Management
Precautions
CAUTION
This operation may interrupt the NE communication.
Procedure
Step 1 Choose Administration > DCN Management from the main menu.
Step 2 Click the NE tab.
Step 3 Select an NE. Double-click the Primary GNE1 field and select a GNE from the drop-down list.
Step 4 Click Apply. Click Close in the Operation Result dialog box.
Step 5 Click Refresh. Test the modification with reference to Checking the Network Communication
Status.
----End
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Procedure
Step 1 Choose Administration > DCN Management from the main menu. Click the NE tab.
Step 2 Select an NE. Double-click GNE2 and select a GNE from the drop-down list.
Issue 02 (2010-09-24)
2-37
2 DCN Management
l To configure multiple standby GNEs, select a GNE from the GNE3 and GNE4 drop-down
lists.
l When the active GNE and standby GNEs fail one by one, the switching sequence is Primary
GNE1, GNE2, GNE23, and GNE4.
l You can select multiple lines at a time to set standby NEs in batches.
Step 3 Click Apply. Click Close in the Operation Result dialog box.
----End
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Context
CAUTION
This operation may interrupt the service.
Procedure
Step 1 Choose Administration > DCN Management from the main menu. Click the GNE tab.
Step 2 Right-click the GNE that you want to change and choose Delete GNE from the shortcut menu.
Click OK in the Confirm and Reconfirm dialog box. Click Close in the Operation Result
dialog box.
----End
Postrequisite
After changing the GNE to a normal NE, modify the attributes of the NE that uses the GNE and
select another GNE.
2-38
Issue 02 (2010-09-24)
2 DCN Management
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Procedure
Step 1 Choose Administration > DCN Management from the main menu. Click the NE tab.
Step 2 Right-click a normal NE and choose Change to GNE from the shortcut menu.
Step 3 Click OK. Click Close in the Operation Result dialog box.
NOTE
----End
Prerequisite
The active and standby GNEs must be created for an NE.
You must be an NM user with "NE maintainer" authority or higher.
Procedure
Step 1 Choose Administration > DCN Management from the main menu.
Step 2 Click the NE tab.
Step 3 Click Refresh to query the GNE switching status.
----End
2-39
2 DCN Management
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 Choose Administration > DCN Management from the main menu. Click the GNE tab.
Step 2 Right-click the GNE to be tested and choose Test GNE from the shortcut menu.
Step 3 Click Close in the Operation Result dialog box.
----End
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Context
l
When an NE uses IP over DCC, to check the NE communication status by using the ping
function, you can right-click the NE on the Main Topology and choose Ping from the
shortcut menu.
You can use the ping function after installing the OSI software on the NE that uses OSI
over DCC and the computer where the U2000 resides.
Check the communication status between the U2000 and a non-gateway NE.
Procedure
1.
2.
Click the NE tab. Click Refresh to view the communication status of all NEs.
3.
Select an NE. Right-click in the Communication Status column and choose Test
NE from the shortcut menu.
4.
The Operation Result dialog box is displayed indicating the test result of the nongateway NE.
Check the communication status between the U2000 and the GNE.
1.
2.
Click the GNE tab. Click Refresh to view the communication status of the GNE.
3.
4.
The Operation Result dialog box is displayed indicating the test result of the GNE.
----End
2.14.1 Overview of the Inband DCN
2-40
Issue 02 (2010-09-24)
2 DCN Management
Inband DCN refers to the networking mode that uses service paths provided by the managed
equipment to realize the management of network equipment. In this mode, the network
management information is transmitted over service paths of the equipment.
2.14.2 Basic Concepts
The DCN contains two networking modes, which are inband networking and outband
networking.
2.14.3 Application of the Inband DCN
When no special DCN is available for transmitting network management information, you can
perform the networking in the inband DCN mode.
2.14.4 Configuring an Inband DCN
This section describes how to configure an inband DCN.
Realization Principle
As shown in Figure 2-16, in the inband DCN mode, the DCN information and service
information share the same path for transmission.
Figure 2-16 Inband DCN networking mode
NMS
Ethernet Link
Ethernet Link
Service
DCN information
Issue 02 (2010-09-24)
2-41
2 DCN Management
Managed network
Firewall
NOTE
l The devices managed by the U2000 are connected to the IP core network. The NMS center only needs
to be connected to the nearby IP devices in the IP core network. You can manage all the devices in the
network by configuring the route.
l The mode of connection between the NMS center and the IP core network is based on the location of
the IP devices near the NMS center. If the U2000 and the nearby IP device are in the same equipment
room, you can adopt the LAN networking mode. In the case of the long distance transmission, the
networking is realized through private line services.
Issue 02 (2010-09-24)
2 DCN Management
DCN
Firewall
Managed network
NOTE
The U2000 uses the dedicated communication channels to transmit the management information to the
managed networks.
Context
The configuration of an inband DCN includes the following contents:
2.14.4.1 Setting NE Communication Parameters
When configuring the IP Over DCC communication, you need to set the parameters including
IP, Subnet Mask, Gateway IP, Extended ID, and Connection Mode for the NE.
2.14.4.2 Setting the VLAN ID and Bandwidth Used by an Inband DCN
Issue 02 (2010-09-24)
2-43
2 DCN Management
The RTN equipment communicates with the U2000 in inband DCN mode. The network
management information is transmitted with the service information, and the equipment marks
the management information with a default VLAN ID. You can adjust the bandwidth of an
inband DCN.
2.14.4.3 Setting the U2000 Access Parameters
In the case of the traditional DCN network, the equipment accesses to the U2000 through the
SCC board. The RTN equipment can also access to the U2000 through the network interface of
the Ethernet board. When the RTN equipment accesses to the U2000 by using the network
interface of the Ethernet board, set the access parameters of the Ethernet board for the equipment
to communicate with the U2000.
2.14.4.4 Enabling the Port DCN
The NM information can be transported in the inband DCN only when the DCN access function
is enabled for the ports at two ends of the link.
2.14.4.5 Enabling the Tunnel DCN
The NM information can be transported in the IP/GRE Tunnel only when the DCN access
function is enabled for the IP/GRE tunnel.
Prerequisite
l
Context
CAUTION
The operation of modifying the NE communication parameters interrupts the communication
and affects the services.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > Communication
Parameters from the Function Tree.
Step 2 Set the NE communication parameters, including IP, Subnet Mask, Gateway IP, Extended
ID, NSAP Address.
Step 3 Click Apply and then click OK in the Warning dialog box that appears twice. in the Warning
dialog box that appears twice. Click Close in the Operation Result dialog box.
----End
2-44
Issue 02 (2010-09-24)
2 DCN Management
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
l
If the default VLAN ID of the DCN conflicts with the VLAN ID used by the service,
manually modify the VLAN ID of the DCN to ensure that the networkwide DCN uses the
same VLAN ID.
If the DCN packets do not use all the available bandwidth, the idle bandwidth can be shared
with the service packets.
It is recommended to perform the modification on non-gateway NEs and then the gateway
NE, to prevent the non-gateway NEs from being unreachable to the U2000.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCN Management from the
Function Tree.
Step 2 Click the Bandwidth Management tab, and enter parameters.
NOTE
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Issue 02 (2010-09-24)
2-45
2 DCN Management
Context
NOTE
l You need to set the parameters only when the U2000 accesses the equipment by using an Ethernet
service board.
l By default, the Enabled Status is Disabled.
CAUTION
In the case of the OptiX RTN equipment, when the DCN port is interconnected to the U2000,
the IP address of the U2000 and the IP address of the NNI should not be set to the same subnet.
This operation may affect the communication between the U2000 and NEs.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCN Management from the
Function Tree.
Step 2 Click the Access Control tab, and enter parameters.
Step 3 Click Apply.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCN Management from the
Function Tree.
Step 2 Click the Port Settings tab.
Step 3 Select different interface types, and set the corresponding attributes.
NOTE
Issue 02 (2010-09-24)
2 DCN Management
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCN Management from the
Function Tree.
Step 2 Click the Tunnel Settings tab.
Step 3 Select different tunnel types, and set the corresponding attributes.
Step 4 Click Apply.
----End
Issue 02 (2010-09-24)
2-47
3 Configuring Clocks
Configuring Clocks
Issue 02 (2010-09-24)
3-1
3 Configuring Clocks
If the traceable clock source of an NE is line clock, you can customize switching conditions for
the clock source, so that the NE switches to other clocks when the clock source fails. In this
manner, services are less affected.
3.9 Configuring the Clock Source Reversion
When there are multiple clock sources for an NE, set the clock sources to automatic reversion
mode, so that the deteriorated clock source automatically becomes the traceable timing reference
after it recovers.
3.10 Modifying the Parameters of the External Clock Output
The NE outputs the 2 Mbit/s external clock regardless of the clock quality.
3.11 Setting the Clock Source Quality
In a complex clock network, there may be some unknown clock sources. You can uniformly
define these clock sources as unavailable clocks so that NEs do not trace wrong clock sources.
The NE obtains their quality information automatically for clock sources that are allocated to
an NE. You should define the quality level of clock sources only during test and maintenance.
3.12 Configuring the SSM Output
If the standard SSM or extended SSM protocol is enabled, the clock signals carry SSM messages
automatically. You can prevent clock sources from sending SSM messages to other clock
subnets. This helps you to ensure that the equipment of different clock subnets do not affect each
other at the edge of clock networks.
3.13 Configuring the Ethernet Clock Source
Configure the Ethernet clock source of the IDU 605 1F/2F according to the planned clock
synchronization strategy to ensure that all the NEs in the network trace the same clock.
3.5 Viewing the Clock Tracing Status
Correct clock tracing relationships are critical to ensure the clock synchronization within the
entire network. Using the U2000, you can monitor the clock trace status of each NE.
3.15 Checking the Clock Switching Status
Clock failure may interrupt services. To detect failure of the clock source in time, you need to
check the clock switching status.
3.16 Switching a Clock Source
When the traceable clock source in a network deteriorates, NEs may not be able to execute a
switch on the clock source. You need to manually switch the clock source to prevent clock
deterioration from affecting the normal running of NEs.
3-2
Issue 02 (2010-09-24)
3 Configuring Clocks
Switch a clock
source
Set switching
conditions for
clock sources
Switch a clock
source
Set switching
conditions for
clock sources
Switch a clock
source
NOTE
l The horizontal direction of the figure shows the three stages when you use the U2000 to configure
clocks.
l The vertical direction of the figure shows the relations between operation tasks at each stage.
Issue 02 (2010-09-24)
3-3
3 Configuring Clocks
If the main (first) node accesses a clock source (external clock or line clock), configure this
clock source for this node.
Configure the clock source of the higher-level radio link for other nodes.
When the higher-level radio link adopts 1+1 protection, configure two clock sources for
the corresponding node. Note that the clock source priority of the main radio link should
be higher than the clock source priority of the standby radio link.
When multiple higher-level radio links exist, (for example, when the radio link is
configured with XPIC or N+1 protection), the node configures a microwave clock source
for each radio link and allocates different clock priority levels based on the situation of
each radio link.
Do not configure the synchronization status message (SSM) or extended SSM protection.
The PXC board in slot 1 on the main node NE1 accesses the external clock source. Hence,
the clock source priority levels are external clock source 1 and internal clock source in the
descending order.
The IF1A boards in slots 5 and 7 on NE2 form an IF 1+1 protection group (the board in
slot 5 is the main board) and provide the radio link from NE1 to NE2. Hence, the clock
source level priority levels are 5-IF1A-1, 7-IF1A-1, and internal clock source in the
descending order.
The IF1A board in slot 5 on NE2 provides the radio link from NE3 to NE2. Hence, the
clock source level priority levels are 5-IF1A-1 and internal clock source in the descending
order.
The IF1A board in slot 5 on NE4 provides the radio link from NE4 to NE3. Hence, the
clock source level priority levels are 5-IF1A-1 and internal clock source in the descending
order.
NE2
5-IF1A-1/
7-IF1A-1/
Internal
External 1/
Internal
NE3
5-IF1A-1/
Internal
NE4
5-IF1A-1/
Internal
Master clock
3-4
Issue 02 (2010-09-24)
3 Configuring Clocks
The SL1 board in slot 4 on NE1 accesses the line clock source. Hence, the clock source
level priority levels are 4-SL1-1 and internal clock source in the descending order.
The IFX boards in slots 5 and 7 on NE2 form an XPIC workgroup (the IFX board in slot
5 works on polarization V and the IFX board in slot 7 is works on polarization H) and
provide the radio link from NE1 to NE2. Hence, the clock source level priority levels are
5-IF1A-1, 7-IF1A-1, and internal clock source in the descending order.
The IF1A board in slot 5 on NE3 provides the radio link from NE3 to NE2. Hence, the
clock source level priority levels are 5-IF1A-1 and internal clock source in the descending
order.
The IF1A board in slot 5 on NE4 provides the radio link from NE4 to NE3. Hence, the
clock source level priority levels are 5-IF1A-1 and internal clock source in the descending
order.
NE1
NE2
5-IF1A-1/
Internal
NE4
4-SL1-1/
Internal
5-IFX-1/
7-IFX-1/
Internal
Master clock
5-IF1A-1/
Internal
Issue 02 (2010-09-24)
When the entire ring network line is an SDH line, set the SSM or extended SSM according
to the clock synchronization schemes of an optical transmission network.
3-5
3 Configuring Clocks
When a PDH section exists on the line of the ring network, divide the ring network into
two chains and set the synchronization according to the clock synchronization schemes of
a chain network.
Figure 3-6 shows the clock synchronization scheme of a ring network of which the entire ring
network line is an SDH line.
l
The SSM or extended SSM protection is enabled on all the nodes in the ring network.
The PXC board in slot 1 on the main node NE1 accesses the external clock source. Hence,
the clock source priority levels are external clock source 1 and internal clock source in the
descending order.
The clock source priority levels of other nodes are the west clock source, east clock source,
and internal clock source in the descending order.
Figure 3-6 Clock synchronization scheme for a ring network (the entire ring network line is an
SDH line)
NE2
NE6
NE1
West/
East/
Internal
West/
East/
Internal
External 1/
Internal
West/
East/
Internal
West/
East/
Internal
NE3
Master clock
NE4
West/
East/
Internal
NE5
Figure 3-7 shows the clock synchronization scheme of a ring network of which not the entire
ring network line is an SDH line.
3-6
This ring network is formed by PDH microwave. Hence, divide the ring network at the
main node NE1 into two chains: from NE1 to NE2 and from NE3 to NE4.
The SL1 board in slot 4 on NE1 accesses the line clock source. Hence, the clock source
level priority levels are 4-SL1-1 and internal clock source in the descending order.
NE2 traces the clock of the main node. Hence, the clock source level priority levels are the
west clock source and internal clock source in the descending order.
NE4 traces the clock of the main node. Hence, the clock source level priority levels are the
east clock source and internal clock source in the descending order.
NE3 traces the clock of NE4. Hence, the clock source level priority levels are the east clock
source and internal clock source in the descending order.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
3 Configuring Clocks
Figure 3-7 Clock synchronization scheme for a ring network (not the entire ring network line
is an SDH line)
NE1
NE2
NE4
4-SL1-1/
Internal
NE3
West/
Internal
Master clock
East/
Internal
East/
Internal
The higher-level NE accesses the clock source (external clock source or line clock source).
The lower-level NEs trace the tributary clock sources (port 1 and port 5 of the PO1/PH1/
PD1 board can be used as the tributary clock sources).
Figure 3-8shows the clock synchronization scheme for networking with convergence at
tributary ports.
l
The PXC board in slot 1 on the main node NE1 accesses the external clock source. Hence,
the clock source priority levels are external clock source 1 and internal clock source in the
descending order.
The IF1A board in slot 5 on NE2 provides the radio link from NE3 to NE2. Hence, the
clock source level priority levels are 5-IF1A-1 and internal clock source in the descending
order.
Issue 02 (2010-09-24)
3-7
3 Configuring Clocks
NE3 converges services TO NE2 through ports 1-4 of the PO1 board in slot 4. Hence, the
clock source level priority levels are 4-PO1-1 and internal clock source in the descending
order.
Multiple microwave hops exist in the downstream of NE4. In this case, the downstream
nodes will report point adjustments if NE4 adopts the tributary clock source. Hence, NE4
adopts the external clock output from NE2 as the external clock input to the PXC board in
slot 1.
Figure 3-8 Clock synchronization scheme for networking with convergence at tributary ports
NE3
NE1
NE2
4-PO1-1/
Internal
NE4
External 1/
Internal
5-IF1A-1/
Internal
External/
Internal
Master clock
E1
External clock
The number of the NEs on the long clock chain must not exceed 20. It is recommended
that the long clock chain contains less than 10 NEs. If the long clock chain contains too
many NEs, new clock sources need be added to the chain for use compensation.
Use SDH interface boards to converge services at the convergence node. Thus, the clock
signals can be passed over SDH signals not over PDH signals, which ensures the high
quality of the clock.
Issue 02 (2010-09-24)
3 Configuring Clocks
By keeping the clock synchronization of each NE in the network, you can avoid pointer
justification events, jitters, and bit errors thus caused when the clocks are not synchronous. All
NEs trace the same PRC through a specific clock synchronization path, thus realizing the
networkwide synchronization.
3.3.2 SSM Protocol and Clock ID
The synchronization status message (SSM) protocol and clock ID are used for clock protection.
3.3.3 Clock Subnet
The nodes that have clock tracing relations between each other comprise a clock subnet.
3.3.4 Clock Protection
Clock protection ensures that each node traces the correct clock source even when a fault occurs
in a network.
Tracing mode: It is the normal working mode. In this mode, the local clock is synchronized
with the input reference clock signals.
Holdover mode: When all timing reference signals are lost, the slave clock enters into the
holdover mode. In this mode, the slave clock takes timing reference from the last frequency
information saved before the loss of timing reference signals. This mode can be used to
cope with an interruption of external timing signals lasting many days.
Free-run mode: When all timing reference signals are lost and the slave clock losses the
saved configuration data about the timing reference or the slave clock fails to enter the
holdover mode, the internal oscillator of the slave clock enters the free-run mode from the
holdover mode.
External clock source: 2M timing signals from the external clock interface of an NE
Line clock source: timing signals extracted from optical signals that the line board receives
Tributary clock source: timing signals extracted from optical signals that the tributary board
receives
Internal clock source: The internal timing source is available for each NE. When the
external source is lost, the NE can use the internal timing source.
Clock Synchronization
Generally, an NE can obtain the PRC through several paths. In Figure 3-9, NE4 can trace the
clock from NE3 and the clock from NE5. These two clock sources are from the same PRC.
Issue 02 (2010-09-24)
3-9
3 Configuring Clocks
NE1
NE2
NE6
NE3
NE5
NE4
Clock Signal Flow
S1 Byte
The S1 byte is located in row 9 and column 1 in the multiplex section overhead in an SDH frame
structure. The lower four bits (bit 5-bit 8) of the S1 byte are allocated to transport a
synchronization status of an NE, which is referred to as the synchronization status message byte
(SSMB). Table 3-1 shows the meaning of clock quality that the SSMB stands for. The smaller
the SSMB value, the higher the quality of the clock source that the SSMB represents.
In a clock network, the node that is connected to an external clock extracts a reference timing
source from the BITS equipment, writes an SSMB to bit 5-bit 8 of S1 byte, and transports the
SSMB to downstream nodes. In this way, the SSMB is output. A downstream node extracts the
timing source from a line signal, and obtains the clock quality level from bit 5-bit 8 of S1 byte.
In this way, the downstream node often determines whether the current clock source is effective
and transmits back 0xf to the upstream node through bit 5-bit 8 of S1 byte. 0xf means the returned
3-10
Issue 02 (2010-09-24)
3 Configuring Clocks
clock source is unavailable. This prevents two nodes from tracing the timing source mutually.
Each node obtains the quality of all clock sources from the S1 byte, and choose to trace a clock
source according to the preset priority level.
Table 3-1 SSM allocation
Bit 5-bit 8 of S1 byte
0000
0001
Retained
0010
0011
Retained
0100
SSU-ANote 1
0101
Retained
0110
Retained
0111
Retained
1000
SSU-BNote 1
1001
Retained
1010
Retained
1011
1100
Retained
1101
Retained
1110
Retained
1111
Note 1: The "G.812 Transit Exchange" and "G.812 Local Clock" terms are used in the previous
version of ITU-T Recommendations. In the new version of ITU-T G.812, the clock definition
is changed to synchronization supply unit (SSU). The SSU has A and B types. The SSU-A
corresponds to the "G.812 Transit Exchange" and the SSU-B corresponds to the "G.812 Local
Clock" that are previously used.
SSM Protocol
The standard SSM protocol is mechanism of network synchronization management. It uses bit
5-bit 8 of S1 byte to exchange the quality information of clock sources between nodes. This
ensures that the equipment automatically selects the clock source of the highest quality and
priority levels, to prevent an interlock of clocks. The standard SSM protocol improves the
performance of a synchronous network, and realizes synchronization of different network
Issue 02 (2010-09-24)
3-11
3 Configuring Clocks
structures in an easy manner. The standard SSM protocol applies to the interconnection of
equipment from different vendors.
In the case that the S1 byte is enabled for clock protection, the concept of clock ID is introduced.
That is, clock protection is extended based on the original SSM protocol. In this manner, the
extended SSM protocol is developed.
In the case of the extended SSM protocol, Huawei introduces the concept of clock ID based on
the standard SSM protocol. The extended SSM protocol uses b1 through b4 of S1 byte as the
unique ID of a clock source and transports the clock ID with an SSM. After a node receives the
S1 byte, the node verifies the clock ID (bit 1-bit 4) to determine whether the clock is locally
output. If the clock is locally output, the node regards the clock as unavailable. This prevents a
timing loop. The extended SSM protocol is mainly used to realize the interconnection of
transmission equipment from Huawei.
When an NE works in different clock protection modes, the method of selecting a clock source
during automatic clock switching is changed accordingly, as shown in Table 3-2.
Table 3-2 Methods of selecting clock sources in different modes
Working Mode
Clock ID
A clock ID use bit 1-bit 4 of S1 byte, and the value range is 0x0 to 0xf. Basically, a clock ID is
used to distinguish the clock information between local and other nodes, to prevent a node from
tracing the clock signal that is locally transmitted and comes from the negative direction. Hence,
a timing loop is prevented.
A value of 0 indicates that a clock ID is invalid. Hence, the default value of a clock ID is 0 when
an ID is not set for a clock source. When enabling the extended SSM protocol, an NE does not
select the clock source whose ID is 0 as the current clock source.
3-12
Issue 02 (2010-09-24)
3 Configuring Clocks
A clock ID is a tag set for a reference timing source. The clock sources at the same quality level
that carry different IDs mean different timing signals and are not different in priority levels and
other aspects.
Set the clock ID according to the following principles:
l
Allocate a clock ID to the internal clock source of each node that has an external BITS.
Allocate a clock ID to the internal clock source of each node that enters into another ring
network from one chain or ring network.
Allocate a clock ID to the line clock source of the node that enters into another ring network
from one chain or ring network, when the line clock source exists.
All the NEs that trace the same clock source should be divided to the same clock subnet.
To make sure that the clock tracing chain is not too long, configure at most 20 NEs to
prevent the clock precision from being degraded.
You must divide the NEs that have the SSM clock protection to clock subnets. Otherwise,
SSM is not enabled for the NEs that are not divided to the clock subnets. This results in
incorrect traced clock switching.
If the clock source priority is set, the NE selects the clock source of the highest quality level
as the synchronization source and sends the synchronization status message bit (SSMB) to
downstream NEs.
If multiple clock sources of the same quality level exist, the NE selects the clock source of
the highest priority level as the synchronization source and sends the SSMB to downstream
NEs.
If NE B traces the clock source that is output from NE A, the clock of NE B is an unavailable
source for NE A.
If the extended SSM protocol is enabled, the NE does not select the clock that has the same
ID as the local clock, or the clock whose ID is 0, as the clock source.
Issue 02 (2010-09-24)
3-13
3 Configuring Clocks
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Clock Synchronization
Status from the Function Tree.
NOTE
To view the clock synchronization status of NEs in batches, Choose Configuration > NE Batch
Configuration > Batch Clock Operation from the main menu. Then, click the Clock Synchronization
Status tab. In the Object Tree, select the desired NEs and click
Step 2 Click Query. You can view the information about the clock synchronization status queried from
the NE side.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
When the clock tracing relationships are changed, the U2000 refreshes the tracing status in the
Clock View automatically.
Procedure
Step 1 In the Main Topology window, selectClock View from the Current View drop-down list.
Step 2 Select the NE to be queried or configured from the object tree. In the Clock View, right-click
and choose Search Clock Link from the shortcut menu.
Step 3 In the Operation Result dialog box, click Close.
----End
3-14
Issue 02 (2010-09-24)
3 Configuring Clocks
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The PXC boards and input/output clock source boards must be configured.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Clock
Source Priority from the Function Tree.
Step 2 Click Create.
The Add Clock Source dialog box is displayed.
Step 3 Select the clock sources.
TIP
By pressing the Ctrl key, you can select multiple clock sources at one time.
or
The clock priority levels are arranged in the descending order from the first row to the last row.
The internal clock source is fixed with the lowest priority.
Step 7 Optional: Set External Clock Source Mode and Synchronous Status Byte for the external
clock sources.
Issue 02 (2010-09-24)
3-15
3 Configuring Clocks
Parameters
Parameter
Value Range
Default Value
Description
Clock Source
External Clock
Source Mode
2 Mbit/s, 2 MHz
2 Mbit/s
Synchronization
Status Byte
SA4-SA8
SA4
3-16
Issue 02 (2010-09-24)
3 Configuring Clocks
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The clock source priority table must be configured.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Clock
Subnet Configuration from the Function Tree.
Step 2 Enable the clock protection protocol.
1.
2.
Enable the clock protection protocol and set the protocol parameters.
3.
Click Apply.
2.
Issue 02 (2010-09-24)
3-17
3 Configuring Clocks
3.
Click Apply.
2.
3.
Click Apply.
----End
Parameters
Parameter
Value Range
Default Value
Description
Protection Status
3-18
Issue 02 (2010-09-24)
3 Configuring Clocks
Parameter
Value Range
Default Value
Description
Affiliated Subnet
0-255
Clock Source ID
(None), 0-15
(None)
Control Status
Enabled, Disabled
Enabled
Enable Status
Enabled, Disabled.
Enabled
Issue 02 (2010-09-24)
3-19
3 Configuring Clocks
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Clock Source
Switching from the Function Tree. Click the Clock Source Switching Condition tab.
Step 2 Click Query to query the existing parameter settings.
Step 3 Double-click the parameter column and set the alarms and performance events that are to be
used as the clock source switching conditions to Yes.
Step 4 Click Apply. In the Operation Result dialog box, click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Clock Source
Switching from the Function Tree. Click the Clock Source Reversion Parameter tab.
NOTE
To set the clock source reversion for multiple NEs in batches, Choose Configuration > NE Batch
Configuration > Batch Clock Operation from the main menu. . Click the Clock Source Reversion
Parameter tab. In the Object Tree, select the desired NEs and click
Step 2 Double-click and set the reversion mode and the WTR time.
3-20
Issue 02 (2010-09-24)
3 Configuring Clocks
NOTE
Do not set Clock Source WTR Time(min) to 0 to avoid repeated switching when the clock is unstable.
Step 3 Click Apply. In the Operation Result dialog box, click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The PXC board must be configured.
Precautions
In the OptiX RTN 600, external clock source 1 indicates the external clock on the PXC board
in slot 1 and external clock source 2 indicates the external clock on the PXC board in slot 3.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock >
Phase-Locked Source Output by External Clock from the Function Tree.
Step 2 Modify the clock output parameters.
Parameters
Parameter
Value Range
Default Value
Description
External Clock
Output Mode
2 Mbit/s, 2 MHz
2 Mbit/s
Issue 02 (2010-09-24)
3-21
3 Configuring Clocks
Parameter
Value Range
Default Value
Description
External Clock
Output Timeslot
SA4-SA8, ALL
ALL
External Clock
Output Threshold
2M Phase-Locked
Source Fail
Condition
Threshold Disabled,
Not Inferior to G.
813 SETS Signal,
Not Inferior to G.
812 Local Clock
Signal, Not Inferior
to G.812 Transit
Clock Signal, Not
Inferior to G.811
Clock Signal
Threshold Disabled
No Failure
Condition, AIS,
LOF, AIS OR LOF
No Failure
Condition
2M Phase-Locked
Source Fail Action
Prerequisite
You must be an NM user with "NE operator" authority or higher.
3-22
Issue 02 (2010-09-24)
3 Configuring Clocks
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Clock Subnet
Configuration from the Function Tree. Click the Clock Quality tab.
Step 2 Click Query to query the existing parameter settings.
Step 3 Click the Clock Source Quality tab and set Configuration Quality to a desired level.
NOTE
Step 4 Click Apply. In the Operation Result dialog box, click Close.
Step 5 If the quality level of a clock source is zero, you can specify the level manually. Click the Manual
Setting of 0 Quality Level tab and set Manual Setting of 0 Quality Level to a desired level.
NOTE
To set the clock source quality for multiple NEs in batches, Choose Configuration > NE Batch
Configuration > Batch Clock Operation from the main menu. Click the Manual Setting of 0 Quality
Level tab. In the Object Tree, select the desired NEs and click
Step 6 Click Apply. In the Operation Result dialog box, click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Clock Subnet
Configuration from the Function Tree. Click the SSM Output Control tab.
Step 2 Set the Control Status of the clock source.
Issue 02 (2010-09-24)
3-23
3 Configuring Clocks
Step 3 Click Apply. In the Operation Result dialog box, click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock Source
Priority from the Function Tree.
Step 2 Set Use the clock source of the data port.
Step 3 Click Apply.
----End
Parameters
Parameter
Value Range
Default Value
Description
Yes, No
No
Prerequisite
You must be an NM user with "NE operator" authority or higher.
3-24
Issue 02 (2010-09-24)
3 Configuring Clocks
Context
When the clock tracing relationships are changed, the U2000 refreshes the tracing status in the
Clock View automatically.
Procedure
Step 1 In the Main Topology window, selectClock View from the Current View drop-down list.
Step 2 Select the NE to be queried or configured from the object tree. In the Clock View, right-click
and choose Search Clock Link from the shortcut menu.
Step 3 In the Operation Result dialog box, click Close.
----End
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Clock Source
Switching from the Function Tree.
Step 2 Click the Clock Source Switching tab, and click Query to query the current switching status
of the current clock source.
3-25
3 Configuring Clocks
Prerequisite
l
Context
CAUTION
Performing clock source switching may cause signal jitter and bit errors.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Clock Source
Switching from the Function Tree. Click the Clock Source Switching tab.
Step 2 Click Query to query the current switching status of a clock source.
Step 3 Optional: If the Lock Status is Lock, right-click and choose Release Lockout.
Step 4 Right-click the clock source that you want to switch and choose a switching operation.
NOTE
Before switching the clock source, make sure that the new clock source that is not locked and that is of a
good quality is created in the priority table.
Step 5 Optional: To restore the automatic clock source selection mode, right-click the switched clock
source and choose Clear Switching.
----End
3-26
Issue 02 (2010-09-24)
Issue 02 (2010-09-24)
4-1
4-2
Issue 02 (2010-09-24)
BMC Algorithm
In a PTP clock network, the equipment computes the best clock source according to the BMC
algorithm.
The BMC algorithm compares the descriptive data of two clocks and detects the better one,
which is selected as the clock source. The BMC algorithm includes the following algorithms:
l
Data set comparison algorithm: The NE selects the clock of better quality as the clock
source. If an NE receives two or more channels of clock signals from the same grandmaster
clock (GMC), the NE selects one channel of the clock signals that traverses the least nodes
as the clock source.
State decision algorithm: The result of data set comparison determines the next state of the
port.
Clock Architecture
Figure 4-1 shows the architecture of the IEEE 1588V2 clock.
Issue 02 (2010-09-24)
4-3
BITS
GMC
Master
OC
TC
Slave
BC
Master
BC
Slave
Master
TC+OC
OC
Master
Slave
Slave
OC
NOTE
l Master: A master port provides a time source for the downstream equipment.
l Slave: A slave port receives the clock signals from the upstream port.
The OptiX RTN equipment supports four architectures of the IEEE 1588V2 clock.
4-4
Ordinary clock (OC): The OC equipment provides only one port to extract the IEEE 1588
packets. The OC equipment can work as a slave clock equipment and maintains
synchronization with the upstream clock. The equipment extracts the clock packets from
the port that supports the IEEE 1588 packets and recovers the clock. The equipment can
also work as a master clock equipment, which inputs the external time from the external
time interface, and outputs the clock signals to the downstream through the port that
supports the IEEE 1588 packets.
Boundary clock (BC): When used as a BC, the equipment provides multiple ports to extract
the IEEE 1588 packets. The BC can work as either master clock equipment or slave clock
equipment. The BC equipment can distribute the clock packets to the downstream through
multiple ports, but the OC equipment can distribute the clock packets to the downstream
through only one port.
Transparent clock (TC): The TC equipment transparently transmits the IEEE 1588 packets
and records the period when the packets stay on the equipment. During the period, the TC
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
equipment transports the packets to the slave clock equipment for processing. The TC
equipment only transparently transmits the clock, and does not recover the clock.
End-to-end TC: The TC equipment adopts the end-to-end delay measurement
mechanism between the master and slave clocks.
Peer-to-peer TC: The TC adopts the point-to-point delay measurement mechanism.
l
TC+OC: The TC+OC equipment corrects and transparently transmits the time stamps for
the IEEE 1588V2 packets, and achieves clock synchronization. By adopting the BMC
algorithm, the TC+OC equipment selects the clock source, which is then sent to the system
clock module. If necessary, the clock source can be used as the system clock of the
equipment.
NOTE
The end-to-end TC and peer-to-peer TC adopt different mechanisms to realize delay transmission, and
cannot operate in the same communication channel alternatively. That is, the adjacent TC equipment along
one time channel adopts either the end-to-end TC or peer-to-peer TC, but not both at the same time.
Master-Slave Synchronization
In the case of master-slave synchronization, each slave clock maintains synchronization with
the master clock by exchanging the synchronization packets with the master clock.
Figure 4-2 shows the master-slave synchronization process of the equipment.
Figure 4-2 Master-slave synchronization process
Time stamp at
slave clock
Slave clock
Master clock
t1
Sync packets
t2
t1t2
t3
t1t2t3
Delay_Req
packets
t4
Delay_Resp
packets
t1t2t3t4
At time point t1, the master clock sends the Sync packets that contain time stamp t1 to the
slave clock.
At time point t2, the slave clock receives the Sync packets and obtains time stamp t1.
At time point t3, the slave clock sends the Delay_Req packets to the master clock.
Issue 02 (2010-09-24)
4-5
At time point t4, the master clock receives the Delay_Req packets. Then, the master clock
sends the Delay_Resp packets that contain time stamp t4 to the slave clock.
NOTE
A time stamp (TS) is used to transmit the time information. The Sync packets, Delay_Req packets, and
Delay_Resp packets are used to generate or communicate the time information. The OC equipment and
BC equipment maintain synchronization by processing related time information.
The slave clock computes the delay and offset from the master clock according to time stamps
t1, t2, t3, and t4. Then, the slave clock corrects the time according to the delay and offset.
l
Delay = [(t4-t1)-(t3-t2)]/2
Offset = [(t2-t1)+(t3-t4)]/2
Sync
Delay_Req
Pdelay_Req
Pdelay_Resp
Announce
Delay_Resp
Management
Signaling
The Sync, Delay_Req, and Delay_Resp packets are used to generate or transport the timing
information. The OC and BC maintains synchronization by using the timing information and
adopting the delay request-response mechanism.
The Pdelay_Req and Pdelay_Resp packets are used to measure the link delay between two clock
ports that support the Pdelay mechanism. The link delay is used to correct the timing information
contained in the Sync packets in the P2P TC system. The OC and BC maintain synchronization
according to the link delay and the timing information contained in the Sync messages.
NOTE
The Pdelay mechanism is intended to measure the point-to-point transmission time between two
communication ports that support the Pdelay mechanism. The point-to-point transmission time is the link
delay. The P2P TC has to compute the link delay by adopting the Pdelay mechanism.
Issue 02 (2010-09-24)
network. This meets the requirement of the telecommunications network for precise time. The
equipment with the PTP clock can achieve networkwide frequency synchronization and time
synchronization in the packet switching network (PSN). The telecommunications network carry
various services. Certain services require precise time synchronization, such as the network
voting and charging services. In such a scenario, the IEEE 1588V2 clock is applicable and
ensures precise time synchronization.
Figure 4-3 shows the scenario where the PTP clock is applicable.
Figure 4-3 Networking diagram for typical application of the PTP clock
Node B
NE E
GPS
RTN 910
OC
NE B
NE A
BC
NE C
RNC
BC
NE D
RTN 910
BC
BC
NE F
OC
RTN 910
RTN 950
As shown in Figure 4-3, BITS sends clock signals to NE A and RNC. NE A works as BC
equipment and sends the PTP packets to two ports. NE E and NE F, which are connected to
Node B, work as the OC equipment, recover the PTP clock, and send the clock to Node B through
the external time interface.
Issue 02 (2010-09-24)
4-7
Required
Start
Optional
Setting the Frequency
Selection Mode
Setting the PTP System
Time
Setting the PTP Clock
Subnet
Issue 02 (2010-09-24)
The PTP priority service needs to be configured only when the PTP clock works in the TC or
TC+OC mode.
The PTP clock source priority needs to be configured only when the PTP clock works in the TC
+OC mode.
4-9
or the PTP packets from the client side should be forwarded (Layer 2 or Layer 3), set the status
of the PTP clock port accordingly. By default, the equipment performs Layer 2 forwarding for
the PTP packets.
4.5.10 Setting the Cable Transmitting Wrap
The cable transmitting distance wrap indicates the transmitting time difference of the cables
between two sets of equipment in the transmit and receive directions. During deployment, you
can use the GPS to compute the transmitting time difference between the two directions. Set the
cable transmitting wrap, and thus the equipment performs the clock compensation. The wrap
modes includes the length wrap and time wrap. The equipment can choose only one mode.
4.5.11 Setting the Wait-to-Restore Time for the PTP Clock Source
When a clock port recovers from a failure, the system acknowledges the validity of the port a
certain period later. This period is referred to as the wait-to-restore (WTR) time. During the
WTR time, the system considers the clock signals as unavailable and the clock signals are not
involved in the clock source selection.
4.5.12 Setting the PTP Clock Source Priority
If the NE works in the TC+OC mode, you need to set the priorities for the clock sources traced
by the OC. Normally, the OC traces the PTP clock source of the highest priority. If the PTP
clock source of the highest priority fails, the OC traces the PTP clock source of the second highest
priority. The priority table is configured with a source ID. When a local port receives a clock
source in the priority table, the port checks whether the domain that the clock source belongs to
is consistent with the domain configured at the local end.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In NE Explorer, choose Configuration > Clock > Frequency Selection Mode from the
Function Tree.
Step 2 In Frequency Selection Mode, you can select one of the clock synchronization mode.
CAUTION
l When the external time interface is set to the external time input interface, the NE can run
in only the physical synchronization mode. That is, the frequency selection mode of the
equipment that accesses the external clock must be set to the physical synchronization mode.
l When the NE is running in the PTP synchronization mode, the external interface cannot be
set to the external time input interface.
4-10
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The PTP system time can be set only when the current time of the NE traces the local clock.
Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Synchronization
Attribute.
Step 2 In PTP System Time, click
NOTE
Move the cursor to the time bar. To increase the value, click or right-click the time bar. To decrease the
value, hold the Shift key, and click or right-click the time bar.
4-11
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The working mode of the equipment clock should not be TC.
Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Subnet
Configuration from the Function Tree.
Step 2 Select the Clock Subnet tab to set the clock subnet number.
Step 3 Click Apply.
Step 4 Click the BMC tab to set the parameters related to the BMC in the clock subnet.
Step 5 Click Apply.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > External Time Interface.
Step 2 Click the Basic Attribute tab.
Step 3 Set Interface Mode of the external time interface.
Step 4 Optional: If Interface Mode is set to External Time Interface, you can set Direction,
Interface Protocol Type, and Interface Eletricity.
NOTE
l OptiX RTN 910 and 950: Interface Protocol Type is set according to the type of the external time
protocol. Interface Protocol Type can be set to DCLS or 1PPS+TIME.
l OptiX RTN 910 and 950: Interface Level is set according to the setting of the external time interface.
Interface Level can be set to RS422.
The BMC-related parameters can be set only the working mode is set to BC or OC, and when the Interface
Mode of the External Time Interface is set to External Time Interface.
Issue 02 (2010-09-24)
Step 7 Click the Cable Transmitting Distance tab to set the cable parameters for the clock
compensation such as Transmitting Distance Mode, Transmitting Length(m), and
Transmitting Time(ns).
NOTE
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Synchronization
Attribute from the Function Tree.
Step 2 Set Work Mode, SLAVE_ONLY, Time Adjusting, and Transmitting Packet Multi-cast
Mode.
Step 3 According to the working mode of the NE in the network, set Work Mode.
NOTE
The PTP standard defines four working modes, that is, BC, OC, TC, and TC+OC. When the NE working
mode is TC or TC+OC, if the PTP clock service or the clock source priority table is already configured,
you cannot modify the working mode.
Step 4 When Work Mode is set to OC, SLAVE_ONLY can be set to SLAVE_ONLY or
NON_SLAVE_ONLY.
NOTE
l SLAVE_ONLY indicates that the NE in the OC mode can only trace other PTP clocks.
l NON_SLAVE_ONLY indicates that in the OC mode the NE can function as the standy clock to trace
other PTP clocks and the NE can also function as the primary clock. Whether the NE functions as the
standby clock or primary clock depends on the quality of the PTP clock.
Step 6 When Work Mode is set to BC or OC, Transmitting Packet Multi-cast Mode is configurable.
NOTE
If the mode is set to Entire Multi-cast, the equipment multicasts all the PTP packets. If the mode is set to
Part Multi-cast, the equipment unicasts the DELAY packets.
Issue 02 (2010-09-24)
4-13
Step 7 When Work Mode is set to BC or OC, Protocol Packet Format is configurable.
NOTE
The Protocol Packet Format can be set to NMEA or UBX. The default parameter value is NMEA. This
parameter is valid only when Interface Protocol Type of the external time interface is set to 1PPS
+Time. When Interface Protocol Type of the external time interface is set to DCLS, the parameter can
still be set but the parameter value is invalid.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Synchronization
Attribute from the Function Tree.
Step 2 Click the Port Status tab, and then click New to display the Create PTP Clock Port dialog
box.
Step 3 Select the corresponding board, and then select the corresponding port from Available Port.
Click
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Service from the
Function Tree.
Step 2 Click New to display the New Clock Service dialog box.
Step 3 Set Service ID and Service Name.
Step 4 In the dialog box, click the UNI tab. Then, click Configuration to display the Configure
Port dialog box.
4-14
Issue 02 (2010-09-24)
Step 5 Select the port from the Available Port list, and then click
Selected Port list.
NOTE
l When the PTP packets contain VLAN tags, you need to set a VLAN tag for the port. The OptiX
RTN equipment supports the setting of only one VLAN tag.
l When two TC services share a port, set a VALN tag for the port if the port is a UNI port.
l If the port is Layer 3 port, the port can be used only as a UNI port for the TC service. The encapsulation
mode should be ETH and no VLAN tag can be set.
In the dialog box, click the NNI tab. Then, click New to display the New PW dialog box.
2.
Click the General Attributes tab to set PW ID, PW Type, PW Ingress Label, and PW
Egress Label.
3.
Click
to display Resource Selection Window. Select the tunnel that carries the
PW, and then click OK.
NOTE
Select the static MPLS tunnel, because the dynamic MPLS tunnel cannot carry the PTP packets.
4.
Issue 02 (2010-09-24)
Optional: Click the Advanced Attributes tab to set the corresponding parameters.
4-15
5.
Click OK in the New PW dialog box to finish the PW configuration on the NNI side.
Step 8 Click OK in the New Clock Service dialog box to complete the configuration of the clock
service.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
A PTP clock port must be created.
Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Synchronization
Attribute from the Function Tree.
Step 2 Click the Port Message tab to set P/E Mode and the corresponding packet periods.
NOTE
In P2P mode, the TC equipment transmits only the PDELAY packets. You can set the period for the TC
equipment to transmit the PDELAY packets.
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
A PTP clock port must be created.
The working mode of the NE must be set to BC or OC.
Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Synchronization
Attribute from the Function Tree.
Step 2 Click the Port Status tab and set PTP Message Format.
NOTE
If the port is configured with a clock service, do not change the PTP message format of the port.
Step 3 Optional: If the working mode of the NE is set to BC or OC, and the PTP packets contain VLAN
IDs, set PTP Message VLAN to a proper VLAN value accordingly.
NOTE
In the case of interconnection with the client equipment, if the client equipment forwards the PTP packets
according to VLAN IDs, the PTP packets should contain VLAN IDs.
Step 4 Optional: If the working mode of the NE is set to BC or OC, set Port Status accordingly.
NOTE
Step 5 Optional: If the working mode of the NE is set to BC or OC, double-click the blank line below
Selected Clock Source to display the Clock Source Coding Configuration dialog box.
Step 6 Optional: Set the parameters related to the clock source and click OK.
Issue 02 (2010-09-24)
4-17
CAUTION
The clock sources at the local port should be numbered in the same manner as the clock sources
at the upstream port, or the clock sources do not need to be numbered. Otherwise, clock tracing
fails if the working mode of the NE is set to BC or OC.
NOTE
When one PTP clock port receives multiple channels of clock signals, number the clock sources so that
the NE selects one clock source. For example, multiple TC clock services from the upstream equipment
are converged onto one clock port on the local equipment and then are transmitted to the downstream
equipment. As a result, the port on the downstream equipment connected to the upstream equipment
receives the multiple TC clock services. In this case, you need to number the clock sources at the port on
the downstream equipment.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Synchronization
Attribute.
Step 2 Click the Cable Transmitting Wrap tab.
Step 3 Set Wrap Direction. Positive direction indicates that the transmitting distance or transmitting
time of the clock receive end is longer than the transmitting distance or transmitting time at the
clock transmit end. Negative direction indicates that the transmitting distance or transmitting
time of the clock transmit end is longer than the transmitting distance or transmitting time at the
clock receive end.
Step 4 Wrap Mode can be set to Length or Time.
Step 5 According to Wrap Mode, set Wrap Length(m) or Wrap Time(ns).
NOTE
Issue 02 (2010-09-24)
4.5.11 Setting the Wait-to-Restore Time for the PTP Clock Source
When a clock port recovers from a failure, the system acknowledges the validity of the port a
certain period later. This period is referred to as the wait-to-restore (WTR) time. During the
WTR time, the system considers the clock signals as unavailable and the clock signals are not
involved in the clock source selection.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
A PTP clock port must be created.
The working mode of the NE must be set to BC, OC or TC+OC.
Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Source Priority
Table from the NE Explorer.
Step 2 Click the Clock Source Reversion Parameter tab and set Clock Source WTR Time(min.).
NOTE
Set Clock Source WTR Time(min.) within the range of 0 minutes to 12 minutes at a spacing of 1 minute.
By default, the WTR time is 5 minutes.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The working mode of the NE must be set to TC+OC.
Procedure
Step 1 In NE Explorer, choose Configuration > Clock > PTP Clock > Clock Source Priority
Table from the NE Explorer.
Step 2 Click the Clock Source Priority Table tab and click New to create a clock source.
You can change the working mode of NE only after you delete the PTP clock source priority.
Step 3 Select a clock source and click
Issue 02 (2010-09-24)
or
4-19
4-20
Issue 02 (2010-09-24)
5 Configuring Orderwire
Configuring Orderwire
Issue 02 (2010-09-24)
5-1
5 Configuring Orderwire
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Orderwire from the Function
Tree. Click the General tab.
Step 2 Click Query to query information from the NE.
Step 3 Set Call Waiting Time(s), Telephone No. and orderwire ports.
NOTE
l Call Waiting Time(s) should be set to the same value for all NEs with orderwire communication.
When the number of NEs is smaller than 30, set the value to 5 seconds. Otherwise, set it to 9 seconds.
l The telephone number must be unique in an orderwire subnet.
l Set the length of the telephone number according to the actual requirements. The maximum length is
eight digits and the minimum length is three digits. In the same orderwire subnet, the number length
must be the same.
Issue 02 (2010-09-24)
5 Configuring Orderwire
F1 Data Port
Node A
Node B
Node C
Node A and node C transmit data through the F1 data port. You can use the U2000 to configure
each node as follows:
l
Configure added or dropped services at node A. Select the F1 data port and a port on the
intermediate frequency (IF) board as two data channel ports. In this case, the F1 data port
service from the client side is added or dropped from the F1 data port of the orderwire
board, and is transmitted through the a port on the intermediate frequency (IF) board.
Configure pass-through services at node B. Select two a port on the intermediate frequency
(IF) board as the data channel ports. In this case, the F1 data port service passes through
the two a port on the intermediate frequency (IF) board at this node.
Configure added or dropped services at node C. Select the F1 data port and a port on the
intermediate frequency (IF) board as two data channel ports. In this case, the F1 data port
service is cross-connected from the a port on the intermediate frequency (IF) board to the
orderwire board, and then added or dropped from the F1 data port of the orderwire board.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The boards that are related to the synchronous data services must be configured.
Context
In the case of the RTN 610/620, the synchronous data services are transmitted over the F1
overhead bytes in the SDH/PDH radio frame or STM-N frame.In the case of the RTN 605, the
synchronous data services are transmitted over the F1 overhead bytes in the radio frame.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire
from the Function Tree.
Issue 02 (2010-09-24)
5-3
5 Configuring Orderwire
NOTE
Data Channel 1 and Data Channel 2: Depending on the board configuration, the following ports can be
selected.
l SDH optical/electrical port: When the SDH optical/electrical line port is selected, the F1 byte in the
SDH frame of this port is used.
l IF port: When the IF port is selected, the self-defined F1 byte in the radio frame of this port is used.
l F1 port: When the F1 port is selected, the F1 synchronous data port on the SCC board is used. The F1
port conforms to the G.703 and the rate is 64 kbit/s.
l external clock port of the PXC board: When the PXC-1 is selected, the external clock port of the PXC
board is used. In this case, the external clock port is used as the output port of the overhead bytes.
When the F1 data channel of the RTN 605 transmits the synchronous data services, the F1 data channel is
bound with the working channel in most cases.
Issue 02 (2010-09-24)
5 Configuring Orderwire
any of the bytes Serial1-Serial4 in the normal SDH overheads is used to transparently transmit
the asynchronous data services. In the case of the RTN 605, the Serial byte in the PDH radio
overheads is used to transmit the asynchronous data services. The asynchronous data services
need to not be configured, but are automatically activated.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The boards that are related to the asynchronous data services must be configured.
Context
The asynchronous data port of the OptiX RTN 600 is an RS-232 port and can implement the
universal asynchronous receiver/transmitter (UART) full-duplex communication. The service
transmission is required to be point-to-point transparent transmission. Therefore, the port rate
and transmission control protocol need not be configured and the maximum communication rate
is 19.2 kbit/s. Hence, the asynchronous data port is also considered as the transparent data port.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire
from the Function Tree.
Step 2 Click the Broadcast Data Port tab.
Step 3 Set the parameters of the broadcast data port.
Issue 02 (2010-09-24)
5-5
5 Configuring Orderwire
NOTE
Issue 02 (2010-09-24)
5 Configuring Orderwire
The networking diagram forms the foundation of service planning. In the following example,
the networking diagram shows the NE networking mode and service requirements.
5.4.2 Service Planning
According to the service requirements and the equipment specifications that are shown in the
networking diagram, the network planning department can plan all the services of the NEs. In
the following example, the service planning covers all the parameter information required for
configuring the NEs.
5.4.3 Configuration Process
You can configure the synchronous data services of each NE based on the parameters of the
service planning, by using the NMS.
64kbit/s
NE 2
NE 3
64kbit/s
Issue 02 (2010-09-24)
5-7
5 Configuring Orderwire
NE1
NE2
NE3
Data Channel 1
6-SL1
5-IF1A
5-IF1A
Data Channel 2
F1
6-SL1
F1
NE1
NE2
NE3
Data Channel 1
6-SL1
5-IF0A
8-IF0-1
Data Channel 2
F1
6-SL1
F1
NE2
NE1
6-SL1-1
NE3
6-SL1-1 5-IF1A-1
5-IF1A-1
F1
F1
2-SCC: F1
2-SCC: F1
Add/Frop
Forward
Station
Timeslot
6-SL1-1
6-SL1-1 5-IF0A-1
F1
2-SCC: F1
NE3
NE2
NE1
8-IF0-1
F1
2-SCC: F1
Add/Frop
Forward
5-8
The F1 port on the SCC board in slot 2 of NE1 and F1 port on the SCC board in slot 2 of
NE3 are used to add/drop the synchronous data services.
The F1 overhead byte on the SDH line between the SL1 board in slot 6 of NE1 and the SL1
board in slot 6 of NE2 is used to transmit the synchronous data services.
The F1 overhead byte on the radio link between the IF1A board in slot 5 of NE2 and the
IF1A board in slot 5 of NE3 is used to transmit the synchronous data services.
Issue 02 (2010-09-24)
5 Configuring Orderwire
The synchronous data services are passed through between the SL1 board in slot 6 and the
IF1A board in slot 5 of NE2.
The F1 port on the SCC board in slot 2 of NE1 and F1 port on the SCC board in slot 2 of
NE3 are used to add/drop the synchronous data services.
The F1 overhead byte on the SDH line between the SL1 board in slot 6 of NE1 and the SL1
board in slot 6 of NE2 is used to transmit the synchronous data services.
The F1 overhead byte on the radio link between the IF0A board in slot 5 of NE2 and the
IF board in logical slot 8 of NE3 is used to transmit the synchronous data services.
The synchronous data services are passed through between the SL1 board in slot 6 and the
IF0A board in slot 5 of NE2.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
All the required boards must be added.
Procedure
Step 1 5.2.2 Configuring F1 Data Port Services.
1.
In the NE Explorer, select NE1 and then choose Configuration > Orderwire from the
Function Tree.
2.
3.
Hold down the Ctrl key and select two data channels from Available Data Channel. Then,
click Apply.
Parameter
Value Range
Description
Data Channel 1
6-SL1-1
Data Channel 2
F1
In the NE Explorer, select NE2 and then choose Configuration > Orderwire from the
Function Tree.
2.
3.
Hold down the Ctrl key and select two data channels from Available Data Channel. Then,
click Apply.
Issue 02 (2010-09-24)
5-9
5 Configuring Orderwire
Parameter
Value Range
Description
Data Channel 1
6-SL1-1
Data Channel 2
5-IF1A-1
When the 5-IF1A-1 port is selected, the selfdefined F1 byte in the radio frame of this port is
used.
In the NE Explorer, select NE3 and then choose Configuration > Orderwire from the
Function Tree.
2.
3.
Hold down the Ctrl key and select two data channels from Available Data Channel. Then,
click Apply.
Parameter
Value Range
Description
Data Channel 1
5-IF1A-1
When the 5-IF1A-1 port is selected, the selfdefined F1 byte in the radio frame of this port is
used.
Data Channel 2
F1
----End
5-10
Issue 02 (2010-09-24)
5 Configuring Orderwire
Point-to-point communication must exist between the monitor server and the environment
monitor, through services at the asynchronous data ports.
NE 1
NE 3
RS-232
RS-232
Issue 02 (2010-09-24)
Parameter
NE1
NE2
NE3
Overhead Byte
SERIAL1
SERIAL1
SERIAL1
Broadcast Data
Source
6-SL1-1
5-IF1A-1
5-IF1A-1
S1
6-SL1-1
S1
5-11
5 Configuring Orderwire
NE1
NE2
NE3
Overhead Byte
SERIAL1
SERIAL1
SERIAL
Broadcast Data
Source
6-SL1-1
5-IF0A-1
8-IF0-1
S1
6-SL1-1
S1
NE3
NE2
NE1
6-SL1-1
6-SL1-1 5-IF1A-1
5-IF1A-1
Serial1
Serial1
2-SCC: S1
2-SCC: S1
Add/Frop
Forward
Station
Timeslot
NE3
NE2
NE1
6-SL1-1
6-SL1-1 5-IF0A-1
Serial1
2-SCC: S1
8-IF0-1
Serial
2-SCC: S1
Add/Frop
Forward
As shown in the timeslot allocation diagram, the asynchronous data services are as follows:
5-12
The S1 port on the SCC board in slot 2 of NE1 and S1 port on the SCC board in slot 2 of
NE3 are used to add and drop the asynchronous data services.
The S1 port on the SCC board in slot 2 of NE1 and S1 port of NE3 are used to add and
drop the asynchronous data services.
The SERIAL1 overhead byte on the SDH optical line between the SL1 board in slot 6 of
NE1 and the SL1 board in slot 6 of NE2 is used to transmit the asynchronous data services.
The self-defined SERIAL byte on the radio link between the IF1A board in slot 5 of NE2
and the IF1A board in slot 5 of NE3 to transmit the asynchronous data services.
The self-defined SERIAL byte on the radio link between the IF0A board in slot 5 of NE2
and the IF0 board in logical slot 8 of NE3 to transmit the asynchronous data services.
The asynchronous data services are passed through between port 1 of the SL1 board in slot
6 and port 1 of the IF1A board in slot 5 of NE2.
The asynchronous data services are passed through between port 1 of the SL1 board in slot
6 and port 1 of the IF0A board in slot 5 of NE2.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
5 Configuring Orderwire
Prerequisite
You must be an NM user with "NE operator" authority or higher.
All the required boards must be added.
Procedure
Step 1 5.3.2 Configuring Asynchronous Data Services.
1.
In the NE Explorer, select NE1 and then choose Configuration > Orderwire from the
Function Tree.
2.
Click the Broadcast Data Port tab. After setting the parameters, click Apply.
Parameter
Value Range
Description
Overhead Byte
SERIAL1
Broadcast Data
Source
6-SL1-1
Selected
Broadcast Data
Sink
S1
In the NE Explorer, select NE2 and then choose Configuration > Orderwire from the
Function Tree.
2.
Click the Broadcast Data Port tab. After setting the parameters, click Apply.
Issue 02 (2010-09-24)
5-13
5 Configuring Orderwire
Parameter
Value Range
Description
Overhead Byte
SERIAL1
Broadcast Data
Source
6-SL1-1
Selected
Broadcast Data
Sink
5-IF1A-1
In the NE Explorer, select NE3 and then choose Configuration > Orderwire from the
Function Tree.
2.
Click the Broadcast Data Port tab. After setting the parameters, click Apply.
Parameter
Value Range
Description
Overhead Byte
SERIAL1
Broadcast Data
Source
5-IF1A-1
Selected
Broadcast Data
Sink
S1
----End
5-14
Issue 02 (2010-09-24)
Issue 02 (2010-09-24)
6-1
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Apply to the EOW, AUX and CXP boards.
Context
The external alarms are also considered as housekeeping alarms. The external alarm port is a
relay port. This port can be either in the "on" state or in the "off" state.
The alarm input ports report the RELAY_ALARM alarm (the alarm parameter indicates the port
number of the input alarm) after the external alarm is triggered. To ensure that the external alarm
port works normally, the external alarm cables must be correctly connected.
Procedure
Step 1 Select the board from the Object Tree in the NE Explorer. Choose Configuration >
Environment Monitor Configuration > Environment Monitor Interface from the Function
Tree.
Step 2 In the case of RTN 600 NEs:
1.
2.
6-2
b.
c.
Click Apply.
b.
Issue 02 (2010-09-24)
c.
Click Apply.
Select the attributes you want to configure from the drop-down list.
2.
3.
----End
Outputs two external alarmsone external alarm, and reports a critical alarm and a major
alarmreports a critical alarm. The alarm modes are the same, that is,mode is as follows: the
port enters the "off" state when an alarm is generated.
Inputs three external alarms. The alarm modes are the same, that is, an alarm is generated
when the port enters the "on" state.
Alarm In1
Alarm In2
Alarm In3
Alarm Out
Issue 02 (2010-09-24)
6-3
Alarm In1
Alarm In2
Alarm In3
Alarm Out1
Alarm Out2
Alarm Mode
6-4
Port No.
Alarm Mode
Issue 02 (2010-09-24)
Port No.
Alarm Mode
Prerequisite
You must be logged in to the NE.
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 Configure external alarms.
1.
In the NE Explorer, select the EOW board and then choose Configuration > Environment
Monitor Configuration > Environment Monitor Interface from the Function Tree.
2.
Configure the input alarm. Select Input Relay from the drop-down list. Click Apply.
3.
Paramet
er
Value Range
Using
Status
Used
Alarm
Mode
EOW-1
EOW-2
Description
EOW-3
Configure the output alarm. Select Output Relay from the drop-down list. Click Apply.
Parameter
Value Range
Description
EOW-1
Issue 02 (2010-09-24)
Use or Not
Used
Working Mode
Automatic
6-5
Parameter
Value Range
Description
EOW-1
Alarm Trigger
Conditions
Critical Alarm
Auto Trigger
Alarm Mode
An Alarm is
Generated if the
Relay Turns Off
and Low Level is
Caused
Parameter
Value Range
EOW-1
Description
EOW-2
Use or Not
Used
Working
Mode
Automatic
Alarm
Trigger
Conditions
Critical
Alarm Auto
Trigger
Major Alarm
Auto Trigger
Alarm
Mode
----End
6-6
Issue 02 (2010-09-24)
Issue 02 (2010-09-24)
7-1
Procedure
Step 1 Select the corresponding navigation path and check the related board parameters.
1.
Check SDH board parameters. For the SDH board parameters, see Table 7-1.
Table 7-1 SDH board parameters
Board Type
Parameter
Navigation Path
Application
Scenario
SDH
Laser Switch
a. In the NE
Explorer, select
a board.
b. Choose
Configuration
> SDH
Interface from
the Function
Tree.
c. Click By
Board/Port
(channel) and
select Port from
the drop-down
list.
When configuring
services on an
optical interface of
a board, enable this
parameter.
Optical(Electrical)
Interface Loopback
l Non-loopback:
It is a normal
state. When the
equipment runs
normally, set
this parameter to
non-loopback.
l Inloop: The loop
is performed
toward the local
NE.
l Outloop: The
loop is
performed
toward the
opposite NE.
Inloop and
outloop of an
optical interface
affect services.
They are used to
locate faults.
2.
7-2
Check PDH board parameters. For the PDH board parameters, see Table 7-2.
Issue 02 (2010-09-24)
Paramet
er
Navigation
Path
Tributary
Loopback
PDH
Service
Load
Indication
Retiming
Mode
Application Scenario
a. In the NE
Explorer,
select a board.
b. Choose
Configuratio
n > PDH
Interface
from
the
Function
Tree.
c. Click
By
Board/Port
(channel)
and
select
Port from the
drop-down
list.
3.
Check RTN board parameters. For the RTN board parameters, see Table 7-3.
Table 7-3 RTN board parameters
Boar
d
Type
Paramet
er
Navigation
Path
Radio
Work
Mode
a. In the NE
Explorer,
select a board.
b. Choose
Configuratio
n
>
IF
Interface
from
the
RTN
Radio
Link ID
Issue 02 (2010-09-24)
Application Scenario
Specifies the microwave working mode. Its
formats are service capacity, working
bandwidth and modulation mode.
The transmit end and the receive end must
have the same settings of the microwave
working mode.
Radio Link ID: 1 to 4094
7-3
Boar
d
Type
Paramet
er
Navigation
Path
IF Port
Loopback
Function
Tree.
c. Click
By
Board/Port
(channel)
and
select
Port from the
drop-down
list.
Application Scenario
Sets the loopback status of an intermediate
frequency interface on the equipment.
Non-Loopback refers to the normal status. It
is not required to set loopback during normal
equipment operation.
Outloop means that the input signal passes
through the ingress port and reaches the
intermediate frequency board at the local NE
and then is directly loopbacked to the service
egress end.
Inloop means that the input signal returns
from the intermediate frequency board of the
destination NE along the original trail.
This function is usually used to locate faults
for various IF interfaces. Performing loopback
on an intermediate frequency interface is a
diagnosis function which may affect services
of related ports. Exercise caution before
performing this function.
2M
Wayside
Enable
Status
ATPC
Enable
Status
4.
Check data board parameters. For the data board parameters, see Table 7-4.
Table 7-4 Data board parameters
Boar
d
Type
Ethern
et
7-4
Parame
ter
Enabled/
Disabled
Navigation Path
Application Scenario
a. In the NE Explorer,
select a board.
b. Choose
Configuration >
Issue 02 (2010-09-24)
Boar
d
Type
Parame
ter
Working
Mode
Maximu
m Frame
Length
Navigation Path
Application Scenario
Ethernet Interface
Management
>
Ethernet
Interface from the
Function Tree.
c. Click
External
Port.
d. Click the Basic
Attributes tab.
MAC
Loopbac
k
PHY
Loopbac
k
Entry
Detectio
n
Issue 02 (2010-09-24)
a. In the NE Explorer,
select a board.
b. Choose
Configuration >
Ethernet Interface
Management
>
Ethernet
Interface from the
Function Tree.
c. Click
External
Port.
d. Click the TAG
Attributes tab.
7-5
Step 2 Modify board parameters according to service planning and actual board configurations.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The required SDH interface boards must be added.
Procedure
Step 1 Select the SDH interface board from the Object Tree in the NE Explore. Choose
Configuration > SDH Interface from the Function Tree.
Step 2 Select By Board/Port(Channel) (default option of the system).
Step 3 Select Port from the dropdown list and set the parameters of the SDH interface board.
7-6
Issue 02 (2010-09-24)
Parameters
Parameter
Value
Default Value
Description
Laser Switcha
Open, Close
Open
Optical (Electrical)
Interface Loopback
Non-Loopback,
Inloop, Outloop
Non-Loopback
Issue 02 (2010-09-24)
7-7
Parameter
Value
Default Value
Description
VC4 Loopback
Non-Loopback,
Inloop, Outloop
Non-Loopback
NOTE
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The required PDH interface boards must be added.
Procedure
Step 1 Select the PDH interface board from the Object Tree in the NE Explorer. Choose
Configuration > PDH Interface from the Function Tree.
Step 2 Select By Board/Port(Channel) (default value).
Step 3 Select Port from the drop-down list, Set the parameters of the PDH interface.
Step 4 Select Port from the drop-down list, Set the parameters of the PDH interfaces according to the
types of the PDH interfaces.
l Set the parameters of the PDH interfaces on the E1 interface board.
7-8
Issue 02 (2010-09-24)
l Set the parameters of the PDH interface on the E3/T3 interface board.
Parameters
Parameter
Value Range
Default Value
Description
Tributary Loopback
Non-Loopback,
Inloop, Outloop
Non-Loopback
Path Impedance
75 ohms
Service Load
Indication
Load, Non-Loaded
Load
Issue 02 (2010-09-24)
7-9
Parameter
Value Range
Default Value
Description
Retiming Modea
Normal, Retiming
Mode of Tributary
Clock, Retiming
Mode of CrossConnect Clock
Normal
E3, T3
E3
Input Signal
Equalizationb
Unequalized,
Equalized
Unequalized
7-10
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Output Signal
Equalizationb
Unequalized,
Equalized
Unequalized
NOTE
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The required IF boards must be added.
Procedure
Step 1 In the NE Explorer, select the IF board from the Object Tree. Choose Configuration > IF
Interface from the Function Tree.
Step 2 Click the IF Attributes tab.
Step 3 Set each parameter for the IF attributes.
NOTE
The IFH1 board of the IDU 605 1F/2F does not support the setting of the Radio Work Mode.
The IFH2 board of the IDU 620 does not support the setting of the Radio Work Mode.
Issue 02 (2010-09-24)
7-11
NOTE
The IF0 board of the IDU 605 1A/1B/2B does not support the ATPC Automatic Threshold Enable
Status.
7-12
Issue 02 (2010-09-24)
Parameters
Parameter
Value Range
Default Value
Description
1,4E1,7MHz,QPSK
(IF1A/B)
5,16E1,28MHz,QP
SK (IF0A/B)
1,4E1,7MHz,QP
SK
7,STM-1,28MHz,
128QAM (IFX)
2,4E1,3.5MHz,
16QAM
5,16E1,28MHz,QP
SK (IF0)
3,8E1,14MHz,Q
PSK
4,8E1,7MHz,
16QAM
5,16E1,28MHz,
QPSK
6,16E1,14MHz,
16QAM
7,STM-1,28MH
z,128QAM
8,E3,28MHz,QP
SK
9,E3,14MHz,
16QAM
10,22E1,14MHz
,32QAM
11,26E1,14MHz
,64QAM
12,32E1,14MHz
,128QAM
13,35E1,28MHz
,16QAM
14,44E1,28MHz
,32QAM
15,53E1,28MHz
,64QAM
16,5E1,7MHz,Q
PSK
17,10E1,14MHz
,QPSK
18,2E1,3.5MHz,
QPSK
l In the case of the
IDU 605 1A/1B/
2B, the value
Issue 02 (2010-09-24)
7-13
Parameter
Value Range
Default Value
Description
range is as
follows:
5,16E1,28MHz,
QPSK
16,5E1,7MHz,Q
PSK
17,10E1,14MHz
,QPSK
18,2E1,3.5MHz,
QPSK
Radio Link ID
1 to 4094
Non-Loopback,
Inloop, Outloop
Non-Loopback
7-14
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
2M Wayside Enable
Statusb
Enabled, Disabled
Disabled
2M Wayside Input
Boardb
1, 3
XPIC Enablec
Enabled, Disabled
Enabled
Issue 02 (2010-09-24)
7-15
Parameter
Value Range
Default Value
Description
ATPC Enable
Statusd
Enabled, Disabled
Disabled
ATPC Upper
Threshold (dBm)d
-45 dBm
ATPC Lower
Threshold (dBm)d
-70dBm
ATPC Automatic
Threshold Enable
Status
Enabled, Disabled
Enabled
7-16
Issue 02 (2010-09-24)
NOTE
l a: The IFH2 and IFX boards do not support the loopback on the IF ports.
l b: The IFH2 and IF0A/B boards do not support wayside E1 services.
l c: The IFH2, IF0A/B, and IF1A/B boards do not support the XPIC function.
l d: The ATPC attributes need to be set to the same values at both ends of a radio link.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The required IF boards must be added.
The corresponding ODU must be added in the slot layout diagram.
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU
Interface from the Function Tree.
Step 2 Click the Radio Frequency Attributes tab.
Step 3 Configure the TX frequency and T/R spacing.
7-17
Parameters
Parameter
Value Range
Default Value
Description
Transmit Frequency
(MHz)
Maximum Transmit
Power (dBm)
Transmit Power
(dBm)
7-18
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Receive Power
(dBm)
0-4294967.295
Configure
Transmission Status
mute, unmute
unmute
Issue 02 (2010-09-24)
7-19
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet board must be included in the NE Panel.
Precautions
l
The IDU 610 supports the Ethernet board EFT4. The IDU 620 supports the Ethernet boards
EFT4 and EMS6.
Ethernet ports FE1-FE4 of an EFT4 board correspond to PORT1-PORT4 respectively.
The EFT4 board does not support the setting of TAG attributes, network attributes, and
advanced attributes.
Ethernet ports FE1-FE4 of an EMS6 board correspond to PORT1-PORT4 respectively.
Ports GE1 and GE2 of an EMS6 board correspond to PORT5 and PORT6 respectively.
7-20
Issue 02 (2010-09-24)
The IDU 605 IF/2F supports the Ethernet board EMS4 (a logical board).
Ethernet ports FE1-FE3 of an EMS4 board (a logical board) correspond to PORT1PORT3 respectively. Port FE4/GE1 of an EMS4 board corresponds to PORT4.
Ethernet ports FE1-FE2 of an EM4T board correspond to PORT1-PORT2 respectively.
Ports GE1 and GE2 of an EM4T board corresponds to PORT3 and PORT4 respectively.
The following procedures describe how to configure the external port of an EMS6 board.
The EFT4 board does not support the configuration of the TAG attributes, network
attributes, and advanced attributes.
The Hybrid IF board (IFH2) provides the GE port for accessing Ethernet services and it
supports certain Ethernet service access functions. The procedure for configuring the
Ethernet port of the IFH2 board is similar to the procedure for configuring the external
Ethernet port. The IFH2 board, however, supports the configuration of only the basic
attributes and flow control function.
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet Interface
Management > Ethernet Interface from the Function Tree. Select External Port.
NOTE
If you need to configure the attributes of the Ethernet port on the IFH2 board, select the IFH2 board in the
NE Explorer.
2.
3.
Click Apply.
2.
3.
Click Apply.
2.
Issue 02 (2010-09-24)
7-21
3.
Click Apply.
2.
3.
Click Apply.
2.
3.
Click Apply.
----End
Parameters
Parameter
Value Range
Default Value
Description
Enabled/Disabled
Enabled, Disabled
Disabled
7-22
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Working Mode
10M Full-Duplex,
100M Full-Duplex,
Auto-Negotiation
(EFT4)
Auto-Negotiation
10M Half-Duplex,
10M Full-Duplex,
100M Half-Duplex,
100M Full-Duplex,
1000M FullDuplex, AutoNegotiation (EMS6)
Auto-Negotiation,
10M Full-Duplex,
100M Full-Duplex,
1000M Full-Duplex
(IFH2)
10M Half-Duplex,
10M Full-Duplex,
100M Half-Duplex,
100M Full-Duplex,
Auto-Negotiation (a
logical board EMS4,
PORT1-PORT3)
10M Half-Duplex,
10M Full-Duplex,
100M Half-Duplex,
100M Full-Duplex,
1000M FullDuplex, AutoNegotiation (a
logical board EMS4,
PORT4)
Issue 02 (2010-09-24)
7-23
Parameter
Value Range
Default Value
Description
Maximum Frame
Length
1518-1535 (EFT4)
1522
1518-9600 (EMS6)
1522/1632 (a logical
board EMS4)
MAC Loopback
Non-Loopback,
Inloop
Non-Loopback
PHY Loopback
Non-Loopback,
Inloop
Non-Loopback
7-24
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
NonAutonegotiation
Flow Control Mode
Disabled, Enable
Symmetric Flow
Control, Send Only,
Receive Only (EFT4
and EMS6)
Disabled
Disabled, Enable
Symmetric Flow
Control (IFH2)
Disabled, Enable (a
logical board
EMS4)
Issue 02 (2010-09-24)
7-25
Parameter
Value Range
Default Value
Description
Autonegotiation
Flow Control Mode
Disabled, Enable
Symmetric/
Dissymmetric Flow
Control, Enable
Symmetric Flow
Control, Enable
Dissymmetric Flow
Control (EFT4 and
EMS6)
Disabled
Disabled, Enable
Symmetric Flow
Control (IFH2)
Disabled, Enable
Symmetric Flow
Control (a logical
board EMS4)
Entry Detection
Enabled, Disabled
Enabled
TAG
Tag Aware
7-26
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Default VLAN ID
1 to 4095
VLAN Priority
0 to 7
Port Attributes
UNI
Enabling Broadcast
Packet Suppression
Enabled, Disabled
Disabled
Broadcast Packet
Suppression
Threshold
10% to 100%
30%
Issue 02 (2010-09-24)
7-27
Parameter
Value Range
Default Value
Description
Loop Detection
Disabled, Enabled
Disabled
Disabled, Enabled
Enabled
Ingress
Egress
Type of Data
Frame
How to Process
Tag aware
Access
Hybrida
Tagged frame
Untagged frame
Tagged frame
l If the VLAN ID
in the frame is
Default VLAN
ID, the port
strips the VLAN
tag from the
frame and then
transmits the
frame.
l If the VLAN ID
in the frame is
not Default
VLAN ID, the
port directly
transmits the
frame.
7-28
Issue 02 (2010-09-24)
NOTE
a: When the TAG attribute of a port on the EMS4 board (a logical board) that is supported by the IDU 605
1F/2F is set to Hybrid, the packet that is forwarded by this port remains the same as the packet that enters
the bridge.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet board must be included in the slot layout.
Precautions
The IDU 610 supports the Ethernet board EFT4. The IDU 620 supports the Ethernet boards
EFT4 and EMS6.
l
The EFT4 board supports VCTRUNKs 1-4, which are bound with PORTs 1-4 respectively.
The EFT4 board does not support the setting of TAG attributes and network attributes.
The EMS6 board supports VCTRUNKs 1-8. VCTRUNKs 1-8 determine the services to be
transmitted depending on information of the created Ethernet services.
The following procedures describe how to configure the internal port of an EMS6 board. The
EFT4 board does not support the configuration of the TAG attributes and network attributes.
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet Interface
Management > Ethernet Interface from the Function Tree. Choose Internal Port.
Step 2 Set the encapsulation and mapping protocol used by the port.
1.
2.
3.
Click Apply.
2.
Click Configuration.
The system displays the Bound Path Configuration dialog box.
3.
4.
In Available Bound Paths, set Level and Direction of the bound paths.
Issue 02 (2010-09-24)
7-29
5.
Select required items in Available Resources and Available Timeslots and click
6.
7.
Click OK. Then, click Yes in the dialog box that is displayed.
2.
3.
Click Apply.
2.
3.
Click Apply.
7-30
1.
2.
Issue 02 (2010-09-24)
3.
Click Apply.
----End
Parameters
Parameter
Value Range
Default Value
Description
Mapping Protocol
GFP
Scramble
Unscrambled,
Scrambling Mode
[X43+1],
Scrambling Mode
[X48+1]
Scrambling Mode
[X43+1]
Yes, No
Yes
FCS32, FCS16, No
FCS32
Issue 02 (2010-09-24)
7-31
Parameter
Value Range
Default Value
Description
l Big endian
(GFP)
l Little endian
(LAPS or
HDLC)
Extension Header
Option
No, Yes
No
Configurable Ports
VCTRUNKs
VCTRUNK 1
Available Bound
Paths
7-32
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Enabling LCAS
Enabled, Disabled
Disabled
LCAS Mode
Huawei Mode,
Standard Mode
Huawei Mode
2000
WTR Time(s)
0 to 720
300
Issue 02 (2010-09-24)
7-33
Parameter
Value Range
Default Value
Description
TSD
Enabled, Disabled
Disabled
Entry Detection
Enabled, Disabled
Enabled
TAG
Tag Aware
Default VLAN ID
1 to 4095
VLAN Priority
0 to 7
7-34
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Port Attributes
UNI
Activated,
Inactivated
Activation Status
NOTE
l The Mapping Protocol and protocol parameters set for VCTRUNKs at one end of a transmission line must
be the same as the Mapping Protocol and protocol parameters set for VCTRUNKs at the other end of the
transmission line.
l The Enabling LCAS and LCAS protocol parameters set for VCTRUNKs at one end of a transmission line
must be the same as the Enabling LCAS and LCAS protocol parameters set for VCTRUNKs at the other
end of the transmission line.
l The timeslots to which the paths bound with a VCTRUNK correspond must be the same at both ends of a
transmission line.
Ingress
Issue 02 (2010-09-24)
Type of Data
Frame
How to Process
Tag Aware
Access
Hybrid
Tagged frame
Untagged frame
7-35
Direction
Egress
Type of Data
Frame
How to Process
Tag Aware
Access
Hybrid
Tagged frame
l If the VLAN ID
in the frame is
Default VLAN
ID, the port
strips the VLAN
tag from the
frame and then
transmits the
frame.
l If the VLAN ID
in the frame is
not Default
VLAN ID, the
port directly
transmits the
frame.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet board must be included in the slot layout.
Precautions
The EMS6 board supports the modification of the type field of Jumbo frames.
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet Interface
Management > Jumbo Frame from the Function Tree.
Step 2 Modify the type field of Jumbo frames.
Issue 02 (2010-09-24)
Parameters
Parameter
Value Range
Default Value
Description
Jumbo Frame
00 00 to FF FF
88 70
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet board must be included in the slot layout.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Advanced Attributes
> QinQ Type Area Settings from the Function Tree.
Step 2 Modify the type field of QinQ frames.
Parameters
Parameter
Value Range
Default Value
Description
81 00, 98 A8, 91 00
81 00
Issue 02 (2010-09-24)
7-37
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet board must be included in the slot layout.
Procedure
Step 1 Select the Ethernet board from the Object Tree in the NE Explorer. Choose Configuration >
Ethernet Interface Management > Ethernet Interface from the Function Tree. Select
Internal Port.
Step 2 Click the Bound Path tab.
Step 3 Click Configuration.
The system displays the Bound Path Configuration dialog box.
Step 4 Optional: Dynamically increase the VCTRUNK bandwidth.
1.
2.
In Available Bound Paths, set Level and Direction of the bound paths.
3.
Select desired items in Available Resources and Available Timeslots and click
4.
7-38
1.
2.
Issue 02 (2010-09-24)
3.
Parameters
For specific parameters, see 7.3.2 Configuring the Internal Port of the Ethernet Board.
Prerequisite
l
Context
CAUTION
Disabling an Ethernet port may interrupt services.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Interface
Management > Ethernet Interface from the Function Tree.
Step 2 Click the External Port option button.
Step 3 Click the Basic Attributes tab. Double-click Enabled/Disabled of the port to be disabled and
select Disabled.
Step 4 Click Apply. In the Prompt dialog box, click OK. In the Operation Result dialog box, click
Close.
----End
Issue 02 (2010-09-24)
7-39
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
CAUTION
If you set the service load indication to Non-Loaded, the services may be interrupted or you
may fail to log in to certain NEs.
Procedure
Step 1 In the NE Panel, select a board, right-click, and choose Service Load Indication from the
shortcut menu.
Step 2 Double-click Service Load Indication of the corresponding path, and select Load or NonLoaded.
Step 3 Click Apply. In the Operation Result dialog box, click Close.
NOTE
If you select Non-Loaded, you need not click OK in the Confirm dialog box.
----End
Postrequisite
In the case of a path that is configured with services but does not carry real services, if you set
Service Load Indication to Non-Loaded, you need to change the value of Service Load
Indication to Load at both ends of the services after the path carries real services in the future.
7-40
Issue 02 (2010-09-24)
Issue 02 (2010-09-24)
8-1
Ethernet packets. The Ethernet virtual interface attributes include general attributes and layer 3
attributes.
8.8 Configuring an IMA Group
When the RTN equipment accesses IMA services, configure an ATM IMA group at the access
node.
8-2
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > SDH
Interface from the Function Tree.
Step 2 Select the desired board.
Step 3 Set the parameters as required.
NOTE
Issue 02 (2010-09-24)
8-3
Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is
successful.
Step 5 Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > SDH
Interface from the Function Tree.
Step 2 Click the Advanced Attributes tab.
Step 3 Select the board to be configured and set the parameters as required.
Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is
successful.
Step 5 Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The encapsulation type of the created SDH interface must be PPP.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > SDH
Interface from the Function Tree.
Step 2 Select Port, right-click, and choose Query PPP Running Status from the shortcut menu. The
PPP Running Status dialog box is displayed.
Step 3 Click Close.
----End
8-4
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The encapsulation type of the created SDH interface must be PPP.
Context
CAUTION
Resetting the PPP will interrupt services.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > SDH
Interface from the Function Tree.
Step 2 Right-click Port, and choose Reset PPP from the shortcut menu. A dialog box is displayed,
indicating that the operation will interrupt the services.
Step 3 Click Yes. A dialog box is displayed, indicating that the operation was successful.
Step 4 Click Close.
----End
Context
The application scenario of a PDH interface depends on the setting of the interface attributes.
For details, refer to Table 8-1.
Table 8-1 Application scenario of PDH interfaces
Issue 02 (2010-09-24)
Application Scenario
Interface Type
Required Interface
Attribute
E1 interface
8-5
Application Scenario
Interface Type
Required Interface
Attribute
E1 interface
E1 interface
NOTE
When the E1 interface is used to carry the CES service, set the general attributes and an advanced attribute, that
is, frame format, to ensure that the frame format is the same as the service encapsulation format. When the
emulation mode of a CES service is CESoPSN, it is recommended that you set the frame format at the interface
to CRC-4 multiframe. When the emulation mode of a CES service is SAToP, the frame format at the interface
should be set to non-framing.
When the E1 interface is used to carry the ATM service, the Layer 2 attributes should be set. In addition, the
IMA group should be created. When setting the layer 2 attributes of the E1 interface, set Port Mode to Layer
2 in 8.2.1 Setting General Attributes of PDH Interfaces.
When the E1 interface is used to carry the tunnels, the Layer 3 attributes should be set. In addition, create the
ML-PPP group, and configure the interface as an ML-PPP member.
Carry Tunnel
Start
Start
Start
Configure general
attributes
Configure general
attributes
Configure general
attributes
Configure advanced
attributes
Configure advanced
attributes
Configure layer 3
attributes
End
End
Configure advanced
attributes
End
Required
Optional
Issue 02 (2010-09-24)
Before you create services, you need to set the general attributes of the corresponding PDH
interfaces. The general attributes of a PDH interface define the related information of the physical
layer.
8.2.2 Setting the Layer 3 Attributes of PDH Interfaces
Before you run PPP on a PDH interface, you need to set the layer 3 attributes of the PDH interface.
The layer 3 attributes of a PDH interface define the related attributes of the network layer.
8.2.3 Setting the Advanced Attributes of PDH Interfaces
The advanced attributes of PDH interfaces include frame format, line encoding format and
loopback mode.
8.2.4 Querying the Running Status of PPP
In the case of a network failure, you can query the running status of the PPP to analyze the cause
of the failure.
8.2.5 Resetting the PPP
In the case of a network failure, you can reset the PPP to enable the PPP ports on the two ends
of a link to re-negotiate.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > PDH
Interface from the Function Tree.
Step 2 Select the desired board.
Step 3 Set the parameters as required.
NOTE
Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is
successful.
Issue 02 (2010-09-24)
8-7
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > PDH
Interface from the Function Tree.
Step 2 Click the Layer 3 Attributes tab.
Step 3 Select the desired board and set the parameters as required.
NOTE
Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is
successful.
Step 5 Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > Interface Management > PDH
Interface from the Function Tree.
Step 2 Click the Advanced Attributes tab.
Step 3 Select the board to be configured and set the parameters as required.
8-8
Issue 02 (2010-09-24)
NOTE
In the case of the OptiX RTN , Frame Mode of the packets at the PDH interface can be set to 30 or 31. In
hybrid networking, make sure that the frame modes of the local port and opposite port should be the same.
l 30: In the E1 frame format, timeslots 1-15 and 17-31 are used to transport service data.
l 31: In the E1 frame format, timeslots 1-31 are used to transport service data.
Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is
successful.
Step 5 Click Close.
----End
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > PDH
Interface from the Function Tree.
Step 2 Select Port, right-click, and choose Query PPP Running Status from the shortcut menu. The
PPP Running Status dialog box is displayed.
Step 3 Click Close.
----End
Prerequisite
l
Context
CAUTION
Resetting the PPP will interrupt services.
Issue 02 (2010-09-24)
8-9
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > PDH
Interface from the Function Tree.
Step 2 Right-click Port, and choose Reset PPP from the shortcut menu. A dialog box is displayed,
indicating that the operation will interrupt the services.
Step 3 Click Yes. A dialog box is displayed, indicating that the operation was successful.
Step 4 Click Close.
----End
Context
The application scenario of an Ethernet interface depends on the setting of the interface attributes.
For details, refer to Table 8-2.
Table 8-2 Application scenario of Ethernet interfaces
Application Scenario
Interface Type
Required Interface
Attribute
Ethernet interface
General attributes
Ethernet interface
Issue 02 (2010-09-24)
When an Ethernet interface is used to carry a tunnel, you need to configure the layer 3 attributes
of the Ethernet interface. The layer 3 attributes of an Ethernet interface define the related
attributes of the network layer.
8.3.4 Setting the Advanced Attributes of Ethernet Interfaces
The routine maintenance parameters can be set through setting the advanced attributes of
Ethernet interfaces.
8.3.5 Configuring Flow Control
In the case that the flow control function is enabled, if congestion occurs on the link, the Ethernet
interface sends a PAUSE frame to the opposite end, and then the opposite end stops transmitting
Ethernet packets. As a result, congestion is avoided.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management >
Ethernet Interface from the Function Tree.
Step 2 Click the General Attributes tab.
Step 3 Select the desired board and set the parameters as required.
NOTE
l When Port Mode is set to Layer 2, the Encapsulation Type support Null.
l When Port Mode is set to Layer 3, the Encapsulation Type support 802.1Q, and then the interface
can be used by tunnel.
l When Port Mode is set to Layer Mix, the port can carry layer 2 services and layer 3 services. To create
a VLAN sub-interface, set the port mode to Layer Mix.
l Before changing Layer 3 to Layer Mix, make sure that route protocols, such as IGP-ISIS not enabled
on the port. Before changing Layer Mix to Layer 3, make sure that no VLAN tag is added to the port
and no Layer 2 service is configured on the port.
l In the case an NNI interface,Max Data Packet Size(byte) must be larger than 960. A DCN packet
contains a maximum of 960 bytes. If Max Data Packet Size(byte) is smaller than 960, the DCN packets
in the receive direction may be lost.
Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is
successful.
Step 5 Click Close.
----End
8-11
within the PSN network. The Layer 2 attributes of an Ethernet interface define the related
information of the data link layer.
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management >
Ethernet Interface from the Function Tree.
Step 2 Click the Layer 2 Attributes tab.
Step 3 Select the desired board and set the parameters as required.
NOTE
Step 4 Click Apply. Click OK, The Operation Result dialog box is displayed indicating that the
operation is successful.
Step 5 Click Close.
----End
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management >
Ethernet Interface from the Function Tree.
Step 2 Click the Layer 3 Attributes tab.
Step 3 Select the desired board and set the parameters as required.
8-12
Issue 02 (2010-09-24)
NOTE
Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is
successful.
Step 5 Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > Interface Management >
Ethernet Interface from the Function Tree.
Step 2 Click the Advanced Attributes tab.
Step 3 Select the board to be configured and set the parameters as required.
Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is
successful.
Step 5 Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management >
Ethernet Interface from the Function Tree.
Step 2 Click the Flow Control tab.
Issue 02 (2010-09-24)
8-13
Step 3 Select the desired board and set the parameters as required.
Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is
successful.
Step 5 Click Close.
----End
Context
The application scenario of an microwave interface depends on the setting of the interface
attributes. For details, refer to Table 8-3.
Table 8-3 Application scenario of microwave interfaces
Interface Attributes
Signal to Carry
Functioning Location
Layer 2 attributes
Ethernet packets
Layer 3 attributes
Tunnels
NNI side
NOTE
When the microwave interface is used to carry the QinQ Link, the configuration procedure is similar to the
configuration procedure when the microwave interface is used to carry the Ethernet service. In this case, however,
the encapsulation types are different. For details, see 8.4.3 Setting the Layer 2 Attributes of Microwave
Interfaces.
8-14
Issue 02 (2010-09-24)
Carry Tunnel
Start
Start
Creating IF 1+1
Protection
Creating IF 1+1
Protection
Setting the IF
Attributes
Setting the IF
Attributes
End
End
Required
Optional
8-15
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The IF board and the ODU that connects to the IF board must be added.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Microwave Interface from the Function Tree.
Step 2 Click the General Attributes tab.
Step 3 Select the desired board and set the parameters as required.
NOTE
l When Port Mode is set to Layer 2, the Encapsulation Type support Null, 802.1Q and QinQ.
l When Port Mode is set to Layer 3, the Encapsulation Type support 802.1Q, and then the interface
can be used by tunnel.
l In the case an NNI interface, MTU(byte), which indicates the maximum data packet length, must be
set to a value larger than 960. A DCN packet contains a maximum of 960 bytes. If MTU(byte) is
smaller than 960, the DCN packets in the receive direction may be lost.
Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is
successful.
Step 5 Click Close.
----End
8-16
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The IF board and the ODU that connects to the IF board must be added.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Microwave Interface from the Function Tree.
Step 2 Click the IF Attributes tab.
Step 3 Select the desired board and set the parameters as required.
NOTE
l When you set Assured Capacity Modulation and Full Capacity Modulation, note the following
points:
This parameter is valid only when Enable AM is set to Enable.
l When you set Manually Specified Modulation, note the following points:
This parameter is valid only when Enable AM is set to Disable.
l When you set ATPC Upper Threshold(dBm), note the following points:
Generally, ATPC Upper Threshold(dBm) should be 20 dB to 30 dB higher than ATPC Lower
Threshold(dBm), and must not be less than 15 dB. If the difference between the upper threshold and
the lower threshold is big, the number of ATPC adjustments is reduced and the system load is also
reduced. If the difference between the upper threshold and the lower threshold is small, the transmit
power is adjusted in a timely manner and the interference to adjacent systems is reduced.
l When you set ATPC Lower Threshold(dBm), note the following points:
Generally, set this parameter to a value of 10 dB or greater than the receiver sensitivity to prevent
sudden fast fading because sudden fast fading makes the RSL value lower than the receiver sensitivity.
Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is
successful.
Step 5 Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The IF board and the ODU that connects to the IF board must be added.
Issue 02 (2010-09-24)
8-17
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Microwave Interface from the Function Tree.
Step 2 Click the Layer 2 Attributes tab.
Step 3 Select the desired board and set the parameters as required.
NOTE
When you set QinQ Type Domain, note the following points:
QinQ Type Domain can be set only when Encapsulation Type is QinQ.
Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is
successful.
Step 5 Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The IF board and the ODU that connects to the IF board must be added.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Microwave Interface from the Function Tree.
Step 2 Click the Layer 3 Attributes tab.
Step 3 Select the desired board and set the parameters as required.
NOTE
Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is
successful.
Step 5 Click Close.
----End
8-18
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The IF board and the ODU that connects to the IF board must be added.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface
Management > Microwave Interface from the Function Tree.
Step 2 Click the Advanced Attributes tab.
Step 3 Select the desired board and set the parameters as required.
NOTE
When you set Radio Link ID, note the following points:
l If this parameter is different from Received Link ID, the NE reports the MW_LIM alarm and inserts
the AIS into the downstream.
l Set this parameter according to the planning. Each radio link of an NE should have a unique Link ID,
and the Link IDs at both the ends of a radio link should be the same.
l Before performing the loopback operation for the IF board, disable the AM function at the two ends
of a link.
Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is
successful.
Step 5 Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The required IF boards must be added.
The corresponding ODU must be added in the slot layout diagram.
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU
Interface from the Function Tree.
Step 2 Click the Radio Frequency Attributes tab.
Issue 02 (2010-09-24)
8-19
l When you set Transmission Frequency (MHz), note the following points:
l The parameter specifies the channel center frequency.
l This parameter cannot be set to a value that is less than the minimum TX frequency supported by
the ODU + 50% channel spacing or more than the maximum TX frequency supported by the ODU
- 50% channel spacing.
l The difference between the TX frequencies of both the ends of a radio link is a T/R spacing.
l Set this parameter according to the planning.
l When you set T/R Spacing (MHz), note the following points:
l This parameter indicates the spacing between the TX power and receive power of the ODU. If
Station Type of the ODU is TX high, the TX power is one T/R spacing higher than the receive
power. If Station Type of the ODU is TX low, the TX power is one T/R spacing lower than the
receive power.
l If the ODU supports only one T/R spacing, set this parameter to 0, indicating that the T/R spacing
supported by the ODU is used.
l The T/R spacing of the ODU should be set to the same value at both the ends of a radio link.
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The required IF boards must be added.
The corresponding ODU must be added in the slot layout diagram.
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU
Interface from the Function Tree.
Step 2 Click the Radio Frequency Attributes tab.
Step 3 Configure the TX frequency and T/R spacing.
8-21
Parameters
Parameter
Value Range
Default Value
Description
Transmit Frequency
(MHz)
Maximum Transmit
Power (dBm)
Transmit Power
(dBm)
8-22
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Receive Power
(dBm)
0-4294967.295
Configure
Transmission Status
mute, unmute
unmute
Issue 02 (2010-09-24)
8-23
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Serial
Interface from the Function Tree.
Step 2 Click New in the General Attributes tab and the New Serial Interface dialog box is displayed.
Step 3 Set the parameters as required.
NOTE
l In the case of the serial interface at the VC12 level, currently a serial interface can be bound to only
one timeslot.
l In the case of the serial interface at the 64 kbit/s level, when the E1 frame mode is 30, timeslots 0 and
16 are unavailable. When the E1 frame mode is 31, timeslot 0 is unavailable.
Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is
successful.
Step 5 Click Close.
----End
8-24
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
A serial interface must be created.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Serial
Interface from the Function Tree.
Step 2 Set the parameters as required.
NOTE
When you set Port Mode to Layer 2, Encapsulation Type is ATM. The serial interface supports IMA
binding.
When you set Port Mode to Layer 3, you can set Encapsulation Type to PPP or Null. When you set
Encapsulation Type to PPP, you can add the serial interface to an MP group. The serial interfaces that
are bound to the same MP group have the same E1 frame mode. When Encapsulation Type is Null, Port
Mode can be changed to Layer 2.
In the case an NNI interface,Max Data Packet Size (byte) must be larger than 960. A DCN packet contains
a maximum of 960 bytes. If Max Data Packet Size (byte) is smaller than 960, the DCN packets in the
receive direction may be lost.
Step 3 Click Apply. The Operation Result dialog box is displayed indicating that the operation was
successful.
Step 4 Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
In General Attributes, Encapsulation Type must be set to PPP.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Serial
Interface from the Function Tree.
Step 2 Click the Layer 3 Attributes tab and set the parameters as required.
Issue 02 (2010-09-24)
8-25
Step 3 Click Apply. The Operation Result dialog box is displayed indicating that the operation was
successful.
Step 4 Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The encapsulation type of the created serial interface must be PPP.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Serial
Interface from the Function Tree.
Step 2 Select Port, right-click, and choose Query PPP Running Status from the shortcut menu. The
PPP Running Status dialog box is displayed.
Step 3 Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The encapsulation type of the created serial interface must be PPP.
8-26
Issue 02 (2010-09-24)
Context
CAUTION
Resetting the PPP will interrupt services.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > Serial
Interface from the Function Tree.
Step 2 Right-click Port, and choose Reset PPP from the shortcut menu. A dialog box is displayed,
indicating that the operation will interrupt the services.
Step 3 Click Yes. A dialog box is displayed, indicating that the operation was successful.
Step 4 Click Close.
----End
Context
Follow the procedure shown in Figure 8-3 to configure an MP group.
Issue 02 (2010-09-24)
8-27
Create MP
group
Configure members to an
MP group
End
Required
Optional
8-28
Issue 02 (2010-09-24)
Bandwidth increased.
The ML-PPP complies with RFC1990 (PPP multilink protocol). The ML-PPP protocol focuses
on the transmission of fragments of data packets over multiple data links, reassembly and
sequence of these fragments.
Long sequence number fragment format (LSNFF): The sequence number field has 24 bits.
This format is the default format.
Short sequence number fragment format (SSNFF): The sequence number field has 12 bits.
The fragment format of transmitted packets can be different from that of received packets on
the condition of mutual negotiation. If the negotiation does not allow that the received packets
are of the LSNFF format, the MP packets of the SSNFF format should be transmitted.
Issue 02 (2010-09-24)
8-29
Control
0xFF
0xFF
0x03
PPP Header
Protocol
0x003d
0x003d
sequence
number
ML-PPP Header
sequence
number
fragment data
....
FCS
PPP FCS
Adress
0xFF
0xFF
Control
0x03
PPP Header
Protocol
ML-PPP Header
0x003d
0x003d
sequence number
fragment data
....
FCS
PPP FCS
8-30
Issue 02 (2010-09-24)
ML-PPP
NE2
PPP link
PPP link
PPP link
Prerequisite
l
The E1 Frame Format of the local MP group and the opposite MP group should be
consistent.
Context
NOTE
The MP group can be bound only with the E1 interfaces of the same board.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > MP
Group Management from the Function Tree.
Step 2 Click New in the General Attributes tab and the New MP Group dialogue box is displayed.
Step 3 Set the parameters as required.
Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation was
successful.
Step 5 Click Close.
----End
Prerequisite
l
Issue 02 (2010-09-24)
8-31
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > MP
Group Management from the Function Tree.
Step 2 Select an MP group and click Configuration. The Config Member Interface dialog box is
displayed.
Step 3 Set the parameters as required.
Step 4 Click Apply. The Warning dialog box is displayed, indicating that the operation may interrupt
the services.
NOTE
Deleting the member interface of the MP group may damage the service.
The member interface in the same MP group must have the same frame mode. That is, the values of Frame
Mode are all 30 or 31. for the parameters of Frame Mode, to see E1 Frame Format.
Step 5 Click Yes. A dialog box is displayed, indicating that the operation is successful.
Step 6 Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management >
Ethernet Virtual Interface from the Function Tree.
8-32
Issue 02 (2010-09-24)
Step 2 Click Query. The Operation Result dialog box is displayed dialog box is displayed indicating
that the operation is successful.
Step 3 Click Close. The general attributes of an Ethernet virtual interface are displayed in the field.
Step 4 Specify the port name as required.
Step 5 Click OK. A prompt is displayed indicating that the operation is successful. Click Close.
----End
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
The general attributes of Ethernet virtual interface must be set.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management >
Ethernet Virtual Interface from the Function Tree.
Step 2 Click the Layer 3 Attributes tab, set the Specify IP to Manually and set the IP Address and
IP Mask for the port.
Step 3 Double-click the Enable Tunnel field, and select Enabled.
Step 4 Click Apply. A prompt is displayed indicating that the operation is successful. Click Close.
----End
Context
Figure 8-6 shows the flow for configuring an IMA group.
Issue 02 (2010-09-24)
8-33
Configure bound
paths for an
ATM IMA group
Configure IMA
group attributes
Configure ATM
interface attributes
Reset an IMA
group
Modify an IMA
group
Delete an IMA
group
End
Required
Optional
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
When the MLPPP or CES services is configured or the DCN is enabled on the VCTRUNK, the
VCTRUNK resources are occupied and thus the IMA group cannot be created.
When an E1or Fractional E1 port is bound with an IMA group, Port Mode should be set to
Layer 2.
Context
NOTE
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM
IMA Management from Function Tree.
Step 2 Click the Binding tab and click Configuration. The Bound Path dialog box is displayed.
Step 3 Configure boards and VCTRUNK ports in Available Boards and Configurable Ports
respectively.
Step 4 Select E1, Fractional E1 for Level.
Step 5 Select a port in Available Resources. Click
Issue 02 (2010-09-24)
8-35
CAUTION
The VCTRUNK that is first added into the IMA group should be deleted at last.
The ports that are bound to the same VCTRUNK must have the same E1 frame mode or VC12
frame mode.
When the member links of an IMA group are at the serial ports of the 64K level, there are the
following restrictions:
l One serial port should be bound with a minimum of three 64K timeslots.
l The number of bound 64K timeslots should be the same for different serial ports.
l In one E1, only one serial port can be used as a member link of an IMA group.
Step 6 Click OK. A dialog box is displayed, indicating that the operation succeeds. Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 Click the NE in the NE Explorer. Choose Configuration > Interface Management > ATM
IMA Management from Function Tree.
Step 2 Click the IMA Group Management tab, enable the IMA protocol, and configure attributes of
the IMA group. Click Apply. A dialog box is displayed, indicating that the operation succeeds.
Click Close.
NOTE
----End
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM
IMA Management from the Function Tree. Click the ATM Interface Management tab.
Step 2 Optional: Click Query to query the current attributes of each interface.
Step 3 Set relevant attributes of the interfaces bound with the IMA group as required.
Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is
successful.
Step 5 Click Close.
----End
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM
IMA Management from Function Tree.
Step 2 Click the IMA Group States tab and select the IMA group for query. Click Query. A dialog
box is displayed, indicating that the operation succeeds. Click Close.
----End
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM
IMA Management from Function Tree.
Issue 02 (2010-09-24)
8-37
Step 2 Click the IMA Link States tab and select the IMA link for query. Click Query. A dialog box
is displayed, indicating that the operation succeeds. Click Close.
----End
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM
IMA Management from Function Tree.
Step 2 Click the IMA Group Management tab and select the IMA group. Click Reset. A dialog box
is displayed, indicating that the operation succeeds. Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
CAUTION
If any service is configured and activated at the ATM Trunk port for the IMA group, modification
of the IMA group may interrupt services. Exercise caution for this.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM
IMA Management from Function Tree.
Step 2 Click the IMA Group Management tab and modify related attributes of the IMA group. Click
Apply. A dialog box is displayed, indicating that the operation succeeds. Click Close.
----End
8-38
Issue 02 (2010-09-24)
Prerequisite
l
The IMA Protocol Enable Status of the IMA group must be Disabled.
Context
CAUTION
If any service is configured and activated at the ATM Trunk port for the IMA group, deleting
the IMA group may interrupt the services. Exercise caution for this.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM
IMA Management from the Function Tree.
Step 2 Click the Banding tab and select an IMA group. Click Delete. A dialog box is displayed,
indicating that the operation may interrupt the services. Click OK. A dialog box is displayed,
indicating that the operation is successful. Click Close.
----End
Issue 02 (2010-09-24)
8-39
Issue 02 (2010-09-24)
9-1
During the creation of a radio link, the link ID at local end must be consistent with that at the opposite end,
to ensure the communication.
Refer to Figure 9-1. The communication channel between two radio stations is the radio link.
The radio stations are classified by function as follows:
Figure 9-1 Classification of Radio Stations
Relay
Station
Add/Drop
Station
Terminal
Station
Terminal
Station
Pivotal
Station
Terminal
Station
Terminal station: A station located at either end of the link or at the endpoint of a tributary
link.
Relay station: A station located in the middle of the link without adding or dropping voice
channels.
Pivotal station: A station located in the backbone link to communicate with other stations
in various directions.
Add/drop station: A station located in the middle of the link to add/drop tributaries and
realize the communication in two directions of the backbone link.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The IF board and the ODU that connects to the IF board or IF port must be added.
9-2
Issue 02 (2010-09-24)
Precautions
l
In 1+1 HSB/SD protection mode, one protection group corresponds to one radio link. In
this case, you need configure only the IF/ODU information of the main equipment.
In 1+1 FD protection mode, one protection group corresponds to one radio link. In this
case, you need configure the IF/ODU information of the main equipment and the ODU
information of the standby equipment.
In the case of XPIC radio links, one XPIC workgroup corresponds to two radio links. The
IF/ODU information of the radio links should be configured in the XPIC workgroup.
In the case of N+1 radio links, one N+1 protection group corresponds to N+1 radio links
and the IF/ODU information of the N+1 radio links should be set respectively.
NOTE
1+1HSB: indicates that the IF 1+1 HSB protection is configured for the NE.
Procedure
Step 1 In the case of RTN 600 and RTN 900 V100R002 NEs, select the NE from the Object Tree in
the NE Explorer. Choose Configuration > Link Configuration from the Function Tree.
Step 2 In the case of RTN 900 V100R001 NEs, select the NE from the Object Tree in the NE Explorer.
Choose Configuration > Microwave Link Configuration from the Function Tree.
Step 3 Click IF/ODU Configuration.
Step 4 Click an IF board icon or ODU icon.
Then, the system displays the IF/ODU information of the radio link to which the IF board
belongs.
Step 5 Set the corresponding IF information of the radio link.
9-3
Click Apply after you set the IF information of the radio link and after you set the ODU information of the radio
link.
----End
Parameters
Parameter
Value Range
Default Value
Description
Work Mode
l 1,4E1,7MHz,Q
PSK
l 2,4E1,3.5MHz,
16QAM
l 3,8E1,14MHz,
QPSK
l 4,8E1,7MHz,
16QAM
l 5,16E1,28MHz,
QPSK
l 6,16E1,14MHz,
16QAM
l 7,STM-1,28MH
z,128QAM
l 8,E3,28MHz,Q
PSK
l 9,E3,14MHz,
16QAM
l 10,22E1,14MH
z,32QAM
l 11,26E1,14MH
z,64QAM
l 12,32E1,14MH
z,128QAM
l 13,35E1,28MH
z,16QAM
l 14,44E1,28MH
z,32QAM
l 15,53E1,28MH
z,64QAM
l 16,5E1,7MHz,
QPSK
l 17,10E1,14MH
z,QPSK
l 18,2E1,3.5MHz
,QPSK
9-4
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Link ID
1-4094
Enabled, Disabled
Disabled
ATPC Automatic
Threshold Enable
Status
Enabled, Disabled
Enabled
Issue 02 (2010-09-24)
9-5
Parameter
Value Range
Default Value
Description
TX Frequency
(MHz)
0-4294967.295
0.0
Range of Frequency
(MHz)
TX Power (dBm)
-10.0 to +35.0
-10.0
0-4294967.295
0.0
9-6
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
TX Status
mute, unmute
unmute
TX Power (dBm)
-10.0 to 35.0
TX High Threshold
-10.0 to 35.0
TX Low Threshold
-10.0 to 35.0
RX High Threshold
-90.0 to -20.0
RX Low Threshold
-90.0 to -20.0
Range of Power
(dBm)
For example: 12
Enable AM
Enabled, Disabled
Disabled
Channel Space
7M
Assured Capacity
Modulation
QPSK, 16QAM,
32QAM, 64QAM,
128QAM,
256QAM
QPSK
Issue 02 (2010-09-24)
9-7
Parameter
Value Range
Default Value
Description
Full Capacity
Modulation
QPSK, 16QAM,
32QAM, 64QAM,
128QAM,
256QAM
QPSK
Manually Specified
Modulation
QPSK, 16QAM,
32QAM, 64QAM,
128QAM,
256QAM
QPSK
NOTE
The ATPC attributes at both the ends of a radio link should be set to the same.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The related IF board must be added.
Precautions
l
In the case of the IF boards that are configured with the 1+1 protection, set only the ATPC
attributes of the main IF board.
The following procedure describes the configuration of ATPC parameters in the IF interface
configuration dialog box of the IF board. You can also set ATPC parameters in the following
configuration dialog boxes:
Create an XPIC working group
IF/ODU configuration
9-8
In the IF/ODU configuration dialog box, the ATPC adjustment thresholds cannot be
modified.
The transmit power of the two ODUs that are in an XPIC working group should be the
same if possible. Hence, each of the ATPC parameters (ATPC enable status, ATPC upper
threshold, ATPC lower threshold, and ATPC adjustment) should be set to the same value
for the IF boards that are in an XPIC working group.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
In the case of the Hybrid microwave, the AM switching is controlled through detection of
the change in the ATPC information and returned microwave message.
Procedure
Step 1 In the case of RTN 600 and RTN 900 V100R002 NEs.
1.
Select the IF board from the Object Tree in the NE Explorer. Choose Configuration > IF
Interface from the Function Tree.
2.
3.
NOTE
The IF0 board of the RTN 605 does not support the ATPC Automatic Threshold Enable Status.
4.
Click Apply.
Step 2 In the case of RTN 900 V1R1 NEs, see Configuring the IF Attributes of Microwave
Interfaces to take the details of configuration.
----End
Parameters
Parameter
Value Range
Default Value
Description
Enabled, Disabled
Disabled
Issue 02 (2010-09-24)
9-9
Parameter
Value Range
Default Value
Description
ATPC Upper
Threshold (dBm)
-20 to -75
-45
ATPC Lower
Threshold (dBm)
-35 to -90
-70
9-10
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
ATPC Automatic
Threshold Enable
Status
Enabled, Disabled
Enabled
NOTE
l Set ATPC parameters consistent at the two sides of a hop of microwave link.
l During commissioning, set ATPC Enable Status to Disabled to ensure that the transmit power is not
changed. After the commissioning, re-set the ATPC attributes.
l It is recommended that you disable the ATPC function for areas where fast fading is severe.
l To prevent that the RSL is lower than the receiver sensitivity caused by sudden fast fading, set the ATPC
lower threshold 10 dB or more higher than the receiver sensitivity.
l Generally, the ATPC upper threshold should be 20 dB to 30 dB higher than the ATPC lower threshold, and
must not be less than 15 dB. If the difference between the upper threshold and the lower threshold is big,
the number of ATPC adjustments can be reduced and the system load can also be reduced. If the difference
between the upper threshold and the lower threshold is small, the transmit power can be adjusted in a timely
manner and the interference to adjacent systems can be reduced.
l It is recommended that you set the ATPC adjustment step to 5 dB.
l In the case of hybrid radio links, the automatic ATPC threshold is recommended. In the case of SDH/PDH
radio links, the automatic ATPC threshold is recommended or you can make adjustment according to
multipath fading situation.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The IF boards and the ODUs to which the IF boards are connected must be created.
The XPIC Enabled parameter must be set to Enabled for the IF boards.
Issue 02 (2010-09-24)
9-11
Context
l
Relation with the 1+1 Protection Configuration: The two IF boards in an XPIC working
group cannot be configured into one 1+1 protection group, but the two IF boards in different
XPIC working groups can be configured into one 1+1 protection group. Therefore, the four
IF boards in two XPIC working groups can form two 1+1 protection groups.
Relation with the N+1 Protection: Each member of an XPIC working group can work as
the working channel or the protection channel of the N+1 protection.
Relation with the ATPC Feature: The transmit power of the two ODUs that are in an XPIC
working group should be the same if possible. Hence, each of the ATPC parameters (ATPC
enable status, ATPC upper threshold, ATPC lower threshold, and ATPC adjustment)
should be set to the same value for the IFX boards that are in an XPIC working group.
Procedure
Step 1 In the NE Explorer, select the NE and then choose Configuration > Link Configuration from
the Function Tree.
Step 2 Click the XPIC tab.
Step 3 Click New.
Step 4 In the dialog displayed box, Set the parameters for the XPIC workgroup.
For RTN 600 NEs:
NOTE
l When CCDP is applied to the STM-1 microwave links, the IFX/IFX2 boards must be installed and the
XPIC function must be enabled.
l An XPIC working group must be configured to ensure that the XPIC working group is configured with
the same working mode, transmission frequency, transmit power, and ATPC attributes.
l When the used ODUs support two T/R spacings, ensure that the two ODUs of an XPIC working group
adopt the same T/R spacing.
9-12
Issue 02 (2010-09-24)
Postrequisite
Generally, you do not need to configure the IF/ODU information after you configure an XPIC
workgroup. You, however, need to set the T/R spacing used by the ODU in the IF/ODU
Configuration tab page if the used ODU supports two T/R spacings.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 Select the target Hybrid IF board in the NE Explorer. Then, choose Configuration > Hybrid/
AM Configuration from the Function Tree.
Step 2 Click Query.
Step 3 Set the parameters related to the Hybrid/AM function.
Step 4 Optional: In the case of a card that supports the function of enabling E1 priority, click the
Advanced Attributes tab to set the minimum number of E1 services in different modulation
modes and check the bandwidth of data services.
Step 5 Click Apply.
----End
9-13
direction and search out the peer NE quickly. The HOP management integrates all functions in
one GUI, in which a user can perform all maintenance operations.
The Hop management is based on per link and the equipment at the two ends of a link is managed
at the same time. This ensures the consistency of configuration data between NEs at the two
ends.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The radio link must be created.
Procedure
Step 1 In the case of RTN 600 and RTN 900 V1R2 NEs.
9-14
1.
In the NE Explorer, select an NE and choose Configuration > Link Configuration from
the Function Tree.
2.
Issue 02 (2010-09-24)
3.
Select the IF board, right-click, and choose HOP Management from the shortcut menu.
4.
In the HOP Management window, choose Configuration > Link Configuration from
the Function Tree. Then, click the IF/ODU Configuration tab.
Double click the NE on the main topology, select the IF board in the NE panel, right-click,
and choose HOP Management from the shortcut menu.
2.
CAUTION
Modifying the value of Transmit Frequency interrupts the link. Exercise caution when you
perform this operation.
Step 4 Click Apply.
----End
Issue 02 (2010-09-24)
9-15
10
Issue 02 (2010-09-24)
10-1
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > Board 1+1 Protection from the
Function Tree.
Step 2 Click Query to query the configuration of the board 1+1 protection group.
----End
Prerequisite
l
Context
CAUTION
If the protection board is abnormal, services may be interrupted when you perform switching.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Board 1+1 Protection from the
Function Tree.
Step 2 Click Query to view the active board and the current working board.
Step 3 Select a 1+1 protection group and click Working/Protection Switching. The Confirm dialog
box is displayed.
Step 4 Click OK. The Operation Result dialog box is displayed.
Step 5 Click Close.
10-2
Issue 02 (2010-09-24)
Step 6 Click Query to refresh the switching status of the 1+1 protection group.
NOTE
In the case of SCC protection pair, you can query standby status of the SCC board.
----End
Issue 02 (2010-09-24)
10-3
11
Issue 02 (2010-09-24)
11-1
Main channel
MODEM
Transmitter
Transmitter
MODEM
Service
Service
MODEM
Transmitter
Transmitter
Standby channel
MODEM
Standby channel
In the case of the 1+1 HSB protection configuration, the main channel of the transmit end
transmits the RF signal to the opposite end. the main channel and standby channel of receive
end received the same RF signal respectively. When the main channel if faulty, the service unit
of receive end receives the signal from the standby channel. In this manner, the protection
switching is realized.
11.1.2 Availability
The 1+1 HSB feature requires the support of the applicable equipment and boards.
11-2
Issue 02 (2010-09-24)
Applicable Equipment
RTN 605
IF0A/IF0B
IF1A/IF1B
RTN 620
IFX
IFH2
Applicable Equipment
IFE2
IF1
RTN 910/950
IFU2
IFX2
The 18)2E1,3.5MHz,QPSK work mode does not support 1+1 HSB protection.
The configuration mode of 1+1 protection in one direction can only be 1+1 HSB, 1+1 FD,
or 1+1 SD. The configuration mode in one direction can be different from that in another
direction.
The two IF boards in an XPIC working group cannot be configured into one 1+1 HSB
protection group, but the two IF boards in different XPIC working groups can be configured
into one 1+1 HSB protection group. Therefore, the four IF boards in two XPIC working
groups can form two 1+1 HSB protection groups.
The IF boards in a 1+1 HSB protection group cannot be configured to provide the N+1
protection.
The radio link with the 1+1 HSB configuration can work only as the service sink of an
SNCP service pair, and cannot work as the working source or the protection source.
Issue 02 (2010-09-24)
11-3
Antenna
Main
ODU
Hybrid
coupler
Standby
ODU
Main Cross-connect
IF board
board
Service
board
Standby
IF board
The service board sends the received service signal to the cross-connect board.
2.
The cross-connect board transmits the service signal to both the main IF board and the
standby IF board.
3.
The main IF board and the standby IF board send the processed analog IF signal to the main
ODU and the standby ODU respectively.
4.
The main ODU transmits the RF signal to the hybrid coupler, which sends the RF signal
to the antenna. The standby ODU mutes (that is, the standby ODU does not send the RF
signal).
Figure 11-3 1+1 HSB realization principle (before the switching, in the receive direction)
Antenna
Hybrid
coupler
Main
ODU
Standby
ODU
11-4
Main Cross-connect
IF board
board
Service
board
Standby
IF board
Issue 02 (2010-09-24)
The hybrid coupler splits the RF signal received from the antenna to two signals and sends
them to both the main ODU and the standby ODU.
2.
The main ODU and the standby ODU send the processed analog IF signal to the main IF
board and the standby IF board respectively.
3.
The main IF board and the standby IF board send the service signal to the cross-connect
board.
4.
The cross-connect board selects the service signal from the main IF board and sends the
signal to the service board.
5.
The service board sends the service signal to the equipment at the opposite end.
Antenna
Hybrid
coupler
Main
ODU
Standby
ODU
Main Cross-connect
IF board
board
Service
board
Standby
IF board
Figure 11-5 1+1 HSB realization principle (after the switching, in the transmit direction)
Antenna
Hybrid
coupler
Main
ODU
Standby
ODU
Main Cross-connect
IF board
board
Service
board
Standby
IF board
Issue 02 (2010-09-24)
In the receive direction, the cross-connect board selects the service signal from the standby
IF board.
11-5
In the transmit direction, the standby ODU transmits the RF signal to the hybrid coupler,
which sends the RF signal to the antenna. The main ODU mutes (that is, the main ODU
does not send the RF signal).
NOTE
In the case of the RTN 605, the multiplexing sub-unit that is embedded in the IF unit replaces the cross-connect
unit of the IDU 620 to realize the dual fed and selective receiving function.
Main
IF board
Cross-connect
board
Service
board
Hybrid
coupler
Antenna
Standby
ODU
Standby
IF board
EMS6
board
11-6
1.
The service board multiplexes the received E1 service signal into the VC-4 and then sends
the VC-4 to the cross-connect board.
2.
The cross-connect board transmits the E1 service signal tin the VC-4 o the main IF board
and the standby IF board.
3.
The Ethernet service port of the main IF board is in LinkUp state, whereas the Ethernet
service port of the standby IF board is in LinkDown state. The Ethernet board EMS6
transmits the Ethernet service to the Ethernet service port of the main IF board through the
LAG function.
4.
The MUX unit of the main IF board multiplexes the E1 service signal and Ethernet service
signal into the Hybrid microwave frame. The MUX unit of the standby IF board multiplexes
the E1 service signal and Ethernet service signal into the non-standard Hybrid microwave
frame.
5.
The IF processing units of the main IF board and the standby IF board receive the Hybrid
microwave frame that is multiplexed by their corresponding IF board and modulate the
Hybrid microwave frame into the analog IF signal. Then, the IF processing units of the
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
main IF board and the standby IF board send the analog IF signal to the main ODU and the
standby ODU respectively.
6.
The main ODU transmits the RF signal to the hybrid coupler, which sends the RF signal
to the antenna. The standby ODU is muted (that is, the standby ODU does not transmit the
RF signal).
Figure 11-7 1+1 HSB realization principle (before the switching, in the receive direction)
Main
ODU
Main
IF board
Cross-connect
board
Service
board
Hybrid
coupler
Antenna
Standby
ODU
Standby
IF board
EMS6
board
The hybrid coupler splits the RF signal received from the antenna into two signals and
sends them to the main ODU and the standby ODU.
2.
The main ODU and the standby ODU send the processed analog IF signal to the main IF
board and the standby IF board respectively.
3.
The main IF board and the standby IF board demodulate the Hybrid frame from the IF
signal.
4.
The MUX units of the main IF board and the standby IF board receive the Hybrid frame
that is demultiplexed from their corresponding IF board and then separate the Hybrid frame
into the E1 service signal and Ethernet service signal.
5.
The E1 service signal is transmitted to the cross-connect board after being multiplexed into
the VC-4. The Ethernet service signal is transmitted to the Ethernet service port of the IF
board.
6.
The cross-connect board receives the E1 service signal from the main IF board and crossconnects the service signal to the corresponding service board.
7.
The EMS6 board receives the Ethernet service signal from the main IF board because the
Ethernet service port of the main IF board is in LinkUp state whereas the Ethernet service
port of the standby IF board is in LinkDown state.
Issue 02 (2010-09-24)
11-7
Main
IF board
Cross-connect
board
Service
board
Hybrid
coupler
Antenna
Standby
ODU
Standby
IF board
EMS6
board
Figure 11-9 1+1 HSB realization principle (after the switching, in the transmit direction)
Main
ODU
Main
IF board
Cross-connect
board
Service
board
Hybrid
coupler
Antenna
Standby
ODU
Standby
IF board
EMS6
board
11-8
Issue 02 (2010-09-24)
the standby IF board send the analog IF signal to the main ODU and the standby ODU. The
standby ODU transmits the RF signal to the hybrid coupler, which sends the RF signal to
the antenna. The main ODU is muted (that is, the main ODU does not transmit the RF
signal).
NOTE
l The two built-in IF units of theRTN 605 realize the functions of two IF boards of the RTN 620.
Procedure
Step 1 Plan the parameters relevant to the protection configuration.
l If the protection is in the revertive mode, set the WTR time to a value, which ranges from
five minutes to twelve minutes. It is recommended that you set the value to ten minutes.
l It is recommended that you enable the reverse switching. If reverse switching is enabled, and
both the main IF board and the standby IF board at the sink end report a service alarm, a
reverse switching occurs at the source end.
l In the case of the RTN 620, although the 1+1 HSB protection has no restriction on the slot
of the IF board, it is recommended that you install a pair of main and standby IF boards in
slots 5 and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot
6 is the main board).
----End
11.2 1+1 FD
1+1 FD is a configuration mode of 1+1 protection. In the 1+1 FD protection mode, the system
uses two channels that have a frequency spacing between them, to transmit and receive the same
service signal. The opposite end selects signals from the two received signals. With the 1+1 FD
protection, the impact of the fading on signal transmission is reduced.
11.2.1 Feature Description
This topic describes the 1+1 FD protection through its application.
11.2.2 Availability
The 1+1 FD feature requires the support of the applicable equipment and boards.
11.2.3 Relation with Other Features
The 1+1 FD protection is related to the microwave work mode, 1+1 HSB protection, 1+1 SD
protection, XPIC feature, N+1 protection, SNCP, and Hybrid microwave.
11.2.4 Realization Principle
The realization principle of the 1+1 FD for the Hybrid microwave is different from the realization
principle of the 1+1 FD for the SDH/PDH microwave.
11.2.5 Planning Guide
If there are sufficient spectrum resources, it is recommended that you adopt the 1+1 FD
protection configuration.
Issue 02 (2010-09-24)
11-9
Main channel
MODEM
Service
MODEM
Transmitter
Transmitter
F1
F1
F2
F2
Service
Transmitter
Transmitter
MODEM
MODEM
Standby channel
Standby channel
In the case of the 1+1 FD protection configuration, the main channel and the standby channel
of the receive end receive RF signals of different frequencies which from the transmit end
respectively. When the quality of the microwave signal received by the main antenna is degraded,
bit errors occur in the service on the main channel. The service unit then receives the service
signal from the standby channel to protect the service.
In addition, the 1+1 FD protection supports the 1+1 HSB protection switching.
11.2.2 Availability
The 1+1 FD feature requires the support of the applicable equipment and boards.
Table 11-3 Availability of the 1+1 FD feature
Applicable Board
Applicable Equipment
RTN 605
IF0A/IF0B
IF1A/IF1B
RTN 620
IFX
IFH2
11-10
Applicable Board
Applicable Equipment
IFE2
RTN 910/950
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
Applicable Board
Applicable Equipment
IF1
IFU2
IFX2
The configuration mode of 1+1 protection in one direction can only be 1+1 HSB, 1+1 FD,
or 1+1 SD. The configuration mode in one direction can be different from that in another
direction.
The two IF boards in an XPIC working group cannot be configured into one 1+1 FD
protection group, but the two IF boards in different XPIC working groups can be configured
into one 1+1 FD protection group. Therefore, the four IF boards in two XPIC working
groups can form two 1+1 FD protection groups.
The IF boards in a 1+1 FD protection group cannot be configured to provide the N+1
protection.
The radio link with the 1+1 FD configuration can work only as the service sink of an SNCP
service pair, and cannot work as the working source or the protection source.
Issue 02 (2010-09-24)
11-11
Main
ODU
Main Cross-connect
IF board
board
Service
board
f2
Antenna
Standby
ODU
Standby
IF board
The service board sends the received service signal to the cross-connect board.
2.
The cross-connect board transmits the service signal to both the main IF board and the
standby IF board.
3.
The main IF board and the standby IF board send the processed analog IF signal to the main
ODU and the standby ODU respectively.
4.
The main ODU and the standby ODU transmit RF signals at different frequencies and send
the signals to their respective antennas.
Figure 11-12 1+1 FD realization principle (before the switching, in the receive direction)
Antenna
Main
ODU
Main
IF board
Antenna
Standby
ODU
Standby
IF board
Cross-connect
board
Service
board
11-12
1.
The antennas receive RF signals and send the signals to their respective ODUs.
2.
The main ODU and the standby ODU send the processed analog IF signal to the main IF
board and the standby IF board respectively.
3.
The multiplex unit of the IF board sends the processed baseband signal to itself and to the
multiplex unit of its paired board.
4.
The main IF board and the standby IF board select their own baseband signal.
5.
The cross-connect board selects the service signal from the main IF board and sends the
signal to the service board.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
6.
The service board sends the service signal to the equipment at the opposite end.
Main
ODU
Main
IF board
Antenna
Standby
ODU
Standby
IF board
Cross-connect
board
Service
board
In the receive direction, the IF boards select their own service signal. The cross-connect
board selects the signal from the standby IF board.
Figure 11-14 1+1 FD HSM realization principle (after the switching, in the receive direction)
Antenna
Main
ODU
Main
IF board
Antenna
Standby
ODU
Standby
IF board
Cross-connect
board
Service
board
In the receive direction, the IF boards select the baseband signal from their own paired IF
board.
l The two built-in IF units of the IDU 605 2B/2F realize the functions of two IF boards of the IDU 620.
l The multiplexing sub-unit that is embedded in the IF unit of the IDU 605 2B/2F realizes the functions of
the cross-connect board of the IDU 620.
Issue 02 (2010-09-24)
11-13
Antenna
Main
IF board
Cross-connect
board
Service
board
f1
f2
Antenna
Standby
ODU
Standby
IF board
EMS6
board
11-14
1.
The service board multiplexes the received E1 service signal into the VC-4 and then sends
the VC-4 to the cross-connect board.
2.
The cross-connect board transmits the E1 service signal in the VC-4 to the main IF board
and the standby IF board.
3.
The Ethernet service port of the main IF board is in LinkUp state, whereas the Ethernet
service port of the standby IF board is in LinkDown state. The Ethernet board EMS6
transmits the Ethernet service to the Ethernet service port of the main IF board through the
LAG function.
4.
The MUX unit of the main IF board multiplexes the E1 service signal and Ethernet service
signal into the Hybrid microwave frame. The MUX unit of the standby IF board multiplexes
the E1 service signal and Ethernet service signal into the non-standard Hybrid microwave
frame.
5.
The IF processing units of the main IF board and the standby IF board receive the Hybrid
microwave frame that is multiplexed by the main IF board and modulate the Hybrid
microwave frame into the analog IF signal. Then, the IF processing units of the main IF
board and the standby IF board send the analog IF signal to the main ODU and the standby
ODU respectively.
6.
The main ODU transmits the RF signal at frequency f1 to the main antenna. The standby
ODU transmits the RF signal at frequency f2 to the standby antenna.
Issue 02 (2010-09-24)
Figure 11-16 1+1 FD realization principle (before the switching, in the receive direction)
Antenna
f1
Antenna
f2
Main
ODU
Standby
ODU
Main
IF board
Standby
IF board
Cross-connect
board
Service
board
EMS6
board
The antennas receive RF signals at different frequencies and send the signals to their
corresponding main ODU and standby ODU.
2.
The main ODU and the standby ODU send the processed analog IF signal to the main IF
board and the standby IF board respectively.
3.
The main IF board and the standby IF board demodulate the Hybrid frame from the IF
signal. The Hybrid microwave frame of the standby IF board is transmitted to the main IF
board through the protection bus.
4.
The MUX units of the main IF board and the standby IF board receive the Hybrid frame
that is demultiplexed from their corresponding IF board and then separate the Hybrid frame
into the E1 service signal and Ethernet service signal.
5.
The E1 service signal is transmitted to the cross-connect board after being multiplexed into
the VC-4. The Ethernet service signal is transmitted to the Ethernet service port of the IF
board.
6.
The cross-connect board receives the E1 service signal from the main IF board and crossconnects the service signal to the corresponding service board.
7.
The EMS6 board receives the Ethernet service signal from the main IF board because the
Ethernet service port of the main IF board is in LinkUp state whereas the Ethernet service
port of the standby IF board is in LinkDown state.
Issue 02 (2010-09-24)
11-15
Antenna
Main
IF board
Cross-connect
board
Service
board
f1
f2
Standby
ODU
Antenna
Standby
IF board
EMS6
board
Figure 11-18 1+1 FD HSB realization principle (after the switching, in the receive direction)
Antenna
f1
Antenna
f2
Main
ODU
Standby
ODU
Main
IF board
Standby
IF board
Cross-connect
board
Service
board
EMS6
board
11-16
Issue 02 (2010-09-24)
Figure 11-19 1+1 FD HSM realization principle (after the switching, in the receive direction)
Main
ODU
Antenna
f1
Antenna
f2
Standby
ODU
Main
IF board
Standby
IF board
Cross-connect
board
Service
board
EMS6
board
l The two built-in IF units of the IDU 605 2F realize the functions of two IF boards of the IDU 620.
Procedure
Step 1 Plan the parameters relevant to the protection configuration.
Issue 02 (2010-09-24)
11-17
l If the protection is in the revertive mode, set the WTR time to a value, which ranges from
five minutes to twelve minutes. It is recommended that you set the value to ten minutes.
l The spacing between the emission frequency of the main ODU and that of the standby ODU
should be greater than 56 MHz to prevent adjacent-channel interference.
l In the case of the RTN 620, a pair of main and standby IF boards must be installed in slots
5 and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot 6 is
the main board). In the case of the RTN 605 , the active/standby relation of the IF unit is
fixed. Hence, planning is not required.
----End
11.3 1+1 SD
1+1 SD is a configuration mode of 1+1 protection. In the 1+1 SD protection mode, the system
uses two antennas that have a space distance between them, to receive the same RF signal. The
equipment selects signals from the two received signals. With the 1+1 SD protection, the impact
of the fading on signal transmission is reduced.
11.3.1 Feature Description
This topic describes the 1+1 FD protection through its application.
11.3.2 Availability
The 1+1 SD feature requires the support of the applicable equipment and boards.
11.3.3 Relation with Other Features
The 1+1 SD protection is related to the microwave work mode, 1+1 HSB protection, 1+1 SD
protection, XPIC feature, N+1 protection, SNCP, and Hybrid microwave.
11.3.4 Realization Principle
The realization principle of the 1+1 SD for the Hybrid microwave is different from the realization
principle of the 1+1 SD for the SDH/PDH microwave.
11.3.5 Planning Guide
In the case of the radio links whose transmission performance is significantly affected by
multipath fading, it is recommended that you adopt the 1+1 SD protection configuration.
MODEM
Main channel
T2
T1
T2
T1
Transmitter
Transmitter
MODEM
Service
Service
MODEM
Transmitter
Transmitter
MODEM
T2
Standby channel
11-18
T1
Standby channel
Issue 02 (2010-09-24)
In the case of the 1+1 SD protection configuration, the two antennas at the receive end receive
the same RF signals from the transmit end. When the quality of the microwave signal that is
received by the main antenna is degraded, bit errors may occur in the service on the main channel.
Due to the space diversity, the signal that is received by the standby antenna may not be degraded.
In this case, the service unit receives the service from the standby receive channel to protect the
service.
In addition, the 1+1 SD protection supports the 1+1 HSB protection switching.
11.3.2 Availability
The 1+1 SD feature requires the support of the applicable equipment and boards.
Table 11-5 Availability of the 1+1 SD feature
Applicable Board
Applicable Equipment
RTN 605
IF0A/IF0B
IF1A/IF1B
RTN 620
IFX
IFH2
Applicable Equipment
IFE2
IF1
RTN 910/950
IFU2
IFX2
The configuration mode of 1+1 protection in one direction can only be 1+1 HSB, 1+1 FD,
or 1+1 SD. The configuration mode in one direction can be different from that in another
direction.
The two IF boards in an XPIC working group cannot be configured into one 1+1 SD
protection group, but the two IF boards in different XPIC working groups can be configured
Issue 02 (2010-09-24)
11-19
into one 1+1 SD protection group. Therefore, the four IF boards in two XPIC working
groups can form two 1+1 SD protection groups.
l
The IF boards in a 1+1 SD protection group cannot be configured to provide the N+1
protection.
The radio link with the 1+1 SD configuration can work only as the service sink of an SNCP
service pair, and cannot work as the working source or the protection source.
Antenna
Main
ODU
Standby
ODU
Main Cross-connect
board
IF board
Service
board
Standby
IF board
11-20
1.
The service board sends the received service signal to the cross-connect board.
2.
The cross-connect board transmits the service signal to both the main IF board and the
standby IF board.
3.
The main IF board and the standby IF board send the processed analog IF signal to the main
ODU and the standby ODU respectively.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
4.
The main ODU transmits the RF signal to the hybrid coupler, which sends the RF signal
to the antenna. The standby ODU mutes (that is, the standby ODU does not send the RF
signal).
Figure 11-22 1+1 SD realization principle (before the switching, in the receive direction)
Antenna
Main
ODU
Main
IF board
Antenna
Standby
ODU
Standby
IF board
Cross-connect
board
Service
board
The antennas receive RF signals and send the signals to their respective ODUs.
2.
The main ODU and the standby ODU send the processed analog IF signal to the main IF
board and the standby IF board respectively.
3.
The multiplex unit of the IF board sends the processed baseband signal to itself and to the
multiplex unit of its paired board.
4.
The main IF board and the standby IF board select their own baseband signal.
5.
The cross-connect board selects the service signal from the main IF board and sends the
signal to the service board.
6.
The service board sends the service signal to the equipment at the opposite end.
Main
ODU
Main
IF board
Antenna
Standby
ODU
Standby
IF board
Issue 02 (2010-09-24)
Cross-connect
board
Service
board
11-21
Figure 11-24 1+1 SD HSB realization principle (after the switching, in the transmit direction)
Antenna
Antenna
Main
ODU
Standby
ODU
Main Cross-connect
IF board
board
Service
board
Standby
IF board
In the receive direction, the IF boards select their own service signal. The cross-connect
board selects the signal from the standby IF board.
In the transmit direction, the standby ODU transmits the RF signal to the hybrid coupler,
which sends the RF signal to the antenna. The main ODU mutes (that is, the main ODU
does not send the RF signal).
Figure 11-25 1+1 SD HSM realization principle (after the switching, in the receive direction)
Antenna
Main
ODU
Main
IF board
Antenna
Standby
ODU
Standby
IF board
Cross-connect
board
Service
board
In the receive direction, the IF boards select the baseband signal from their own paired IF
board.
l The two built-in IF units of the IDU 605 2B/2F realize the functions of two IF boards of the IDU 620.
l The multiplexing sub-unit that is embedded in the IF unit of the IDU 605 2B/2F realizes the functions of
the cross-connect board of the IDU 620.
Issue 02 (2010-09-24)
Antenna
Main
ODU
Standby
ODU
Main
IF board
Standby
IF board
Cross-connect
board
Service
board
EMS6
board
The service board multiplexes the received E1 service signal into the VC-4 and then sends
the VC-4 to the cross-connect board.
2.
The cross-connect board transmits the E1 service signal in the VC-4 to the main IF board
and the standby IF board.
3.
The Ethernet service port of the main IF board is in LinkUp state, whereas the Ethernet
service port of the standby IF board is in LinkDown state. The Ethernet board EMS6
transmits the Ethernet service to the Ethernet service port of the main IF board through the
LAG function.
4.
The MUX unit of the main IF board multiplexes the E1 service signal and Ethernet service
signal into the Hybrid microwave frame. The MUX unit of the standby IF board multiplexes
the E1 service signal and Ethernet service signal into the non-standard Hybrid microwave
frame.
5.
The IF processing units of the main IF board and the standby IF board receive the Hybrid
microwave frame that is multiplexed by the main IF board and modulate the Hybrid
microwave frame into the analog IF signal. Then, the IF processing units of the main IF
board and the standby IF board send the analog IF signal to the main ODU and the standby
ODU respectively.
6.
The main ODU transmits the RF signal to the antenna. The standby ODU is muted (that is,
the standby ODU does not transmit the RF signal).
Issue 02 (2010-09-24)
11-23
Figure 11-27 1+1 SD realization principle (before the switching, in the receive direction)
Antenna
Antenna
Main
ODU
Standby
ODU
Main
IF board
Standby
IF board
Cross-connect
board
Service
board
EMS6
board
11-24
1.
The antennas receive RF signals and transmit the signals to their corresponding main ODU
and standby ODU.
2.
The main ODU and the standby ODU send the processed analog IF signal to the main IF
board and the standby IF board respectively.
3.
The main IF board and the standby IF board demodulate the IF signal into the Hybrid
microwave frame. The Hybrid microwave frame of the standby IF board is transmitted to
the main IF board through the protection bus.
4.
The MUX units of the main IF board and the standby IF board receive the Hybrid frame
that is demultiplexed from their corresponding IF board and then separate the Hybrid frame
into the E1 service signal and Ethernet service signal.
5.
The E1 service signal is transmitted to the cross-connect board after being multiplexed into
the VC-4. The Ethernet service signal is transmitted to the Ethernet service port of the IF
board.
6.
The cross-connect board receives the E1 service signal from the main IF board and crossconnects the service signal to the corresponding service board.
7.
The EMS6 board receives the Ethernet service signal from the main IF board because the
Ethernet service port of the main IF board is in LinkUp state whereas the Ethernet service
port of the standby IF board is in LinkDown state.
Issue 02 (2010-09-24)
Antenna
Main
ODU
Standby
ODU
Main
IF board
Standby
IF board
Cross-connect
board
Service
board
EMS6
board
Figure 11-29 1+1 SD HSB realization principle (after the switching, in the transmit direction)
Antenna
Antenna
Main
ODU
Standby
ODU
Main
IF board
Standby
IF board
Cross-connect
board
Service
board
EMS6
board
Issue 02 (2010-09-24)
11-25
Figure 11-30 1+1 SD HSM realization principle (after the switching, in the receive direction)
Main
ODU
Main
IF board
Cross-connect
board
Standby
ODU
Standby
IF board
EMS6
board
Antenna
Antenna
Service
board
The two built-in IF units of the IDU 605 2F realize the functions of two IF boards of the IDU 620.
Procedure
Step 1 Plan the parameters relevant to the protection configuration.
l There should be a height difference between the two antennas so that the dependence of the
diversity-received microwave signals on the space is minimized.
l If the protection is in the revertive mode, set the WTR time to a value, which ranges from
five minutes to twelve minutes. It is recommended that you set the value to ten minutes.
11-26
Issue 02 (2010-09-24)
l It is recommended that you enable the reverse switching. If reverse switching is enabled, and
both the main IF board and the standby IF board at the sink end report a service alarm, a
reverse switching occurs at the source end.
l In the case of the IDU 620, a pair of main and standby IF boards must be installed in slots 5
and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot 6 is
the main board). In the case of the IDU 605 2B/2F, the active/standby relation of the IF unit
is fixed. Hence, planning is not required.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The IF boards and their corresponding ODUs that form the IF 1+1 protection must be included
in the NE Panel.
Background Information
When a 1+0 service is converted into a 1+1 service by configuring the 1+1 protection, the original
services are not interrupted.
Precautions
The 18,2E1,3.5MHz,QPSK work mode does not support IF 1+1 protection.
Procedure
Step 1 In the case of RTN 600 and RTN 900 V100R002/V100R001C02 NEs.
1.
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1
Protection from the Function Tree.
2.
Click New. Set the parameters of the IF 1+1 protection group in the displaying dialog box.
3.
Click OK.
Step 2 In the case of RTN 900 V100R001C00 and RTN 900 V100R001C01 NEs.
1.
Issue 02 (2010-09-24)
Select the NE from the Object Tree in the NE Explorer. Choose Configuration >
Microwave Link Configuration from the Function Tree.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
11-27
2.
3.
Click New. Set the parameters of the IF 1+1 protection group in the displaying dialog box.
4.
Click OK.
----End
Postrequisite
l
In the case of the 1+1 HSB protection and 1+1 SD protection, you need to configure the
IF/ODU information of the active microwave link later. The standby microwave link
automatically copies the related information of the active microwave link except the
transmission status of the ODU.
In the case of the 1+1 FD protection, you need to configure the IF/ODU information of the
active microwave link and the information of the standby ODU later. The standby
microwave link automatically copies the IF information of the active microwave link.
NOTE
The default TX Status of an ODU is Unmute. Hence, you do not need to configure the TX Status of the standby
ODU after you create an IF 1+1 protection group.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > IF 1
+1 Protection from the Function Tree.
Step 2 Modify the parameters of the IF 1+1 protection.
11-28
Issue 02 (2010-09-24)
Parameters
Parameter
Value Range
Default Value
Description
Working Mode
HSB, FD, SD
HSB
Revertive Mode
Revertive, NonRevertive
Revertive
Issue 02 (2010-09-24)
11-29
Parameter
Value Range
Default Value
Description
WTR Time(s)
300 to 720
Enable, Disable
Enable Reverse
Switching
Enable
NOTE
Each of the following parameters should be set to the same value at the two ends of a microwave link: Working
Mode, Revertive Mode, WTR Time (s), and Enable Reverse Switching.
Postrequisite
l
In the case of the 1+1 HSB protection and 1+1 SD protection, you need to configure the
IF/ODU information of the active microwave link later. The standby microwave link
automatically copies the related information of the active microwave link except the
transmission status of the ODU.
In the case of the 1+1 FD protection, you need to configure the IF/ODU information of the
active microwave link and the information of the standby ODU later. The standby
microwave link automatically copies the IF information of the active microwave link.
NOTE
The default TX Status of an ODU is Unmute. Hence, you do not need to configure the TX Status of the standby
ODU after you create an IF 1+1 protection group.
11-30
Issue 02 (2010-09-24)
12
Issue 02 (2010-09-24)
12-1
Link aggregation allows multiple links that are attached to the same equipment to be aggregated
to form a link aggregation group (LAG) so that the bandwidths and availability of the links
increase. The aggregated links can be considered as a single logical link.
12-2
Issue 02 (2010-09-24)
Issue 02 (2010-09-24)
12-3
...
MST
RST
SPI
... ...
SPI
RST
MST
...
RS
MS
Capacity
Description
Issue 02 (2010-09-24)
B2SD raised on the equipment). External switching is performed after you issue an external
switching command, and thus brings a status change of the multiplex section. External switching
requests include lockout, forced switching, manual switching, exercise switching, and clear of
switching.
For MSP protection, the following switching requests can bring a status change of the multiplex
section. For their switching (or preemption) priorities, refer to Table 12-2.
NOTE
l The following table lists the switching priorities in a descending order, that is, LP_S (SF_P) has the highest
priority, and NR has the lowest. The requests of lockout, forced switching, manual switching and exercise
switching can be cleared as required.
l For LP_S (SF_P), the lockout of protection is available for only the span instead of the ring. LP_S and SF_P
have the same priority, and perform the same action on both the protocol and service. LP_S is triggered by
an external command, and SF_P is triggered by the protection channel failure in a four-fiber ring.
l The span switching has a higher priority than the ring switching.
l External commands are issued on the U2000. After a command is executed, the NE keeps this request until
the command is cleared or is preempted by another command of a higher priority. If there is a switching
request of a higher priority in the network, the external command cannot be executed, and thus the NE loses
this external command request.
Issue 02 (2010-09-24)
No.
Switching
Request
Description
Cause
LP_S(SF_P)
Span lockout
SF in the protection
channel of a fourfiber ring or the issue
of an external
command
FS_S
Forced switching of a
span
Issue of an external
command
FS_R
Forced switching of a
ring
Issue of an external
command
SF_S
SF of a span
SF in the working
channel of a span on
a four-fiber ring
SF_R
SF of a ring
SF in the working
channel of a fourfiber or two-fiber
ring
SD_P
SD of the protection
channel
SD in the protection
channel of a fourfiber or two-fiber
ring
SD_S
SD of a span
SD in the working
channel of a span on
a four-fiber ring
12-5
No.
Switching
Request
Description
Cause
SD_R
SD of a ring
SD in the working
channel of a fourfiber or two-fiber
ring
MS_S
Manual switching of
a span
Issue of an external
command
10
MS_R
Manual switching of
a ring
Issue of an external
command
11
WTR
Wait-to-restore
12
EXER_S
Exercise switching
of a span
Issue of an external
command
13
EXER_R
Exercise switching
of a ring
Issue of an external
command
14
RR_S
Reverse request of a
span
Reverse request
during a switching
15
RR_R
Reverse request of a
ring
Reverse request
during a switching
16
NR
No request
Principle
The transmit end of an SNCP service transmits two service sources, and the receive end checks
the service sources and selectively receives one. In this way, the service is protected. Hence,
SNCP is dual fed and selective receiving, which is similar to path protection (PP). The difference
between the SNCP and PP is about the specific implementation. When a service is selectively
received at the receive end, in path protection, the tributary board verifies the selective receiving.
In SNCP protection, the cross-connect board verifies the selective receiving. Hence, SNCP can
protect services on the line, and PP protects only services on the local tributary board.
Subnet-Related Concepts
The definitions in ITU-T G.805 are as follows:
l
12-6
Issue 02 (2010-09-24)
Implementation Principle
l
Service pair:
SNCP service pair is the service structure that consists of a working source, a protection
source, and a service sink. See Figure 12-2.
Figure 12-2 SNCP service pair
Working source
Protection
source
Service sink
SNCP service is from line to line. A service that is added to and dropped from the local
tributary board is not an SNCP service and an SNCP service pair cannot be generated. See
Figure 12-3.
Figure 12-3 SNCP service
SCC
Issue data/
Collect data
Line
board
Cross-connect
board
Intra-board
communication
Intra-board
communication
Line
board
Check point: In an SNCP service pair, the status of the sink node is not checked. The two
source nodes are two check points of the protection group. The line board of the
corresponding service source checks the status of a check point (SF, SD, or Normal).
Check point migration: An SNCP service pair usually has two check points. When a
network contains SNCP and MSP, several types of protection exists. Hence, some standby
check points are added accordingly. The line board enables the standby check point
Issue 02 (2010-09-24)
12-7
according to a command, and disables the original check point to realize migration of the
check point.
l
SNCP service number: It uniquely identifies a service pair. The SNCP service number
information is saved to the SCC, cross-connect board, and line board. The SNCP protection
switching on the line board and cross-connect board handles according to SNCP service
number. Hence, ensure that the SNCP service number on the line board is consistent with
that on the cross-connect board.
Condition of generating an SNCP service pair: The node attributes must contain or imply
the SNCP attribute. The service must across rings.
SCC board side: The SCC verifies the SNCP service, analyzes service route, and issues the
configuration data. The tasks contain setting check points, issuing SNCP service attribute
data, collecting the SNCP service status from the cross-connect board, and reporting the
SNCP service status.
Cross-connect board side: The cross-connect board collects the SNCP service status from
the line board, realizes the switching process of the service source, and reports changes of
the SNCP service status to the SCC.
Line board side: The line board mainly monitors the SNCP service and periodically reports
the service monitoring status to the cross-connect board. When the service status changes,
the line board notifies the cross-connect board of the change in real time.
Service flow: The flow of the SNCP service is the flow that the system configures the
service. Because of the special dual fed and selective receiving attribute, SNCP attribute
must be specified during service configuration.
12-8
Protection
Type
Revertive
Mode
Switching
Time
Default WTR
Time
Switching
Condition
(Trigger by
Any One
Condition)
SNCP
Revertive
<= 50 ms
600s
Non-revertive
<= 50 ms
R_LOS
R_LOF
AU_LOP
TU_LOP
MS_AIS
TU_AIS
HP_UNEQ
HP_TIM
B2_EXC
B3_EXC
B3_SD
BIP_EXC
BIP_SD
Issue 02 (2010-09-24)
You need to configure the line board whose rate is at the STM-1 for the N+1 protection.
Protection schemes:
Single-NE N+1 protection: When N is equal to or less than 2, an NE is required for the
protection.
Dual-NE N+1 protection: When N is equal to 3, two NEs are required for the protection.
NOTE
The single-NE N+1 protection and dual-NE N+1 protection shown are only schematic drawings. On the
real equipment, a dual-polarized antenna has only two interfaces. When multiple ODUs are connected,
every two ODUs are installed on a combiner and then the combiner is connected to the antenna.
ODU
IF
SL1
IF
PXC
SD1
PXC
SCC
Protect
ODU
Dual-Polarized
Antennas
ODU
ODU
ODU
ODU
Add/Drop
Services
F
A
N
IF
IF
SL1
IF
PXC
SD1
PXC
SCC
Add/Drop
Services
Line board: The rate level of the line board should be STM-1.
Others: The SCC board and the integrated power, cross-connect and clock (PXC) board
are required.
Issue 02 (2010-09-24)
12-9
IF
F
A
N
ODU
Secondary NE
IF
PXC
PXC
SD1
ODU
SCC
SD1
IF
SD1
IF
PXC
SD1
PXC
SCC
ODU
IF
F
A
N
Dual-Polarized
Antennas
Fiber
Interconnection
F
A
N
ODU
ODU
ODU
Add/Drop
Services
SD1
PXC
SCC
Fiber
Interconnection
ODU
Primary NE
IF
PXC
ODU
SD1
F
A
N
IF
SD1
IF
PXC
SD1
PXC
SCC
Add/Drop
Services
A standby channel is used to protect the services on three active channels. The IF 3+1
protection needs two OptiX RTN 620. One is the primary NE and the other is the secondary
NE. You need to configure the REG on the NEs and then create the IF 3+1 protection on
the primary NE.
Line board: The line board should support the interaction between the primary and
secondary NEs. Slot 4 is the optimum location for the line board. Two more line boards
are needed for adding and dropping services.
Others: The SCC board and the integrated power, cross-connect and clock (PXC) board
are required.
12-10
Issue 02 (2010-09-24)
...
Working
channel 1
Site B
Normal
service1
...
Working
channel N
Normal
service N
Normal
service N
Protection
channel
Extra
service
Extra
service
Protection switching
Site A
Normal
service 1
...
Normal
service N
Working
channel 1
Site B
Working
channel N
Protection
channel
Extra
service
Normal
service1
...
Normal
service N
Extra
service
You need to configure the line board whose rate is at the STM-1 for the N+1 protection.
Protection schemes:
Single-NE N+1 protection: When N is equal to or less than 2, an NE is required for the
protection.
Dual-NE N+1 protection: When N is equal to 3, two NEs are required for the protection.
NOTE
The single-NE N+1 protection and dual-NE N+1 protection shown are only schematic drawings. On the
real equipment, a dual-polarized antenna has only two interfaces. When multiple ODUs are connected,
every two ODUs are installed on a combiner and then the combiner is connected to the antenna.
Issue 02 (2010-09-24)
12-11
Protect
IF
F
A
N
IF
SL1
IF
PXC
SD1
PXC
SCC
Protect
ODU
Dual-Polarized
Antennas
ODU
ODU
ODU
ODU
F
A
N
Add/Drop
Services
IF
IF
SL1
IF
PXC
SD1
PXC
SCC
Add/Drop
Services
Line board: The rate level of the line board should be STM-1.
Others: The SCC board and the integrated power, cross-connect and clock (PXC) board
are required.
ODU
IF
PXC
PXC
SD1
ODU
SD1
SCC
IF
SD1
IF
PXC
SD1
PXC
SCC
ODU
IF
F
A
N
Dual-Polarized
Antennas
Fiber
Interconnection
F
A
N
ODU
Secondary NE
ODU
ODU
Add/Drop
Services
SD1
PXC
SCC
Fiber
Interconnection
ODU
Primary NE
IF
PXC
ODU
SD1
F
A
N
IF
SD1
IF
PXC
SD1
PXC
SCC
Add/Drop
Services
12-12
A standby channel is used to protect the services on three active channels. The IF 3+1
protection needs two OptiX RTN 620. One is the primary NE and the other is the secondary
NE. You need to configure the REG on the NEs and then create the IF 3+1 protection on
the primary NE.
Issue 02 (2010-09-24)
Line board: The line board should support the interaction between the primary and
secondary NEs. Slot 4 is the optimum location for the line board. Two more line boards
are needed for adding and dropping services.
Others: The SCC board and the integrated power, cross-connect and clock (PXC) board
are required.
12.2.2 Availability
The N+1 protection feature requires the support of the applicable equipment and boards.
Table 12-4 Availability of the N+1 protection feature
Applicable Board
Applicable Equipment
IF1A/IF1B
RTN 620
IFX
Applicable Equipment
IFU2
RTN 910/950
IFX2
NOTE
The following describes the switching principle of the 2+1 protection as an example.
Issue 02 (2010-09-24)
12-13
5-IF1B-1
15-ODU
6-SL1-1
7-IF1B-1
17-ODU
4-SD1-2
8-IF1B-1
18-ODU
Working channel
Protection channel
5-IF1B-1
15-ODU
6-SL1-1
7-IF1B-1
17-ODU
4-SD1-2
8-IF1B-1
18-ODU
Working channel
Protection channel
In this example, port 1 of the IF1B board in slot 5, port 1 of the IF1B board in slot 7, and port 1
of the IF1B board in slot 8 form a 2+1 protection group.
When a working channel fails, the switching principle of the 2+1 protection configuration is as
follows:
12-14
1.
Before the switching, the NE sends and receives normal traffic signals on the working
channel, and sends and receives extra traffic signals on the protection channel.
2.
On detecting that the signals on a working channel fail (for example, the IF1B board in slot
5 detects that an MW_LOF alarm is generated on port 1), the IF board notifies the SCC
board.
3.
The SCC board controls the PXC board to realize the transmission of the working traffic
signals (port 1 of the SD1 board in slot 4) on the protection channel (port 1 of the IF1B
board in slot 8). The SCC board also interacts with the NE on the opposite side through
byte K to enable the NE on the opposite side to perform synchronous switching.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
NOTE
The interaction of byte K between NEs complies with the N+1 protection protocol, which is similar to the MSP
protocol. For details, see Realization Principle of 1:N Linear MSP.
The following describes the switching principle of the 3+1 protection as an example.
Figure 12-7 Realization principle of the 3+1 protection (before the switching)
Primary NE
PXC
6-SD1-1
5-IF1B-1
15-ODU
6-SD1-2
7-IF1B-1
17-ODU
8-SD1-1
4-SD1-1
8-SD1-2
4-SD1-2
Secondary NE
PXC
4-SD1-1
5-IF1B-1
15-ODU
4-SD1-2
7-IF1B-1
17-ODU
Working channel
Issue 02 (2010-09-24)
Protection channel
12-15
Figure 12-8 Realization principle of the 3+1 protection (after the switching)
Primary NE
PXC
6-SD1-1
5-IF1B-1
15-ODU
6-SD1-2
7-IF1B-1
17-ODU
8-SD1-1
4-SD1-1
8-SD1-2
4-SD1-2
Secondary NE
PXC
4-SD1-1
5-IF1B-1
15-ODU
4-SD1-2
7-IF1B-1
17-ODU
Working channel
Protection channel
In this example, port 1 of the IF1B board in slot 5 of the primary NE, port 1 of the IF1B board
in slot 7 of the primary NE, and ports 1 and 2 of the SD1 board in slot 4 of the primary NE form
a 3+1 protection group. An REG is established between port 1 of the IF1B board in slot 5 of the
secondary NE and port 1 of the SD1 board in slot 4 of the secondary NE. Another REG is
established between port 1 of the IF1B board in slot 7 of the secondary NE and port 2 of the
SD1 board in slot 4 of the secondary NE.
When a working channel fails, the switching principle of the 3+1 protection configuration is as
follows:
12-16
1.
Before the switching, the primary NE sends and receives normal traffic signals on the
working channel, and sends and receives extra traffic signals on the protection channel.
The secondary NE works as an REG to transparently transmit VC signals and multiplex
section overheads.
2.
On detecting that the signals on a working channel fail (for example, the IF1B board in slot
5 detects that an MW_LOF alarm is generated on port 1), an IF board of the secondary NE
inserts the MS_AIS alarm and transparently transmits the multiplex section overheads and
VC signals to port 1 of the SD1 board in slot 4 of the primary NE through port 1 of the SD1
board in slot 4 of the secondary NE.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
3.
On detecting the MS_AIS alarm, the SD1 board in slot 4 of the primary NE reports the
alarm to the SCC board.
4.
The SCC board controls the PXC board to realize the transmission of the working traffic
signals (port 1 of the SD1 board in slot 8) on the protection channel (port 2 of the SD1
board in slot 4). The SCC board also interacts with the NE on the opposite side through
byte K to enable the NE on the opposite side to perform synchronous switching. When the
primary NE exchanges byte K with the NE on the opposite side, the secondary NE always
transparently transmits byte K because byte K belongs to the multiplex section overheads.
NOTE
l In this example, the working channels of the secondary NE fail. If the working channels of the primary NE
fail, the IF board directly reports the alarm to the SCC board to trigger the protection switching.
l The REG formed by the secondary NE is slightly different from an ordinary REG. The REG formed by the
secondary NE does not insert an AU_AIS alarm but inserts an MS_AIS alarm to trigger the N+1 protection
switching when an MW_LOF alarm or a regenerator section alarm (for example, R_LOS, R_LOC, and
R_LOF) is generated.
l The interaction of byte K between NEs complies with the N+1 protection protocol, which is similar to the
MSP protocol. For details, see Realization Principle of 1:N Linear MSP.
Issue 02 (2010-09-24)
12-17
Create an N+1
protection group
Is the 3+1
protection mode
used?
No
Yes
2
Create REGs
End
Table 12-6 Description of the configuration flow of the N+1 protection mode
Number
Description
The members of an N+1 protection group cannot be configured with the 1+1 protection.
Each member of an XPIC working group can work as the working channel or the protection
channel of the N+1 protection.
The radio link with the N+1 protection configuration can work only as the service sink of
an SNCP service pair, and cannot work as the working source or the protection source.
12-18
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The IF boards and the ODUs to which the IF boards are connected must be created.
The STM-1 optical/electrical interface board that is connected to the primary NE must be created.
The IF boards must work in the STM-1 mode.
Context
In the case of the 3+1 protection, you need to two configure REGs for the secondary NE.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Protection
Configuration > REG Configuration from the Function Tree.
Step 2 Click Create.
The system displays the Create REG dialog box.
Step 3 Set the SD Enabled parameter.
Step 4 Set the slot mapping relation.
1.
2.
In Select Mapping Mode, select the line port to which the west line corresponds and click
.
3.
4.
In Select Mapping Mode, select the line port to which the east line corresponds and click
.
Issue 02 (2010-09-24)
12-19
----End
12-20
Issue 02 (2010-09-24)
Parameters
Parameter
Value Range
Default Value
Description
SD Enabled
Enabled, Disabled
Enabled
Slot Mapping
Relation
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The IF boards and the ODUs to which the IF boards are connected must be created.
The STM-1 optical/electrical interface boards (only in the case of the primary NE that is to be
configured with 3+1 protection) must be created.
The IF boards must work in the STM-1 mode.
Background Information
When an N+0 service is converted into an N+1 service by configuring the N+1 protection, the
original services are not interrupted.
NOTE
Procedure
Step 1 Select a navigation path:
l In the NE Explorer, select the NE from the Function Tree and then choose Configuration >
Link Configuration from the Function Tree. Click the N+1 Protection tab.
l In the NE Explorer, select the NE from the Object Tree and then choose Configuration >
Protection Configuration > N+1 Protection from the Function Tree.
Step 2 Click Create.
The system displays the Create an N+1 Protection Group dialog box.
Step 3 Set the attributes of the N+1 protection group.
Issue 02 (2010-09-24)
12-21
2.
In Select Mapping Mode, select the line port to which a working channel corresponds and
click
3.
Repeat Step 4.2 to select the line ports to which other working channels correspond.
4.
5.
In Select Mapping Mode, select the line port to which the protection channel corresponds
.
and click
NOTE
l Set the WTR time to a value, which ranges from five minutes to twelve minutes. It is recommended that
you set the value to ten minutes.
l It is recommended that you use SD as a switching condition.
Parameters
Parameter
Value Range
Default Value
Description
WTR Time(s)
300 to 720
600
12-22
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
SD enable
Enabled, Disabled
Enabled
Slot Mapping
Relation
NOTE
The N+1 protection groups of the equipment at both ends must have the same attributes.
Prerequisite
l
Context
After maintaining the equipment, enable the N+1 protection control protocol, to restore the
normal protection function of the equipment.
Procedure
Step 1 In the NE Explorer, select Link Configuration from the Function Tree, click the N+1
Protection tab. Select the N+1 protection group and click Start Protocol.
Step 2 A prompt is displayed indicating that the operation is successful. Click OK.
Step 3 Click Query and the current protocol status is displayed.
----End
Issue 02 (2010-09-24)
12-23
Postrequisite
NOTE
Before maintaining the equipment, disable the N+1 protection control protocol, to avoid the protection
switching caused by the equipment maintenance.
In the NE Explorer, select Configuration > N+1 Protection from the Function Tree. Select
the IF N+1 protection group and click Stop Protocol.
Prerequisite
l
Context
The external switching commands are as follows: clear switching, lockout of protection, forced
switching to protection, manual switching to protection, and exercise switching.
l
Clear switching: This command can be used to clear the forced switching, manual
switching, lockout of switching, and exercise switching.
Lockout of protection: No service, including the normal and extra services, is allowed to
be switched from the working channel to the protection channel. If the service is already
switched to the protection channel, the command will force it back to the working channel
even if the working channel is abnormal.
CAUTION
Therefore, if the protection switching already occurs, running this command will interrupt
services.
12-24
Forced switching to protection: That means to forcibly switch the services from the working
channel to protection channel regardless of the state of the protection channel. After the
forced switching, the system will be always in the switching status, and will not be switched
back to the working channel unless manual interference.
Manual switching to protection: That means to switch the services from the working
channel to protection channel. If the protection channel is normal, the switching will occur.
If the protection channel fails or is satisfying a switching of higher priority, the manual
switching will not occur. After the manual switching, the system will not be switched back
to the working channel unless manual interference.
Exercise switching: This command is used to test whether the switching protocol works
normally. Actually, no switching occurs and the service will not be affected
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
Procedure
Step 1 Select the NE to be queried. In the NE Explorer, choose Configuration > Link
Configuration from the Function Tree. In the right pane, click the N+1 Protection tab.
Step 2 In Slot Mapping Relation, right-click the working or protection unit and choose corresponding
external switching command from the shortcut menu.
Step 3 In the prompt displayed, click OK.
Step 4 Click Query to query the switching status.
----End
Issue 02 (2010-09-24)
12-25
Working
channel
NE B
Protection
channel
Protection switching
NE A
Working
channel
NE B
Protection
channel
12-26
Issue 02 (2010-09-24)
...
Working
channel 1
NE B
Normal
service1
...
Working
channel N
Normal
service N
Normal
service N
Protection
channel
Extra
service
Extra
service
Protection switching
NE A
Normal
service 1
...
Normal
service N
Extra
service
Working
channel 1
NE B
Working
channel N
Protection
channel
Normal
service1
...
Normal
service N
Extra
service
Dedicated protection
Dedicated protection refers to the case that one working channel exclusively uses one
protection channel. The dedicated protection channel cannot carry extra services. The 1+1
protection is the dedicated protection.
Shared protection
Shared protection refers to the case that one or more working channels share one protection
channel. The shared protection channel can carry extra services. The 1:N (including the
1:1) protection is the shared protection.
In terms of the switching mode, the linear MSP is classified into the single-ended switching and
the dual-ended switching.
l
Issue 02 (2010-09-24)
Single-ended switching
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
12-27
In the single-ended switching mode, the switching occurs only at one end and the state of
the other end remains unchanged.
l
Dual-ended switching
In the dual-ended switching mode, the switching occurs at both ends at the same time.
In terms of the revertive mode, the linear MSP is classified into the revertive mode and the nonrevertive mode.
l
Revertive mode
When an NE is in the switching state, the NE releases the switching and enables the former
working channel to return to the normal state some time after the former working channel
is restored to normal. The period from the time the former working channel is restored to
normal to the time the NE releases the switching is called the wait to restore (WTR) time.
To prevent frequent switching events due to an unstable working channel, it is
recommended that you set the WTR time to five to twelve minutes.
Non-revertive mode
When an NE is in the switching state, the NE keeps the current state unchanged unless
another switching occurs even though the former working channel is restored to normal.
Hence, the linear MSP is classified into the following eight modes:
l
The OptiX RTN 600/900 supports the following five linear MSP modes:
l
The 1:N dual-ended revertive mode is switched according to the MSP protocol of the linear MSP
described in ITU-T G.841. The 1+1 dual-ended mode uses the protocol that is compatible with
the 1:N mode. The switching in the 1+1 single-ended mode does not use protocols.
NOTE
Huawei realizes two multiplex section protocols, the new protocol and the restructure protocol. The new protocol
is more mature and the restructure protocol is in better compliance with the standards.
12.3.2 Availability
The linear MSP solution requires the support of the applicable equipment and boards.
12-28
Issue 02 (2010-09-24)
Applicable Equipment
SL4
RTN 620
SL1/SD1
RTN 610/620
SLE/SDE
Applicable Equipment
SL1D
RTN 910/950
The following describes the switching principle of the 1+1 linear MSP. The switching triggered by the signal
failure on the working channel is provided as an example.
Figure 12-12 Realization principle of 1+1 linear MSP (before the switching)
NE B
Working
NE A
Protection
Working
Protection
Normal service
Issue 02 (2010-09-24)
12-29
Figure 12-13 Realization principle of 1+1 linear MSP (after the switching, in the single-ended
mode)
NE B
Working
NE A
Protection
Working
Protection
Normal service
Figure 12-14 Realization principle of 1+1 linear MSP (after the switching, in the dual-ended
mode)
NE B
Working
NE A
Protection
Working
Protection
Normal service
When the signal on the working channel fails, the switching principle in the single-ended mode
is as follows:
1.
Before the switching, the source sends traffic signals to both the working channel and the
protection channel. The sink selects the traffic signals from the working channel.
2.
On detecting that the signal on the working channel fails, the line board at the sink in a
certain direction (NE A) reports the event to the SCC board.
3.
After confirming that the signal on the working channel fails and that the signal on the
protection channel is normal, the SCC board enables the cross-connect board to complete
the cross-connection between the protection channel and the service sink.
When the signal on the working channel fails, the switching principle in the dual-ended mode
is as follows:
12-30
Issue 02 (2010-09-24)
1.
Before the switching, the source sends traffic signals to both the working channel and the
protection channel. The sink selects the traffic signals from the working channel.
2.
On detecting that the signal on the working channel fails, the sink in a certain direction (NE
A) sends byte K to the source (NE B) on the protection channel (the request type is "signal
fail").
3.
NE B sends byte K to NE A also on the protection channel (the request type is "reverse
request").
4.
5.
The following describes the switching principle of the 1:N linear MSP. The 1:1 linear MSP switching triggered
by the signal failure on the working channel is provided as an example.
Figure 12-15 Realization principle of 1:1 linear MSP (before the switching)
NE B
Working
NE A
Protection
Working
Protection
Normal service
Extra service
Figure 12-16 Realization principle of 1:1 linear MSP (after the switching)
NE B
Working
NE A
Protection
Working
Protection
Normal service
Issue 02 (2010-09-24)
Extra service
12-31
When the signal on the working channel fails, the switching principle in the 1:1 mode is as
follows:
1.
Before the switching, both the source and the sink send and receive normal traffic signals
on the working channel, and send and receive extra traffic signals on the protection channel.
2.
On detecting that the signal on the working channel fails, the sink in a certain direction (NE
A) sends byte K to the source (NE B) on the protection channel (the request type is "signal
fail").
3.
NE B performs a bridge of the normal traffic signals onto the protection channel and sends
byte K to NE A on the protection channel (the request type is "reverse request").
4.
NE A receives the normal traffic signals from the protection channel and performs a bridge
of the normal traffic signals onto the protection channel.
5.
Actually, to speed up the switching, NE B does not perform a service bridge in Step 3 but performs it in Step 5.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The boards where the working unit and the protection unit are located must be configured.
Background Information
When an unprotected service is converted into a linear MSP service by configuring the linear
MSP, the original services are not interrupted.
12-32
Issue 02 (2010-09-24)
WARNING
l The line that is configured with the linear MSP can work only as the sink of an SNCP service
pair, and cannot work as the working source or the protection source.
l The line that is configured with the linear MSP cannot be configured to form an MSP ring.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Protection
Configuration > Linear MS from the Function Tree.
Step 2 Click Create.
The system displays the Create a Linear Multiplex Section dialog box.
Step 3 Set the attributes of the linear MSP group.
NOTE
When Protection Type is set to 1:N Protection. A prompt is displayed, indicating that the service that is
configured in the protection timeslot is changed to an extra service.
2.
In Select Mapping Mode, select the line port to which the working channel corresponds
and click
3.
4.
In Select Mapping Mode, select the line port to which the protection channel corresponds
and click
Issue 02 (2010-09-24)
12-33
NOTE
l It is recommended that you select the 1+1 single-ended non-revertive mode or the 1:1 dual-ended revertive
mode, depending on the requirements.
l In the 1+1 single-ended non-revertive mode, the realization is simple and the switching speed is high.
In addition, the equipment at both sides need not be interconnected.
l In the 1:N dual-ended revertive mode, extra services can be transmitted.
l Plan the parameters relevant to the protection configuration.
l The MS protocols used at both sides must be consistent. It is recommended that you adopt the new
protocol when both sides use the OptiX equipment.
l It is recommended that the working channel uses the line ports of one line board and the protection
channel uses those of another line board to prevent the situation in which the failure of a line board
causes the protection to fail.
l If the protection is in the revertive mode, set the WTR time to a value, which ranges from five minutes
to twelve minutes. It is recommended that you set the value to ten minutes.
l It is recommended that you use SD as a switching condition.
12-34
Issue 02 (2010-09-24)
Parameters
Parameter
Value Range
Default Value
Description
Protection Type
1+1 Protection
Switching Mode
l Single-Ended
l Single-Ended
Switching, DualSwitching (1+1
Ended Switching
protection)
(1+1 protection) l Dual-Ended
l Dual-Ended
Switching (1:N
Switching (1:N
protection)
protection)
Revertive Mode
l Non-Revertive,
Revertive (1+1
protection)
l Revertive (1:N
protection)
l Non-Revertive
(1+1 protection)
l Revertive (1:N
protection)
WTR Time(s)
300 to 720
600
SD enable
Enabled, Disabled
Enabled
Issue 02 (2010-09-24)
12-35
Parameter
Value Range
Default Value
Description
Protocol Type
New Protocol,
Restructure Protocol
New Protocol
Slot Mapping
Relation
NOTE
Ensure that the MSP groups of the equipment at both ends of the linear multiplex section are set with the same
attributes.
Postrequisite
l
In the case of the 1:N linear MSP, you need to configure bidirectional cross-connections
between the services and the working channels later. If extra services need to be transmitted,
it is necessary to configure bidirectional cross-connections between the extra services and
the protection channels.
In the case of the 1+1 linear MSP, you need to configure unidirectional cross-connections
between the services and the protection channels, in addition to configuring the
bidirectional cross-connections between the services and the working channels.
12-36
Issue 02 (2010-09-24)
Prerequisite
l
Context
The external switching for MSP protection includes lockout, forced switching, manual
switching, and exercise switching.
l
In the event of lockout of switching, the switching request for the port is denied, but the
reversion of switching is allowed. Regardless of the status of the working and protection
channels, the services are locked in the working channel.
Forced switching has a higher priority than signal failure and signal degrade, on the
protection section. This switching is performed regardless of the protection channel state,
unless the protection channel is satisfying a higher priority bridging request.
Manual switching has a lower priority than signal failure and signal degrade, on the
protection section. The manual switching request is valid only when there is no signal
failure or signal degrade on the protection section.
The exercise switching is used to test the APS protocol. In fact services are not switched
to the protection section, and only the calculation result of the protocol is displayed.
CAUTION
Switching other than the exercise switching may interrupt services.
Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > Protection Configuration >
Linear MS from the Function Tree.
Step 2 In the slot mapping table, right-click a direction and choose a switching or lockout option from
the shortcut menu. Click Close in the Operation Result dialog box.
NOTE
----End
Prerequisite
l
Issue 02 (2010-09-24)
12-37
Context
CAUTION
Setting an MS node number may affect the existing service.
Procedure
l
Double-click Local Node, West Node, and East Node respectively and enter a new value.
NOTE
For the rules of setting an MS node number, see 12.4.3.1 Configuring the Ring MSP.
Click Apply. In the Confirm dialog box, click Yes. In the Operation Result dialog box,
click Close.
----End
Issue 02 (2010-09-24)
East
East
West
STM-4 two-fiber
bidirectional MSP ring
NE B
East
NE D
West
West
East
NE C
Protection swicthing
NE A
West
East
East
West
NE B
STM-4 two-fiber
bidirectional MSP ring
NE D
West
East
East
West
NE C
Service between NE A and NE C
The two-fiber bidirectional MSP ring is applicable to the ring on which the services are
distributed. When the services are converged on the ring, the maximum service capacity of this
ring is STM-N/2. When the services are evenly distributed on the ring, the maximum service
capacity of this ring is M x STM-N/2, where M indicates the number of nodes on the ring.
Protection Type
The two-fiber bidirectional ring MSP has the following characteristics in terms of the protection
type:
l
A ring network uses two fibers. One fiber is used to receive signals and the other fiber is
used to transmit signals.
The normal services between different nodes share the protection channel. The protection
channel can be used to transfer extra services. In a two-fiber bidirectional MSP ring, the
Issue 02 (2010-09-24)
12-39
first half of the VC-4s are the working channels and the second half of the VC-4s are the
protection channels.
l
The two-fiber bidirectional ring MSP adopts the revertive mode. That is, an NE that is in
the switching state releases the switching and enables the former working channel to return
to the normal state some time after the former working channel is restored to normal. The
period from the time the former working channel is restored to normal to the time the NE
releases the switching is called the wait-to-restore (WTR) time. To prevent frequent
switching events due to an unstable working channel, it is recommended that you set the
WTR time to five to twelve minutes.
12.4.2 Availability
The two-fiber bidirectional ring MSP needs the support of the corresponding equipment and
boards.
Table 12-9 Availability of the two-fiber bidirectional ring MSP
Feature
Applicable Board
Applicable Equipment
IDU 620
The following section describes the switching principle of the two-fiber bidirectional ring MSP. The protection
switching triggered by a unidirectional signal failure on a two-fiber bidirectional MSP ring formed by four NEs
is provided as an example.
Figure 12-18 Realization principle of the two-fiber bidirectional ring MSP (before the
switching)
NE A
#1 VC-4
West
East
East
West
STM-4 two-fiber
bidirectional MSP ring
NE B
East
NE D
West
West
East
NE C
Service between NE A and NE C
12-40
Issue 02 (2010-09-24)
Figure 12-19 Realization principle of the two-fiber bidirectional ring MSP (after the switching)
NE A
West
East
#3VC-4
West
NE B
East
STM-4 two-fiber
bidirectional MSP ring
#3 VC-4
East
#1 VC-4
NE D
West
East
West
NE C
Service from NE A to NE C
When the signal on the working channel fails, the switching principle of the two-fiber
bidirectional ring MSP is as follows:
1.
When the network is in the normal state, the service between NE A and NE C is transmitted
in certain timeslots of the first VC-4 in the line. The service route is shown in Figure
12-18.
2.
On detecting that the signal on the working channel in the receive direction fails, the west
line board of NE B sends byte K (the request type being SF_R and the state being MS-RDI)
on the short path (NE B -> NE A) and also sends byte K (the request type being SF_R and
the state being idle) on the long path (NE B -> NE C -> NE D -> NE A).
3.
4.
After receiving byte K on the short path, the east line board of NE A sends byte K (the
request type being RR_R and the state being idle) on the short path (NE A -> NE B) and
also sends byte K (the request type being SF_R and the state being idle) on the long path
(NE A -> NE D -> NE C -> NE B).
5.
After receiving byte K on the long path, the west line board of NE A sends byte K (the
request type being RR_R and the state being the bridging and switching) on the short path
(NE A -> NE B) and also sends byte K (the request type being SF_R and the state being
the bridging and switching) on the long path (NE A -> NE D -> NE C -> NE B).
NE A enters the east switching state. That is, NE A receives the services that should be
received from the east working channels in normal cases from the west protection channels,
and transmits the services that should be transmitted to the east working channels in normal
cases to the west protection channels. In the case of the service between NE A and NE C,
NE A transmits the service to the first VC-4 path in the east direction in the normal state,
but transmits the service to the third VC-4 path in the west direction in the east switching
state.
6.
After receiving byte K (the request type being SF_R and the state being the bridging and
switching) sent from NE A to NE B, NE C and NE D enter the pass-through state. When
NE C and NE D pass through byte K, NE C and NE D also pass through the information
carried on the protection channels.
7.
After receiving byte K (the request type being SF_R and the state being the bridging and
switching) sent from NE A, NE B sends byte K (the request type being SF_R and the state
being the bridging and switching) on the long path (NE B -> NE C -> NE D -> NE A).
Issue 02 (2010-09-24)
12-41
NE B enters the west switching state. That is, NE A receives the services that should be
received from the west working channels in normal cases from the east protection channels,
and transmits the services that should be transmitted to the west working channels in normal
cases to the east protection channels. In the case of the service between NE A and NE C,
NE B receives the service from the first VC-4 path in the west direction and transmits the
service to the first VC-4 in the east direction in the normal state, but receives the service
from the third VC-4 path in the east direction and transmits the service to the first VC-4
path in the east direction in the west switching state.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The boards where the working unit and the protection unit are located must be configured.
Background Information
When an unprotected service is converted into a ring MSP service by configuring the ring MSP,
the original services are not interrupted.
NOTE
l The line of a two-fiber bidirectional MSP ring cannot be configured with the linear MSP.
l The line of a two-fiber bidirectional MSP ring can work only as the sink of an SNCP service pair, and cannot
work as the working source or the protection source.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Protection
Configuration > Ring MS from the Function Tree.
Step 2 Click Create.
A prompt is displayed, indicating that the service that is configured in the protection timeslot is
changed to an extra service.
Step 3 Click OK.
The system displays the Create a Ring Multiplex Section dialog box.
Step 4 Set the attributes of the ring MSP protection group according to the networking plan.
Step 5 Set the slot mapping relation.
12-42
1.
Set Local Node, West Node, and East Node according to the networking plan.
2.
Issue 02 (2010-09-24)
3.
In Select Mapping Mode, select the line port to which the working channel corresponds
and click
4.
5.
In Select Mapping Mode, select the line port to which the protection channel corresponds
and click
NOTE
12-43
Parameters
Parameter
Value Range
Default Value
Description
Level
Protection Type
Local Node
0 to 15
West Node
0 to 15
East Node
0 to 15
WTR Time(s)
300 to 720
600
SD enable
Enabled, Disabled
Enabled
Protocol Type
New Protocol,
Restructure Protocol
New Protocol
Slot Mapping
Relation
12-44
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Map as VC4
Selected, Not
selected
Not selected
NOTE
The protection groups of the NEs that form a ring multiplex section must be set with the same attributes except
Local Node, West Node, and East Node.
Postrequisite
In the case of a two-fiber bidirectional MSP ring, you need to configure bidirectional crossconnections between the services and the timeslots of the working channel (the first half of the
timeslots of the line port) later. If extra services need to be transmitted, you need to configure
bidirectional cross-connections between the extra services and the timeslots of the protection
channel (the second half of the timeslots of the line port).
Issue 02 (2010-09-24)
12-45
Trail sink
NE A
NE B
Protection SNC
Protection switching
Working SNC
Trail source
Trail sink
NE A
NE B
Protection SNC
Protection Type
SNCP is classified into the revertive mode and the non-revertive mode.
l
Revertive mode
When an NE is in the switching state, the NE releases the switching and enables the former
working channel to return to the normal state some time after the former working channel
is restored to normal. The period from the time the former working channel is restored to
normal to the time the NE releases the switching is called the wait to restore (WTR) time.
To prevent frequent switching events due to an unstable working channel, it is
recommended that you set the WTR time to five to twelve minutes.
Non-revertive mode
When an NE is in the switching state, the NE keeps the current state unchanged unless
another switching occurs even though the former working channel is restored to normal.
12-46
Issue 02 (2010-09-24)
Protection source
Service sink
The working source and the protection source can be of the fiber line, STM-1e cable, or radio
link, and can be of different line types. The service sink can be of any line or tributary type.
12.5.2 Availability
The SNCP solution requires the support of the applicable equipment and boards.
Table 12-10 Availability of the SNCP solution
Applicable Board
Applicable Equipment
IF1A/IF1B
IDU 610/620
SL1/SD1
SLE/SDE
IFX
IDU 620
SL4
Applicable Equipment
SL1D
RTN 910/950
IF1
IFU2
IFX2
CSTA
RTN 910
CSHC
The following describes the switching principle of SNCP. The switching triggered by the signal failure of the
working SNC is provided as an example.
Issue 02 (2010-09-24)
12-47
Trail sink
NE A
NE B
Protection SNC
Trail sink
NE A
NE B
Protection SNC
When the working SNC fails, the SNCP switching principle is as follows:
1.
Before the switching, the trail source of the SNC (NE A) sends normal service signals to
the trail sink (NE B) through both the working SNC and the protection SNC.
2.
On detecting that the signal of the working SNC fails, the line board of NE B reports the
event to the SCC board.
3.
After confirming that the signal of the working SNC fails and that the signal of the
protection SNC is normal, the SCC board of NE B enables the cross-connect board to
complete the cross-connection between the protection SNC and the service sink.
Issue 02 (2010-09-24)
When the control attributes that you set when creating an SNCP service are not applicable any
more, you can modify the attributes.
12.5.4.3 Setting the Automatic Switching Conditions of SNCP Services
In the case of the SNCP services at the VC-4 level, you can set certain alarms as the automatic
switching conditions.
12.5.4.4 Verifying the SNCP Service Switching
During deployment and commissioning, you can perform switching to test whether SNCP
switching works properly. In fault maintenance, you can perform this operation to locate faults.
12.5.4.5 Converting Non-Protection Services into SNCP Services
After converting the non-protection services into the SNCP services, you can convert the
unidirectional cross-connection of the non-protection services into the unidirectional crossconnection in the receive direction of the SNCP services.
12.5.4.6 Converting SNCP Services into Non-Protection Services
After converting the SNCP services into the non-protection services, you can convert the SNCP
cross-connection in the receive direction into the unidirectional cross-connection of the nonprotection services.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The boards where the source and the sink are must be configured.
Context
l
The MSP line can work only as the service sink of an SNCP service pair and cannot work
as the working source or the protection source.
The radio link with the 1+1 protection configuration can work only as the service sink of
an SNCP service pair, and cannot work as the working source or the protection source.
The radio link with the N+1 protection configuration can work only as the service sink of
an SNCP service pair, and cannot work as the working source or the protection source.
The radio link with the XPIC configuration can work only as the service sink of an SNCP
service pair, and cannot work as the working source or the protection source.
The Hybrid radio link can work only as the service sink of an SNCP service pair, and cannot
work as the working source or the protection source.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > SDH
Service Configuration from the Function Tree.
Step 2 Click Options. Then, select Interleaved or Complete Service to change the VC-12 timeslot
numbering policy used by the cross-connection.
Step 3 Click Create SNCP.
Issue 02 (2010-09-24)
12-49
l When you create a cross-connection whose source or sink is the timeslots of an IF board, the creation may
fail due to the limited number of licenses.
l The calculation of the required number of licenses is based on the total number of service timeslots of all
the IF boards that are involved in cross-connections. In the case of the cross-connections of VC-3 or VC-4
services, the VC-3 or VC-4 services need to be converted into E1 services that have the same capacity. For
example, the cross-connections of one E3 service from a PL3 board to an IF board require the number of
licenses that are used for 21xE1. One VC-3 pass-through service between two IF boards requires the number
of licenses that are used for 42xE1. The 8xE1 SNCP services from two IF boards to one PO1 board require
the number of licenses that are used for 16xE1.
----End
12-50
Issue 02 (2010-09-24)
Parameters
Parameter
Value Range
Default Value
Description
Service Type
SNCP
SNCP
Level
VC12
Revertive Mode
Non-Revertive,
Revertive
Non-Revertive
Direction
Unidirectional,
Bidirectional
Bidirectional
Issue 02 (2010-09-24)
12-51
Parameter
Value Range
Default Value
Description
Hold-off Time
(100ms)
0 to 100
WTR Time(s)
300 to 720
600
Source Slot
Source VC4
Source Timeslot
Range(e.g.1,3-6)
Sink Slot
Sink VC4
12-52
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Sink Timeslot
Range(e.g.1,3-6)
Checked,
Unchecked
Configure SNCP
Tangent Ring
Unchecked
Yes, No
Activate
Immediately
Yes
Postrequisite
If Direction is set to Unidirectional, the cross-connection only in the SNCP receive direction
is created. Hence, you need to configure a unidirectional cross-connection between the service
and the working trail, and later, a unidirectional cross-connection between the service and the
protection trail.
Prerequisite
l
Issue 02 (2010-09-24)
12-53
Procedure
Step 1 In the NE Explorer, click NE and choose Configuration > Protection Configuration > SNCP
Service Control from the Function Tree.
Step 2 Optional: Click Query.
Step 3 In the Working Cross-Connections or Protection Cross-Connections pane, select the SNCP
service for which you want to modify the control attributes.
Step 4 Double click the parameter that you want to modify, select or input a new value, and click
Apply. In the dialog box displayed, click OK according to the actual situation.
NOTE
l You can modify the WTR Time only when you set Revertive Mode to Revertive.
l After you modify the initiation condition, you need to click OK.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
An SNCP protection group at the VC-4 level must be configured.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Protection
Configuration > SNCP Service Control from the Function Tree.
Step 2 Select the SNCP protection group. Double-click Initiation Condition to which the working
service corresponds.
The system displays the Initiation Condition dialog box.
Step 3 Select SD switching conditions. Then, click OK.
Step 4 Select the SNCP protection group. Double-click Initiation Condition to which the protection
service corresponds.
The system displays the Initiation Condition dialog box.
12-54
Issue 02 (2010-09-24)
Parameters
Parameter
Value Range
Default Value
Description
UNEQ
Selected, Not
selected
Not selected
TIM
Selected, Not
selected
Not selected
SD
Selected, Not
selected
Not selected
EXC
Selected, Not
selected
Not selected
NOTE
It is recommended that you set Initiation Condition of the working service to be the same as Initiation
Condition of the protection service.
Prerequisite
l
Issue 02 (2010-09-24)
12-55
Context
The external switching for SNCP protection includes: lockout, forced switching and manual
switching.
l
In the event of lockout of switching, the switching request for the port is denied, but the
reversion of switching is allowed. Regardless of the status of the working and protection
channels, the services are locked in the working channel.
Forced switching has a higher priority than signal failure and signal degrade, on the
protection section. This switching is performed regardless of the protection channel state,
unless the protection channel is satisfying a higher priority bridging request.
Manual switching has a lower priority than signal failure and signal degrade, on the
protection section. The manual switching request is valid only when there is no signal
failure or signal degrade on the protection section.
CAUTION
All switching may interrupt services.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Protection Configuration >
SNCP Service Control from the Function Tree.
Step 2 In the Working Service pane, select a service that you want to switch, right-click the Current
Status of the service, and choose the corresponding item from the shortcut menu to switch or
lock the service.
NOTE
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The unidirectional cross-connection of non-protection services must be configured and the
source of the cross-connection must be a line board.
12-56
Issue 02 (2010-09-24)
Background Information
When this task is performed to convert a non-protection service into an SNCP service, the
original services are not interrupted.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > SDH
Service Configuration from the Function Tree.
Step 2 Optional: Query the data.
1.
Click Query.
Then, the Confirm dialog box is displayed, prompting This operation will query service
at the NE and update service data at the NM. Are you sure to continue?.
2.
Click OK.
Then, the Operation Result dialog box is displayed, prompting Operation Succeeded.
3.
Click Close.
Issue 02 (2010-09-24)
12-57
Parameters
Parameter
Value Range
Default Value
Description
Revertive Mode
Non-Revertive,
Revertive
Non-Revertive
Hold-off Time
(100ms)
0 to 100
WTR Time(s)
300 to 720
600
Source Slot
Source VC4
12-58
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Source Timeslot
Range(e.g.1,3-6)
Sink Slot
Sink VC4
Sink Timeslot
Range(e.g.1,3-6)
Postrequisite
The SNCP service after the conversion is the SNCP service only in the receive direction. Later,
you need to configure a unidirectional cross-connection between the service and the working
trail, and a unidirectional cross-connection between the service and the protection trail. The non-
Issue 02 (2010-09-24)
12-59
protection service can be converted into the SNCP service both in the receive direction and the
transmit direction only after the configuration.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The current service is transmitted in the working path.
The SNCP cross-connection in the receive direction must be configured.
Background Information
When this task is performed to convert an SNCP service into a non-protection service, the
original services are not interrupted.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > SDH
Service Configuration from the Function Tree.
Step 2 In the Auto-Created Cross-Connection pane, select the cross-connection. Right-click and
choose Convert to Non-Protection Service from the shortcut menu.
Step 3 Choose Working or Protection from the displayed menu.
Step 4 Then, the Prompt dialog box is displayed, prompting If the SNCP service is converted into a
non-protection service, the service may be interrupted. Are you sure to continue?.
Step 5 Click OK.
----End
Postrequisite
You need to delete the unidirectional cross-connection between the service and the working path
or the unidirectional cross-connection between the service and the protection path. The SNCP
service can be converted into the non-protection service both in the receive direction and the
transmit direction only after the deletion.
Issue 02 (2010-09-24)
At the link layer, the detection is conducted by MPLS OAM in 10 ms. Set Detection Packet
Period to 3.3 ms so that the protection switching time is less than 50 ms.
In MPLS APS, detection at the link layer is performed by MPLS OAM. Thus, you must set the
MPLS OAM parameters for relevant tunnels before configuring MPLS APS.
Issue 02 (2010-09-24)
12-61
Processing board
Access
Processing board
switching
switching
Processing board
Protection path/
protocol path
Access
Processing board
Subnetwork
The APS protocol is transmitted through the protection tunnel to exchange the protocol state
and the switching state. The equipment at the two ends performs service switching and
selectively receives services according to the protocol state and switching state.
Table 12-12 lists parameters for MPLS APS 1+1 protection.
Table 12-12 Parameters for MPLS APS 1+1 protection
Switching
Mode
Revertive
Mode
Switching
Protocol
Switching
Time
Switching
Hold-off
Time
Default
Recovery
Time
(100ms)
1+1 singleended
switching
Nonrevertive
APS
protocol
50 ms
0 to 100 (0 by
default)
1+1 dualended
switching
Nonrevertive
APS
protocol
50 ms
0 to 100 (0 by
default)
1+1 singleended
switching
Revertive
APS
protocol
50 ms
0 to 100 (0 by
default)
5 minutes
1+1 dualended
switching
Revertive
APS
protocol
50 ms
0 to 100 (0 by
default)
5 minutes
12-62
Issue 02 (2010-09-24)
Processing board
Access
Processing board
switching
switching
Processing board
Access
Processing board
Subnetwork
Protection path
Protocol path
In MPLS APS 1:1 protection, services accessed are transmitted through the working tunnel.
When the working tunnel fails, the services are switched to the protection tunnel. Then, the
services are transmitted through the protection tunnel and the receive end receive the services
from the protection tunnel. The APS protocol is transmitted through the protection tunnel to
exchange the protocol state and the switching state. The equipment at the two ends performs
service switching and selectively receives services according to the protocol state and switching
state.
Table 12-13 lists parameters for MPLS APS 1:1 protection.
Table 12-13 Parameters for MPLS APS 1:1 protection
Switching
Mode
Revertive
Mode
Switching
Protocol
Switching
Time
Switching
Hold-off
Time
Default
Recovery
Time
(100ms)
Issue 02 (2010-09-24)
1:1 dualended
switching
Nonrevertive
APS
protocol
50 ms
0 to 100 (0 by
default)
1:1 dualended
switching
Revertive
APS
protocol
50 ms
0 to 100 (0 by
default)
5 minutes
12-63
Switching
Mode
Revertive
Mode
Switching
Protocol
Switching
Time
Switching
Hold-off
Time
Default
Recovery
Time
(100ms)
Any of the following conditions triggers the switching:
l The board has a hardware or software failure.
l A cold reset is performed on the board.
l A switching command is manually issued.
l MPLS OAM detects that the working tunnel is faulty at the link layer.
APS
The automatic protection switching (APS) protocol is used to coordinate actions of the source
and the sink in the case of bidirectional protection switching. By the APS protocol, the source
and the sink cooperate with each other to perform functions such as protection switching,
switching delay, and WTR function.
According to ITU-T Y.1720, the source and the sink both need to select channels in the APS.
In this case, the APS protocol is required for coordination. In the case of bidirectional protection
switching, the APS protocol needs to be used regardless of the revertive mode.
The APS protocol is always transmitted through the protection tunnel. Then, the equipment at
either end knows that the tunnel from which the APS protocol is received is the protection tunnel
of the opposite end and thus to determine whether the configuration about the working tunnel
and the protection tunnel is consistent at the two ends.
When the equipment cannot receive any APS packet, services should be always transmitted and
received from the working tunnel.
Switching Mode
MPLS APS provides two switching modes, that is, single-ended switching and dual-ended
switching.
In the case of single-ended switching, when one end detects a fault, it only performs switching
on the local end and does not instruct the opposite end to perform any switching.
In the case of dual-ended switching, when one end detects a fault, it performs switching on the
local end and also instructs the opposite end to perform switching.
Single-ended switching does not require the APS protocol for negotiation and it features rapid
and stable switching.
12-64
Issue 02 (2010-09-24)
Dual-ended switching ensures that the services are transmitted in a consistent channel, which
facilitates service management.
Revertive Mode
The MPLS APS function supports two revertive modes, that is, revertive mode and non-revertive
mode.
In the non-revertive mode, services are not switched from the protection tunnel to the working
tunnel even the working tunnel is restored to the normal state.
In the revertive mode, services are switched from the protection tunnel to the original working
tunnel if the working tunnel is restored to the normal state within the WTR time.
WTR Time
The WTR time refers to the period from the time when the original working tunnel is restored
to the time when the services are switched from the protection tunnel to the original working
tunnel.
In certain scenarios, the state of the working tunnel is unstable. In this case, setting the WTR
time can prevent frequent switching of services between the working tunnel and the protection
tunnel.
By default, the WTR time of the equipment is 5 minutes.
Hold-off Time
The hold-off time refers to the period from the time when the equipment detects a fault to the
time when the switching operation is performed.
When the equipment is configured with the MPLS APS protection and other protection, setting
the hold-off time can ensure that other protection switching operations are performed first.
By default, the hold-off time of the equipment is 0s.
Protocol State
The protocol state indicates whether the APS protocol of the protection group is valid currently.
In the case of configuring the MPLS APS protection, the protocol state is disabled by default.
If you enable the APS protocol at the local NE first and then the opposite NE when configuring
the MPLS APS protection, the opposite NE may has an anomaly in receiving services. After the
MPLS APS protection group is configured at the two ends, start the protocol.
12-65
NE B
Protection Tunnel
There are two MPLS tunnels as shown in the figure. Normally, services are transmitted through
the working tunnel, and the protection tunnel is used to transmit the APS protocol.
MPLS OAM performs the connectivity check for each unidirectional MPLS tunnel. The source
sends connectivity check packets periodically and the sink performs the check. Set the OAM
packet type to FFD and the sending period to 3.3 ms to ensure that the APS switching time is
less than 50 ms.
The switching mode of the MPLS APS 1+1 protection includes single-ended and dual-ended
switching.
NE B
Protection Tunnel
There are two MPLS tunnels as shown in the figure. The continuous line indicates the working
tunnel and the dashed line indicates the protection tunnel. Normally, services are transmitted
through the working tunnel, and the protection tunnel is used to transmit the APS protocol.
12-66
Issue 02 (2010-09-24)
MPLS OAM performs the connectivity check for each unidirectional MPLS tunnel. The source
sends connectivity check packets periodically and the sink performs the check. Set the OAM
packet type to FFD and the sending period to 3.3 ms to ensure that the APS switching time is
less than 50 ms.
The switching mode of the MPLS APS 1:1 protection includes single-ended and dual-ended
switching.
Enable MPLS OAM of the tunnels before configuring the APS protection.
Set the MPLS OAM packet type to FFD and the sending period to 3.3 ms.
Set the APS protocol to the enabled state after the nodes at both ends are configured with
the APS protection group.
Prerequisite
l
You must have enabled the MPLS OAM state of each MPLS tunnel in the protection group.
The OAM packet type must be set to FFD and transmission period to 3.3 ms.
WARNING
l The protection tunnel should not carry any extra service.
Procedure
Step 1 Select the source NE of the Tunnel in the NE Explorer. Choose Configuration > APS
Protection Management from the Function Tree.
Step 2 Click New. The New Tunnel Protection Group dialog box is displayed.
Issue 02 (2010-09-24)
12-67
CAUTION
When creating an APS protection group, disable Protocol Status. Start the protocol only when
the configuration of the APS protection group is complete at both nodes.
Step 4 Click OK. The MPLS tunnel protection group is successfully configured.
NOTE
The bandwidth of the protection tunnel should exceed that of the working tunnel. To increase the bandwidth
of the working tunnel after the protection group is created, increase the bandwidth of the protection tunnel
first.
Step 5 Refer to Steps 1 through 4 to configure the protection group on the sink NE of the tunnel.
Step 6 Start the protocol state of the MPLS APS protection group.
12-68
Issue 02 (2010-09-24)
1.
Select the source NE of the Tunnel in the NE Explorer. Choose Configuration > APS
Protection Management from the Function Tree.
2.
3.
A dialog box is displayed indicating that the operation is successful. Protocol Status of
the APS protection group turns to Enabled.
----End
Prerequisite
l
You must complete the creation of the MPLS tunnel protection group and you must have
enable the protocol status.
Context
CAUTION
When other switching operations, excluding the exercise switching, are performed, the services
may be interrupted.
Procedure
Step 1 Select the source NE of the Tunnel in the NE Explorer. Choose Configuration > APS Protection
Management from the Function Tree.
Step 2 Select a protection group that you want to perform protection switching.
Step 3 Click Function tab.
Step 4 Choose the switching operation to be performed from the displayed shortcut menu.
Issue 02 (2010-09-24)
12-69
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 Select the source NE of the Tunnel in the NE Explorer. Choose Configuration > APS Protection
Management from the Function Tree.
Step 2 Select a protection group that you want to delete.
Step 3 Click Delete. A dialog box is displayed for confirmation.
Step 4 Click Yes. The Operation Result dialog box is displayed.
Step 5 Click Close.
----End
Issue 02 (2010-09-24)
Definition
Based on the traditional Ethernet mechanism, ERPS uses the R-APS protocol to achieve fast
protection switching on the Ethernet ring network.
Objective
The following are objectives of Ethernet ring protection:
l
To provide protection at any physical or server layer for any type of client signals.
To reduce operational expenditure (OpEx) and capital expenditure (CapEx) for vendors.
Ethernet Ring
An Ethernet ring is a collection of Ethernet ring nodes forming a closed loop whereby each node
is connected to two adjacent nodes through a full-duplex communication link.
RPL
The RPL is the ring link that is blocked at one end or both ends under normal conditions to
prevent loops. One Ethernet ring has only one RPL.
RPL Owner
The RPL owner is an Ethernet ring node adjacent to the RPL. It is responsible for blocking and
unblocking the RPL port. Under normal conditions, the RPL owner blocks the RPL port to
prevent loops.
R-APS message
R-APS message is a protection switching protocol defined for the ERPS, which contains the
messages, requests, or states required by the protection switching. Through the R-APS message
between ring nodes, it is ensured that the nodes perform consistent operations to complete the
protection switching.
l
R-APS (NR, RB): A type of R-APS message that is sent by the RPL owner to indicate that
the ring is in normal state and the RPL port is blocked.
R-APS (SF): A type of R-APS message that is sent by the node detecting the link fault to
indicate that an SF event occurs at the local node.
Issue 02 (2010-09-24)
12-71
R-APS (NR): A type of R-APS message that is sent by the node detecting the link recovery
to indicate that the SF event at the local node is cleared.
Control VLAN
The ERPS uses an independent VLAN channel to carry the R-APS messages. The control VLAN
ID cannot be the same as the service VLAN ID.
R-APS Format
R-APS information is carried in the R-APS protocol data unit (PDU), which is transmitted
through R-APS messages. R-APS messages ensure that all nodes on the ring perform consistent
operations. R-APS frame format is a type of ETH-OAM frame formats. See Figure 12-28. The
default destination MAC address of R-APS message is 01-19-A7-00-00-01. In Figure 12-28,
the gray part indicates the 32-byte R-APS specific information.
Figure 12-28 R-APS format
Table 12-14 lists the description of each filed in R-APS specific information.
Table 12-14 Description of each filed in R-APS specific information
Field
Length
Value
Description
Request/State
4 bits
1011
0000
Others
Reserved.
4 bits
0000
Reserved.
1 bit
Resv1
Status
RB (RPL
Blocked)
Issue 02 (2010-09-24)
Field
Length
Value
Description
1 bit
6 bits
Reserved.
Node ID
6 bytes
Reserved
24 bytes
All 0s
Reserved.
DNF (Do
Not Flush)
Status
Reserved
R-APS Timer
During the ERPS process, three timers are used, that is, guard timer, wait-to-restore (WTR)
timer, and holdoff timer.
l
Guard Timer
R-APS messages are periodically transmitted over the ring and the status of the ring
nodes may change at any moment. This can result in an outdated and useless R-APS
message being received by ring nodes. The reception or forwarding of the outdated
messages may result in erroneous protection switching decisions. The guard timer is
used to prevent ring nodes from receiving outdated R-APS messages.
The period of the guard timer may be configured in 10 ms steps between 10 ms and 2s,
with a default value of 500 ms.
When the guard timer is running, the received R-APS message is discarded. When the
guard timer expires, the received R-APS message is forwarded directly.
WTR Timer
The period from the time when the original working channel is recovered to normal to
the time when the NE releases the switching is called the wait-to-restore (WTR) time.
When the original working channel is recovered to normal, the WTR timer on the RPL
owner starts. While the timer is running, a WTR running signal is continuously
generated. After the timer expires and no switching request of higher priority is received,
the WTR timer stops generating the WTR running signal but starts to continuously
generate the WTR expire signal.
The period of the WTR timer may be configured in 1 minute steps between 5 minutes
and 12 minutes, with a default value of 5 minutes.
The WTR timer is used to prevent the frequent switching actions due to instability of
the working channel.
Holdoff Timer
When a new fault or more faults occur, the holdoff timer starts if the preset holdoff timer
value is non-zero. When the holdoff timer is running, the fault is not reported to ERPS.
When the holdoff timer expires, the link state is checked regardless of whether the defect
persists. If there is a fault, the fault is reported to ERPS for protection switching. The
reported fault need not be the same as the fault that starts the holdoff timer.
Issue 02 (2010-09-24)
12-73
The period of the holdoff timer may be configured in 100 ms steps between 0s and 10s
with an accuracy of 5 ms. The default value is 0s.
The holdoff timer is used to coordinate protection switching time between ERPS and
other existing protection schemes. Its purpose is to allow the protection switching at
another layer or level (for example, the LAG protection at ports) to have a chance to fix
the problem before ERPS switching.
12.7.3 Availability
This section describes the equipment type and software versions that support the ERPS
protection.
Table 12-15 Boards and equipment versions of the OptiX RTN 910, OptiX RTN 950, OptiX
RTN 620 and NMS versions that support the ERPS protection
Board Type
Equipment Version
EM6T
EFP6
Trigger Condition
The automatic Ethernet ring protection switching can be triggered on any of the following
conditions:
l
Board fault: A key board is faulty (for example, the line board is powered off or offline).
In the case of Ethernet ports, the trigger conditions are R_LOS, LINK_ERR, and
LSR_NO_FITED.
NOTE
If a VCG port is not bound with any VC, it indicates that the VCG port is normal and will not trigger ERPS
switching.
12-74
Issue 02 (2010-09-24)
Switching Time
In the case of the LINK_LOS state at the ports on the client side, the switching time is less than
50 ms. In other cases, the switching time is 200 ms.
Switching Mode
Revertive means that the service is switched to the working channel after the working channel
becomes normal. Non-Revertive means that the service is not switched to the working channel
after the working channel becomes normal.
Switching State
The switching states are idle, wait-to-restore, automatic switching, idle (protection channel is
active), and SF switching.
Working Principle
ERPS uses the R-APS protocol to achieve protection switching. Figure 12-29 and Figure
12-30 show the working principle of ERPS.
NOTE
In this document, R-APS (SF), R-APS (NR), and R-APS (NR, RB) messages are referred to as SF, NR,
and NR, RB respectively.
Issue 02 (2010-09-24)
12-75
Figure 12-29 ERPS switching process (upon a fault not on the RPL link)
NE A
NE B
RPL
NE C
NE D
RPL Owner
W
Normal
State
NR, RB (DNF)
NR, RB (DNF)
NR, RB (DNF)
NR, RB (DNF)
Failure
3
4
SF
Flush
SF
Flush
SF
5
6
Protection
State
Flush
SF
SF
Flush
SF
7
8
SF
SF
SF
NR
NR
Recovery
Guard timer
NR
NR
NR
WTR timer
NR, RB (DNF)
Normal
State
10
Flush
NR, RB (DNF)
NR, RB (DNF)
Flush
NR, RB (DNF)
Flush
NR, RB (DNF)
NR, RB (DNF)
NR, RB (DNF)
12-76
1.
In normal state, the RPL owner (NE D) blocks the east port and sends the NR, RB message
at the east and west ports.
2.
3.
NE A and NE B detect the SF condition. After the holdoff timer expires, NE A and NE B
block the ports connecting to the faulty link and flush filtering database (FDB).
4.
NE A and NE B keep forwarding the SF message to the Ethernet ring periodically while
the SF condition persists.
5.
The node receiving the SF message on the ring flushes FDB. When the RPL owner receives
the SF message, it unblocks the blocked RPL port.
6.
The ERPS switching is complete and the ring enters stable state.
7.
8.
NE A and NE B detect that the SF condition is cleared. Then, NE A and NE B start the
guard timer and initiate periodical transmission of the NR message at both ring ports. When
the guard timer is running, the received R-APS message is discarded. After the guard timer
expires, NE A and NE B accept the new R-APS message that they receive.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
9.
When the RPL owner receives the NR message, it starts the WTR timer. At expiration of
the WTR timer, the RPL owner blocks the RPL port, sends the NR, RB message, and flushes
FDB.
10. When NE A and NE B receive the NR, RB message, they unblock the blocked ports and
stop forwarding the NR message. In addition, NE A, NE B, and NE C flush FDB when
receiving the NR, RB message. Then, the Ethernet ring returns to normal state.
Figure 12-30 ERPS switching process (upon a fault on the RPL link)
NE A
NE B
RPL
NE C
NE D
RPL Owner
W
Normal
State
NR, RB (DNF)
NR, RB (DNF)
NR, RB (DNF)
NR, RB (DNF)
Failure
3
4
Protection
State
SF (DNF)
SF (DNF)
SF (DNF)
SF (DNF)
Recovery
Guard timer
NR
NR
NR
NR
NR
WTR timer
Normal
State
NR, RB (DNF)
NR, RB (DNF)
NR, RB (DNF)
NR, RB (DNF)
NR, RB (DNF)
NR, RB (DNF)
NR, RB (DNF)
NR, RB (DNF)
In normal state, the RPL owner (NE D) blocks the east port.
2.
3.
NE A and NE D detect the SF condition. After the holdoff timer expires, NE A and NE D
block the ports connecting to the faulty link.
4.
NE A and NE D keep forwarding the SF message to the Ethernet ring periodically while
the SF condition persists. The SF message contains the Do Not Flush (DNF) indication,
which prevents every node on the Ethernet ring from flushing FDB under any condition.
The RPL owner receives the SF message with the DNF indication, but the SF message is
ignored because there is a local higher priority request (local SF). When receiving the SF
message with the DNF indication, the other NEs on the ring are informed of the RPL link
fault. The other NEs, however, do not flush FDB under any condition. Then, the ring enters
stable state. There is the SF message with the DNF indication on the ring.
Issue 02 (2010-09-24)
12-77
5.
6.
NE A and NE D detect that the SF condition is cleared. Then, NE A and NE D start the
guard timer and initiate periodical transmission of the NR message at both ring ports. The
guard timer prevents NE A and NE D from receiving R-APS messages. After the guard
timer expires, NE A and NE D accept the new R-APS message that they receive.
7.
When the RPL owner receives the NR message, it starts the WTR timer. At expiration of
the WTR timer, the RPL owner blocks the RPL port, sends the NR, RB message with the
DNF indication. This message prevents every node on the ring from flushing FDB under
any condition.
8.
When NE A receives the NR, RB message, it unblock the blocked west port and stop
forwarding the NR message. In addition, when receiving the NR, RB message, NE A, NE
B, and NE C are informed of the RPL link recovery and are required not to flush FDB under
any condition. Then, the Ethernet ring returns to normal state.
12-78
Issue 02 (2010-09-24)
VB
RPL Owner
NE A
VB
NE B
VB
NE D
VB
Normal State
NE C
Protection switching
Failure
VB
RPL Owner
NE A
VB
NE B
VB
NE D
VB
Protection State
NE C
Ethernet service direction
12-79
The Ethernet ring protection is applicable only to ring networks and supports the network
consisting of only one ring currently.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Ethernet Protection > ERPS
Management from the Function Tree.
Step 2 Click New. Then, the Create Ethernet Ring Protection Protocol Instance dialog box is
displayed.
Step 3 The protection parameters should be set according to network planning.
NOTE
Step 4 Click OK. After the operation succeeds, the Operation Result dialog box is displayed. Click
Close.
Step 5 Set Hold-Off Time(ms), Guard Time(ms), WTR Time(min), Packet Transmit Interval(s),
and Entity Level according to network planning. Click Apply.
Step 6 Display the NE Explorer of the other nodes on the ring in turn and repeat Steps 1 through 5 to
create Ethernet ring protection at each node. Then, the creation of the protection ring is complete.
Step 7 Optional: Select an instance and click Delete. Click OK in the Confirm dialog box displayed.
Then, the Operation Result dialog box is displayed, indicating that the operation is successful.
Click Close. In this case, the instance is deleted.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
12-80
Issue 02 (2010-09-24)
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Ethernet Protection > ERPS
Management from the Function Tree.
Step 2 Click Query. Then, the parameters of the current protection instance are displayed.
Step 3 Optional: Double-click the required field or click the drop-down list and then you can modify
the parameter value or choose a new value. In the case of Ethernet ring protection, the following
parameters can be modified: Control VLAN, Hold-Off Time(ms), Guard Time(ms), WTR
Time(min), Packet Transmit Interval(s), and Entity Level.
Step 4 Click Apply to deliver the configuration.
----End
12.8.1 Overview
Link aggregation allows multiple links that are attached to the same equipment to be aggregated
to form a link aggregation group (LAG) so that the bandwidths and availability of the links
increase. The aggregated links can be considered as a single logical link.
The LAG aggregates multiple physical links to form a logical link that is at a higher rate. Link
aggregation functions between adjacent equipment. Hence, link aggregation is not related to the
architecture of the entire network. Link aggregation is also called port aggregation because each
link corresponds to a port in an Ethernet.
As shown in Figure 12-32, link aggregation provides the following functions:
l
Increased bandwidth
The LAG provides the telecom operators with a cost-effective method of increasing the
link bandwidth. The telecom operators obtain data links with higher bandwidths by
Issue 02 (2010-09-24)
12-81
combining multiple physical links into one logical link without upgrading the existing
equipment. The bandwidth of the logical link is equal to the sum of the bandwidths of the
physical links. The aggregation module distributes the traffic to different members by using
the load sharing algorithm, thus realizing the load sharing function at the link level.
l
Increased availability
The links in a LAG provide backup to each other dynamically. When a link fails, another
link in the LAG quickly replaces the failed link. The process in which link aggregation
starts the backup link relates only to the links in the same LAG and does not relate to the
links that are not in the LAG.
Link 3
Ethernet
packets
LAG
LAG Types
Types of Aggregation: Link aggregation is available in the following two types.
l
Manual aggregation
A user manually creates a LAG. When a user adds or deletes a member port, the LACP
protocol is disabled. A port can be in the up or down state. The system determines whether
to perform aggregation depending on the physical status of a port (up or down).
Manual aggregation is not as accurate or effective as static aggregation in controlling link
aggregation.
Static aggregation
A user manually creates a LAG. When a user adds or deletes a member port, the LACP
protocol is enabled. A port can be in the selected, unselected, or standby state. The
equipment exchanges aggregation information by using the LACP protocol to reach
agreement on aggregation.
Static aggregation is more accurate and more effective than manual aggregation in
controlling link aggregation.
Load Sharing Modes: The LAG supports the following load sharing modes.
l
12-82
Issue 02 (2010-09-24)
Port Types
NOTE
l The main port number cannot appear in the slave port number list.
l A slave port can be added to an LAG only when no service is configured for the port. A main port can
be added to an LAG even if you configure services for the port, and the services of the port are not
affected.
l You can modify or query the attributes of a main port. You cannot set the logical attributes of a slave
port, but can query it.
l FE port and GE port can not in the same LAG.
Main Port
l
The Main Port indicates the LAG member port available for creating services. Each LAG
has only one main port. If the load sharing parameter is set to Non-Sharing, the main port
carries the services. When the main port becomes faulty, the services are switched to and
carried by the slave port.
Slave Port
l
The slave ports in a link aggregation group are fixed. Unless they are manually modified,
the system does not automatically add them to or delete them from the link aggregation
group.
Add the relevant slave port to the link aggregation group as required.
12.8.2 Availability
The LAG feature requires the support of the applicable equipment and boards.
Table 12-16 Availability of the LAG feature
Applicable Board
Applicable Equipment
EMS6, EFP6
RTN 620
EM4T
RTN 605
Applicable Equipment
IFU2
RTN 910/950
IFX2
EM6T
Issue 02 (2010-09-24)
12-83
Applicable Board
Applicable Equipment
EM6F
CSHA
RTN 910
CSHB
CSHC
12.8.3 Principle
The LACP protocol is used to realize dynamic aggregation and de-aggregation of links. The
LACP protocol is developed based on IEEE 802.3ad.
The LACP protocol is developed based on IEEE 802.3ad and performs the following functions:
l
The LACP protocol provides the data switching equipment with a standard negotiation
mode. Hence, the system automatically forms aggregation links according to its
configuration and enables the aggregation links to transmit and receive data.
After an aggregation link is formed, the LACP protocol maintains the status of the
aggregation link. When the aggregation conditions change, the LACP protocol
automatically adjusts or releases the LAG.
Equipment A and equipment B exchange LACP packets through port 1, port 2, port 3, and
port 4. Each LACP packet contains the system priority, system MAC address, port priority,
port number, and operational key. The operational key reflects the aggregation capability
of the port. The key value is determined by certain factors such as the physical
characteristics of the port (for example, rate and duplex), configuration constraints set by
the network administrator, characteristics of the port, and limitations of the port.
2.
3.
4.
Equipment A and equipment B reach agreement on the ports that can be added into a LAG,
and then, form a LAG.
12-84
Equipment A
Equipment B
PORT1
PORT1
PORT2
PORT2
PORT3
PORT3
PORT4
PORT4
Issue 02 (2010-09-24)
The systems realize auto-negotiation by exchanging LACP packets. Each LACP packet
contains the configuration and current status of the system that sends the LACP packet.
The LACP packet is not numbered. Hence, both parties use the timer and periodical sending
mechanism, instead of the detection and re-transmission of lost packets mechanism, to
prevent loss of information.
The number of LACP packets that are sent in one second does not exceed five.
LAG
12-85
By querying the LAG details, you can obtain detailed information of the current LAG.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The physical network topology must be established.
The Ethernet and IF boards that need to be aggregated must be created.
When IF boards are used to create an LAG, the attributes of all member ports must be consistent.
Context
NOTE
In the case of RTN600V100R004 NEs, RTN900V100R002 NEs and the NEs after the versions, when the Load
Sharing is Sharing, you can not set or query the Revertive Mode.
Procedure
Step 1 In the case of RTN 600 NEs:
1.
In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet
Interface Management > Ethernet Link Aggregation Management from the Function
Tree.
2.
3.
Click New and the Create Link Aggregation Group dialog box is displayed. Set the
parameters.
4.
Click OK.
5.
Optional: Click the Link Aggregation Parameters tab. Set Port Priority and System
Priority.
NOTE
l The port ID consists of Port and Port Priority. The port that has the smallest port ID in an LAG
has the priority to be aggregated first.
l The system ID consists of System Priority and System MAC Address. When the system
negotiates with the remote system, the system with the smallest ID has the priority to choose the
port. In this example, the system refers to the board, and the system MAC address refers to the
MAC address of the board. The factory-set MAC address is globally unique and cannot be
modified.
In the NE Explorer, select the NE and choose Configuration > Interface Management
> Link Aggregation Group Management from the Function Tree.
2.
Click New and set the parameters in the dialog box displayed.
l You can select an Ethernet port or multiple IF boards to create an LAG group.
12-86
Issue 02 (2010-09-24)
l You can select the ports on different boards of the same type, but not of different types,
to configure an LAG group. For example, you cannot select an Ethernet board and an
IF board to configure an LAG group.
3.
Click OK.
4.
Optional: Click the Port Priority tab. Set Port Priority for ports.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The LAG must be created.
Procedure
Step 1 In the case of RTN 600 NEs:
1.
In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet
Interface Management > Ethernet Link Aggregation Management from the Function
Tree.
2.
The LAG where the LACP protocol is not used, such as a manual LAG, the setting of the port priority
does not take effect.
3.
In the NE Explorer, select the NE and choose Configuration > Interface Management
> Link Aggregation Group Management from the Function Tree.
2.
Click Modify and set the parameters in the dialog box displayed.
3.
Click OK.
4.
Optional: Click the Port Priority tab. You can modify Port Priority for ports as required.
----End
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
It is only applicable to LAGs of the static aggregation mode.
Issue 02 (2010-09-24)
12-87
Procedure
Step 1 In the case of RTN 600:
1.
In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet
Interface Management > Ethernet Link Aggregation Management from the Function
Tree.
2.
Step 2 In the case of RTN 900: In the NE Explorer, select the NE and choose Configuration > Interface
Management > Link Aggregation Group Management from the Function Tree.
Step 3 Select an LAG of the static aggregation mode. Right-click the LAG and choose Link LACP
Packet Statistics. You can view the statistics in the dialog box is displayed.
----End
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
It is only applicable to LAGs of the static aggregation mode.
Procedure
Step 1 In the case of RTN 600:
1.
In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet
Interface Management > Ethernet Link Aggregation Management from the Function
Tree.
2.
Step 2 In the case of RTN 900: In the NE Explorer, select the NE and choose Configuration > Interface
Management > Link Aggregation Group Management from the Function Tree.
Step 3 Select an LAG of the static aggregation mode. Right-click the LAG and choose Link
Aggregation Group Details. You can view the information in the dialog box is displayed.
----End
12-88
Issue 02 (2010-09-24)
13
Issue 02 (2010-09-24)
13-1
This section describes how to plan the service parameters and complete the entire process of
configuring the parameters of each NE according to E1 service requirements, through an
example.
13.9 Configuration Example (Hop between the IDU 605 and the IDU 620)
This section describes how to plan the service parameters and complete the entire process of
configuring the parameters of each NE according to E1 service requirements, through an
example.
13-2
Issue 02 (2010-09-24)
By order
This timeslot numbering scheme is also considered as timeslot scheme, where the
numbering formula is as follows: VC-12 number = TUG-3 number + (TUG-2 number - 1)
x 3 + (TU-12 number -1) x 21.
This scheme is the numbering scheme recommended by ITU-T G.707, which is the default
scheme adopted by the OptiX equipment.
Interleaved scheme
This timeslot numbering scheme is also considered as line scheme, where the numbering
formula is as follows: VC-12 number = (TUG-3 number - 1) x 21 + (TUG-2 number -1) x
3 + TU-12 number.
The OptiX equipment can adopt this scheme when it interconnects with the equipment that
adopts the interleaved scheme or when specific timeslot numbering scheme is required.
TUG-3
Issue 02 (2010-09-24)
{
{
{
10
13
16
19
22
25
28
31
34
37
40
43
46
49
52
55
58
61
11
14
17
20
23
26
29
32
35
38
41
44
47
50
53
56
59
62
12
15
18
21
24
27
30
33
36
39
42
45
48
51
54
57
60
63
TU-12
13-3
TUG-3
{
{
{
TUG-2
4
10
13
16
19
11
14
17
20
12
15
18
21
22
25
28
31
34
37
40
23
26
29
32
35
38
41
24
27
30
33
36
39
42
43
46
49
52
55
58
61
44
47
50
53
56
59
62
45
48
51
54
57
60
63
TU-12
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explore. Choose Configuration > CrossConnection Configuration.
Step 2 Select the used E1 port.
13-4
Issue 02 (2010-09-24)
Parameters
Parameter
Value
Default Value
Frequency of Recurrence
l E1-1 to E1-5
(IDU 605 1A)
Selected, Not
Selected
Selected
l E1-1 to E1-16
(IDU 605 1B/
2B)
l E1-1 to E1-16
(IDU 605 1F/2F)
l The number of
E1 ports is
related to the
Hybrid/AM
attribute (IDU
605 1F/2F).
Issue 02 (2010-09-24)
13-5
Step 4 Set the Level, the Direction, the source and the sink of the service.
Step 5 Click OK.
----End
13-6
Issue 02 (2010-09-24)
Sample Configuration
In Figure 13-3, NE1, NE2, NE3 and NE4 comprise an unprotected chain. Services are
transmitted by microwave between NE1 and NE2, and NE3 and NE4. Services are transmitted
by fiber between NE2 and NE3.
Figure 13-3 Chain network
NE1
NE2
NE3
NE4
Two point-to-point bidirectional E1 services are transmitted between NE1 and NE2. The services
use the first and the second VC12 timeslot of a tributary board, and the first and the second VC12
timeslot of an intermediate frequency board.
Two bidirectional E1 services are transmitted between NE1 and NE4. The services use the third
and the fourth VC12 timeslots of the tributary board, the third and the fourth VC12 timeslots of
the intermediate frequency board, and the third and the fourth VC12 timeslots in the first VC4
of a line board.
The service flow of the E1 services between NE1 and NE2 is as follows: E1tributary board
at NE1intermediate frequency board at NE1intermediate frequency board at NE2
tributary board at NE2
The service flow of the E1 services between NE1 and NE4 is as follows: E1tributary board
at NE1intermediate frequency board at NE1intermediate frequency board at NE2
line board at NE2line board at NE3intermediate frequency board at NE3
intermediate frequency board at NE4tributary board at NE4
According to the service flow, you need to perform the configuration as follows:
l
Configure add or drop VC12 services for NE1. The source and the sink timeslots of the
bidirectional services between the tributary board and the intermediate frequency board
range from 1 to 4.
Configure add or drop VC12 services for NE2. The source and the sink timeslots of the
bidirectional services between the intermediate frequency board and the tributary board
range from 1 to 2.
Configure pass-through VC12 services for NE2. The source and the sink timeslots of the
bidirectional services between the intermediate frequency board and the line board range
from 3 to 4.
Configure pass-through VC12 services for NE3. The source and the sink timeslots of the
bidirectional services between the line board and the intermediate frequency board range
from 3 to 4.
Configure add or drop VC12 services for NE4. The source and the sink timeslots of the
bidirectional services between the intermediate frequency board and the tributary board
range from 3 to 4.
13-7
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > SDH
Service Configuration from the Function Tree.
Step 2 Optional: Click Options. Then, select Interleaved or Complete Service to change the VC-12
timeslot numbering policy used by the cross-connection.
Step 3 Click Create.
Then, the Create SDH Service dialog box is displayed.
Step 4 Configure the cross-connections of the service.
13-8
Issue 02 (2010-09-24)
l When you create a cross-connection whose source or sink is the timeslots of an IF board, the creation
may fail due to the limited number of licenses.
l The calculation of the required number of licenses is based on the total number of service timeslots of
all the IF boards that are involved in cross-connections. In the case of the cross-connections of VC-3
or VC-4 services, the VC-3 or VC-4 services need to be converted into E1 services that have the same
capacity. For example, the cross-connections of one E3 service from a PL3 board to an IF board require
the number of licenses that are used for 21xE1. One VC-3 pass-through service between two IF boards
requires the number of licenses that are used for 42xE1. The 8xE1 SNCP services from two IF boards
to one PO1 board require the number of licenses that are used for 16xE1.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The boards where the source and the sink are must be configured.
Context
l
The MSP line can work only as the service sink of an SNCP service pair and cannot work
as the working source or the protection source.
The radio link with the 1+1 protection configuration can work only as the service sink of
an SNCP service pair, and cannot work as the working source or the protection source.
The radio link with the N+1 protection configuration can work only as the service sink of
an SNCP service pair, and cannot work as the working source or the protection source.
The radio link with the XPIC configuration can work only as the service sink of an SNCP
service pair, and cannot work as the working source or the protection source.
The Hybrid radio link can work only as the service sink of an SNCP service pair, and cannot
work as the working source or the protection source.
Issue 02 (2010-09-24)
13-9
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > SDH
Service Configuration from the Function Tree.
Step 2 Click Options. Then, select Interleaved or Complete Service to change the VC-12 timeslot
numbering policy used by the cross-connection.
Step 3 Click Create SNCP.
The system displays the Create SNCP Service dialog box.
Step 4 Set the attributes of the SNCP protection group and the slot mapping relation of the SNCP
service.
NOTE
13-10
Issue 02 (2010-09-24)
NOTE
l When you create a cross-connection whose source or sink is the timeslots of an IF board, the creation may
fail due to the limited number of licenses.
l The calculation of the required number of licenses is based on the total number of service timeslots of all
the IF boards that are involved in cross-connections. In the case of the cross-connections of VC-3 or VC-4
services, the VC-3 or VC-4 services need to be converted into E1 services that have the same capacity. For
example, the cross-connections of one E3 service from a PL3 board to an IF board require the number of
licenses that are used for 21xE1. One VC-3 pass-through service between two IF boards requires the number
of licenses that are used for 42xE1. The 8xE1 SNCP services from two IF boards to one PO1 board require
the number of licenses that are used for 16xE1.
----End
Parameters
Parameter
Value Range
Default Value
Description
Service Type
SNCP
SNCP
Level
VC12
Revertive Mode
Non-Revertive,
Revertive
Non-Revertive
Issue 02 (2010-09-24)
13-11
Parameter
Value Range
Default Value
Description
Direction
Unidirectional,
Bidirectional
Bidirectional
Hold-off Time
(100ms)
0 to 100
WTR Time(s)
300 to 720
600
Source Slot
Source VC4
13-12
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Source Timeslot
Range(e.g.1,3-6)
Sink Slot
Sink VC4
Sink Timeslot
Range(e.g.1,3-6)
Configure SNCP
Tangent Ring
Checked,
Unchecked
Unchecked
Issue 02 (2010-09-24)
13-13
Parameter
Value Range
Default Value
Description
Activate
Immediately
Yes, No
Yes
Postrequisite
If Direction is set to Unidirectional, the cross-connection only in the SNCP receive direction
is created. Hence, you need to configure a unidirectional cross-connection between the service
and the working trail, and later, a unidirectional cross-connection between the service and the
protection trail.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
An SNCP protection group at the VC-4 level must be configured.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Protection
Configuration > SNCP Service Control from the Function Tree.
Step 2 Select the SNCP protection group. Double-click Initiation Condition to which the working
service corresponds.
The system displays the Initiation Condition dialog box.
Step 3 Select SD switching conditions. Then, click OK.
Step 4 Select the SNCP protection group. Double-click Initiation Condition to which the protection
service corresponds.
The system displays the Initiation Condition dialog box.
13-14
Issue 02 (2010-09-24)
Parameters
Parameter
Value Range
Default Value
Description
UNEQ
Selected, Not
selected
Not selected
TIM
Selected, Not
selected
Not selected
SD
Selected, Not
selected
Not selected
EXC
Selected, Not
selected
Not selected
NOTE
It is recommended that you set Initiation Condition of the working service to be the same as Initiation
Condition of the protection service.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The cross-connections of the point-to-point service must be configured and the point-to-point
service is not used.
Issue 02 (2010-09-24)
13-15
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > SDH
Service Configuration from the Function Tree.
Step 2 Query the data.
1.
Click Query.
Then, the Confirm dialog box is displayed, prompting This operation will query service
at the NE and update service date at the NM. Are you sure to continue?.
2.
Click OK.
Then, the Operation Result dialog box is displayed, prompting Operation succeeded.
3.
Click Close.
Step 3 Select the cross-connection of the point-to-point service that needs to be deleted in CrossConnection.
Step 4 Deactivate the service.
1.
Click Deactivate.
Then, the Confirm dialog box is displayed, prompting Are you sure to deactivate all
selected services (only for activated services)?.
2.
Click OK. Another Confirm dialog box is displayed, prompting This services of the NE
will be cleared by this operation. Are you sure to continue?.
3.
Click OK.
Then, the Operation Result dialog box is displayed, prompting Operation succeeded.
4.
Click Close.
Click Delete.
Then, the Confirm dialog box is displayed, prompting Are you sure to delete all the
selected services (only for inactive services)?.
2.
Click OK.
Then, the Operation Result dialog box is displayed, prompting Operation succeeded.
3.
Click Close.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The cross-connections of the service must be configured and the service is not be used.
13-16
Issue 02 (2010-09-24)
Procedure
Step 1 In the NE Explorer, select the NE and then choose Configuration > SDH Service
Configuration from the Function Tree.
Step 2 Query the data.
1.
Click Query.
Then, the Confirm dialog box is displayed, prompting This operation will query service
at the NE and update service date at the NM. Are you sure to continue?.
2.
Click OK.
Then, the Operation Result dialog box is displayed, prompting Operation succeeded.
3.
Click Close.
Step 3 Select the cross-connection of the SNCP service that needs to be deleted in CrossConnection.
Step 4 Deactivate the service.
1.
Click Deactivate.
Then, the Confirm dialog box is displayed, prompting Are you sure to deactivate all
selected services (only for activated services?).
2.
Click OK. Another Confirm dialog box is displayed, prompting This services of the NE
will be cleared by this operation. Are you sure to continue?.
3.
Click OK.
Then, the Operation Result dialog box is displayed, prompting Operation succeeded.
4.
Click Close.
Click Delete.
Then, the OK dialog box is displayed, prompting Are you sure to delete all the selected
services (only for inactive services)?.
2.
Click OK.
Then, the Operation Result dialog box is displayed, prompting Operation succeeded.
3.
Click Close.
Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > SDH Service Configuration from
the Function Tree.
Issue 02 (2010-09-24)
13-17
Step 2 Optional: Click Query to query the cross-connection services from the NE.
Step 3 Click Create SNCP and the Create SNCP Service dialog box is displayed.
Step 4 Set the Service Type, Level, Revertive Mode, Direction, Hold-off Time and WTR Time. Set
the Working Service and Protection Service of SNCP.
Step 5 Click OK.
----End
Sample Configuration
In Figure 13-4, NE1, NE2, NE3 and NE4 comprise a unidirectional SNCP ring, and NE4 and
NE5 comprise a unprotected chain. The SNCP ring transmits services by fiber, and the
unprotected chain transmits services by microwave.
13-18
Issue 02 (2010-09-24)
East
West
NE 2
East
STM-1
SNCP Ring
NE 4
NE 5
West
East
West
East
NE 3
Four bidirectional E1 services are transmitted between NE1 and NE5. The services use the first
through fourth VC12 timeslots of a tributary board, the first through fourth VC12 timeslots of
an intermediate frequency board, and the first through fourth VC12 timeslots in the first VC4
of a line board.
The E1 services are bidirectional. The service from NE1 to NE5 and the service from NE5 to
NE1 use diverse routes.
l
When the network is normal, the service flow between NE1 and NE5 is as follows: E1
tributary board at NE1east line board at NE1west line board at NE2east line board
at NE2west line board at NE3east line board at NE3west line board at NE4
intermediate frequency board at NE4intermediate frequency board at NE5tributary
board at NE5
When the network is normal, the service flow between NE5 and NE1 is as follows: E1
tributary board at NE5intermediate frequency board at NE5intermediate frequency
board at NE4east line board at NE4west line board at NE1tributary board at NE1
According to the service flow, you need to perform the configuration as follows:
l
Configure add or drop VC12 services for NE1. Configure a bidirectional SNCP service,
and select a east line board as the source of Working Service, an west line board as the
source of Protection Service, and a tributary board as the sink. The source and the sink
timeslots range from 1 to 4.
Configure pass-through VC12 services for NE2. Configure bidirectional services between
the west and the east line boards. The source and the sink timeslots range from 1 to 4.
Configure pass-through VC12 services for NE3. Configure bidirectional services between
the west and the east line boards. The source and the sink timeslots range from 1 to 4.
Configure add or drop VC12 services for NE4. Configure a bidirectional SNCP service,
and select a west line board as the source of Working Service, an east line board as the
source of Protection Service, and an intermediate frequency board as the sink. The source
and the sink timeslots range from 1 to 4.
Issue 02 (2010-09-24)
13-19
Configure add or drop VC12 services for NE5. The source and the sink timeslots of the
bidirectional services between the intermediate frequency board and the tributary board
range from 1 to 4.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The unidirectional cross-connection of non-protection services must be configured and the
source of the cross-connection must be a line board.
Background Information
When this task is performed to convert a non-protection service into an SNCP service, the
original services are not interrupted.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > SDH
Service Configuration from the Function Tree.
Step 2 Optional: Query the data.
1.
Click Query.
Then, the Confirm dialog box is displayed, prompting This operation will query service
at the NE and update service data at the NM. Are you sure to continue?.
2.
Click OK.
Then, the Operation Result dialog box is displayed, prompting Operation Succeeded.
13-20
Issue 02 (2010-09-24)
3.
Click Close.
Issue 02 (2010-09-24)
13-21
Parameters
Parameter
Value Range
Default Value
Description
Revertive Mode
Non-Revertive,
Revertive
Non-Revertive
Hold-off Time
(100ms)
0 to 100
WTR Time(s)
300 to 720
600
Source Slot
Source VC4
13-22
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Source Timeslot
Range(e.g.1,3-6)
Sink Slot
Sink VC4
Sink Timeslot
Range(e.g.1,3-6)
Postrequisite
The SNCP service after the conversion is the SNCP service only in the receive direction. Later,
you need to configure a unidirectional cross-connection between the service and the working
trail, and a unidirectional cross-connection between the service and the protection trail. The non-
Issue 02 (2010-09-24)
13-23
protection service can be converted into the SNCP service both in the receive direction and the
transmit direction only after the configuration.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The current service is transmitted in the working path.
The SNCP cross-connection in the receive direction must be configured.
Background Information
When this task is performed to convert an SNCP service into a non-protection service, the
original services are not interrupted.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > SDH
Service Configuration from the Function Tree.
Step 2 In the Auto-Created Cross-Connection pane, select the cross-connection. Right-click and
choose Convert to Non-Protection Service from the shortcut menu.
Step 3 Choose Working or Protection from the displayed menu.
Step 4 Then, the Prompt dialog box is displayed, prompting If the SNCP service is converted into a
non-protection service, the service may be interrupted. Are you sure to continue?.
Step 5 Click OK.
----End
Postrequisite
You need to delete the unidirectional cross-connection between the service and the working path
or the unidirectional cross-connection between the service and the protection path. The SNCP
service can be converted into the non-protection service both in the receive direction and the
transmit direction only after the deletion.
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The required SDH interface boards must be added.
Procedure
Step 1 Select the SDH interface board from the Object Tree in the NE Explorer. Choose
Configuration > Overhead Management > Regenerator Section Overhead from the
Function Tree.
Step 2 Set the J0 byte.
1.
2.
3.
Click OK.
Issue 02 (2010-09-24)
13-25
Parameters
Parameter
Value Range
Default Value
Description
J0 to Be Sent
([Mode]Content)
[16 Byte]HuaWei
SBS
J0 to Be Received
([Mode]Content)
Disable
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The required line boards must be added.
Procedure
Step 1 Select the line board from the Object Tree in the NE Explorer. Choose Configuration >
Overhead Management > VC4 Path Overhead from the Function Tree.
Step 2 Optional: Set the J1 byte.
13-26
1.
2.
3.
Issue 02 (2010-09-24)
4.
Click OK.
5.
Click Apply.
Then, a prompt box is displayed. Confirm the operations in this prompt box.
6.
Click OK.
2.
Then, a prompt box is displayed. Confirm the operations in this prompt box.
3.
Click OK.
4.
Click Apply.
2.
3.
Click Apply.
Then, a prompt box is displayed. Confirm the operations in this prompt box.
4.
Click OK.
----End
Issue 02 (2010-09-24)
13-27
Parameters
Parameter
Value Range
Default Value
Description
J1 to Be Sent
([Mode]Content)
[16 Byte]HuaWei
SBS
J1 to Be Received
([Mode]Content)
Disable
C2 to Be Sent
13-28
(0x00)Unequipped,
(0x01)Reserved,
(0x02) TUG
Structure, (0x03)
Locked TU-n,
(0x04)34M/45M
into C-3, (0x05)
Experimental
Mapping, (0x12)
140M into C-4
asynchronization,
(0x13)ATM
Mapping, (0x14)
MAN DQDB
Mapping, (0x15)
FDDI Mapping,
(0x16)HDLC/PPP
Mapping, (0x17)
Reserved for Special
Purpose, (0x18)
HDLC/LAPS
Mapping, (0x19)
Reserved for Special
Purpose, (0x1A)
10G Ethernet
Frame, (0x1B)GFP
Mapping, (0xCF)
Reserved, (0xE1)
Reserved, (0xFC)
Reserved, (0xFE)O.
(0x02) TUG
Structure
Issue 02 (2010-09-24)
Parameter
Value Range
C2 to Be Received
VC4 Overhead
Termination
Auto, PassThrough,
Termination
Default Value
Description
If the local NE reports the HP_SLM alarm,
set this parameter according to the C2 byte
to be transmitted from the remote NE.
Auto
l When this parameter is set to PassThrough, the local NE detects the VC-4
overheads (the C2 byte is not detected)
and then forwards the original
overheads.
l When this parameter is set to
Termination, the local NE detects the
VC-4 overheads (the C2 byte is not
detected) and then generates new VC-4
overheads according to the board
settings.
l When this parameter is set to Auto, the
VC-4 overhead termination of VC-4
pass-through services is Pass-Through
and the overhead termination of the
VC-3/VC-12 services is Termination.
l It is recommended that this parameter
takes the default value.
Issue 02 (2010-09-24)
13-29
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The corresponding E3/T3 interface board or Ethernet board must be added.
Procedure
Step 1 Select the E3/T3 interface board or Ethernet board from the Object Tree in the NE Explorer.
Choose Configuration > Overhead Management > VC3 Path Overhead from the Function
Tree.
Step 2 Optional: Set the J1 byte.
1.
2.
3.
4.
Click OK.
5.
Click Apply.
Then, a prompt box is displayed. Confirm the operations in this prompt box.
6.
Click OK.
13-30
1.
2.
Issue 02 (2010-09-24)
Then, a prompt box is displayed. Confirm the operations in this prompt box.
3.
Click OK.
4.
Click Apply.
----End
Parameters
Parameter
Value Range
Default Value
Description
J1 to Be Sent
([Mode]Content)
[16 Byte]HuaWei
SBS
J1 to Be Received
([Mode]Content)
Disable
C2 to Be Sent
Issue 02 (2010-09-24)
(0x00)Unequipped,
(0x01)Reserved,
(0x02) TUG
Structure, (0x03)
Locked TU-n,
(0x04)34M/45M
into C-3, (0x05)
Experimental
Mapping, (0x12)
140M into C-4
asynchronization,
(0x13)ATM
Mapping, (0x14)
MAN DQDB
Mapping, (0x15)
FDDI Mapping,
(0x16)HDLC/PPP
Mapping, (0x17)
Reserved for Special
Purpose, (0x18)
HDLC/LAPS
Mapping, (0x19)
(0x04)34M/45M
into C-3 (E3/T3
interface boards)
(0x02) TUG
Structure (Ethernet
boards)
13-31
Parameter
Value Range
C2 to Be Received
Default Value
Description
If the local NE reports the LP_TIM or
LP_TIM_VC3 alarm, set this parameter
according to the C2 byte to be transmitted
from the remote NE.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The corresponding E1 interface board or Ethernet board must be added.
Procedure
Step 1 Select the E1 interface board or Ethernet board from the Object Tree in the NE Explorer. Choose
Configuration > Overhead Management > VC12 Path Overhead from the Function Tree.
Step 2 Optional: Set the J2 byte.
1.
13-32
Issue 02 (2010-09-24)
2.
3.
4.
Click OK.
5.
Click Apply.
Then, a prompt box is displayed. Confirm the operations in this prompt box.
6.
Click OK.
2.
3.
Click Apply.
Then, a prompt box is displayed. Confirm the operations in this prompt box.
4.
Click OK.
----End
Parameters
Parameter
Value Range
Default Value
Description
J2 to Be Sent
([Mode]Content)
[16 Byte]HuaWei
SBS
Issue 02 (2010-09-24)
13-33
Parameter
Value Range
Default Value
Description
J2 to Be Received
([Mode]Content)
Disable
V5 to Be
Transmitted
V5 to Be Received
(0x00)Unequipped
or SupervisoryUnequipped, (0x01)
Equipped-NonSpecific Payload,
(0x02)
Asynchronous,
(0x03)Bit
Synchronization,
(0x04)Byte
Synchronization,
(0x05)Retained
Signal Flag, (0x06)
O.181 Test Signal,
(0x07)VC_AIS
(0x02)
Asynchronous
Issue 02 (2010-09-24)
This topic describes how to configure the microwave service data of NE2 based on the parameters
of the service planning, by using the NMS.
13.7.5 Configuring NE3
This topic describes how to configure the microwave service data of NE3 based on the parameters
of the service planning, by using the NMS.
13.7.6 Configuring NE4
This topic describes how to configure the microwave service data of NE4 based on the parameters
of the service planning, by using the NMS.
13.7.7 Configuring NE5
NE5 is the OptiX RTN 600 that adopts the IDU 605. Therefore, the configuration of NE5 is not
contained in this manual.
NE1, NE2, and NE3 are the OptiX RTN 600 that is configured with IDU 620.
NE4 is the OptiX RTN 600 that is configured with IDU 610.
NE5 is the OptiX RTN 600 that is configured with IDU 605 1B.
The E1 services need to be converged from each NE to the STM-1 optical line board at the
client side. Table 13-1 lists the service requirements.
NE2
NE4
SDH
OptiX RTN 600
(IDU 610)
NE3
Issue 02 (2010-09-24)
NE5
13-35
Sink
NE1
NE2
NE3
NE4
NE5
8xE1
8xE1
8xE1
20xE1
2xE1
NE Attributes
Parameter
NE1
NE2
NE3
NE4
NE5
Equipment
Type
IDU 620
IDU 620
IDU 620
IDU 610
IDU 605
NE ID
101
102
103
104
105
Extended ID
9 (the same
as the default
value)
9 (the same
as the default
value)
9 (the same
as the default
value)
9 (the same
as the default
value)
9 (the same
as the default
value)
NE IP
129.9.0.101
129.9.0.102
129.9.0.103
129.9.0.104
129.9.0.105
13-36
Issue 02 (2010-09-24)
V-polarization NE2
14547MHz
(IDU 620)
Tx Hi
Tx Low
14967MHz
Tx Hi 14930 MHz
V-polarization
NE1
(IDU 620)
14510 MHz
Tx Low
Tx Low
14532 MHz
14952 MHz
NE3
(IDU 620)
V-polarization
NE5
(IDU 605)
Tx Hi 14930 MHz
H-polarization
Tx Hi
14510 MHz
Tx Low
Link 1
Link 2
Link 3
Link 4
TX High
NE1
NE3
NE4
NE3
TX Low
NE2
NE2
NE2
NE5
Transmit Frequency
of TX High Station
(MHz)
14930
14952
14967
14930
Transmit Frequency
of TX High Station
(MHz)
14510
14532
14547
14510
420
420
420
420
STM-1, 28MHz,
128QAM
16E1, 14MHz,
16QAM
22E1, 14MHz,
32QAM
2E1, 3.5MHz,
QPSK
Link Protection
Mode
1+1
1+0
1+0
1+0
Polarization
Directiona
V (vertical
polarization)
H ((horizontal
polarization)
V (vertical
polarization)
V (vertical
polarization)
NOTE
a: Information other than the polarization direction, which is not related to the link planning is not provided in this section.
Issue 02 (2010-09-24)
13-37
FAN
FAN
Slot 20
EXT
IF1A
Slot7
EXT
Slot8
EXT
IF1A
Slot5
EXT
SL1
Slot6
PXC
PXC
Slot3
EXT
PO1
Slot4
PXC
PXC
Slot1
SCC
SCC
Slot2
FAN
FAN
Slot 20
EXT
IF1A
Slot7
IF1A
EXT
Slot8
EXT
IF1A
Slot5
EXT
IF1A
Slot6
PXC
PXC
Slot3
EXT
PO1
Slot4
PXC
PXC
Slot1
SCC
SCC
Slot2
FAN
FAN
Slot 20
EXT
IF0A
Slot7
EXT
Slot8
EXT
IF1A
Slot5
EXT
Slot6
PXC
PXC
Slot3
EXT
PO1
Slot4
PXC
PXC
Slot1
SCC
SCC
Slot2
Slot3
IF1A
Slot4
PXC
Slot1
SCC
Slot2
13-38
PW
SCC
EOW
PF1
IF0
Slot 1
Slot 2
Slot 3
Slot 4
Slot 8
Issue 02 (2010-09-24)
NOTE
The ODU that is connected to the IF board in slot n occupies logical slot 10+n. The logical slot of the ODU is
not displayed in the board configuration diagram. In the case of the IDU 620, n ranges from 5 to 8. In the case
of the IDU 610, n is fixed to 4. In the case of the IDU 605, n can be 7 or 8.
NE1
NE2
Protection Group ID
Protection Type
Working Slot
Slot 5
Slot 5
Protection Slot
Slot 7
Slot 7
Revertive Mode
WTR Time
Information of IF Ports
Table 13-4 Information of IF ports (NE1 and NE2)
Parameter
IF
Attri
butes
ATP
C
NE1
NE2
5-IF1A (7-IF1A)
5-IF1A (7-IF1A)
6-IF1A
8-IF1A
Work Mode: 7
Work Mode: 7
Work Mode: 6
Work Mode: 10
Service Capacity:
STM-1
Service Capacity:
STM-1
Service Capacity:
16xE1
Service Capacity:
22xE1
Signal Bandwidth:
28 MHz
Signal Bandwidth:
28 MHz
Signal Bandwidth:
14 MHz
Signal Bandwidth:
14 MHz
Modulation:
128QAM
Modulation:
128QAM
Modulation:
16QAM
Modulation:
32QAM
Radio Link ID
101
101
102
103
Wayside Enable
Status
Enabled
Enabled
Not supported
Not supported
Wayside Input
Board
Slot 1
Slot 1
Enable Status
Enabled
Enabled
Enabled
Enabled
Radio Work
Mode
Issue 02 (2010-09-24)
13-39
Parameter
ATPC Automatic
Threshold Enable
Status
NE1
NE2
5-IF1A (7-IF1A)
5-IF1A (7-IF1A)
6-IF1A
8-IF1A
Enabled
Enabled
Enabled
Enabled
NE4
NE5
IF
Attri
butes
ATP
C
NE3
5-IF1A
7-IF0A
5-IF1A
8-IF0
Work Mode: 6
Work Mode: 18
Work Mode: 10
Work Mode: 18
Service Capacity:
16xE1
Service Capacity:
2xE1
Service Capacity:
22xE1
Service Capacity:
2xE1
Signal Bandwidth:
14 MHz
Signal Bandwidth:
3.5 MHz
Signal Bandwidth:
14 MHz
Signal Bandwidth:
3.5 MHz
Modulation:
16QAM
Modulation:
QPSK
Modulation:
32QAM
Modulation:
QPSK
Radio Link ID
102
104
103
104
Wayside Enable
Status
Not supported
Not supported
Not supported
Not supported
Wayside Input
Board
Enable Status
Enabled
Enabled
Enabled
Enabled
ATPC Automatic
Threshold Enable
Status
Enabled
Enabled
Enabled
Enabled
Radio Work
Mode
Radio
Frequency
Properties
13-40
Transmission
Frequency
(MHz)
NE1
NE2
15-ODU (17ODU)
15-ODU (17ODU)
16-ODU
18-ODU
14930
14510
14532
14547
Issue 02 (2010-09-24)
Parameter
NE1
NE2
15-ODU (17ODU)
15-ODU (17ODU)
16-ODU
18-ODU
T/R Spacing
(MHz)
420
420
420
420
Power
Attributes
Transmit Power
(dBm)
10
10
10
10
Equipment
Attributes (The
equipment
attributes can be
planned but
cannot be set.)
Station Type
TX High
TX Low
TX Low
TX Low
NOTE
Note: The attributes of the main and standby ODUs on NE1 and NE2 are the same.
NE3
NE4
NE5
15-ODU
17-ODU
15-ODU
18-ODU
Transmission
Frequency
(MHz)
14952
14930
14967
14510
T/R Spacing
(MHz)
420
420
420
420
Power
Attributes
Transmit Power
(dBm)
10
10
10
10
Equipment
Attributes (The
equipment
attributes can be
planned but
cannot be set.)
Station Type
TX High
TX High
TX High
TX Low
Radio
Frequency
Properties
Issue 02 (2010-09-24)
13-41
NE1
Timeslot
VC4-1
6-SL1
VC12: 1-8
4-PO1:1-8
NE1
NE2
NE3
NE5
6-SL1 5-IF1A
5-IF1A 6-IF1A
5-IF1A 7-IF0A
VC12: 9-16
VC12: 9-16
4-PO1:1-8
VC12: 17-24
VC12: 17-24
VC12:1-8
VC4-1
4-PO1:1-8
VC12:9-10
4-SL1
VC12:25-26
VC12:25-26
8-IF0
VC12:1-2
4-PF1:1-2
4-SL1
Links-2: NE1 - NE2 - NE4
Station
Timeslot
VC4-1
NE1
NE2
6-SL1 5-IF1A
5-IF1A 8-IF1A
VC12: 27-46
VC12: 27-46
NE4
5-IF1A
VC12: 1-20
4-SL1
4-PD1:1-20
Add/Drop
Foward
NOTE
On the radio links of NE3, NE4, and NE5, the E1 signals are directly mapped into the timeslots
corresponding to the PDH radio frames. Figure 13-12 considers VC-12 timeslots as an example to illustrate
how the timeslots are allocated.
Figure 13-12 shows the timeslot allocation for the services between the NEs.
l
E1 services of NE1:
The services are added to/dropped from ports 1-8 of the PO1 board in slot 4 on NE1.
The E1 services occupy VC-12 timeslots 1-8 on the optical line of the SL1 board in slot
6 on NE1.
E1 services of NE2:
The services are added to/dropped from ports 1-8 of the PO1 board in slot 4 on NE2.
The services occupy VC-12 timeslots 9-16 on the radio link of the IF1A board in slot
5 on NE1 and on the radio link of the IF1A board in slot 5 on NE2.
The services are passed through between the IF1A board in slot 5 and the SL1 board in
slot 6 on NE1.
l
13-42
E1 services of NE3:
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
The services are added to/dropped from ports 1-8 of the PO1 board in slot 4 on NE3.
The services occupy VC-12 timeslots 1-8 on the radio link of the IF1A board in slot 6
on NE2 and on the radio link of the IF1A board in slot 5 on NE3.
The services are passed through between the IF1A board in slot 5 and the IF1A board
in slot 6 on NE2.
The services occupy VC-12 timeslots 17-24 on the radio link of the IF1A board in slot
5 on NE1 and on the radio link of the IF1A board in slot 5 on NE2.
The services are passed through between the IF1A board in slot 5 and the SL1 board in
slot 6 on NE1.
l
E1 services of NE4:
The services are added to/dropped from ports 1-20 of the PD1 board in slot 4 on NE4.
The services occupy VC-12 timeslots 1-20 on the radio link of the IF1A board in slot
8 on NE2 and on the radio link of the IF1A board in slot 5 on NE4.
The services are passed through between the IF1A board in slot 5 and the IF1A board
in slot 8 on NE2.
The services occupy VC-12 timeslots 27-46 on the radio link of the IF1A board in slot
5 on NE1 and on the radio link of the IF1A board in slot 5 on NE2.
The services are passed through between the IF1A board in slot 5 and the SL1 board in
slot 6 on NE1.
E1 services of NE5:
The services are added to/dropped from ports 1-2 of the PF1 board in slot 4 on NE5.
The services occupy VC-12 timeslots 1-2 on the radio link of the IF1A board in slot 7
on NE3 and on the radio link of the IF1A board in slot 8 on NE5.
The services are passed through between the IF1A board in slot 5 and the IF1A board
in slot 7 on NE3.
The services occupy VC-12 timeslots 9-10 on the radio link of the IF1A board in slot
6 on NE2 and on the radio link of the IF1A board in slot 5 on NE3.
The services are passed through between the IF1A board in slot 5 and the IF1A board
in slot 6 on NE2.
The services occupy VC-12 timeslots 25-26 on the radio link of the IF1A board in slot
5 on NE1 and on the radio link of the IF1A board in slot 5 on NE2.
The services are passed through between the IF1A board in slot 5 and the SL1 board in
slot 6 on NE1.
Issue 02 (2010-09-24)
13-43
Clock Information
Figure 13-13 Clock Synchronization Scheme
NE1
NE2
NE4
SDH
5-IF1A/7-IF1A/
Internal
6-SL1/Internal
5-IF1A/Internal
NE3
5-IF1A/Internal
Master clock
NE5
8-IF0/Internal
NE1
NE2
NE3
NE4
NE5
Cl
oc
k
So
ur
ce
First
Clock
Source
6-SL1
5-IF1A
5-IF1A
5-IF1A
8-IF0
Second
Clock
Source
Internal
Clock
Source
7-IF1A
Internal
Clock
Source
Internal
Clock
Source
Internal
Clock
Source
Third
Clock
Source
Internal
Clock
Source
Orderwire Information
Table 13-9 Orderwire information
13-44
Parameter
NE1
NE2
NE3
NE4
NE5
Telephone
No.
101
102
103
104
105
Call Waiting
Time (s)
Issue 02 (2010-09-24)
Parameter
NE1
NE2
NE3
NE4
NE5
Orderwire
Port
5-IF1A-1, 6SL1-1
5-IF1A-1, 7SL1-1
5-IF1A-1
8-IF0
Orderwire
Occupied
Bytes
E1
E1
E1
E1
E1
Prerequisite
You must be logged in to the NE.
You must be an NM user with "NE operator" authority or higher.
All the required boards must be added.
Procedure
Step 1 Modify the NE ID.
Set the parameters as follows:
l New ID: 101
l New Extended ID: 9
Step 2 Modify the IP address of an NE.
Set the parameters as follows:
l IP: 129.9.0.101
Step 3 Configure IF 1+1 protection.
1.
In the NE Explorer, select NE1 and then choose Configuration > Link Configuration
from the Function Tree.
2.
3.
Click New.
Then, the Create IF 1+1 Protection dialog box is displayed. Click OK.
Issue 02 (2010-09-24)
Parameter
Value Range
Description
Protection
Group ID
13-45
Parameter
Value Range
Description
Working Mode
HSB
Revertive Mode
Revertive
600
WTR Time(s)
Enable
Working Board
5-IF1A-1
Protection Board
7-IF1A-1
In the NE Explorer, select NE1 and then choose Configuration > Link Configuration
from the Function Tree.
2.
3.
Set the information about the 5-IF1A and 15-ODU on the radio link. After setting the
information about the 5-IF1A or 15-ODU on the radio link, click Apply.
Parameter
Value Range
Description
Work Mode
7,STM-1,28MH
z,128QAM
Link ID
101
13-46
Issue 02 (2010-09-24)
Parameter
Value Range
Description
ATPC Enable
Status
Enabled
TX Frequency
(MHz)
14930.0
T/R Spacing
(MHz)
420.0
TX Power
(dBm)
10.0
TX Status
unmute
In the NE Explorer, select the 5-IF1A and then choose Configuration > IF Interface from
the Function Tree.
2.
Click the IF Attributes tab. After setting the parameters, click Apply.
Parameter
Value Range
Description
Enabled
ATPC Automatic
Threshold Enable
Status
Enabled
In the NE Explorer, select NE1 and then choose Configuration > Cross-Connection
Configuration from the Function Tree.
2.
Click New. The Create SDH Service dialog box is displayed. After setting the parameters.
Then, click OK.
Issue 02 (2010-09-24)
13-47
Value Range
Description
Level
VC12
Direction
Bidirectional
Source
6-SL1
Source
Timeslot
Range(e.g.
1,3-6)
1-8
Sink
4-PO1
Sink Timeslot
Range(e.g.
1,3-6)
1-8
Value Range
Description
Level
VC12
Direction
Bidirectional
13-48
Source
5-IF1A
Source
Timeslot
Range(e.g.
1,3-6)
9-46
Sink
6-SL1
Issue 02 (2010-09-24)
Parameter
Value Range
Description
Sink Timeslot
Range(e.g.
1,3-6)
9-46
In the NE Explorer, select NE1 and then choose Configuration > Clock > Clock Source
Priority from the Function Tree.
2.
Click Create. The Add Clock Source dialog box is displayed. Select the clock sources.
Then, click OK.
3.
Parameter
Value Range
Description
Clock Source
6-SL1-1
or
to adjust the priority level of this
Select a clock source and click
clock source. Set Clock Source and Clock Source Priority Sequence(1 is the highest).
Then, click Apply.
Parameter
Value Range
Clock
Source
6-SL1-1
Internal
Clock Source
Clock
Source
Priority
Sequence(1
is the
highest)
Description
----End
Prerequisite
You must be logged in to the NE.
Issue 02 (2010-09-24)
13-49
Procedure
Step 1 Modify the NE ID.
Set the parameters as follows:
l New ID: 102
l New Extended ID: 9
Step 2 Modify the IP address of an NE.
Set the parameters as follows:
l IP: 129.9.0.102
Step 3 Configure IF 1+1 protection.
1.
In the NE Explorer, select NE2 and then choose Configuration > Link Configuration
from the Function Tree.
2.
3.
Click New.
Then, the Create IF 1+1 Protection dialog box is displayed. Click OK.
Parameter
Value Range
Description
Protection
Group ID
Working Mode
HSB
Revertive Mode
Revertive
WTR Time(s)
600
13-50
Issue 02 (2010-09-24)
Parameter
Value Range
Description
Enable Reverse
Switching
Enable
Working Board
5-IF1A-1
Protection Board
7-IF1A-1
In the NE Explorer, select NE2 and then choose Configuration > Link Configuration
from the Function Tree.
2.
3.
Set the information about the 5-IF1A and 15-ODU on the first radio link, the information
about the 6-IF1A and 16-ODU on the second radio link, and the information about the 8IF1A and 18-ODU on the third radio link. Then, click Apply.
l Set the parameters of the 5-IF1A and 15-ODU as follows.
Parameter
Value Range
Description
Work Mode
7,STM-1,28MH
z,128QAM
Link ID
101
Issue 02 (2010-09-24)
ATPC Enable
Status
Enabled
TX Frequency
(MHz)
14510.0
T/R Spacing
(MHz)
420.0
TX Power
(dBm)
10.0
13-51
Parameter
Value Range
Description
TX Status
unmute
Value Range
Description
Work Mode
6,16E1,14MHz,
16QAM
Link ID
102
ATPC Enable
Status
Enabled
TX Frequency
(MHz)
14532.0
T/R Spacing
(MHz)
420.0
TX Power
(dBm)
10.0
TX Status
unmute
13-52
Parameter
Value Range
Description
Work Mode
10,22E1,14MH
z,32QAM
Issue 02 (2010-09-24)
Parameter
Value Range
Description
Link ID
103
ATPC Enable
Status
Enabled
TX Frequency
(MHz)
14547.0
T/R Spacing
(MHz)
420.0
TX Power
(dBm)
10.0
TX Status
unmute
In the NE Explorer, select the 5-IF1A and then choose Configuration > IF Interface from
the Function Tree.
2.
Click the IF Attributes tab. After setting the parameters, click Apply.
3.
Issue 02 (2010-09-24)
Parameter
Value Range
Description
ATPC Enable
Status
Enabled
ATPC
Automatic
Threshold
Enable Status
Enabled
Repeat Step 5.1 to Step 5.2 to set the ATPC parameters of the 6-IF1A and 8-IF1A to the
same values. Click Apply.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
13-53
Parameter
Value Range
Description
ATPC Enable
Status
Enabled
ATPC
Automatic
Threshold
Enable Status
Enabled
In the NE Explorer, select NE2 and then choose Configuration > Cross-Connection
Configuration from the Function Tree.
2.
Click New. The Create SDH Service dialog box is displayed. After setting the parameters.
Then, click OK.
l Configure the cross-connections of the add/drop services as follows.
Parameter
Value Range
Description
Level
VC12
Direction
Bidirectional
Source
5-IF1A
Source
Timeslot
Range(e.g.
1,3-6)
9-16
Sink
4-PO1
Sink Timeslot
Range(e.g.
1,3-6)
1-8
l Configure the cross-connections of the services that pass through NE3 as follows.
13-54
Issue 02 (2010-09-24)
Parameter
Value Range
Description
Level
VC12
Direction
Bidirectional
Source
5-IF1A
Source
Timeslot
Range(e.g.
1,3-6)
17-26
Sink
6-IF1A
Sink Timeslot
Range(e.g.
1,3-6)
1-10
l Configure the cross-connections of the services that pass through NE4 as follows.
Parameter
Value Range
Description
Level
VC12
Direction
Bidirectional
Issue 02 (2010-09-24)
Source
5-IF1A
Source
Timeslot
Range(e.g.
1,3-6)
27-46
Sink
8-IF1A
13-55
Parameter
Value Range
Description
Sink Timeslot
Range(e.g.
1,3-6)
1-20
In the NE Explorer, select NE2 and then choose Configuration > Clock > Clock Source
Priority from the Function Tree.
2.
Click Create. The Add Clock Source dialog box is displayed. Select the clock sources.
Then, click OK.
3.
Parameter
Value Range
Description
Clock Source
5-IF1A-1
7-IF1A-1
or
to adjust the priority level of this
Select a clock source and click
clock source. Set Clock Source and Clock Source Priority Sequence(1 is the highest).
Then, click Apply.
Paramet
er
Value Range
Clock
Source
5-IF1A-1
7-IF1A-1
Internal
Clock
Source
Clock
Source
Priority
Sequence
(1 is the
highest)
Description
----End
13-56
Issue 02 (2010-09-24)
Prerequisite
You must be logged in to the NE.
You must be an NM user with "NE operator" authority or higher.
All the required boards must be added.
Procedure
Step 1 Modify the NE ID.
Set the parameters as follows:
l New ID: 103
l New Extended ID: 9
Step 2 Modify the IP address of an NE.
Set the parameters as follows:
l IP: 129.9.0.103
Step 3 Configure the IF/ODU information of a radio link.
1.
In the NE Explorer, select NE3 and then choose Configuration > Link Configuration
from the Function Tree.
2.
3.
Set the information about the 5-IF1A and 15-ODU on one radio link and the information
about the 7-IF0A and 17-UDU on the other radio link. Then, click Apply.
l Set the parameters of the 5-IF1A and 15-ODU as follows.
Parameter
Value Range
Description
Work Mode
6,16E1,14MHz,
16QAM
Link ID
102
Issue 02 (2010-09-24)
ATPC Enable
Status
Enabled
TX Frequency
(MHz)
14952.0
13-57
Parameter
Value Range
Description
T/R Spacing
(MHz)
420.0
TX Power
(dBm)
10.0
TX Status
unmute
Value Range
Description
Work Mode
18,2E1,3.5MHz
,QPSK
Link ID
104
ATPC Enable
Status
Enabled
TX Frequency
(MHz)
14930.0
T/R Spacing
(MHz)
420.0
TX Power
(dBm)
10.0
TX Status
unmute
13-58
Issue 02 (2010-09-24)
1.
In the NE Explorer, select the 5-IF1A and then choose Configuration > IF Interface from
the Function Tree.
2.
Click the IF Attributes tab. After setting the parameters, click Apply.
3.
Parameter
Value Range
Description
ATPC Enable
Status
Enabled
ATPC
Automatic
Threshold
Enable Status
Enabled
Repeat Step 4.1 to Step 4.2 to set the ATPC parameters of the 7-IF0A to the same values.
Click Apply.
Parameter
Value Range
Description
ATPC Enable
Status
Enabled
ATPC
Automatic
Threshold
Enable Status
Enabled
In the NE Explorer, select NE3 and then choose Configuration > Clock > CrossConnection Configuration from the Function Tree.
2.
Click New. The Create SDH Service dialog box is displayed. After setting the parameters.
Then, click OK.
l Configure the cross-connections of the add/drop services as follows.
Parameter
Value Range
Description
Level
VC12
Issue 02 (2010-09-24)
13-59
Parameter
Value Range
Description
Direction
Bidirectional
Source
5-IF1A
Source
Timeslot
Range(e.g.
1,3-6)
1-8
Sink
4-PO1
Sink Timeslot
Range(e.g.
1,3-6)
1-8
l Configure the cross-connections of the services that pass through NE5 as follows.
Parameter
Value Range
Description
Level
VC12
Direction
Bidirectional
13-60
Source
5-IF1A
Source
Timeslot
Range(e.g.
1,3-6)
9-10
Sink
7-IF0A
Sink Timeslot
Range(e.g.
1,3-6)
1-2
Issue 02 (2010-09-24)
In the NE Explorer, select NE3 and then choose Configuration > Clock > Clock Source
Priority from the Function Tree.
2.
Click Create. The Add Clock Source dialog box is displayed. Select the clock sources.
Then, click OK.
3.
Parameter
Value Range
Description
Clock Source
5-IF1A-1
Value Range
Description
Clock
Source
5-IF1A-1
Internal
Clock Source
Clock
Source
Priority
Sequence(1
is the
highest)
----End
Prerequisite
You must be logged in to the NE.
You must be an NM user with "NE operator" authority or higher.
All the required boards must be added.
Procedure
Step 1 Modify the NE ID.
Issue 02 (2010-09-24)
13-61
In the NE Explorer, select NE4 and then choose Configuration > Link Configuration
from the Function Tree.
2.
3.
Set the information about the 4-IF1A and 14-ODU on the radio link. Then, click Apply.
Parameter
Value Range
Description
Work Mode
10,22E1,14MHz
,32QAM
Link ID
103
ATPC Enable
Status
Enabled
TX Frequency
(MHz)
14967.0
T/R Spacing
(MHz)
420.0
TX Power
(dBm)
10.0
TX Status
unmute
13-62
In the NE Explorer, select the 5-IF1A and then choose Configuration > IF Interface from
the Function Tree.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
2.
Click the IF Attributes tab. After setting the parameters, click Apply.
Parameter
Value Range
Description
ATPC Enable
Status
Enabled
ATPC
Automatic
Threshold
Enable Status
Enabled
In the NE Explorer, select NE4 and then choose Configuration > Cross- Connection
Configuration from the Function Tree.
2.
Click New. Then, the Create SDH Service dialog box is displayed. Configure the crossconnections of the add/drop services. Click OK.
Parameter
Value Range
Description
Level
VC12
Direction
Bidirectional
Source
4-IF1A
Source
Timeslot Range
(e.g.1,3-6)
1-20
Sink
3-PD1
Sink Timeslot
Range(e.g.
1,3-6)
1-20
13-63
l Phone 1: 104
l Orderwire Port: 4-IF1A-1
Step 7 Configure the clock source.
1.
In the NE Explorer, select NE4 and then choose Configuration > Clock > Clock Source
Priority from the Function Tree.
2.
Click Create. The Add Clock Source dialog box is displayed. Select the clock sources.
Then, click OK.
3.
Parameter
Value Range
Description
Clock Source
4-IF1A-1
Value Range
Description
Clock
Source
4-IF1A-1
Internal
Clock Source
Clock
Source
Priority
Sequence(1
is the
highest)
----End
Issue 02 (2010-09-24)
According to the service requirements and the equipment specifications that are shown in the
networking diagram, the network planning department can plan all the services of the NEs. In
the following example, the service planning covers all the parameter information required for
configuring the NEs.
13.8.3 Configuring NE1
You can configure the data of NE1 based on the parameters of the engineering planning, by
using the NMS.
13.8.4 Configuring NE2
You can configure the data of NE2 based on the parameters of the service planning, by using
the NMS.
NE1and NE2 are the OptiX RTN 600 that is configured with the IDU 605 2B.
NE1
(IDU 605 2B)
NE2
(IDU 605 2B)
NE Attributes
Issue 02 (2010-09-24)
Parameter
NE1
NE2
Equipment Type
IDU 605 2B
IDU 605 2B
NE ID
101
102
13-65
Parameter
NE1
NE2
Extended ID
NE IP
129.9.0.101
129.9.0.102
NE1
(IDU 605 2B)
NE2
(IDU 605 2B)
Tx Hi
14952 MHz
14532 MHz
Tx Low
Link
TX High Station
NE1
TX Low Station
NE2
14952
14532
420
Work Mode
16E1,28MHz,QPSK
1+1 HSB
Polarization Directiona
V (vertical polarization)
NOTE
a: Information other than the polarization direction, which is not related to the link planning is not provided in this section.
13-66
Issue 02 (2010-09-24)
Board Configuration
Figure 13-16 IDU board configuration (NE1 and NE2)
IDU 605 2B
PW
SCC
EOW
PH1
IF0
IF0
Slot 1
Slot 2
Slot 3
Slot 4
Slot 7
Slot 8
NOTE
The ODU that is connected to the IF board in slot n occupies logical slot 10+n. The logical slot of the ODU is
not displayed in the board configuration diagram. In the case of the IDU 605, n can be 7 or 8.
NE1
NE2
Protection group ID
Protection Type
Active board
Slot 8
Slot 8
Protection board
Slot 7
Slot 7
Revertive Mode
Recovery time
Information of IF Ports
Table 13-12 Information of IF ports
Parameter
IF
Attributes
ATPC
NE1
NE2
8-IF0 (7-IF0)
8-IF0 (7-IF0)
Work Mode: 5
Work Mode: 5
Modulation: QPSK
Modulation: QPSK
Radio Link ID
101
101
Enable status
Enabled
Enabled
Issue 02 (2010-09-24)
13-67
Parameter
NE1
NE2
8-IF0 (7-IF0)
8-IF0 (7-IF0)
-40
-40
-60
-60
NE1
NE2
18-ODU (17-ODU)
18-ODU (17-ODU)
Transmission Frequency
(MHz)
14952
14532
420
420
Power Properties
10
10
Station Type
TX High
TX Low
Radio Frequency
Properties
NOTE
Note: The attributes of the main and standby ODUs on NE1 and NE2 are the same.
NE1
NE2
E1 ports
E1-1 to E1-12
E1-1 to E1-12
Orderwire Information
Table 13-15 Orderwire information
13-68
Parameter
NE1
NE2
Telephone No.
101
102
5 seconds
5 seconds
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
You must be logged in to the NE.
Procedure
Step 1 Modify the NE ID.
Set the parameters as follows:
l New ID: 101
l New Extended ID: 9
Step 2 Modify the IP address of an NE.
Set the parameters as follows:
l IP: 129.9.0.101
Step 3 Modify the IF 1+1 protection.
1.
In the NE Explorer, select NE1 and then choose Configuration > Link Configuration
from the Function Tree.
2.
Click the IF 1+1 Protection tab. After setting the parameters, click Apply.
Parameter
Value Range
Description
Working Mode
HSB
Revertive
Mode
Revertive
Issue 02 (2010-09-24)
13-69
Parameter
Value Range
Description
WTR Time(s)
600
Enable Reverse
Switching
Enable
In the NE Explorer, select NE1 and then choose Configuration > Link Configuration
from the Function Tree.
2.
3.
Set the information about the 8-IF0. Click Apply. Set the information about the 18-ODU.
Click Apply.
Parameter
Value Range
Description
Work Mode
5,16E1,28MHz,
QPSK
Link ID
101
13-70
Issue 02 (2010-09-24)
Parameter
Value Range
Description
ATPC Enable
Status
Enabled
TX Frequency
(MHz)
14952.0
T/R Spacing
(MHz)
420.0
TX Power
(dBm)
10.0
TX Status
unmute
In the NE Explorer, select the 8-IF0 board and then choose Configuration > IF
Interface from the Function Tree.
2.
Click the ATPC Attributes tab. After setting the parameters, click Apply.
Issue 02 (2010-09-24)
Parameter
Value Range
Description
ATPC Enable
Status
Enabled
ATPC Upper
Threshold
(dBm)
-40.0
13-71
Parameter
Value Range
ATPC Lower
Threshold
(dBm)
-60.0
Description
automatic ATPC lower threshold is not less
than 5 dB.
NOTE
The ATPC attributes should be set to the same value at both ends of a radio link.
In the NE Explorer, select NE1 and then choose Configuration > Cross-Connection
Configuration from the Function Tree.
2.
Select the used E1 port. After setting the parameters, click Apply.
Parameter
Value Range
Description
E1-1 to E1-12
Selected
Prerequisite
You must be an NM user with "NE operator" authority or higher.
You must be logged in to the NE.
Procedure
Step 1 Modify the NE ID.
Set the parameters as follows:
13-72
Issue 02 (2010-09-24)
In the NE Explorer, select NE2 and then choose Configuration > Link Configuration
from the Function Tree.
2.
Click the IF 1+1 Protection tab. After setting the parameters, click Apply.
Parameter
Value Range
Description
Working Mode
HSB
Revertive
Mode
Revertive
WTR Time(s)
600
Enable Reverse
Switching
Enable
Issue 02 (2010-09-24)
13-73
In the NE Explorer, select NE2 and then choose Configuration > Link Configuration
from the Function Tree.
2.
3.
Set the information about the 8-IF0. Click Apply. Set the information about the 18-ODU.
Click Apply.
Parameter
Value Range
Description
Work Mode
5,16E1,28MHz,
QPSK
Link ID
101
ATPC Enable
Status
Enabled
TX Frequency
(MHz)
14532.0
T/R Spacing
(MHz)
420.0
TX Power
(dBm)
10.0
TX Status
unmute
13-74
Issue 02 (2010-09-24)
In the NE Explorer, select the 8-IF0 and then choose Configuration > IF Interface from
the Function Tree.
2.
Click the ATPC Attributes tab. After setting the parameters, click Apply.
Parameter
Value Range
Description
ATPC Enable
Status
Enabled
ATPC Upper
Threshold
(dBm)
-40.0
ATPC Lower
Threshold
(dBm)
-60.0
NOTE
Each of the ATPC parameters must be set to the same value at the two ends of a radio link.
In the NE Explorer, select NE2 and then choose Configuration > Cross-Connection
Configuration from the Function Tree.
2.
Select the used E1 port. After setting the parameters, click Apply.
Parameter
Value Range
Description
E1-1 to E1-12
Selected
13-75
13-76
NE1, NE2, and NE3 are the OptiX RTN 600 that is configured with IDU 620.
NE4 is the OptiX RTN 600 that is configured with IDU 610.
NE5 is the OptiX RTN 600 that is configured with IDU 605 1B.
The E1 services need be converged from each NE to the STM-1 optical line board at the
client side. The service requirement in NE5 is 2xE1.
Issue 02 (2010-09-24)
NE2
NE4
SDH
OptiX RTN 600
(IDU 610)
NE3
NE5
NE Attributes
Parameter
NE5
Equipment Type
IDU 605 1A
NE ID
105
Extended ID
NE IP
129.9.0.105
Issue 02 (2010-09-24)
13-77
V-polarization NE2
14547MHz
(IDU 620)
Tx Hi
Tx Low
14967MHz
Tx Hi 14930 MHz
V-polarization
NE1
(IDU 620)
14510 MHz
Tx Low
Tx Low
14532 MHz
14952 MHz
NE3
(IDU 620)
V-polarization
NE5
(IDU 605)
Tx Hi 14930 MHz
H-polarization
Tx Hi
14510 MHz
Tx Low
Table 13-16 Planning information of the radio link between NE3 and NE5
Parameter
Link 4
TX High
NE3
TX Low
NE5
14930
14510
420
Work Mode
2E1,3.5MHz,QPSK
1+0
Polarization Directiona
V (vertical polarization)
NOTE
a: Information other than the polarization direction, which is not related to the link planning is not provided in this section.
Board Configuration
Figure 13-19 IDU board configuration (NE5)
13-78
PW
SCC
EOW
PF1
IF0
Slot 1
Slot 2
Slot 3
Slot 4
Slot 8
Issue 02 (2010-09-24)
NOTE
The ODU that is connected to the IF board in slot n occupies logical slot 10+n. The logical slot of the ODU is
not displayed in the board configuration diagram.
NE5
8-IF0
IF Attributes
Work Mode: 18
Service Capacity: 2xE1
Signal Bandwidth: 3.5 MHz
Modulation: QPSK
ATPC
Radio Link ID
104
Enable status
Enabled
-45
-70
NE5
18-ODU
14510
420
Power Properties
10
Station Type
TX Low
Issue 02 (2010-09-24)
13-79
NE5
E1 ports
E1-1 to E1-2
Orderwire Information
Table 13-20 Orderwire information
Parameter
NE5
Telephone No.
105
5 seconds
Prerequisite
You must be an NM user with "NE operator" authority or higher.
You must be logged in to the NE.
Procedure
Step 1 Modify the NE ID.
Set the parameters as follows:
l New ID: 105
l New Extended ID: 9
Step 2 Modify the IP address of an NE.
Set the parameters as follows:
l IP: 129.9.0.105
13-80
Issue 02 (2010-09-24)
In the NE Explorer, select NE5 and then choose Configuration > Link Configuration
from the Function Tree.
2.
3.
Set the information about the 8-IF0. Click Apply. Set the information about the 18-ODU.
Click Apply.
Parameter
Value Range
Description
Work Mode
18,2E1,3.5MHz,
QPSK
Link ID
104
ATPC Enable
Status
Enabled
TX Frequency
(MHz)
14510.0
T/R Spacing
(MHz)
420.0
TX Power
(dBm)
10.0
TX Status
unmute
Issue 02 (2010-09-24)
13-81
1.
In the NE Explorer, select NE5 and then choose Configuration > Service
Configuration from the Function Tree.
2.
13-82
Issue 02 (2010-09-24)
14
Issue 02 (2010-09-24)
14-1
Issue 02 (2010-09-24)
need to create the cross-connections. When Ethernet services are transmitted over the Hybrid
microwave, you need not configure the encapsulation and mapping in the VCTRUNKs or the
cross-connections between the VCTRUNKs and line timeslots.
14-3
To implement the VLAN function, the IEEE 802.1q protocol defines the Ethernet frame format
that contains the VLAN information. Compared with the ordinary Ethernet frame, the frame
with the format defined by the IEEE 802.1q protocol is added with a four-byte header.
To implement VLAN mesting (QinQ), the IEEE 802.1ad protocol defines two VLAN tag types.
See Figure 14-1. two VLAN tag types are defined to differentiate the services on the client side
and the services on the supplier service side.
l
The VLAN tag used on the client side is represented as C-VLAN, of which the frame format
is the same as the frame format defined by the IEEE 802.1q protocol.
The VLAN tag used on the supplier service side is represented as S-VLAN.
VLAN
6 bytes
Length/Type
Data
FCS Check
Character
2 bytes
Variable
length
4 bytes
Length/Type
Data
FCS Check
Character
2 bytes
Variable
length
4 bytes
4 bytes
C-VLAN
6 bytes
4 bytes
S-VLAN
6 bytes
C-VLAN
4 bytes
Length/Type
4 bytes
2 bytes
Data
FCS Check
Character
Variable
length
4 bytes
The length of the data field is variable. maximum length of the data field depends on the
maximum frame length that the ports of the equipment support.
The four-byte S-VLAN or C-VLAN field is divided into two sub-fields: the tag protocol ID
(TPID) and the tag control Information (TCI).
Both the TPID and TCI consist of two bytes. See Figure 14-2.
Figure 14-2 Positions of the TPID and TCI in the frame structure
S-VLAN
14-4
TCI
C-VLAN
TPID
TCI
Length/Type
2 bytes
Data
Variable
length
FCS Check
Character
4 bytes
Issue 02 (2010-09-24)
TPID structure
The TPID consists of two bytes and indicates the VLAN tag type. TPID of the C-VLAN is
always 0x8100 whereas the TPID of the S-VLAN can be customized. Refer to Table 14-1.
Table 14-1 Tag types defined by using the TPID
Tag Type
Name
Value
C-VLAN tag
0x8100
S-VLAN tag
Customizable
NOTE
The IEEE 802.1ad specifies the TPID of the S-VLAN to 0x88a8. In actual application, the setting of TPID
for the S-VLAN tag varies according to the equipment manufacturer. To ensure compatibility between
interconnected equipment, it is recommended that you set the TPIDs of the S-VLAN tags of the
interconnected equipment to the same value within 0X600-FFFF.
TCI structure
The TCI structure of the S-TAG is basically the same as the TCI structure of the C-TAG. VLAN
ID (VID) field consists of 12 bits and ranges from 0 to 4095. difference is that the TCI of the STAG contains the drop eligible (DE) indication and works with the priority code point (PCP) to
indicate the priority of the S-TAG frame.
The TCI structures of the C-TAG and S-TAG are shown in Figure 14-3 and Figure 14-4.
Figure 14-3 TCI structure of the C-TAG
Octets:
2
PCP
Bits:
VID
CFI
6
VID
1
PCP: 3 bits
CFI: 1 bit
2
PCP
Bits:
Issue 02 (2010-09-24)
DE
6
VID
VID
4
14-5
PCP: 3 bits
DE: 1 bit
VID: 12 bits
VCTRUNK port
Interface
module
Service
processing
module
Encapsulation/
Mapping
module
Backplane
Interface
conversion
module
Crossconnect unit
Crossconnect unit
Ethernet board
14.1.1.3 Auto-Negotiation
The auto-negotiation function allows the network equipment to send information of its supported
working mode to the opposite end on the network and to receive the corresponding information
that the opposite end may transfer.
The working modes of the interconnected ports on the equipment at both ends must be the same.
Otherwise, the services are unavailable.
If the working mode of the port on the opposite equipment is full duplex and if the working
mode of the port on the local equipment is auto-negotiation, the local equipment works in the
half-duplex mode. That is, the working modes of the interconnected ports at both ends are
different, and thus packets may be lost. Hence, when the working mode of the port on the opposite
equipment is full duplex, you need to set working mode of the port on the local equipment to
full duplex.
14-6
Issue 02 (2010-09-24)
NOTE
When the interconnected ports at both sides work in the auto-negotiation mode, the equipment at both sides
can negotiate the flow control through the auto-negotiation function.
The auto-negotiation function uses fast link pulses (FLPs) and normal link pulses (NLPs) to
transfer information of the working mode so that no packet or upper layer protocol overhead
needs to be added.
NOTE
This topic considers FE electrical ports as an example to describe how to implement the auto-negotiation
function.
The FLP is called the 100BASE-T link integrity test pulse sequence. Each set of equipment on
the network must be capable of issuing FLP bursts in the case of power-on, issuing of
management commands, or user interaction. FLP burst consists of a series of link integrity test
pulses that form an alternating clock/data sequence. Extraction of the data bits from the FLP
burst yields a link code word that identifies the working modes supported by the remote
equipment and certain information used for the negotiation and handshake mechanism.
To maintain interoperability with the existing 100BASE-T equipment, the auto-negotiation
function also supports the reception of 100BASE-T compliant link integrity test pulses.
10BASE-T link pulse activity is referred to as the NLP sequence. equipment that fails to respond
to the FLP burst sequence by returning only the NLP sequence is treated as the 100BASE-T
compatible equipment.
The first pulse in an FLP burst is defined as a clock pulse. Clock pulses within an FLP burst
occur at intervals of 125 us. Data pulses occur in the middle of two adjacent clock pulses. positive
pulse represents logic "1" and the absence of a pulse represents logic "0". An FLP burst consists
of 17 clock pulses and 16 data pulses (if all data bits are 1). NLP waveform is simpler than the
FLP waveform. NLP sends a positive pulse every 16 ms when no data frame needs to be
transmitted.
Figure 14-6 Waveform of a single FLP
T3
Clock pulses
T1
T2
1
D
0
T1: 100 ns
Issue 02 (2010-09-24)
1
D
1
0
D
2
T2: 62.5 us
1
D
3
T3: 125 us
14-7
FLP bursts
NLPs
T4: 2 ms
T5: 16 ms
Send only
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
The port can transmit PAUSE frames in the case of congestion but cannot process the
received PAUSE frames.
l
Receive only
The port can process the received PAUSE frames but cannot transmit PAUSE frames in
the case of congestion.
Realization Principle
The realization principle of the flow control function is described as follows:
1.
When congestion occurs in the receive queue of an Ethernet port (the data in the receive
buffer exceeding a certain threshold) and the port is capable of sending PAUSE frames,
the port sends a PAUSE frame to the opposite end. Pause-time value in the frame is N (0
< N 65535).
2.
If the Ethernet port at the opposite end is capable of processing PAUSE frames, this Ethernet
port stops sending data within a specified period of time N (the unit is the time needed for
sending 521 bits) after receiving the PAUSE frame.
3.
If the congestion at the receive port is cleared (the data in the receive buffer is below a
certain threshold) but the pause-time does not end, the port sends a PAUSE frame whose
pause-time is 0 to notify the opposite end to send data.
01-80-C2-00-00-01
6 octets
XX-XX-XX-XX-XX-XX
6 octets
Type/Length
88-08
2 octets
00-01
2 octets
XX-XX
2 octets
Source address
Reserved
Issue 02 (2010-09-24)
14-9
HDLC
The HDLC is a general data link control procedure. When using the HDLC protocol, the system
encapsulates data services into HDLC-like frames as information bits and maps the frames into
SDH VC containers.
LAPS
The LAPS is also a data link control procedure. It is optimized based on the HDLC. LAPS
complies with ITU-T X.86.
GFP
The GFP is the most widely applied general encapsulation and mapping protocol. It provides a
general mechanism to adapt higher-layer client signal flows into the transport network and can
map the variable-length payload into the byte-synchronized transport path. client signals can be
protocol data units (PDU-oriented, such as IP/PPP and Ethernet), block code data (block-code
oriented, such as Fiber Channel and ESCON), or common bit data streams. GFP protocol
complies with ITU-T G.7041.
GFP defines the following modes to adapt client signals:
l
Issue 02 (2010-09-24)
containers, or VC-4 containers) into a bit virtual structure to transport. virtual concatenation
breaks the contiguous bandwidth into individual VCs, transports the individual VCs, and
recombines these VCs to a contiguous bandwidth at the transmission termination point.
In the case of virtual concatenation, transport of each VC container may occupy different paths
and there may be a transport delay difference between VC containers. Hence, there are
difficulties to restore the client signal. Virtual concatenation requires concatenation functionality
only at the path termination equipment and it can flexibly allocate bandwidth. Hence, the virtual
concatenation technology is widely used.
Virtual concatenation is available in two types: virtual concatenation in a higher order path and
virtual concatenation in a lower order path. A higher order virtual concatenation VC-4-Xv
provides a payload of X Container-4s (VC-4s). payload is mapped individually into X
independent VC-4s. Each VC-4 has its own POH. A lower order virtual concatenation VC-12Xv provides a payload of X Container-12s (VC-12s). payload is mapped individually into X
independent VC-12s. Each VC-12 has its own POH. It is the same case with the virtual
concatenation of VC-3s.
Issue 02 (2010-09-24)
14-11
SQ = X-1
= 15
SQ = 0
= 255
MFI-1 = 15
MFI-2 = 255 X-1
=0
SQ = 0
=0
MFI-1 = 0
MFI-2 = 0
POH
POH
POH
POH
SQ = X-1
= 15
SQ = 0
MFI-1 = 15 = 0
MFI-2 = 0
X-1
SQ = 0
=0
MFI-1 = 0
= 15
MFI-2 = 1
Multiframe (MF)
POH
POH
C-3-Xv/C-4-Xv
SQ = X-1
=0
SQ = 0
=0
MFI-1 = 0
X-1
MFI-2 = 0
=1
SQ = 0
=0
MFI-1 = 1
MFI-2 = 0
H
C-3-X/C-4-X
With the MFI and SQ, the sink end can correctly restore the position of each frame in the C-nXv to prevent the frame alignment problem due to the different propagation delays of the frames.
VC-12-Xv
The virtual container that is formed by a VC-12-Xv can be mapped into X individual VC-12s
which form the VC-12-Xv. Each VC-12 has its own POH. POH has the same specifications as
the ordinary VC-12 POH. Bit 2 of the K4 byte in the POH is used for the virtual concatenationspecific frame count and sequence indicator.
Bit 2s of the K4 bytes in every 32 multiframes (one multiframe comprising four VC-12s) are
extracted to form a 32-bit character string to express the frame count and sequence indicator.
Bits 1-5 of the string express the frame count, whose value range is between 0 and 31. structure
formed by 32 multiframes has 128 frames. Hence, the resulting overall multiframe is 4096 frames
with the period of 512 ms. Bits 6-11 of the string express the sequence indicator. frame count/
sequence indicator in the VC-12-Xv has the same usage as the multiframe indicator/sequence
indicator in the VC-4-Xv/VC-3-Xv.
Issue 02 (2010-09-24)
Table 14-2 Processing mode of data frames at ports with different tags
Direction
Ingress port
Egress port
Processing Mode
Tag Aware
Access
Hybrid
Transparently
transmits the
frames.
Transparently
transmits the
frames.
Frames without
VLAN tags
Transparently
transmits the
frames.
NOTE
The tag setting is valid only if the following conditions are met:
l The port type is PE or UNI.
l The entry detection function is enabled. When the Ethernet switching board works in the Ethernet
transparent transmission state and when the entry detection function is disabled, the ports transparently
transmit the received data frames regardless of whether the data frames have the VLAN tags.
Based on the tag aware, access, and hybrid features, adhere to the following principles when
setting the tag for a port:
l
If it is certain that the data packets transmitted from the interconnected equipment have the
VLAN tags, set the local port to the tag aware mode.
If it is certain that the data packets transmitted from the interconnected equipment do not
have the VLAN tags, set the local port to the access mode.
If it is uncertain whether the data packets transmitted from the interconnected equipment
have the VLAN tags, set the local port to the hybrid mode.
14.1.1.8 Bridge
The bridge is the functional unit used to implement the interconnection between two or more
LANs.
Issue 02 (2010-09-24)
14-13
VB and LP
The various bridge (VB) is the unique concept for Huawei products. In the case of the Ethernet
data boards that have the Layer 2 switching capability, the switching domain can be divided into
multiple sub-switching domains. As a result, if no services are interconnected, different VBs
cannot access each other. Each VB has an independent configuration mode and uses an
independent VLAN. Different VBs can use the same VLAN.
A VB can contain a number of logical ports (LPs). By configuring the mounting relation, you
can mount multiple MAC ports and VCTRUNK ports to the same VB.
Figure 14-10 shows the relation between VB, LP, external port, and VCTRUNK port.
Figure 14-10 Relation between VB, LP, external port, and VCTRUNK port
LP1
LP4
VCTRUNK1
PORT2
LP2
LP5
VCTRUNK2
PORT3
LP3
LP6
VCTRUNK3
VB2
PORT4
LP1
LP4
VCTRUNK4
PORT5
LP2
LP5
VCTRUNK5
PORT6
LP3
LP6
VCTRUNK6
The services of different transparent bridges are isolated but the services of the same
transparent bridge are not isolated. entire transparent bridge is a switching domain.
The services of different virtual bridges are isolated and the services with different VLAN
IDs in the same virtual bridge are also isolated. switching domain of the entire virtual bridge
is divided into multiple sub-switching domains according to the VLAN IDs.
NOTE
As shown in Figure 14-11, the same logical port may belong to one or more sub-switching domains with
different VLAN IDs. On the U2000, the same logical port can belong to multiple filtering tables for different
VLAN IDs.
14-14
Issue 02 (2010-09-24)
PORT1
VLAN1
VLAN2
VLAN3
...
PORT2
PORT3
VCTRUNK1
VCTRUNK2
PORT1
VCTRUNK3
VCTRUNK4
PORT2
VCTRUNK5
VCTRUNK6
PORT3
Pure bridge
VLAN1
VLAN2
VLAN3
VCTRUNK1
VCTRUNK2
VCTRUNK3
VCTRUNK4
VCTRUNK5
VCTRUNK6
Virtual bridge
Logical port
Transparent Bridge
Virtual Bridge
It must be configured.
Ingress filtering
SVLa
IVLb
Broadcast range
NOTE
To forward a Layer 2 switching service, a bridge must learn the MAC address. A bridge learns the MAC
address in one of the following two ways: shared VLAN learning (SVL) and independent VLAN learning
(IVL).
l a: When the bridge adopts the SVL learning mode, the entry in the MAC address table is created
according to the source MAC address and source port of the data frame. entry is valid for all the VLANs.
l b: When the bridge adopts the IVL learning mode, the entry in the MAC address table is created
according to the source MAC address, VLAN ID, and source port of the data frame. entry is not valid
for all the VLANs.
Types of Bridges
As listed in Table 14-4, the Ethernet boards support three types of bridges.
Issue 02 (2010-09-24)
14-15
Bridge Learning
Mode
Ingress
Filtering
SVL/Ingress Filter
Disable
SVL
Disabled
IVL/Ingress Filter
Enable
IVL
Enabled
IEEE 802.1ad
provider bridge
SVL/Ingress Filter
Disable
SVL
Disabled
IVL/Ingress Filter
Enable
IVL
Enabled
IEEE 802.1d MAC bridge: This bridge does not check the contents of the VLAN tags that
are in the data frames and performs Layer 2 switching according to the destination MAC
addresses of the data frames.
IEEE 802.1q virtual bridge: This bridge supports isolation by using one layer of VLAN
tags. This bridge checks the contents of the VLAN tags that are in the data frames and
performs Layer 2 switching according to the destination MAC addresses and VLAN IDs.
IEEE 802.1ad provider bridge: This bridge supports data frames with two layers of VLAN
tags. This bridge adopts the outer S-VLAN tags to isolate different VLANs and supports
only the mounted ports whose attributes are C-Aware or S-Aware. This bridge supports the
following switching modes:
1.
This bridge does not check the contents of the VLAN tags that are in the data frames
and performs Layer 2 switching according to the destination MAC addresses of the
data frames.
2.
This bridge checks the contents of the VLAN tags that are in the data frames and
performs Layer 2 switching according to the destination MAC addresses and the SVLAN IDs of the data frames.
Dynamic entry
Indicates the entry that the bridge obtains by adopting the SVL/IVL learning mode. dynamic
entry ages and is even lost after the Ethernet switching board is reset.
Static entry
Indicates the entry corresponding to the MAC address and the port that the network
administrator manually adds in the MAC address table on the U2000. dynamic entry does
not age and is not lost after the Ethernet switching board is reset.
Blackhole entry
Indicates the entry used to discard the data frame that contains the specified destination
MAC address, and is also referred to as the MAC address disable entry. blackhole entry is
14-16
Issue 02 (2010-09-24)
configured by the network administrator. This entry does not age and is not lost after the
Ethernet switching board is reset.
NOTE
l If a routing entry is not updated within a specific period of time, that is, if the MAC address fails to be learnt
because the new data frame from the MAC address is not received, this routing entry is automatically deleted.
This mechanism is considered as aging, and this period of time is considered as the aging time. aging time
of the MAC address table is five minutes by default and can be set by using the U2000.
l A limited number of MAC addresses can be learnt at a time.
Hub/Spoke
Generally, the central station and non-central stations can access each other but the non-central
stations cannot access each other in the case of convergence services. Hence, the ports mounted
to the bridge need to be defined as Hub ports or Spoke ports.
l
Hub port
Hub ports can access each other. Hub ports and Spoke ports can also access each other.
Spoke port
Spoke ports cannot access each other. Hub ports and Spoke ports can access each other.
14-17
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > SDH
Service Configuration from the Function Tree.
Step 2 Query the data.
1.
Click Query.
Then, the Confirm dialog box is displayed, prompting This operation will query service
at the NE and update service date at the NM. Are you sure to continue?.
2.
Click OK.
Then, the Operation Result dialog box is displayed, prompting Operation succeeded.
3.
Click Close.
Step 3 Select the cross-connection of the Ethernet service that needs to be deleted in CrossConnection.
Step 4 Deactivate the service.
1.
Click Deactivate.
Then, the Confirm dialog box is displayed, prompting Are you sure to deactivate all
selected services (only for activated services?).
2.
Click OK. Another Confirm dialog box is displayed, prompting This services of the NE
will be cleared by this operation. Are you sure to continue?.
3.
Click OK.
Then, the Operation Result dialog box is displayed, prompting Operation succeeded.
4.
Click Close.
Click Delete.
Then, the Confirm dialog box is displayed, prompting Are you sure to delete all the
selected services (only for inactive services)?.
2.
Click OK.
Then, the Operation Result dialog box is displayed, prompting Operation succeeded.
3.
Click Close.
Issue 02 (2010-09-24)
14.1.3.2 Setting Port Attributes and Bound Paths for an Ethernet Board
You need to set the port attributes and bound paths for an Ethernet board prior to creating Ethernet
services.
14.1.3.3 Creating Ethernet Line Service
To enable the Ethernet switching board to transmit the line service, perform certain operations
to configure the related information, such as the service source and service sink.
14.1.3.4 Testing Ethernet Services
You can enable an Ethernet board to send Ethernet test frames for the purpose of fault location.
14.1.3.5 Deleting an Ethernet Private Line Service
When an Ethernet private line service is not used, you can delete the Ethernet private line service
to release the corresponding resources.
Deploying a
Network
Configure
source NE
Creating and
Configuring NEs
Configure
sink NE
Setting External
Ports Attributes of
Ethernet Boards
Setting External
Ports Attributes of
Ethernet Boards
Setting Internal
Ports Attributes of
Ethernet Boards
Setting Internal
Ports Attributes of
Ethernet Boards
Setting Bound
Paths of Ethernet
Boards
Setting Bound
Paths of Ethernet
Boards
Creating CrossConnection
Between Ethernet
and Line Boards
Creating CrossConnection
Between Ethernet
and Line Boards
Creating EPL
Services
Creating EPL
Services
Configure
pass-through NE
Creating CrossConnection
Between Ethernet
and Line Boards
Verify service
Creating Fibers
Configuring
Communication
Setting the NE
Time
Configuring Clocks
Configuring
Orderwire
Configuring
Protection
Issue 02 (2010-09-24)
14-19
l In the case of the EFT4 board for the RTN equipment, the EPL service is written to the board. Thus,
Creating EPL Services is not needed for the source or sink NE.
l In the landscape orientation of the configuration flow chart by using U2000, there are five main phases
of EPL service configuration process. They are deploying a network, configuring source NEs,
configuring sink NEs, configuring pass-through NEs, and verifying services.
l The portrait orientation of the flow chart shows the relations between operation tasks in each phase.
14.1.3.2 Setting Port Attributes and Bound Paths for an Ethernet Board
You need to set the port attributes and bound paths for an Ethernet board prior to creating Ethernet
services.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet board must be created.
Procedure
Step 1 Configure the external port of a board. For details, refer to 14.4.7.1 Configuring the Internal
Port of the Ethernet Board.
Step 2 Configure the internal port of a board. For details, refer to 14.3.7.1 Configuring External
Ethernet Ports.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be added in the slot layout.
Precautions
l
This topic does not describe the method for creating the QinQ service.
IDU 620 supports the Ethernet switching board EMS6. The EFT4 board is an Ethernet
transparent transmission board, and the PORTs of the EFT4 board correspond to the
VCTRUNKs. Hence, you do not need to create the Ethernet line service.
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Ethernet
Service > Ethernet Line Service from the Function Tree.
Step 2 Click New.
14-20
Issue 02 (2010-09-24)
Step 4 Optional: Set the port attributes of the source port and sink port.
NOTE
The result of setting the port attributes during the Ethernet line service configuration process is the same as the
result of directly setting the Ethernet service port attributes.
Click Configuration.
The Bound Path Configuration dialog box is displayed.
2.
3.
In Available Bound Paths, set Level and Direction of the bound paths.
4.
Select required items in Available Resources and Available Timeslots and click
5.
Issue 02 (2010-09-24)
14-21
NOTE
The result of setting the port attributes during the Ethernet line service configuration process is the same
as the result of directly setting the Ethernet service port attributes.
6.
Click OK.
Parameters
Parameter
Value Range
Default Value
Description
Service Type
EPL
Direction
Unidirectional,
Bidirectional
Bidirectional
14-22
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Source Port
A specific PORT or
VCTRUNK
PORT1
1-4095
Sink Port
A specific PORT or
VCTRUNK
PORT1
Issue 02 (2010-09-24)
14-23
Parameter
Value Range
Default Value
Description
1-4095
Port Enabled
Enabled, Disabled
TAG
Tag Aware
Configurable Ports
14-24
VCTRUNKs
VCTRUNK 1
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Available Bound
Paths
Activation Status
Activated,
Inactivated
Prerequisite
l
Context
As shown in Figure 14-13, when Ethernet services are unavailable between router A and
router B, you can send test frames between NE1 and NE2 to determine whether a fault
occurs. NE1 sends test frames to NE2, and NE2 sends response frames after it receives the
Issue 02 (2010-09-24)
14-25
test frames. According to the response frames from NE2, NE1 determines whether a fault
occurs.
Figure 14-13 Ethernet test
NE1
NE2
Test
Frame
NE3
Answer
Frame
Router A
Router B
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > Ethernet Maintenance >
Ethernet Test from the Function Tree.
Step 2 Select the internal port that you want to test and set the test parameters.
NOTE
Set an NE to send test frames when you want to test whether a network is normal or not. The Send Mode and
Frames to send parameters can be edited. When setting Send Mode, note the following:
l If you select the Continue Mode, you can continuously send one test packet every 1s until you stop.
l If you select the Burst Mode, you can set the number of frames you want to send. The sending duration is
50 ms.
l If you select the Disabled mode, you stop sending test frames.
Step 3 Click Apply. A prompt is displayed indicating that the operation is successful. Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet private line service must be configured and the service is not be used.
14-26
Issue 02 (2010-09-24)
Procedure
Step 1 Select the target Ethernet switching board in the NE Explorer. Then, choose Configuration >
Ethernet Service > Ethernet Line Service from the Function Tree.
Step 2 Click Query.
Click OK in the dialog box that is displayed.
Step 3 Select the Ethernet private line service that needs to be deleted and then click Delete.
Click OK in the dialog box that is displayed.
Step 4 Click Query.
Click OK in the dialog box that is displayed.
At this time, the Ethernet private line service is already deleted.
----End
14-27
Deploying a
Network
Creating and
Configuring NEs
Configure
source NE
Configure
sink NE
Configure
pass-through NE
Setting External
Ports Attributes of
Ethernet Boards
Setting External
Ports Attributes of
Ethernet Boards
Configuring SDH
Services
Creating Fibers
Configuring
Communication
Setting the NE
Time
Setting Internal
Ports Attributes of
Ethernet Boards
Setting Internal
Ports Attributes of
Ethernet Boards
Creating CrossConnection
Between Ethernet
and Line Boards
Creating CrossConnection
Between Ethernet
and Line Boards
Creating EPLAN
Services
Creating EPLAN
Services
Creating VALN
Creating VALN
Configuring QOS
Configuring QOS
Configuring LPT
Configuring LPT
Configuring LCAS
Configuring LCAS
Configuring
Ethernet Service
OAM
Configuring
Ethernet Service
OAM
Configuring the
Ethernet Port OAM
Configuring the
Ethernet Port OAM
Verify service
Checking the
Connectivity of
Ethernet Service
Checking the
Connectivity of
Ethernet Port
Configuring Clocks
Configuring
Orderwire
Configuring
Protection
NOTE
l In the landscape orientation of the configuration flow chart by using U2000, there are five main phases
of Ethernet LAN service configuration process. They are deploying a network, configure source NE,
configure sink NE, configure pass-through NE and verify service.
l The portrait orientation of the flow chart shows the relations between operation tasks in each phase.
14.1.4.2 Setting Port Attributes and Bound Paths for an Ethernet Board
You need to set the port attributes and bound paths for an Ethernet board prior to creating Ethernet
services.
14-28
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet board must be created.
Procedure
Step 1 Configure the external port of a board. For details, refer to 14.4.7.1 Configuring the Internal
Port of the Ethernet Board.
Step 2 Configure the internal port of a board. For details, refer to 14.3.7.1 Configuring External
Ethernet Ports.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
Precautions
l
This task describes only how to create the 802.1d bridge and how to create the 802.1q
bridge.
The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board).
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Ethernet
Service > Ethernet LAN Service from the Function Tree.
Step 2 Click New.
The Create Ethernet LAN Service dialog box is displayed.
Step 3 Set the attributes of the bridge according to the bridge type.
l Set the attributes of the 802.1q bridge.
Issue 02 (2010-09-24)
14-29
14-30
2.
Select a port from the ports listed in Available Mounted Ports, and then click
3.
Issue 02 (2010-09-24)
4.
Click OK.
Step 5 Optional: If any VCTRUNK is mounted to the VB, configure the VC paths that are bound to
the VCTRUNK.
1.
Click Configuration.
The Bound Path Configuration dialog box is displayed.
2.
3.
In Available Bound Paths, set Level and Service Direction of the bound paths.
4.
Select required items in Available Resources and Available Timeslots and click
5.
NOTE
The result of setting the port attributes during the Ethernet line service configuration process is the same
as the result of directly setting the Ethernet service port attributes.
6.
Click OK.
14-31
Parameters
Parameter
Value Range
Default Value
Description
VB Name
Bridge Type
802.1q, 802.1d,
802.1ad (EMS6)
802.1q
802.1q, 802.1d
(EM4T, a logical
board EMS4)
IVL/Ingress Filter
Enable (802.1q),
SVL/Ingress Filter
Disable (802.1d)
IVL/Ingress Filter
Enable (802.1q),
SVL/Ingress Filter
Disable (802.1d)
Mount Port
Configurable Ports
14-32
Mount each
VCTRUNK of the
port.
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Available Bound
Paths
Activation Status
Activated,
Inactivated
14.1.4.4 Creating the EVPLAN Services That Are Based on the IEEE 802.1ad Bridge
To enable the Ethernet switching board to transmit the EVPLAN services that are based on the
IEEE 802.1ad bridge, you need to create the bridge, set the attributes of the bridge, select the
ports that are mounted to the bridge, and select the operation type.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
Issue 02 (2010-09-24)
14-33
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > Ethernet
Service > Ethernet LAN Service from the Function Tree.
Step 2 Click New.
The Create Ethernet LAN Service dialog box is displayed.
Step 3 Set the attributes of the IEEE 802.1ad bridge.
2.
3.
4.
Repeat Step 4.2 to Step 4.3 to add the other mount ports.
5.
Click OK.
Step 5 Optional: If any VCTRUNK is mounted to the VB, configure the VC paths that are bound to
the VCTRUNK.
1.
Click Configuration.
The Bound Path Configuration dialog box is displayed.
2.
3.
In Available Bound Paths, set Level and Direction of the bound paths.
4.
Select the required items in Available Resources and Available Timeslots and click
.
5.
14-34
Issue 02 (2010-09-24)
NOTE
The result of setting the port attributes during the configuration of the private network service is consistent
with the result of directly setting the attributes of the Ethernet service port.
6.
Click OK.
----End
Parameters
Parameter
Value Range
Default Value
Description
VB Name
VB Type
802.1q, 802.1d,
802.1ad
802.1q
IVL/Ingress Filter
Enable
IVL/Ingress Filter
Enable
SVL/Ingress Filter
Disable
14-35
Parameter
Value Range
Default Value
Description
Operation Type
Mount Port
C-VLAN
1-4095
S-VLAN
1-4095
l When Operation Type is set to Add SVLAN Base for Port, this parameter
specifies that the data frames that enter
the IEEE 802.1ad bridge need to be
added with the S-VLAN tag.
l When Operation Type is set to Add SVLAN Base for Port and C-VLAN,
this parameter and C-VLAN specify the
mapping relation between the S-VLAN
tag to be added and the C-VLAN tag
carried by the data frame that enters the
IEEE 802.1ad bridge.
l When Operation Type is set to Mount
Port, this parameter is invalid.
l When Operation Type is set to Mount
Port and Base for Port and S-VLAN,
this parameter specifies the S-VLAN tag
to be carried by the data frames that enter
the IEEE 802.1ad bridge.
Configurable Ports
14-36
Mount each
VCTRUNK of the
port.
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Available Bound
Paths
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
The EVPLAN service must be created.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board).
Issue 02 (2010-09-24)
14-37
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Ethernet
Service > Ethernet LAN Service from the Function Tree.
Step 2 Select the bridge that is already created, and click the VLAN Filtering tab.
Step 3 Create the VLAN filter table.
1.
Click New.
The Create VLAN dialog box is displayed.
2.
3.
Select a port from the ports listed in Available forwarding ports, and then click
4.
5.
Click OK.
----End
14-38
Issue 02 (2010-09-24)
Parameters
Parameter
Value Range
Default Value
Description
VLAN ID (e.g:
1,3-6)
1-4095
selected forwarding
ports
This parameter
indicates the ports
that are mounted to a
bridge.
Prerequisite
l
Context
As shown in Figure 14-15, when Ethernet services are unavailable between router A and
router B, you can send test frames between NE1 and NE2 to determine whether a fault
occurs. NE1 sends test frames to NE2, and NE2 sends response frames after it receives the
test frames. According to the response frames from NE2, NE1 determines whether a fault
occurs.
Issue 02 (2010-09-24)
14-39
NE1
NE2
Test
Frame
NE3
Answer
Frame
Router A
Router B
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > Ethernet Maintenance >
Ethernet Test from the Function Tree.
Step 2 Select the internal port that you want to test and set the test parameters.
NOTE
Set an NE to send test frames when you want to test whether a network is normal or not. The Send Mode and
Frames to send parameters can be edited. When setting Send Mode, note the following:
l If you select the Continue Mode, you can continuously send one test packet every 1s until you stop.
l If you select the Burst Mode, you can set the number of frames you want to send. The sending duration is
50 ms.
l If you select the Disabled mode, you stop sending test frames.
Step 3 Click Apply. A prompt is displayed indicating that the operation is successful. Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet LAN service must be configured and the service is not used.
Background Information
Deleting an Ethernet LAN service involves the following tasks:
1.
14-40
Issue 02 (2010-09-24)
2.
Procedure
Step 1 Select the target Ethernet switching board in the NE Explorer. Then, choose Configuration >
Ethernet Service > Ethernet LAN Service from the Function Tree.
Step 2 Click Query.
Then, click OK in the dialog box that is displayed.
Step 3 Click the VLAN Filtering tab.
Step 4 Select the VLAN filtering entries that need to be deleted. Then, click Delete.
Then, click OK in the dialog box that is displayed.
Step 5 Click the Service Mount tab.
Step 6 Select the Ethernet LAN service that needs to be deleted and then click Delete.
Then, click OK in the dialog box that is displayed.
Step 7 Click Query.
Then, click OK in the dialog box that is displayed.
At this time, the Ethernet private line service is already deleted.
----End
14-41
Deploying a
Network
Configure
source NE
Creating and
Configuring NEs
Configure
sink NE
Setting External
Ports Attributes of
Ethernet Boards
Setting External
Ports Attributes of
Ethernet Boards
Setting Internal
Ports Attributes of
Ethernet Boards
Setting Internal
Ports Attributes of
Ethernet Boards
Setting Bound
Paths of Ethernet
Boards
Setting Bound
Paths of Ethernet
Boards
Creating CrossConnection
Between Ethernet
and Line Boards
Creating CrossConnection
Between Ethernet
and Line Boards
Creating
EVPL(QinQ)
Services
Creating
EVPL(QinQ)
Services
Configure
pass-through NE
Creating CrossConnection
Between Ethernet
and Line Boards
Verify service
Creating Fibers
Configuring
Communication
Setting the NE
Time
Configuring Clocks
Configuring
Orderwire
Configuring
Protection
NOTE
l In the landscape orientation of the configuration flow chart by using U2000, there are five main phases
of EVPL(QinQ) service configuration process. They are deploying a network, configure source NE,
configure sink NE, configure pass-through NE and verify service.
l The portrait orientation of the flow chart shows the relations between operation tasks in each phase.
14.1.5.2 Setting Port Attributes and Bound Paths for an Ethernet Board
You need to set the port attributes and bound paths for an Ethernet board prior to creating Ethernet
services.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet board must be created.
Procedure
Step 1 Configure the external port of a board. For details, refer to 14.4.7.1 Configuring the Internal
Port of the Ethernet Board.
14-42
Issue 02 (2010-09-24)
Step 2 Configure the internal port of a board. For details, refer to 14.3.7.1 Configuring External
Ethernet Ports.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet board must be included in the slot layout.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Advanced Attributes
> QinQ Type Area Settings from the Function Tree.
Step 2 Modify the type field of QinQ frames.
Parameters
Parameter
Value Range
Default Value
Description
81 00, 98 A8, 91 00
81 00
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
Issue 02 (2010-09-24)
14-43
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > Ethernet
Service > Ethernet Line Service from the Function Tree.
Step 2 Select Display QinQ Shared Service.
Step 3 Click New.
The system displays the Create Ethernet Line Service dialog box.
Step 4 Set the attributes of the Ethernet line service.
Step 5 Optional: Set the port attributes of the source port and sink port.
NOTE
The result of configuring the port attributes during the Ethernet line service configuration process is the same
as the result of directly configuring the Ethernet service port attributes.
14-44
Issue 02 (2010-09-24)
Parameters
Parameter
Value Range
Default Value
Description
Service Type
EPL, EVPL(QinQ)
EPL
Direction
Unidirectional,
Bidirectional
Bidirectional
Operation Type
Source Port
Transparently
transmit C-VLAN,
Translate C-VLAN,
Add S-VLAN,
Transparently
transmit S-VLAN,
Translate S-VLAN,
Strip S-VLAN (only
for unidirectional
services)
Add S-VLAN
A specific PORT or
VCTRUNK
PORT1
Issue 02 (2010-09-24)
14-45
Parameter
Value Range
Default Value
Description
Source C-VLAN
(e.g. 1,3-6)
1 to 4095
Source S-VLAN
1 to 4095
Sink Port
A specific PORT or
VCTRUNK
PORT1
14-46
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
1 to 4095
Sink S-VLAN
1 to 4095
C-VLAN Priority
AUTO, Priority0Priority7
AUTO
S-VLAN Priority
AUTO, Priority0Priority7
AUTO
Port Enabled
Issue 02 (2010-09-24)
Enabled, Disabled
14-47
Prerequisite
l
Context
As shown in Figure 14-17, when Ethernet services are unavailable between router A and
router B, you can send test frames between NE1 and NE2 to determine whether a fault
occurs. NE1 sends test frames to NE2, and NE2 sends response frames after it receives the
test frames. According to the response frames from NE2, NE1 determines whether a fault
occurs.
Figure 14-17 Ethernet test
NE1
NE2
Test
Frame
NE3
Answer
Frame
Router A
Router B
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > Ethernet Maintenance >
Ethernet Test from the Function Tree.
Step 2 Select the internal port that you want to test and set the test parameters.
14-48
Issue 02 (2010-09-24)
NOTE
Set an NE to send test frames when you want to test whether a network is normal or not. The Send Mode and
Frames to send parameters can be edited. When setting Send Mode, note the following:
l If you select the Continue Mode, you can continuously send one test packet every 1s until you stop.
l If you select the Burst Mode, you can set the number of frames you want to send. The sending duration is
50 ms.
l If you select the Disabled mode, you stop sending test frames.
Step 3 Click Apply. A prompt is displayed indicating that the operation is successful. Click Close.
----End
The two branches of User A that are located at NE1 and NE2 need communicate with each
other over Ethernet. A 10 Mbit/s bandwidth is required.
The two branches of User B that are located at NE1 and NE2 need communicate with each
other over Ethernet. A 20 Mbit/s bandwidth is required.
The Ethernet equipment of User A and User B provide 100 Mbit/s Ethernet electrical ports
of which the working mode is auto-negotiation, and does not support VLAN.
Issue 02 (2010-09-24)
14-49
User A2
NE2
NE 1
User B2
User B1
FAN
FAN
Slot 20
EXT
IF1A
Slot7
EXT
EFT4
Slot8
EXT
IF1A
Slot5
EXT
Slot6
PXC
PXC
Slot3
EXT
PH1
Slot4
PXC
PXC
Slot1
SCC
SCC
Slot2
NE2:8-EFT4
VCTRUNK1
VCTRUNK1
VC4-2:VC12:1-5
VC4-2:VC12:1-5
VCTRUNK2
VCTRUNK2
VC4-2:VC12:6-15
VC4-2:VC12:6-15
PORT1
User A2
PORT2
User B2
SDH
14-50
Issue 02 (2010-09-24)
NE1
NE2
Board
8-EFT4
8-EFT4
Port
PORT1
PORT2
PORT1
PORT2
Enabled/
Disabled
Enabled
Enabled
Enabled
Enabled
Working Mode
AutoNegotiation
AutoNegotiation
AutoNegotiation
AutoNegotiation
Maximum
Frame Length
1522
1522
1522
1522
Flow Control
Disabled
Disabled
Disabled
Disabled
NE1
NE2
Board
8-EFT4
8-EFT4
Port
VCTRUNK1
VCTRUNK2
VCTRUNK1
VCTRUNK2
Encapsulation
Mapping
Protocol
GFP
GFP
GFP
GFP
LCAS Enabled
Enabled
Enabled
Enabled
Enabled
Bound Path
VC4-2:
VC12-1VC12-5
VC4-2:
VC12-6VC12-15
VC4-2:
VC12-1VC12-5
VC4-2:
VC12-6VC12-15
1#VC4
NE1
5-IF1A-1
NE2
5-IF1A1-1
VC12:17-21
8-EFT4
8-EFT4
VC4-2:1-5
VC4-2:1-5
VC12:22-31
8-EFT4
8-EFT4
VC4-2:6-15
VC4-2:6-15
Add/Drop
Issue 02 (2010-09-24)
14-51
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The EFT4 board must be added.
Procedure
Step 1 Configure Ethernet external ports.
1.
In the NE Explorer, select the EFT4 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select External
Port.
2.
Click the Basic Attributes tab. After setting the parameters, click Apply.
Parameter
Value Range
Port
PORT1
Description
PORT2
Enabled/
Disabled
Enabled
Working
Mode
Auto-Negotiation
Issue 02 (2010-09-24)
1.
In the NE Explorer, select the EFT4 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select Internal
Port. Set the parameters of VCTRUNK1 and VCTRUNK2.
2.
3.
a.
b.
Set Mapping Protocol and the protocol parameters. After setting the parameters, click
Apply.
Paramete
r
Value Range
Description
Port
VCTRUN
K1
Mapping
Protocol
GFP
VCTRU
NK2
b.
Set Enabling LCAS and other LCAS parameters. After setting the parameters, click
Apply.
Paramete
r
Value Range
Description
Port
VCTRU
NK1
Enabling
LCAS
Enabled
VCTRUN
K2
4.
Issue 02 (2010-09-24)
b.
Click Configuration. Then, the Bound Path Configuration dialog box is displayed.
c.
d.
In Available Bound Paths, set Level and Service Direction of the bound paths. After
setting the parameters, click OK. Then, click Yes in the dialog box that is displayed.
Paramete
r
Value Range
Description
Configura
ble Ports
VCTRUN
K1
VCTRUN
K2
14-53
Paramete
r
Value Range
Description
Level
VC12
Service
Direction
Bidirectional
Available
Resources
VC4-2
Available
Timeslots
VC12-1 to
VC12-5
VC12-6 to
VC12-15
Activation
Status
Activated
In the NE Explorer, select NE1 from the Object Tree and then choose Configuration >
SDH Service Configuration from the Function Tree.
2.
Click Create. The Create SDH Service dialog box is displayed. After setting the
parameters. Then, click OK.
l Set the parameters of the cross-connections of VCTRUNK1 as follows.
Parameter
Value Range
Description
Level
VC12
Direction
Bidirectional
14-54
Source
5-IF1A
Source Timeslot
Range(e.g.1,3-6)
17-21
Issue 02 (2010-09-24)
Parameter
Value Range
Description
Sink
8-EFT4
Sink VC4
VC4-2
Sink Timeslot
Range(e.g.1,3-6)
1-5
Activate
Immediately
Yes
Value Range
Description
Level
VC12
Direction
Bidirectional
Source
5-IF1A
Source Timeslot
Range(e.g.1,3-6)
22-31
Sink
8-EFT4
Sink VC4
VC4-2
Sink Timeslot
Range(e.g.1,3-6)
6-15
Activate
Immediately
Yes
----End
14-55
The procedures for configuring NE2 are the same as the procedures for configuring NE1. For
details, see 14.1.6.3 Configuring NE1.
The headquarters C1 of User C are located at NE1 and the two branches of User C (C2 and
C3) are located at NE2 and NE3. The services between C1 and C2 are transmitted in the
VLAN of which the VLAN ID ranges from 100 to 110. The services between C1 and C3
are transmitted in the VLAN of which the VLAN ID ranges from 200 to 210.
The services of C2 are isolated from the services of C3. The services of C2 and C3 require
a 20 Mbit/s bandwidth respectively.
The Ethernet equipment of C1, C2, and C3 provide 100 Mbit/s Ethernet electrical ports of
which the working mode is auto-negotiation, and supports VLAN.
User C1
NE2
VLAN100-110
VLAN200-210
NE3
User C3
14-56
Issue 02 (2010-09-24)
FAN
FAN
Slot 20
EXT
IF1A
Slot7
EXT
EMS6
Slot8
EXT
IF1A
Slot5
EXT
Slot6
PXC
PXC
Slot3
EXT
PD1
Slot4
PXC
PXC
Slot1
SCC
SCC
Slot2
FAN
FAN
Slot 20
EXT
Slot7
EXT
EFT4
Slot8
EXT
IF1A
Slot5
EXT
Slot6
PXC
PXC
Slot3
EXT
PH1
Slot4
PXC
PXC
Slot1
SCC
SCC
Slot2
NE1:8-EMS6
VC4-2:VC12:1-10
PORT1
User C2
VCTRUNK1
PORT1
User C1
VC4-2:VC12:1-10
VCTRUNK2
NE3:8-EFT4
VC4-2:VC12:11-20
VCTRUNK1
VC4-2:VC12:1-10
PORT1
User C3
SDH
Issue 02 (2010-09-24)
14-57
NE1
NE2
NE3
Board
8-EMS6
8-EFT4
8-EFT4
Port
PORT1
PORT1
PORT1
Enabled/Disabled
Enabled
Enabled
Enabled
Working Mode
Auto-Negotiation
Auto-Negotiation
Auto-Negotiation
Maximum Frame
Length
1522
1522
1522
Flow Control
Disabled
Disabled
Disabled
TAG
Tag Aware
Entry Detection
Enabled
NE1
NE2
NE3
Board
8-EMS6
8-EFT4
8-EFT4
Port
VCTRUNK1
VCTRUNK2
VCTRUNK1
VCTRUNK1
Encapsulation
Mapping
Protocol
GFP
GFP
GFP
GFP
Enabling LCAS
Enabled
Enabled
Enabled
Enabled
TAG
Tag Aware
Tag Aware
Entry Detection
Enabled
Enabled
Bound Path
VC4-2:
VC12-1VC12-10
VC4-2:
VC12-11VC12-20
VC4-2:
VC12-1VC12-10
VC4-2:
VC12-1VC12-10
NE1
Private Line Service 1
14-58
Board
8-EMS
Service Type
EPL
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
Parameter
NE1
Private Line Service 1
Direction
Bidirectional
Source Port
PORT1
PORT1
100-110
200-210
Sink Port
VCRTUNK1
VCTRUNK2
100-110
200-210
1#VC4
NE2
5-IF1A-1
NE1
5-IF1A1-1
VC12:17-26
8-EMS6
8-EFT4
VC4-2:1-10
VC4-2:1-10
7-IF1A1-1
NE3
5-IF1A1-1
VC12:17-26
8-EMS6
8-EFT4
VC4-2:11-20
VC4-2:1-10
Add/Drop
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Issue 02 (2010-09-24)
14-59
Procedure
Step 1 Configure Ethernet external ports.
1.
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select External
Port.
2.
Click the Basic Attributes tab. After setting the parameters, click Apply.
Parameter
Value Range
Description
Port
PORT1
3.
Enabled/
Disabled
Enabled
Working Mode
AutoNegotiation
The Ethernet equipment of users work in autonegotiation mode. Hence, the Working Mode of
the external ports should be set to AutoNegotiation.
Click the TAG Attributes tab. After setting the parameters, click Apply.
Parameter
Value Range
Description
Port
PORT1
TAG
Tag Aware
Entry Detection
Enabled
14-60
1.
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select Internal
Port. Set the parameters of VCTRUNK1 and VCTRUNK2.
2.
b.
Set Mapping Protocol and the protocol parameters. After setting the parameters, click
Apply.
Issue 02 (2010-09-24)
3.
Paramete
r
Value Range
Description
Port
VCTRUN
K1
Mapping
Protocol
GFP
VCTRU
NK2
b.
Set Enabling LCAS and other LCAS parameters. After setting the parameters, click
Apply.
Paramete
r
Value Range
Description
Port
VCTRU
NK1
Enabling
LCAS
Enabled
VCTRUN
K2
4.
Click the TAG Attributes tab. After setting the parameters, click Apply.
Parameter
Value Range
Port
VCTRUNK1
TAG
Tag Aware
Description
VCTRUNK2
Entry
Detection
5.
Issue 02 (2010-09-24)
Enabled
b.
Click Configuration. Then, the Bound Path Configuration dialog box is displayed.
c.
14-61
d.
In Available Bound Paths, set Level and Direction of the bound paths. After setting
the parameters, click OK. Then, click Yes in the dialog box that is displayed.
Paramete
r
Value Range
Description
Configura
ble Ports
VCTRUN
K1
Level
VC12
Service
Direction
Bidirectional
VCTRUN
K2
VC4-2
Available
Timeslots
VC12-1 to
VC12-10
Activation
Status
Activated
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Service > Ethernet Line Service from the Function Tree.
2.
Click New. The Create Ethernet Line Service dialog box is displayed. After setting the
parameters, click OK.
l Set the parameters of the Ethernet private line services on PORT1 and VCTRUNK1 as
follows.
Parameter
Value Range
Description
Service Direction
Bidirectional
Source Port
14-62
PORT1
Issue 02 (2010-09-24)
Parameter
Value Range
Description
Source VLAN
(e.g. 1,3-6)
100-110
Sink Port
VCTRUNK1
100-110
l Set the parameters of the Ethernet private line services on PORT1 and VCTRUNK2 as
follows.
Parameter
Value Range
Description
Service Direction
Bidirectional
Source Port
PORT1
Source VLAN
(e.g. 1,3-6)
200-210
Sink Port
VCTRUNK2
200-210
In the NE Explorer, select NE1 from the Object Tree and then choose Configuration >
SDH Service Configuration from the Function Tree.
2.
Click Create. The Create SDH Service dialog box is displayed. After setting the
parameters. Then, click OK.
l Set the parameters of the cross-connections of VCTRUNK1 as follows.
Issue 02 (2010-09-24)
Parameter
Value Range
Description
Level
VC12
14-63
Parameter
Value Range
Description
Direction
Bidirectional
Source
5-IF1A
Source
Timeslot
Range(e.g.
1,3-6)
17-26
Sink
8-EMS6
Sink VC4
VC4-2
Sink Timeslot
Range(e.g.
1,3-6)
1-10
Activate
Immediately
Yes
Value Range
Description
Level
VC12
Direction
Bidirectional
14-64
Source
7-IF1A
Source
Timeslot
Range(e.g.
1,3-6)
17-26
Sink
8-EMS6
Sink VC4
VC4-2
Issue 02 (2010-09-24)
Parameter
Value Range
Description
Sink Timeslot
Range(e.g.
1,3-6)
11-20
Activate
Immediately
Yes
----End
Issue 02 (2010-09-24)
The two branches of User D are located at NE1 and NE2, and need to communicate with
each other.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
14-65
The two branches of User E are located at NE1 and NE2, and need to communicate with
each other.
The services of User D need to be isolated from the services of User E. The traffic of User
D and User E, however, is supplementary to each other, and thus can share the 20 Mbit/s
bandwidth.
The Ethernet equipment of User D and User E provide 100 Mbit/s Ethernet electrical ports
of which the working mode is auto-negotiation, and does not support VLAN.
User D1
NE 1
12
NE2
User E1
User E2
FAN
FAN
Slot 20
14-66
EXT
Slot7
EXT
EMS6
Slot8
EXT
IF1A
Slot5
EXT
Slot6
PXC
PXC
Slot3
EXT
PH1
Slot4
PXC
PXC
Slot1
SCC
SCC
Slot2
Issue 02 (2010-09-24)
NE1:8-EMS6
PORT1
User D1
EPL1
PORT2
User E1
EPL2
VCTRUNK1
VCTRUNK1
VC4-2:VC12:1-10
VC4-2:VC12:1-10
EPL1
PORT1
User D2
EPL2
PORT2
User E2
SDH
NE1
NE2
Board
8-EMS6
8-EMS6
Port
PORT1
PORT2
PORT1
PORT2
Enabled/
Disabled
Enabled
Enabled
Enabled
Enabled
Working Mode
AutoNegotiation
AutoNegotiation
AutoNegotiation
AutoNegotiation
Maximum
Frame Length
1522
1522
1522
1522
Flow Control
Disabled
Disabled
Disabled
Disabled
TAG
Access
Access
Access
Access
Entry Detection
Enabled
Enabled
Enabled
Enabled
Default VLAN
ID
100
200
100
200
VLAN Priority
Issue 02 (2010-09-24)
Parameter
NE1
NE2
Board
8-EMS6
8-EMS6
Port
VCTRUNK1
VCTRUNK1
Encapsulation Mapping
Protocol
GFP
GFP
Enabling LCAS
Enabled
Enabled
14-67
Parameter
NE1
NE2
TAG
Tag Aware
Tag Aware
Entry Detection
Enabled
Enabled
Bound Path
VC4-2: VC12-1-VC12-10
VC4-2: VC12-1-VC12-10
NE1
NE2
EPL Service 1
EPL Service 2
EPL Service 1
EPL Service 2
Board
8-EMS
8-EMS
Service Type
EPL
EPL
Direction
Bidirectional
Bidirectional
Source Port
PORT1
PORT2
PORT1
PORT2
100
200
100
200
Sink Port
VCRTUNK1
VCRTUNK1
VCTRUNK2
VCTRUNK2
Sink C-VLAN
(e.g. 1,3-6)
100
200
100
200
1#VC4
NE1
NE2
5-IF1A-1
5-IF1A1-1
VC12:17-26
8-EMS6
VC4-2:1-10
8-EMS6
VC4-2:1-10
Add/Drop
14-68
The VCTRUNK-shared EVPL services of User D and User E occupy VC-12 timeslots
17-26 in the first VC-4 on the radio link from NE1 to NE2.
VC-12 timeslots 1-10 in the second VC-4 of the EMS6 board in slot 8 of NE1 and VC-12
timeslots 1-10 in the second VC-4 of the EMS6 board in slot 8 of NE2 are used to add/drop
the services.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The EMS6 board must be added.
Procedure
Step 1 Configure Ethernet external ports.
1.
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select External
Port.
2.
Click the Basic Attributes tab. After setting the parameters, click Apply.
Parameter
Value Range
Port
PORT1
Description
PORT2
3.
Enabled/
Disabled
Enabled
Working
Mode
Auto-Negotiation
Click the TAG Attributes tab. After setting the parameters, click Apply.
Parameter
Value Range
Port
PORT1
Description
PORT2
TAG
Access
Issue 02 (2010-09-24)
14-69
Parameter
Value Range
Default
VLAN ID
100
Description
200
Entry
Detection
Enabled
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select Internal
Port.
2.
3.
4.
14-70
a.
b.
Set Mapping Protocol and the protocol parameters. After setting the parameters, click
Apply.
Parameter
Value
Range
Description
Port
VCTRUNK
1
Mapping
Protocol
GFP
b.
Set Enabling LCAS and other LCAS parameters. After setting the parameters, click
Apply.
Parameter
Value
Range
Description
Port
VCTRUN
K1
Enabling
LCAS
Enabled
Click the TAG Attributes tab. After setting the parameters, click Apply.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
Parameter
Value Range
Description
Port
VCTRUNK1
TAG
Tag Aware
Entry Detection
5.
Enabled
b.
Click Configuration. Then, the Bound Path Configuration dialog box is displayed.
c.
d.
In Available Bound Paths, set Level and Direction of the bound paths. After setting
the parameters, click OK. Then, click Yes in the dialog box that is displayed.
Paramete
r
Value Range
Description
Configura
ble Ports
VCTRUNK1
Level
VC12
Service
Direction
Bidirectional
Available
Resources
VC4-2
Available
Timeslots
VC12-1 to VC12-10
Activation
Status
Activated
Issue 02 (2010-09-24)
14-71
1.
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Service > Ethernet Line Service from the Function Tree.
2.
Click New. The Create Ethernet Line Service dialog box is displayed. After setting the
parameters, click OK.
l Set the parameters of the Ethernet private line services on PORT1 and VCTRUNK1 as
follows.
Parameter
Value Range
Description
Service Direction
Bidirectional
Source Port
PORT1
Source VLAN
(e.g. 1,3-6)
100
Sink Port
VCTRUNK1
100
l Set the parameters of the Ethernet private line services on PORT2 and VCTRUNK1 as
follows.
Parameter
Value Range
Description
Service Direction
Bidirectional
14-72
Source Port
PORT2
Source VLAN
(e.g. 1,3-6)
200
Sink Port
VCTRUNK1
200
Issue 02 (2010-09-24)
In the NE Explorer, select NE1 and then choose Configuration > SDH Service
Configuration from the Function Tree.
2.
Click Create.
Then, the Create SDH Service dialog box is displayed. Click OK.
Parameter
Value Range
Description
Level
VC12
Direction
Bidirectional
Source
5-IF1A
Source Timeslot
Range(e.g.1,3-6)
17-26
Sink
8-EMS6
Sink VC4
VC4-2
Sink Timeslot
Range(e.g.1,3-6)
1-10
Activate
Immediately
Yes
----End
14-73
The three branches of User F, which are F1, F2, and F3, are located at NE1, NE2, and NE3.
F1 need communicate with F2 and F3, and thus a 10 Mbit/s bandwidth is required.
Communication is not required between F2 and F3.
The Ethernet equipment of User F provides 100 Mbit/s Ethernet electrical ports, of which
the working mode is auto-negotiation, and supports VLAN. The VLAN ID and the number
of the VLANs are unknown and may be changed.
NE 1
User F1
NE3
User F3
Issue 02 (2010-09-24)
In the following example, the 802.1q VB is used to implement EPLAN services of which the
user VLAN is not defined. NE1 needs to be configured with Ethernet switching boards. NE2
and NE3 need to be configured with Ethernet transparent transmission boards.
FAN
FAN
Slot 20
EXT
IF1A
Slot7
EXT
EMS6
Slot8
EXT
IF1A
Slot5
EXT
Slot6
PXC
PXC
Slot3
EXT
PD1
Slot4
PXC
PXC
Slot1
SCC
SCC
Slot2
FAN
FAN
Slot 20
EXT
Slot7
EXT
EFT4
Slot8
EXT
IF1A
Slot5
EXT
Slot6
PXC
PXC
Slot3
EXT
PH1
Slot4
PXC
PXC
Slot1
SCC
SCC
Slot2
VCTRUNK1
NE1:8-EMS6
VC4-2:VC12:1-5
VCTRUNK1
PORT1
User F1
VC4-2:VC12:1-5
VCTRUNK2
NE3:8-EFT4
VC4-2:VC12:6-10
VB1
VCTRUNK1
VC4-2:VC12:1-5
PORT1
User F3
SDH
Issue 02 (2010-09-24)
14-75
NE1
NE2
NE3
Port
PORT1
PORT1
PORT1
Enabled/Disabled
Enabled
Enabled
Enabled
Working Mode
Auto-Negotiation
Auto-Negotiation
Auto-Negotiation
Maximum Frame
Length
1522
1522
1522
Flow Control
Disabled
Disabled
Disabled
Entry Detection
Disabled
NE1
NE2
NE3
Port
VCTRUNK1
VCTRUNK2
VCTRUNK1
VCTRUNK1
Encapsulation
Mapping
Protocol
GFP
GFP
GFP
GFP
Enabling LCAS
Enabled
Enabled
Enabled
Enabled
Entry Detection
Disabled
Disabled
Bound Path
VC4-2:
VC12-1VC12-5
VC4-2:
VC12-6VC12-10
VC4-2:
VC12-1VC12-5
VC4-2:
VC12-1VC12-5
Board
8-EMS
VB Name
VB1
VB Type
802.1d
VB Mount Port
Hub/Spoke
14-76
PORT1
Hub
VCTRUNK1
Spoke
VCTRUNK2
Spoke
Issue 02 (2010-09-24)
1#VC4
NE2
5-IF1A-1
NE3
NE1
5-IF1A1-1
VC12:17-21
8-EMS6
8-EFT4
VC4-2:1-5
VC4-2:1-5
7-IF1A1-1
5-IF1A1-1
VC12:17-21
8-EMS6
8-EFT4
8-EMS6
VC4-2:6-10
VC4-2:1-5
VC4-2:6-15
Add/Drop
The Ethernet LAN service of User F occupies VC-12 timeslots 17-21 in the first VC-4 on
the radio link from NE1 to NE2 and VC-12 timeslots 17-21 in the first VC-4 on the radio
link from NE1 to NE3.
VC-12 timeslots 1-5 in the second VC-4 of the EMS6 board in slot 8 of NE1 and VC-12
timeslots 1-5 in the second VC-4 of the EFT4 board in slot 8 of NE2 to add/drop the Ethernet
LAN service from NE1 to NE2.
VC-12 timeslots 6-10 in the second VC-4 of the EMS6 board in slot 8 of NE1 and VC-12
timeslots 1-5 in the second VC-4 of the EFT4 board in slot 8 of NE3 to add/drop the Ethernet
LAN service from NE1 to NE3.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The EMS6 board must be added.
Procedure
Step 1 Configure Ethernet external ports.
1.
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select External
Port.
2.
Click the Basic Attributes tab. After setting the parameters, click Apply.
Parameter
Value Range
Description
Port
PORT1
Enabled/
Disabled
Issue 02 (2010-09-24)
Enabled
14-77
3.
Parameter
Value Range
Description
Working Mode
AutoNegotiation
The Ethernet equipment of users work in autonegotiation mode. Hence, the Working Mode of
the external ports should be set to AutoNegotiation.
Click the TAG Attributes tab. After setting the parameters, click Apply.
Parameter
Value Range
Description
Port
PORT1
Entry Detection
Disabled
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select Internal
Port. Set the parameters of VCTRCUNK1 and VCTRCUNK2.
2.
3.
14-78
a.
b.
Set Mapping Protocol and the protocol parameters. After setting the parameters, click
Apply.
Paramete
r
Value Range
Description
Port
VCTRUN
K1
Mapping
Protocol
GFP
VCTRU
NK2
b.
Set Enabling LCAS and other LCAS parameters. After setting the parameters, click
Apply.
Paramete
r
Value Range
Description
Port
VCTRU
NK1
VCTRUN
K2
Issue 02 (2010-09-24)
Paramete
r
Value Range
Description
Enabling
LCAS
Enabled
4.
5.
Click the TAG Attributes tab. After setting the parameters, click Apply.
Parameter
Value Range
Port
VCTRUNK1
Entry
Detection
Disabled
Description
VCTRUNK2
b.
Click Configuration. Then, the Bound Path Configuration dialog box is displayed.
c.
d.
In Available Bound Paths, set Level and Direction of the bound paths. After setting
the parameters, click OK. Then, click Yes in the dialog box that is displayed.
Paramete
r
Value Range
Description
Configura
ble Ports
VCTRUN
K1
Level
VC12
Service
Direction
Bidirectional
VCTRUN
K2
Issue 02 (2010-09-24)
VC4-2
14-79
Paramete
r
Value Range
Description
Available
Timeslots
VC12-1 to
VC12-5
VC12-6 to
VC12-10
Activated
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Service > Ethernet LAN Service from the Function Tree.
2.
Click New. The Create Ethernet LAN Service dialog box is displayed. Set the parameters
as follows.
3.
4.
Parameter
Value Range
Description
VB Name
VB1
VB Type
802.1d
Bridge Switch
Mode
SVL/Ingress
Filter Disable
(802.1d)
Click Configure Mount. The Service Mount Configuration dialog box is displayed. After
setting the parameters, click OK.
Parameter
Value Range
Description
selected
forwarding
ports
PORT1,
VCTRUNK1,
VCTRUNK2
Click OK.
14-80
1.
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Service > Ethernet LAN Service from the Function Tree.
2.
Select the created bridge. Click the Service Mount tab. After setting the parameters, click
Apply.
Issue 02 (2010-09-24)
Paramet
er
Value Range
Mount
Port
PORT1
VCTRUN
K1
Description
VCTRUN
K2
Hub/
Spoke
Hub
Spoke
Activatio
n Status
Activated
Spoke
In the NE Explorer, select NE1 from the Object Tree and then choose Configuration >
SDH Service Configuration from the Function Tree.
2.
Click Create. The Create SDH Service dialog box is displayed. After setting the
parameters. Then, click OK.
l Set the parameters of the cross-connections of VCTRUNK1 as follows.
Parameter
Value Range
Description
Level
VC12
Direction
Bidirectional
Issue 02 (2010-09-24)
Source
5-IF1A
Source
Timeslot
Range(e.g.
1,3-6)
17-21
Sink
8-EMS6
Sink VC4
VC4-2
14-81
Parameter
Value Range
Description
Sink Timeslot
Range(e.g.
1,3-6)
1-5
Activate
Immediately
Yes
Value Range
Description
Level
VC12
Direction
Bidirectional
Source
7-IF1A
Source
Timeslot
Range(e.g.
1,3-6)
17-21
Sink
8-EMS6
Sink VC4
VC4-2
Sink Timeslot
Range(e.g.
1,3-6)
6-10
Activate
Immediately
Yes
----End
Issue 02 (2010-09-24)
The three branches of User G are located at NE1, NE2, and NE3 respectively, need form
a LAN, and share a 10 Mbit/s bandwidth.
The three branches of User H are located at NE1, NE2, and NE3 respectively, need form
a LAN, and share a 20 Mbit/s bandwidth.
The Ethernet equipment of User G and User H provide 100 Mbit/s Ethernet electrical ports
of which the working mode is auto-negotiation, and does not support VLAN.
Issue 02 (2010-09-24)
14-83
User G2
User H2
User G1
NE 1
User H1
NE3
User G3
User H3
FAN
FAN
Slot 20
14-84
EXT
IF1A
Slot7
EXT
EMS6
Slot8
EXT
IF1A
Slot5
EXT
Slot6
PXC
PXC
Slot3
EXT
PD1
Slot4
PXC
PXC
Slot1
SCC
SCC
Slot2
Issue 02 (2010-09-24)
FAN
FAN
Slot 20
EXT
Slot7
EXT
EFT4
Slot8
EXT
IF1A
Slot5
EXT
Slot6
PXC
PXC
Slot3
EXT
PH1
Slot4
PXC
PXC
Slot1
SCC
SCC
Slot2
VCTRUNK1
NE1:8-EMS6
VC4-2:VC12:1-5
PORT2
User H2
VCTRUNK2
VLAN 100
VCTRUNK1
PORT1
User G1
VC4-2:VC12:6-15
VC4-2:VC12:1-5
VCTRUNK2
VC4-2:VC12:6-10
VLAN 200
VCTRUNK3
PORT2
User H1
NE3:8-EFT4
VC4-2:VC12:11-20
VCTRUNK4
VCTRUNK1
VC4-2:VC12:21-30
VC4-2:VC12:1-5
VB1
PORT1
User G3
PORT2
User H3
VCTRUNK2
VC4-2:VC12:6-15
SDH
Issue 02 (2010-09-24)
Paramete
r
NE1
NE2
NE3
Board
8-EMS6
8-EFT4
8-EFT4
Port
PORT1
PORT2
PORT1
PORT2
PORT1
PORT2
Enabled/
Disabled
Enabled
Enabled
Enabled
Enabled
Enabled
Enabled
Working
Mode
AutoNegotiatio
n
AutoNegotiatio
n
AutoNegotiatio
n
AutoNegotiatio
n
AutoNegotiatio
n
AutoNegotiatio
n
14-85
Paramete
r
NE1
NE2
NE3
Maximum
Frame
Length
1522
1522
1522
1522
1522
1522
Flow
Control
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
TAG
Access
Access
Entry
Detection
Enabled
Enabled
Default
VLAN ID
100
200
VLAN
Priority
14-86
Param
eter
NE1
NE2
NE3
Board
8-EMS6
8-EFT4
8-EFT4
Port
VCTR
UNK1
VCTR
UNK2
VCTR
UNK3
VCTR
UNK4
VCTR
UNK1
VCTR
UNK2
VCTR
UNK1
VCTR
UNK2
Encaps
ulation
Mappin
g
Protoco
l
GFP
GFP
GFP
GFP
GFP
GFP
GFP
GFP
Enablin
g
LCAS
Enable
d
Enable
d
Enable
d
Enable
d
Enable
d
Enable
d
Enable
d
Enable
d
TAG
Access
Access
Access
Access
Entry
Detecti
on
Enable
d
Enable
d
Enable
d
Enable
d
Default
VLAN
ID
100
100
200
200
VLAN
Priority
Issue 02 (2010-09-24)
Param
eter
NE1
Bound
Path
VC4-2:
VC121VC125
NE2
VC4-2:
VC126VC1210
VC4-2:
VC1211VC1220
VC4-2:
VC1221VC1230
VC4-2:
VC121VC125
NE3
VC4-2:
VC126VC1215
VC4-2:
VC121VC125
VC4-2:
VC126VC1215
Board
8-EMS
VB Name
VB1
VB Type
802.1q
Mount Port
VLAN
Filtering
Table
Filtering
Table
VLAN ID
100
200
Forwarding
Port
PORT1, VCTRUNK1,
VCTRUNK2
PORT2, VCTRUNK3,
VCTRUNK4
1#VC4
NE2
5-IF1A-1
NE1
5-IF1A1-1
VC12:17-21
8-EMS6
8-EFT4
VC4-2:1-5
VC4-2:1-5
VC12:22-31
8-EMS6
8-EFT4
VC4-2:11-20
VC4-2:6-15
7-IF1A1-1
NE3
5-IF1A1-1
VC12:17-21
8-EMS6
8-EFT4
VC4-2:6-10
VC4-2:1-5
VC12:22-31
8-EMS6
8-EFT4
VC4-2:21-30
VC4-2:6-15
Add/Drop
l
Issue 02 (2010-09-24)
14-87
Occupies VC-12 timeslots 17-21 in the first VC-4 on the radio link from NE1 to NE2
and VC-12 timeslots 17-21 in the first VC-4 on the radio link from NE1 to NE3.
Uses VC-12 timeslots 1-5 in the second VC-4 of the EMS6 board in slot 8 of NE1 and
VC-12 timeslots 1-5 in the second VC-4 of the EFT4 board in slot 8 of NE2 to add/drop
services between NE1 and NE2.
Uses VC-12 timeslots 6-10 in the second VC-4 of the EMS6 board in slot 8 of NE1 and
VC-12 timeslots 1-5 in the second VC-4 of the EFT4 board in slot 8 of NE3 to add/drop
services between NE1 and NE3.
l
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The EMS6 board must be added.
Procedure
Step 1 Configure Ethernet external ports.
1.
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select External
Port.
2.
Click the Basic Attributes tab. After setting the parameters, click Apply.
Parameter
Value Range
Port
PORT1
Description
PORT2
Enabled/
Disabled
14-88
Enabled
Issue 02 (2010-09-24)
3.
Parameter
Value Range
Description
Working
Mode
Auto-Negotiation
Click the TAG Attributes tab. After setting the parameters, click Apply.
Parameter
Value Range
Port
PORT1
Description
l The tag attributes of PORT1 and
PORT2 need to be set.
PORT2
Access
100
200
Enabled
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select Internal
Port.
2.
Issue 02 (2010-09-24)
a.
b.
Set Mapping Protocol and the protocol parameters. After setting the parameters, click
Apply.
Param
eter
Value Range
Port
VCTRU
NK1
VCTRU
NK2
Description
VCTR
UNK3
VCTRU
NK4
3.
4.
Param
eter
Value Range
Description
Mappi
ng
Protoc
ol
GFP
b.
Set Enabling LCAS and other LCAS parameters. After setting the parameters, click
Apply.
Param
eter
Value Range
Port
VCTRU
NK1
Enabli
ng
LCAS
Enabled
VCTRU
NK2
Description
VCTR
UNK3
VCTRU
NK4
Click the TAG Attributes tab. After setting the parameters, click Apply.
Param
eter
Value Range
Port
VCTRU
NK1
TAG
Access
VCTRU
NK2
Description
VCTR
UNK3
VCTRU
NK4
14-90
Issue 02 (2010-09-24)
5.
Param
eter
Value Range
Description
Entry
Detecti
on
Enabled
b.
Click Configuration. Then, the Bound Path Configuration dialog box is displayed.
c.
d.
In Available Bound Paths, set Level and Direction of the bound paths. After setting
the parameters, click OK. Then, click Yes in the dialog box that is displayed.
Param
eter
Value Range
Config
urable
Ports
VCTRU
NK1
Level
VC12
Service
Directi
on
Bidirectional
VCTRU
NK2
Description
VCTR
UNK3
VCTRU
NK4
Issue 02 (2010-09-24)
VC4-2
14-91
Param
eter
Value Range
Availa
ble
Timesl
ots
VC12-1
to
VC12-5
VC12-6
to
VC12-1
0
Description
VC1211 to
VC1220
VC12-2
1 to
VC12-3
0
Activated
Activat
ion
Status
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Service > Ethernet LAN Service from the Function Tree.
2.
Click New. The Create Ethernet LAN Service dialog box is displayed. Set the parameters
as follows.
3.
4.
Parameter
Value Range
Description
VB Name
VB1
VB Type
802.1q
Bridge Switch
Mode
IVL/Ingress
Filter Enable
(802.1q)
Click Configure Mount. The Service Mount Configuration dialog box is displayed. After
setting the parameters, click OK.
Parameter
Value Range
Description
selected
forwarding
ports
PORT1, PORT2,
VCTRUNK1,
VCTRUNK2,
VCTRUNK3,
VCTRUNK4
Click OK.
Issue 02 (2010-09-24)
1.
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Service > Ethernet LAN Service from the Function Tree.
2.
Select the created bridge. Click the VLAN Filtering tab. After setting the parameters, click
OK.
Set the parameters of VLAN filtering table 1 as follows.
Parameter
Value Range
Description
VLAN ID(e.g:
1,3-6)
100
selected
forwarding
ports
PORT1,
VCTRUNK1,
VCTRUNK2
Value Range
Description
VLAN ID(e.g:
1,3-6)
200
selected
forwarding
ports
PORT2,
VCTRUNK3,
VCTRUNK4
In the NE Explorer, select NE1 from the Object Tree and then choose Configuration >
SDH Service Configuration from the Function Tree.
2.
Click Create. Then, the Create SDH Service dialog box is displayed. After setting the
parameters, click OK.
l Set the parameters of the cross-connections of VCTRUNK1 as follows.
Parameter
Value Range
Description
Level
VC12
Direction
Bidirectional
Source
Issue 02 (2010-09-24)
5-IF1A
14-93
Parameter
Value Range
Description
Source
Timeslot
Range(e.g.
1,3-6)
17-21
Sink
8-EMS6
Sink VC4
VC4-2
Sink Timeslot
Range(e.g.
1,3-6)
1-5
Activate
Immediately
Yes
Value Range
Description
Level
VC12
Direction
Bidirectional
Source
7-IF1A
Source
Timeslot
Range(e.g.
1,3-6)
17-21
Sink
8-EMS6
Sink VC4
VC4-2
Sink Timeslot
Range(e.g.
1,3-6)
6-10
Activate
Immediately
Yes
14-94
Issue 02 (2010-09-24)
Parameter
Value Range
Description
Level
VC12
Direction
Bidirectional
Source
5-IF1A
Source
Timeslot
Range(e.g.
1,3-6)
22-31
Sink
8-EMS6
Sink VC4
VC4-2
Sink Timeslot
Range(e.g.
1,3-6)
11-20
Activate
Immediately
Yes
Value Range
Description
Level
VC12
Direction
Bidirectional
Issue 02 (2010-09-24)
Source
7-IF1A
Source
Timeslot
Range(e.g.
1,3-6)
22-31
Sink
8-EMS6
14-95
Parameter
Value Range
Description
Sink VC4
VC4-2
Sink Timeslot
Range(e.g.
1,3-6)
21-30
Activate
Immediately
Yes
----End
Precautions
NOTE
For details on the services configured in this example, see the description of the EVPL service that is based on
QinQ in 14.2.6.1 EVPL Services Based on QinQ.
Procedure
Step 1 Set the attributes of the ports of NE1 and NE4. For details, see 14.3.7.1 Configuring External
Ethernet Ports.
Step 2 Set the attributes of the VCTRUNKs of NE1-NE4. For details, see 14.4.7.1 Configuring the
Internal Port of the Ethernet Board.
Step 3 Configure a QinQ service from PORT1 to VCTRUNK1 of NE1. For details, see 14.1.5.4
Creating QinQ Line Services.
Set the parameters as follows:
l Set Direction to Bidirectional.
l Set Operation Type to Add S-VLAN.
l Set Source Port to PORT1.
l Do not set Source C-VLAN (e.g. 1,3-6).
l Set Sink Port to VCTRUNK1.
l Do not set Sink C-VLAN (e.g. 1,3-6).
14-96
Issue 02 (2010-09-24)
14-97
Precautions
NOTE
For details on the services configured in this example, refer to the example described in 14.2.6.2 EVPLAN
Services Based on the IEEE 802.1ad Bridge.
The following configuration flow is based on the configuration of services on convergence node NE3.
Procedure
Step 1 Set Network Attributes of PORT1 and PORT2 of the Ethernet switching board of NE3 to CAware. For details, see 14.3.7.1 Configuring External Ethernet Ports.
Step 2 Set Network Attributes of VCTRUNNK1 and VCTRUNK2 of the Ethernet switching board
of NE3 to C-Aware. For details, see 14.4.7.1 Configuring the Internal Port of the Ethernet
Board.
Step 3 Configure the EVPLAN services that are based on the IEEE 802.1ad bridge for NE3. For details,
see 14.1.4.4 Creating the EVPLAN Services That Are Based on the IEEE 802.1ad
Bridge.
Set the parameters for the IEEE 802.1ad bridge as follows:
l Set VB Name to VB1.
l Set VB Type to 802.1ad.
l Set Bridge Switch Mode to IVL\Ingress Filter Enable.
l Bridge Learning Mode is set to IVL automatically.
l Ingress Filter is set to Enabled automatically.
14-98
Issue 02 (2010-09-24)
Parameter Value
Operation
Type
VB Port
Mount Port
PORT1
PORT2
VCTRUNK1
VCTRUNK2
C-VLAN
10
20
30
40
S-VLAN
100
200
100
200
100
200
Step 4 Create the VLAN filtering table. For details, see 14.1.4.5 Creating the VLAN Filter Table.
Set the parameters for the VLAN filtering table of the VoIP services as follows:
l Set VLAN ID to 100.
l Select the corresponding forwarding ports, including PORT1, VCTRUNK1, and
VCTRUNK2.
Set the parameters for the VLAN filtering table of the HSI services as follows:
l Set VLAN ID to 200.
l Select the corresponding forwarding ports, including PORT2, VCTRUNK1, and
VCTRUNK2.
Step 5 Create the cross-connection from the paths that are bound to the VCTRUNK to the corresponding
timeslots on the line.
----End
14-99
the following example, the service planning covers all the parameter information required for
configuring the NEs.
14.1.13.4 Service Planning (Ethernet Services Accessed Through the IFH2 Board)
According to the service requirements and the equipment specifications that are shown in the
networking diagram, the network planning department can plan all the services of the NEs. In
the following example, the service planning covers all the parameter information required for
configuring the NEs.
14.1.13.5 Configuring NE1 (Microwave Services)
You can configure the microwave service data of NE1 based on the parameters of the service
planning, by using the NMS.
14.1.13.6 Configuring NE1 (Ethernet Services Accessed Through the EMS6 Board)
You can configure the Ethernet services that are accessed through the EMS6 board of NE1 based
on the parameters of the service planning, by using the NMS.
14.1.13.7 Configuring NE2 (Microwave Services)
You can configure the microwave service data of NE2 based on the parameters of the service
planning, by using the NMS.
14.1.13.8 Configuring NE2 (Ethernet Services Accessed Through the EMS6 Board)
You can configure the Ethernet services that are accessed through the EMS6 board of NE2 based
on the parameters of the service planning, by using the NMS.
14.1.13.9 Configuring NE2 (Ethernet Services Accessed Through the IFH2 Board)
You can configure the attributes and CoS of the Ethernet ports of the IFH2 board based on the
parameters of the engineering plan so that Ethernet services can be accessed to the IFH2 board
normally, thus meeting the requirement for CoS scheduling.
14.1.13.10 Configuring NE3 (Ethernet Services)
You can configure the Ethernet service data of NE3 based on the parameters of the service
planning, by using the NMS.
14-100
The Ethernet equipment of user A, user B, and user C provides 100 Mbit/s auto-negotiative
Ethernet electrical interfaces. The Ethernet equipment of user A does not support VLAN
tags. The services of user A are frames that do not carry VLAN tags, namely, untagged
framed. The Ethernet equipment of user B and user C supports VLAN tags. Hence, the
services of user B and user C are frames that carry VLAN tags, namely, tagged frames.
User A has two branches (user A1 and user A2), which are located at NE1 and NE2. There
are 4xE1 services and Ethernet services between the two branches. The Ethernet services
are Internet services, whose maximum bandwidth is 10 Mbit/s. The bandwidth of the
Internet services can be allocated flexibly. After the user services are accessed, the default
VLAN ID of 300 is added to the services.
User B has two branches (user B1 and B2), which are located at NE1 and NE2. There are
2xE1 services and Ethernet services between the two branches. One part of the Ethernet
services are voice over IP (VoIP) services, whose maximum bandwidth is 4 Mbit/s. The
transmission of the VoIP services must be stable. The VLAN ID is 100. The other part of
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
the Ethernet services are Internet services, whose maximum bandwidth is 20 Mbit/s. The
bandwidth of the Internet services can be allocated flexibly. The VLAN ID is 200.
l
The radio link between NE1 and NE2 uses the 1+1 HSB configuration.
User C has two branches, which are located at NE2 and NE3. There are 4xE1 services and
Ethernet services between the two branches. One part of the Ethernet services are VoIP
services, whose maximum bandwidth is 4 Mbit/s. The transmission of the VoIP services
must be stable and the VLAN priority level is 7. The other part of the Ethernet services are
Internet services, whose maximum bandwidth is 20 Mbit/s. The bandwidth of the Internet
services can be allocated flexibly and the VLAN priority level is 1.
NE Attributes
Issue 02 (2010-09-24)
Parameter
NE1
NE2
NE3
Equipment Type
IDU 620
IDU 620
IDU 605 1F
NE ID
101
102
103
Extended ID
9 (default value)
9 (default value)
9 (default value)
14-101
Parameter
NE1
NE2
NE3
NE IP
129.9.0.101
129.9.0.102
129.9.0.103
H-polarization
NE2
(IDU 620)
Tx Hi 14930 MHz
14510 MHz
Tx Low
Tx Low
14952 MHz
14532 MHz
NE3
(IDU 605 1F)
V-polarization
Tx Hi
NOTE
NE1, NE2, and NE3 use the ODUs that operate on sub-band A of the 15 GHz frequency band with a T/R
spacing of 420 MHz. Hence, fewer types of spare parts are required.
In addition, the networking diagram shows the capacity information of the two Hybrid radio
links, as listed in Table 14-19.
Table 14-19 Link capacity
14-102
Radio Link
Number of
E1 Services
Capacity of
E1 Services
(Mbit/s)
Assured
Ethernet Service
Capacity (Mbit/
s)
Maximum
Ethernet Service
Capacity (Mbit/s)
Link between
NE1 and NE2
12
34
Link between
NE2 and NE3
24
Issue 02 (2010-09-24)
The Hybrid radio link can be planned properly according to the previous information and the
actual engineering requirements. Table 14-20 provides the planning information of the Hybrid
radio link in this example.
Table 14-20 Information for planning a radio link
Parameter
Link 1
Link 2
TX High Station
NE1
NE3
TX Low Station
NE2
NE2
14930
14952
14510
14532
T/R Spacing(MHz)
420
420
TX Power(dBm)
Channel Spacing(MHz)
14
14
AM Enable Status
Enable
Enable
AM Mode
Asymmetric
Asymmetric
QPSK
QPSK
32QAM
32QAM
Radio Link ID
101
102
Disabled
Disabled
1+1 HSB
1+0
Polarization Directiona
H (horizontal polarization)
V (vertical polarization)
NOTE
a: The planning information that is not related to the configuration of the IDU (except for the polarization direction) is not provided
in this example.
Issue 02 (2010-09-24)
14-103
Board Layout
Figure 14-43 Board layout of the IDU (NE1)
FAN
FAN
Slot 20
EXT
IFH2
Slot7
EXT
Slot8
EXT
IFH2
Slot5
EXT
EMS6
Slot6
PXC
PXC
Slot3
EXT
PH1
Slot4
PXC
PXC
Slot1
SCC
SCC
Slot2
FAN
FAN
Slot 20
EXT
IFH2
Slot7
IFH2
EXT
Slot8
EXT
IFH2
Slot5
EXT
EMS6
Slot6
PXC
PXC
Slot3
EXT
PH1
Slot4
PXC
PXC
Slot1
SCC
SCC
Slot2
SCC
EOW
PH1
EMS4
IFH1
Slot 1
Slot 2
Slot 3
Slot 4
Slot 5
Slot 8
NOTE
The ODU that is connected to the IF board in slot n occupies logical slot 10+n. The logical slot of the ODU is
not shown in the board layout diagram. In the case of the IDU 620, "n" ranges from five to eight whereas in the
case of the IDU 605, "n" is 7 or 8.
14-104
Parameter
NE1
NE2
Protection Group ID
Protection Type
Working Slot
Slot 5
Slot 5
Protection Slot
Slot 7
Slot 7
Revertive Mode
Issue 02 (2010-09-24)
Parameter
NE1
NE2
WTR Time(s)
Timeslot Allocation
Figure 14-46 Timeslot allocation diagram
Station
NE2
NE3
5-IFH2 8-IFH2
8-IFH1
NE1
5-IFH2
E1: 1-4
4-PH1:7-10
Timeslot
4-PH1:1-4
E1: 1-6
4-PH1:1-6
4-PH1:1-6
Add/Drop
As shown in Figure 14-46, the timeslots are allocated for the services between the NEs as
follows.
l
Issue 02 (2010-09-24)
14-105
Clock Information
Figure 14-47 Clock synchronization scheme
NE1
NE2
BITS
External clock
source 1/Internal
clock source
5-IFH2(SDH-1)/
7-IFH2(SDH-1)/
Internal clock source
NE1
NE2
Clock
Source
First Clock
Source
5-IFH2(SDH-1)
Second
Clock
Source
7-IFH2(SDH-1)
Third Clock
Source
Orderwire Information
Table 14-23 Orderwire information
Parameter
NE1
NE2
NE3
Telephone No.
101
102
103
Selected Orderwire
Port
5-IFH2-1
5-IFH2-1
Orderwire Occupied
Bytes
E1
E1
14.1.13.3 Service Planning (Ethernet Services Accessed Through the EMS6 Board)
According to the service requirements and the equipment specifications that are shown in the
networking diagram, the network planning department can plan all the services of the NEs. In
14-106
Issue 02 (2010-09-24)
the following example, the service planning covers all the parameter information required for
configuring the NEs.
NE1:
6-EMS6
NE2: 5-IFH2
NE2: (main)
15-ODU
(main)
PORT1
PORT3
(main)
PORT3
(main)
User
A1
User
B1
NE2:
6-EMS6
PORT1
PORT1
PORT1
LAG
LAG
PORT2
PORT2
NE1:
17-ODU
(standby)
PORT4
(slave)
NE2:
17-ODU
(standby)
PORT1
User
A2
User
B2
PORT4
(slave)
PORT1
NE1: 7-IFH2
(standby)
NE2: 7-IFH2
(standby)
Network cable
IF cable
NE1
NE2
Board
6-EMS6
6-EMS6
Port
PORT1-PORT4
PORT1-PORT4
Enabled/Disabled
Enabled
Enabled
Working Mode
Auto-Negotiation
Auto-Negotiation
1522
1522
Flow Control
Disabled
Disabled
TAG
Enabled
Enabled
Entry Detection
Issue 02 (2010-09-24)
14-107
NE1
NE2
Board
5-IFH2
7-IFH2
5-IFH2
7-IFH2
Enabled/
Disabled
Enabled
Enabled
Enabled
Enabled
Working Mode
AutoNegotiation
AutoNegotiation
AutoNegotiation
AutoNegotiation
Flow Control
Disabled
Disabled
Disabled
Disabled
NE1
Private Line
Service 1 (User A1)
Private Line
Service 2 (User B1,
VoIP Service)
Private Line
Service 3 (User B1,
Internet Service)
Board
6-EMS
Service Type
EPL
EPL
EPL
Service Direction
Bidirectional
Bidirectional
Bidirectional
Source Port
PORT1
PORT2
PORT2
Source C-VLAN
(e.g. 1,3-6)
300
100
200
Sink Port
PORT3
PORT3
PORT3
300
100
200
NE2
Private Line
Service 1 (User A2)
14-108
Private Line
Service 2 (User B2,
VoIP Service)
Private Line
Service 3 (User B2,
Internet Service)
Board
6-EMS
Service Type
EPL
EPL
EPL
Service Direction
Bidirectional
Bidirectional
Bidirectional
Source Port
PORT1
PORT2
PORT2
Issue 02 (2010-09-24)
Parameter
NE2
Private Line
Service 1 (User A2)
Private Line
Service 2 (User B2,
VoIP Service)
Private Line
Service 3 (User B2,
Internet Service)
Source C-VLAN
(e.g. 1,3-6)
300
100
200
Sink Port
PORT3
PORT3
PORT3
300
100
200
NE1
Board
6-EMS
Flow
Type
PORT
+VLAN
Flow
PORT
+VLAN
Flow
PORT
+VLAN
Flow
Port
PORT1
PORT2
VLAN
ID
300
Bound
CAR
Bound
CoS
User A1
NE2
User B1,
VoIP
Service
User B1,
Internet
Service
User A2
User B2,
VoIP
Service
User B2,
Internet
Service
PORT
+VLAN
Flow
PORT
+VLAN
Flow
PORT
+VLAN
Flow
PORT2
PORT1
PORT2
PORT2
100
200
300
100
200
6-EMS
Issue 02 (2010-09-24)
Parameter
NE1
NE2
Board
6-EMS
6-EMS
CAR ID
Enabled/Disabled
Enabled
Enabled
Enabled
Enabled
14-109
Parameter
NE1
NE2
20480
10240
20480
20480
40960
20480
40960
NOTE
a: You can limit the Ethernet service rate on a port of the EMS6 board, by performing the corresponding
configuration of the CAR that is bound with the port.
NE1
NE2
Board
6-EMS
6-EMS
CoS ID
CoS Type
simple
simple
simple
simple
simple
simple
CoS Priority
NE1
NE2
Board
6-EMS
6-EMS
LAG No.
LAG Name
LAG_1
LAG_1
LAG Type
Manual
Manual
Load Sharing
Non-Sharing
Non-Sharing
Main Port
PORT3
PORT3
PORT4
PORT4
14.1.13.4 Service Planning (Ethernet Services Accessed Through the IFH2 Board)
According to the service requirements and the equipment specifications that are shown in the
networking diagram, the network planning department can plan all the services of the NEs. In
14-110
Issue 02 (2010-09-24)
the following example, the service planning covers all the parameter information required for
configuring the NEs.
Figure 14-49 Configuration diagram of the Ethernet services between NE2 and NE3
NE2:
18-ODU
User
C2
NE3:
5-EMS4
NE3:
8-IFH1
NE2:
8-IFH2
NE3:
18-ODU
PORT1
PORT1
User
C1
Network cable
IF cable
NE2
NE3
Board
8-IFH2
5-EMS4
Port
PORT1
PORT1
Enabled/Disabled
Enabled
Enabled
Working Mode
Auto-Negotiation
Auto-Negotiation
Autonegotiation Flow
Control Mode
Disabled
CoS Priority
Issue 02 (2010-09-24)
Parameter
Board
5-EMS4
VB Name
VB1
VB Type
802.1d
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
14-111
Parameter
Mount Port
PORT1, IFUP1
Prerequisite
You must be an NM user with "NE operator" authority or higher.
You must be logged in to the NE.
All the required boards must be added.
Procedure
Step 1 Modify the NE ID.
Set the parameters as follows:
l New ID: 101
l New Extended ID: 9
Step 2 Modify the IP address of an NE.
Set the parameters as follows:
l IP: 129.9.0.101
Step 3 Configure IF 1+1 protection.
1.
In the NE Explorer, select NE1 and then choose Configuration > IF 1+1 Protection from
the Function Tree.
2.
Click Create.
Then, the Create IF 1+1 Protection dialog box is displayed. Click OK.
14-112
Parameter
Value Range
Description
Protection
Group ID
Working Mode
HSB
Issue 02 (2010-09-24)
Parameter
Value Range
Description
Revertive Mode
Revertive
600
WTR Time(s)
Enable Reverse
Switching
Enable
Working Board
5-IFH2-1
Protection Board
7-IFH2-1
In the NE Explorer, select the 5-IFH2 board and then choose Configuration > Hybrid/
AM Configuration from the Function Tree.
2.
Click the Hybrid/AM Configuration tab. After setting the parameters, click Apply.
Parameter
Value Range
Description
IF Channel
Bandwidth
14M
Issue 02 (2010-09-24)
E1 Capacity
AM Mode
Asymmetric
14-113
Parameter
Value Range
Description
AM Enable
Status
Enable
Modulation
Mode of the
Assured AM
Capacity
QPSK
Modulation
Mode of the Full
AM Capacity
32QAM
NOTE
The 5-IFH2 and 7-IFH2 boards are configured as a 1+1 HSB protection group. The 5-IFH2 functions as
the main IF board and the 7-IFH2 functions as the standby IF board. The system automatically sets the
relevant parameters of the standby board (7-IFH2). Hence, you need not set the parameters manually.
In the NE Explorer, select NE1 and then choose Configuration > Link Configuration
from the Function Tree.
2.
3.
Set the information about the 5-IFH2. Then, click Apply. Set the information about the 15ODU on the radio link. Then, click Apply.
Parameter
Value Range
Description
Link ID
101
14-114
ATPC Enable
Status
Disabled
TX Frequency
(MHz)
14930.0
T/R Spacing
(MHz)
420.0
TX Power
(dBm)
10.0
Issue 02 (2010-09-24)
Parameter
Value Range
Description
TX Status
unmute
In the NE Explorer, select NE1 and then choose Configuration > SDH Service
Configuration from the Function Tree.
2.
Click Create. Then, the Create SDH Service dialog box is displayed. Configure the crossconnections of the service. Click OK.
Parameter
Value Range
Description
Level
VC12
Direction
Bidirectional
Source
4-PH1
Source
Timeslot Range
(e.g.1,3-6)
1-6
Sink
5-IFH2
Sink Port
Sink VC4
VC4-1
Sink Timeslot
Range(e.g.
1,3-6)
1-6
14-115
In the NE Explorer, select NE1 and then choose Configuration > Clock > Clock Source
Priority from the Function Tree.
2.
Click Create. The Add Clock Source dialog box is displayed. After setting the parameters,
click OK.
3.
Parameter
Value Range
Description
Clock Source
5-IFH2-1(SDH)
7-IFH2-1(SDH)
Value Range
Description
Clock
Source
5-IFH2-1
(SDH)
7-IFH2-1
(SDH)
Internal
Clock
Source
Clock
Source
Priority
Sequence
(1 is the
highest)
----End
14.1.13.6 Configuring NE1 (Ethernet Services Accessed Through the EMS6 Board)
You can configure the Ethernet services that are accessed through the EMS6 board of NE1 based
on the parameters of the service planning, by using the NMS.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
You must be logged in to the NE.
The EMS6 board must be added.
The IFH2 board must be added.
14-116
Issue 02 (2010-09-24)
Procedure
Step 1 Configure Ethernet external ports of the IFH2 board.
1.
In the NE Explorer, select the IFH2 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select External
Port.
2.
Click the Basic Attributes tab. After setting the basic attributes of the port, click Apply.
Parameter
Value Range
Description
Port
PORT1
3.
Enabled/
Disabled
Enabled
Working Mode
AutoNegotiation
Click the Flow Control tab. After setting the flow control mode of the port, click Apply.
Parameter
Value Range
Description
Port
PORT1
NonAutonegotiatio
n Flow Control
Mode
Disabled
Autonegotiatio
n Flow Control
Mode
Disabled
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select External
Port.
2.
Click the Basic Attributes tab. After setting the basic attributes of the ports, click
Apply.
Issue 02 (2010-09-24)
14-117
Parameter
Value Range
Description
Port
PORT1-PORT4
3.
Enabled/
Disabled
Enabled
Working Mode
AutoNegotiation
Click the Flow Control tab. After setting the flow control mode of the ports, click
Apply.
Parameter
Value Range
Description
Port
PORT1-PORT4
4.
NonAutonegotiatio
n Flow Control
Mode
Disabled
Autonegotiatio
n Flow Control
Mode
Disabled
Click the TAG Attributes tab. After setting the parameters, click Apply.
Parameter
Value Range
Description
Port
PORT1-PORT4
14-118
Issue 02 (2010-09-24)
Parameter
Value Range
Description
TAG
l In this
example,
TAG is set to
Access for
PORT1.
l In this
example,
TAG is set to
Tag Aware
for PORT2PORT4.
Default VLAN
ID
300
Entry Detection
Enabled
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Service > Ethernet Line Service from the Function Tree.
2.
Click New. Then, the Create Ethernet Line Service dialog box is displayed.
3.
Set the attributes of the three Ethernet private line services. Then, click OK.
l Set the parameters of Ethernet private line service 1 as follows.
Parameter
Value Range
Description
Service Type
EPL
Service
Direction
Bidirectional
Issue 02 (2010-09-24)
Source Port
PORT1
Source VLAN
(e.g.1, 3-6)
300
Sink Port
PORT3
14-119
Parameter
Value Range
Description
Sink VLAN
(e.g.1, 3-6)
300
Value Range
Description
Service Type
EPL
Service
Direction
Bidirectional
Source Port
PORT2
Source VLAN
(e.g.1, 3-6)
100
Sink Port
PORT3
Sink VLAN
(e.g.1, 3-6)
100
Value Range
Description
Service Type
EPL
Direction
Bidirectional
14-120
Source Port
PORT2
Source VLAN
(e.g.1, 3-6)
200
Sink Port
PORT3
Sink VLAN
(e.g.1, 3-6)
200
Issue 02 (2010-09-24)
In the NE Explorer, select the EMS6 board and then choose Configuration > QoS
Management > Flow Management from the Function Tree.
b.
c.
Click New. The New Flow dialog box is displayed. Set the parameters of the three
flows. Then, click OK.
Value Range
Description
Flow Type
PORT+VLAN
Flow
Port
PORT1
VLAN ID
300
Value Range
Description
Flow Type
PORT+VLAN
Flow
Port
PORT2
VLAN ID
100
2.
Issue 02 (2010-09-24)
Parameter
Value Range
Description
Flow Type
PORT+VLAN
Flow
Port
PORT2
VLAN ID
200
14-121
a.
In the NE Explorer, select the EMS6 board and then choose Configuration > QoS
Management > Flow Management from the Function Tree.
b.
c.
Click New. The New CAR dialog box is displayed. Select the parameters of the two
CARs. Then, click OK.
Value Range
Description
CAR ID
Enabled/
Disabled
Enabled
Committed
Information
Rate(kbit/s)
10240
Committed
Burst Size
(kbyte)
Peak
Information
Rate(kbit/s)
20480
Maximum
Burst Size
(kbyte)
14-122
Parameter
Value Range
Description
CAR ID
Enabled/
Disabled
Enabled
Issue 02 (2010-09-24)
3.
Parameter
Value Range
Description
Committed
Information
Rate(kbit/s)
20480
Committed
Burst Size
(kbyte)
Peak
Information
Rate(kbit/s)
40960
Maximum
Burst Size
(kbyte)
In the NE Explorer, select the EMS6 board and then choose Configuration > QoS
Management > Flow Management from the Function Tree.
b.
c.
Click New. The New CoS dialog box is displayed. Set the parameters of the three
CoSs. Then, click OK..
Value Range
Description
CoS ID
CoS Type
simple
CoS Priority
Issue 02 (2010-09-24)
14-123
Parameter
Value Range
Description
CoS ID
CoS Type
simple
CoS Priority
4.
14-124
Parameter
Value Range
Description
CoS ID
CoS Type
simple
CoS Priority
In the NE Explorer, select the EMS6 board and then choose Configuration > QoS
Management > Flow Management from the Function Tree.
b.
Click the Flow Configuration tab. After setting the parameters, click OK.
Paramet
er
Value Range
Port
PORT1
PORT2
PORT2
Flow
Type
PORT
+VLAN
Flow
PORT
+VLAN
Flow
PORT
+VLAN
Flow
VLAN ID
300
100
200
Description
Issue 02 (2010-09-24)
Paramet
er
Value Range
Description
Bound
CAR
Bound
CoS
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Interface Management > Ethernet Link Aggregation Management from the Function
Tree.
2.
3.
Click New. The Create Link Aggregation Group dialog box is displayed. After setting
the parameters, click OK. Then, click OK in the dialog box that is displayed.
Parameter
Value Range
Description
LAG No.
LAG Name
LAG_1
LAG Type
Manual
Load Sharing
Non-Sharing
Main Port
PORT3
Selected Slave
Ports
PORT4
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Issue 02 (2010-09-24)
14-125
Procedure
Step 1 Modify the NE ID.
Set the parameters as follows:
l New ID: 102
l New Extended ID: 9
Step 2 Modify the IP address of an NE.
Set the parameters as follows:
l IP: 129.9.0.102
Step 3 Configure IF 1+1 protection.
1.
In the NE Explorer, select NE1 and then choose Configuration > IF 1+1 Protection from
the Function Tree.
2.
Click Create.
Then, the Create IF 1+1 Protection dialog box is displayed. Click OK.
Parameter
Value Range
Description
Protection
Group ID
Working Mode
HSB
Revertive Mode
Revertive
600
WTR Time(s)
Enable Reverse
Switching
Enable
14-126
Issue 02 (2010-09-24)
Parameter
Value Range
Description
Working Board
5-IFH2-1
Protection Board
7-IFH2-1
In the NE Explorer, select the 5-IFH2 and then choose Configuration > Hybrid/AM
Configuration from the Function Tree.
2.
Click the Hybrid/AM Configuration tab. After setting the parameters, click Apply.
Parameter
Value Range
Description
IF Channel
Bandwidth
14M
Issue 02 (2010-09-24)
E1 Capacity
AM Mode
Asymmetric
AM Enable
Status
Enable
Modulation
Mode of the
Assured AM
Capacity
QPSK
Modulation
Mode of the
Full AM
Capacity
32QAM
14-127
The 5-IFH2 and 7-IFH2 boards are configured as a 1+1 HSB protection group. The 5-IFH2 functions
as the main IF board and the 7-IFH2 functions as the standby IF board. The system automatically
sets the relevant parameters of the standby board (7-IFH2). Hence, you need not set the parameters
manually.
3.
In the NE Explorer, select the 8-IFH2 and then choose Configuration > Hybrid/AM
Configuration from the Function Tree.
4.
Click the Hybrid/AM Configuration tab. After setting the parameters, click Apply.
Parameter
Value Range
Description
IF Channel
Bandwidth
14M
E1 Capacity
AM Mode
Asymmetric
AM Enable
Status
Enable
Modulation
Mode of the
Assured AM
Capacity
QPSK
Modulation
Mode of the
Full AM
Capacity
32QAM
14-128
Issue 02 (2010-09-24)
In the NE Explorer, select NE2 and then choose Configuration > Link Configuration
from the Function Tree.
2.
3.
Set the information about the 5-IFH2 and 15-ODU on one radio link. Then, click Apply.
Set the information about the 8-IFH2 and 18-ODU on the other radio link. Then, click
Apply.
l Set the parameters of the 5-IFH2 and 15-ODU as follows.
Parameter
Value Range
Description
Link ID
101
ATPC Enable
Status
Disabled
TX Frequency
(MHz)
14510.0
T/R Spacing
(MHz)
420.0
TX Power
(dBm)
10.0
TX Status
unmute
Value Range
Description
Link ID
102
Issue 02 (2010-09-24)
ATPC Enable
Status
Disabled
TX Frequency
(MHz)
14532.0
T/R Spacing
(MHz)
420.0
14-129
Parameter
Value Range
Description
TX Power
(dBm)
10.0
TX Status
unmute
In the NE Explorer, select NE1 and then choose Configuration > SDH Service
Configuration from the Function Tree.
2.
Click Create. The Create SDH Service dialog box is displayed. After setting the
parameters. Then, click OK.
l Configure the cross-connections of the E1 services of NE1 and NE2 as follows.
Parameter
Value Range
Description
Level
VC12
Direction
Bidirectional
Source
4-PH1
Source
Timeslot
Range(e.g.
1,3-6)
1-6
Sink
5-IFH2
Sink Port
Sink VC4
VC4-1
Sink Timeslot
Range(e.g.
1,3-6)
1-6
Issue 02 (2010-09-24)
Parameter
Value Range
Description
Level
VC12
Direction
Bidirectional
Source
4-PH1
Source
Timeslot
Range(e.g.
1,3-6)
7-10
Sink
8-IFH2
Sink Port
Sink VC4
VC4-1
Sink Timeslot
Range(e.g.
1,3-6)
1-4
In the NE Explorer, select NE2 and then choose Configuration > Clock > Clock Source
Priority from the Function Tree.
2.
Click Create. The Add Clock Source dialog box is displayed. Select the clock sources.
Then, click OK.
Issue 02 (2010-09-24)
Parameter
Value Range
Description
Clock Source
External Clock
Source 1
14-131
3.
Value Range
Description
Clock
Source
External
Clock Source
1
Internal
Clock Source
Clock
Source
Priority
Sequence(1
is the
highest)
----End
14.1.13.8 Configuring NE2 (Ethernet Services Accessed Through the EMS6 Board)
You can configure the Ethernet services that are accessed through the EMS6 board of NE2 based
on the parameters of the service planning, by using the NMS.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
You must be logged in to the NE.
The EMS6 board must be added.
The IFH2 board must be added.
Procedure
Step 1 Configure Ethernet external ports of the IFH2 board.
1.
In the NE Explorer, select the IFH2 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select External
Port.
2.
Click the Basic Attributes tab. After setting the basic attributes of the port, click Apply.
Parameter
Value Range
Description
Port
PORT1
14-132
Enabled/
Disabled
Enabled
Working Mode
AutoNegotiation
Issue 02 (2010-09-24)
3.
Click the Flow Control tab. After setting the flow control mode of the port, click Apply.
Parameter
Value Range
Description
Port
PORT1
NonAutonegotiatio
n Flow Control
Mode
Disabled
Autonegotiatio
n Flow Control
Mode
Disabled
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select External
Port.
2.
Click the Basic Attributes tab. After setting the basic attributes of the ports, click
Apply.
Parameter
Value Range
Description
Port
PORT1-PORT4
3.
Issue 02 (2010-09-24)
Enabled/
Disabled
Enabled
Working Mode
AutoNegotiation
Click the Flow Control tab. After setting the flow control mode of the ports, click
Apply.
14-133
Parameter
Value Range
Description
Port
PORT1-PORT4
4.
NonAutonegotiatio
n Flow Control
Mode
Disabled
Autonegotiatio
n Flow Control
Mode
Disabled
Click the TAG Attributes tab. After setting the parameters, click Apply.
Parameter
Value Range
Description
Port
PORT1-PORT4
l In this
example,
TAG is set to
Access for
PORT1.
TAG
l In this
example,
TAG is set to
Tag Aware
for PORT2PORT4.
Default VLAN
ID
300
Entry Detection
Enabled
14-134
Issue 02 (2010-09-24)
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Service > Ethernet Line Service from the Function Tree.
2.
Click New. Then, the Create Ethernet Line Service dialog box is displayed.
3.
Set the attributes of the three Ethernet private line services. Then, click OK.
l Set the parameters of Ethernet private line service 1 as follows.
Parameter
Value Range
Description
Service Type
EPL
Direction
Bidirectional
Source Port
PORT1
Source VLAN
(e.g.1, 3-6)
300
Sink Port
PORT3
Sink VLAN
(e.g.1, 3-6)
300
Value Range
Description
Service Type
EPL
Direction
Bidirectional
Issue 02 (2010-09-24)
Source Port
PORT2
Source VLAN
(e.g.1, 3-6)
100
Sink Port
PORT3
14-135
Parameter
Value Range
Description
Sink VLAN
(e.g.1, 3-6)
100
Value Range
Description
Service Type
EPL
Direction
Bidirectional
Source Port
PORT2
Source VLAN
(e.g.1, 3-6)
200
Sink Port
PORT3
Sink VLAN
(e.g.1, 3-6)
200
In the NE Explorer, select the EMS6 board and then choose Configuration > QoS
Management > Flow Management from the Function Tree.
b.
c.
Click New. The New Flow dialog box is displayed. Select the parameters of the eight
flows. Then, click OK.
14-136
Parameter
Value Range
Description
Flow Type
PORT+VLAN
Flow
Port
PORT1
VLAN ID
300
Issue 02 (2010-09-24)
Value Range
Description
Flow Type
PORT+VLAN
Flow
Port
PORT2
VLAN ID
100
2.
Parameter
Value Range
Description
Flow Type
PORT+VLAN
Flow
Port
PORT2
VLAN ID
200
In the NE Explorer, select the EMS6 board and then choose Configuration > QoS
Management > Flow Management from the Function Tree.
b.
c.
Click New. The New CAR dialog box is displayed. Set the parameters of the two
CARs. Then, click OK.
Issue 02 (2010-09-24)
Parameter
Value Range
Description
CAR ID
Enabled/
Disabled
Enabled
Committed
Information
Rate(kbit/s)
10240
Committed
Burst Size
(kbyte)
14-137
Parameter
Value Range
Description
Peak
Information
Rate(kbit/s)
20480
Maximum
Burst Size
(kbyte)
14-138
Parameter
Value Range
Description
CAR ID
Enabled/
Disabled
Enabled
Committed
Information
Rate(kbit/s)
20480
Committed
Burst Size
(kbyte)
Peak
Information
Rate(kbit/s)
40960
Maximum
Burst Size
(kbyte)
Issue 02 (2010-09-24)
3.
In the NE Explorer, select the EMS6 board and then choose Configuration > QoS
Management > Flow Management from the Function Tree.
b.
c.
Click New. The New CoS dialog box is displayed. Set the parameters of the three
CoSs. Then, click OK.
Value Range
Description
CoS ID
CoS Type
simple
CoS Priority
Value Range
Description
CoS ID
CoS Type
simple
CoS Priority
Issue 02 (2010-09-24)
Parameter
Value Range
Description
CoS ID
CoS Type
simple
CoS Priority
14-139
4.
In the NE Explorer, select the EMS6 board and then choose Configuration > QoS
Management > Flow Management from the Function Tree.
b.
Click the Flow Configuration tab. After setting the parameters, click OK.
Paramet
er
Value Range
Description
Port
PORT1
PORT2
PORT2
Flow
Type
PORT
+VLAN
Flow
PORT
+VLAN
Flow
PORT
+VLAN
Flow
VLAN ID
300
100
200
Bound
CAR
Bound
CoS
14-140
1.
In the NE Explorer, select the EMS6 board and then choose Configuration > Ethernet
Interface Management > Ethernet Link Aggregation Management from the Function
Tree.
2.
3.
Click New. The Create Link Aggregation Group dialog box is displayed. After setting
the parameters, click OK. Then, click OK in the dialog box that is displayed.
Parameter
Value Range
Description
LAG No.
LAG Name
LAG_1
LAG Type
Manual
Issue 02 (2010-09-24)
Parameter
Value Range
Description
Load Sharing
Non-Sharing
Main Port
PORT3
Selected Slave
Ports
PORT4
----End
14.1.13.9 Configuring NE2 (Ethernet Services Accessed Through the IFH2 Board)
You can configure the attributes and CoS of the Ethernet ports of the IFH2 board based on the
parameters of the engineering plan so that Ethernet services can be accessed to the IFH2 board
normally, thus meeting the requirement for CoS scheduling.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
You must be logged in to the NE.
The IFH2 board must be added.
Procedure
Step 1 Configure the Ethernet ports of the IFH2 board.
1.
In the NE Explorer, select the IFH2 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select External
Port.
2.
Set the basic attributes of the ports. Click the Basic Attributes tab. After setting the
parameters, click Apply.
Parameter
Value Range
Description
Port
PORT1
Issue 02 (2010-09-24)
Enabled/
Disabled
Enabled
Working Mode
Auto-Negotiation
NonAutonegotiation
Flow Control
Mode
Disabled
14-141
Parameter
Value Range
Description
Autonegotiation
Flow Control
Mode
Enable
Symmetric Flow
Control
In the NE Explorer, select the IFH2 board and then choose Configuration > QoS
Management > Flow Management from the Function Tree.
2.
3.
Set CoS Parameter and CoS Priority. After setting the parameters, click Apply.
Parameter
Value Range
Description
CoS
Parameter
Priority 7 in
the VLAN
Tag
Priority 1 in
the VLAN
Tag
CoS Priority
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
You must be logged in to the NE.
Procedure
Step 1 Configure Ethernet external ports.
14-142
1.
In the NE Explorer, select the 5-EMS4 board and then choose Configuration > Ethernet
Interface Management > Ethernet Interface from the Function Tree. Select External
Port.
2.
Click the Basic Attributes tab. After setting the parameters, click Apply.
Issue 02 (2010-09-24)
Parameter
Value Range
Description
Port
PORT1
Enabled/
Disabled
Enabled
Working Mode
AutoNegotiation
The Ethernet equipment of users work in autonegotiation mode. Hence, the Working Mode of
the external ports should be set to AutoNegotiation.
Maximum
Frame Length
1522
PHY Loopback
Non-Loopback
3.
Click the Flow Control tab. After setting the parameters, click Apply.
Parameter
Value Range
Description
Port
PORT1
4.
NonAutonegotiatio
n Flow Control
Mode
Disabled
Autonegotiatio
n Flow Control
Mode
Disabled
Click the TAG Attributes tab. After setting the parameters, click Apply.
Parameter
Value Range
Description
Port
PORT1
TAG
Tag Aware
14-143
1.
In the NE Explorer, select the 5-EMS4 board and then choose Configuration > Ethernet
Service > Ethernet LAN Service from the Function Tree.
2.
Click New. The Create Ethernet LAN Service dialog box is displayed. Set the parameters
as follows:
3.
4.
Parameter
Value Range
Description
VB Name
VB1
VB Type
802.1d
Bridge Switch
Mode
SVL/Ingress
Filter Disable
(802.1d)
Click Configure Mount. The Service Mount Configuration dialog box is displayed. After
setting the parameters, click OK.
Parameter
Value Range
Description
selected
forwarding
ports
PORT1, IFUP1
Click OK.
2.
14-144
In the NE Explorer, select the 5-EMS4 and then choose Configuration > QoS
Management > Flow Configuration from the Function Tree.
b.
c.
Click New. The Create SDH Service dialog box is displayed. After setting the
parameters. Then, click OK.
Parameter
Value Range
Description
Flow Type
Port Flow
Port
PORT1
In the NE Explorer, select the 5-EMS4 and then choose Configuration > QoS
Management > Flow Management from the Function Tree.
b.
c.
Click New. The New CoS dialog box is displayed. After setting the parameters. Then,
click OK.
Issue 02 (2010-09-24)
3.
Parameter
Value Range
Description
CoS ID
CoS Type
VLAN Priority
CoS
Parameter
Priority 7 in the
VLAN Tag
Priority 1 in
the VLAN
Tag
CoS Priority
In the NE Explorer, select the 5-EMS4 board and then choose Configuration > QoS
Management > Flow Management from the Function Tree.
b.
Click the Flow Configuration tab. After setting the parameters, click Apply.
Parameter
Value Range
Description
Flow Type
Port Flow
Port
PORT1
Bound CAR
Bound CoS
----End
14-145
14.2.3 Availability
The QinQ technology is applicable to the Ethernet private line service and the Ethernet LAN
service.
14.2.4 Relation with Other Features
The QinQ technology is applied to the Ethernet line service and LAN service of the Ethernet
switching board.
14.2.5 Realization Principle
The attributes of QinQ packets are closely related to the port attributes and service type.
14.2.6 Planning Guide
Plan related parameters according to the specific application of the QinQ feature.
14.2.7 Configuration Guide
This topic describes the configuration flow and the corresponding configuration tasks of the
QinQ line service. An example is provided as additional information to help understand the
configuration.
With the application of the QinQ technology, the number of VLAN IDs can reach 4096 x
4096. This solves the problem that the number of VLAN IDs cannot meet the requirement.
Operators can plan VLAN resources independently and flexibly, thus simplifying network
configuration and maintenance.
The QinQ technology, providing a cheaper and simpler L2 VPN solution, replaces the
MPLS technology.
The QinQ technology enables the expansion of Ethernet services from local area networks
(LANs) to wide area networks (WANs).
IEEE 802.1q
IEEE 802.1ad
Issue 02 (2010-09-24)
Source
address
C-TAG
Length/Type
Data
FCS
(CRC-32)
TCI
TPID
16 bits
PCP
3 bits
CFI
VID
1 bit
12 bits
The TPID in the S-TAG that is supported by the Ethernet switching board has the same value as the TPID
in the C-TAG. The TPID value is 0x8100. The TPID value in the S-TAG can be modified. For details,
see 14.2.7.3 Modifying the Type Field of QinQ Frames.
Issue 02 (2010-09-24)
14-147
Figure 14-51 Format of the Ethernet frame with a C-TAG and an S-TAG
4 bytes
Destination
address
Source
address
S-TAG
C-TAG
Length/Type
Data
FCS
(CRC-32)
TCI
TPID
PCP
16 bits
3 bits
DEI
VID
1 bit
12 bits
NOTE
Certain vendors use the Ethernet frames each of which contains a C-TAG and an S-TAG but whose type field
is not set to 0x8100. To ensure that the OptiX RTN 600 can be interconnected with the equipment of the vendors,
the Ethernet switching board of Huawei supports manual setting of the type field.
Source
address
S-TAG
Length/Type
Data
FCS
(CRC-32)
TCI
TPID
16 bits
PCP
3 bits
DEI
VID
1 bit
12 bits
UNI Port
A UNI port verifies and processes the outer tag of an Ethernet frame according to the TAG
attributes of the port. UNI ports cannot be used in the case of QinQ services.
14-148
Issue 02 (2010-09-24)
C-Aware Port
A C-aware port is in an equivalent position as a UNI port in a network. A C-aware port considers
that an accessed packet does not contain an S-TAG. C-aware ports can be used in the case of
QinQ services.
NOTE
l C-TAG frames and untagged frames can normally enter and exit C-aware ports.
l When an S-TAG frame enters and exits a C-aware port, the port processes the S-TAG as a C-TAG.
l When a frame that contains an S-TAG and a C-TAG enters and exits a C-aware port, the port processes the
S-TAG as a C-TAG and does not process the inner C-TAG.
S-Aware Port
An S-aware port is in an equivalent position as a NNI port in a network. An S-aware port
considers that an accessed packet contains an S-TAG. S-aware ports can be used in the case of
QinQ services.
NOTE
l S-TAG frames or the frames that contain an S-TAG and a C-TAG can normally enter and exit S-aware ports.
l When a C-TAG frame enters and exits an S-aware port, the port processes the C-TAG frame as an S-TAG
frame.
l When an untagged frame enters and exits an S-aware port, the port discards the frame.
l When a frame that contains an S-TAG and a C-TAG enters and exits an S-aware port of an EMS6 board,
the port processes only the S-TAG and does not process the inner C-TAG.
Issue 02 (2010-09-24)
Type of Packet
(Type of Source
Port)
Operation Type
Direction
Description
Transparently
transmit C-VLAN
Unidirectional/
Bidirectional
Transparently
transmits packets
according to the CVLAN.
Transparently
transmit C-VLAN
Unidirectional/
Bidirectional
Transparently
transmits packets.
14-149
Operation
Type
Direction
Description
Add S-VLAN
Unidirectional
Bidirectional
In the case of the service from a Caware port to an S-aware port, the
port transmits the packets according
to the C-VLAN and adds an SVLAN tag to each packet.
In the case of the service from an Saware port to a C-aware port, the
port transmits the packets according
to the C-VLAN and strips the SVLAN tag from each packet.
Add S-VLAN
Unidirectional
Bidirectional
In the case of the service from a Caware port to an S-aware port, the
port adds an S-VLAN tag to each
packet.
In the case of the service from an Saware port to a C-aware port, the
port strips the S-VLAN tag from
each packet.
Strip S-VLAN
Unidirectional
NOTE
The priority of the S-VLAN tag added by the "Add S-VLAN" operation is 0 by default. The priority can be set.
14-150
Issue 02 (2010-09-24)
Operation
Type
Direction
Description
Transparently
transmit SVLAN
Unidirectional/
Bidirectional
Translate SVLAN
Unidirectional/
Bidirectional
The IEEE 802.1ad bridge does not check the contents of the VLAN tags in the data frames
that enter the bridge but performs Layer 2 switching according to the destination MAC
addresses of the data frames.
2.
The IEEE 802.1ad bridge checks the contents of the VLAN tags in the data frames that
enter the bridge and performs Layer 2 switching according to the destination MAC
addresses and S-VLAN IDs of the data frames.
IEEE 802.1ad
bridge
Bridge
Learning
Mode
Ingress Filter
SVL/Ingress Filter
Disable
SVL
Disabled
IVL/Ingress Filter
Enable
IVL
Enabled
The C-aware ports are used to add and strip the S-VLAN tags. The S-aware ports are used to
transparently transmit the S-VLAN tags.
The ports that are mounted to the IEEE 802.1ad bridge support the following operation types:
l
Issue 02 (2010-09-24)
14-151
Mount port
This topic describes the four operation types when Bridge Switch Mode of the IEEE 802.1ad
bridge is set to IVL/Ingress Filter Enabled.
Operation
Type
Direction
Description
Add S-VLAN
Base for Port
Ingress
Add S-VLAN
Base for Port
and C-VLAN
Egress
Ingress
Egress
14-152
Issue 02 (2010-09-24)
NOTE
a:
l The same C-aware port supports the mapping of different C-VLAN tags to the same S-VLAN tag. For
example, the data frames whose C-VLAN IDs are 1, 2, and 3 can be added with the same S-VLAN tag
whose ID is 100.
l The same C-aware port supports the mapping of different C-VLAN tags to different S-VLAN tags.
For example, the data frames whose C-VLAN IDs are 1, 2, and 3 can be added with the S-VLAN tags
whose IDs are 100, 200, and 300 respectively.
l The same C-aware port does not support the mapping of the same C-VLAN tag to different S-VLAN
tags at the same time. For example, the data frame whose C-VLAN ID is 1 cannot be added with the
S-VLAN tags whose IDs are 100, 200, and 300 at the same time.
Operation
Type
Direction
Description
Mount Port
Ingress
Egress
Ingress
Egress
Issue 02 (2010-09-24)
14-153
The data frame that enters the S-aware port must contain an S-VLAN tag. Otherwise, the port discards
the data frame.
14.2.3 Availability
The QinQ technology is applicable to the Ethernet private line service and the Ethernet LAN
service.
Table 14-41 Availability of the QinQ feature
Feature
Applicable Board
Applicable Equipment
EVPL (QinQ)
IDU 620
C-VLAN1
NE1
Service
network A
NE2
C-VLAN1
S-VLAN1 C-VLAN1
S-VLAN2 C-VLAN1
NE3
S-VLAN3 C-VLAN1
S-VLAN4 C-VLAN1
S-VLAN1 C-VLAN1
S-VLAN2 C-VLAN1
Service
network B
NE4
C-VLAN1
Frame of customer a
Frame of customer b
14-154
C-VLAN1
Issue 02 (2010-09-24)
On the network, the data frames from NE1 to NE4 are processed as follows:
1.
NE1 adds an S-TAG to each data frame from customer a and customer b that are connected
to NE1, and forwards the frames to NE2. NE1 adds an S-VLAN1 tag to each data frame
from customer a and an S-VLAN2 tag to each frame from customer b.
2.
Based on the S-VLAN tags, NE2 transparently transmits the data frames of customer a and
customer b to NE3 of service provider B.
3.
Because service provider B plans different S-VLAN tags for customer a and customer b,
NE3 translates the data frame that contains an S-VLAN1 tag into a data frame that contains
an S-VLAN3 tag, translates the data frame that contains an S-VLAN2 tag into a data frame
that contains an S-VLAN4 tag, and forwards the data frames to NE4.
4.
NE4 removes the S-VLAN3 tag and S-VLAN4 tag, and forwards the data frames to the
Ethernet ports of customer a and customer b.
The data frame process from NE4 to NE1 is reverse to the preceding process.
Node B1
Service C-VLAN
10
VoIP
20
HSI
PORT1
NE3
VCTRUNK1
PORT1
HSI
NE2
PORT2
VCTRUNK2
Node B2
Service C-VLAN
VoIP
30
HSI
40
PORT1
NE1
NE3:EMS6
PORT1
S-VLAN 100
PORT1
VoIP
Node B1
VCTRUNK1
S-VLAN 200
NE2
VCTRUNK2
PORT2
HSI
PORT1
Node B2
802.1ad bridge
PORT
Strip S-VLAN Label
C-VLAN(10/30) Data(VoIP)
S-VLAN(100)
C-VLAN(10/30) Data(VoIP)
C-VLAN(10/30) Data(VoIP)
Data(HSI)
S-VLAN(200)
C-VLAN(20/40)
C-VLAN(20/40)
C-VLAN(20/40)
Issue 02 (2010-09-24)
VCTRUNK
Add S-VLAN Label
Data(HSI)
Data(HSI)
14-155
As shown in Figure 14-54, the transmission network needs to carry the voice over IP (VoIP)
service and the high speed Internet (HSI) service. The VoIP service and the HSI service of Node
B1 and Node B2 that are connected to NE1 and NE2 respectively use different C-VLANs that
have been planned. To mark and schedule the VoIP service and the HSI service in a unified
manner on the aggregation node NE3, on the transmission network the planned S-VLAN tags
are added to the two types of services from the user side.
On the network, NE3 processes the data frames as follows:
1.
The VoIP service and the HSI service of Node B1 and Node B2 are transparently transmitted
to NE3 through NE1 and NE2 respectively.
2.
NE3 adds S-VLAN tag 100 to the VoIP service of Node B1, Node B2, and VoIP server
(with the C-VLANs 10 and 30).
3.
NE3 adds S-VLAN tag 200 to the HSI service of Node B1, Node B2, and HSI server (with
the C-VLANs 20 and 40).
4.
After these data frames carrying the S-VLAN tag enter the 802.1ad bridge, the Layer 2
switching is performed according to the Ethernet port specified in the S-VLAN filtering
table. When the data frames carrying the S-VLAN tag leave the bridge from the
corresponding port due to being forwarded, the S-VLAN tag is removed.
Prerequisite
You must have understood the specific applications of the QinQ feature.
Procedure
Step 1 Plan the network attributes of the ports according to the actual requirements.
Adhere to the following principles when planning the network attributes of the ports:
l If packets need to be forwarded according to C-VLAN tags or C-VLAN tags need to be
translated, select the line services between C-aware ports.
l If S-VLAN tags need to be added/stripped, select the line services between a C-aware port
and an S-aware port.
l If packets need to be forwarded according to S-VLAN tags or S-VLAN tags need to be
translated, select the line services between S-aware ports.
14-156
Issue 02 (2010-09-24)
Example
The following describes how to plan QinQ line services. The QinQ services illustrated in Figure
14-53 are provided as an example. The ports used in this example are shown in Figure 14-55.
Figure 14-55 Ports used by the QinQ line services
PORT1
PORT2
NE1
Service
network A
NE2
NE3
Service
network B
VCTRUNK1
VCTRUNK1
VCTRUNK2
VCTRUNK2
VCTRUNK1
VCTRUNK1
NE4
PORT1
PORT2
1.
2.
Issue 02 (2010-09-24)
14-157
In the case of NE3, select the bidirectional "Translate S-VLAN" operation because NE3
needs to translate S-VLAN tags according to S-VLAN tags and does not translate S-VLAN
tags based on ports.
3.
Prerequisite
You must be familiar with the specific application of the QinQ feature.
Procedure
Step 1 Plan the network attributes of the ports that are mounted to the IEEE 802.1ad bridge according
to the actual requirements.
Adhere to the following principles when planning the network attributes of the ports:
l If the packets that enter the port do not contain a VLAN tag or contain a C-VLAN tag, plan
the network attribute of the port as C-Aware.
l If the packets that enter the port contain an S-VLAN tag, plan the network attribute of the
port as S-Aware.
Step 2 Select a QinQ operation type according to the actual requirements.
Adhere to the following principles when planning the QinQ operation type:
l In the case of the C-aware port, select "Add S-VLAN Base for Port" or "Add S-VLAN Base
for Port and C-VLAN". For details, refer to Table 14-39.
l In the case of the S-aware port, select "Mount Port" or "Mount Port and Base for Port and
S-VLAN". For details, refer to Table 14-40.
Step 3 Allocate S-VLAN tags to customers or service types.
Adhere to the following principles when planning S-VLAN tags:
l The S-VLAN tag allocated to each customer or each service type must be unique.
l If a customer or service type requires multiple S-VLAN tags, allocate a section of consecutive
S-VLAN tags to the customer or service type. For example, allocate S-VLAN tags 100-109
to customer A or service type A (for example, VoIP services), and allocate S-VLAN tags
110-119 to customer B or service type B (for example, HSI services).
----End
Example
This topic considers the EVPLAN services (IEEE 802.1ad bridge) that are illustrated in Figure
14-54 as an example to describe the planning method.
14-158
Issue 02 (2010-09-24)
1.
2.
Accessed Service
PORT1
VoIP services
PORT2
HSI services
VCTRUNK1
In the case of NE1 and NE2, you need not plan QinQ operation types because NE1 and
NE2 transparently transmit the Ethernet services.
3.
14-159
14.2.7.5 Creating the EVPLAN Services That Are Based on the IEEE 802.1ad Bridge
To enable the Ethernet switching board to transmit the EVPLAN services that are based on the
IEEE 802.1ad bridge, you need to create the bridge, set the attributes of the bridge, select the
ports that are mounted to the bridge, and select the operation type.
Yes
No
4
Create QinQ line services
5
Create cross-connections
for Ethernet services
End
Table 14-42 Description of the configuration flow of the QinQ line service
14-160
Number
Description
For the configuration flow, see 14.2.7.3 Modifying the Type Field of QinQ
Frames.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
Number
Description
For the configuration flow, see 14.4.7.1 Configuring the Internal Port of
the Ethernet Board.
For the configuration flow, see 14.2.7.4 Creating QinQ Line Services.
Create the cross-connection from the paths that are bound to the VCTRUNK
to the corresponding timeslots on the line.
NOTE
To configure the QoS feature for the QinQ line service, see 14.7 Configuring QoS.
14.2.7.2 Configuration Flow (EVPLAN Services Based on the IEEE 802.1ad Bridge)
This topic describes the configuration flow of the EVPLAN service that is based on the 802.1ad
bridge.
Issue 02 (2010-09-24)
14-161
Figure 14-57 Configuration flow for the EVPLAN service that is based on the 802.1ad bridge
Start
Yes
No
1
Modify the type field of QinQ frames
2
Configure the external port of the Ethernet
board
3
Configure the internal port of the Ethernet
board
4
Create the EVPLAN services based on
IEEE 802.1ad bridge
5
Create the VLAN filter table
6
Modify the Hub/Spoke attribute of the port
mounted to a bridge
7
End
Table 14-43 Description of the configuration flow of the EVPLAN service that is based on the
802.1ad bridge
14-162
Number
Description
For the configuration process, see 14.2.7.3 Modifying the Type Field of
QinQ Frames.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
Number
Description
For the configuration process, see 14.4.7.1 Configuring the Internal Port
of the Ethernet Board.
For the configuration process, see 14.2.7.5 Creating the EVPLAN Services
That Are Based on the IEEE 802.1ad Bridge.
For the configuration process, see 14.1.4.5 Creating the VLAN Filter
Table.
For the configuration process, see 14.6.9 Modifying the Mounted Port of a
Bridge.
If the communication between ports needs to be isolated, you need to set the
Hub/Spoke attribute to "Spoke". In this case, Step 6 is required.
Create the cross-connection from the paths that are bound to the VCTRUNK
to the corresponding timeslots on the line.
NOTE
l To configure the Layer 2 switching feature for the EVPLAN services that are based on the IEEE 802.1ad
bridge, see 14.6 Configuring Layer 2 Switching.
l To configure the QoS feature for the EVPLAN services that are based on the IEEE 802.1ad bridge, see
14.7 Configuring QoS.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet board must be included in the slot layout.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Advanced Attributes
> QinQ Type Area Settings from the Function Tree.
Step 2 Modify the type field of QinQ frames.
Issue 02 (2010-09-24)
14-163
Parameters
Parameter
Value Range
Default Value
Description
81 00, 98 A8, 91 00
81 00
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > Ethernet
Service > Ethernet Line Service from the Function Tree.
Step 2 Select Display QinQ Shared Service.
Step 3 Click New.
The system displays the Create Ethernet Line Service dialog box.
Step 4 Set the attributes of the Ethernet line service.
14-164
Issue 02 (2010-09-24)
Step 5 Optional: Set the port attributes of the source port and sink port.
NOTE
The result of configuring the port attributes during the Ethernet line service configuration process is the same
as the result of directly configuring the Ethernet service port attributes.
Parameters
Parameter
Value Range
Default Value
Description
Service Type
EPL, EVPL(QinQ)
EPL
Issue 02 (2010-09-24)
14-165
Parameter
Value Range
Default Value
Description
Direction
Unidirectional,
Bidirectional
Bidirectional
Operation Type
Source Port
Transparently
transmit C-VLAN,
Translate C-VLAN,
Add S-VLAN,
Transparently
transmit S-VLAN,
Translate S-VLAN,
Strip S-VLAN (only
for unidirectional
services)
Add S-VLAN
A specific PORT or
VCTRUNK
PORT1
Source C-VLAN
(e.g. 1,3-6)
1 to 4095
14-166
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Source S-VLAN
1 to 4095
Sink Port
A specific PORT or
VCTRUNK
PORT1
1 to 4095
Sink S-VLAN
1 to 4095
Issue 02 (2010-09-24)
14-167
Parameter
Value Range
Default Value
Description
C-VLAN Priority
AUTO, Priority0Priority7
AUTO
S-VLAN Priority
AUTO, Priority0Priority7
AUTO
Port Enabled
Enabled, Disabled
14.2.7.5 Creating the EVPLAN Services That Are Based on the IEEE 802.1ad Bridge
To enable the Ethernet switching board to transmit the EVPLAN services that are based on the
IEEE 802.1ad bridge, you need to create the bridge, set the attributes of the bridge, select the
ports that are mounted to the bridge, and select the operation type.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > Ethernet
Service > Ethernet LAN Service from the Function Tree.
Step 2 Click New.
The Create Ethernet LAN Service dialog box is displayed.
14-168
Issue 02 (2010-09-24)
2.
3.
4.
Repeat Step 4.2 to Step 4.3 to add the other mount ports.
5.
Click OK.
Step 5 Optional: If any VCTRUNK is mounted to the VB, configure the VC paths that are bound to
the VCTRUNK.
1.
Click Configuration.
The Bound Path Configuration dialog box is displayed.
2.
3.
In Available Bound Paths, set Level and Direction of the bound paths.
4.
Select the required items in Available Resources and Available Timeslots and click
.
5.
Issue 02 (2010-09-24)
14-169
NOTE
The result of setting the port attributes during the configuration of the private network service is consistent
with the result of directly setting the attributes of the Ethernet service port.
6.
Click OK.
----End
Parameters
Parameter
Value Range
Default Value
Description
VB Name
VB Type
802.1q, 802.1d,
802.1ad
802.1q
IVL/Ingress Filter
Enable
IVL/Ingress Filter
Enable
SVL/Ingress Filter
Disable
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Operation Type
Mount Port
C-VLAN
1-4095
S-VLAN
1-4095
l When Operation Type is set to Add SVLAN Base for Port, this parameter
specifies that the data frames that enter
the IEEE 802.1ad bridge need to be
added with the S-VLAN tag.
l When Operation Type is set to Add SVLAN Base for Port and C-VLAN,
this parameter and C-VLAN specify the
mapping relation between the S-VLAN
tag to be added and the C-VLAN tag
carried by the data frame that enters the
IEEE 802.1ad bridge.
l When Operation Type is set to Mount
Port, this parameter is invalid.
l When Operation Type is set to Mount
Port and Base for Port and S-VLAN,
this parameter specifies the S-VLAN tag
to be carried by the data frames that enter
the IEEE 802.1ad bridge.
Configurable Ports
Issue 02 (2010-09-24)
Mount each
VCTRUNK of the
port.
14-171
Parameter
Value Range
Default Value
Description
Available Bound
Paths
Issue 02 (2010-09-24)
Auto-Negotiation Function
The auto-negotiation function allows the network equipment to send information of its supported
working mode to the opposite end on the network and to receive the corresponding information
that the opposite end may transfer.
The external port of the Ethernet service board and the data communication equipment at the
opposite end must work in the same duplex mode and operate at the same rate. If the working
modes at the two ends do not match, the transmission efficiency is reduced and the data may
even be lost.
Jumbo Frames
An Ethernet frame requires that the maximum size of the payload must not exceed 1500 bytes.
This requirement severely affects the transmission efficiency of certain high-speed data services.
To improve the transmission efficiency, the Jumbo frame technology is developed. A Jumbo
frame adopts the structure of an ordinary Ethernet frame but does not have a requirement for the
maximum size of the payload. To differentiate a Jumbo frame from an ordinary Ethernet frame,
we define the type field of a Jumbo frame as "0x8870".
14-173
The auto-negotiation function allows the network equipment to send information of its supported
working mode to the opposite end on the network and to receive the corresponding information
that the opposite end may transfer.
14.3.2.2 Jumbo Frames
The maximum length of the payload of an Ethernet frame must not exceed 1500 bytes. This
requirement greatly affects the transmission efficiency of certain high-speed data services. To
improve the transmission efficiency, the Jumbo frame technology emerged.
14.3.2.3 Flow Control Function
When the equipment fails to handle the flow received at the port due to poor data processing/
transferring capability, congestion occurs on the line. To reduce the number of discarded packets
caused by buffer overflow, proper flow control measures must be taken.
The following sections describe the basic concepts related to the auto-negotiation function, including all
the working modes. The working mode supported by each Ethernet port of the equipment may be different.
For details, refer to 14.3.7.1 Configuring External Ethernet Ports.
14-174
Auto-Negotiation Result
Auto-negotiation
100M full-duplex
10M half-duplex
10M half-duplex
10M full-duplex
10M half-duplex
100M half-duplex
100M half-duplex
100M full-duplex
100M half-duplex
Issue 02 (2010-09-24)
NOTE
From Table 14-44, it is evident that when the working mode of the opposite equipment is 10M full-duplex or
100M full-duplex, the auto-negotiation result cannot realize the matching between the working modes of both
sides. As a result, certain packets are lost. Hence, when the working mode of the opposite equipment is 10M
full-duplex or 100M full-duplex, set the working mode of the local equipment to 10M full-duplex or 100M fullduplex.
When the FE electrical ports on both sides are working in the auto-negotiation mode, the
equipment on both sides can negotiate the flow control function through the auto-negotiation
function.
Table 14-45 Auto-negotiation rules of GE electrical ports (when the local port adopts the autonegotiation mode)
Working Mode of the Opposite Port
Auto-Negotiation Result
1000M full-duplex
100M full-duplex
10M half-duplex
10M half-duplex
10M full-duplex
10M half-duplex
100M half-duplex
100M half-duplex
100M full-duplex
100M half-duplex
1000M full-duplex
1000M full-duplex
From Table 14-45, it is evident that when the working mode of the opposite equipment is 10M
full-duplex or 100M full-duplex, the auto-negotiation result cannot realize the matching between
the working modes of both sides. As a result, certain packets are lost. Hence, when the working
mode of the opposite equipment is 10M full-duplex or 100M full-duplex, set the working mode
of the local equipment to 10M full-duplex or 100M full-duplex.
When the GE electrical ports on both sides are working in the auto-negotiation mode, the
equipment on both sides can negotiate the flow control function through the auto-negotiation
function.
Issue 02 (2010-09-24)
14-175
If the GE optical port of the equipment on one side works in the 1000M full-duplex mode and the GE optical
port of the equipment on the other side works in the auto-negotiation mode, a link error occurs due to an autonegotiation failure, and as a result, a LINK_ERR alarm is generated.
The Ethernet port of the EFT4 board checks the type field in an Ethernet frame to determine
whether the Ethernet frame is a Jumbo frame. If the Ethernet frame is a Jumbo frame, the
maximum frame length is not restricted.
The Ethernet port of the EMS6 board checks whether an Ethernet frame whose length
exceeds 1536 bytes is a Jumbo frame. All the frames are restricted by the maximum frame
length.
VCTRUNKs 1-4 of the EFT4 board and VCTRUNKs 5-8 of the EMS6 board check whether
an Ethernet frame is a Jumbo frame. If an Ethernet frame is not a Jumbo frame but its length
exceeds the maximum frame length, the board discards the frame. VCTRUNKs 1-4 of the
EMS6 board do not check Jumbo frames. The EMS6 board discards any frame whose length
exceeds the maximum frame length.
The maximum frame length (namely, the MTU), is a parameter of the Ethernet port. In the
case of common Ethernet frames, the Ethernet service board discards the frame whose
length exceeds the value of this parameter.
The following sections describe the basic concepts related to the flow control function, including all the
flow control modes. The flow control mode supported by each Ethernet port of the equipment may be
different. For details, refer to 14.3.7.1 Configuring External Ethernet Ports.
14-176
Issue 02 (2010-09-24)
Symmetric PAUSE
The port can send and process PAUSE frames.
Disabled
The port does not send or process PAUSE frames.
Send only
In case of congestion, the port can send PAUSE frames but cannot process received PAUSE
frames.
Receive only
In case of congestion, the port can process received PAUSE frames but cannot send PAUSE
frames.
Disabled
The port does not send or process PAUSE frames.
14.3.3 Availability
The Ethernet port feature requires the support of the applicable equipment and boards.
Table 14-46 Availability of the Ethernet port feature
Issue 02 (2010-09-24)
Feature
Applicable Board
Applicable Equipment
Auto-negotiation
IDU 610/620
IDU 620
14-177
Feature
Jumbo frame
Flow control
Applicable Board
Applicable Equipment
IDU 620
IDU 610/620
IDU 620
IDU 610/620
IDU 620
IDU 620
The following describes the realization principle of the auto-negotiation function. The auto-negotiation function
of FE electrical ports is provided as an example.
The fast link pulse (FLP) is called the 10BASE-T link integrity test pulse sequence. Each device
must be capable of issuing FLP bursts at power up, on command from management, or due to
user interaction. The FLP burst consists of a series of link integrity test pulses that form an
alternating clock/data sequence. Extraction of the data bits from the FLP burst yields a link code
word that identifies the working modes supported by the remote device, as well as certain
information used for the handshake mechanism of the auto-negotiation function.
To maintain interoperability with existing 10BASE-T devices, the auto-negotiation function also
supports the reception of 10BASE-T compliant link integrity test pulses. 10BASE-T link pulse
activity is referred to as the normal link pulse (NLP) sequence. A device that fails to respond to
the FLP burst sequence by returning only the NLP sequence is treated as a 10BASE-T compatible
device.
The first pulse in an FLP burst is defined as a clock pulse. Clock pulses within an FLP burst are
spaced at 125 us. Data pulses occur in the middle of two adjacent clock pulses. The presence of
14-178
Issue 02 (2010-09-24)
a positive pulse represents a logic one and the absence of a pulse represents a logic zero. An
FLP burst consists of 17 clock pulses and 16 data pulses (if all data bits are 1). The NLP waveform
is simpler than the FLP waveform. The NLP sends a positive pulse every 16 ms when no data
frame needs to be transmitted.
Figure 14-58 Waveform of a single FLP
T3
Clock pulses
T1
T2
1
D
0
1
D
1
T1: 100 ns
0
D
2
1
D
3
T2: 62.5 us
T3: 125 us
FLP bursts
NLPs
T4: 2 ms
T5: 16 ms
When congestion occurs in the receive queue of an Ethernet port (the data in the receive
buffer exceeding a certain threshold) and the port is capable of sending PAUSE frames,
the port sends a PAUSE frame to the opposite end. The pause-time value in the frame is N
(0<N65535).
2.
After receiving the PAUSE frame, and being capable of processing PAUSE frames, the
Ethernet port at the opposite end stops sending data within a specified period of time N
(whose unit is the time needed for sending 521 bits).
Issue 02 (2010-09-24)
14-179
3.
If the congestion at the receive port is cleared (the data in the receive buffer is below a
certain threshold) but the pause-time does not end, the port sends a PAUSE frame whose
pause-time is 0 to notify the opposite end to start sending data.
01-80-C2-00-00-01
6 octets
XX-XX-XX-XX-XX-XX
6 octets
Type/Length
88-08
2 octets
00-01
2 octets
XX-XX
2 octets
Source address
Reserved
Procedure
Step 1 Plan the working mode of the Ethernet port.
Ensure that the working modes of the Ethernet ports at the two ends should be the same.
Step 2 Plan the parameter MTU.
In the case of the EFT4 board, adhere to the following principles when planning the MTU of
the Ethernet port:
l The MTU must be greater than the length of the maximum frame among all the L2 data
frames that are to be transmitted.
l The value of the MTU ranges from 1518 to 1535 bytes.
l The default value of the MTU is 1522 bytes, which is the sum of the length of the maximum
basic frame and the length of the VLAN label.
l The MTU is invalid for the Jumbo frame.
14-180
Issue 02 (2010-09-24)
In the case of the EMS6 board, adhere to the following principles when planning the MTU of
the Ethernet port:
l The MTU should be greater than the length of the maximum frame among all L2 data frames
to be transmitted.
l The value of the MTU ranges from 1518 to 9600 bytes.
l The default value of the MTU is 1522 bytes, which is the sum of the length of the maximum
basic frame and the length of the VLAN label.
l The MTU parameter restricts the maximum length of a Jumbo frame.
Step 3 Plan the flow control parameters for the Ethernet port.
Adhere to the following principles when planning the flow control parameters for the Ethernet
port:
l The flow control parameters are valid only for the full-duplex Ethernet.
l The flow control parameters are valid only for the Ethernet transparent transmission service.
l When the Ethernet port works in the auto-negotiation mode, use the auto-negotiation flow
control parameter.
l When the Ethernet port works in a fixed working mode, use the non-auto-negotiation flow
control parameter.
l The flow control parameters at both sides must match each other. The flow control function
must not be enabled at one side and disabled at the other side.
l It is recommended that you enable the flow control function for the Ethernet board and for
the opposite equipment on the network with flow bursts.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet board must be included in the NE Panel.
Issue 02 (2010-09-24)
14-181
Precautions
l
The IDU 610 supports the Ethernet board EFT4. The IDU 620 supports the Ethernet boards
EFT4 and EMS6.
Ethernet ports FE1-FE4 of an EFT4 board correspond to PORT1-PORT4 respectively.
The EFT4 board does not support the setting of TAG attributes, network attributes, and
advanced attributes.
Ethernet ports FE1-FE4 of an EMS6 board correspond to PORT1-PORT4 respectively.
Ports GE1 and GE2 of an EMS6 board correspond to PORT5 and PORT6 respectively.
The IDU 605 IF/2F supports the Ethernet board EMS4 (a logical board).
Ethernet ports FE1-FE3 of an EMS4 board (a logical board) correspond to PORT1PORT3 respectively. Port FE4/GE1 of an EMS4 board corresponds to PORT4.
Ethernet ports FE1-FE2 of an EM4T board correspond to PORT1-PORT2 respectively.
Ports GE1 and GE2 of an EM4T board corresponds to PORT3 and PORT4 respectively.
The following procedures describe how to configure the external port of an EMS6 board.
The EFT4 board does not support the configuration of the TAG attributes, network
attributes, and advanced attributes.
The Hybrid IF board (IFH2) provides the GE port for accessing Ethernet services and it
supports certain Ethernet service access functions. The procedure for configuring the
Ethernet port of the IFH2 board is similar to the procedure for configuring the external
Ethernet port. The IFH2 board, however, supports the configuration of only the basic
attributes and flow control function.
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet Interface
Management > Ethernet Interface from the Function Tree. Select External Port.
NOTE
If you need to configure the attributes of the Ethernet port on the IFH2 board, select the IFH2 board in the
NE Explorer.
2.
3.
Click Apply.
14-182
1.
2.
Issue 02 (2010-09-24)
3.
Click Apply.
2.
3.
Click Apply.
2.
3.
Click Apply.
2.
3.
Click Apply.
----End
Issue 02 (2010-09-24)
14-183
Parameters
Parameter
Value Range
Default Value
Description
Enabled/Disabled
Enabled, Disabled
Disabled
Working Mode
10M Full-Duplex,
100M Full-Duplex,
Auto-Negotiation
(EFT4)
10M Half-Duplex,
10M Full-Duplex,
100M Half-Duplex,
100M Full-Duplex,
1000M FullDuplex, AutoNegotiation (EMS6)
Auto-Negotiation,
10M Full-Duplex,
100M Full-Duplex,
1000M Full-Duplex
(IFH2)
10M Half-Duplex,
10M Full-Duplex,
100M Half-Duplex,
100M Full-Duplex,
Auto-Negotiation (a
logical board EMS4,
PORT1-PORT3)
Auto-Negotiation
10M Half-Duplex,
10M Full-Duplex,
100M Half-Duplex,
100M Full-Duplex,
1000M FullDuplex, AutoNegotiation (a
logical board EMS4,
PORT4)
14-184
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Maximum Frame
Length
1518-1535 (EFT4)
1522
1518-9600 (EMS6)
1522/1632 (a logical
board EMS4)
MAC Loopback
Non-Loopback,
Inloop
Non-Loopback
PHY Loopback
Non-Loopback,
Inloop
Non-Loopback
Issue 02 (2010-09-24)
14-185
Parameter
Value Range
Default Value
Description
NonAutonegotiation
Flow Control Mode
Disabled, Enable
Symmetric Flow
Control, Send Only,
Receive Only (EFT4
and EMS6)
Disabled
Disabled, Enable
Symmetric Flow
Control (IFH2)
Disabled, Enable (a
logical board
EMS4)
14-186
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Autonegotiation
Flow Control Mode
Disabled, Enable
Symmetric/
Dissymmetric Flow
Control, Enable
Symmetric Flow
Control, Enable
Dissymmetric Flow
Control (EFT4 and
EMS6)
Disabled
Disabled, Enable
Symmetric Flow
Control (IFH2)
Disabled, Enable
Symmetric Flow
Control (a logical
board EMS4)
Entry Detection
Enabled, Disabled
Enabled
TAG
Tag Aware
Issue 02 (2010-09-24)
14-187
Parameter
Value Range
Default Value
Description
Default VLAN ID
1 to 4095
VLAN Priority
0 to 7
Port Attributes
UNI
Enabling Broadcast
Packet Suppression
Enabled, Disabled
Disabled
Broadcast Packet
Suppression
Threshold
10% to 100%
30%
14-188
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Loop Detection
Disabled, Enabled
Disabled
Disabled, Enabled
Enabled
Ingress
Egress
Type of Data
Frame
How to Process
Tag aware
Access
Hybrida
Tagged frame
Untagged frame
Tagged frame
l If the VLAN ID
in the frame is
Default VLAN
ID, the port
strips the VLAN
tag from the
frame and then
transmits the
frame.
l If the VLAN ID
in the frame is
not Default
VLAN ID, the
port directly
transmits the
frame.
Issue 02 (2010-09-24)
14-189
a: When the TAG attribute of a port on the EMS4 board (a logical board) that is supported by the IDU 605
1F/2F is set to Hybrid, the packet that is forwarded by this port remains the same as the packet that enters
the bridge.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet board must be included in the slot layout.
Precautions
The EMS6 board supports the modification of the type field of Jumbo frames.
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet Interface
Management > Jumbo Frame from the Function Tree.
Step 2 Modify the type field of Jumbo frames.
Parameters
Parameter
Value Range
Default Value
Description
Jumbo Frame
00 00 to FF FF
88 70
14-190
Issue 02 (2010-09-24)
VCTRUNK port
Interface
module
Service
processing
module
Encapsulation/
Mapping
module
Backplane
Interface
conversion
module
Crossconnect unit
Crossconnect unit
Ethernet board
Issue 02 (2010-09-24)
14-191
The features relevant to the external port of the Ethernet service board include the encapsulation
and mapping protocol, virtual concatenation, and LCAS.
Virtual Concatenation
The rate of the Ethernet service does not adapt to the rate of the standard VC container. Hence,
if you directly map the Ethernet service data into a standard VC container, the transmission
bandwidth is wasted to a great extent. To solve the problem, use the virtual concatenation
technology to concatenate many standard VC containers to a large VC container that adapts to
the rate of the Ethernet service.
LCAS
The LCAS is applied on the basis of virtual concatenation and can improve the performance of
virtual concatenation. The LCAS can dynamically adjust the number of virtual containers for
mapping required services to meet the bandwidth requirements of the application. As a result,
the bandwidth utilization is improved.
Issue 02 (2010-09-24)
HDLC
The HDLC is a general data link control procedure. When using the HDLC protocol, the system
encapsulates data services into HDLC-like frames as information bits and maps the frames to
SDH VC containers.
LAPS
The LAPS is also a data link control procedure. It is developed based the HDLC. The LAPS
complies with ITU-T X.86.
GFP
The GFP is the most widely applied general encapsulation and mapping protocol currently. It
provides a general mechanism to adapt higher-layer client signal flows into the transport network
and can map the variable-length payload into the byte-synchronized transport path. Client signals
can be protocol data units (PDU-oriented, such as IP/PPP and Ethernet), block-code data (blockcode-oriented, such as FC and ESCON), or common bit streams. The GPF protocol complies
with ITU-T G.7041.
The GFP defines the following two modes to adapt to client signals:
l
All Ethernet boards of the OptiX RTN 600 use the GFP-F mode to perform encapsulation and
mapping.
14-193
In the case of the virtual concatenation, each VC container may be transported in different paths
and there may be a transport delay difference between VC containers. Hence, there are
difficulties in restoring the client signal. Virtual concatenation only requires that the path
termination equipment provides the concatenation function and it can allocate bandwidth
flexibly. Hence, virtual concatenation is a widely applied concatenation technology.
Virtual concatenation is available in two types, virtual concatenation in a higher order path and
virtual concatenation in a lower order path. A higher order virtual concatenation VC-4-Xv
provides a payload area of X Container-4 (VC-4). The payload is mapped individually into X
independent VC-4s. Each VC-4 has its own POH. Similarly, a lower order virtual concatenation
VC-12-Xv provides a payload area of X Container-12 (VC-12). The payload is mapped
individually into X independent VC-12s. Each VC-12 has its own POH, as does the virtual
concatenation of VC-3s.
Physical channels formed by virtual concatenation are called VCTRUNKs and are also called
internal ports of the Ethernet board. The Ethernet board does not support VC-4-Xv.
14.4.2.3 LCAS
The link capacity adjustment scheme (LCAS) is applied on the basis of virtual concatenation
and can improve the performance of virtual concatenation. The LCAS can dynamically adjust
the number of virtual containers for mapping the required services, to meet the bandwidth
requirements of the application. As a result, the bandwidth utilization ratio is improved.
The LCAS technology has the following advantages:
l
The LCAS can dynamically adjust (add, delete, or modify) the service bandwidth without
affecting the availability of the existing service.
If there are failed physical channels in virtual concatenation, the LCAS shields these
physical channels. Other physical channels in virtual concatenation can transfer services.
Hence, this prevents a situation where the failure of a single physical channel causes
interruption of services. After the failed physical channels are restored, they can transfer
services.
14.4.3 Availability
The Ethernet encapsulation and mapping feature requires the support of the applicable equipment
and boards.
Table 14-48 Availability of the Ethernet encapsulation and mapping feature
Feature
Applicable Board
Applicable Equipment
EFT4
IDU 610/620
EMS6
IDU 620
Virtual concatenation
EFT4
IDU 610/620
EMS6
IDU 620
EFT4
IDU 610/620
EMS6
IDU 620
LCAS
EFP6
14-194
Issue 02 (2010-09-24)
Issue 02 (2010-09-24)
14-195
Core header
Payload area
4-65535
n
1
16-bit payload
length indicator
c-HEC
(CRC-16)
Core header
Payload
headers
(4-64 bytes)
Payload area
Client
payload
information
field
Optional
payload FCS
(CRC-32)
A GFP frame consists of a core header and a payload area. The Idle frame does not have the
payload area.
The GFP core header includes the following fields:
14-196
Issue 02 (2010-09-24)
The GFP payload area includes the payload header, client payload information field, and payload
frame check sequence. The payload header consists of the type, type HEC (tHEC), extension
header field, and extension HEC (eHEC). The type field includes the following:
l
PFI
EXI
UPI
7
1
6
2
5
3
4
4
3
5
2
6
1
7
0 Bit number
8
Octet transmission order
The tHEC field protects the integrity of the type field by enabling both single-bit error correction
and multi-bit error detection.
The extension header field and eHEC field are used to support special data link header
technologies and are seldom used in actual situations.
14-197
management frames are used to transport information associated with the management of the
client signal or GFP connection. The type field of the client data frames uses the following
values:
l
PTI = 100
Usage
0000 0000
Reserved
1111 1111
0000 0001
0000 0010
0000 0011
through
1111 11110
The Ethernet MAC octets from the destination address through the frame check sequence,
inclusive, are placed in the GFP payload information field. Octet-alignment is maintained
and bit identification within octets is maintained.
Ethernet MAC frame
Octets
7
1
6
6
2
Preamble
Start of frame delimiter
Destination Address (DA)
Source Address (SA)
Length/Type
MAC client data
Pad
Frame Check Sequence (FCS)
4
1
14-198
GFP frame
Octets
2
2
2
2
0-60
PLI
cHEC
Type
tHEC
GFP extension header
GFP
payload
Bits
Bits
2.
Calculate other fields of the GFP client data frame over the content of the payload.
3.
Scramble the core header and the payload area to maintain DC balance of the transported
data.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
4.
Map GFP client data frames into virtual containers and insert the Idle frame to realize the
rate adaptation between the variable-length PDUs and the defined virtual containers.
Check for a correct cHEC, byte by byte in the payload of the virtual container. Once a
correct cHEC is detected, a GFP frame is found.
2.
Check for subsequent GFP frames frame by frame according to the PLI in the GFP frame
and discard Idle frames.
3.
Descramble the payload area in the found GFP frame and extract the Ethernet MAC octets
from the destination address through the frame check sequence, inclusive.
Issue 02 (2010-09-24)
14-199
SQ = X-1
= 15
SQ = 0
= 255
MFI-1 = 15
MFI-2 = 255 X-1
=0
SQ = 0
=0
MFI-1 = 0
MFI-2 = 0
POH
POH
POH
POH
SQ = X-1
= 15
SQ = 0
MFI-1 = 15 = 0
MFI-2 = 0
X-1
SQ = 0
=0
MFI-1 = 0
= 15
MFI-2 = 1
Multiframe (MF)
POH
POH
C-3-Xv/C-4-Xv
SQ = X-1
=0
SQ = 0
=0
MFI-1 = 0
X-1
MFI-2 = 0
=1
SQ = 0
=0
MFI-1 = 1
MFI-2 = 0
H
C-3-X/C-4-X
With the MFI and SQ, the sink can correctly restore the position of each frame in the C-n-Xv to
avoid the frame alignment problem due to the different propagation delays of the frames.
VC-12-Xv
The virtual container that is formed by a VC-12-Xv can be mapped into X individual VC-12s
which form the VC-12-Xv. Each VC-12 has its own POH. The POH has the same specifications
as the ordinary VC-12 POH. Bit 2 of the K4 byte in the POH is used for the virtual concatenationspecific frame count and sequence indicator.
Bit 2s of the K4 bytes in every 32 multiframes (one multiframe comprising four VC-12s) are
extracted to form a 32-bit character string to express the frame count and sequence indicator.
Bits 1-5 of the string express the frame count, whose value range is between 0 and 31. The
structure formed by 32 multiframes has 128 frames. Hence, the resulting overall multiframe is
1096 frames (= 512 ms) long. Bits 6-11 of the string express the sequence indicator. The frame
count/sequence indicator in the VC-12-Xv has the same usage as the multiframe indicator/
sequence indicator in the VC-4-Xv/VC-3-Xv.
14.4.5.3 LCAS
The LCAS realizes the capacity adjustment of the virtual container by exchanging the control
information between both the source and the sink side.
Control Information
Synchronization of changes in the capacity of the transmitter (So) and the receiver (Sk) is
achieved by a control packet. Each control packet describes the state of the link during the next
14-200
Issue 02 (2010-09-24)
control packet. Changes are sent in advance so that the receiver can switch to the new
configuration as soon as it arrives.
The control packet is transported in byte H4 (higher order path) or bit 2 of byte K4 (lower order
path).
The control packet includes the following:
l
SQ
SQ is used to indicate the position of a frame in the C-n-Xv. For the usage, see 14.4.5.2
Virtual Concatenation.
GID
The GID is used for identification of the VCG. The GID bit of all members of the same
VCG has the same value. The VCG refers to a group of co-located member trail termination
functions that are connected to the same virtual concatenation link. The members of a VCG
are the virtual containers that form the VCG. The VCG is equivalent to the generally spoken
VCTRUNK.
Command
Remarks
FIXED
ADD
NORM
Normal transmission
EOS
IDLE
DNU
CRC
The CRC check is performed on every control packet after it has been received, and the
contents rejected if the test fails.
Issue 02 (2010-09-24)
14-201
The forward control packets from the source to the sink include the MFI, SQ, GID, CTRL, and
CRC. The backward control packets from the sink to the source include the MST, RS-Ack, and
CRC.
Source (new)
Sink (new)
Source (EOS)
Ctrl=ADD
MST=OK
Ctrl=EOS
RS-Ack
Ctrl=NORM
When a member is added to a VCTRUNK on the NMS, the LCAS capacity adjustment process
is as follows:
14-202
1.
The LCAS source assigns a sequence number (one larger than the currently highest
sequence number) to the new member and sends a forward control packet with its CTRL
word being ADD to the sink.
2.
The LCAS sink performs continuity check for the new member. If the link of the new
member is normal, the sink sends a backward control packet in which MST = OK to the
source.
3.
The LCAS source sends a forward control packet with its CTRL code being EOS to the
sink for the new member, indicating that the SQ of the new member is the currently highest
number in the VCG.
4.
The LCAS sink sends the RS-Ack to the source to acknowledge the change of the SQ.
5.
The LCAS source sends a forward control packet with its CTRL code being NORM to the
sink for the member whose original state is EOS, indicating that the member is normally
transmitted but is not the one with the highest SQ.
6.
Both the source and the sink use the new member to transport the payload.
Issue 02 (2010-09-24)
Source(removed)
Sink(removed)
Sink(SQ>removed
member's SQ)
Ctrl=IDLE
MST=FAIL
RS-Ack
Ctrl=EOS/NORM
RS-Ack
When a member is deleted from a VCTRUNK on the NMS, the LCAS capacity adjustment
process is as follows:
1.
The LCAS source sends a forward control packet with its CTRL code being IDLE to the
sink for the deleted member.
2.
The LCAS sink sets the status of the member to FAIL and sends a backward control packet
in which MST = FAIL to the source and also sends the RS-Ack to acknowledge the change
of the SQ.
3.
The LCAS source reallocates SQs for all the members whose SQ is higher than that of the
deleted member (SQ decremented successively by 1). It also sends a forward control packet
with its CTRL code being EOS or NORM to the sink to indicate the change of the SQ.
4.
The LCAS sink sends the RS-Ack to the source to acknowledge the change of the SQ.
5.
Both the source and the sink do not use the deleted member to transport the payload.
Figure 14-67 Capacity adjustment process (one member link restored after a failure)
Source (link error)
Sink
MST=FAIL
Ctrl=DNU
...
MST=OK
Ctrl=NORM
When a member link of a VCTRUNK is restored after a failure, the process of adjusting the
LCAS capacity is as follows:
1.
On detecting that a member link is faulty, the LCAS sink sends a backward control packet
in which MST = FAIL to the source.
2.
The LCAS source sends a forward control packet with its CTRL code being DNU to the
sink for the member, indicating that the member is temporarily unavailable.
3.
If the original status of the member is EOS, the LCAS source sends a forward control packet
with its CTRL word being EOS to the sink for the member whose SQ is one lower than
EOS.
4.
Both the source and the sink do not use the faulty link member to transport the payload.
Issue 02 (2010-09-24)
14-203
5.
On detecting that the member link is restored, the LCAS sink sends a backward control
packet in which MST = OK to the source.
6.
The LCAS source sends a forward control packet with its CTRL code being NORM or
EOS to the sink for the member, indicating that the member is restored and available.
7.
If the original status of the member is EOS, the LCAS source sends a forward control packet
with its CTRL word being NORM to the sink for the member whose status is set to EOS.
8.
Both the source and the sink use the restored member to transport the payload.
NOTE
l The LCAS source can adopt the Huawei mode or the standard mode to send the two control packets MST
and Rs-Ack. In the Huawei mode, the Rs-Ack is sent before the MST. In the standard mode, the MST is
sent before the Rs-Ack. You can set the mode on the NMS.
l The LCAS sink uses the trail signal fail (TSF) or the loss of multiframe (LOM) as a required condition to
determine whether a link is faulty. It uses the trail signal degraded (TSD) as an optional condition. In the
case of the VC-12, the TSD is the BIP_SD. In the case of the VC-3, the TSD is the B3_SD_VC3. You can
enable or disable the TSD on the NMS.
l When a member link is faulty, the LCAS performs a protection switching after a delay of time to prevent
the situation where an NE simultaneously performs a protection switching such as SNCP and deletes the
member. You can set the delay time on the NMS.
l A VCG uses a member to transport payload some time after the member link is restored. You can set the
WTR time on the NMS.
Procedure
Step 1 Plan the Ethernet encapsulation and mapping protocol.
Adhere to the following principles when planning the encapsulation and mapping of the Ethernet
port:
l Plan the same encapsulation and mapping protocol for both sides. It is recommended that
you adopt the GFP protocol.
l The parameters of the encapsulation and mapping protocol at both sides should be consistent.
It is recommended that you adopt the default parameters of the protocol.
Step 2 Plan VCTRUNKs.
Adhere to the following principles when planning VCTRUNKs:
l The capacity of VCTRUNKs should be determined by the actual bandwidth of the service
needs.
l Bind only the paths in a VC-4 if possible. If the paths of several VC-4s need to be bound,
the VC-4s that have the same transmission path take priority.
l As each VC-4 of the Ethernet board can bind only VC-3 or VC-12, give priority to the VC-4s
whose paths are already bound with the VC-12 or VC-3.
l As the VC-4-1 of the EFT4 board and EMS6 board can bind only VC-3 paths whereas the
VC-4-2 can bind both VC-12 and VC-3 paths, give priority to the paths in the VC-4-1 if
VC-3 paths are to be bound.
14-204
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet board must be included in the slot layout.
Precautions
The IDU 610 supports the Ethernet board EFT4. The IDU 620 supports the Ethernet boards
EFT4 and EMS6.
l
The EFT4 board supports VCTRUNKs 1-4, which are bound with PORTs 1-4 respectively.
The EFT4 board does not support the setting of TAG attributes and network attributes.
The EMS6 board supports VCTRUNKs 1-8. VCTRUNKs 1-8 determine the services to be
transmitted depending on information of the created Ethernet services.
The following procedures describe how to configure the internal port of an EMS6 board. The
EFT4 board does not support the configuration of the TAG attributes and network attributes.
Issue 02 (2010-09-24)
14-205
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Configuration > Ethernet Interface
Management > Ethernet Interface from the Function Tree. Choose Internal Port.
Step 2 Set the encapsulation and mapping protocol used by the port.
1.
2.
3.
Click Apply.
2.
Click Configuration.
The system displays the Bound Path Configuration dialog box.
3.
4.
In Available Bound Paths, set Level and Direction of the bound paths.
5.
Select required items in Available Resources and Available Timeslots and click
6.
7.
Click OK. Then, click Yes in the dialog box that is displayed.
14-206
1.
2.
Issue 02 (2010-09-24)
3.
Click Apply.
2.
3.
Click Apply.
2.
3.
Click Apply.
----End
Parameters
Parameter
Value Range
Default Value
Description
Mapping Protocol
GFP
Scramble
Unscrambled,
Scrambling Mode
[X43+1],
Scrambling Mode
[X48+1]
Scrambling Mode
[X43+1]
Issue 02 (2010-09-24)
14-207
Parameter
Value Range
Default Value
Description
Yes, No
Yes
FCS32, FCS16, No
FCS32
l Big endian
(GFP)
l Little endian
(LAPS or
HDLC)
Extension Header
Option
No, Yes
No
Configurable Ports
14-208
VCTRUNKs
VCTRUNK 1
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Available Bound
Paths
Enabling LCAS
Enabled, Disabled
Disabled
Issue 02 (2010-09-24)
14-209
Parameter
Value Range
Default Value
Description
LCAS Mode
Huawei Mode,
Standard Mode
Huawei Mode
2000
WTR Time(s)
0 to 720
300
TSD
Enabled, Disabled
Disabled
14-210
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Entry Detection
Enabled, Disabled
Enabled
TAG
Tag Aware
Default VLAN ID
1 to 4095
VLAN Priority
0 to 7
Issue 02 (2010-09-24)
14-211
Parameter
Value Range
Default Value
Description
Port Attributes
UNI
Activation Status
Activated,
Inactivated
NOTE
l The Mapping Protocol and protocol parameters set for VCTRUNKs at one end of a transmission line must
be the same as the Mapping Protocol and protocol parameters set for VCTRUNKs at the other end of the
transmission line.
l The Enabling LCAS and LCAS protocol parameters set for VCTRUNKs at one end of a transmission line
must be the same as the Enabling LCAS and LCAS protocol parameters set for VCTRUNKs at the other
end of the transmission line.
l The timeslots to which the paths bound with a VCTRUNK correspond must be the same at both ends of a
transmission line.
Ingress
14-212
Type of Data
Frame
How to Process
Tag Aware
Access
Hybrid
Tagged frame
Untagged frame
Issue 02 (2010-09-24)
Direction
Egress
Type of Data
Frame
How to Process
Tag Aware
Access
Hybrid
Tagged frame
l If the VLAN ID
in the frame is
Default VLAN
ID, the port
strips the VLAN
tag from the
frame and then
transmits the
frame.
l If the VLAN ID
in the frame is
not Default
VLAN ID, the
port directly
transmits the
frame.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
l
The configuration that complies with the LCAS protocol should meet the following two
requirements:
The configured services should be bidirectional services that adopt virtual
concatenation.
The networking topology should be of the point-to-point mode.
When configuring the LCAS function, you must set the LCAS parameters to the same
values for the equipment at the two ends.
The LCAS enable/disable attribute of the equipment at the two ends must be the same.
The equipment at the two ends must be set to the same LCAS mode.
Procedure
Step 1 Select an NE in the NE explore, choose Configuration > Cross-Connection Configuration
from the Function tree.
Step 2 Click the Create button below the right-side pane, configure the SDH services between the
Ethernet board and the line board according to the requirement.
Issue 02 (2010-09-24)
14-213
The class of bound path configured for the Ethernet board on the source NE must be the same as that on
the sink NE. Otherwise, the LCAS function fails to be configured.
----End
Issue 02 (2010-09-24)
14-215
positions of the network. The broadcast packets are restricted to this VLAN without affecting
the members of other VLANs. If the network location of one member is changed but the VLAN
to which the member belongs is not changed, the configuration of this member can remain
unchanged. If the physical location of one member is not changed but the VLAN to which the
member belongs is changed, the network administrator needs to modify the configuration of this
member.
The virtual workgroup is a long-term goal, which requires support in other aspects.
Source
address
4 bytes
802.1q
header
Length/Type
Data
FCS
(CRC-32)
TCI
TPID
16 bits
PCP
3 bits
CFI
VID
1 bit
12 bits
The 4-byte 802.1q header is divided into two parts: tag protocol identifier (TPID) and tag control
information (TCI). The TCI is divided into three parts: user_priority, canonical format indicator
(CFI), and VLAN identifier (VID).
14-216
Issue 02 (2010-09-24)
TPID
The TPID is a 2-byte field, and it identifies an Ethernet frame as a tagged frame. The value
is always 0x8100. When the network equipment that cannot identify the tagged frame
receives the tagged frame, the equipment discards this frame.
PCP
The priority code point (PCP) identifies the priority of an Ethernet frame. This field can be
used to provide the requirement for the service quality.
CFI
The CFI is a 1-bit filed, and it is used in certain physical networks that adopt the ring
topology. This field is not processed in the Ethernet.
VID
The VLAN ID is a 12-bit field, and it indicates the VLAN that the frame belongs to.
Restricted to the field length, the value of the VID ranges from 1 to 4095.
Ingress
Egress
Type of Frame
Processing Method
Tag Aware
Access
Hybrida
Tagged frame
Receives the
frame.
Discards the
frame.
Receives the
frame.
Untagged frame
Discards the
frame.
Receives the
frame after the
untagged frame
is added with the
port VID
(PVID).
Receives the
frame after the
untagged frame
is added with the
PVID.
Tagged frame
Transmits the
frame.
Transmits the
frame after the
PVID of the
tagged frame is
stripped.
Transmits the
frame after the
PVID of the
tagged frame is
stripped if the
VID equals the
PVID.
Directly
transmits the
frame if the VID
does not equal
the PVID.
Issue 02 (2010-09-24)
14-217
CAUTION
a:
When the TAG attribute of a port on the EMS4 board (a logical board) that is supported by
the IDU 605 1F/2F is set to Hybrid, the packet that is forwarded by this port remains the same
as the packet that enters the bridge.
14.5.2.3 Application
A VLAN allows new application scenarios for the Ethernet private line (EPL) service and the
Ethernet private LAN (EPLAN) service.
In the case of the EPL service, after the VLAN is adopted, the Ethernet board can divide the
flow by port and VLAN ID other than only by port, which allows the development of the EPL
service to the Ethernet virtual private line (EVPL) service. In the case of the EPLAN service,
after the VLAN is adopted, the Ethernet board can create the 802.1q bridge, which allows the
development of the EPLAN service to the Ethernet virtual private LAN (EVPLAN) service.
This topic only describes the application of the VLAN in the EPL service. For details about the
802.1q bridge, see 14.6.2.1 Bridge.
NE2
Branch A
VLAN200-210
VCTRUNK2
Headquaters
NE1
14-218
VLAN100-110
VCTRUNK1
NE3
Branch B
Issue 02 (2010-09-24)
PORT1 VLAN100
VLAN100
PORT1
VCTRUNK1
NE1
VLAN200
NE2
VLAN200
PORT2
PORT2
14.5.3 Availability
The VLAN feature requires the support of the applicable equipment and boards.
Table 14-53 Availability of the VLAN
Feature
Applicable Board
Applicable Equipment
VLAN
IDU 620
NOTE
a:
IDU 605 1F/2F supports the LAN service that is based on the VLAN, but does not support the Ethernet
line service.
Issue 02 (2010-09-24)
Processes the data frame that is input into the switch through a port, according to the
attribute of this port. For details, see Table 14-52.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
14-219
2.
3.
Processes the data frame that is output from this port on the switch, according to the attribute
of this port. For details, see Table 14-52.
Prerequisite
You must learn about the specific application of VLAN.
Precautions
NOTE
This topic describes the planning based on the cases in 14.5.2.3 Application.
Procedure
Step 1 According to the actual requirements, plan the line service type.
When planning the line service type, adhere to the following principles:
l In the case of the point-to-point service, use the Ethernet transparent transmission service.
l If the service of the same PORT needs to be divided by VLAN and if the service frame is
the tagged frame, use the PORT-shared EVPL service.
l If the services of different PORTs need to share one transmission channel and if the service
frame is the untagged frame, use the VCTRUNK-shared EVPL service.
l In the case of other requirements that are not contained in the preceding description, use the
QinQ service or Layer 2 switching service.
Step 2 Optional: Plan the PORT-shared EVPL service.
When planning the PORT-shared EVPL service, adhere to the following principles:
l Set TAG of the PORT to Tag Aware.
l Allocate the VLAN service of this PORT to different VCTRUNKs by VLAN ID.
Step 3 Optional: Plan the VCTRUNK-shared EVPL service.
When planning the VCTRUNK-shared EVPL service, adhere to the following principles:
l Set TAG of the PORT to Access.
l Because the PVIDs of different PORTs should be different, configure the PVIDs of PORTs
by user. For example, if the PVIDs of the PORTs used by user A range from 100 to 199, the
PVIDs of the PORTs used by user B should range from 200 to 299.
l The services of different PORTs should share one VCTRUNK.
----End
14-220
Issue 02 (2010-09-24)
Configure the
Ethernet external port
Configure the
Ethernet internal port
Create the
Ethernet line service
Issue 02 (2010-09-24)
14-221
Table 14-54 Configuration flow of the EVPL service that uses the VLAN feature (PORT-shared
EVPL service)
Number
Description
Create the cross-connection from the paths that are bound to the VCTRUNK
to the corresponding timeslots on the line.
Table 14-55 Configuration flow of the EVPL service that uses the VLAN feature (VCTRUNKshared EVPL service)
Number
Description
14-222
Issue 02 (2010-09-24)
Number
Description
l Configure the EVPL service from the PORT to the specified VCTRUNK
+VLAN.
l For the configuration process, see 14.5.7.2 Creating Ethernet Line
Service.
Create the cross-connection from the paths that are bound to the VCTRUNK
to the corresponding timeslots on the line.
NOTE
If the QoS of the EVPL service needs to be set, see 14.7 Configuring QoS.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be added in the slot layout.
Precautions
l
This topic does not describe the method for creating the QinQ service.
IDU 620 supports the Ethernet switching board EMS6. The EFT4 board is an Ethernet
transparent transmission board, and the PORTs of the EFT4 board correspond to the
VCTRUNKs. Hence, you do not need to create the Ethernet line service.
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Ethernet
Service > Ethernet Line Service from the Function Tree.
Step 2 Click New.
The Create Ethernet Line Service dialog box is displayed.
Step 3 Set the attributes of the Ethernet line service.
Issue 02 (2010-09-24)
14-223
Step 4 Optional: Set the port attributes of the source port and sink port.
NOTE
The result of setting the port attributes during the Ethernet line service configuration process is the same as the
result of directly setting the Ethernet service port attributes.
14-224
1.
Click Configuration.
The Bound Path Configuration dialog box is displayed.
2.
3.
In Available Bound Paths, set Level and Direction of the bound paths.
4.
Select required items in Available Resources and Available Timeslots and click
5.
Issue 02 (2010-09-24)
NOTE
The result of setting the port attributes during the Ethernet line service configuration process is the same
as the result of directly setting the Ethernet service port attributes.
6.
Click OK.
Parameters
Parameter
Value Range
Default Value
Description
Service Type
EPL
Direction
Unidirectional,
Bidirectional
Bidirectional
Issue 02 (2010-09-24)
14-225
Parameter
Value Range
Default Value
Description
Source Port
A specific PORT or
VCTRUNK
PORT1
1-4095
Sink Port
A specific PORT or
VCTRUNK
PORT1
14-226
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
1-4095
Port Enabled
Enabled, Disabled
TAG
Tag Aware
Configurable Ports
Issue 02 (2010-09-24)
VCTRUNKs
VCTRUNK 1
14-227
Parameter
Value Range
Default Value
Description
Available Bound
Paths
Activation Status
Activated,
Inactivated
Precautions
NOTE
l For details about the service configured in this example, refer to the description of the PORT-shared EVPL
service in 14.5.2.3 Application.
l Because NE2 and NE3 in this example are both configured with the point-to-point EVPL service, only the
configuration of NE1 is described here.
Procedure
Step 1 Set the port attributes of PORT. See 14.3.7.1 Configuring External Ethernet Ports.
14-228
Issue 02 (2010-09-24)
Precautions
NOTE
l For details about the service configured in this example, refer to the description of the VCTRUNK-shared
EVPL service in14.5.2.3 Application.
l Because the service configuration of NE1 is the same as the service configuration of NE2 in this example,
only the configuration of NE1 is described here.
Procedure
Step 1 Set the port attributes of PORT1. See 14.3.7.1 Configuring External Ethernet Ports.
Issue 02 (2010-09-24)
14-229
Issue 02 (2010-09-24)
14.6.3 Availability
The Layer 2 switching feature requires the support of the applicable equipment and boards.
14.6.4 Relation with Other Features
The Layer 2 switching has different relations with other features.
14.6.5 Realization Principle
The bridge, STP/RSTP, and IGMP Snooping comply with the relevant IEEE standards.
14.6.6 Planning Guide
Plan the relevant parameters of the Layer 2 switching service according to the actual situation
of microwave links.
14.6.7 Configuration Guide
This topic describes the configuration tasks relevant to the Layer 2 switching feature.
14.6.8 Creating the Ethernet LAN Service
To enable the Ethernet switching board to transmit the LAN service, perform certain operations
to create the bridge and set the attributes of the bridge and to configure the mounted ports of the
bridge.
14.6.9 Modifying the Mounted Port of a Bridge
This operation enables the user to modify the mounted port of a bridge, the enabled state of the
mounted port, and Hub/Spoke attribute of the port.
14.6.10 Creating the VLAN Filter Table
You need to create the VLAN filter table for the bridge when you create the EVPLAN service.
14.6.11 Creating the Entry of a MAC Address Table Manually
The bridge can obtain the dynamic entry of a MAC address table by using the SVL or IVL mode.
In addition, you can manually add the entry of a MAC address table. The manually created
entries of a MAC address table can be classified into two categories: unicast entry (that is, static
entry) and disabled entry (that is, blacklist entry).
14.6.12 Modifying the Aging Time of the MAC Address Table Entry
In the case of the Ethernet switching board, the aging time of a MAC address table entry is 5
minutes by default.
14.6.13 Querying the Actual Capacity of the MAC Address Table and the Dynamic Entry
By querying the actual capacity of the MAC address table and the dynamic entry, you can learn
about the MAC address learning situation of the bridge.
14.6.14 Configuring the Spanning Tree Protocol
In the case of the Layer 2 service, if the loop is formed, enable the STP or RSTP for the bridge
and set bridge parameters and port parameters.
14.6.15 Querying the Running Information About the Spanning Tree Protocol
The running information about the spanning tree protocol includes the bridge running
information and port running information.
14.6.16 Configuring the IGMP Snooping Protocol
If the bridge accesses a LAN where the IGMP multicast server exists, you can enable the IGMP
Snooping protocol and configure the method for processing the unknown multicast packet.
14.6.17 Querying the Running Information About the IGMP Snooping Protocol
The running information about the IGMP Snooping protocol includes the current multicast router
port and multicast table item.
14.6.18 Modifying the Aging Time of the Multicast Table Item
Issue 02 (2010-09-24)
14-231
In the case of the Ethernet switching board, the aging time of a multicast table item is 8 minutes
by default.
14.6.19 Querying the Multicast Router Port
The multicast router port refers to the port that transmits the IGMP query packet to routers. The
Ethernet data board considers the port that receives the IGMP query packet as the router port.
14.6.20 Configuring the Static Multicast Table Item
You can manually specify the static multicast table item that can be forwarded to the
corresponding port in multicast mode.
14.6.21 Querying the Multicast Table Item
You can query the multicast item that the IGMP Snooping protocol dynamically learns and the
static multicast item that is manually created.
Bridge
A bridge refers to a functional unit that realizes the interconnection of two or more LANs. In
the case of the Ethernet service boards that have the Layer 2 switching capability, the switching
domain can be divided into multiple independent sub-switching domains. As a result, different
bridges can access each other only when there are interconnected services. Each bridge is
configured independently and uses VLANs independently. That is, different bridges can use the
same VLAN.
STP/RSTP
Spanning Tree Protocol (STP) applies to a loop network to realize path redundancy backup by
using certain algorithms. STP prunes a loop network into a tree network without loops. This
helps to avoid proliferation and infinite loop of packets on the loop network.
The rapid spanning tree protocol (RSTP) is an update version of the STP. Compared with the
STP, the RSTP can stabilize the network topology more rapidly.
IGMP Snooping
If the multicast router exists on the network, the bridge can start the IGMP Snooping to realize
the multicast function with the cooperation of the router.
14-232
Issue 02 (2010-09-24)
14.6.2.1 Bridge
A bridge refers to a functional unit that realizes the interconnection of two or more LANs.
14.6.2.2 STP/RSTP
When the network topology of the Ethernet service forms loops, enable the STP or RSTP.
14.6.2.3 IGMP Snooping
If the multicast router exists in the network, enable the IGMP Snooping for the bridge to realize
the multicast function with the cooperation of the router.
14.6.2.4 Broadcast Packet Suppression
You can enable the broadcast packet suppression function that is based on the Ethernet port to
prevent spreading of the broadcast storm, through restricting the traffic of the broadcast packet
that enters the Layer 2 switch.
14.6.2.1 Bridge
A bridge refers to a functional unit that realizes the interconnection of two or more LANs.
VB and LP
VB, which is originally put forward by Huawei, is short for various bridge. In the case of the
Ethernet boards that have the Layer 2 switching capability, the switching domain can be divided
into multiple independent sub-switching domains.
A VB contains several logic ports (LPs). By configuring the mounting relation, you can mount
multiple external ports and VCTRUNK ports to one VB. One external port or VCTRUNK port
cannot be mounted to different LPs on one VB.
Figure 14-72 lists the relations among the VB, LP, external port, and VCTRUNK port.
Figure 14-72 Relations among the VB, LP, external port, and VCTRUNK port
Ethernet Switching Board
VB1
PORT1
LP1
LP4
VCTRUNK1
PORT2
LP2
LP5
VCTRUNK2
PORT3
LP3
LP6
VCTRUNK3
Bridge Type
The Ethernet switching board supports three types of bridges: 802.1d bridge, 802.1q bridge, and
802.1ad bridge.
As shown in Figure 14-73, the services on different 802.1d bridges are isolated, but the services
of different VLANs on one bridge are not isolated. The services on different 802.1q bridges are
isolated and the services of different VLANs on one bridge are also isolated.
Issue 02 (2010-09-24)
14-233
PORT1
VLAN1
VLAN2
VLAN3
...
PORT2
PORT3
VCTRUNK1
VCTRUNK2
PORT1
VCTRUNK3
VCTRUNK4
PORT2
VCTRUNK5
VCTRUNK6
PORT3
VCTRUNK1
VCTRUNK2
VLAN1
VLAN2
VCTRUNK3
VCTRUNK4
VCTRUNK5
VCTRUNK6
VLAN3
802.1d bridge
802.1q bridge
Logical port
As shown in Figure 14-74, two conditions may occur for the 802.1ad bridge.
l
When Bridge Switch Mode is set to SVL/Ingress Filter Disable, the services on different
bridges are isolated but the services of different S-VLANs on one bridge are not isolated.
When Bridge Switch Mode is set to IVL/Ingress Filter Enable, the services on different
bridges are isolated and the services of different S-VLANs on one bridge are also isolated.
PORT1
S-VLAN1
S-VLAN2
S-VLAN3
...
PORT2
PORT3
VCTRUNK1
VCTRUNK2
PORT1
VCTRUNK3
VCTRUNK4
PORT2
VCTRUNK5
VCTRUNK6
PORT3
S-VLAN2
VCTRUNK3
VCTRUNK4
VCTRUNK5
VCTRUNK6
S-VLAN3
802.1ad bridge
IVL/Ingress Filter Enable
VCTRUNK1
VCTRUNK2
S-VLAN1
802.1ad bridge
Logic Port
Table 14-56 Three Types of Bridges Supported by the Ethernet Switching Board
14-234
802.1d Bridge
802.1q Bridge
802.1ad Bridge
Bridge switch
mode
SVL/Ingress
Filter Enable
IVL/Ingress
Filter Enable
SVL/Ingress
Filter Disable
IVL/Ingress
Filter Enable
VLAN filtering
table
Not configured
Required
Not configured
Required
Issue 02 (2010-09-24)
802.1d Bridge
802.1q Bridge
802.1ad Bridge
Ingress filtering
Disabled: Does
not check the
VLAN tag.
Enabled:
Checks the
VLAN tag. If
the VLAN ID
does not equal
the VLAN ID of
the port defined
in the VLAN
filtering table,
the packet is
discarded.
Disabled: Does
not check the
VLAN tag.
Enabled:
Checks the SVLAN tag. If the
VLAN ID does
not equal the
VLAN ID of the
port defined in
the VLAN
filtering table,
the packet is
discarded.
Bridge learning
mode
SVLa
IVLb
SVLa
IVLb
Packet
forwarding
mode
Obtains the
packet
forwarding port
by querying the
MAC address
table, according
to the
destination
MAC address of
the packet.
Obtains the
packet
forwarding port
by querying the
MAC address
table, according
to the
destination
MAC address
and VLAN ID
of the packet.
Obtains the
packet
forwarding port
by querying the
MAC address
table, according
to the
destination
MAC address of
the packet.
Obtains the
packet
forwarding port
by querying the
MAC address
table, according
to the
destination
MAC address
and VLAN ID of
the packet.
Range of
broadcasting
Forwards the
broadcast
packet to all the
ports on the
bridge.
Forwards the
broadcast
packet to the
ports that are
specified in the
VLAN filtering
table.
Forwards the
broadcast
packet to all the
ports on the
bridge.
Forwards the
broadcast packet
to the ports that
are specified in
the S-VLAN
filtering table.
Mount port
attribute
UNI
UNI
C-aware
C-aware
S-aware
S-aware
NOTE
l a: When the bridge uses the shared VLAN learning (SVL) mode, it creates an entry according to the source
MAC address and the source port of a packet. This entry is valid to all VLANs.
l b: When the bridge uses the independent VLAN learning (IVL) mode, it creates an entry according to the
source MAC address, VLAN ID, and source port of a packet. This entry is valid to only this VLAN.
l For details about the 802.1ad bridge, see 14.2.2.4 Application of the QinQ Technology in LAN
Services.
14-235
Dynamic entry
A dynamic entry is obtained by a bridge through the SVL/IVL mode. The dynamic entry
ages, and is lost after the Ethernet switching board is reset.
Static entry
A static entry, which corresponds to a specific MAC address and port, is manually added
by the network administrator into the MAC address table on the NM. A static entry is also
called a unicast entry. The static entry does not age, and is not lost after the Ethernet
switching board is reset.
Blacklist entry
A blacklist entry is used to discard the data frame that contains the specified destination
MAC address, that is, the MAC disabled entry. A blacklist entry is also called a blackhole
entry. The blackhole entry is configured by the network administrator. The blackhole entry
does not age, and is not lost after the Ethernet switching board is reset.
NOTE
l If one routing entry is not updated in a certain period, that is, if no new packet from this MAC address is
received to enable the re-learning of this MAC address, this routing entry is automatically deleted. This
mechanism is called aging, and this period is called aging time. The aging time of a MAC address table is
5 minutes by default. You can set this value on the NM.
l The number of entries in a MAC address table is limited. The MAC address capacity of each bridge in the
case of the Ethernet switching board is 16K.
Hub/Spoke
In the case of the convergence service, the mutual access between the non-central stations and
central stations is required but the access between non-central stations is not required. In this
case, specify a mounted port as a Hub port or a Spoke port.
l
Hub port
Hub ports can mutually access each other. Hub ports and Spoke ports can mutually access
each other.
Spoke port
Spoke ports cannot mutually access each other. Hub ports and Spoke ports can mutually
access each other.
14.6.2.2 STP/RSTP
When the network topology of the Ethernet service forms loops, enable the STP or RSTP.
STP
The spanning tree protocol (STP) is used in the looped network. This protocol realizes the routing
redundancy by adopting certain algorithms and releases the looped network into loop-free tree
network, thus preventing the packets from increasing and cycling in an endless manner in the
looped network.
The STP meets the following requirements:
l
14-236
Configures any activated topology of any bridge to a single spanning tree, and releases the
redundant data loop if there is any between two stations in the network topology.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
Re-configures the spanning tree topology in the case of a bridge fault or an interrupted
route, thus providing a certain protection, and prevents temporary data loops by
automatically containing the bridges and ports of the bridges that are newly added into the
LAN.
The finally activated topology can be predicted and repeated. In addition, the topology can
be selected by managing the parameters of certain algorithms.
Operations to the end stations are transparent. For example, the end stations are unaware
of their attachment to a single LAN or a bridged LAN.
A small part of the available bandwidth of the link is used to create or maintain the spanning
tree, and the bandwidth does not increase with the expanding network size.
The Ethernet switching board supports the STP, which complies with IEEE 802.1d.
RSTP
The rapid spanning tree protocol (RSTP) is an optimized version of STP. Compared to the STP,
the RSTP can stabilize the network topology in a shorter time. The RSTP is compatible with the
STP. These two topologies can be identified by the bridge that uses the RSTP for calculating
the spanning tree.
The Ethernet switching board supports the RSTP, which complies with IEEE 802.1w.
Multicast Protocol
The multimedia network applications, such as video conference, E-learning, and video on
demand (VOD) service, require that the information is transmitted from one source to multiple
destinations, that is, transmitted in one-to-many transmission mode. Because the data traffic of
the multimedia information is large, simulating the one-to-many transmission through one-toone mode occupies a large volume of bandwidth. In addition, information flooding is generated
if the broadcast is used. Hence, the one-to-many multicast protocol is required.
The IP multicast protocol is based on the IP protocol stack. The IP multicast protocol uses a Dtype IP address that is similar to the unicast address to indicate a group. When the packet is
transmitted to all the IP hosts in a multicast group, the calling and access mode is similar to the
calling and access mode of the unicast. The hosts in an IP multicast group can join or quit this
multicast group at any time and at any location, with unlimited number of members. The
multicast router does not store the member relations of all the hosts. The router stores the
information only about whether any host in the physical subnetwork on the physical interface
belongs to a specific multicast group. The host stores the information only about the multicast
groups that it joins.
The IP multicast protocol is classified into two categories: communication protocol among the
multicast routers and the protocol among the multicast routers, hosts, and Layer 2 switches.
l
Issue 02 (2010-09-24)
The communication protocol among multicast routers is used to obtain the multicast routing
information. This type of protocol contains the protocol independent multicast-dense mode
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
14-237
The protocol among the multicast routers, hosts, and Layer 2 switches is used to forward
the multicast packet according to the multicast routing information. This type of protocol
contains the Internet group management protocol (IGMP), IGMP Snoop, IGMP Proxy.
IGMP is a Layer 3 multicast protocol, and IGMP Snooping, IGMP Proxy are Layer 2
multicast protocols.
IGMP
The IGMP contained in the TCP/IP suite is used to manage members of the IP multicast group.
It creates and maintains the member relations of the multicast group between the host and its
adjacent multicast router.
The host notifies the local router of joining a specific multicast group and of accepting the
information from this multicast group through this protocol. The router periodically queries
whether a member of a specific group in the LAN is activated through this protocol (that is,
whether the member of a specific multicast group still exists in the network segment), and thus
collects and maintains the member relations of groups that are connected to the router. By using
this mechanism, the multicast router establishes a table, which contains the ports of the router
and members of each specific group in the subnetworks corresponding to each port. When
receiving the packet of a specific group, the router forwards the packet only to these ports that
have the members of this group.
The router uses the IP multicast address to forward multicast packets. Each multicast group
corresponds to a specific IP multicast address. The IP multicast address is a D-type IP address,
which ranges from 224.0.0.0 to 239.255.255.255.
IGMP Snooping
When the multicast router is connected to the host by using the bridge, the switch broadcasts the
multicast packet at Layer 2 if the bridge disables the Layer 2 multicast protocol. See Figure
14-75. When the multicast router is connected to the host by using the bridge, if the bridge
enables the Layer 2 multicast protocol (such as IGMP Snooping), the bridge can establish the
mapping relations between group members and switch ports and thus can forward the packet
only to the ports that have group members.
Figure 14-75 Transmission of the multicast packet (with IGMP Snooping disabled)
Internet/
Intranet
Video stream
VOD server
Multicast router
Video stream
Layer 2 Ethernet
switch
Video
stream
Multicast
group member
14-238
Video
stream
Video
stream
Non-multicast Non-multicast
group member group member
Issue 02 (2010-09-24)
Figure 14-76 Transmission of the multicast packet (with IGMP Snooping enabled)
Internet/
Intranet
Video stream
VOD server
Multicast router
Layer 2 Ethernet
switch
Video stream
Video
stream
Multicast
group member
Non-multicast Non-multicast
group member group member
The IGMP Snooping creates and maintains the mapping relations between group members and
switch ports by sensing the IGMP packet. After the IGMP Snooping is enabled, the bridge
considers the port that receives the IGMP request as the router port. When detecting the response
that is transmitted to the router port, the bridge adds the port that receives the response and the
router port into a specific multicast group. When detecting that a certain port in a multicast group
does not respond to the IGMP request for consecutive times and that the times exceed the
threshold, the bridge deletes this port from the multicast group.
After the IGMP Snooping is enabled, when receiving the multicast packet, the bridge queries
the multicast table in which the source port is the router port. If a multicast group that matches
the multicast address exists in the multicast table, the bridge forwards the packet to this multicast
group. If no multicast group exists, the bridge discards the multicast packet or broadcasts the
packet depending on the NM setting.
Three versions of IGMP requests are available, and they are, V1, V2, and V3. The Ethernet
switching board can process versions V1 and V2. The Ethernet switching board also supports
the aging of the router port and multicast table item.
NOTE
l If a router port is not updated in a certain period (that is, no IGMP request from this port is received), all the
multicast tables that are related to this router port are deleted. This mechanism is called aging, and this period
is called aging time. The aging time of a router port is 5 minutes by default. You cannot set this value on
the NM.
l Similarly, the multicast table item (that is, multicast group) ages. The aging time is 8 minute by default. You
can set this value on the NM.
14-239
Based on the ratio of the number of broadcast packets to the total number of packets, the broadcast
packet suppression function determines whether the system restricts the broadcast traffic. When
the ratio of the number of broadcast packets to the total number of packets exceeds the value set
by the user, the system discards the broadcast traffic to decrease the ratio of the broadcast packets
so that the ratio is in a reasonable range. In this manner, the broadcast storm can be prevented
and the network congestion is avoided, which ensures the normal operation of the network.
PORTs of the Ethernet switching board support the broadcast packet suppression function.
14.6.3 Availability
The Layer 2 switching feature requires the support of the applicable equipment and boards.
Table 14-57 Availability of Layer 2 Switching
Feature
Applicable Board
Applicable Equipment
EMS6, EFP6
IDU 620
EM4T
IDU 605
EMS6, EFP6
IDU 620
EMS6, EFP6
IDU 620
EM4T
IDU 605
EMS6, EFP6
IDU 620
IDU 605
IGMP Snooping
STP/RSTP
Broadcast packet
suppression
The port that is used by the bridge cannot be configured with the line service.
The broadcast packet suppression function is applicable only to the PORT on the bridge.
Issue 02 (2010-09-24)
The IGMP Snooping establishes and creates the mapping relations between the group members
and switch ports by sensing the IGMP packet. This ensures that the multicast packet is
transmitted only to the ports that are connected to the multicast users.
14.6.5.1 Bridge
A bridge forwards a packet according to the entry of a MAC address table.
A bridge forwards a packet as follows:
1.
In the case of an 802.1q bridge, it checks the VLAN ID of a data frame that is received at
the port. If the VLAN ID of this frame does not equal the VLAN ID of the port that is
defined in the VLAN filter table, the bridge discards this frame.
2.
If the broadcast packet suppression function of the bridge port is enabled and the traffic of
the broadcast packet exceeds the pre-set threshold value, the port discards the received
broadcast frame.
3.
If the IGMP Snooping protocol of the bridge is enabled, the bridge processes the IGMP
packet and multicast packet that are received at the port, according to the principle described
in 14.6.5.3 IGMP Snooping.
4.
If the bridge receives the multicast packet but the IGMP Snooping protocol is disabled, it
forwards the multicast packet among all the ports of the bridge or among all the mounted
ports of the VLAN (excluding the source port).
5.
According to the learning mode, the bridge adds or updates the entry corresponding to the
source MAC address of the data frame in the MAC address table, and thus establishes the
mapping relation between the MAC address and the receive port.
6.
The bridge checks the MAC address table according to the destination MAC address of the
data frame.
l If the blacklist entry corresponding to the destination MAC address exists, the bridge
discards this data frame.
l If the dynamic entry or the static entry corresponding to the destination MAC address
exists, the bridge forwards this data frame to the destination port indicated by the entry.
l If no corresponding entry exists, the bridge forwards the packet among all the ports of
the bridge or among all the mounted ports of the VLAN (excluding the source port),
according to the bridge type (802.1d bridge or 802.1q bridge).
7.
The bridge needs to determine whether the source port and the destination port are Hub or
Spoke when forwarding the data frame. If the source port is the Hub port, the bridge
forwards the packet to the Hub port and the Spoke port. If the source port is the Spoke port,
the bridge forwards the packet to the Hub port.
NOTE
If the STP or the RSTP of the bridge is enabled, only the port in the forwarding state can forward the data frame.
14.6.5.2 STP/RSTP
The realization of the STP complies with IEEE 802.1d, and the realization of the RSTP complies
with IEEE 802.1w.
Basic Concepts
l
Issue 02 (2010-09-24)
14-241
The STP transmits the BPDU among pieces of equipment to determine the network
topology. The BPDU contains adequate information that is required to implement the
calculation of the spanning tree. The BPDU is classified into the following categories:
Configuration BPDU (CBPDU)
The CBPDU refers to a packet that is used to calculate the spanning tree and maintain
the spanning tree topology. The CBPDU contains the root bridge ID, root path cost,
designated bridge ID, designated port ID, and related timing information.
Topology change Notification BPDU (TCN BPDU)
The TCN BPDU refers to a packet that is used to notify the relevant equipment of the
network topology change in the case of topology change.
l
Bridge ID
The bridge ID is used to indicate a bridge. The bridge ID is 64-bit long. The most significant
16 bits indicate the priority of the bridge, and the least significant 48 bits indicate the MAC
address of a certain bridge port. In the STP, the bridge ID also indicates the priority of the
bridge. The smaller the value of the bridge ID, the higher the priority.
Port ID
The port ID is used to indicate a port on the bridge. The port ID is 16-bit long. The most
significant eight bits indicate the priority of the port, and the least significant eight bits
indicate the port number. In the STP, the port ID also indicates the priority of the port. The
smaller the value of the port ID, the higher the priority.
Root bridge
In a network that enables the STP, only one root bridge exists. The root bridge is selected
based on the running of the STP. The bridge with the smallest bridge ID is selected as the
root bridge. When a network that enables the STP is stabilized, only the root bridge
generates and transmits the CBPDU periodically. Other bridges only relay the CBPDU.
This can ensure a stable network topology. If the network topology is changed, the root
bridge may also change.
Root port
The root port refers to a port on the bridge that transmits/receives frames to/from the root
bridge. Each non-root bridge has only one root port. The root port is selected based on the
running of the STP. The port of a bridge whose root path cost is the smallest is selected as
the root port. If more than one port whose root path cost is the smallest exist, the port with
the smallest port ID is selected as the root port.
Designated port
The designated port refers to a port of a LAN that transmits/receives frames to/from the
root bridge. Each LAN has only one designated port. The designated port is selected based
on the running of the STP. The port that is connected to the LAN and whose root path cost
is the smallest is selected as the designated port. If more than one port whose root path cost
is the smallest exist and if these ports are on different bridges, the port whose bridge ID is
the smallest is selected as the designated port. If more than one port whose root path cost
is the smallest exist and if these ports are on the same bridge, the port with the smallest port
ID is selected as the designated port.
Path cost
The path cost is used to indicate the status of the network that is connected to the port. The
higher the rate of the port, the smaller the path cost.
l
14-242
Issue 02 (2010-09-24)
The root path cost refers to the cost of the path from a certain port to the root bridge. That
is, the sum of path cost of all the passed ports from this port to the root bridge.
l
Port state
In a network that enables the STP, the port state can be any of the following states:
Blocking
A port in the blocking state receives and processes the BPDU and does not transmit the
BPDU. When a port is in the blocking state, it does not learn the MAC address and does
not forward the user packet.
Listening
It is a transitional state. A port in the listening state transmits, receives, and processes
the BPDU. When a port is in the listening state, it neither learns the MAC address nor
forwards the user packet.
Learning
It is a transitional state. A port in the learning state transmits, receives, and processes
the BPDU. When a port is in the learning state, it learns the MAC address but does not
forward the user packet.
Forwarding
A port in the forwarding state transmits, receives, and processes the BPDU. When a
port is in the learning state, it learns the MAC address and forwards the user packet.
Disabled
A port in the disabled state does not forward frames, and does not implement the
spanning tree algorithm and STP.
Timer
Port timers are classified into the following categories:
Hold timer
The hold timer is used to measure the interval between two CBPDU transmissions. The
timeout value is the Hold Time of the bridge.
Message age timer
The message age timer is used to measure the age of the CBPDU packet recorded by a
port. When the age of the CBPDU packet stored by the bridge exceeds the Message Age
parameter, the bridge discards the packet. The Message Age parameter determines the
initialization age when the CBPDU packet is stored in the bridge. The Message Age
parameter is 0 when the root bridge generates the packet. Each time the packet is
forwarded to a port, a fixed increment value is added to the Message Age parameter.
Forward delay timer
The forward delay timer is used to measure the holding time of a port in the listening
state and in the learning state. When the listening state remains for a period that is the
same as the value of the Forward Delay parameter, the port state is changed to learning.
When the learning state remains for a period that is the same as the value of the Forward
Delay parameter, the port state is changed to forwarding.
Bridge timers are classified into the following categories:
Hello timer
The hello timer is used to measure the interval when the bridge transmits the CBPDU
packet. The timeout value is the Bridge Hello Time of the bridge.
Topology change notification timer
Issue 02 (2010-09-24)
14-243
The topology change notification timer indicates the duration when the bridge
periodically transmits the TCN. The timer is used to notify the designated bridge in the
LAN that is attached to the root port of the bridge of any detected topology change. The
timeout value is the Bridge Hello Time of the bridge.
Topology change timer
In the case of the root bridge, when receiving the TCN, the bridge transmits the TCN
after the topology change is complete and the time period indicated by the topology
change timer times out. The timeout value is the Topology Change Time of the bridge.
NOTE
The Max Age, Hello Time, and Forward Delay parameters that are used by different bridges are unified
to the values of these three parameters that are used by the root bridge, by mutually transmitting the
CBPDU.
STP Algorithm
The STP algorithm is conducted as follows:
1.
In the initialization state, all the ports on all the bridges are in the listening state. In this
case, each port generates the CBPDU, and the CBPDU considers the bridge where the port
resides as the root bridge and the root path cost of the CBPDU is 0. Each port transmits the
CBPDU periodically, and the period is the Hello Time of the bridge.
2.
The bridge compares the information about the CBPDU that is received at the port with
the CBPDU information that is stored by that port.
The bridge compares the information that is carried by the CBPDU as follows:
(1) The bridge first compares the root bridge IDs. The smaller the ID, the better.
(2) If the root bridge IDs are the same, the bridge compares the root path cost values. The
smaller the root path cost, the better.
(3) If the root path cost values are the same, the bridge compares the designated bridge
IDs. The smaller the designated bridge ID, the better.
(4) If the designated bridge IDs are the same, the bridge compares the designated port
IDs. The smaller the designated port ID, the better.
3.
If the information about the CBPDU that is received at the port is better, the bridge replaces
the information about the CBPDU that is originally stored by the port. If the root bridge ID
or the root path cost in the information about the CBPDU that replaces the information
about the CBPDU originally stored by the port is smaller than the information originally
stored by the port, the bridge needs to process this new CBPDU as follows:
l The bridge stores the information about the CBPDU (including the root bridge ID, root
path cost, message age, and corresponding timers).
l The bridge updates the root bridge ID and root path cost (the root path cost of the bridge
equals the sum of the root path cost of the port that stores the packet and the root path
cost of the port that receives the CBPDU).
l The designated port updates the designated root bridge and the root path cost at the same
time (the root path cost of the designated port equals the sum of the root path cost of
the bridge and the path cost of the port).
l The designated port relays the CBPDU.
If the information about the CBPDU that is received at the port is worse than the information
about the CBPDU that is stored by the port, the port transmits the CBPDU that is stored as
a response.
14-244
Issue 02 (2010-09-24)
4.
If the bridge maintains a root bridge ID that is the same as its bridge ID and if the root path
cost is 0, the bridge is a root bridge. The root bridge sets the path cost of each port to 0.
5.
If the bridge is a non-root bridge, it considers the port that receives the best CBPDU
information as the root port.
6.
If the bridge is a non-root bridge, it considers any of the following ports as the designated
port:
l The bridge ID and port ID of the port are the same as the designated bridge ID and port
ID recorded by the port.
l The root bridge ID recorded by the port is different from the root bridge ID of the bridge.
l The root path cost of the port (sum of the root path cost of the bridge and the path cost
of the port) is smaller than the root path cost recorded by the port.
l The root path cost of the port is the same as the root path cost recorded by the port, but
the bridge ID is smaller than the designated bridge ID of the port.
l The root path cost of the port is the same as the root path cost recorded by the port, and
the bridge ID is the same as the designated bridge ID of the port. The port ID, however,
is smaller than the designated ID of the port.
7.
When the Forward Delay parameter set for the listening state timer of the port expires, the
states of the root port and the designated port transition to learning. When the learning state
remains for a period that is the same as the value of the Forward Delay parameter, the states
of the root port and the designated port transition to forwarding. The states of these ports
whose states are not changed to forwarding transition to blocking.
8.
If a trail becomes faulty, the root port on this trail no longer receives new CBPDUs, and
therefore, the original CBPDU is discarded due to timeout. In this case, the calculation of
the spanning tree is conducted again, and a new trail will be available to replace the faulty
trail, thus restoring the connectivity of the network.
Issue 02 (2010-09-24)
14-245
attribute of a port is set to shared media, the actual point-to-point attribute of the port
is "false". If the point-to-point attribute of a port is set to link connection, the actual
point-to-point attribute is "true". Only the port whose point-to-point attribute is "true"
can transmit the rapid transition request and response.
Edge port
The edge port refers to the bridge port that is connected only to the LAN. If a port is set
to an edge port and if this port can receive the BPDU, the port is actually an edge port.
If the port role of this edge port is a designated port, the port can realize the rapid state
transition.
The rapid transition among port states can be classified into the rapid port state transition
of the root port, rapid port state transition of the designated port, and the rapid port state
transition of the alternate port and backup port.
Rapid port state transition of the root port
A root port that does not function as a backup port recently (that is, in a recent period
that is less than double times of the Hello Time) transition to the forwarding state without
any delay, and this root port enables the designated port that functions as the root port
recently (that is, in a recent period that is less than Forward Delay) to transition to the
discarding state.
Rapid port state transition of the designated port
If an edge port is also a designated port, the port state transitions to the forwarding state
without any delay. The designated port whose actual point-to-point attribute is "true"
can realize the rapid transition among port states through rapid switching between the
request process and response process.
Rapid port state transition of the alternate port and the backup port
The port state of the alternate port and the backup port transitions to the disabled state
without any delay.
Basic Concepts
l
Router port
The router port refers to a port that connects to a multicast router.
Multicast group
The multicast group records the mapping relations among the router ports, MAC multicast
addresses, and multicast group members. A multicast group is also called a multicast table
item.
14-246
Issue 02 (2010-09-24)
response times of the port. When the no-response times of the port exceeds the pre-set
threshold, the bridge deletes the multicast member from the multicast group.
l
Processing Flow
The 802.1q bridge processes the IGMP Snooping as follows:
1.
If receiving the IGMP general query packet or the IGMP specific query packet, the bridge
processes this packet as follows:
(1) The bridge checks whether the port that receives the packet is already learnt as the
router port.
(2) If this port is already learnt, the bridge re-sets the aging time of the router port. If this
port is not learnt, the bridge records the port as the router port and starts the aging
timer of the port.
(3) If the received packet is the IGMP specific query packet and the port that receives this
packet is already recorded as the router port, the bridge broadcasts this packet in the
specific multicast group and starts the timer for the maximum query response time if
the multicast group that is specified in this packet exists. Otherwise, the bridge
broadcasts this packet in the VLAN domain of the 802.1q bridge.
2.
If receiving the IGMP report packet, the bridge processes this packet as follows:
(1) The bridge checks whether the multicast record is already learnt in the VLAN domain
of the 802.1q bridge.
(2) If this multicast record is not learnt and if the multicast group does not exist, the bridge
creates the multicast group and establishes the mapping relations among the router
ports, MAC multicast addresses, and multicast group members by considering this
port as the multicast member port. If this multicast record is not learnt and this port is
not contained in the multicast member ports of the multicast group, the multicast group
adds this port as the multicast member port. If this multicast record is learnt, the bridge
re-sets the counting of no-response times for this multicast member.
3.
If receiving the multicast packet, the bridge processes this packet as follows:
l The bridge queries the multicast table that uses the router port as the source port.
l If a multicast group that matches the multicast address exists in the multicast table, the
bridge forwards the packet to this multicast group.
l If no multicast group exists, the bridge discards the multicast packet or broadcasts the
packet in the VLAN range depending on the NM setting.
Issue 02 (2010-09-24)
14-247
4.
The 802.1d bridge processes the IGMP Snooping similarly. The difference is as follows: The
802.1d learns the packet by using the SVL mode other than by using the IVL mode, and the
802.1d bridge broadcasts the packet without the restriction of the VLAN domain.
Version
Three versions of IGMP requests are available, and they are, V1, V2, and V3. The Ethernet
switching board can process versions V1 and V2.
V2 is compatible with V1. Compared with V1, V2 is improved as follows:
l
Prerequisite
You must learn the situation of the microwave links.
Procedure
Step 1 Plan the bridge.
Adhere to the following principles when planning the bridge:
l Using the 802.1q bridge is a priority. If the conditions of the VLAN that is used by the user
are not known and if the user does not require the isolation of the data among VLANs, you
can also use the 802.1d bridge.
l If the Layer 2 switching services from several branch nodes are converged at a convergence
node, set this convergence node to Hub and set these branch nodes to Spoke. In the case of
the multipoint-to-multipoint Layer 2 switching service, set each node to Hub.
Step 2 Plan the MAC address table.
Adhere to the following principles when planning the MAC address table:
l If the node that only receives data frames exists in the network, configure the corresponding
VLAN unicast entry.
14-248
Issue 02 (2010-09-24)
l If certain nodes are not allowed to transmit data frames, configure the corresponding MAC
disabled entries for the bridge that accesses these nodes.
l Set the aging time of the MAC address table to the same value as the aging time of the
interconnected Ethernet equipment. It is recommended that you set the aging time of the
MAC address table to 5 minutes (default value).
Step 3 Plan the STP/RSTP.
Adhere to the following principles when planning the STP/RSTP:
l In the service networking process, it is recommended that you prevent the loop from forming
in the case of the Layer 2 service and thus avoid enabling the STP or RSTP.
l If the loop is already formed in the service networking, you must enable the STP or RSTP.
The protocol type should be set according to the requirement of the interconnected Ethernet
equipment. It is recommended that you use the RSTP.
l The bridge priority, port priority, and port path cost should be set according to the requirement
of the interconnected Ethernet equipment. Use the default values, unless otherwise specified.
l The Max Age, Hello Time, and Forward Delay parameters should be set to the same values
as these parameters of the interconnected Ethernet equipment. Use the default values, unless
otherwise specified.
Step 4 Plan the IGMP Snooping protocol.
Adhere to the following principles when planning the IGMP Snooping protocol:
l If the IGMP multicast router exists in the interconnected Ethernet network, enable the IGMP
Snooping protocol according to the requirement of the router. Otherwise, do not enable the
IGMP Snooping protocol.
l Set the processing method for the unknown multicast packet and multicast aging time
according to the requirement of the IGMP multicast router. It is recommended that you use
the default values.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
Precautions
l
Issue 02 (2010-09-24)
This task describes only how to create the 802.1d bridge and how to create the 802.1q
bridge.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
14-249
The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board).
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Ethernet
Service > Ethernet LAN Service from the Function Tree.
Step 2 Click New.
The Create Ethernet LAN Service dialog box is displayed.
Step 3 Set the attributes of the bridge according to the bridge type.
l Set the attributes of the 802.1q bridge.
14-250
Issue 02 (2010-09-24)
2.
Select a port from the ports listed in Available Mounted Ports, and then click
3.
4.
Click OK.
Step 5 Optional: If any VCTRUNK is mounted to the VB, configure the VC paths that are bound to
the VCTRUNK.
1.
Click Configuration.
The Bound Path Configuration dialog box is displayed.
2.
Issue 02 (2010-09-24)
14-251
3.
In Available Bound Paths, set Level and Service Direction of the bound paths.
4.
Select required items in Available Resources and Available Timeslots and click
5.
NOTE
The result of setting the port attributes during the Ethernet line service configuration process is the same
as the result of directly setting the Ethernet service port attributes.
6.
Click OK.
Parameters
Parameter
Value Range
Default Value
Description
VB Name
Bridge Type
802.1q, 802.1d,
802.1ad (EMS6)
802.1q
802.1q, 802.1d
(EM4T, a logical
board EMS4)
14-252
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
IVL/Ingress Filter
Enable (802.1q),
SVL/Ingress Filter
Disable (802.1d)
IVL/Ingress Filter
Enable (802.1q),
SVL/Ingress Filter
Disable (802.1d)
Mount Port
Configurable Ports
Issue 02 (2010-09-24)
Mount each
VCTRUNK of the
port.
14-253
Parameter
Value Range
Default Value
Description
Available Bound
Paths
Activation Status
Activated,
Inactivated
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
The Ethernet LAN service must be created.
14-254
Issue 02 (2010-09-24)
Precautions
CAUTION
Modifying the ports that are mounted to the bridge may interrupt the service.
CAUTION
Incorrect configuration of Hub/Spoke attribute interrupts the service.
The IDU 620 supports the Ethernet switching board EMS6.
The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board).
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Ethernet
Service > Ethernet LAN Service from the Function Tree.
Step 2 Select the bridge that is already created, and click the Service Mount tab.
Step 3 Modify the mounted port of this bridge and the related attributes of the mounted port.
To change the port that is connected to the 802.1d/802.1q bridge, click the corresponding Mount
Port. After selecting the corresponding option from the drop-down list, click Apply.
To change the port that is connected to the 802.1ad bridge, click Configure Mount. After
changing the settings in the dialog box that is displayed, click OK.
----End
Parameters
Parameter
Value Range
Default Value
Description
VB Port
1 to 14
Mount Port
Unconnected, a
specific PORT, a
specific
VCTRUNK, IFUP1
Enabled, Disabled
Enabled
Port Enabled
Issue 02 (2010-09-24)
14-255
Parameter
Value Range
Default Value
Description
Hub/Spoke
Hub, Spoke
Hub
TAG
Tag Aware
Working Mode
10M Half-Duplex,
10M Full-Duplex,
100M Half-Duplex,
100M Full-Duplex,
Auto-Negotiation (a
logical board
EMS4, PORT1PORT3)
Auto-Negotiation
10M Half-Duplex,
10M Full-Duplex,
100M Half-Duplex,
100M Full-Duplex,
1000M FullDuplex, AutoNegotiation (a
logical board
EMS4, PORT4)
10M Half-Duplex,
10M Full-Duplex,
100M Half-Duplex,
100M Full-Duplex,
1000M FullDuplex, AutoNegotiation
(EMS6)
Activation Status
14-256
Activated,
Inactivated
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
The EVPLAN service must be created.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board).
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Ethernet
Service > Ethernet LAN Service from the Function Tree.
Step 2 Select the bridge that is already created, and click the VLAN Filtering tab.
Step 3 Create the VLAN filter table.
1.
Click New.
The Create VLAN dialog box is displayed.
2.
3.
Select a port from the ports listed in Available forwarding ports, and then click
4.
Issue 02 (2010-09-24)
14-257
5.
Click OK.
----End
Parameters
Parameter
Value Range
Default Value
Description
VLAN ID (e.g:
1,3-6)
1-4095
selected forwarding
ports
This parameter
indicates the ports
that are mounted to a
bridge.
14-258
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
The Ethernet LAN service must be created.
The VLAN filter table must be created.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board).
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Ethernet
Service > Ethernet LAN Service from the Function Tree.
Step 2 Optional: Create the unicast entry manually.
1.
Select the bridge that is already created, and click the VLAN Unicast tab.
2.
Click New.
The Create VLAN Unicast dialog box is displayed.
3.
4.
Click OK.
Select the bridge that is already created, and click the Disable MAC Address tab.
2.
Click New.
The Disable MAC Address Creation dialog box is displayed.
3.
Issue 02 (2010-09-24)
14-259
4.
Click OK.
----End
Parameters
Parameter
Value Range
Default Value
Description
VLAN ID (e.g.
1,3-6)
1-4095
VLAN ID
Physical Port
14.6.12 Modifying the Aging Time of the MAC Address Table Entry
In the case of the Ethernet switching board, the aging time of a MAC address table entry is 5
minutes by default.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
The Ethernet LAN service must be created.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board).
14-260
Issue 02 (2010-09-24)
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Layer-2
Switching Management > Aging Time from the Function Tree.
Step 2 Modify the aging time of the MAC address table entry.
1.
Double-click MAC Address Aging Time corresponding to this Ethernet switching board.
The MAC Address Aging Time dialog box is displayed.
2.
3.
Click OK.
Parameters
Parameter
Value Range
Default Value
Description
MAC Address
Aging Time
5 Min
14-261
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
The Ethernet LAN service must be created.
Precautions
The IDU 620 supports the Ethernet switching board EMS6, which supports the querying of the
VLAN MAC address table capacity and the self-learning MAC address.
The IDU 605 IF/2F supports the Ethernet switching board EMS4 (a logical board), which
supports the querying of the self-learning MAC address only.
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Ethernet
Service > Ethernet LAN Service from the Function Tree.
Step 2 Query the actual capacity of the MAC address table.
1.
Select the bridge that is already created, and click the VLAN MAC Address Table
Capacity tab.
2.
Click Query.
3.
Select the bridge that is already created, and click the Self-learning MAC Address tab.
2.
Optional: Click First page, Previous, or Next to view the dynamic entries of the MAC
address table by page.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
The Ethernet LAN service must be created.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
14-262
Issue 02 (2010-09-24)
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > Layer-2
Switching Management > Spanning Tree from the Function Tree.
Step 2 Optional: Set the enabled status of the protocol.
1.
2.
3.
Click Apply.
2.
3.
Click Apply.
2.
3.
Click Apply.
Step 5 Optional: If you are enabling the RSTP, set the point-to-point attribute of the Ethernet port.
1.
2.
3.
Click Apply.
----End
Issue 02 (2010-09-24)
14-263
Parameters
Parameter
Value Range
Default Value
Description
Protocol Enabled
Enabled, Disabled
Disabled
Protocol Type
STP, RSTP
RSTP
Priority (Bridge
Parameter)
0-61440
32768
6-40
20
14-264
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
1-10
4-30
15
TxHoldCout (per
second)
1-10
Priority (Port
Parameters)
0-240
128
1-65535
Admin Edge
Attribute
Enabled, Disabled
Disabled
Issue 02 (2010-09-24)
14-265
Parameter
Value Range
Default Value
Description
Protocol Enabled
Enabled, Disabled
Enabled
Auto Edge
Detection
Enabled, Disabled
Disabled
Point-to-Point
Attribute
Adaptive
connection, Link
connection, Shared
media
Adaptive
connection
14-266
Issue 02 (2010-09-24)
NOTE
l In the service networking process, it is recommended that you prevent the loop from forming in the case of
the Layer 2 service and thus avoid enabling the STP or RSTP.
l Because the RSTP and STP are complicated, it is recommended that you negotiate with the engineer in
charge of maintaining the opposite Ethernet equipment and set the related parameters as instructed, before
enabling the STP or RSTP.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
The Ethernet LAN service must be created.
The STP or RSTP of the bridge must be enabled.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Layer-2
Switching Management > Spanning Tree from the Function Tree.
Step 2 Query the bridge running information.
1.
2.
Click Query.
3.
2.
Click Query.
3.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Issue 02 (2010-09-24)
14-267
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > Layer-2
Switching Management > IGMP Snooping Protocol from the Function Tree.
Step 2 Click the Protocol Enable tab.
Step 3 Set the information related to the IGMP Snooping protocol.
Parameters
Parameter
Value Range
Default Value
Description
Protocol Enable
Enabled, Disabled
Disabled
14-268
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
Enabled, Disabled
Enabled
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
The Ethernet LAN service must be created.
The IGMP Snooping protocol of the bridge must be enabled.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Layer-2
Switching Management > IGMP Snooping Protocol from the Function Tree.
Step 2 Query the information about the router port.
1.
2.
Click Query.
Issue 02 (2010-09-24)
14-269
3.
2.
Click Query.
3.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
The Ethernet LAN service must be created.
The IGMP Snooping protocol of the bridge must be enabled.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
Procedure
Step 1 Select the Ethernet switching board from the NE Explorer. Choose Configuration > Layer-2
Switching Management > IGMP Snooping Protocol from the Function Tree.
Step 2 Click the Multicast Aging Time tab.
Step 3 Modify the aging time of the multicast table item.
14-270
Issue 02 (2010-09-24)
Parameters
Parameter
Value Range
Default Value
Description
Multicast Aging
Time (Min)
1-120
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select the Ethernet data board. Choose Configuration > Layer-2 Switching
Management > IGMP Snooping Protocol from the Function Tree.
Step 2 Click the Multicast Router Port Management tab.
Step 3 Click Query to query the multicast router ports.
----End
14-271
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select the Ethernet data board. Choose Configuration > Layer-2 Switching
Management > IGMP Snooping Protocol from the Function Tree.
Step 2 Click the Static Multicast Table tab. Click New to display the Create Static Multicast Item
dialog box.
Step 3 Configure the parameters of the static multicast item.
Step 4 Click OK or Apply.
----End
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select the Ethernet data board. Choose Configuration > Layer-2 Switching
Management > IGMP Snooping Protocol from the Function Tree.
Step 2 Select the Multicast Table Item tab.
Step 3 Click Query.
----End
Issue 02 (2010-09-24)
Packets
transmitted out
of the interface
Queue
FIFO
Out-of-queue
grooming
Issue 02 (2010-09-24)
14-273
All packets to be transmitted through this interface enter the tail of the FIFO queue according
to the sequence of their arrival at the interface. The interface transmits these packets from the
head of the queue. The packets are not differentiated during the transmission, and the quality of
packet transmission is not guaranteed.
Figure 14-77 uses the PQ to support QoS packet transmission.
Figure 14-78 SP queue
Packets to be
transmitted through
the interface
Classification
Queue
Priority
Queue 8
Highest
Queue 7
High
Queue 6
Low
Packets
transmitted out
of the interface
Out-of-queue
grooming
...
Queue 1 Lowest
After packets arrive at the interface, the packets are classified first and then enter the tail of a
queue according to the classification. The interface transmits the packets in the queue with high
priority first, and then transmits the packets in the queue with low priority. In this way, the
packets with higher priority are always transmitted first and these packets have a short delay. In
addition, the performance specifications of these packets, including the packet loss ratio and the
delay jitter, can also be guaranteed.
The Ethernet switching board provides the following QoS functions: flow classification,
committed access rate (CAR), class of service (CoS), and traffic shaping. These functions
comply with IEEE 802.1p, RFC 2697, RFC 2698, RFC 2309, RFC 2597, and RFC 2598.
Issue 02 (2010-09-24)
14.7.2.3 CoS
By using the CoS, the packets in a flow can be scheduled to different queues of different priorities
and can be processed according to the priority of each queue. This ensures that the packets of
different priorities can be processed according to different QoS requirements.
14.7.2.4 Traffic Shaping
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. The Ethernet switching board shapes the irregular
traffic or the traffic that does not conform to the specified traffic characteristics based on the
generic traffic shaping (GTS) technology.
Port flow
The packets from a certain port are classified as a type of flow. The associated Ethernet
service of this flow type is the line service that uses this port as the service source. The
Layer 2 switching service can also be classified as a port flow.
14.7.2.2 CAR
CAR is a type of traffic policing technology. After the flow classification, the CAR assesses the
rate of the traffic in a certain period (including the rate in the long term and in the short term).
The CAR sets the packet whose rate does not exceed the specified rate to high priority and
discards the packet whose rate exceeds the specified rate or downgrades this type of packet, thus
restricting the traffic into the transmission network.
The Ethernet switching board processes the flow whose CAR feature is enabled as follows:
Issue 02 (2010-09-24)
14-275
When the rate of packets is not more than the set committed information rate (CIR), these
packets pass the restriction of the CAR and are forwarded first even in the case of network
congestion.
When the rate of packets exceeds the set peak information rate (PIR), the packets whose
rate is higher than the PIR are directly discarded.
When the rate of packets is higher than the CIR but is not higher than the PIR, the packets
whose rate is higher than the CIR can pass the restriction of the CAR and are colored yellow,
which enables these packets to be discarded first in case of network congestion.
When the rate of packets that pass the restriction of the CAR is not higher than CIR in a
certain period, certain packets can burst and these packets can be forwarded first even in
case of network congestion. The maximum traffic of burst packets is determined by the
committed burst size (CBS). The CBS contains two parts: fixed part and variable part. The
fixed part is determined by the CIR and the variable part is set on the NM.
When the rate of the packets that pass the restriction of the CAR is higher than the CIR but
is not higher than the PIR, certain packets can burst and are marked yellow, which enables
these packets to be discarded first in case of network congestion. The maximum traffic of
burst packets is determined by the maximum burst size (MBS). The MBS contains two
parts: fixed part and variable part. The fixed part is determined by the PIR and the variable
part is set on the NM.
NOTE
The CIR and PIR of IDU 605 1F/2F must be set to be the same and the CBS and PBS cannot be set.
14.7.2.3 CoS
By using the CoS, the packets in a flow can be scheduled to different queues of different priorities
and can be processed according to the priority of each queue. This ensures that the packets of
different priorities can be processed according to different QoS requirements.
Each port on the Ethernet switching board EMS6 that is supported by the IDU 620 provides
eight outgoing queues with the CoS priorities from 0 to 7. If the traffic shaping feature of all the
queues is enabled or disabled, the queue with CoS priority 7 is a strict priority (SP) queue, and
the other queues with CoS priorities 0 to 6 are weighted round robin (WRR) queues. The weight
proportion of these WRR queues (with priorities from 0 to 6 respectively) is 1:2:4:8:16:32:64.
If the traffic shaping feature of certain queues is enabled, according to the preset CIR, bandwidth
is allocated first to the queue whose traffic shaping feature is enabled. By using the SP + WRR
algorithm, the remaining bandwidth is allocated to the queues whose traffic shaping is disabled.
The Ethernet port on the IFH2 board that is supported by the IDU 620 provides four outgoing
queues. The corresponding CoS priorities are 0-3 respectively and the queue scheduling mode
is SP. The higher the CoS priority, the higher the queue priority. The IFH2 board supports only
the CoS type of VLAN priority. The data frames that do not carry the VLAN tag are scheduled
to the queue with the lowest priority by default.
The Ethernet port on the IDU 605 1F/2F provides four outgoing queues. The corresponding CoS
priorities are 0-3 respectively. The higher the CoS priority, the higher the queue priority. The
queue scheduling mode is SP or WRR (the weight proportion is 1:2:4:8). These two scheduling
modes cannot be used at the same time.
Table 14-58 lists the CoS types that are supported by the equipment.
14-276
Issue 02 (2010-09-24)
Description
IDU 620
EMS6
IFH2
Simple
Supports
Does not
support
Does not
support
VLAN priority
Supports
Supports
Supports
DSCP
Supports
Does not
support
Supports
NOTE
In the case of the simple type, the maximum number of CoSs supported by the EMS6 board is 8. In the
case of the VLAN priority type, the maximum number of CoSs supported by the EMS6 board is 6. In the
case of the DSCP type, the maximum number of CoSs supported by the EMS6 board is 6.
The EMS4 board (a logical board) that is used on the IDU 605 1F/2F supports one board-level CoS.
14-277
traffic or the traffic that does not conform to the specified traffic characteristics based on the
generic traffic shaping (GTS) technology.
In the case of the port queue whose traffic shaping feature is enabled, the Ethernet switching
board processes the packets as follows before they enter the queue:
l
When the rate of the packets is not more than the set CIR, these packets directly enter the
egress queue.
When the rate of the packets is more than the set PIR, these packets enter the buffer. When
the buffer overflows, the packets are discarded.
When the rate of the packets is more than the CIR but not more than the PIR, the packets
whose rate is more than the CIR enter the buffer of the CIR. When the buffer overflows,
these packets are marked yellow and enter the egress queue. In this case, these packets are
discarded in the case of queue congestion.
When the rate of the packets that pass the restriction of the traffic shaping in a certain period
is not more than the CIR, certain burst packets enter the egress queue. The maximum traffic
of the burst packets is determined by the CBS. The value of the CBS is determined by the
CIR, and cannot be set.
When the rate of the packets that pass the restriction of the traffic shaping in a certain period
is more than the CIR but not more than the PIR, certain burst packets enter the buffer of
the CIR. The maximum traffic of the burst packets is determined by the MBS. The value
of the MBS is determined by the PIR, and cannot be set.
As is evident from the preceding processing mechanism, the difference of the traffic shaping
from the CAR is as follows:
l
In the processing of the CAR, the packet that does not conform to the traffic characteristics
is downgraded in priority or directly discarded.
In the processing of the traffic shaping, the packet that does not conform to the traffic
characteristics is stored in the buffer. The packet is downgraded in priority or directly
discarded only when the buffer overflows.
14.7.3 Availability
The QoS feature requires the support of the applicable equipment and boards.
Table 14-59 Availability of the QoS Feature
Feature
QoS
Traffic classification
CAR
CoS
14-278
Applicable Board
Applicable
Equipment
EMS6, EFP6
IDU 620
EM4T
IDU 605
EMS6, EFP6
IDU 620
EM4T
IDU 605
EMS6, EFP6
IDU 620
EM4T
IDU 605
IFH2
IDU 620
Issue 02 (2010-09-24)
Feature
Traffic shaping
Applicable Board
Applicable
Equipment
EMS6, EFP6
IDU 620
14.7.5.1 CAR
The CAR uses the dual token bucket three color marker algorithm.
...
Tokens
Packets that
leave this port
Classification
Token bucket
Issue 02 (2010-09-24)
14-279
In this algorithm, the token bucket is a container that has a certain capacity for storing tokens.
The tokens are placed into the bucket at a specified rate. When the number of tokens in the bucket
exceeds the capacity of the bucket, the number of tokens no longer increases. A token indicates
certain packet traffic. When the packets are transmitted, certain tokens are removed from the
buckets according to the length of the packet. When the number of tokens that are stored in the
token bucket cannot support the transmitting of the packets, these packets are discarded or
processed in another way. When the token bucket is filled with tokens, the packets that are
represented by these tokens can be transmitted, which allows the transmission of the burst data.
Hence, the traffic of the burst packets is determined by the capacity of the bucket.
...
...
PIR
Classification
Tp
CIR
Tc
This algorithm uses two token buckets Tc and Tp, and marks colors for packets according to the
situations when these packets pass the token bucket.
NOTE
In the case of the EMS6 board, the marked colors are only internal tags and do not change original priorities
of packets.
The packet is placed into the Tc token bucket at the rate of CIR, and the capacity of the Tc
token bucket equals the CBS.
The packet is placed into the Tp token bucket at the rate of PIR, and the capacity of the Tp
token bucket equals the MBS.
14-280
Issue 02 (2010-09-24)
If a packet obtains the Tp token but does not obtain the Tc token, this packet is marked
yellow.
This kind of packet can pass the restriction of the CAR but is discarded first in the case of
network congestion.
If a packet does not obtain the Tp token, this packet is marked red.
This kind of packet is directly discarded.
In the case of the EMS6 board, the marked colors are only internal tags and do not change original priorities
of packets.
Figure 14-81 Basic principle of the algorithm that is used by the traffic shaping
...
...
PIR
Tp
buffer queue
Tp
token bucket
CIR
Tc
buffer queue
Tc
token bucket
This algorithm uses two token buckets Tc and Tp, and places packets into different queues
according to the situations when these packets pass the token bucket.
The parameters of these two token buckets are as follows:
l
The packet is placed into the Tc token bucket at the rate of CIR, and the capacity of the Tc
token bucket equals the CBS.
The packet is placed into the Tp token bucket at the rate of PIR, and the capacity of the Tp
token bucket equals the EBS.
If a packet obtains the Tc token, this packet is directly placed into the egress queue.
If a packet obtains the Tp token but does not obtain the Tc token, this packet is placed into
the Tc buffer queue.
Issue 02 (2010-09-24)
14-281
When the Tc buffer queue overflows, the overflow packet is marked yellow and then enters
the egress queue, which indicates that the packet is discarded first in the case of network
congestion.
l
If a packet does not obtain the Tp token, this packet is placed into the Tp buffer queue.
When the Tp buffer queue overflows, the overflow packet is directly discarded.
Basic Concepts
Port available bandwidth: The system allocates bandwidth to a port.
l
For an external Ethernet port, the port available bandwidth is determined by the working
mode of the port. For example, if the working mode of a port is 1000M full duplex, the
available bandwidth of the port is 1000 Mbit/s.
For a VCTRUNK port, the available bandwidth is determined by the total bandwidth of
the virtual concatenation (VC) paths that is bound to the port virtual concatenation group
(VCG).
Classification
Queue
Priority
Queue 8
Highest
Queue 7
High
Queue 6
Low
Packets
transmitted out
of the interface
Out-of-queue
grooming
...
Queue 1 Lowest
The SP queue scheduling algorithm is designed for key service applications. A key service must
be processed with the highest priority when congestion occurs so that the response delay can be
shortened. This is an important feature for a key service. For example, a port provides eight
outgoing queues, which are prioritized from 7 to 0 in a descending order.
During the SP queue scheduling, packets are transmitted in a descending order of priority. When
a queue with a higher priority is empty, the packets in the queue with a lower priority can be
transmitted. In this way, if packets of key service are put into queues with high priority and
packets of non-key services (such as E-mail service) into queues with lower priority, the packets
14-282
Issue 02 (2010-09-24)
of key service can be sent first and the packets of non-key service are sent when the data of key
service is not processed.
The disadvantage of the SP scheduling algorithm is as follows: if there are packets existing in
the queues with high priority when congestion occurs, packets in the queues with low priority
cannot be transmitted all the time.
Queue
Classification
Packets
transmitted out
of the interface
Weight
Queue 4
50
Queue 3
30
Queue 2
10
Queue 1
10
Out-of-queue
grooming
The WRR scheduling algorithm divides each port into several outgoing queues and schedules
the packets in these queues in turn. This ensures that each queue obtains a certain service period.
For example, a port provides four queues. In a descending order of priority, the WRR configure
the w3, w2, w1, and w0 weights for the four queues respectively. Each weight stands for the
proportion of resources that the relevant queue can obtain from the total resources. If this port
is a 100M port and the weights of its four queues are set to 50, 30, 10, and 10 (corresponding to
w3, w2, w1, and w0 respectively) by the WRR scheduling algorithm, then a minimum of 10
Mbit/s bandwidth is guaranteed for the queue with the lowest priority. This prevents the
disadvantage that in the SP queue scheduling, packets in the queues with lower priority may fail
to obtain service for a long time.
Another advantage of WRR scheduling is that, although scheduling of multiple queues is
performed in the polling manner, time segment allocated to each queue is not fixed. That is,
when a queue is empty, the packets of the next queue are scheduled immediately. In this way,
the bandwidth resources can be fully utilized.
14-283
Queue 8
Classification
Weight
Strict priority
Queue 7
64
Queue 6
32
Egress
scheduling
...
Queue 1
Queue 8 (whose CoS value is 7) uses the SP algorithm. When there are packets existing in
this queue, these packets are transmitted first. When there is no packet existing in this queue,
the packets in other queues can be transmitted.
Service time segment is allocated to each queue of queues 1-7 (whose CoS values 0-6
respectively) according to the weight proportions 1:2:4:8:16:32:64, and at each time
segment the packets in the corresponding queue are transmitted. If there is no packet
existing in the queue that corresponds to a time segment, this time segment is neglected
and the packets in the queue that corresponds to the next time segment are transmitted. For
example, if the port that supports four queues is used as an example and the four queues
are weighted as follows: 1:2:4:8, the WRR allocates the service time segments in the form
of cyclic sequence with a period 432443414342434.
If the traffic shaping of some queues is enabled, according to the set CIR, the bandwidth is first
allocated to the queue whose traffic shaping is enabled. By using the preceding algorithm, the
remaining bandwidth is allocated to the queue whose traffic shaping is disabled. For example,
the traffic shaping of queues 5 and 7 is enabled, the preset CIR of both queues is 10 Mbit/s, and
the total port bandwidth is 25 Mbit/s. In this case, the service time segments are allocated to
queue 5, queue 7, and the remaining queues according to the WRR algorithm in which the weight
proportion is 10:10:5. When a service time segment corresponding to the collection of the
remaining queues arrives, this service time segment is allocated to the remaining queues based
on the SP + WRR algorithms. That is, this service time segment is first allocated to queue 8, and
then is allocated to queues 1, 2, 3, 4, and 6 according to the weight proportion 1:2:4:8:32 of these
queues.
When congestion occurs on the outgoing queues, the packet that is colored yellow in the CAR
or in the traffic shaping is first discarded.
14-284
Issue 02 (2010-09-24)
Prerequisite
l
You must know the type and specific situation of the Ethernet service that requires the QoS
application.
Procedure
Step 1 Select the proper QoS function according to the requirement.
Adhere to the following principles when selecting the QoS function:
l First select the CAR. This can control the service traffic on the ingress side.
l In the case of the important service that requires to improve the traffic fluctuation, select the
traffic shaping function.
l If differentiated services are required for different service types or different user classes,
select the CoS function.
Step 2 Optional: Plan the CAR.
Adhere to the following principles when planning the CAR:
l Bind a CAR to a flow. Do not bind a CAR to multiple flows.
l The sum of CIRs of all the CARs that are associated with a particular PORT or VCTRUNK
should not exceed the physical bandwidth of that particular PORT or VCTRUNK.
Step 3 Optional: Plan the traffic shaping and CoS.
Adhere to the following principles when planning the traffic shaping and CoS:
l Allocate the service of low delay or the service of low delay commitment (such as the
signaling data, VoIP data, and network management protocol packet) into the queues of strict
priority.
l Allocate the service that does not require low delay or that does not provide low delay
commitment (such as the Internet service) into the WRR queue.
l The sum of CIRs of all the queues that are associated with a particular PORT or VCTRUNK
should not exceed the physical bandwidth of that particular PORT or VCTRUNK.
l Plan the parameters of the traffic shaping according to the traffic characteristics, thus
preventing the buffer from overflowing frequently.
----End
14-285
the packet whose rate exceeds the specified rate or downgrades this kind of packet, thus
restricting the traffic into the transmission network.
14.7.7.3 Creating the CoS
By using the CoS, the packets in a flow can be scheduled to different queues of different priorities
and can be processed according to the priority of each queue. This ensures that the packets of
different priorities can be processed according to different QoS requirements.
14.7.7.4 Binding the CAR/CoS
To enable the CAR or CoS function, bind the corresponding flow to the created CAR/CoS.
14.7.7.5 Configuring the Traffic Shaping
The traffic shaping can restrict the traffic and burst of a connection in a network, and thus enables
the packets to be transmitted at an even rate.
14.7.7.6 Configuring the CoS of the IFH2 Board
The IFH2 board supports scheduling packets into different queues according to the
corresponding user priority levels in the VLAN tags.
14.7.7.7 Setting the Queue Scheduling Mode
The IDU 605 1F/2F supports the setting of the board-level queue scheduling mode of the EMS4
board (a logical board).
14.7.7.8 Creating a Flow by Using a Template
This topic describes how to create a flow by using a template. The use of a template improves
the efficiency of creating a flow.
14.7.7.9 Modifying CAR Parameters
The committed access rate (CAR) is the traffic policing technology that is used to check the
traffic rate within a specific period (a long time or short time) after the flow classification. The
CAR allocates the packets whose rates do not exceed the rate limit of the packets of higher
priority, and discards or downgrades the packets whose rates exceed the rate limit. In this process,
restriction of the service access to the transport network is realized. That is, you can adjust the
rate limit by adjusting the parameters such as the committed information rate and the peak
information rate.
14.7.7.10 Modifying CoS Parameters
The class of service (CoS) schedules packets into different priority queues and processes the
packets according to the priority levels of the specific queues. Modifying the CoS parameters
may affect the priority of the egress packets.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
The associated Ethernet service must be created.
14-286
Issue 02 (2010-09-24)
Context
This topic describes how to create a flow without a QoS template. For details of how to create
a flow by using a QoS template, see14.7.7.8 Creating a Flow by Using a Template.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board), which
supports the creation of port flow only.
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoS
Management > Flow Management from the Function Tree.
Step 2 Click the Flow Configuration tab.
Step 3 Click New.
The New Flow dialog box is displayed.
Step 4 Set the flow parameters.
Issue 02 (2010-09-24)
14-287
Parameters
Parameter
Value Range
Default Value
Description
Flow Type
Port Flow
Port
PORT1-PORT6,
VCTRUNK1VCTRUNK8
(EMS6)
PORT1
PORT1-PORT4
(EMS4)
VLAN ID
1-4095
C-VLAN
1-4095
14-288
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
S-VLAN
1-4095
Postrequisite
After creating a flow, bind it to the corresponding CAR or CoS operation as required.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board). In the case
of the EMS4 board, the values of the CIR and PIR should be set the same and the setting of the
CBS and MBS is not supported.
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoS
Management > Flow Management from the Function Tree.
Step 2 Click the CAR Configuration tab.
Step 3 Click New.
The New Car dialog box is displayed.
Step 4 Set the CAR parameters.
Issue 02 (2010-09-24)
14-289
Parameters
Parameter
Value Range
Default Value
Description
CAR ID
1-65535 (EMS6)
Enabled, Disabled
Disabled
Committed Information
Rate (kbit/s)
14-290
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
0-1024
Issue 02 (2010-09-24)
0-1024
14-291
NOTE
a: In the case of the IDU 605 1F/2F, the values of the CIR and PIR should be set the same and the setting
of the CBS and MBS is not supported.
Postrequisite
After creating the CAR, bind the flow to the corresponding CAR operation as required.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board).
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoS
Management > Flow Management from the Function Tree.
Step 2 Click the CoS Configuration tab.
Step 3 Click New.
The New CoS dialog box is displayed.
Step 4 Set the CoS parameters.
14-292
Issue 02 (2010-09-24)
Parameters
Parameter
Value Range
Default Value
Description
CoS ID
1-65535
CoS Type
Issue 02 (2010-09-24)
14-293
Parameter
Value Range
Default Value
Description
CoS Priority
Postrequisite
After creating the CoS, bind the flow to the corresponding CoS operation as required.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
14-294
Issue 02 (2010-09-24)
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board).
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoS
Management > Flow Management.
Step 2 Click the Flow Configuration tab.
Step 3 Bind the CAR/CoS.
Parameters
Parameter
Value Range
Default Value
Description
Bound CAR
Bound CoS
14-295
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoS
Management > Port Shaping Management from the Function Tree.
Step 2 In Port List, select a port.
Step 3 Set the traffic shaping information about the port queue.
Parameters
Parameter
Value Range
Default Value
Description
Port
A specific PORT or
VCTRUNK
Enabled/Disabled
Enabled, Disabled
Disabled
CIR (kbit/s)
An integer ranging
from 0 to 1048574,
with a step of 64
14-296
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
PIR (kbit/s)
An integer ranging
from 0 to 1048574,
with a step of 64
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The IFH2 board must be added in the NE Panel.
Procedure
Step 1 Select the IFH2 board in the NE Explorer. Then, choose Configuration > QoS Management
> Flow Management from the Function Tree.
Step 2 Set CoS Priority for User Priority 0 in the VLAN Tag to User Priority 7 in the VLAN
Tag.
Issue 02 (2010-09-24)
14-297
Parameters
Parameter
Value Range
Default Value
Description
CoS Parameter
CoS Priority
0-3
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoS
Management > Board Shaping Management from the Function Tree.
Step 2 Select a board-level Queue Scheduling Mode.
Step 3 Click Apply.
----End
14-298
Issue 02 (2010-09-24)
Parameters
Parameter
Value Range
Default Value
Description
Queue Scheduling
Mode
WRR, SP
SP
Prerequisite
You must be an NM user with "NE operator" authority or higher.
A QoS template must be created.
Context
When you create a flow by using a template, the CAR is automatically bound with the flow.
Procedure
Step 1 Select the Ethernet switching board in the NE Explorer. Choose Configuration > QoS
Management > Flow Management from the Function Tree.
Step 2 Click the Flow Configuration tab.
Step 3 Click Quick New QoS.
Step 4 In the dialog box that is displayed, specify parameters, such as Flow Type.
Step 5 Select a QoS template that is created.
NOTE
After you modify the values of the parameters in the template and click Save Parameters, the new values
are saved to the template.
14-299
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
The CAR must be configured.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board). In the case
of the EMS4 board, the values of the CIR and PIR should be set the same and the setting of the
CBS and MBS is not supported.
Procedure
Step 1 Select the target Ethernet switching board in the NE Explorer. Then, choose Configuration >
QoS Management > Flow Management from the Function Tree.
Step 2 Click the CAR Configuration tab.
Step 3 Click Query.
Step 4 Select CAR ID that needs to be changed.
Step 5 Modify the other parameters that need to be modified.
Parameters
For details, see 14.7.7.2 Creating the CAR.
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet switching board must be included in the slot layout.
The CoS must be configured.
Precautions
The IDU 620 supports the Ethernet switching board EMS6.
The IDU 605 1F/2F supports the Ethernet switching board EMS4 (a logical board).
Procedure
Step 1 Select the target Ethernet switching board in the NE Explorer. Then, choose Configuration >
QoS Management > Flow Management from the Function Tree.
Step 2 Click the CoS Configuration tab.
Step 3 Click Query.
Step 4 Select the CoS ID that needs to be changed.
Step 5 Select the CoS Parameter that needs to be changed.
Step 6 Modify CoS Priority.
Parameters
For details, see 14.7.7.3 Creating the CoS.
14-301
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The PXC boards and input/output clock source boards must be configured.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Clock
Source Priority from the Function Tree.
Step 2 Click Create.
The Add Clock Source dialog box is displayed.
Step 3 Select the clock sources.
TIP
By pressing the Ctrl key, you can select multiple clock sources at one time.
Issue 02 (2010-09-24)
Parameters
Parameter
Value Range
Default Value
Description
Clock Source
2 Mbit/s, 2 MHz
External Clock
Source Mode
2 Mbit/s
Synchronization
Status Byte
SA4-SA8
SA4
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Issue 02 (2010-09-24)
14-303
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock Source
Priority from the Function Tree.
Step 2 Set Use the clock source of the data port.
Step 3 Click Apply.
----End
Parameters
Parameter
Value Range
Default Value
Description
Yes, No
No
14-304
Issue 02 (2010-09-24)
15
Issue 02 (2010-09-24)
15-1
Service availability, which indicates the ensured normal running time of a service.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
Delay, which indicates the period between transmission and receiving of data packets
between two reference points.
Jitter, which indicates the time interval difference for the receive side to receive a group of
data packets transmitted on the same route.
Packet loss rate, which indicates the maximum ratio of discarded data packets among the
transmitted data packets in the network. Data packets are discarded mainly due to network
congestion.
15-3
15.1.2.1 DiffServ
As an end-to-end QoS control model, the DiffServ can be simply realized and easily extended.
Figure 15-1 shows the application of the DiffServ model.
Figure 15-1 Networking diagram for the DiffServ model
DS node
Non-DS node
DS node
DS node
Non-DS node
The DS (DiffServ) domain consists of a group of network nodes (DS nodes) that provide the
same service policy and realize the same PHB (per-hop behavior).
The DS nodes are classified into edge DS nodes and internal DS nodes. The edge DS nodes
classify the traffic that enters the DS domain. For the service traffic of different types, different
PHB service levels are marked. The internal DS nodes control the flow according to the PHB
service level.
As a node in the DS domain, the RTN equipment uses the following technologies to realize the
end-to-end QoS control.
Flow Classification
The RTN equipment supports two flow classifying schemes, that is, simple flow classification
and complex flow classification.
l
CAR Control
Committed access rate (CAR) is used at the access side of the RTN equipment to perform dualrate three-color management for the accessed traffic.
15-4
Issue 02 (2010-09-24)
In normal cases, when the traffic is lower than the committed information rate (CIR), packets
are marked green and normally pass. When the traffic is higher than the CIR and lower than the
peak information rate (PIR), the packets that exceed the CIR are marked yellow and normally
pass. When the traffic exceeds the PIR, the packets that exceed the PIR are marked red and are
directly discarded.
The RTN equipment supports two colorizing modes, that is, color-blind and color-aware. The
difference between the two modes lies in that the current colors of packets should be considered
in the case of the color-aware mode. The RTN equipment supports the configuration of
processing methods for packets with different colors.
Congestion Management
When network congestion occurs or aggregates, specific packet discarding policies are used to
ensure the QoS of services of higher priorities.
Three common packet discarding policies are available.
l
The RTN equipment supports the tail drop policy and the WRED policy. In addition, it supports
the configuration of discarding starting point and discarding rate of the WRED.
Queue Scheduling
In the case of congestion, the RTN equipment provides the ensured QoS for services at the higher
service level by using different queue scheduling schemes. The RTN uses two queue scheduling
schemes, that is, priority queuing (PQ) and weighted fair queuing (WFQ).
Table 15-1 lists the features and application of the two queue scheduling schemes.
Issue 02 (2010-09-24)
15-5
Basic Concept
Scheduling Feature
RTN Application
PQ
WFQ
NOTE
For queues of the lowest priorities, which carry BE packets, the QoS is not ensured. In the case of
congestion, the RTN equipment does not schedule queues that provide this service level (BE).
15.1.2.2 HQoS
When used as an edge DS node, the RTN equipment supports hierarchical QoS (HQoS).
To increase the QoS control efficiency in the network, the HQoS control is always realized at
edge nodes in the network and only simple QoS processing is performed at internal nodes in the
network.
As an edge DS node, the RTN equipment provides multi-layer QoS function points to realize
the HQoS control function.
Compared with the traditional QoS, the HQoS provided by the RTN equipment has the following
advantages.
15-6
The hierarchical scheduling mechanism is used to realize the scheduling based on port,
service, PW or QinQ link. In this way, the QoS control granularities are further divided.
The hierarchical flow control mechanism is used to control the traffic based on port, service,
PW or QinQ link. In this way, the service QoS can be fully controlled.
The WFQ and WRED policies can be configured to increase the flexibility of the QoS
control.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
Figure 15-2 shows where the HQoS function points are and how the QoS processing is
performed.
Figure 15-2 HQoS function points and corresponding QoS processing
Acce s s s ide
QoS function
point
QoS
ma na ge me nt
Port
Apply
port
policy
Ne twork s ide
V-UNI
Apply
V-UNI
ingrees
policy
Apply
V-UNI
egrees
policy
Control
V-UNI
group
bandwidth
PW/QinQ
Apply PW
policy /
Control PW
bandwidth
Apply
QinQ
policy
Tunnel
Control
tunnel
bandwidth
Port
Apply
port
policy
Service flow
15-7
First the RTN equipment establishes the mapping relation between the service priority and PHB
forwarding type.
Then the RTN equipment can use the following QoS polices to realize the end-to-end QoS
control.
l
Table 15-2 Table for mapping relations between the RTN equipment and the supported QoS
policies
Port
Policy
V-UNI
Ingres
s
Policy
V-UNI
Egress
Policy
PW
Policy
QINQ
Policy
ATM
Policy
WFQ
Sched
uling
Policy
WRED
Policy
RTN
910
Support
ed
Not
support
ed
Not
support
ed
Not
support
ed
Not
support
ed
Suppor
ted
Support
ed
Support
ed
RTN
950
Support
ed
Not
support
ed
Not
support
ed
Not
support
ed
Not
support
ed
Suppor
ted
Support
ed
Support
ed
Prerequisite
l
15-8
Issue 02 (2010-09-24)
You must complete the configuration of the control plane on the RTN equipment.
Context
As a node in the DiffServ domain, the RTN equipment supports creating the DiffServ domain
according to the physical ports. Each RTN NE supports a maximum of eight DiffServ domains.
By default, there is a DiffServ domain for the RTN equipment. Before any DiffServ domain is
created, all ports belong to this default domain.
To create a DiffServ domain, perform the following operations.
l
Create mapping relations in the DiffServ domain, which include the mapping relation
between the priorities of user packets in both the ingress and egress directions, and the PHB
service levels.
Configure the physical ports that use the mapping relations, that is, add the physical ports
to this domain.
Table 15-3 lists the service quality that corresponds to the PHB service level.
Table 15-3 PHB service level and mapping PHB service quality
PHB Service
Level
BE
AF1
The service traffic is allowed to exceed the specified range. For the
traffic within the specified range, forwarding quality is ensured. For
the traffic beyond the specified range, the forwarding quality is lowered
and such traffic is not simply discarded.
This PHB service level is applicable for transmission of multimedia
services.
Each AF level is further divided into three discarding priorities (color).
For example, the AF1 level is further divided into the following
discarding priorities.
l AF11, green priority. Traffic with this priority can normally pass.
l AF12, yellow priority. Packets with this priority are discarded in
the case of congestion according to requirements.
l AF13, red priority. Packets with this priority are discarded first.
AF2
AF3
AF4
EF
CS6
CS7
Issue 02 (2010-09-24)
15-9
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > DiffServ
Domain Management from the Function Tree.
Step 2 Click Create. The Create DS Mapping Relation dialog box is displayed. Set the following
parameters in the dialog box.
l ID and name of the DS domain mapping relation, and mapping packet type.
l Mapping relation between priorities of ingress and egress packets, and the PHB service level.
(When no configuration is performed, the mapping relation recommended by the system is
used.)
NOTE
Regarding the DSCP priority, if the DSCP value is not within the range specified in the Ingress
Mapping Relation table, the PHB service level is BE.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
The default DiffServ cannot be modified or deleted.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > DiffServ
Domain Management from the Function Tree.
Step 2 Select the DiffServ domain to be modified. For a DiffServ domain, the following parameters
can be modified.
15-10
Issue 02 (2010-09-24)
l Modify the name of the domain mapping relation, and then click Apply.
l In the Ingress Mapping Relation tab, modify the mapping relation, and then click Apply.
l In the Egress Mapping Relation tab, modify the mapping relation, and then click Apply.
l In the Apply Port tab, click Modify. In the displayed Config Ports dialog box, modify the
applied port. Then, click OK.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
l
To delete a DiffServ domain, first delete the ports involved in the DiffServ domain, and
then delete the mapping relations in the DiffServ domain. If the DiffServ domain contains
any port, the mapping relations cannot be successfully deleted.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > DiffServ
Domain Management from the Function Tree.
Step 2 Select the DiffServ domain to be deleted. Click Modify in the Apply Port tab. The Config
Ports dialog box is displayed.
Step 3 All ports chosen in this domain are deleted. Click OK.
Step 4 Click Delete in the Ingress Mapping Relation tab. The Confirm dialog box is displayed, Click
OK.
----End
15-11
Prerequisite
l
When a physical port is configured with both the port policy and UNI ingress policy, only the UNI ingress
policy functions. Configuring one physical port with both the port policy and UNI ingress policy is not
recommended.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy
Management from the Function Tree.
Step 2 Click the Port Policy tab. Click New in the tab. The Create Port Policy dialog box is displayed.
Set the following parameters in the dialog box.
l Policy ID , Policy Name.
Step 3 In the Create Port Policy dialog box, click OK.
Step 4 Select the port policy created. Click the Applied Object tab, and then click Modify.
Step 5 In the displayed Configure Port dialog box, select the port to be applied, and then click OK.
NOTE
The OptiX RTN 910/950 supports the port policy at the ML-PPP port.
----End
Related Operation
Use the copy function to fast create a new port policy based on the created port policy. The
detailed operation is as follows:
1.
In the Port Policy tab, click Copy. In the displayed Duplicate QoS Policy dialog box,
select the policy to be copied, and then enter the new policy name. Then, click OK.
2.
Modify the related parameters of the newly created policy, and then make the new policy
meet the QoS requirement.
NOTE
l For the method of modifying the port policy, see 15.1.5.2 Modifying the Port Policy.
l In the case of the copy function, the application policy of port can not be copied.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The policy is not applied.
15-12
Issue 02 (2010-09-24)
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy
Management from the Function Tree.
Step 2 Click the Port Policy tab. In the tab, select the port policy to be modified. The following
parameters can be modified.
l Policy name.
l Parameters of traffic classification bandwidth sharing.
l CoS parameters.
In the CoS Configuration tab, modify the traffic control parameters and packet discarding
policy, and then click Apply.
l Traffic classification rule.
Click the Traffic Classification Configuration tab.
Select the traffic classification rule to be modified, and then click Traffic Classification
Rule. In the Traffic Classification Configuration dialog box, modify the traffic
classification rule, and then click OK.
Click New. In the displayed Create Traffic Classification dialog box, configure the new
ACL rule, and then click OK.
Select the traffic classification rule to be deleted, and then click Delete.
l Applied port.
Click Applied Object tab, and then click Modify.
In the displayed Configure Port dialog box, modify the applied port, and then click
OK.
----End
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy
Management from the Function Tree.
Step 2 Click the Port Policy tab. In the tab, select the port policy to be deleted.
Step 3 Click Delete.
----End
15-13
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy
Management from the Function Tree.
Step 2 Click the CAR Policy tab.
Step 3 Click New. The Create CAR Policy dialog box is displayed.
Step 4 Set the Policy ID, Policy Name, CAR parameters and Coloration Mode.
Step 5 Set the handing mode of the packet with different color.
Step 6 Click OK.
----End
Issue 02 (2010-09-24)
Modify the V-UNI ingress policy that is successfully created. The policy name, CoS parameters
and traffic classification parameters.
15.1.7.4 Querying the V-UNI Ingress Policy-Applied Object
The created V-UNI ingress policy is applied to a certain service to perform the QoS control. The
RTN equipment supports querying the V-UNI ingress policy-applied objects, including service
ID and V-UNI ID.
15.1.7.5 Deleting the V-UNI Ingress Policy
Delete the V-UNI ingress policy not required. If used by a service, this policy cannot be deleted.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
The default WFQ schedule policy (Policy ID: 1; Policy Name: WFQ Default Scheduling) cannot
be created, modified or deleted.
In the case of the OptiX RTN , the WFQ scheduling policy can be applied to the Port policy.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy
Management > WFQ Schedule Policy from the Function Tree.
Step 2 Click New. The Create WFQ Schedule Policy dialog box is displayed. Set the following
parameters in the dialog box.
l Policy ID and name.
l AF scheduling weight.
NOTE
15-15
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy
ManagementV-UNI Ingress Policy from the Function Tree.
Step 2 Click New. The Create V-UNI Ingress Policy dialog box is displayed.
Step 3 Set the Policy ID and Policy Name.
Step 4 Click New. Then, configure the following attributes in the displayed Create Traffic
Classification dialog box.
Step 5 Set Traffic Classification ID, ACL Action and Logical Relation Between Matched Rules.
NOTE
In the case of OptiX RTN , the default value of ACL Action is Permit and cannot be set.
Logical Relation Between Matched Rules can be set to And or Or.
And indicates that all the traffic classification rules must be followed. Or indicates that just one traffic
classification rule need be followed.
In the case of OptiX RTN , the default value of Logical Relation Between Matched Rules is Or and
cannot be set.
Step 6 Click Add and configure the traffic classification rules. You can set more traffic classification
rules.
NOTE
In the case of OptiX RTN , the match type of the traffic classification rule can be set to CVlan ID or SVlan
ID.
Related Operation
Use the copy function to fast create a new V-UNI Ingress policy based on the created V-UNI
Ingress policy. The detailed operation is as follows:
1.
In the V-UNI Ingress Policy tab, click Copy. In the displayed Duplicate QoS Policy dialog
box, select the policy to be copied, and then enter the new policy name. Then, click OK.
2.
Modify the related parameters of the newly created policy, and then make the new policy
meet the QoS requirement.
NOTE
l For the method of modifying the V-UNI ingress policy, see 15.1.7.3 Modifying the V-UNI Ingress
Policy.
l In the case of the copy function, the application information of the policy can not be copied.
15-16
Issue 02 (2010-09-24)
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy
Management > V-UNI Ingress Policy from the Function Tree.
Step 2 Select the V-UNI ingress policy to be modified.
Step 3 Modify the following parameters.
l Policy name.
l Applied WFQ scheduling policy.
l Traffic classification bandwidth sharing.
Step 4 Modify the CoS parameters.
In the CoS Configuration tab, modify the CoS parameters. Then, click Apply.
Step 5 Modify the traffic classification parameters.
1.
2.
3.
----End
15-17
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy
Management > V-UNI Ingress Policy from the Function Tree.
Step 2 Select the V-UNI ingress policy for the query.
Step 3 Click the Applied Object tab and click Query. Information on the service that uses this policy
is displayed.
----End
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy
Management > V-UNI Ingress Policy from the Function Tree.
Step 2 Select the V-UNI ingress policy to be deleted.
Step 3 Click Delete.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
The OptiX RTN equipment supports the flexible mapping between the ATM service type and
PHB service class. Table 15-4 lists the default ATM CoS mapping relation.
15-18
Issue 02 (2010-09-24)
Table 15-4 Mapping relation between the ATM service type and PHB service class
Service Type
CBR
EF
RT-VBR
AF31
NRT-VBR
AF21
UBR+
AF11
UBR
BE
NOTE
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > QoS Management > Diffserv
domain Management > ATM CoS Mapping Configuration from the Function Tree.
Step 2 Click Create. The Create ATM CoS Mapping Relation dialog box is displayed.
Step 3 Set the following parameters in the dialog box.
l Mapping Relation ID
l Mapping Relation Name
l Mapping between the service type and CoS level
15-19
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy
Management > ATM Policy from the Function Tree.
Step 2 Click New. The Create ATM Policy dialog box is displayed. Set the following parameters in
the dialog box.
l Policy ID and name
l Service type
l Traffic parameter
l UPC/NPC
15-20
Issue 02 (2010-09-24)
NOTE
The service encapsulated in AAL5 is sliced into cells. Enable Traffic Frame Discarding Flag determines
whether to discard cells or to discard the complete AAL5 frames for the cells. When Enable Traffic Frame
Discarding Flag is set to Enabled, the RTN equipment will discards the complete AAL5 frames for the
cells.
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy
Management from the Function Tree.
Step 2 Click the ATM Policy tab and select the ATM policy to be modified. The following parameters
can be modified.
l Policy name.
l Service type.
l ATM traffic parameter.
l Frame discarding label.
l UPC/NPC.
Step 3 Click Apply.
----End
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy
Management from the Function Tree.
Issue 02 (2010-09-24)
15-21
Step 2 Click the ATM Policy tab and select the ATM policy for the query.
Step 3 Click the Applied Object tab and click Query. Information on the service that uses this policy
is displayed.
----End
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > QoS Management > Policy
Management from the Function Tree.
Step 2 Click the ATM Policy tab and select the ATM policy to be deleted.
Step 3 Click Delete.
----End
Issue 02 (2010-09-24)
15-23
PE
Switching Network
B Company
UNI
City1
PE
Switching Network
A Company
A Company
City2
City1
UNI
NNI
NNI
UNI
Issue 02 (2010-09-24)
Hence, the company service accessed at the user side is encapsulated into a PW, and then is
carried by the Tunnel.
Different E-Line services of different companies are carried by different PWs, and then are
transmitted to the same NNI. As a result, the number of NNIs is saved, and the bandwidth
utilization is increased. In the uplink direction of the user side, the hierarchical QoS can be
performed for data packets.
Figure 15-5 UNI-NNI E-Line service carried by a PW
NE 1
A Company
Package Switching
Network
NE2
A Company
B Company
B Company
City1
UNI
NNI
NNI
UNI
City2
Tunnel
PW
Issue 02 (2010-09-24)
15-25
A Company
City1
Packet
Switching
Network
The internal
network of A
Company
VLAN = 1-100
NE2
B Company
A Company
City2
B Company
QinQ Link
The internal
network of B
Company
VLAN = 1-200
15-26
Issue 02 (2010-09-24)
S-VLAN1
S-VLAN3
C-VLAN1
UserA
UserB
UserC
C-VLAN2
S-VLAN2
S-VLAN4
C-VLAN2
UserD
E-LINE B
RTN NE
15-27
FE
FE
NE 1
MPLS Tunnel 1
MPLS Tunnel 2
FE
NE 3
RNC
GE
NE 2
FE
Node B
Issue 02 (2010-09-24)
The service is accessed at the user side, and transported to one PW at the network side for
carrying. In this way, user data can be transparently transmitted in a point-to-point manner. For
such a application, create a UNI-NNI E-Line service carried by a PW.
15.2.2.5 Creating a QinQ Link
The QinQ link indicates that a VLAN is added on the accessed packets by using the QinQ
encapsulation mode. In this way, multiple VLAN packets from the user-side network are
encapsulated into a VLAN in the transport network for transport. The VLAN resources in the
transport network are saved. The E-Line service can be carried by the QinQ link at the network
side.
15.2.2.6 Creating a UNI-NNI E-Line Service Carried by the QinQ Link
The services accessed on the user side are carried by the QinQ link on the network side. Multiple
VLANs of the user network are encapsulated in the QinQ mode into one VLAN in the transport
network. In this way, the VLAN resources in the transport network are saved.
15.2.2.7 Modifying an E-Line Service
For an E-Line service, some attributes can be modified, such as the service name, MTU, userside VLAN and QoS-related parameters. For the PW and QinQ Link that carries the service,
only QoS-related parameters can be modified, such as the overall bandwidth and applied policy
template.
15.2.2.8 Deleting an E-Line Service
When a user-to-network E-Line service carried by a PW is deleted, the PW is also deleted.
Issue 02 (2010-09-24)
Task
Remarks
1. Creating
Network
2. Configure the
QoS Policy
The QoS policy is used for traffic management of the E-Line service.
3. Configure the
user-side
Interface
4. Configure the
UNI-UNI E-Line
Service
15-29
Remarks
1. Creating
Network
2. Configure the
QoS Policy
The QoS policy is used for traffic management of the E-Line service.
3. Configure the
Interface
4. Configure the
UNI-NNI E-Line
Service
15-30
Task
Remarks
1. Creating
Network
2. Configure the
LSR ID
3. Configure the
network-side
interface
Set the general attributes and Layer 3 attributes (tunnel enable status and
IP address) for interfaces to carry the tunnel carrying.
Issue 02 (2010-09-24)
Task
Remarks
4. Configure the
control plane
Set the protocol parameters related to the control plane to create the
tunnel.
l To create a static MPLS tunnel to transmit the E-Line service, the
parameters related to the control plane need not be set.
l To create a dynamic MPLS tunnel to transmit the E-Line service, you
need to set the following protocol parameters:
1. Set the IGP-ISIS protocol parameters.
2. Set the MPLS-RSVP protocol parameters.
To create a dynamic PW to transmit the service, you need to set the
parameters related to the MPLS-LDP protocol and the IGP-ISIS
protocol.
5. Configure the
Tunnel
6. Configure the
QoS Policy
The QoS policy is used for traffic management of the E-Line service.
7. Configure the
user-side
Interface
8. Configure the
UNI-NNI E-Line
service
1. Create an E-Line service: Specify the service ID, name the service,
and set service VLan.
2. Configure a PW: Set the PW type, label, and tunnel type.
3. Configure QoS: Set the QoS of UNI and PW.
Issue 02 (2010-09-24)
Task
Remarks
1. Creating
Network
2. Configure the
QoS Policy
The E-Line policy is used for traffic management of the E-Line service.
15-31
Task
Remarks
3. Configure the
Interface
4. Configure
QinQ Link
Create the QinQ link, and set the ID, board, port, S-VlAN, and QoS
information of the QinQ link.
The QinQ link encapsulates multiple VLAN packets to a VLAN on the
network side for transmission. This saves the VLAN resources on the
network.
5. Configure the
UNI-NNI E-Line
service
Set the service ID, name, VLAN, and QinQ link ID.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
If a port need be exclusively used, disable the DCN function of the port that carries the service.
For details, see 2.14.4.4 Enabling the Port DCN.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Ethernet Service
Management > E-Line Service from Function Tree.
Step 2 Click New. The dialog box is displayed.
Step 3 Set parameters in the dialog box.
NOTE
When BPDU is set to Transparently Transmitted, you cannot set MTU(byte) and VLANs. The
transparently transmitted service does not support configuring the alarm performance, OAM and QoS.
For Direction, select UNI-UNI.
For VLANs, you can set several VLANs. Separate consecutive VLANs with "-", and inconsecutive VLANs
with ",". For example, "1,3,5,8-10".
Step 4 Optional: Click Configure QoS. The Configure QoS dialog box displayed.
Step 5 Optional: Click the UNI tab in the Configure QoS dialog box. Set Default Forwarding
Priority and Default Packet Relabeling Color for ports. Click OK. The New E-Line
Service dialog box is displayed.
Step 6 Click OK. A dialog box is displayed for confirmation.
----End
15-32
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
If a port need be exclusively used, disable the DCN function of the port that carries the service.
For details, see 2.14.4.4 Enabling the Port DCN.
Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > Ethernet Service Management
> E-Line Service from Function Tree.
Step 2 Click New. The New E-Line Service dialog box is displayed.
Step 3 Set parameters in the dialog box.
NOTE
l When BPDU is set to Transparently Transmitted, you cannot set MTU(byte) and VLANs. The
transparently transmitted service does not support configuring the alarm performance, OAM and QoS.
l For Direction, select UNI-NNI.
l For Bearer Type, select Port.
l For VLANs, you can set several VLANs. Separate consecutive VLANs with "-", and inconsecutive
VLANs with ",". For example, "1,3,5,8-10".
Step 4 Optional: Click Configure QoS. The Configure QoS dialog box displayed.
Step 5 Optional: Click the UNI tab in the Configure QoS dialog box. Set Default Forwarding
Priority and Default Packet Relabeling Color for ports. Click OK. The New E-Line
Service dialog box is displayed.
Step 6 Click OK. A dialog box is displayed for confirmation.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
You must complete the creation of the MPLS tunnel that carries PWs.
If a port need be exclusively used, disable the DCN function of the port at the UNI side. For
details, see 2.14.4.4 Enabling the Port DCN.
Issue 02 (2010-09-24)
15-33
Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > Ethernet Service Management
> E-Line Service from Function Tree.
Step 2 Click New. The New E-Line Service dialog box is displayed.
Step 3 Set parameters in the dialog box.
NOTE
l When BPDU is set to Transparently Transmitted, you cannot set VLANs. The transparently
transmitted service does not support configuring the alarm performance, OAM and QoS.
l For Direction, select UNI-NNI.
l For Bearer Type, select PW.
l For VLANs, you can set several VLANs. Separate consecutive VLANs with "-", and inconsecutive
VLANs with ",". For example, "1,3,5,8-10".
Step 4 Click Configure PW. The Configure PW dialog box is displayed. In the dialog box, set PWrelated parameters.
NOTE
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Layer 2 attributes of the port on the QinQ link must be set and the encapsulation mode must
be the QinQ mode.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Service
Management > QinQ Link from the Function Tree.
15-34
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The QinQ link must be created for the network-side ports.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Service
Management > E-Line Service from the Function Tree.
Step 2 Click New. The New E-Line Service dialog box is displayed.
Step 3 Set each parameter in the dialog box.
Issue 02 (2010-09-24)
15-35
l When BPDU is set to Transparently Transmitted, you cannot set MTU(byte) and VLANs. The
transparently transmitted service does not support configuring the alarm performance, OAM and QoS.
l Set Direction to UNI-NNI.
l Set Bearer Type to QinQ Link.
l Select a created QinQ link in QinQ Link ID.
Step 4 Optional: Click Configure QoS. The Configure QoS dialog box displayed.
Step 5 Optional: Click the UNI tab in the Configure QoS dialog box. Set Policy, Default Forwarding
Priority and Default Packet Relabeling Color for ports. Click OK. The New E-Line
Service dialog box is displayed.
Step 6 Click OK. The Operation Result dialog box is displayed, indicating that the operation is
successful. Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
CAUTION
If you modify the E-Line service, the E-Line service may be interrupted.
Procedure
Step 1 Select the NE from NE Explorer. Choose Configuration > Ethernet Service Management >
E-Line Service from Function Tree.
Step 2 Select the E-Line service to be modified. The Service Name and MTU can be modified. After
the modification is complete, click Apply.
NOTE
After the service transmitted in a PW is created, the MTU value of the service cannot be changed. After
the service transmitted through a port or in the QinQ is created, however, the MTU value of the service
can be changed. The reason is as follows: In the case of the service transmitted in a PW, the MTU value
needs to be negotiated when the PW is created and cannot be changed after creation.
Step 3 Click the UNI tab. In the tab, you can modify VLANS of ports. After the modification is
complete, click Apply. A dialog box is displayed for confirmation, click OK.
15-36
Issue 02 (2010-09-24)
Step 4 Click the QoS tab. The QoS-related parameters for the UNI port, PW and QinQ Link can be
modified. After the modification is complete, click Apply. A dialog box is displayed for
confirmation, click OK.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
CAUTION
If you delete the E-Line service, the E-Line service is interrupted.
Procedure
Step 1 Select the NE from NE Explorer. Choose Configuration > Ethernet Service Management >
E-Line Service from the Function Tree.
Step 2 Select the E-Line service to be deleted and click Delete. A dialog box is displayed for
confirmation. Click OK. A dialog box is displayed, indicating that the E-Line service is
successfully deleted. Click Close.
----End
15-37
encapsulated into a VLAN in the transport network for transport. The VLAN resources in the
transport network are saved. The E-Line service can be carried by the QinQ link at the network
side.
15.2.3.4 Creating a UNI-NNI E-Line Service Carried by the QinQ Link
The services accessed on the user side are carried by the QinQ link on the network side. Multiple
VLANs of the user network are encapsulated in the QinQ mode into one VLAN in the transport
network. In this way, the VLAN resources in the transport network are saved.
15.2.3.5 Modifying an E-Line Service
For an E-Line service, some attributes can be modified, such as the service name, and user-side
VLAN.
15.2.3.6 Deleting an E-Line Service
You can delete the existing E-Line services that are not applicable.
Remarks
1. Creating
Network
2. Configure the
QoS Policy
The QoS policy is used for traffic management of the E-Line service.
3. Configure the
user-side
Interface
4. Configure the
UNI-UNI E-Line
Service
15-38
Issue 02 (2010-09-24)
Table 15-10 Tasks for configuring the UNI-NNI E-Line service carried by QinQ Link
Task
Remarks
1. Creating
Network
2. Configure the
QoS Policy
The E-Line policy is used for traffic management of the E-Line service.
3. Configure the
Interface
4. Configure
QinQ Link
Create the QinQ link, and set the ID, board, port, S-VlAN, and QoS
information of the QinQ link.
The QinQ link encapsulates multiple VLAN packets to a VLAN on the
network side for transmission. This saves the VLAN resources on the
network.
5. Configure the
UNI-NNI E-Line
service
Set the service ID, name, VLAN, and QinQ link ID.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
If a port need be exclusively used, disable the DCN function of the port that carries the service.
For details, see 2.14.4.4 Enabling the Port DCN.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Ethernet Service
Management > E-Line Service from Function Tree.
Step 2 Click New. The New E-Line Service dialog box is displayed.
Step 3 Set parameters for the source and sink in the dialog box.
Issue 02 (2010-09-24)
15-39
NOTE
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Layer 2 attributes of the port on the QinQ link must be set and the encapsulation mode must
be the QinQ mode.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Service
Management > QinQ Link from the Function Tree.
Step 2 Click New. The New QinQ Link window is displayed.
Step 3 Set QinQ Link ID, Board, Port and S-Vlan ID.
Step 4 Click OK.
----End
15-40
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The QinQ link must be created for the network-side ports.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Service
Management > E-Line Service from the Function Tree.
Step 2 Click New. The New E-Line Service dialog box is displayed.
Step 3 Set parameters for the source and sink in the dialog box.
NOTE
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
CAUTION
If you modify the E-Line service, the E-Line service may be interrupted.
Procedure
Step 1 Select the NE from NE Explorer. Choose Configuration > Ethernet Service Management >
E-Line Service from Function Tree.
Step 2 Select the E-Line service to be modified. The Service Name, MTU(byte) can be modified. After
the modification is complete, click Apply.
Issue 02 (2010-09-24)
15-41
Step 3 Click the tabs such as UNI. In these tabs, you can modify the parameters such as VLANs,
EXP of ports. After the modification is complete, click Apply. A dialog box is displayed for
confirmation, click OK.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
CAUTION
If you delete the E-Line service, the E-Line service is interrupted.
Procedure
Step 1 Select the NE from NE Explorer. Choose Configuration > Ethernet Service Management >
E-Line Service from the Function Tree.
Step 2 Select the E-Line service to be deleted and click Delete. A dialog box is displayed for
confirmation. Click OK. A dialog box is displayed, indicating that the E-Line service is
successfully deleted. Click Close.
----End
Issue 02 (2010-09-24)
Issue 02 (2010-09-24)
15-43
Start
Optional
Creating Network
Configuring E-LAN
Service
Configuring the
Control Plane
Configuring QinQ
Link
Creating a V-UNI
Group
Configuring an MPLS
Tunnel
Configuring E-LAN
Service
End
Configuring E-LAN
Service
Creating a V-UNI
Group
Creating a V-UNI
Group
End
End
The columns in the figure shows the three sub processes. From left to right, the sub systems
indicate the NNI carried by ports, NNI carried by PWs, and NNI carried by QinQ Link
respectively.
Before configuring the E-LAN service, you should complete configuring network (including 1
Creating NEs, Links, and Topology Subnets, Configuring Inband DCN, Configuring the NE
Time, 3 Configuring Clocks, and Configuring the Equipment-Level Protection), 15.1
Configuring the QoS Policy, and 8.3 Configuring Ethernet Interfaces.
Perform the following operations according to the NNI bearer type.
l
In the case that the operations mentioned above are completed, when the port is set to Bearer
Type, the E-LAN service can be configured.
When the PW is set to Bearer Type, the MPLS tunnel need be configured. See the following
contents according to the MPLS tunnel type.
When the static MPLS tunnel is used, the MPLS tunnel can be configured on a per-NE
basis or by using the trail function. See Creating a Static MPLS Tunnel by Using the
Trail Function and 21.2.2 Creating an MPLS Tunnel. When the static MPLS tunnel
is used, 20 Configuring the Control Plane can be skipped.
15-44
Issue 02 (2010-09-24)
When the dynamic MPLS tunnel is used, see Creating a Dynamic MPLS Tunnel by
Using the Trail Function.
l
If the network side is carried by the QinQ Link, 15.2.4.2 Creating a QinQ Link need be
complete.
When configuring the E-LAN service, see 15.2.4 Configuring an E-LAN Service.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Layer 2 attributes of the port on the QinQ link must be set and the encapsulation mode must
be the QinQ mode.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Service
Management > QinQ Link from the Function Tree.
Step 2 Click New. The New QinQ Link window is displayed.
Step 3 Set QinQ Link ID, Board, Port and S-Vlan ID.
Step 4 Click OK.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
You must complete the correct configuration of the port attributes.
If the port need be exclusively used, disable the DCN function of the port that carries the service.
For the operation steps, see 2.14.4.4 Enabling the Port DCN.
If the service need be carried by a QinQ link, you must configure a QinQ link first.
Issue 02 (2010-09-24)
15-45
CAUTION
l The ML-PPP line should not carry any E-LAN service.
l On the network side, the E-LAN service does not support the LMSP, FRR, MPLS APS, and
LAG protection.
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Ethernet Service
Management > E-LAN Service from the Function Tree.
Step 2 Click New to display the New E-LAN Service dialog box. Then, set Service ID, Service
Name.
NOTE
l Self-Learning MAC Address is set to enabled. When Self-Learning MAC Address is set to enabled,
the bridge supports the MAC address self-learning, the forwarding table items are generated through
the MAC address self-learning. You can also manually configure the static MAC address forwarding
table items.
l MAC Address Learning Mode is set to IVL. IVL indicates the independent VLAN learning. The
forwarding tables for different VLANs are independent from each other. It is acceptable that the MAC
address forwarding tables for different VLANs have the same MAC address.
l Tag Type can be set to C-Awared, S-Awared or Tag Transparent. C-Awared corresponds to the
accessed service packets with one C-VLAN. S-Awared corresponds to the accessed service packets
with one C-VLAN and one S-VLAN. Tag Transparent corresponds to the accessed service packets
without any VLAN.
Step 3 Click OK to display the dialog box, which indicates that the operation is successful. Then, click
Close.
Step 4 Click the UNI tab. Then, click Configuration to display the Configure Port dialog box.
Step 5 In the Available Ports list, select the port. Then, click
Ports list.
Step 6 In the Selected Ports list, set VLANs/CVLAN of the port, and then click OK.
Step 7 Click the NNI tab.
l
If configuring the NNI interface carried by the port, click the Port tab. See Step 4 to Step
6 to add and configure the NNI port. Then, click OK.
If configuring the NNI interface carried by the QinQ link, click the QinQ Link tab.
1.
2.
3.
Click Apply. The Operation Result dialog box is displayed, indicating that the
operation is successful. Click Close,
NOTE
The services carried by the QinQ link can not support to create MP.
Step 8 Click the Split Horizon Group tab. Then, click New to display the New Split Horizon
Group dialog box.
15-46
Issue 02 (2010-09-24)
Step 9 Configure the split horizon group id, and add the interface that need be added into the split
horizon group to the Selected Interfaces pane. Click OK to display the dialog box, which
indicates that the operation is successful. Then, click Close.
Step 10 Click the MAC Address Learning Parameters tab. Set Aging Ability, Aging Time(min),
Address Table Specified Capacity, Address Detection Upper Threshold(%) and Address
Detection Lower Threshold(%).
NOTE
Address Detection Upper Threshold(%) and Address Detection Upper Threshold(%) indicate the
upper threshold and lower threshold of the self-learning capacity. If the upper threshold is crossed, the
equipment reports an alarm. If the lower threshold is crossed, the alarm is cleared.
Step 11 Click Apply. The dialog box is displayed, indicating that the operation is successful. Click
Close.
Step 12 Click the Unknown Frame Processing tab. Set the processing modes for the unicast frames
and multicast frames. The default value is broadcast.
Step 13 Click Apply. The dialog box is displayed, indicating that the operation is successful. Click
Close.
Step 14 Optional: Click the Static MAC Address tab. Manually bind the VLAN ID, MAC Address
and Egress Interface.
NOTE
Set the VLAN ID only when MAC Address Learning Mode is set IVL.
Step 15 Optional: Click the Maintenance Association tab and the MEP Point tab. Set the OAM-related
parameters.
NOTE
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
You must complete the creation of E-LAN services.
Context
After the MAC address blacklist is created on a port that carries the ELAN service, if the
destination MAC or source MAC information carried by a packet enters this port is consistent
with a random MAC address created in the blacklist, this packet is discarded.
NOTE
The MAC address that is added to the static route should not be added to the MAC address of the blacklist.
Issue 02 (2010-09-24)
15-47
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Ethernet Service
Management > E-LAN Service from the Function Tree.
Step 2 In the Disabled MAC Address tab page, select Query to query the added MAC address of the
blacklist.
Step 3 Click New and the Create Disabled MAC Address dialog box is displayed. Set VLAN ID and
MAC Address.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
You must complete the creation of E-LAN services.
Context
The broadcast suppression is enabled on a port that carries the ELAN service. In this case, when
the packets that enter this port are unknown unicast packets, unknown multicast packets, or
broadcast packets, if the traffic exceeds the broadcast suppression threshold set for the port, the
packets that exceeds the bandwidth are discarded.
NOTE
Currently, the equipment supports the broadcast suppression function for the UNI only. The broadcast
suppression function for the NNI is not supported.
15-48
Issue 02 (2010-09-24)
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Ethernet Service
Management > E-LAN Service from the Function Tree.
Step 2 In the UNI tab page, select the corresponding port. Double-click the Enabled Broadcast Packet
Suppression parameter field, and then select Enabled.
Step 3 Double-click the Broadcast Suppression Threshold parameter field, and then set the threshold
value.
Step 4 Click Apply.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
CAUTION
If you modify the E-AN service, the E-LAN service may be interrupted.
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Ethernet Service
Management > E-LAN Service from the Function Tree.
Step 2 Select the E-LAN service to be modified. The service name can be modified. After the
modification is complete, click Apply.
Step 3 Click the UNI tab. Select the port to be modified. Click Configuration. After the attributes are
modified, click OK to return to the UNI tab. Then, click Apply.
Step 4 Click Port in the NNI tab. Click Configuration. After the attributes are modified, click OK to
return to the NNItab. Click Apply.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Issue 02 (2010-09-24)
15-49
Context
CAUTION
If you delete the E-LAN service, the E-LAN service is interrupted.
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Ethernet Service
Management > E-LAN Service from the Function Tree.
Step 2 Select the E-LAN service to be deleted and click Delete. A prompt dialog box is displayed. Click
OK.
----End
15-50
Issue 02 (2010-09-24)
Start
Optional
Creating Network
Configuring a UNIs-UNI
E-AGGR Service for NEs
Configuring a UNIs-NNI
E-AGGR Service for NEs
Creating a V-UNI
Group
Configuring a NNIs-UNI
E-AGGR Service for NEs
End
Creating a V-UNI
Group
End
Configuring the
Control Plane
Configuring an MPLS
Tunnel
Configuring a UNIs-NNI
E-AGGR Service for NEs
Configuring a NNIs-UNI
E-AGGR Service for NEs
Creating a V-UNI
Group
End
The columns in the figure shows the three sub processes, which are for the configuration of a
UNI-UNI E-AGGR service, the configuration of an E-AGGR service carried by ports on the
NNI side, and the configuration of an E-AGGR service carried by PWs on the NNI side from
the left to right.
Before configuring the UNI-UNI E-AGGR service, you should complete configuring network
(including 1 Creating NEs, Links, and Topology Subnets, Configuring Inband DCN,
Configuring the NE Time, 3 Configuring Clocks, and Configuring the Equipment-Level
Protection), 15.1 Configuring the QoS Policy, Configuring Interfaces, 20 Configuring the
Control Plane, and 21 Configuring an MPLS Tunnel. When configuring the E-AGGR service,
see 15.2.5 Configuring an E-AGGR Service.
When the MPLS tunnel is configured, see the following contents according to the MPLS tunnel
type.
l
When the static MPLS tunnel is used, the MPLS tunnel can be configured on a per-NE
basis or by using the trail function. See Creating a Static MPLS Tunnel by Using the Trail
Function and 21.2.2 Creating an MPLS Tunnel.
When the dynamic MPLS tunnel is used, see Creating a Dynamic MPLS Tunnel by Using
the Trail Function.
Issue 02 (2010-09-24)
15-51
Prerequisite
You must be an NM user with "NE operator" authority or higher.
You must complete the correct configuration of port attributes.
You must complete the creation of the MPLS tunnel that carries the PW.
If a port need be exclusively used, disable the DCN function of the port that carries the service.
For detail, see 2.14.4.4 Enabling the Port DCN.
Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > Ethernet Service Management
> E-AGGR Service from the Function Tree.
Step 2 Click New to display the New E-AGGR Service dialog box. Then, configure Service ID,
Service Name and MTU(byte).
Step 3 Click the UNI tab. Then, click Configuration to display the Configure Port dialog box.
Step 4 In the Available Port list, select the desired port and click
Selected Port list.
NOTE
The port of the E-AGGR service does not support the S-Aware attribute.
Step 5 In the Selected Port list, configure Location and VLANs of the port, and then click OK.
NOTE
Location can be set to the source end or the sink end. Multiple source ends can be set, but only one sink
end can be set. Otherwise, the E-AGGR service cannot be correctly configured.
To configure the NNI interface carried by the port, click the Port tab. When adding and
setting the port at the NNI side, see Step 3 and Step 5. Then, click OK.
To configure the NNI interface carried by the PW, click the PW tab. Click New to set
related parameters of the PW. Then, click OK.
NOTE
l For PW Signaling Type, select Dynamic or Static. Dynamic indicates that the LDP signaling is used
to create a PW.
l For PW Type, select Ethernet or Ethernet Tagged Mode.
Step 7 Select VLAN Forwarding Table Item. Click New to display the New VLAN Forwarding
Table Item window to set the forwarding attributes. Then, click OK.
NOTE
The service is forwarded based on VLAN, and thus the forwarding attributes should be set in VLAN
Forwarding Table Item from each source interface to sink interface.
15-52
Issue 02 (2010-09-24)
Step 8 Optional: Click Configure QoS. Set the parameters of the QoS.
l
Click the UNI tab to set Default Forwarding Priority and Default Packet Relabeling
Color.
Step 9 Click OK to display the confirmation dialog box. Then, close the dialog box.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
CAUTION
If you modify the E-AGGR service, the E-AGGR service may be interrupted.
Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > Ethernet Service Management
> E-AGGR Service from the Function Tree.
Step 2 Select the E-AGGR service to modify the service name and MTU. After the modification, click
Apply.
Step 3 Click the UNI tab to select the port to be modified. Click Configuration. After the modification
of attributes, click OK to return to the UNI tab. Then, click Apply.
Step 4 Select the Port tab from the NNI tab. Click Configuration. After the modification of attributes,
click OK to return to the NNI tab. Then, click Apply.
Step 5 Click the QoS tab to modify the UNI port and QoS parameters of the PW. After the modification,
click Apply. A dialog box is displayed for confirmation, click OK.
----End
15-53
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
CAUTION
If you delete the E-AGGR service, the E-AGGR service is interrupted.
Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > Ethernet Service Management
> E-AGGR Service from the Function Tree.
Step 2 Select the E-AGGR service to be deleted and click Delete. A dialog box is displayed for
confirmation. Click OK. The Operation Result dialog box is displayed, indicating that the EAGGR service is successfully deleted. Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The mirror listener port should contain no Ethernet service, and has not be aggregated.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Port Mirroring from the Function
Tree.
Step 2 Click New.
Step 3 In the window is displayed, set Mirror Name, Direction, Mirror Listener Port and Listened
Port.
Step 4 Click OK.
----End
15-54
Issue 02 (2010-09-24)
16
Configuring Cross-Polarization
Interference Cancellation
Issue 02 (2010-09-24)
16-1
Site B
IDU
ODU 1
Service
f1
Service
f2
f1
f1
ODU 1
IDU
Service
H
V
ODU 2
Service
f2
f2
ODU 2
Figure 16-2 Channel configuration in CCDP mode (with the application of the XPIC
technology)
Site A
Site B
IDU
ODU 1
Service
f1
f1
f1
IDU
ODU 1
Service
H
V
Service
f1
Service
f1
ODU 2
ODU 2
16.2 Availability
The XPIC feature requires the support of the applicable equipment and boards.
Table 16-1 Availability of the XPIC feature
16-2
Applicable Board
Applicable Equipment
RTN 620
Issue 02 (2010-09-24)
Applicable Board
Applicable Equipment
IFU2
RTN 910/950
EM6T/F
IFX2
Modem
horizontal
Filter
Decision
Coefficient
control
Cross
interference
Filter
Cross
interference
Filter
Modem
vertical
A/D
Filter
Decision
Vertical
polarization
The transmitter transmits two signals with the same frequency over a horizontal polarization
wave and a vertical polarization wave.
2.
Due to XPD of the antenna and channel degradation, cross-polarization interference exists
in the signals received by the ODU and also in the IF signals transmitted from the ODU to
the IF boards of XPIC.
3.
The XPIC module on the XPIC board receives the IF signal from the ODU and also the IF
signal from the other IF board of XPIC, and processes the IF signals, for example, A/D
conversion.
4.
The XPIC module on the XPIC board controls the coefficient of the feed forward equalizer
filters (FFF) of the two IF signals by using the decision feedback equalizer (DFE). As a
result, after filtering and combination, the interference is cancelled in the two IF signals.
16-3
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The IF boards and the ODUs to which the IF boards are connected must be created.
The XPIC Enabled parameter must be set to Enabled for the IF boards.
Context
l
Relation with the 1+1 Protection Configuration: The two IF boards in an XPIC working
group cannot be configured into one 1+1 protection group, but the two IF boards in different
XPIC working groups can be configured into one 1+1 protection group. Therefore, the four
IF boards in two XPIC working groups can form two 1+1 protection groups.
Relation with the N+1 Protection: Each member of an XPIC working group can work as
the working channel or the protection channel of the N+1 protection.
Relation with the ATPC Feature: The transmit power of the two ODUs that are in an XPIC
working group should be the same if possible. Hence, each of the ATPC parameters (ATPC
enable status, ATPC upper threshold, ATPC lower threshold, and ATPC adjustment)
should be set to the same value for the IFX boards that are in an XPIC working group.
Procedure
Step 1 In the NE Explorer, select the NE and then choose Configuration > Link Configuration from
the Function Tree.
Step 2 Click the XPIC tab.
Step 3 Click New.
Step 4 In the dialog displayed box, Set the parameters for the XPIC workgroup.
For RTN 600 NEs:
16-4
Issue 02 (2010-09-24)
NOTE
l When CCDP is applied to the STM-1 microwave links, the IFX/IFX2 boards must be installed and the
XPIC function must be enabled.
l An XPIC working group must be configured to ensure that the XPIC working group is configured with
the same working mode, transmission frequency, transmit power, and ATPC attributes.
l When the used ODUs support two T/R spacings, ensure that the two ODUs of an XPIC working group
adopt the same T/R spacing.
Postrequisite
Generally, you do not need to configure the IF/ODU information after you configure an XPIC
workgroup. You, however, need to set the T/R spacing used by the ODU in the IF/ODU
Configuration tab page if the used ODU supports two T/R spacings.
Issue 02 (2010-09-24)
16-5
17
Issue 02 (2010-09-24)
17-1
If the RSL at the receive end is lower than the preset ATPC lower threshold, the receiver
notifies the transmitter to increase the transmit power according to the preset ATPC
adjustment step at the transmit end until the RSL is higher than the ATPC lower threshold.
If the RSL at the receive end is higher than the preset ATPC upper threshold, the receiver
notifies the transmitter to decrease the transmit power according to the preset ATPC
adjustment step at the transmit end until the RSL is lower than the ATPC upper threshold.
Table 17-1 provides the ATPC performance of the OptiX RTN 600.
Table 17-1 ATPC performance
ATPC Control Range
Lower Threshold
(dBm)
Upper Threshold
(dBm)
Rated maximum
transmit power + 1.5
dB (SP ODU series)
Rated minimum
transmit power (HP/
SPA/LP ODU series)
Value Range of
the ATPC
Adjustment Step
(dB)
ATPC Adjustment
Speed (dB/s)
1 to 5
10 (when the
adjustment step is set
to 1 dB)
Rated maximum
transmit power (HP/
SPA/LP ODU series)
20 (when the
adjustment step is set
to 2 dB)
30 (when the
adjustment step is set
to a value, which
ranges from 3 dB to 5
dB)
17-2
When the automatic ATPC threshold setting is enabled, the ATPC lower threshold and the
ATPC upper threshold that are manually set do not take effect. The equipment uses the
preset ATPC lower threshold and ATPC upper threshold according to the IF work mode.
When the automatic ATPC threshold setting is disabled, the ATPC lower threshold and the
ATPC upper threshold that are manually set are used.
Issue 02 (2010-09-24)
17.2 Availability
The ATPC feature requires the support of the applicable equipment and boards.
Table 17-2 Availability of the ATPC feature
Applicable Board
Applicable Equipment
RTN 605
RTN 610/620
RTN 620
Applicable Equipment
IF1
IFU2
RTN 910/950
IFX2
Issue 02 (2010-09-24)
17-3
Receiver
2.
After the ATPC function is enabled, when the RSL is lower than the lower ATPC threshold
or higher than the upper ATPC threshold, the receiver sets the ATPC overhead in the
microwave frame to be sent to the transmitter, to indicate an increase or decrease in the
transmit power.
NOTE
To prevent continuous adjustment to ODU power at the transmit end from occupying a large number of
resources, the receiver does not set the ATPC overhead in each microwave frame to indicate an increase
or decrease in the transmit power. Instead, the receiver sets the ATPC overhead every several microwave
frames.
17-4
3.
The transmitter detects the ATPC overhead in the received microwave frame.
4.
When the transmitter detects that the ATPC overhead in a microwave frame indicates an
increase or decrease in the transmit power, the transmitter increases or decreases the
transmit power of the ODU according to the preset ATPC adjustment step.
5.
When the receiver detects that the RSL is within the ATPC adjustment range, the receiver
sets the ATPC overhead in the microwave frame again to make the ATPC overhead indicate
not to adjust the transmit power.
Issue 02 (2010-09-24)
6.
When the transmitter does not detect the ATPC overhead that indicates an increase or
decrease in the transmit power, the transmitter does not change the transmit power of the
ODU.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The related IF board must be added.
Precautions
l
In the case of the IF boards that are configured with the 1+1 protection, set only the ATPC
attributes of the main IF board.
The following procedure describes the configuration of ATPC parameters in the IF interface
configuration dialog box of the IF board. You can also set ATPC parameters in the following
configuration dialog boxes:
Create an XPIC working group
IF/ODU configuration
In the IF/ODU configuration dialog box, the ATPC adjustment thresholds cannot be
modified.
The transmit power of the two ODUs that are in an XPIC working group should be the
same if possible. Hence, each of the ATPC parameters (ATPC enable status, ATPC upper
threshold, ATPC lower threshold, and ATPC adjustment) should be set to the same value
for the IF boards that are in an XPIC working group.
In the case of the Hybrid microwave, the AM switching is controlled through detection of
the change in the ATPC information and returned microwave message.
Procedure
Step 1 In the case of RTN 600 and RTN 900 V100R002 NEs.
1.
Select the IF board from the Object Tree in the NE Explorer. Choose Configuration > IF
Interface from the Function Tree.
2.
3.
NOTE
The IF0 board of the RTN 605 does not support the ATPC Automatic Threshold Enable Status.
4.
Issue 02 (2010-09-24)
Click Apply.
17-5
Step 2 In the case of RTN 900 V1R1 NEs, see Configuring the IF Attributes of Microwave
Interfaces to take the details of configuration.
----End
Parameters
Parameter
Value Range
Default Value
Description
Enabled, Disabled
Disabled
ATPC Upper
Threshold (dBm)
-20 to -75
-45
17-6
Issue 02 (2010-09-24)
Parameter
Value Range
Default Value
Description
ATPC Lower
Threshold (dBm)
-35 to -90
-70
ATPC Automatic
Threshold Enable
Status
Enabled, Disabled
Enabled
Issue 02 (2010-09-24)
17-7
NOTE
l Set ATPC parameters consistent at the two sides of a hop of microwave link.
l During commissioning, set ATPC Enable Status to Disabled to ensure that the transmit power is not
changed. After the commissioning, re-set the ATPC attributes.
l It is recommended that you disable the ATPC function for areas where fast fading is severe.
l To prevent that the RSL is lower than the receiver sensitivity caused by sudden fast fading, set the ATPC
lower threshold 10 dB or more higher than the receiver sensitivity.
l Generally, the ATPC upper threshold should be 20 dB to 30 dB higher than the ATPC lower threshold, and
must not be less than 15 dB. If the difference between the upper threshold and the lower threshold is big,
the number of ATPC adjustments can be reduced and the system load can also be reduced. If the difference
between the upper threshold and the lower threshold is small, the transmit power can be adjusted in a timely
manner and the interference to adjacent systems can be reduced.
l It is recommended that you set the ATPC adjustment step to 5 dB.
l In the case of hybrid radio links, the automatic ATPC threshold is recommended. In the case of SDH/PDH
radio links, the automatic ATPC threshold is recommended or you can make adjustment according to
multipath fading situation.
17-8
Issue 02 (2010-09-24)
18
Issue 02 (2010-09-24)
18-1
Ethernet
E1 OH
E1 OH
E1
E1
MUX
Microwave
frame
MODEM
Transmitter
Receiver
Ethernet
MODEM
Microwave
frame
DMUX
Ethernet
The Hybrid microwave feature of the OptiX RTN realizes optimization for service reliability
and service capacity by using technologies such as combined transmission of E1 services and
Ethernet services, adaptive modulation (AM), and Ethernet QoS control.
Issue 02 (2010-09-24)
condition of the channel. When the AM function is disabled, the Hybrid microwave uses the
working mode that is set by the user.
18.2.4 QoS Control for Ethernet Services
The Hybrid microwave provides various functions to ensure that Ethernet services can meet the
requirements of variable transmission bandwidth due to the application of the AM technology,
and thus to ensure the QoS of services.
The Hybrid microwave frame remains the frame length unchanged in the case of a certain
modulation scheme or bandwidth.
The E1 services that are multiplexed into the Hybrid microwave frame use a certain
proportion of the bandwidth of this Hybrid microwave frame. That is, the bandwidth used
by these E1 services in the Hybrid microwave frame is equal to the total bandwidth of these
E1 services. Hence, characteristics of these E1 services transmitted over Hybrid microwave
frames are the same as the characteristics of the E1 services transmitted over PDH
microwave, and the TDM feature of the E1 services is not affected in the case of Hybrid
microwave transmission.
The Ethernet services that are multiplexed into the Hybrid microwave frame use the
remaining bandwidth of this Hybrid microwave frame. This does not affect the Ethernet
services because the Ethernet frames undergo certain encapsulation and adaptation
processes. See Figure 18-2.
Figure 18-2 Multiplexing E1 services and Ethernet services into the Hybrid microwave frame
T
OH
E1
E1
Ethernet
In the case of E1 services: The equipment accesses E1 services through the E1 service
interface board, SDH/PDH service interface board, microwave IF board, and the E1 service
interface unit in the other directions.
In the case of Ethernet services: The equipment accesses Ethernet services through the FE
interface or GE interface of the Ethernet board, the GE interface of the IF board, or through
the Ethernet interface of the equipment.
18.2.2 AM
The Hybrid microwave supports the AM technology. With the application of the AM technology,
the Hybrid microwave uses the high-efficiency modulation scheme when the channel is of better
quality. Hence, more user services can be transmitted and thus the transmission efficiency and
Issue 02 (2010-09-24)
18-3
spectrum utilization are improved. When the quality of the channel is degraded, the Hybrid
microwave uses the low-efficiency modulation scheme, in which only the services of a high
priority are transmitted. Hence, the anti-interference capability of links is enhanced and
availability of the links on which the high-priority services are transmitted is ensured.
E1 services are of the highest priority in the AM-based Hybrid microwave transmission. Ethernet
services are classified into flows of different priorities based on the CoS technology. When the
Hybrid microwave uses the lowest-efficiency modulation scheme, the equipment transmits E1
services only (if the service bandwidth is higher than the total bandwidth of the E1 services, the
Ethernet services of a high priority can be transmitted). When the Hybrid microwave uses other
modulation schemes, the increased bandwidth can be used to transmit Ethernet services. In this
case, availability of the links on which the E1 services and Ethernet services of a high priority
are transmitted can be ensured and the capacity for transmitting Ethernet services increases.
Figure 18-3 shows the working principle of the Hybrid microwave that uses the AM technology.
Figure 18-3 Working principle of the Hybrid microwave
256QAM
QPSK
16QAM
64QAM
128QAM
256QAM
Channel
capability
E1 services
Ethernet
services
Figure 18-3 shows the transmission mode of the Hybrid microwave. The orange column
represents E1 services, and the blue column represents Ethernet services. When an Ethernet
service is nearer the edge of the column, the priority of this Ethernet service is lower. As shown
in Figure 18-3, the E1 services use a constant bandwidth irrespective of the real-time condition
of the channel. Hence, the availability of E1 services is ensured. The bandwidth of the Ethernet
services is variable depending on the condition of the channel. When the quality of the channel
is degraded, the Ethernet services of a low priority are discarded.
NOTE
When only the Ethernet services are transmitted over the Hybrid microwave, the bandwidth originally used
by the E1 services as shown in Figure 18-3 is allocated to the Ethernet services of a high priority.
18-4
The AM function switches the modulation scheme step by step. The highest-efficiency
modulation scheme and lowest-efficiency modulation scheme can be configured.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
2.
The AM function retains the transmit frequency, receive frequency, and channel spacing
when switching the modulation scheme.
3.
AM Mode is Asymmetric, an AM switching in one direction of the radio link does not
trigger the AM switching in the other direction of the radio link.
Issue 02 (2010-09-24)
Channel Spacing
(MHz)a, b
Modulation Scheme
Service Capacity
(Mbit/s)
Maximum Number
of E1s in servicec
QPSK
10
16QAM
20
10
32QAM
25
12
64QAM
32
15
128QAM
38
18
256QAM
44
21
14 (13.75)
QPSK
20
10
14 (13.75)
16QAM
42
20
14 (13.75)
32QAM
51
24
14 (13.75)
64QAM
66
31
14 (13.75)
128QAM
78
37
14 (13.75)
256QAM
90
43
28 (27.5)
QPSK
42
20
28 (27.5)
16QAM
84
40
28 (27.5)
32QAM
105
50
28 (27.5)
64QAM
133
64
28 (27.5)
128QAM
158
75
28 (27.5)
256QAM
183
75
56
QPSK
84
40
56
16QAM
168
75
18-5
56
32QAM
208
75
56
64QAM
265
75
56
128QAM
313
75
56
256QAM
363
75
40d
64QAM
75
NOTE
1. The channel spacings 13.75 MHz and 27.5 MHz are applied to the 18 GHz frequency band.
2. The channel spacings listed in the table are the minimum channel spacings supported. The channel spacings
larger than the values are also supported.
3. The E1 services consume the corresponding bandwidth of the service capacity. After the E1 service capacity
is deducted from the service capacity, the remaining bandwidth of the service capacity can be used for the
Ethernet services.
4. This modes are the super PDH modes that do not support the transmission of Ethernet services.
When the EMS6 and IFH2 boards are used, the QoS control of the OptiX RTN 620 supports the
following functions in addition to the functions that are supported when only the IFH2 board is
used:
l
Flow classification
The following flow classification modes are supported.
Flow classification based on PORT
Flow classification based on PORT+CVLAN
Flow classification based on PORT+SVLAN
Flow classification based on PORT+CVLAN+SVLAN
18-6
Issue 02 (2010-09-24)
When the bandwidth on the air interface of the OptiX RTN 620 changes, the EMS6 is informed
of this change through the in-band packet so that the EMS6 can control the bandwidth on the
port.
NOTE
For details about the Ethernet QoS, see 14.7 Configuring QoS.
18.3 Availability
The Hybrid microwave feature requires the support of the applicable equipment and boards.
Table 18-2 Availability of the Hybrid microwave feature
Applicable Board
Applicable Equipment
RTN 605
IFH2
RTN 620
Applicable Equipment
RTN 910/950
IFX2
18-7
On the one hand, the AM engine communicates with the remote AM engine through the
information channel that is provided by the radio link so that the transmit end is informed of the
quality of the signals at the receive end.
On the other hand, the AM engine determines the attributes of the modulation scheme that is
switched to, based on the real-time quality of the link. When the switching of modulation scheme
is required, the AM engine sends the AM switching indication signal to the Tx path.
The switching unit grooms services at different priority levels to the IF port on an IF board,
and the multiplexing unit multiplexes the services to microwave frames. E1 services and
Ethernet services are multiplexed to hybrid microwave frames by the multiplexing unit.
NOTE
2.
The hybrid microwave frames are transmitted to the opposite end over the Tx path after
being modulated by the IF unit.
3.
The opposite end receives the IF signals from the Rx path. In addition, the opposite end
checks the quality of the received signals based on the received signal to noise ratio (SNR).
In the current working modulation scheme, the opposite end determines that the quality of
the received signals is degraded if the value of the received SNR is lower than the threshold.
Then, the opposite end sends signal quality indication signal to the AM engine.
4.
The AM engine at the opposite end sends the hybrid microwave frame to the local end after
the switching indication signal is placed into the overhead of the hybrid microwave frame.
5.
The IF unit at the local end processes the received IF signals and sends the AM switching
indication signal to the AM engine at the local end.
6.
The AM engine at the local end sends the switching indication signal to the service signal
processing unit and IF signal modulation unit. Hence, the service signal transmission unit
and IF signal modulation unit perform the switching of service frames and modulation
schemes after N frames. See Figure 18-4.
IF Module
MUX
Unit
Microwave
frame
IF Module
Tx Path
INDI
INDI
AM
Engine
SNR
MUX
Unit
18-8
Microwave
frame
Rx Path
AM
Messages
MUX
Unit
SNR
AM
Engine
INDI
INDI
Rx Path
Microwave
frame
Microwave
frame
Tx Path
MUX
Unit
Issue 02 (2010-09-24)
When an IF module detects that the SNR is higher than the modulation mode threshold for
triggering service switching, the IF module notifies the opposite end to switch the
modulation mode. The opposite packet switching unit performs QoS processing on services
based on the bandwidth change of the services, and then grooms the corresponding services
to the IF port.
2.
According to the QoS processing result, the opposite packet switching unit discards lowpriority services and grooms high-priority services to the IF port. The bandwidth of
microwave frames decreases, as shown in Figure 18-5. When the IF module detects that
the SNR is higher than the modulation mode threshold for triggering service switching, the
IF module notifies the opposite end to switch the modulation mode in the same manner.
IF Module
MUX
Unit
Microwave
frame
IF Module
Tx Path
INDI
INDI
AM
Engine
SNR
MUX
Unit
3.
Microwave
frame
Rx Path
AM
Messages
MUX
Unit
SNR
AM
Engine
INDI
INDI
Rx Path
Microwave
frame
Tx Path
Microwave
frame
MUX
Unit
The change of modulation schemes implemented through the AM function is based on the
frame boundary of the signal. The Rx path of the receive end sends the signal indicating
the receive mode change of the current frame to the MUX unit when detecting the change
of the modulation scheme. Hence, the MUX unit receives and processes service signals
according to the new modulation scheme.
Issue 02 (2010-09-24)
18-9
NOTE
The procedure of configuring hybrid microwave of the RTN 900 is similar to the procedure of the RTN 600.
Hence, the details are not described here.
18-10
Issue 02 (2010-09-24)
19
19-1
switch becomes absent in the network, these ports still work in the STP-compatible mode. In
this case, manually configure the port to recover the running of the MSTP protocol on the port.
19-2
Issue 02 (2010-09-24)
Switch B
Switch C
Switch D
Switch E
Switch F
Switch A
Switch B
Switch C
Switch E
Switch D
Switch F
Root: Switch F
When the link is congested, it cannot bear any traffic. Thus, the bandwidth is wasted.
When the network structure is dissymmetrical, a portion of the VLAN packets may not be
forwarded.
As shown in Figure 19-2, Host B and Host C belong to VLAN 2. The VLAN tag with 2 as the
VID is added to the Ethernet frames sent by Host B and Host C after the frames enter the switch.
Host A and Host D belong to VLAN 3. The VLAN tag with 3 as the VID is added to the Ethernet
frames sent by Host A and Host D after the frames enter the switch. As shown in Figure 19-2,
Issue 02 (2010-09-24)
19-3
the corresponding VLAN packets can only pass through links marked with VLAN 2 or VLAN
3. Packets of VLAN 2 and VLAN 3 cannot pass through other links.
After the STP/RSTP protocol is enabled, the network topology is divided into a single spanning
tree, which congests other ports. The link between Switch C and Switch D is congested, and
other links cannot forward packets of VLAN 2. Thus, communication between Host B and Host
C is unavailable.
Figure 19-2 Limitations of the STP/RSTP
Host A
Switch A
Switch B
VLAN 3
VLAN 2
VLAN 2
Switch C
Host B
Switch D
VLAN 2
VLAN 3
VLAN 3
Host C
Switch E
Switch F
Host D
Ethernet link
Spanning tree
Root switch
Each VLAN corresponds to one MSTI. In other words, the data in the same VLAN can only be transmitted
on one MSTI. One MSTI, however, may correspond to multiple VLANs.
19-4
Issue 02 (2010-09-24)
The network shown in Figure 19-2 can be considered as an MST region when MSTP is used.
Thus, Figure 19-3 shows the result. It is computed that two spanning trees are generated for
VLAN 2 and VLAN 3 respectively.
l
In this way, all VLAN packets can be properly forwarded. In addition, different VLAN packets
are forwarded through different paths. Thus, the load is balanced.
Figure 19-3 MSTI in an MST region
Host A
Switch A
Switch B
VLAN 3
Host B
VLAN 2
VLAN 2
Switch C
Switch D
VLAN 2
VLAN 3
VLAN 3
Host C
Switch E
Switch B
(Root)
Switch A
Switch A
VLAN 2
VLAN 2
Switch C
Host D
Switch F
Switch D
VLAN 2
VLAN 3
Switch B
VLAN 3
VLAN 2
Switch C
Switch D
VLAN 2
VLAN 3
VLAN 3
Switch E
Switch F
Switch E
Switch F
(Root)
Issue 02 (2010-09-24)
19-5
D0
B0
C0
A0
VLAN1--> MSTI 1
Other VLAN-->MSTI 0
CST
19-6
Issue 02 (2010-09-24)
D0
Switch A
MSTI 1
Root: Switch B
MSTI 2
Root: Switch D
Switch D
Switch B
MSTI 0 (IST)
Root: Switch A
VLAN 1
VLAN 2
VLAN 3
Switch C
-> MSTI 1
-> MSTI 2
-> MSTI 2
MST Region
The MST region consists of switches that support the MSTP in the LAN and network sections
among them. Switches physically and directly connected and configured with the same MST
region attributes belong to the same MST region. The attributes for the same MST region are as
follows:
l
Within a LAN, there can be multiple MST regions, which are physically and directly or indirectly
connected to each other. For example, as shown in Figure 19-4, there are four MST regions,
A0, B0, C0 and D0.
MSTI
Within an MST region, there can be multiple spanning trees, which are independent from each
other and correspond to different VLANs. Each spanning tree is an MSTI. For example, in the
MST region D0, there are three MSTIs, MSTI 0, MSTI 1 and MSTI 2. See Figure 19-5.
CIST
The common and internal spanning tree (CIST), computed by using the RSTP algorithm, is a
single spanning tree connecting all the switches within a switching network. In the CIST, the
common spanning tree (CST) is the portion connected to each MST region. In the CIST, the
portion in each MST region is the internal spanning tree (IST) of each MST region.
Issue 02 (2010-09-24)
19-7
CST
The CST, a spanning tree connected to all MST regions in a switching network, is the portion
responsible for connecting each MST region in the CIST. If each MST region is considered as
a switch, the CST is a spanning tree for the switch. For example, as shown in Figure 19-4, the
dashed lines indicate the CST of the network.
IST
The IST, a spanning tree in each MST region, is a section of the CIST in an MST region.
Normally, it is considered as the MSTI 0. For example, the MSTI 0 is shown in Figure 19-5.
When a packet with a VLAN tag is transmitted in an MST region, if the VLAN ID has no
corresponding MSTI, the packet is transmitted in the IST.
Regional Root
The regional root consists of the CIST regional root and MSTI regional root.
l
The CIST regional root is the root of the IST. For example, as shown in Figure 19-5, Switch
A is the CIST regional root of the MST region D0.
The MSTI regional root is the root of each MSTI. For example, as shown in Figure 19-5,
Switch B is the MSTI regional root of the MSTI 1, and Switch D is the MSTI regional root
of the MSTI 2.
CIST Root
The CIST root is the root switch of the CIST.
19-8
When multiple ports of the RTN equipment are connected to the same user network, these
ports should enable the MSTP protocol with the user network to avoid loops. These ports
connected to the user network should be first divided into a port group, which equals a
network bridge (switch) where the MSTP protocol is running.
One CE equipment of the user is connected to two RTN NEs. Then, the channel switching
is performed by using the MSTP protocol. In this way, the two RTN NEs only transparently
transmit the BPDU packets, but they are not involved in the topology computation of the
MSTP protocol.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
When the user network requires that the STP be enabled across networks of different
carriers, the RTN equipment only transparently transmits the BPDU packets without the
involvement of the MSTP computation.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Precautions
NOTE
l The sum of Ethernet ports enabled MSTP on one RTN equipment do not exceed one hundred.
l If an Ethernet port service is configured, this port can not be added to the port group.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Protocol
Configuration > MSTP Configuration from the Function Tree.
Step 2 Click the Port Group Parameters tab. Click Create to display the Create Port Group dialog
box.
Step 3 Set Protocol Type and Enable Protocol for the port group as required.
Step 4 Click Board and select the boards, to which the ports to be added to the port group belong, from
the drop-down list.
Step 5 Select the ports to be added to the port group from Available Port List. Click
the ports to Selected Port List.
to add
Step 6 When all ports to be added to the port group are added to Selected Port List, click OK. and the
Operation Result dialog box is displayed, indicating that the operation is successful.
Step 7 Click Close. The created port group is then listed in the port group list.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Issue 02 (2010-09-24)
19-9
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Protocol
Configuration > MSTP Configuration from the Function Tree.
Step 2 Click the Bridge Parameters tab, and select the port group. Configure MST Domain Name
and Redaction Level. Click Apply.
Step 3 If the mapping relation of the VLAN of the port group and MSTI need be modified, doubleclick Mapping List of the port group to display the Mapping List dialog box. In the Mapping
List dialog box, set the mapping relation of the VLAN ID and MSTI ID. Then, click Apply.
NOTE
Two means are available for setting the mapping relation between the VLAN ID and MSTI ID.
l Click the Set Mapping List tab, and enter the VLAN ID in the text box behind the MSTI ID. By default,
all VLAN IDs are mapped to MSTI 0.
l Click the Set Mapping Model tab, and enter the mapping module value (1-48) in the text box. Then,
the equipment distributes VLAN IDs (1-4094) equally to the MSTI whose mapping module ranges
from 1 to the mapping module value (1-16).
Two VLAN IDs (0, 4095) always map with MSTI 0.
Step 4 Select the port group and click the Bridge Parameters tab. Then, set MST Domain Max Hop
Count, Network Diameter, Hello Time, Max Age and Forward Delay for the port group.
Click Apply when the settings are completed.
Step 5 Select the port group and click the Port Parameter tab. Then, set Enable Edge Attribute,
Point-to-Point Attribute and Max Transmit Packet Count for each member port in the port
group. Click Apply when the settings are completed.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
You must complete the creation of a port group.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Protocol
Configuration > MSTP Configuration from the Function Tree.
Step 2 Click the CIST Parameters tab, and select the port group to be configured in Port Group.
Step 3 Each MSTI list of the port group is displayed in the upper pane. Double-click Bridge Priority
for the MSTI to modify the bridge priority of the MSTI. Click Apply when the setting is
completed.
19-10
Issue 02 (2010-09-24)
Step 4 Each member port list of the port group is displayed in the lower pane. Double-click Priority
and Path Cost for Port to modify the port priority and path cost of the member port. Click
Apply when the setting is completed.
----End
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Protocol
Configuration > MSTP Configuration from the Function Tree.
Step 2 Click the CIST Running Information tab. The upper pane lists information on the bridge status
of the port group, which works as a bridge where the MSTP is running. The lower pane lists
information on the status of each port in the port group.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
You must complete the creation of a port group.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Protocol
Configuration > MSTP Configuration from the Function Tree.
Step 2 Click the Port Group Parameters tab, and click the port group that contains the ports requiring
protocol transfer in the upper pane.
Step 3 Click the ports requiring protocol transfer in the lower pane. Click Protocol Transfer.
----End
Issue 02 (2010-09-24)
19-11
20
20-1
protocol configuration includes the configuration of node and port attributes, query and
configuration of route importing information, and query of the TE link information.
20.6 Configuring the MP-BGP
MP-BGP means that the BGP runs in the interior of the autonomous system. In an L3VPN, route
switching between the PE equipment is realized through the MP-BGP.
20.7 Configuring Static Routes
The static routes are selected according to the preset route options in the network. On the
U2000, the static routes can be queried and created.
20.8 Configuring the Address Parse
On the U2000, the IP address and MAC address of the ARP table items can be created and
queried.
20-2
Issue 02 (2010-09-24)
20-3
The IS-IS routing protocol packets use the uniform encapsulation format. The length of the
packets is changeable and the extensibility is strong. The complexity of the protocol is decreased,
because the types of the protocol packets are few. Thus, the running is more reliable and efficient.
The equipment realizes the following three types of IS-IS routing protocol packets:
l
Hello packets
Hello packets are used to construct and maintain neighbor relation between network nodes.
Hence, Hello packets are also called IS-to-IS hello (IIH) PDUs.
SNP packets
Sequence number PDUs (SNP) describe the link state PDUs in all or part of the LSDB.
The SNP is used to synchronize and maintain the LSDB of each network node in the
RTN network.
Path Cost
The equipment supports the manual setting of path cost, and controls the route that the MPLS
LSP travels through when it is dynamically created.
IS-IS TE
When the MPLS constructs the LSP, the traffic engineering information of all the links in the
local domain should be known. The IS-IS TE realized by the equipment supports the construction
of the MPLS LSP. The equipment obtains the traffic engineering information (link utilization
and path cost) of all the links in the network through the IS-IS routing protocol. It constructs
and synchronizes the TEDB, and uses the constrained shortest path first (CSPF) algorithm used
by the TEDB to compute the route that the MPLS LSP travels through.
20-4
Issue 02 (2010-09-24)
MPLS-LDP Session
The MPLS-LDP session is used to exchange label mapping and releasing messages between
different equipment. The MPLS-LDP session consists the following two types:
l
Local MPLS-LDP session, in which the two NEs used to set up the session is directly
connected.
Remote MPLS-LDP session, in which the two NEs used to set up the session is not directly
connected.
Discovery message, which is used to notify and maintain the existence of the equipment
in the network.
Session message, which is used to set up, maintain and end the session between MPLSLDP peer entities.
Advertisement message, which is used to create, change and delete the label mapping.
Notification message, which is used to provide the constructive message and error
notification.
Upstream request mode, in which the equipment in the upstream sends the label request
message to the equipment in the downstream. The equipment in the downstream returns
the bound labels to the equipment in the upstream through label mapping message. When
the equipment in the downstream returns the label mapping message is determined by the
label control mode used by the equipment.
If the ordered mode is used, only when the equipment receives the label mapping
message returned by the equipment in the downstream, it sends the label mapping
information to the upstream.
If the independent mode is used, the equipment immediately sends the label mapping
message to the upstream, regardless of whether it receives the label mapping message
returned by the equipment in the downstream.
Downstream unsolicited distribution mode, in which the equipment in the downstream take
the initiative to release the label mapping message to the equipment in the upstream after
the MPLS-LDP session is successfully set up. The equipment in the upstream saves the
label mapping information, and manages the received label mapping information according
to the route table information.
Issue 02 (2010-09-24)
Development phase: In this phase, the equipment that expects to set up a session
periodically sends Hello message to the adjacent equipment to notify the adjacent node of
the local peer relation. In this process, the equipment can automatically discover its LDP
peer entity without manual configuration.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
20-5
Session set-up and maintenance: After the peer relation is set up, the equipment begins to
set up the session.
PW set-up and maintenance: The set-up of the PW is based on the MPLS-LDP protocol.
Session cancellation: A life state timer is set up for each session. When each LDP PDU is
received, this timer is refreshed. If the timer times out before a new LDP PDU is received,
the equipment takes that the session is interrupted and the peer relation is invalid. The
equipment shuts down the corresponding connection at the transmission layer to end the
session.
Fixed-filter (FF) style: When this style is used, resources are reserved for each transmit end
individually. Thus, transmit ends in the same session cannot share the resources with each
other.
Shared-explicit (SE) style: When this style is used, resources are reserved for all transmit
ends in the same session. Thus, transmit ends can share the resources.
Path message: The transmit end sends this type of message in the transmission direction of
data packets. In addition, the path state is saved on all the nodes along the trail.
Resv message: The receive end sends this type of message in the reverse transmission
direction of data packets. In addition, the resource reservation is requested, and the
reservation state is created and maintained on all the nodes along the trail.
20-6
The ingress equipment generates the Path message, which is transmitted in the direction of
the egress equipment.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
After the egress equipment receives the Path message, the Resv message is generated and
then is returned to the ingress equipment. In addition, the Resv message reserves resources
on the equipment along the trail.
When the ingress equipment receives the Resv message, the LSP is successfully created.
The LSP created by using the MPLS-RSVP has the resource reservation function. The
equipment along the trail can distribute some resources to the LSP to ensure the services
on the LSP.
Ingress
Path
Path
Resv
Resv
Sender
Receiver
Issue 02 (2010-09-24)
20-7
Source
MAC
address
MAC
address
type
IP
MAC
protocol addres
type
s length
Frame
type
IP
address
length
ARP request/answer
OP
MAC address
at the transmit
end
IP address
at the
transmit
end
Destination
MAC
address
Destination
IP address
Destination MAC address: six bytes. When an ARP request is sent, the destination MAC
address is the broadcast MAC address, that is, 0xFF.FF.FF.FF.FF.FF.
MAC address type: two bytes. It defines the address type in the network that runs the ARP.
Value 1 indicates the Ethernet address.
IP protocol type: two bytes. It defines the protocol type. Value 0x0800 indicates the IP
address.
MAC address length: one byte. It defines the length of the physical address expressed in
bytes. In the case of an ARP request or answer, the value of this field is 6.
IP address length: one byte. It defines the length of the logical address expressed in bytes.
In the case of an ARP request or answer, the value of this field is 4.
OP: two bytes. It defines the ARP packet type. Value 1 indicates the ARP request and value
2 indicates the ARP answer.
MAC address at the transmit end: six bytes. It defines the MAC address of the transmit
station.
IP address at the transmit end: four bytes. It defines the IP address of the transmit station.
Destination MAC address: six bytes. It defines the destination MAC address. In the case
of an ARP request packet, the value of this field is all-zero.
Static ARP
Static ARP means that there is a fixed mapping relation between the IP address and the MAC
address, and thus you cannot adjust this relation dynamically on the equipment or the router.
For the static ARP, you need to manually create a table that is stored on each equipment in the
network.
The static ARP table is used in the following scenarios:
l
20-8
When a packet is transmitted to a destination address beyond the local network segment,
this packet is bound with a specific network interface card (NIC) in order to be forwarded
through this gateway.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
To filter out certain illegal IP addresses, you can bind these addresses with an MAC address
that does not exist to realize the filtering.
Dynamic ARP
Dynamic ARP means that the mapping relation between the IP address and the MAC address is
constantly refreshed and adjusted through address learning.
Changing the NIC or moving the host to another network usually changes the physical address.
The corresponding MAC address can be obtained in a timely manner based on the dynamic ARP
address resolution.
ARP Principle
When a host or other network equipment needs to transmit data to another host or equipment,
IP data packets must be encapsulated into frames to be transmitted in the physical network.
During the transmission, the destination MAC address must be available.
When the equipment on the transmit station wants to obtain the MAC address of another
equipment in the network, the transmit station searches for the MAC address corresponding to
the IP address in the ARP table. If the ARP table is available, the transmit station obtains the
MAC address from the ARP table directly. Otherwise, the ARP function is enabled. As shown
in Figure 20-3, host A sends data to host B to obtain the MAC address of host B.
To obtain the MAC address of the station whose IP address is 10.1.1.2, host A broadcasts an
ARP request packet in the network. The packet carries the information about the MAC address
and IP address of the transmit station, and the IP address of the destination station. All the
equipment in the network receives and handles the ARP request packet. Only host B on the
destination station, however, can identify the IP address and return an ARP answer packet.
According to the MAC address of the transmit station in the request packet, host B sends the
ARP answer packet to the request station in unicast mode. After receiving the ARP answer
packet, host A obtains the MAC address of host B.
Figure 20-3 ARP address resolution
Transmit station: A-A-B;10.1.1.2
Destination station: A-A-A;10.1.1.1
Host A
IP: 10.1.1.1
MAC: A-A-A
Host B
IP: 10.1.1.2
MAC: A-A-B
Host C
IP: 10.1.1.3
MAC:A-A-C
Issue 02 (2010-09-24)
Host D
IP: 10.1.1.4
MAC:A-A-D
20-9
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration
> IGP-ISIS Configuration from the Function Tree.
Step 2 Click the Node Configuration tab.
NOTE
Step 3 Optional: Select the ISIS Instance, you can modify the parameter of nodes managed by the IGPISIS protocol.
Step 4 Click Apply to complete the setting of parameters.
Step 5 Click Query to query the parameters of a node.
----End
20-10
Issue 02 (2010-09-24)
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration
> IGP-ISIS Configuration from the Function Tree.
Step 2 Click the Port Configuration tab.
Step 3 Optional: Select the port, you can modify the parameter of ports managed by the IGP-ISIS
protocol.
Step 4 Click Apply to complete the setting of port parameters.
Step 5 Click Query to query the parameters of each port.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration
> IGP-ISIS Configuration from the Function Tree.
Step 2 Click the Route Import tab.
Step 3 Click Import to display the Route Import dialog box, and then set parameters of the imported
routes.
Step 4 Click Apply to complete the setting of parameters of the imported routes. Then, click OK.
Step 5 Click Query to query the parameters of the imported routes.
Issue 02 (2010-09-24)
20-11
CAUTION
When modifying the parameters of the imported routes, click Delete to delete the original
settings, and then click Import to re-set. This operation, however, interrupts the services. Thus,
exercise caution when performing this operation.
----End
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration
> IGP-ISIS Configuration from the Function Tree.
Step 2 Click the Link TE Info tab.
Step 3 Click Query to query the information on the parameters of the link TE.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
20-12
Issue 02 (2010-09-24)
Context
For the local session and remote session, you only need to create bidirectional LDP peers between
the source equipment and sink equipment. That is, you need to create peers from the source to
the sink, and from the sink to source.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration
> MPLS-LDP Configuration from the Function Tree.
Step 2 Click Create to display the Create LDP Peer Entity dialog box.
Step 3 For the Local LSR ID and Opposite IP fields, enter LSR ID of the opposite NE. Then, click
Apply.
Step 4 After the setting is complete, click OK.
Step 5 Click Query to query the parameters of the MPLS-LDP peer entities.
NOTE
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration
> MPLS-LDP Configuration from the Function Tree.
Step 2 Set the parameters of the MPLS-LDP protocol.
Step 3 Click Apply to complete the setting of the parameters of the MPLS-LDP protocol.
Step 4 Click Query to query the parameters of the MPLS-LDP protocol.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Issue 02 (2010-09-24)
20-13
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration
> MPLS-RSVP Configuration from the Function Tree.
Step 2 Set the parameters of the MPLS-RSVP protocol.
Step 3 Click Apply to complete the setting of the parameters of the MPLS-RSVP protocol.
Step 4 Click Query to query the parameters of the MPLS-RSVP protocol.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration
> IGP-OSPF Configuration from the Function Tree.
Step 2 Click the Node Configuration tab.
Step 3 Click New. Set the parameters of the node in the Create IGP-OSPF Protocol Instance dialog
box displayed.
20-14
Issue 02 (2010-09-24)
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration
> IGP-OSPF Configuration from the Function Tree.
Step 2 Click the Port Configuration tab.
Step 3 Click New. Add ports managed by the OSPF protocol in the Config IGP-OSPF Protocol
Interface dialog box displayed.
Issue 02 (2010-09-24)
20-15
The OSPF protocol port can be an Ethernet interface, Ethernet virtual interface, or MP group.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration
> IGP-OSPF Configuration from the Function Tree.
Step 2 Click the Route Import tab.
Step 3 Click Import to display the Route Import dialog box, and then set parameters of the imported
routes.
Step 4 Click Apply to complete the setting of parameters of the imported routes. Then, click OK.
Step 5 Click Query to query the parameters of the imported routes.
CAUTION
When modifying the parameters of the imported routes, click Delete to delete the original
settings, and then click Import to re-set. This operation, however, interrupts the services. Thus,
exercise caution when performing this operation.
----End
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
20-16
Issue 02 (2010-09-24)
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration
> IGP-OSPF Configuration from the Function Tree.
Step 2 Click the Link TE Info tab.
Step 3 Click Query to query the information on the parameters of the link TE.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration
> MP-BGP Configuration from the Function Tree.
Step 2 Click the MP-BGP Configuration tab. Click New and the Create MP-BGP Protocol
Instance dialog box is displayed.
Step 3 Set MP-BGP Protocol Instance and AS Number.
Step 4 Click OK and the Operation Result dialog box is displayed indicating that the operation is
successful.
Step 5 Click the Peer Configuration tab. Click New, and the Create Peer dialog box is displayed.
Step 6 Configure the peer of the MP-BGP protocol instance. You can select the MP-BGP Protocol
Instance that is already configured, and set the Remote IP Address and the Remote AS
Number that corresponds to the MP-BGP protocol instance.
Step 7 Click OK and the Operation Result dialog box is displayed indicating that the operation is
successful.
----End
Prerequisite
l
You must complete the setting of the basic attributes and Layer 3 attributes of the port.
Issue 02 (2010-09-24)
20-17
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Control Plane Configuration
> Static Route Management from the Function Tree.
Step 2 Click Create to create the static routes, and then click Apply.
NOTE
l When selecting boards or ports, select those that have Layer 3 attributes.
l When the static route is configured, the port IP address and the next hop IP address must be in the same
network section.
l When the last digit of the IP address of the destination is not 0, the subnet mask is 255.255.255.255.
For example, if the IP address is 193.168.3.2, the mask of the destination node is 255.255.255.255.
l When the last digit of the IP address of the destination is 0, the subnet mask is 255.255.255.0 or
255.255.255.255. For example, if the IP address is 193.168.3.0, the mask of the destination node is
255.255.255.255 or 255.255.255.0.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, click the NE, and choose Configuration > Control Plane Configuration
> Address Parse from the Function Tree.
Step 2 Click Create and the Add Address Parse dialogue box is displayed.
Step 3 Set the IP address and MAC address of the ARP table items separately, and then click Apply.
20-18
Issue 02 (2010-09-24)
CAUTION
When configuring the MAC address of the ARP table items, the first digit of the address must
be of an even number.
Step 4 After the setting is complete, click OK.
CAUTION
The configuration of the address resolution refers to the creation of the static ARP table items.
To delete the dynamic ARP table items, click Clear. This operation, however, clears all the
contents in the ARP table items, and interrupts the services. Thus, exercise caution when
performing this operation.
NOTE
----End
Issue 02 (2010-09-24)
20-19
21
Issue 02 (2010-09-24)
21-1
IMA E1
Ingress node
FE
Transit node
Egress node
MPLS tunnel
ATM STM-1
IMA E1
FE
ATM STM-1
PW
The MPLS tunnel only provides an end-to-end channel, and does not care which service is
encapsulated in the PW it carries. Data packets are first encapsulated in the PW, which is stuck
with an MPLS label and sent to the MPLS tunnel for transmission. At the sink end, data packets
are recovered and retain the original service features. In the tunnel, the intermediate nodes are
called Transit nodes. Hence, a tunnel contains the Ingress node, Egress node and Transit nodes.
Issue 02 (2010-09-24)
PE
MPLS tunnel
Node B
PE
PE
RNC
MPLS tunnel
MPLS tunnel
PE
Node B
An edge node in one network accesses the services from Node B, and transports the services to
the RNC connected to another PE. For such transport, one point-to-point MPLS tunnel can be
used. On the U2000, two schemes can be used to create such a unicast tunnel.
l
Configuration on a per-NE basis: Configure the ingress port and the IP address of the next
hop at each NE involved in the MPLS tunnel. In this way, one unicast MPLS tunnel is
created.
Configuration by trail: This configuration is classified into static configuration and dynamic
configuration.
Static configuration: Specify the source and sink NEs for the MPLS tunnel, and each
NE involved in the tunnel. In this way, one unicast MPLS tunnel is created.
Dynamic configuration: Only specify the source and sink NEs of the MPLS tunnel. The
equipment then creates a unicast MPLS tunnel through signaling.
21-3
By using the U2000, the user can configure 1+1 or 1:1 protection for MPLS tunnels that carry
important services.
Figure 21-3 shows the protection principle for unicast tunnels.
Figure 21-3 Protection principle for unicast tunnels
CE
CE
Working
tunnel
Ingress
node
Egress
node
Protection
tunnel
Configuration of source
protection group
Configuration of sink
protection group
Prerequisite
You must be an NM user with "NE operator" authority or higher.
21-4
Issue 02 (2010-09-24)
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > MPLS Management > Basic
Configuration from the Function Tree.
Step 2 Set LSR ID, Start of Global Label Space and Start of Multicast Label Space.
CAUTION
If there are services on the NE, modifying LSR ID may result in NE reset and service
interruption.
----End
Prerequisite
l
You must complete the correct setting of the LSR ID for each NE.
Procedure
Step 1 Select the source NE of the tunnel in the NE Explorer. Choose Configuration > MPLS
Management > Unicast Tunnel Management from Function Tree.
Step 2 Click the Static Tunnel tab and click New. The New Unicast Tunnel dialog box is displayed.
Step 3 Select New Reverse Tunnel to set parameters for the forward and reverse tunnels.
NOTE
When Node Type is set to Egress, Bandwidth(kbit/s) must be consistent with the tunnel bandwidth in
the Ingress direction and cannot be set.
For Next Hop Address, select the IP address of the interface of the next node, or the LSR ID of the next
node.
If the created tunnel is carried by VLAN sub-interfaces, Vlan ID cannot be set for the tunnel.
----End
Issue 02 (2010-09-24)
21-5
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 Select the source NE of the tunnel in the NE Explorer. Choose Configuration > MPLS
Management > Unicast Tunnel Management from Function Tree.
Step 2 Click the Static Tunnel tab. Select the tunnel to be deleted from the static MPLS tunnel list.
Step 3 Click Delete. A dialog box is displayed for confirmation.
Step 4 Follow Steps 1 - 3 to delete static tunnels for Transit nodes and the Egress node.
----End
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
You must complete the creation of an MPLS tunnel.
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > MPLS Management > MPLS
Label Management from the Function Tree.
Step 2 In the Tunnel Label tab, click Query to view the tunnel label information.
----End
21-6
Issue 02 (2010-09-24)
22
22 Configuring an IP Tunnel
Configuring an IP Tunnel
Issue 02 (2010-09-24)
22-1
22 Configuring an IP Tunnel
22.1 IP Tunnel
IP tunnel can be used to carry the ATM PWE3 service or the CES service.
If ATM or CES emulation service that travels through an IP network is required, the RTN
equipment can use the IP tunnel to carry the service. This complies with RFC 4023 as shown in
Figure 22-1. In the case of the IP tunnel, the situation is similar to that where "IP header" replaces
the MPLS external label (MPLS tunnel label) to establish a tunnel in the IP network. An ATM
emulation service can be provided between NE A and NE B, even though the IP network between
NE A and NE B does not support the MPLS.
Figure 22-1 ATM PWE3 over IP tunnel
ATM
switch
Router
RTN
Router
RTN
ATM
switch
IP network
NE B
NE A
ATM
E1/STM-1
ATM
PWE3
PW Label
IP
Ethernet
ATM
PWE3
PW Label
IP
Ethernet
ATM
E1/STM-1
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > IP/GRE Tunnel
Management > Basic Configuration from the Function Tree.
Step 2 Configure the parameters related to the port of UDP PW. Click Apply.
----End
22-2
Issue 02 (2010-09-24)
22 Configuring an IP Tunnel
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > IP/GRE Tunnel
Management > IP Tunnel Management from the Function Tree.
Step 2 Click New and the Create IP Tunnel dialog box is displayed.
Step 3 Set parameters.
Step 4 Click OK. A prompt appears indicating that the operation was successful. Click Close.
Step 5 Optional: Select the created tunnel. Double-click the Vlan ID filed, and differentiate different
tunnels by adding a VLAN ID.
NOTE
If the created tunnel is carried by VLAN sub-interfaces, Vlan ID cannot be set for the tunnel.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, click an NE. Choose Configuration > IP Tunnel Management from the
Function Tree.
Step 2 Select an IP tunnel and click Delete. The Confirm dialog box is displayed. Click OK. A dialog
box is displayed indicating that the operation is successful.
Step 3 Click Close.
----End
Issue 02 (2010-09-24)
22-3
23
Issue 02 (2010-09-24)
23-1
RTN
Router
Router
ATM
switch
RTN
IP network
NE A
ATM
E1/STM-1
NE B
ATM
PWE3
PW Label
GRE
IP
Ethernet
ATM
PWE3
PW Label
GRE
IP
Ethernet
ATM
E1/STM-1
Prerequisite
l
Procedure
Step 1 In the NE Explorer, click an NE. Choose Configuration > IP/GRE Tunnel Management >
GRE Tunnel Management from the Function Tree.
Step 2 Click New and the Create GRE Tunnel dialog box is displayed.
NOTE
When Loopback Port is set to Used, Source Board and Source Port, is unavailable.
Issue 02 (2010-09-24)
Step 5 Optional: Select the created tunnel. Double-click the Vlan ID filed, and differentiate different
tunnels by adding a VLAN ID.
NOTE
If the created tunnel is carried by VLAN sub-interfaces, Vlan ID cannot be set for the tunnel.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, click an NE. Choose Configuration > GRE Tunnel Management from
the Function Tree.
Step 2 Select a GRE tunnel and click Delete. The Confirm dialog box is displayed. Click OK. A dialog
box is displayed indicating that the operation is successful.
Step 3 Click Close.
----End
Issue 02 (2010-09-24)
23-3
24
24 Configuring an MPLS PW
Configuring an MPLS PW
Issue 02 (2010-09-24)
24-1
24 Configuring an MPLS PW
Prerequisite
l
Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > MPLS Management > PW
Management from Function Tree.
Step 2 Click Query. All MPLS PWs created on the NE are displayed.
Step 3 Click the Advanced Attributes tab to view the advanced attributes of the MPLS PW.
----End
Prerequisite
l
Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > MPLS Management > PW
Management from Function Tree.
Step 2 Click Query. All MPLS PWs created on the NE are displayed in the upper pane.
Step 3 In the QoS information below, query the QoS parameters.
----End
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
24-2
Issue 02 (2010-09-24)
24 Configuring an MPLS PW
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > MPLS Management > MPLS
Label Management from the Function Tree, and then click the PW Label tab.
Step 2 Click Query to view the PW label information.
----End
Issue 02 (2010-09-24)
24-3
25
Issue 02 (2010-09-24)
25-1
Application Mode
The CES service allows a metropolitan Ethernet network (MEN) carrier to provide TDM services
to customers that have only the TDM equipment. This enlarges the service range and the number
of users of the MEN carriers, and provides a way to transform the traditional circuit network to
the wideband data network.
The CES service mainly applies to the wireless service and the enterprise private line service.
The application scenarios include UNI-NNI and UNI-UNI, as shown in Figure 25-1.
l
UNI-NNI CES service: The RTN equipment accesses the TDM services of customers by
using the TDM interface. The CES PW can be created between the RTN equipments to
emulate the end-to-end TDM service. To customers, the CES services are similar to actual
TDM services.
UNI-UNI CES service: The RTN equipment accesses the TDM services by using a single
point.
NOTE
Now only the point-to-point service is supported. That is, the service of one E1 interface mapping to one
PW is supported. But converged services of several TDM interfaces mapping to one PW are not supported.
25-2
Issue 02 (2010-09-24)
UNI-UNI
BTS
UNI-NNI
BSC
PE
PE
BTS
TDM Link
cSTM Link
PW
PE
BTS
Tunnel
Emulation Mode
The RTN equipment supports two types of CES services: structure-aware TDM circuit emulation
service over packet switched network (CESoPSN) and structure-agnostic TDM over packet
(SAToP).
In the CESoPSN mode:
l
The RTN equipment senses frame structures, frame alignment modes and timeslots in the
TDM circuit.
The RTN equipment processes the overhead and extracts the payload in TDM frames. Then,
the RTN equipment delivers the timeslot of each channel to the packet payload according
to certain sequence. As a result, the service in each channel in the packet is fixed and visible.
Each Ethernet frame that carries the CES service loads TDM frames of a fixed number.
Usually the loading time is 0.125 to 5 ms.
25-3
The equipment regards TDM signals as constant rate bit flows, instead of sensing structures
in the TDM signals. The entire bandwidth of TDM signals is emulated.
The overhead and payload in the TDM signal are transparently transmitted.
The Ethernet frame carries the CES service. Usually the loading time is 1 ms.
In the CESoPSN mode, for the free 64 kbit/s timeslot in TDM E1 signal, the RTN equipment
provides the compression function to save the transmission bandwidth. The timeslot number
ranges from 0 to 31. The timeslot number of 0 indicates a reserved timeslot for transmitting
signaling.
Service Clock
The TDM service has high requirements for the clock synchronization. The RTN equipment
provides two solutions to the CES service clock synchronization. See Table 25-1.
Table 25-1 CES service clock type
Synchroni
zation
Solution
PRC Access
Position
Description
External
Clock
Synchroniza
tion
PE equipment
No
PRC/GPS
CES
CE
25-4
TDM+Clock PE
PE
TDM+Clock
CE
Issue 02 (2010-09-24)
Required
Start
Optional
Creating a Network
Configure inferface
Configure UNI-UNI
CES Service
End
Issue 02 (2010-09-24)
Task
Remarks
Creating Network
25-5
Required
Start
Optional
Creating a Network
Configure inferface
Configure Control
Plan
Configure Tunnel
Configure UNI-NNI
CES Service
End
25-6
Task
Remarks
Creating Network
Issue 02 (2010-09-24)
Task
Remarks
25-7
If you create a CES service on a per-NE basis, you need to create relevant attributes of the service
separately on the source and sink nodes of the service.
25.3.2 Creating a UNI-NNI CES Service
If you create a CES service on a per-NE basis, you need to create relevant attributes of the service
separately on the source and sink nodes of the service. After the CES service is created, the
corresponding PW is automatically created.
25.3.3 Deleting a CES Service
When you delete a CES service on a per-NE basis, you need to delete relevant attributes of the
service separately on the source and sink nodes of the service. After the CES service is deleted,
the corresponding PW is automatically deleted.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The ports must be configured.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > CES Service Management from
the Function Tree.
Step 2 Click New, and the Create CES Service dialog box is displayed. In this dialog box, configure
the UNI-UNI service.
NOTE
2.
Click Apply. A dialog box is displayed, indicating that the operation is successful. Click
Close.
----End
Prerequisite
l
25-8
Issue 02 (2010-09-24)
The tunnel must be created. For configuration method, see 21.2.2 Creating an MPLS
Tunnel.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > CES Service Management from
the Function Tree.
Step 2 Click New, and the Create CES Service dialog box is displayed.
NOTE
2.
3.
4.
Click OK.
5.
Issue 02 (2010-09-24)
25-9
6.
7.
Click OK.
8.
Click Apply. A dialog box is displayed, indicating that the operation is successful. Click
Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > CES Service Management from
the Function Tree.
Step 2 Select the service that you want to delete. Click Delete, and the Prompt dialog box is displayed.
Step 3 Confirm the deletion, and the Operation Result dialog box is displayed, indicating that the
operation is successful.
Step 4 Click Close.
----End
25-10
Issue 02 (2010-09-24)
26
Issue 02 (2010-09-24)
26-1
26.1.1 IMA
The inverse multiplexing for ATM (IMA) technology, demultiplexes an ATM cell flow to
multiple low-speed links, which are then multiplexed at the far end so that the cell flow is restored
to its original form. In this way, the multiplexing of multiple low-speed links becomes flexible
and easy.
This functionality applies to E1 interconnections between ATM networks, and does not have
special requirements for service types. See Figure 26-1.
Figure 26-1 ATM IMA group
Physical Link#0
Physical Link#1
Single ATM
Cell Stream
from ATM Layer
26-2
Physical Link#2
IMA Virtual Link
Issue 02 (2010-09-24)
As shown in Figure 26-2, the ATM service on Node B is directly interconnected to the
RTN equipment at the access side through the E1 links.
As shown in Figure 26-3, the ATM service on Node B is accessed to the SDH equipment
through the E1 links, and then the ATM service is aggregated to the STM-1 link. At last,
the IMA protocols are interconnected on the RTN equipment at the access side.
IMA 2
RTN
Node B
E1 Link
Node B
PTN
SDH
Node B
SDH
E1 Link
Node B
cSTM-1 Link
26-3
IMA 2
RTN
Node B
E1 Link
UNIs-NNI ATM service: The RTN equipment accesses the ATM services of customers by
using the IMA link respectively. You can create the ATM PW between the RTN equipment
to emulate end-to-end ATM services. At the source end, the ATM cells are encapsulated
in the PW. Then, data packets are transparently transmitted in the MPLS network. At the
sink end, the ATM services are decapsulated and forwarded to the connected customer
network. To customers, the UNIs-NNI ATM services are similar to actual ATM services.
UNI-UNI ATM services: The RTN equipment switches and transmits the ATM services
at a single point.
The ATM UNIs-NNI service supports the convergence of multiple ATM connections into a PW
for transmission. As shown in Figure 26-5, three ATM connections are encapsulated into a PW.
Figure 26-5 ATM connection convergence sample
26-4
Issue 02 (2010-09-24)
Issue 02 (2010-09-24)
Application Type
Application
Instance
Traffic Parameter
Remarks
PCR, CDVT
LAN emulation, IP
over ATM, and nonspecial traffic
services
PCR, CDVT
UBR+
LAN emulation, IP
over ATM, and nonspecial traffic
services
PCR, CDVT
26-5
Application Type
Application
Instance
Traffic Parameter
Remarks
Data packet
transmission,
terminal meeting,
and file transmission
Peak cell rate (PCR): It defines the maximum cell rate at which cells are transmitted to a
network.
Sustainable cell rate (SCR): It defines the maximum sustainable average cell rate at which
cells are transmitted to a network.
Cell delay variation tolerance (CDVT): When multiple connected cells are converged, at
the convergence egress, the transmission of a connected cell may be delayed because of
the insertion of other connected cells. Similarly, the transmission delay may also be caused
by the insertion of physical layer overheads and OAM cells. In other words. the cells do
not evenly arrive at the receive station. The arrival intervals of consecutive cells are
different in different periods. The maximum tolerance of this difference is called CDVT.
Maximum burst size (MBS): It limits the maximum cell burst amount within the maximum
rate permitted.
Users require each service type to provide a certain QoS and comply with a certain traffic
protocol, which is realized by traffic control. During transmission, only user cells complying
with the protocol can be successfully transmitted. Cells that do not comply with the protocol are
labelled or discarded according to different situations.
26-6
Issue 02 (2010-09-24)
Traffic shaping
UPC/NPC
UPC/NPC monitors and controls the traffic to judge whether cell violation occurs according to
the negotiated parameters. If cell violation occurs, corresponding measures will be taken to
prevent network resources from being invaded viciously or unintentionally. This ensures that
one link never violates the traffic control.
UPC is an act of connection monitoring at the UNI (dedicated or public), and NPC is an act of
connection monitoring at the NNI (dedicated or public).
According to different traffic types. the UPC includes the following measures:
l
Allow cells to pass through: The cells are considered protocol-abiding by the UPC.
Label cells: This operation is performed on the cell loss priority (CLP). The UPC labels
only cells whose CLP values are 0 by changing the CLP values to 1. In this case, these cells
are in conflict with the traffic convention. If the bandwidth is sufficient, these cells are
allowed to pass through. If the bandwidth is insufficient, however, these labeled cells are
discarded.
Discard cells: The cells violate the protocol and thus cannot be transmitted continuously.
Traffic Shaping
Traffic shaping is a method of changing the traffic feature of a cell flow to realize a higher
network efficiency and ensure the QoS index. Traffic shaping helps the cell flow to be transmitted
more evenly, maximize the efficiency, and eases the network burden.
Congestion Control
Traffic parameter control is based on the connection and cells, but congestion control relates to
different service types.
If a network requires discarding cells, a better solution of congestion is to discard packets rather
than cells. When an NE discards cells, it also discards a part of the packet. As a result, the upper
layer protocol, such as the TCP/IP protocol, is retransmitted, and thus congestion or even collapse
occurs.
26-7
Required
Start
Optional
Creating Network
Remarks
1. Creating
Network
2. Configure the
ATM Policy
The ATM policy is used for traffic management of the ATM service.
The ATM interface accesses services from NodeB.
4. Configure the
UNI-UNI ATM
Service
26-8
Issue 02 (2010-09-24)
Required
Start
Optional
Creating Network
Configure the
network-side interface
End
Issue 02 (2010-09-24)
Task
Remarks
1. Creating
Network
2. Configure the
LSR ID
26-9
Task
Remarks
3. Configure the
network-side
interface
Set the general attributes and Layer 3 attributes (tunnel enable status and
IP address) for interfaces to carry the tunnel carrying.
20 Configuring
the Control
Plane4.
Configure the
control plane
Set the protocol parameters related to the control plane to create the
tunnel.
l To create a static MPLS tunnel to transmit the ATM service, the
parameters related to the control plane need not be set.
l To create a dynamic MPLS tunnel to transmit the ATM service, you
need to set the following protocol parameters:
1. Set the IGP-ISIS protocol parameters. For details, see 20.2
Configuring the IGP-ISIS Protocol.
2. Set the MPLS-RSVP protocol parameters. For details, see 20.4
Configuring the MPLS-RSVP Protocol.
To create a dynamic PW to transmit the service, you need to set the
parameters related to the IGP-ISIS protocol and the MPLS-LDP
protocol.
5. Configure the
Tunnel
6. Configure the
ATM Policy
The ATM policy is used for traffic management of the ATM service.
7. Configure the
ATM Interface
8. Configure the
UNIs-NNI ATM
service
1. Create an ATM service: Specify the service ID, name the service,
and select the service type and connection type.
2. Configure the connection: Set the source information, PW ID, sink
information, and policy.
3. Configure a PW: Set the PW type, label, and tunnel type.
4. Configure CoS mapping: Set the CoS policy for the PW.
26-10
Issue 02 (2010-09-24)
Leve
l
Configuration Method
E1
1. In General attributes for the PDH interface, set the port mode to
Layer 2. For details, see 8.2.1 Setting General Attributes of PDH
Interfaces.
2. In Advanced Attributes for the PDH interface, set the Frame
Format and Frame Mode. For details, see 8.2.3 Setting the
Advanced Attributes of PDH Interfaces.
3. Configuring bound channels in an ATM IMA Group, for details, see
26.3.1 Configuring Bound Channels in an ATM IMA Group in
the .
4. Set attributes of the ATM IMA group. In particular, specify the IMA
Transmit Frame Length, set the IMA Symmetry Mode, and enable
the IMA protocol. For details, see 26.3.2 Configuring Attributes of
an ATM IMA Group in the .
5. Set attributes of the ATM interface. In particular, set the interface
type, maximum VPI, and maximum VCI. For details, see 26.3.3
Configuring ATM Interface Attributes in the .
E1 board
(For
example:
)
64K
times
lots
1. In General attributes for the PDH interface, set the port mode to
Layer 1. For details, see 8.2.1 Setting General Attributes of PDH
Interfaces.
2. In Advanced Attributes for the PDH interface, set the Frame
Format and Frame Mode. For details, see 8.2.3 Setting the
Advanced Attributes of PDH Interfaces.
3. Create a serial port and specify the timeslots used by the service. Set
the port mode to Layer 2 and the encapsulation type is ATM. For
details, see 8.5.1 Creating Serial Interfaces.
4. Configuring bound channels in an ATM IMA Group, for details, see
26.3.1 Configuring Bound Channels in an ATM IMA Group in
the .
5. Set attributes of the ATM IMA group. In particular, specify the IMA
Transmit Frame Length, set the IMA Symmetry Mode, and enable
the IMA protocol. For details, see 26.3.2 Configuring Attributes of
an ATM IMA Group in the .
6. Set attributes of the ATM interface. In particular, set the interface
type, maximum VPI, and maximum VCI. For details, see 26.3.3
Configuring ATM Interface Attributes in the .
Issue 02 (2010-09-24)
26-11
Support
ed
Board
Type
Leve
l
Configuration Method
VC1
2
Channeli
zed
STM-1
board
(For
example:
CD1)
1. Create a serial port and specify the timeslots used by the service. Set
the port mode to Layer 2 and the encapsulation type is ATM. For
details, see 8.5.1 Creating Serial Interfaces.
2. Configuring bound channels in an ATM IMA Group, for details, see
26.3.1 Configuring Bound Channels in an ATM IMA Group in
the .
3. Set attributes of the ATM IMA group. In particular, specify the IMA
Transmit Frame Length, set the IMA Symmetry Mode, and enable
the IMA protocol. For details, see 26.3.2 Configuring Attributes of
an ATM IMA Group in the .
4. Set attributes of the ATM interface. In particular, set the interface
type, maximum VPI, and maximum VCI. For details, see 26.3.3
Configuring ATM Interface Attributes in the .
Context
Figure 26-8 shows the flow for configuring an IMA group.
26-12
Issue 02 (2010-09-24)
Configure bound
paths for an
ATM IMA group
Configure IMA
group attributes
Configure ATM
interface attributes
Reset an IMA
group
Modify an IMA
group
Delete an IMA
group
End
Required
Optional
26-13
Prerequisite
You must be an NM user with "NE operator" authority or higher.
When the MLPPP or CES services is configured or the DCN is enabled on the VCTRUNK, the
VCTRUNK resources are occupied and thus the IMA group cannot be created.
When an E1or Fractional E1 port is bound with an IMA group, Port Mode should be set to
Layer 2.
Context
NOTE
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM
IMA Management from Function Tree.
Step 2 Click the Binding tab and click Configuration. The Bound Path dialog box is displayed.
Step 3 Configure boards and VCTRUNK ports in Available Boards and Configurable Ports
respectively.
Step 4 Select E1, Fractional E1 for Level.
Step 5 Select a port in Available Resources. Click
26-14
Issue 02 (2010-09-24)
CAUTION
The VCTRUNK that is first added into the IMA group should be deleted at last.
The ports that are bound to the same VCTRUNK must have the same E1 frame mode or VC12
frame mode.
When the member links of an IMA group are at the serial ports of the 64K level, there are the
following restrictions:
l One serial port should be bound with a minimum of three 64K timeslots.
l The number of bound 64K timeslots should be the same for different serial ports.
l In one E1, only one serial port can be used as a member link of an IMA group.
Step 6 Click OK. A dialog box is displayed, indicating that the operation succeeds. Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 Click the NE in the NE Explorer. Choose Configuration > Interface Management > ATM
IMA Management from Function Tree.
Step 2 Click the IMA Group Management tab, enable the IMA protocol, and configure attributes of
the IMA group. Click Apply. A dialog box is displayed, indicating that the operation succeeds.
Click Close.
NOTE
----End
26-15
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM
IMA Management from the Function Tree. Click the ATM Interface Management tab.
Step 2 Optional: Click Query to query the current attributes of each interface.
Step 3 Set relevant attributes of the interfaces bound with the IMA group as required.
Step 4 Click Apply. The Operation Result dialog box is displayed indicating that the operation is
successful.
Step 5 Click Close.
----End
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM
IMA Management from Function Tree.
Step 2 Click the IMA Group States tab and select the IMA group for query. Click Query. A dialog
box is displayed, indicating that the operation succeeds. Click Close.
----End
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM
IMA Management from Function Tree.
26-16
Issue 02 (2010-09-24)
Step 2 Click the IMA Link States tab and select the IMA link for query. Click Query. A dialog box
is displayed, indicating that the operation succeeds. Click Close.
----End
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM
IMA Management from Function Tree.
Step 2 Click the IMA Group Management tab and select the IMA group. Click Reset. A dialog box
is displayed, indicating that the operation succeeds. Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
CAUTION
If any service is configured and activated at the ATM Trunk port for the IMA group, modification
of the IMA group may interrupt services. Exercise caution for this.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM
IMA Management from Function Tree.
Step 2 Click the IMA Group Management tab and modify related attributes of the IMA group. Click
Apply. A dialog box is displayed, indicating that the operation succeeds. Click Close.
----End
Issue 02 (2010-09-24)
26-17
Prerequisite
l
The IMA Protocol Enable Status of the IMA group must be Disabled.
Context
CAUTION
If any service is configured and activated at the ATM Trunk port for the IMA group, deleting
the IMA group may interrupt the services. Exercise caution for this.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Interface Management > ATM
IMA Management from the Function Tree.
Step 2 Click the Banding tab and select an IMA group. Click Delete. A dialog box is displayed,
indicating that the operation may interrupt the services. Click OK. A dialog box is displayed,
indicating that the operation is successful. Click Close.
----End
Issue 02 (2010-09-24)
Prerequisite
l
You must complete the configuration of the control plane. For configuration method, see
20 Configuring the Control Plane.
If IMA services are accessed, you must complete the configuration of an IMA group. For
configuration method, see Configuring the IMA.
You must complete the configuration of the ATM policy. For configuration method, see
15.1.9.1 Creating the ATM Policy.
You must complete the creation of a tunnel. For configuration method, see 21.2.2 Creating
an MPLS Tunnel.
Context
The OptiX RTN equipment can access services at the E1/VC-12 level or 64K timeslot level.
When the OptiX RTN equipment accesses the services at the E1/VC-12 level, all the available
timeslots of the E1/VC-12 channels are used to transport services. When the OptiX RTN
equipment accesses the services at the 64K timeslot level, one E1/VC-12 channel can be used
to transport both the ATM services and CES services (certain timeslots allocated for ATM
services and others for CES services). In this manner, the E1/VC-12 channels are used flexibly.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > ATM Service Management
from the Function Tree.
Step 2 Click New. The New ATM Service window is displayed. In the window, configure a UNIsNNI or UNI-UNI service.
Issue 02 (2010-09-24)
26-19
NOTE
l For the UNIs-NNI service, set the attributes in the Connection, PW and CoS Mapping tabs.
l For the UNI-UNI service, set only the attributes in the Connection tab.
2.
Click the Connection tab and click Add. In the window displayed, set connection attributes.
NOTE
3.
Click OK.
Issue 02 (2010-09-24)
1.
2.
Click the Connection tab and click Add. In the window displayed, set connection attributes.
3.
Click the PW tab and click Add. The Configure PW window is displayed. In the window,
set attributes of the PW.
4.
Click the General Attributes tab and set the general attributes of PW.
5.
Optional: Click the QoS tab and set the QoS attribute of PW.
6.
Optional: Click the Advanced Attributes tab and set the advanced attributes of PW.
7.
Click the CoS Mapping tab and click Add to configure the CoS mapping table.
NOTE
You can configure the CoS mapping only after configuring the parameters in the PW tab.
8.
Click OK.
Step 6 In the New ATM Service window, click OK. A dialog box is displayed, indicating that the
operation is successful. Click Close.
----End
Issue 02 (2010-09-24)
26-21
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
CAUTION
This operation causes service interruption. Exercise caution when you perform this operation.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > ATM Service Management
from the Function Tree.
Step 2 Select a created service and click the Connection tab. In the tab, click Configure Connection
to modify connection attributes of the service. Click OK. A dialog box is displayed, indicating
that the operation affects services. Click OK. A dialog box is displayed, indicating that the
operation is successful. Click Close.
Step 3 Click the PW tab. In the tab, modify PW attributes of the service. Click Apply. A dialog box is
displayed, indicating that the operation affects services. Click OK. A dialog box is displayed,
indicating that the operation is successful. Click Close.
NOTE
You can modify parameters only in the QoS and Advanced Attributes tabs of the PW, but not the
parameters in the General Attributes tab.
Step 4 Select a created service and click the CoS Mapping tab. Modify the CoS mapping attributes of
the service. Click OK. Click Apply. A dialog box is displayed, indicating that the operation
affects services. Click OK. A dialog box is displayed, indicating that the operation is successful.
Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
26-22
Issue 02 (2010-09-24)
Context
CAUTION
This operation causes service interruption. Exercise caution when you perform this operation.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > ATM Service Management
from Function Tree.
Step 2 Select a created service and click the Connection tab. In the tab, click Delete. A dialog box is
displayed indicating that the operation affects services. Click OK. A dialog box is displayed
telling you that the operation was successful. Click Close.
----End
Issue 02 (2010-09-24)
26-23
27
Issue 02 (2010-09-24)
27-1
Performs fault detection that brings light load and lasts for a short time for the channel
where the BFD session is set up.
Adopts a uniform mechanism to detect faults for any medium and any protocol layer in a
real-time manner.
Session
Before performing the BFD detection, set up the peer session at both ends of the channel. After
the session is set up, each end transmits the BFD control packets to the opposite end at the
negotiated rate.
Single-Hop Detection
The single-hop detection quickly detects and monitors the connectivity of the link of direct
connection. Single-hop detection is applicable to the scenario where the link between BFD peers
does not traverse the third-party equipment.
Diagnosis Word
The diagnosis word indicates the cause of the state change of the latest session in the local BFD
system.
27-2
Issue 02 (2010-09-24)
Prerequisite
l
The port where the BFD session can be created must be a Ethernet port configured with
Layer 3 attributes. In the case of a Lay 3 port, you must enable the MPLS.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > BFD management from the
Function Tree.
Step 2 Click New. The Create BFD dialog box is displayed.
Step 3 Set the parameters related to the BFD session.
NOTE
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > BFD management from the
Function Tree.
Step 2 Select a BFD session, and configure parameters for the BFD session.
It is recommended that you set the following parameters:
l Admin Status: Up
l Local Send Interval of Packets: 1000
l Local Receive Interval of Packets: 1000
Issue 02 (2010-09-24)
27-3
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > BFD management from the
Function Tree.
Step 2 Select a BFD session and click Query. Check the BFD session information.
NOTE
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > BFD management from the
Function Tree.
Step 2 Select a BFD session and click Delete.
Step 3 A dialog box is displayed for confirmation. Click OK.
----End
27-4
Issue 02 (2010-09-24)
28
28-1
28-2
Issue 02 (2010-09-24)
Host
(Non-multicast
member)
Host
Host
(Multicast member)(Multicast member)
Host
(Non-multicast
member)
Physical connection
Flow direction of the multicast service
Issue 02 (2010-09-24)
28-3
Signals are forwarded based on the VLAN. Hence, the information security is increased.
Quick response is made to the link fault. Hence, the reliability is enhanced.
Router Port
The router port refers to the port that faces the multicast router. The E-LAN service of the RTN
equipment takes the port that receives the IGMP query packets as the router port. The router
port consists of the following two types:
l
Dynamic router port, which relies on the protocol packets exchanged between the router
and host, and can be dynamically maintained. Each of this port can enable a router port
aging timer. When the timer times out, this router port is invalid.
Static router port, which is specified by users by using configuration commands, cannot be
aged.
Member Port
The multicast member port refers to the port that faces the host of the member. The switch
transmits the multicast packets from this port. The multicast group member port, referred to as
member port for short, consists of the following two types:
l
28-4
Dynamic member port, which can receive the IGMP report packets. This port, relies on the
protocol packets exchanged between the router and host, can be dynamically maintained.
Each of this port can enable a member port aging timer. When the timer times out, that is,
when the times of not receiving the IGMP report packets exceed certain times, this member
port becomes invalid.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
Static member port, which is specified by users by using configuration commands, cannot
be aged.
Multicast Strategy
The RTN equipment determines the member relation in this network section according to the
received IGMP group member report packet. The range of the multicast groups can be restrained
through the ACL. By default, the ACL is not set. Thus, the host can be added to any multicast
groups.
28-5
Thus, when this function is used, you should make sure that only one multicast service receive
end is connected to this port.
Multicast Forwarding
The IGMP Snooping is configured on RTN-1 and RTN-2. When the multicast packets reach
RTN-1 or RTN-2, the packets are distributed at the port, which has the group member host in
the downstream.
Figure 28-2 Multicast forwarding
Internet
/Intranet
Source
Host 1
Host 2
Group member
Host3
Group member
Host 4
Host 5
Group member
Multicast
packets
Issue 02 (2010-09-24)
forwarding. As shown in Figure 28-2, the multicast group strategy is configured on RTN-1 and
RTN-2. In this way, the range of the group addresses that can be accessed by users through the
access control list (ACL) is set. Thus, the multicast packets that can be received by the user host
can be controlled.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The E-LAN service is already created.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Protocol
Configuration > IGMP Snooping Configuration from the Function Tree.
Step 2 Click the Protocol Configuration tab to configure the required parameters. Click Apply.
NOTE
Issue 02 (2010-09-24)
28-7
Step 3 Select the multicast service that requires setting of the quickly delete member port. The lower
pane lists the multicast service.
Step 4 Configure the parameters related to the quickly delete member port for the multicast service.
The parameters include VLAN ID, Port Type and Port. Double-click the parameters to modify
them.
NOTE
To set a port for a multicast service as a quickly delete member port, the port should have only one multicast
service user. Otherwise, different users on the port affect each other when receiving multicast services.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
You must complete creation of the E-LAN service.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Protocol
Configuration > IGMP Snooping Configuration from the Function Tree.
Step 2 Click the Router Management tab. Click New to display the Create Router Port dialog box.
In the dialog box, set the required parameters and select the multicast router ports to be added.
NOTE
Prerequisite
You must be an NM user with "NE operator" authority or higher.
28-8
Issue 02 (2010-09-24)
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Protocol
Configuration > IGMP Snooping Configuration from the Function Tree.
Step 2 Click the Route Member Port Management tab, and then click New to display the Create
Member Port dialog box.
Step 3 Set parameters in the dialog box.
NOTE
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The route member port is configured.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Ethernet Protocol
Configuration > IGMP Snooping Configuration from the Function Tree.
Step 2 Click the Packet Statistics tab, and set parameters for the IGMP protocol packet statistics. Then,
click Apply.
Issue 02 (2010-09-24)
28-9
Step 3 Click Apply. The Operation Result dialog box is displayed, indicating that the operation is
successful. Click Close.
----End
28-10
Issue 02 (2010-09-24)
29
29 OAM Management
OAM Management
Issue 02 (2010-09-24)
29-1
29 OAM Management
29-2
As a low rate protocol, the Ethernet OAM protocol uses very little network bandwidth.
Hence, this function does not affect services transmitted by the link.
You can perform the OAM on the services that are encapsulated in different formats by
using the Ethernet OAM, which is irrelevant to the Ethernet encapsulation formats. You
can perform the OAM, however, on only the services of the same encapsulation format by
using traditional test frames.
The current frame test method is based on only the encapsulation format where the data of
the same type is contained. Thus, this test method is not applicable to other encapsulation
formats (such as GFP encapsulation format and HDLC encapsulation format) where the
data of different types is contained.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
29 OAM Management
The current port loopback function focuses on all packets at the port. Thus, the loopback
cannot be performed for a specific service selectively.
The OptiX RTN equipment provides the Ethernet OAM solution based on the IEEE 802.1ag
and IEEE 802.3ah protocols, as shown in Figure 29-1.
Figure 29-1 Ethernet OAM solution
IEEE 802.3ah
IEEE 802.1ag
IEEE 802.3ah
Transmission Network
IEEE 802.1ag OAM focuses on the maintenance of end-to-end Ethernet links. Based on
services, IEEE 802.1ag OAM realizes the end-to-end check by detecting each maintenance
domain successively. That is, it performs segmental management on each network segment
that is involved in the same service in the network.
IEEE 802.3ah OAM focuses on the point-to-point Ethernet link maintenance between two
sets of directly-connected equipment in Ethernet in the first mile (EFM). IEEE 802.3ah
OAM does not focus on the specific service. It maintains the Ethernet point-to-point link
by performing OAM auto-discovery, link performance monitoring, fault check, remote
loopback and selfloop check.
29-3
29 OAM Management
Maintenance Domain
In a network, the network segments focused on by users, service providers and operators are
different. Thus, the management should be based on network segment to perform maintenance
on network segments where a service passes through in the network. At the same time, different
service traffics need be managed separately.
IEEE 802.1ag OAM realizes the Ethernet maintenance by performing the end-to-end check
based on the maintenance domain. For OAM, maintenance domain is the collection of all
maintenance points (MP) in a service application. The MPs include the maintenance association
end points (MEP) and maintenance association intermediate points (MIP).
For the management segment to be maintained, establish MEPs at two ends and set the range of
the maintenance domain. Moreover, establish MIPs at other positions in this management
segment. Perform the operations on these maintenance points, including MEPs and MIPs. Based
on relations and responses among these maintenance points, the state of the whole management
segment is under control. In this way, the fault detection and location are realized.
Maintenance Association
An MA is a part of an MD. An MD can be divided into one MA or multiple MAs.
In the network of a carrier, a VLAN is corresponding to a service instance. On the equipment,
a VLAN is corresponding to an MA or multiple MAs. By dividing MAs, you can check the
connectivity of the network that transmits a certain service instance and detect faults of the
network.
29-4
Issue 02 (2010-09-24)
29 OAM Management
The level of an MA is the same as the level of the MD to which the MA belongs.
Maintenance Point
The maintenance point (MP) refers to function entity of IEEE 802.1ag OAM, including the
maintenance end point (MEP) and maintenance intermediate point (MIP).
Each maintenance point has a maintenance point identification (MPID), and this ID is unique
in the entire network. The information of each maintenance point is recorded in the MAC address
table, maintenance point table and route table. The key contents contained in the MP
configuration information are the service type, service ID and VLAN tag. In the case of nonstandard MP, once a maintenance point is created successfully, it transmits the protocol packets
where the MP information is contained to the entire network periodically in the form of
broadcasting. After receiving these protocol packets, other maintenance points record the
information for backup.
l
Issue 02 (2010-09-24)
29-5
29 OAM Management
According to some special operational codes or destination MAC addresses, choose one
of the following processing methods.
Transparent transmission
Transparent transmission and processing
Extract and process all OAM message packets that belong to this MIP layer
According to some special operational codes, discard all OAM message packets whose
level is lower than the level of this MIP layer.
NOTE
Only the MEP can initiate the OAM operations, while the MIP cannot initiate any OAM operation or send
any OAM packet.
Layered Management
IEEE 802.1ag OAM adds the management level fields to OAM protocol packets. In this way,
the layered management is realized. The higher management domain can cross the lower
management domain, but the lower management domain cannot cross the higher management
domain. Based on such layered management, the maintenance of a service traffic can be realized
segmentally. Moreover, the management of different service traffics can be realized as well.
Figure 29-2shows the logical diagram of the maintenance domain layer relation.
Figure 29-2 Logical diagram of maintenance domain layers
CE
a
CE
f
Customer ME Level
Service Provider ME Level
Operator ME Level
Physical ME Level
Bridge with Bridge Ports
Maintenance End Ports
Maintenance Intermediate Points
AIS Convergence Function
Logical path of
CFM Messages
Maintenance
Entities
Currently, the protocol supports the eight-layer division from layer 0 to layer 7. Eight
maintenance entities (ME) levels correspond to the user, supplier or operator accordingly.
29-6
Issue 02 (2010-09-24)
29 OAM Management
Layer levels from the higher to the lower: user ME level > Supplier ME level > Operator ME
level.
The dashed lines in the diagram show the logic channels where IEEE 802.1ag OAM packets
pass through. Methods for maintenance points at different layers to process OAM protocol
packets are as follows.
l
For the OAM protocol packets whose level is higher, the maintenance point processes them
transparently.
For the OAM protocol packets whose level is lower, the maintenance point discards them
directly.
For the OAM protocol packets whose level is the same, the maintenance point gives
response or ends the packets accordingly to messages types of the OAM protocol packets.
Continuity Check
The connectivity between maintenance end points (MEPs) are detected through continuity check
messages (CCMs) that are transmitted between MEPs periodically. This detection is named as
continuity check (CC). You can check the link status in one direction by performing the CC.
The application scenario is as follows: The link status is checked in real time.
l
After receiving the CCM packets from the source MEP, the sink MEP directly enables the
CC function that focuses on this source MEP.
If the sink MEP fails to receive the CCM packets from the source MEP within a check
period, the non-standard MP reports the EX_ETHOAM_CC_LOS alarm automatically
until the link is recovered, and the standard MP reports the ETH_CFM_LOS alarm. That
is, the sink MEP does not clear the alarm until it receives the CCM packets from the sink
MEP.
Loopback Test
The loopback (LB) can be used to test the state of any MP link from the source MEP to the
maintenance domain.
The application scenario is as follows: The location or check is performed on one end.
l
The loopback (LB) can be used to test the state of any node link from the source to the
maintenance domain. For the non-standard MP, as the sink MP can be the MIP, the loopback
can be used to locate the faults.
Compared with the continuity test, the loopback test is not a continuous test. Thus, you
need start the test manually each time.
29-7
29 OAM Management
PING
OAM ping test provides the online test. By using this function, you can simulate the packet loss
ratio and delay period of a service, which are caused by bit errors. Besides the continuity test,
the OAM-Ping test further manages the performance of the Ethernet link at the MAC layer.
The application scenario is as follows: The service performance is checked in real time.
l
The OMA_Ping test provides a method to test the in-service packet loss ratio and hold-off
time that result from bit errors. Compared with the continuity test, the OAM_Ping test
provides more detailed and accurate OAM information.
In this case, the OAM not only ensures the service continuity, but also detects the packet
loss and service delay to a greater extent.
AIS Activation
The alarm indication signal (AIS) is used to report errors to a superstratum node during Ethernet
OAM. When the AIS is active, errors can be reported. If the AIS is inactive, errors cannot be
reported.
Performance Check
After the connectivity between the MPs of the processing boards of Ethernet services is checked,
the performance check realizes the on-line test of the packet loss ratio and delay time of the
services.
OAM Auto-Discovery
By exchanging the information OAM protocol data unit (OAMPDU) periodically, the equipment
at local end is informed that the opposite end supports the IEEE 802.3ah OAM protocol.
The application scenario is as follows: OAM auto-discovery is a prerequisite to realize the link
performance monitoring and remote loopback. The following functions are available at the port
only when the OAM auto-discovery succeeds: link performance monitoring and loopback. If
the OAM auto-discovery fails, the ETHOAM_DISCOVER_FAIL alarm is reported.
Issue 02 (2010-09-24)
29 OAM Management
Triggering condition of error frame events: Within a period of the error frame monitor
window, the number of actually received error frames is larger than the configured threshold
value.
NOTE
The period of the error frame monitor window indicates the time period for each error frame statistics.
Triggering condition of error frame second events: Within the specific seconds, the detected
error frame seconds is larger than defined threshold value.
NOTE
When the error frame number is larger than 0 within a second, this second is called an error frame
second.
Triggering condition of error frame period events: Among the received frames of a specific
amount, the number of error frames is larger than defined threshold value.
The link performance monitoring function is used to precisely analyze and monitor the link
performance within a specific range.
According to actual requirements, you can configure window values and threshold values
of three link performance events respectively on the U2000. In this case, whether the link
performance degrades to the threshold can be detected.
Remote Loopback
The OAM entity at the local end transmits the loopback control OAMPDU packets to the remote
OAM for applying for the loopback. According to loopback data analysis, the fault locating and
link performance test are performed. The IDU 620 do not support responding the remote
loopback, the IDU 605 support responding the remote loopback.
The application scenario is as follows: The loopback is a method to locate the faults and test the
performance. Compare the number of transmitted packets with that of received packets in
loopback. The result can be used to detect link performance and link faults in this link
bidirectionally from the loopback initiation end to the loopback response end.
Self-Loop Test
After the self-loop test function is enabled on an Ethernet service processing board, you can
detect the self-loop that occurs when the fiber in the transmit direction of a port is connected to
the same port in the receive direction, and the intra-board loopback between two connected port
on the same board.
The application scenario is as follows: When the self-loop function is enabled at all ports on the
equipment, the ring network that is available during the networking can be detected. Moreover,
the ETHOAM_SELF_LOOP alarm is reported.
29.1.3 Availability
The ETH-OAM feature requires the support of the applicable equipment and boards.
Issue 02 (2010-09-24)
29-9
29 OAM Management
Applicable Equipment
EMS6
RTN 620
EFP6
EM4T
RTN 605
Applicable Equipment
IFU2
IFX2
EM4T
RTN 910/950
EM4F
EM6T
EM6F
CSHA
CSHB
RTN 910
CSHC
29-10
Issue 02 (2010-09-24)
29 OAM Management
VLAN Tag
Ether Type(OAM)
Type
VER
OAM Type
Length
Service-ID
OAM Date
OAM Mac destination address: Indicates the MAC address of the destination MP.
OAM Mac source address: Indicates the MAC address of the source MP.
Ether type (VLAN): Indicates the Ethernet data type, such as 0x8100.
Ether Type (OAM): Indicates the packet type of the ETH-OAM protocol. The standard
IEEE The packet type of 802.1ag OAM protocol is 0x8902. The non-standard (Huawei,
Draft 3.0)IEEE The packet type of 802.1ag OAM protocol is 0x8809.
OAM type: Indicates that the MP differs and responds to various OAM operations
according to types of OAM packets. OAM For mapping relation between values and OMA
packet types, refer to Table 29-3.
Table 29-3 Mapping relation between values and OMA packet types (non-standard MP)
Issue 02 (2010-09-24)
OAM Type
OAMPDU
Usage
Loopback test
Continuity test
MAC query
Loopback test
MacAck
MacBroadcast
29-11
29 OAM Management
Continuity Check
The source MEP constructs the continuity check message (CCM) packets and transmits them
periodically. After receiving the CCM packets from the source MEP, the sink MEP directly
enables the CC function that focuses on this source MEP.
If the sink MEP fails to receive the CCM packets from the source MEP within a check period,
it reports the alarm automatically until the link is recovered. That is, the sink MEP does not clear
the alarm until it receives the CCM packets from the sink MEP.
As shown inFigure 29-4, the CC function of the MEP1 is enabled. The MEP1 transmits the
CCM packets externally. After receiving the first CCM packet, the MEP2, MEP3 and MEP4 in
the same maintenance domain start the timer respectively to receive all CCM packets from the
MEP1 periodically. Once the link is faulty, the sink MEP fails to receive the CCM packets within
a check period. In this case, the sink MEP reports the EX_ETHOAM_CC_LOS alarm. The alarm
is not cleared until the link is recovered.
Figure 29-4 Continuity check diagram
MEP1
VB
MEP2
VB
MEP4
VB
MEP3
When the CC function is enabled at MEP1, MEP2, MEP3 and MEP4 at the same time, each
MEP is both the source end and sink end for the CC function. In this way, the bidirectional
continuity test is realized.
NOTE
Only the MEP can enable the continuity check and be the receive respond end for the check.
Loopback Test
Based on the bidirectional service, the loopback is a test performed manually at a time. The
source MEP constructs the loopback message (LBM) packets and adds the destination MP (MIP
or MEP) IDs to the packets. When the packets are transmitted, the timer is started.
After receiving the LBM packets, the sink MP constructs the loopback return (LBR) packets
and transmits them back to the source MEP. In this case, the loopback succeeds. If the source
MEP timer expires and fails to receive the LBR from the sink MP, the loopback fails.
As shown in Figure 29-5, the MEP1 transmits the LBM packets to the sink MEP2. After
receiving the packets, the MIP2 and MIP3 in the same maintenance domain detect that the sink
29-12
Issue 02 (2010-09-24)
29 OAM Management
MPIDs contained in the packets are different from those of them. In this case, the MIP2 and
MIP3 transparently transmit the packets. After receiving the packets, the sink MEP2 transmits
the LBR packets back to the source MEP1. At this moment, the loopback is complete.
Figure 29-5 Loopback test diagram
MEP1
MIP2
MIP3
MEP4
LBM
LBR
NOTE
For the non-standard IEEE 802.1ag OAM, only the MEP can initiate the loopback test, while both the MEP
and MIP can be the receive end in the test.
Issue 02 (2010-09-24)
29-13
29 OAM Management
MEP1
1
MIP2
MIP3
MEP4
LTR
LTM
LTR
LTM
LTR
LTM
1.
The source MEP1 transmits the LTM packets to the destination MEP4.
2.
After receiving the LTM packets, the MIP2 transmits the LTR packets to the source MEP1
and forwards the LTM packets at the same time.
3.
After receiving the LTM packets, the MIP3 transmits the LTR packets to the source MEP1
and forwards the LTM packets at the same time.
4.
After receiving the LTM packets, the destination MEP4 concludes the LTM packets and
transmits the LTR packets to the source MEP1.
NOTE
Only the MEP can initiate the link trace test and be the termination of the test.
OAM_Ping Test
The OAM_Ping test includes:
l
MPID-Ping: In the case that both the Ethernet service processing boards of Huawei
equipment at two ends support the IEEE 802.1ag OAM protocol, the ping test is initiated
from the maintenance point on the local Ethernet service processing board to that on the
opposite board.
IP-Ping: In the case that both the equipment at two ends supports the ARP protocol and
ICMP protocol, only the Huawei equipment can initiate the ping test. Moreover, the Huawei
equipment does not respond to the ping test of the opposite end.
The transmit end in OAM_Ping acquires the IP address of the maintenance point first, and then
constructs the ARP packets and ICMP packets for transmission. The maintenance point that
receives the ARP packets or ICMP packets analyzes the packets and then transmits the response
packets back to the transmit end. After receiving the response packets, the OAM_Ping transmit
end reports the test results of the OAM_Ping according to the information contained in the
response packets. The results include the packet loss ratio and delay information.
Issue 02 (2010-09-24)
29 OAM Management
Octets
6
Type
Subtype
Flags Field
Code
42-1496
Data/Pad Field
Mac Destination Address: Indicates the low-speed protocol multicast address whose value
is fixed to 0x01-80-C2-00-00-02.
Type: Indicates the low-speed protocol type whose value is fixed to 0x8809.
Subtype: Indicates that the specified type of the low-speed protocol is IEEE 802.3ah OAM,
which is fixed to 0x03.
Flags Filed: Includes some important state information such as link fault, dying gasp,
critical event. The realization of the fault locating depends on the state information
mentioned previously.
Code: Identifies the IEEE 802.3ah OAM protocol packets of different types. The main
packet types are information OAMPDU, event notification OAMPDU and loopback
control OAMPDU. They are corresponding to OAM auto-discovery, link performance
monitoring and remote loopback respectively. For the mapping relation between code
values and OAM packet types, see Table 29-4.
Table 29-4 Mapping relation between code values and OAM packet types
Issue 02 (2010-09-24)
Code
OAMPDU
Usage
0x00
Information
0x01
Event notification
29-15
29 OAM Management
Code
OAMPDU
Usage
0x02
Variable request
0x03
Variable response
0x04
Loopback control
0x05-0x
FD
Reserved
Reserved.
0xFE
Organization specific
0xFF
Reserved
Reserved.
Data/Pad Field: Indicates the OAMPDU data whose fields can be extended, with a length
range from 42 bytes to 1496 types. When the OAMPDU packet length is less than the
minimum 64 bytes, the extended bytes are contained in the field.
Auto-Discovery
As shown in Figure 29-8, the Code filed of the OAMPDU is 0x00. This indicates that the
OAMPDU is the information OAMPDU and used for OAM auto-discovery.
29-16
Issue 02 (2010-09-24)
29 OAM Management
Octets
Fields
Fixed Values
Destination Address
01-80-c2-00-00-02
Source Address
Length/Type
88-09
Subtype
0x03
Flags
Code
Octets
Fields
1
1
1
2
1
1
2
3
4
Information Type
Information Length
OAM Version
Revision
State
OAM Configuration
OAMPDU Configuration
OUI
Vendor Specific Information
0x01
0x10
0x01
0x00
42-1496 Data/Pad
4
Fixed
Values
FCS
INFORMATION
OAMPDU
1
1
1
2
1
1
Information Type
Information Length
OAM Version
Revision
State
OAM Configuration
2
3
4
OAMPDU Configuration
OUI
Vendor Specific Information
0x02
0x10
0x01
REMOTE INFORMATION
TLV
1
1
1
2
Information Type
Information Length
OUI
Organization Specific Value
0xFE
ORGANIZATION
SPECIFIC
INFORMATION TLV
The Data field of the information OAMPDU includes local information type-length-value (TLV)
domain and remote information type-length-value (TLV) domain. A OAM configuration byte
is contained in the TLV domain. When the link is normal, successful OAM auto-discovery
depends on information of bit digits in the OAM configuration bytes. Also, the information of
bit digits decides what functions are performed after OAM auto-discovery succeeds.
Table 29-5 lists details of OAM configuration bytes.
Issue 02 (2010-09-24)
29-17
29 OAM Management
Name
Description
7 to 5
Reserved
Variable Retrieval
Link Events
29-18
Issue 02 (2010-09-24)
29 OAM Management
Bit Digit
Name
Description
Unidirectional Support
OAM Mode
Issue 02 (2010-09-24)
29-19
29 OAM Management
Table 29-6 Mapping relation between OAM working modes and OAM functions
OAM Capability
OAM Mode
Active Mode
Passive Mode
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
No
Yes
Yes
Permitted to send
organization specific
OAMPDUs
Yes
Yes
When the IEEE 802.3ah OAM protocol is enabled for the port on the Ethernet service processing
board, the information OAMPDU is broadcast periodically. At the same time, the information
OAMPDU from the opposite port is received and processed. In this way, two peer ends exchange
the OAM information (including OAM configuration information and OAM state information)
to establish the OAM connection between two ends.
29-20
Issue 02 (2010-09-24)
29 OAM Management
Fields
Sequence Number
SEQUENCE NUMBER
Event Type
Event Length
Event Time Stamp
Errored Svmbol Window
Errored Svmbol Threshol
Errored Svmbol
Error Running Total
Event Running Total
1
1
2
8
8
8
8
4
Octets
Fields
Fixed Values
Destination Address
01-80-c2-00-00-02
Source Address
Length/Type
88-09
Subtype
0x03
Flags
Code
0x01
42-1496 Data/Pad
4
FCS
ENENT
NOTIFICATION
OAMPDU
Fixed
Values
0x01
0x28
To perform performance statistics from different aspects, the link performance monitoring is
classified into bit error event monitoring, error frame second event monitoring, error frame
period event monitoring.
l
Issue 02 (2010-09-24)
Triggering condition of error frame events: Within a period of the error frame monitor
window, the number of actually received error frames is larger than the configured threshold
value.
29-21
29 OAM Management
Triggering condition of error frame second events: Within the specific seconds, the detected
error frame seconds is larger than defined threshold value.
Triggering condition of error frame period events: Among the received frames of a specific
amount, the number of error frames is larger than defined threshold value.
When the IEEE 802.3ah OAM protocol is enabled at a port, the protocol queries the RMON
statistic count of the hardware chip periodically to acquire the information such as the number
of accurate packets and the number of error packets. You can find out whether the preceding
three performance events occur or not according to corresponding processing of these
information. In the case that a performance event occurs, the opposite end is informed of this
event over the event notification OAMPDU. After receiving the notification, the opposite
equipment reports the ETHOAM_RMT_SD alarm for maintenance personnel to perform
troubleshooting.
Remote Loopback
As shown in Figure 29-10, the code filed of the OAMPDU is 0x04. This indicates that the
OAMPDU is the loopback control OAMPDU and used for the loopback test.
Figure 29-10 Packet format of the loopback control OAMPDU
Octets
Fields
Fixed Values
Destination Address
01-80-c2-00-00-02
Source Address
Length/Type
88-09
Subtype
0x03
Flags
Code
1+41
4
0x04
Data/Pad
Octets
Fields
Fixed
Values
0x01
ENABLE REMOTE
LOOPBACK COMMAND
FCS
LOOPBACK
CONTROL OAMPDU
0x02
DISABLE REMOTE
LOOPBACK COMMAND
The loopback transmit end transmits the loopback control OAMPDU packets to the opposite
end first. After receiving the packets, the opposite end checks whether it can respond to the
remote loopback first. If it can respond to the remote loopback, the opposite end starts remote
loopback and transmits a response packet back to the end that initiates the loopback at the same
time.
After receiving the response packets from the response end, the transmit end analyzes the packets
to confirm that the opposite end is in the response loopback state. Then the transmit end starts
the loopback. In this way, the whole process of loopback initiation is complete.
Self-Loop Test
The self-loop test is a function developed by Huawei on the basis of IEEE 802.3ah protocol.
29-22
Issue 02 (2010-09-24)
29 OAM Management
The self-loop test packets are constructed as the IEEE 802.3ah OAM protocol packets, with a
packet type of protocol reservation type 6. The first eight significant reserved bits in the flag
fields are used to carry the ID of the transmit port.
When the self-loop test is enabled at a port, the specified self-loop check packets are transmitted
from the port. One packet is transmitted each second.
When a port receives the self-loop check packets, it compares the source MAC address carried
in the packets with its own MAC address. If the former MAC address is the same with the later,
it indicates that the local port and the opposite port are located in the same Ethernet service
processing board. At this moment, further compare IDs of two ports. If the IDs are the same,
they are the same port actually. In this case, this indicates the port self-loop. If the IDs are
different, it indicates the intra-board port self-loop.
29-23
29 OAM Management
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The board that supports the creation of the MD must be created.
Procedure
Step 1 In the case of RTN 600 NEs:
1.
In the NE Explorer interface, select an NE, and choose Configuration > Ethernet
Maintenance > Ethernet Service OAMfrom the Function Tree.
2.
In the right-hand pane, click OAM Configuration to display the OAM Configuration
dialog box.
NOTE
In the NE Explorer interface, select an NE, and choose Configuration > Ethernet OAM
Management > Ethernet Service OAM Managementfrom the Function Tree.
Step 3 Click New and select Create MD from the drop-down list.
Step 4 In the New Maintenance Domain dialog box displayed, configure the corresponding
parameters.
Step 5 ClickApply.
Step 6 Click Close.
----End
29-24
Issue 02 (2010-09-24)
29 OAM Management
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Ethernet services must be already created.
The MD must be created.
Procedure
Step 1 In the case of RTN 600 NEs:
1.
In the NE Explorer interface, select an NE, and choose Configuration > Ethernet
Maintenance > Ethernet Service OAMfrom the Function Tree.
2.
Click OAM Configuration in the right window to display the OAM Configuration dialog
box.
NOTE
In this user interface, you can create or delete OAM maintenance Association (MAs).
3.
4.
In the dialog box of New Maintenance Association displayed, configure the OAM
parameters.
5.
ClickApply. The Operation Result dialog box is displayed, indicating that the operation
was successful.
6.
Click Close.
2.
Click New. Select New Maintenance Association to display the New Maintenance
Association dialog box.
3.
4.
Click Apply. The Operation Result dialog box is displayed, indicating that the operation
was successful.
5.
Click Close.
----End
Issue 02 (2010-09-24)
29-25
29 OAM Management
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet service must be created and activated.
The MA and MD must be created before creating a stadard MP.
Precaution
In an OAM test, all maintenance points that are involved in the operating of the same service
flow must be in the same maintenance domain. In an existing maintenance domain involved in
the same service flow, creating a maintenance point of the same level or a higher level may
damage the existing maintenance domain. As a result, the OAM test fails.
Procedure
Step 1 In the case of RTN 600 NEs:
1.
In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet
Maintenance > Ethernet Service OAM from the Function Tree.
2.
Click New and the Create MP dialog box is displayed. Complete the information.
NOTE
l VLAN ID: Leave this field blank for PORT services. For PORT+VLAN services, set the VLAN
ID of the services to be monitored.
l Service Direction: Only MEPs have the directions.
3.
Optional: Click Advanced. In the dialog box displayed, set the corresponding parameters
and click OK.
NOTE
If an MEP is created, you can choose whether to perform the following configuration.
l Activate the CC and configure the sending period of the CC test.
l Set the timeout time for the LB or LT test.
4.
Click OK. A prompt is displayed indicating that the operation is successful. Click Close
to finish the operation.
Step 2 In the case of RTN 900 NEs: Creating a MEP Maintenance Point
29-26
Issue 02 (2010-09-24)
29 OAM Management
NOTE
Ethernet OAM detects the connectivity of an channel based on the maintenance end points (MEP) at two
ends of the channel. MEP is the source and sink of all the Ethernet OAM packets and it is the end point
that forms the maintenance association (MA). After an MEP is successfully created, users can check the
connectivity of a segment within an MA.
1.
2.
Click New. Select New MEP Point to display the New MEP Maintenance Point dialog
box.
3.
l Direction: Ingress indicates that packets are transported to the network side. Egress indicates that
packets are transported to the user side.
l CC Status: When it is set as Active, the link can be checked in a real-time manner.
4.
Click Apply. The Operation Result dialog box is displayed, indicating that the operation
was successful.
5.
Click Close.
Step 3 In the case of RTN 900 NEs: Adding a Remote MEP of the MA
NOTE
This section describes how to add a remote maintenance end point (MEP) of the maintenance association
(MA). When processing OAM packets, the remote MEP checks whether the OAM packets are transmitted
by the MEP in the same MA.
1.
2.
Click OAM and choose Manage Remote MEP Point from the drop-down menu. The
Manage Remote Maintenance Point dialog box is displayed.
3.
Click New and the Add Maintenance Association Remote Maintenance Point dialog
box is displayed.
4.
5.
Click Apply. The Operation Result dialog box is displayed, indicating that the operation
is successful.
6.
Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The MEP maintenance point must be created.
Only the MEP can have the CC test enabled and work as the receiving and responding end in
the test.
Issue 02 (2010-09-24)
29-27
29 OAM Management
Context
l
During the CC check, the source MEP constructs and transmits CC frames periodically.
The destination MEP receives the CC frames and starts the CC check. If the destination
MEP does not receive the CC frames from the source within a specified period of time (for
example, 3.5 times the transmit period), the standard MP automatically reports the
ETH_CFM_LOS alarm and the Huawei MP automatically reports the
EX_ETHOAM_CC_LOC alarm.
Procedure
Step 1 In the case of RTN 600 NEs:
1.
In the NE Explorer, click an Ethernet board and choose Configuration > Ethernet
Maintenance > Ethernet Service OAM from the Function Tree.
2.
Select the node that you want to monitor, click OAM Operation and select Activate
CC. A prompt is displayed indicating that the operation is successful. Click Close.
TIP
l Alternatively, you can select a node, right-click, and then choose Activate CC from the shortcut
menu to start the CC test.
l You can select a node, right-click, and then choose Inactivate CC from the shortcut menu to
stop the CC test.
NOTE
Before you perform the check, set an appropriate CCM Sending Period (ms) as required.
2.
Select Maintenance Domain, and select Maintenance Association. Select MEP Point.
3.
Click OAM and choose Activate CC from the drop-down menu, The Operation Result
dialog box is displayed indicating that the operation is successful.
4.
Click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The source and sink MEPs, and MIPs in the same maintenance domain must be created.
29-28
Issue 02 (2010-09-24)
29 OAM Management
Only MEPs can initiate the LB test, and the MEP can work as the receive end in the test. For
the non-standard protocol, the MIP also can work as the receive end in the test.
The CC function must be enabled before the LB test can be performed on a standard MP.
Context
During the LB check, the source MEP constructs and transmits the LBM frames and starts the
timer. If the destination MP receives the LBM frames, it sends the LBR frames back to the source
MEP. This indicates that the loopback is successful. If the source MEP timer times out, it
indicates that the loopback fails.
Procedure
Step 1 In the case of RTN 600 NEs:
1.
In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet
Maintenance > Ethernet Service OAM from the Function Tree.
2.
Select the node that you want to monitor, click OAM Operation and select Start LB. The
LB Test dialog box is displayed.
3.
Enter the LB test source maintenance point ID and sink maintenance point ID.
4.
Alternatively, you can select a node, right-click, and then choose Start LB from the shortcut menu
to start the LB test.
NOTE
2.
Select Maintenance Domain, and select Maintenance Association. Select MEP Point.
3.
Click OAM and choose Start LB from the drop-down menu. The LB Test dialog box is
displayed.
4.
5.
Click Start Test. The Operation Result dialog box is displayed, indicating that the
operation is successful.
6.
----End
29-29
29 OAM Management
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The source and sink MEPs, and MIPs in the same maintenance domain must be created.
Only MEPs can initiate the LT test and work as the termination point in the test.
In the case of a standard MP, you must activate CC before LT check.
Context
l
During the LT check, the source MEP constructs and transmits LTM frames and starts the
timer. All the MPs that receive the LTM frames send the LTR frame response. According
to the LTR frame response, you can verify all the MIPs that pass from the source MEP to
the destination MEP.
Procedure
Step 1 In the case of RTN 600 NEs:
1.
In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet
Maintenance > Ethernet Service OAM from the Function Tree.
2.
Select the node that you want to monitor, click OAM Operation and select Start LT. The
LT Test dialog box is displayed.
3.
Enter the LT test source maintenance point ID and sink maintenance point ID.
4.
Alternatively, you can select a node, right-click, and then choose Start LT from the shortcut menu
to start the LT test.
NOTE
29-30
1.
2.
Select Maintenance Domain, and select Maintenance Association. Select MEP Point.
3.
Click OAM and choose Start LT from the drop-down menu. The LT Test dialog box is
displayed.
4.
5.
Click Start Test. The Operation Result dialog box is displayed, indicating that the
operation is successful.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
6.
29 OAM Management
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The source and sink MEPs and MIP must be created in the same maintenance domain (MD).
Procedure
Step 1 In the NE Explorer, select the Ethernet board, choose the Configuration > Ethernet
Maintenance > Ethernet Service OAM from the function tree.
Step 2 Select the node to be monitored. Double-click AIS Active State and then select Active or
Deactive, or right-click the AIS Active State and then choose Active or Deactive from the
shortcut menu.
Step 3 Click Apply.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The OAM maintenance node of a service must be created for an Ethernet board. The type of the
maintenance node is MEP.
The MEP where the ping test is initiated must be created on an external physical port.
The tag attribute of the external physical port where the MEP resides must be Access.
Context
l
The ping test can be initiated only from the Ethernet service processing board to the
interconnected data communication equipment.
The ping test is performed in the direction from the board to which the MEP belongs to the
interconnected data communication equipment of the board.
A legal IP address is allocated to the MEP, and the IP addresses of the MEP and the
interconnected data communication equipment must be in the same network segment.
By default, the IP address of an MP is 0.0.0.0.
The IP address of an MP cannot be any of the following:
Issue 02 (2010-09-24)
29-31
29 OAM Management
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet
Maintenance > Ethernet Service OAM from the Function Tree.
Step 2 Optional: Click Query to query OAM information from the NE.
Step 3 Select a node, click OAM Operation and select Start Ping. The Ping Test window is displayed.
TIP
To display the Ping Test window, you can also right-click a node and choose Start Ping from the shortcut
menu.
l The value entered in Local IP Address is the IP address of the local maintenance point.
l Set legal IP addresses for Local IP Address and Destination IP Address and make sure that the two
IP addresses in the same network segment.
Step 6 Click Start Ping and view the returned result in the Detail pane.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The source and sink MEPs, and MIPs in the same maintenance domain must be created.
Context
29-32
The source maintenance point that initiates a performance test must be an MEP. The sink
maintenance point that responds to the performance test can be an MEP or MIP.
Issue 02 (2010-09-24)
29 OAM Management
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet
Maintenance > Ethernet Service OAM from the Function Tree.
Step 2 Optional: Click Query to query OAM information from the NE.
Step 3 Select a node, click OAM Operation and select Performance Detect. The Performance
Detect window is displayed.
TIP
To display the Performance Detect window, you can also right-click a node and choose Performance
Detect from the shortcut menu.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Issue 02 (2010-09-24)
29-33
29 OAM Management
Context
The OAM auto-discovery is realized through the auto-negotiation between the local equipment
and the opposite equipment. If the negotiation fails, the local equipment reports an alarm. After
the OAM auto-discovery succeeds, the link performance is performed according to the error
frame threshold. You can set the error frame threshold on the U2000.
l
The OAM mode includes the active mode and the passive mode. For two interconnected
systems, the OAM mode of one system must be the active mode. Otherwise, the OAM
auto-discovery fails.
if the OAM modes of the two systems are both active modes, a link fault occurs, or one
system fails to receive the OAM protocol message, an alarm is reported, indicating that the
OAM auto-discovery fails.
Procedure
Step 1 In the case of RTN 600 NEs, select an Ethernet board in the NE Explorer and choose
Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree. Click
.
Step 2 In the case of RTN 900 NEs, click the NE in the NE Explorer and choose Configuration >
Ethernet OAM Management > Ethernet Port OAM Management from the Function Tree.
Click
Step 3 Click the OAM Parameter tab, Set OAM Working Mode. In the Enable OAM Protocol dropdown list, select Enabled.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Make sure that the OAM auto-discovery succeeds.
29-34
Issue 02 (2010-09-24)
29 OAM Management
Context
When the OAM auto-discovery succeeds at the two ends, the link fault detection and
performance detection are automatically started.
l
To report the detected link fault event to the opposite equipment, Remote Alarm Support
for Link Event must be set to Enabled for the local equipment.
To report the detected link fault event to the opposite equipment, the following operations
must be performed for the local equipment.
Set Remote Alarm Support for Link Event to Enabled.
Set Error Frame Period Window (Frame) and Error Frame Monitor Threshold.
After Remote Alarm Support for Link Event is set to Enabled at the opposite port, if
the opposite end detects link performance degradation, you can query the
ETHOAM_RMT_SD alarm , which is reported on the local end, by using the U2000. Based
on the alarm, you can determine the type of the link performance event.
After Remote Alarm Support for Link Event is set to Enabled at the opposite port, if
the opposite equipment detects a link fault event or encounters a fault that makes the
equipment fail to be restored (such as a power failure), you can query the
ET_RMT_CRIT_FAULT alarm, which is reported at the local end, by using the U2000.
Based on the alarm, you can determine the fault type.
Procedure
Step 1 In the case of RTN 600 NEs, select an Ethernet board in the NE Explorer and choose
.
Step 2 In the case of RTN 900 NEs, click NE in the NE Explorer and choose Configuration > Ethernet
OAM Management > Ethernet Port OAM Management. Click
Step 3 Click the OAM Parameter tab. Set Remote Alarm Support for Link Event to Enabled.
29.1.6.3 Modifying the Parameters of the OAM Error Frame Monitoring Threshold
The threshold for the OAM error frame monitoring is a standard for the OAM to detect the link
performance. Usually, the default value is used. You can modify the value according to the
situation of the link.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Issue 02 (2010-09-24)
29-35
29 OAM Management
The IEEE 802.3ah OAM function must be enabled on the remote equipment.
Context
After the OAM auto-discovery succeeds, set Error Frame Period Window (Frame) and Error
Frame Monitor Threshold, and set Remote Alarm Support for Link Event to Enabled for the
local equipment. If the local equipment detects a link event in the receive direction, it informs
the opposite equipment of the link event. If the remote alarm for the link event is also supported
on the opposite end, the opposite equipment can also inform the local equipment of the link
event that is detected on the side of the opposite end. Then, the ETHOAM_RMT_SD alarm is
reported on the local end, prompting the maintenance personnel to handle the link event.
Procedure
Step 1 In the case of RTN 600 NEs:
1.
In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet
Maintenance > Ethernet Port OAM from the Function Tree. Click the OAM Error
Frame Monitor tab.
2.
3.
Click Apply. A prompt appears indicating that the operation was successful.
4.
Click Close.
In the NE Explorer, select the NE and choose Configuration > Ethernet OAM
Management > Ethernet Port OAM Management from the Function Tree. Click the
OAM Error Frame Monitor tab.
2.
l Error Frame Monitor Window: If the number of error frames on the link crosses the error frame monitor
threshold in the specified error frame monitor time window, the performance event is reported.
l Error Frame Period Window: If the number of error frames on the link crosses the error frame period
monitor threshold in the error frame period monitor window, the performance event is reported.
l Error Frame Second Window: If the number of error frame seconds on the link crosses the error frame
second monitor threshold in the specified error frame second monitor time window, the performance
event is reported.
l Error Frame Signal Periodic Monitor Window: In a specified number of signals, if the number of error
signals on the link crosses the defined threshold, the performance event is reported.
3.
Click Apply. A dialog box is displayed, indicating that the operation was successful. Click
Close.
----End
29-36
Issue 02 (2010-09-24)
29 OAM Management
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Make sure that the OAM auto-discovery succeeds.
For the equipment where the loopback is initiated, OAM Working Mode must be set to
Active.
The equipment that responds to the loopback must have the capability of supporting the remote
loopback.
Context
l
The IDU 620 do not support responding the remote loopback, and the IDU 605 support
responding the remote loopback.
After the remote loopback function is enabled, normally, service packets, except the
OAMPDU, are looped back at the remote end.
After using the remote loopback function to complete the fault locating and the link
performance detection, you should disable the remote loopback function at the end where
the loopback is initiated and then restore the services. At this time, the alarm is automatically
cleared.
Procedure
Step 1 In the case of RTN 600 NEs:
1.
In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet
Maintenance > Ethernet Port OAM. Click
2.
Click OAM Parametertab. Select the port that needs to initiate a loopback, and choose
Enable Remote Loopback from the drop-down list of OAM.
3.
Click Apply.
In the NE Explorer, select the NE and choose Configuration > Ethernet OAM
Management > Ethernet Port OAM Management.
2.
3.
Select a port and click Query. A dialog box is displayed, indicating that the operation is
successful. Click Close.
----End
Issue 02 (2010-09-24)
29-37
29 OAM Management
Prerequisite
You must be an NM user with "NE operator" authority or higher.
All the external physical ports of the Ethernet service processing board are enabled.
Context
When the self-loop detection is enabled for an external physical port, if the self-loop situation
occurs at the port, the ETHOAM_SELF_LOOP alarm is reported.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet Interface
Management > Ethernet Interface. Click
2.
3.
Click Apply.
----End
Issue 02 (2010-09-24)
29 OAM Management
Provide the query based on requirements and the consecutive detection so that at any
moment you can learn whether the monitored LSP has defects.
Detect, analyze, and locate any defect that occurs, and notify the U2000 of the relevant
information.
ITU-T Y.1731 OAM functions and mechanisms for Ethernet based networks
29-39
29 OAM Management
CV/FFD
You can check the connectivity of a label switch path (LSP) by performing a connectivity
verification (CV) or fast failure detection (FFD). The process of a CV is consistent with that of
an FFD. The difference lies in that the CV transmits CV packets at the frequency of 1 frame per
second and the frequency cannot be set, but the FFD transmits FFD packets at a frequency that
can be self-defined. Figure 29-11 shows the process of a CV and an FFD.
Figure 29-11 Connectivity check of the MPLS OAM
Transit
LSR
CV/FFD
CV/FFD
Ingress
LSR
Egress
LSR
BDI
BDI
Transit
LSR
1.
The ingress node transmits CV or FFD packets, and the transit node transparently transmits
packets. The packets reach the egress node through the detected LSP.
2.
The egress node compares the received information fields, such as packet type, frequency,
and TTSI, with the fields recorded in the local to check the correctness of the packets. It
also performs statistics to the numbers of correct packets and incorrect packets during the
detection period, which is 3s for a CV and three times as long as the transmission period
for an FFD. In this way, the connectivity of an LSP is monitored in real time.
3.
When detecting a defect of the LSP, the egress node analyzes the defect type, and then
transmits the backward defect indication (BDI) packets that carry the defect information
to the ingress node through a reverse channel so that the ingress node can learn the defect
status in time. If a protection group is correctly configured, the corresponding protection
switching is also triggered.
When configuring basic detection functions of the OAM, you can bind a reverse channel for the
detected LSP. The reverse channel is an LSP that has opposite ingress and egress nodes to the
detected LSP, or is a non-MPLS path that can connect to the ingress and egress nodes of the
detected LSP. The reverse channel that carries BDI packets can be one of the following types:
l
Dedicated reverse LSP: Each forward LSP has a corresponding reverse LSP. This method
is relatively stable but may waste resources.
Shared reverse LSP: Many forward LSPs share a reverse LSP. All LSPs return BDI packets
through this reverse LSP. This method saves resources, but a congestion may occur on the
reverse LSP when many forward LSPs have defects at the same time.
29-40
Issue 02 (2010-09-24)
29 OAM Management
Ping/Traceroute
In MPLS, if the LSP fails to forward data, the MPLS control plane responsible for constructing
the tunnel cannot detect this fault. Thus, the network maintenance is difficult. The MPLS Ping/
Traceroute provides a mechanism for detecting the LSP faults and locating the invalid nodes in
a timely manner.
The MPLS Ping/Traceroute uses the MPLS Echo Request and MPLS Echo Reply to detect the
usability of the LSP. The MPLS Echo Request carries the information of the forwarding
equivalence class (FEC) for detection, which is transmitted along the LSP with other packets
belonging to this FEC. In this way, the LSP is checked.
l
The MPLS Ping and Echo Request messages should reach the Egress node of the tunnel.
Then, the control plane of the Egress node determines whether this node is the Egress of
this FEC. Whether the LSP is successfully created can be checked by the MPLS Ping.
The MPLS Traceroute and Echo Request messages should be transmitted to each Transit
node. The control plane of the Transit node determines whether the local node is an
intermediate node on this path. The location of the network fault can be determined through
the Traceroute function.
CE
CE
Access layer
Custom layer
Core layer
OptiX RTN 950
LSP
Table 29-7 lists different application scenarios of the CV/FFD, Ping and Traceroute.
Table 29-7 Application scenarios of MPLS OAM detection methods
Issue 02 (2010-09-24)
OAM Type
Usage
Application Scenario
CV/FFD
Unidirectional connectivity
check
29-41
29 OAM Management
OAM Type
Usage
Application Scenario
Ping
Unidirectional connectivity
check
Traceroute
Fault location
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > MPLS Management > Unicast
Tunnel Management from the Function Tree.
Step 2 Click the OAM Parameters tab. In the OAM Status area, click Enabled.
Step 3 Click Apply. The Operation Result dialog box is displayed indicating that the operation is
successful.
Step 4 Click Close.
----End
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > MPLS Management > Unicast
Tunnel Management from the Function Tree.
Step 2 Select the tunnel, click the OAM Parameters tab and set the parameters.
29-42
Issue 02 (2010-09-24)
29 OAM Management
NOTE
Step 3 Click Apply. The Operation Result dialog box is displayed, indicating that the operation is
successful.
Step 4 Click Close.
----End
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > MPLS Management > Unicast
Tunnel Management from the Function Tree.
Step 2 Click the OAM Parameters tab and select a tunnel. Click OAM Operation and choose Start
CV/FFD from the drop-down menu. The Operation Result dialog box is displayed, indicating
that the operation is successful.
NOTE
When the Node Type of the tunnel is Ingress, the CV/FFD can be enabled.
29-43
29 OAM Management
Prerequisite
l
In the case of a static MPLS tunnel, enable the IS-IS protocol at both the source and sink
ports of the MPLS tunnel, for details, see 20.2.2 Setting Port Attributes. Also, you can
start a ping test at the local end and configure a static route on the opposite NE.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > MPLS Management > Unicast
Tunnel Management from the Function Tree.
Step 2 Click the OAM Parameters tab and select a tunnel. Click OAM Operation and choose Ping
Test from the drop-down menu. The Ping Test dialog box is displayed.
NOTE
When the Node Type of the tunnel is Ingress, you can perform the ping test.
29-44
Issue 02 (2010-09-24)
29 OAM Management
Prerequisite
l
In the case of a static MPLS tunnel, enable the IS-IS protocol at both the source and sink
ports of the MPLS tunnel. Also, you can start a ping test at the local end and configure a
static route on the opposite NE.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > MPLS Management > Unicast
Tunnel Management from the Function Tree.
Step 2 Click the OAM Parameters tab and select a tunnel. Click OAM Operation and choose
Traceroute Test from the drop-down menu. The Traceroute Test dialog box is displayed.
Issue 02 (2010-09-24)
29-45
29 OAM Management
NOTE
To support the traceroute test, the Tunnel Type of the tunnel must be Ingress.
Issue 02 (2010-09-24)
29 OAM Management
Ping
PW Ping is a tool for manually checking the connection status of virtual circuits, which is similar
to the LSP Ping. When the PW fails to forward data, the control plane that is responsible to create
the PW cannot detect this fault. This makes the network maintenance difficult. PW Ping provides
the mechanism of detecting faults of PWs to users.
During the PW forwarding, the Ping packets are encapsulated into the PW at the ingress and are
transmitted along the virtual circuit. Thus, the PW is checked.
TDM E1
NodeB
CES PW
NE1
PW ping
TDM E1
NE2
RNC
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > MPLS Management > PW
Management from the Function Tree.
Step 2 Right-click a PW and choose PW Ping Test from the shortcut menu. The Ping Test dialog box
is displayed.
Issue 02 (2010-09-24)
29-47
29 OAM Management
Issue 02 (2010-09-24)
29 OAM Management
Detect faults.
Locate faults.
Description
Issue 02 (2010-09-24)
29-49
29 OAM Management
Layer
Description
At the ATM layer, the operation flows of F4 and F5 are defined. The F4 flow is an OAM cell
flow in the virtual path connect (VPC) and provides the operation management and maintenance
functions of the VP level. The F5 flow is an OAM cell flow in the virtual channel connect (VCC)
and provides the operation management and maintenance functions of the VC level. After the
OAM is activated at the F4 and F5, the specific OAM cell is inserted into user cells. As a result,
the functions of continuity check (CC) and loopback (LB) check without service interruption
are realized.
The ATM OAM defines the following concepts:
l
Segment point: Only the OAM cells at the segment can be terminated.
Segment and Endpoint: The OAM cells at the segment and end can be terminated.
Non segment and Endpoint: The OAM cells are not terminated.
CC
After the CC detection function at the source end and sink end is enabled, the source end regularly
forms and sends CC cells. If the sink end fails to receive CC cells from the source end within
seconds, it automatically reports the LOC alarm and inserts the corresponding AIS cells to the
downstream.
LB
Perform the remote loopback (LB) detection. The source end forms and sends LB cells and
enable the timer for timing. If the sink end receives the LB cells, it sends the cells back to the
source end. If the source end detects the returned LB cells within the given time, the loopback
succeeds; otherwise, the loopback fails.
Table 29-9 lists different application scenarios of the CC and LB.
29-50
Issue 02 (2010-09-24)
29 OAM Management
Usage
Application Scenario
CC
Unidirectional connectivity
check
LB
Bidirectional connectivity
check
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The ATM service must be created and activated.
Context
The segment end attribute of ATM CPs (Connection Points) contains Segment point and Non
segment and Endpoint.
The ways that the port handles the OAM cell in different segment end attributes are described
as follows:
l
If the segment end attribute is set to Endpoint, only the OAM cell at the end can be
terminated.
If the segment end attribute is set to Segment point, only the OAM cell at the segment can
be terminated.
If the segment end attribute is set to Segment and Endpoint, the OAM cells at the segment
and end can be terminated.
If the segment end attribute is set to Non segment and Endpoint, the OAM cell is not
terminated.
CAUTION
You cannot set OAM segment endpoint or activate CC at the protection connection to which 1
+1 source or 1+1 sink protection group is applied. You cannot set segment end attribute at the
connection that is added to a protection group.
Procedure
Step 1 In the NE Explore, select the NE and choose Configuration > ATM OAM Management.
Step 2 Set the Segment and End Attribute of the connection point.
Issue 02 (2010-09-24)
29-51
29 OAM Management
Step 3 Click Apply and then click Close in the Operation Result dialog box.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
After you activate the CC check at the source and sink ends of a service, the source ends
periodically builds and sends a CC cell. If the sink end does not receive the CC cell from the
source in 3-4 seconds, it automatically reports a CCLOS alarm and inserts an e-to-e_VP_AIS
alarm to the downstream. seconds, it automatically reports LOC alarm and inserts the
corresponding AIS cells to the downstream.
NOTE
When activating the CC, you need to activate the source and sink ends almost at the same time in a short
period. You are recommended to activate the sink first and then the source. Otherwise, the NE may report
timeout.
Procedure
Step 1 In the NE Explore, select the NE and choose Configuration > ATM OAM Management. Click
the CC Activation Status tab.
Step 2 Set the CC Activate Flag of the port and the Segment and End Attribute of the CC cell.
NOTE
l Segment and End Attribute sets the segment end attribute of the CC cell. It corresponds to the segment
end attribute of the port. The CC cell terminates at the port of the same segment attribute.
l After the CC Activate Flag is activated, the CC check is started.
29-52
Issue 02 (2010-09-24)
29 OAM Management
Step 3 Click Apply and then click Close in the Operation Result dialog box.
----End
Prerequisite
Segment end attribute must be set.
Context
During the remote loopback check, the source end builds a LB cell, sends the cell and starts the
timer. If the sink end receives the LB cell, it sends the cell back to the source. If the source end
detects the returned LB cell in a specified time, the loopback is successful. Otherwise, the
loopback fails.
Procedure
Step 1 In the NE Explore, select the NE and choose Configuration > ATM OAM Management. Click
the Remote Loopback Test tab.
Step 2 Set the Loopback PointLoopback Point NE and Segment and End Attribute.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Issue 02 (2010-09-24)
29-53
29 OAM Management
Context
The LB test recognizes an NE by LLID, so the LLID must be unique in the network. After the
LLID is set for an NE, the LLID value is sent to all the boards to keep consistency of LLID
values on all the boards.
Procedure
Step 1 In the NE Explore, select the NE and choose Configuration > ATM OAM Management. Click
the LLID tab.
Step 2 Set the Country Code, Network Code, and NE Code.
Step 3 Click Apply and then click Close in the Operation Result dialog box.
----End
29-54
Issue 02 (2010-09-24)
30
Issue 02 (2010-09-24)
30-1
LPT Application
As a link-based protection scheme, the LPT passes through states of the point-to-point link and
point-to-multipoint link. In this way, the LPT makes sure the network level protection for the
transmission of point-to-point private line services and for the transmission of the point-tomultipoint convergence services.
l
The following description is based on the point-to-point networking. Figure 30-1 shows
the point-to-point networking.
Backup network
Service
Network
Router A
Access
NE1
Node Link 1
NE2
Access
Node Link 2
Router B
Working Link
Protection Link
In normal situations, data of router A and router B is exchanged over the network service
equipment. In the diagram preceding, the network equipment refers to the Huawei OptiX
RTN equipment, namely NE1 and NE2. When faults occur at the link between router A
and router B, the communication between router A and router B is interrupted.
For the important user, however, even when such fault occurs, the important data must be
transmitted normally. Thus, the system must be able to detect and report faults at the earliest
time and then start the backup network to make sure the communication.
30-2
Issue 02 (2010-09-24)
When the LPT function is enabled, the OptiX equipment detects and reports the faults at
the service access node and in the intermediate network. Then the data communication
equipment such as routers switches to the backup network at the earliest time for
communication, thus making sure the normal transmission of the important data.
l
Backup
network
Port1
Port3
Port1
Router A
NE1
Port2
Router B
NE2
Service
network
Port2
Port2
Port1
Port3
Router C
NE3
Backup
network
Protection link
Router D
Working link
Normally, the data among router A, router B, router C and router D is transmitted through
a server network. When the link between router A and NE1 becomes faulty, router A fails
to communicate with router B, router C and router D. When the link fault occurs, the
important data of VIP users must still be normally transmitted. Hence, the system should
detect and notify the fault in time, and start the backup network to retain communication.
LPT Capability
When the LPT function is enabled, the notification interval is less than two seconds after the
fault occurs.
30-3
The LPT bearer mode varies with the different LPT packets. When the bearer mode of the
received LPT packets is not consistent with that of the equipment at the receive end, the LPT
packet is discarded.
30.2 Availability
The LPT feature requires the support of the applicable equipment and boards.
Table 30-1 Availability of the LPT feature(RTN600)
Feature
Applicable Board
Applicable Equipment
Point-to-point LPT
feature
SL61EFT4VER.B
RTN 610/620
SL61EMS6VER.B, EFP6
RTN 620
Point-to-multipoint
LPT feature
SL61EMS6VER.B, EFP6
RTN 620
Applicable Equipment
RTN 910/950
EM4F
CSHA
CSHB
RTN 910
CSHC
Issue 02 (2010-09-24)
Fault locating
Access
Node 1
Service
Equipment
A
Broken
Service
Network
Broken
Service
Equipment
B
Access
Node 2
Both service equipment A and B detect that the service network is unavailable and then transmit
the Broken packets to the opposite ends respectively. At the same time, equipment A and B cut
the connection to local users.
NOTE
l If the service network fault is bidirectional, service equipment A and B can detect the fault in the service
network. As a result, either of the two sets of the equipment can cut the connection between the local
end and the user, and transmit the Broken packets to the opposite end at the same time.
l If the service network fault is unidirectional, for example, if the link in the direction from service
equipment A to B is faulty, only service equipment A can detect the service network fault. In this case,
service equipment A cuts the connection between the local end and access node 1 and transmits the
Broken packets to equipment B in the direction from equipment A to B over the service network where
no fault occurs. After receiving the Broken packets, service equipment B cuts the connection between
the local end and access node 2. In this way, the fault in the service network is detected.
l According to different transmission modes, the Broken packets can be transmitted through specific
GFP management frames or MAC frames.
Link restoration
Access
Node 1
Service
Equipment
A
Non_
Broken
Service
Network
Non_
Broken Service
Equipment
B
Access
Node 2
Both service equipment A and B detects that the service network is recovered, and then notify
the opposite end that the link is recovered by transmitting the Non_Broken packets respectively.
At the same time, equipment A and B recover the connection with local users.
Access
Node 1
Service
Equipment
A
Service
Network
Service
Equipment
B
Access
Node 2
Service equipment A and B recovers the local link when any of the following condition is
satisfied. 1. Equipment A and B receive the Non_Broken packets transmitted by the opposite
ends respectively. 2. Timeout occurs for waiting the Broken frame.
Issue 02 (2010-09-24)
Fault locating
30-5
Access
Node 1
Service
Network
Broken
Service
Equipment
B
Access
Node 2
1.
Service equipment A detects that the link at the access node is faulty, and then reports the
alarm of the fault that occurs at the local end. At the same time, equipment A transmits the
Broken control frame to equipment B.
2.
After receiving the Broken control frame, service equipment B disconnects the local end
and reports the LPT_RFI alarm at the same time.
Link restoration
Service
Network
Access
Node 1
Non_Broken
Recover the
link
Service
Equipment
B
Access
Node 2
1.
Service equipment A detects that the link at the access node is recovered, and then transmits
the Non_Broken control frame to service equipment B.
2.
After receiving the Non_Broken control frame, service equipment B recovers the
connection at the local end.
Context
The point-to-multipoint LPT function processes faults in unidirectional service network and
bidirectional service network by using the same means.
Fault locating
Service
Equipment
A
Broken
30-6
Service
Equipment
B
Access
Node 1
Issue 02 (2010-09-24)
The bidirectional fault occurs in the service network between service equipment A and B. In
this case, equipment A and B cut the local connections respectively and report the LPT_RFI
alarms. At the same time, equipment A transmits the Broken packets to equipment C. In this
case, service equipment C cuts the local connection and reports the LPT_RFI alarm.
l
Link restoration
Non_Broken
Service
Equipment
A
Convergence
Node
Non_Broken
The bidirectional fault is cleared in the service network between service equipment A and B. In
this case, equipment A and B recovers the local connections respectively and report the clearance
of the LPT_RFI alarms. At the same time, equipment A transmits the Non-Broken packets to
equipment C. In this case, service equipment C recovers the connection to the local end and then
reports the clearance of the LPT_RFI alarm.
Point-to-Multipoint LPT Access Node Link Fault at the Convergence Node Side
l
Fault locating
Disconnect the
link and report the
LPT_RFI alarm
Report the link
fault alarm
Convergence
Node
Broken
Service
Equipment
A
Broken
Service
Equipment
B
Access
Node 1
Disconnect the
link and report
the LPT_RFI
alarm
Service
Access
Equipment
Node 2
C
Service Equipment A that connects to the convergence node detects that the link at the access
node is faulty, and then reports the alarm of the fault that occurs at the local end. At the same
time, service equipment A transmits Broken packets to service equipment B and C. After
receiving the packets, equipment B and C disconnect the local end. In this case, equipment B
and C report the LPT_RFI alarms.
l
Issue 02 (2010-09-24)
Link restoration
30-7
Non_Broken
Service
Equipment
B
Non_Broken
Service
Equipment
C
Recover
the link
Recover
the link
Access
Node 1
Access
Node 2
Service Equipment A that connects to the convergence node detects the link restoration at the
access nod, and then reports the clearance of the local fault alarm. At the same time, service
equipment A transmits Non-Broken packets to service equipment B and C. After receiving the
packets, equipment B and C recover the connections to the local end. In this case, equipment B
and C report the clearance of LPT_RFI alarms.
Point-to-Multipoint LPT Access Node Link Fault at the Access Node Side
l
Scenario 1
Fault locating
Disconnect the
link and report
the LPT_RFI
alarm
Convergence
Node
Broken
Service
Equipment
A
Broken
Service
Equipment
B
Service
Equipment
C
1.
Service equipment B that connects to access node 1 detects that the link at the access
node is faulty, and then reports the alarm of the local access node fault. At the same
time, equipment B transmits the Broken packets to service equipment A.
2.
After receiving the packets, equipment A reports the LPT_RFI alarm and transmits
the Broken packets to equipment C at the same time.
3.
In this case, service equipment C disconnects the local end and reports the LPT_RFI
alarm.
Link restoration
Convergence
Node
30-8
Recover
the link
Non_Broken
Service
Equipment
B
Non_Broken
Service
Equipment
C
Service
Equipment
A
Recover
the link
Access
Node 2
Issue 02 (2010-09-24)
1.
Service equipment B that connects to access node 1 detects that the link at the access
node is restored, and then reports the clearance of the local fault alarm. At the same
time, equipment B transmits the Non-Broken packets to service equipment A.
2.
After receiving the packets, equipment A recovers the connection to the local end and
then reports the clearance of the LPT_RFI alarm. At the same time, equipment A
transmits the Broken packets to equipment C.
3.
In this case, service equipment C recovers the connection to the local end and then
reports the clearance of the LPT_RFI alarm.
Scenario 2
Fault locating
Disconnect the link
and report the
LPT_RFI alarm
Convergence
Node
Service
Equipment
B
Service
Equipment
A
Broken
Service
Equipment
C
Access
Node 1
Report the link
fault alarm Access
Node 2
Access
Node 3
Service equipment C that connects to access node 2 detects that the link at the access node
is faulty, and then reports the alarm of the fault that occurs at the local end. At the same
time, equipment C transmits the Broken packets to service equipment A. In this case, service
equipment A disconnects the local end and reports the LPT_RFI alarm.
Disconnect the link
and report the
LPT_RFI alarm
Broken
Convergenc
e Node
Service
Equipment
B
Access
Node 1
Service
Equipment
A
Broken_Ack
Access
Node 2
Service
Equipment
C
Disconnect the
link and report the
LPT_RFI alarm
Access
Node 3
After receiving the Broken packets where the response confirmation frame is contained,
service equipment A transmits the Broken packets to service equipment B. After receiving
the Broken_Ack packets, service equipment C disconnects the access node 3 and reports
the LPT_RFI alarm. After recovering the Broken packets from equipment A, service
equipment B disconnects the local end and reports the LPT_RFI alarm.
Link restoration
Issue 02 (2010-09-24)
30-9
Service
Equipment
B
Service
Equipment
A
Non_Broken
Service
Equipment
C
Access
Node 1
Recover
the link
Access
Node 2
Access
Node 3
Service Equipment C that connects to the access node 2 detects the link at the access node
is restored, and then reports the clearance of the fault alarm at the local end. At the same
time, service equipment C transmits Non-Broken packets to service equipment A. After
receiving the packets, equipment A recovers the local connection and reports the clearance
of the LPT_RFI alarm.
Convergence
Node
Non_Broken
Service
Equipment
B
Non_Broken_Ack
Service
Equipment
C
Service
Equipment
A
Access
Node 1
Access
Node 2
Access
Node 3
After receiving the Non_Broken packets where the response confirmation frame is
contained, service equipment A transmits the Non_Broken packets to service equipment
B. After receiving the Non_Broken_Ack packets, service equipment C recovers the
connection to access node 3 and reports the clearance of the LPT_RFI alarm. After
recovering the Non_Broken packets from equipment A, service equipment B disconnects
the local end and reports the clearance of the LPT_RFI alarm.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet data board supports the LPT function.
The port-based Ethernet private line service must be created and activated.
The data service is configured as the pure transparent service.
30-10
Issue 02 (2010-09-24)
Precautions
NOTE
l Point-to-point LPT and point-to-multipoint LPT are mutually exclusive. On one board, you can select
only one configuration mode to realize the LPT function.
l The data service of the point-to-point LPT is configured as the pure transparent service.
CAUTION
Before configuring the point-to-multipoint LPT function, make sure that the following two
conditions are met. Otherwise, the services may be interrupted.
l
Procedure
Step 1 In the case of RTN 600 NEs.
1.
In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet
Interface Management > LPT Management from the Function Tree.
2.
Click Query. The Operation Result dialog box is displayed. Click Close.
b.
Select a PORT and a VCTRUNK port, and then set the following parameters. For
parameters of the point-to-point LPT, see Table 30-3.
NOTE
If LPT is enabled, you can set Port-Type Port Hold-Off Time(ms) and VCTRUNK Port
Hold-Off Time(ms) as required.
3.
Issue 02 (2010-09-24)
c.
Click Apply and a prompt appears telling you the operation was successful.
d.
Click Close.
e.
Repeat Steps 1 through 2 to configure point-to-point LPT for the opposite NE.
b.
c.
In the Create LPT window, select Port from the Convergence Point pane, and set
Hold-Off Time(ms).
30-11
NOTE
If the port at the convergence point is a VCTRUNK port, you need to set Bearer Mode.
d.
l If the port at the convergence point is not a VCTRUNK port, do not set Bearer Mode.
l If you want to modify Bearer Mode, you can modify it in the Modify LPT window.
e.
f.
Repeat Steps 1 and Steps 3 to configure point-to-multipoint LPT for other NEs.
In the NE Explorer, click the NE and choose Configuration > LPT Management from
the Function Tree.
2.
3.
4.
Click Apply.
----End
30-12
Issue 02 (2010-09-24)
Parameter
Table 30-3 Parameter of the Point-to-Point LPT(RTN600)
Field
Value
Default
Description
Port
For
example:
PORT1
VCTRUNK
Port
For
example:
VCTRU
NK1
Direction
Positive,
Reverse
Issue 02 (2010-09-24)
LPT
Yes, No
No
Bearer Mode
GFP
(HUAW
EI),
Ethernet
GFP(HUAWEI)
Port-Type
Port Hold-Off
Time (ms)
0 to
10000
100
VCTRUNK
Port Hold-Off
Time (ms)
0 to
10000
30-13
Value
Default
Description
Port
PORT1 to
PORT6,
VCTRUNK1 to
VCTRUNK8
PORT1
Bearer Mode
GFP
(HUAWEI),
Ethernet
GFP
(HUAWEI)
The bearer
mode of the port
where the access
point resides.
This parameter
can be edited
only when it is
supported by a
board.
Access Point
Hold-Off Time
(ms)
0 to 10000
If LPT
switching is
enabled, the port
notifies the
opposite end
after the holdoff time.
Port
PORT1 to
PORT6,
VCTRUNK1 to
VCTRUNK8
Bearer Mode
GFP
(HUAWEI),
Ethernet
GFP
(HUAWEI)
The bearer
mode of the port
where the access
point resides.
This parameter
can be edited
only when it is
supported by a
board.
30-14
Field
Value
Default
Description
Board
Issue 02 (2010-09-24)
Issue 02 (2010-09-24)
Field
Value
Default
Description
Port
For example: 1
(PORT-1)
30-15
31
Issue 02 (2010-09-24)
31-1
Storage of statistical data at the agent end; offline operations on the network management
station (NMS)
To implement the preceding functions, the RMON defines a series of statistical formats and
functions to realize the data exchange between the control stations and detection stations that
comply with the RMON standards, and thus to implement management on the Ethernet port.
The RMON provides flexible detection modes and control mechanisms to meet the requirements
of different networks. Furthermore, the RMON provides the function of error diagnosis of the
entire network, and the functions of planning and receiving of the performance events.
The RMON complies with RFC 1757 and RFC 2819.
31.2.1 SNMP
Currently, the SNMP is the most widely used network management protocol in the network.
The SNMP is used to ensure transport of the management information between any two nodes
31-2
Issue 02 (2010-09-24)
in the network. This facilitates the network administrator to retrieve information, modify
information, locate a fault, diagnose a fault, plan capacity, and generate a report on any node in
the network.
NMS
The NMS is a workstation where the client program runs. When the RMON function is
used, the Web LCT or U2000 server functions as the NMS.
Agent
The agent is the server software that runs on the network equipment. When the RMON
function is used, the agent is embedded in the Ethernet board.
The NMS can send the GetRequest, GetNextRequest, or SetRequest packet to the agent. After
receiving such a request packet, the agent reads or writes the packet according to the type of the
packet, generates the Response packet, and sends the Response packet to the NMS.
When an exception occurs in the equipment or the state of the equipment changes (for example,
the equipment restarts), the agent sends the Trap packet to the NMS and reports the event to the
NMS.
The transmission of SNMP packets is based on the connectionless transport layer UDP. Hence,
the OptiX RTN 600 can be connected to a wide variety of equipment without a block.
MIB
In SNMP packets, managed variables are used to describe the managed objects in the equipment.
The SNMP uses the architecture naming solution to uniquely identify each managed object in
the equipment. The overall architecture is like a tree. The nodes on the tree indicate the managed
objects. Each node can be uniquely identified by a path starting from the root. The MIB is used
to describe the architecture of the tree and is the collection of the definitions of the standard
variables of the monitored network equipment. The RMON is a common MIB defined according
to IETF RFC2819.
Statistics Group
The statistics group counts the absolute performance values from the time the statistics group is
created until the current time.
The Ethernet board supports port-based statistics groups. In the case of a board, you can create
a statistics group for only one port. The sampling interval of a statistics group can be set. The
value range of the sampling interval is from 1 second to 100 seconds.
Issue 02 (2010-09-24)
31-3
Alarm Group
The alarm group monitors the specified alarm objects (for example, the performance data of
ports). When the value of the monitored data crosses the configured threshold, an alarm event
is generated.
The Ethernet board supports port-based alarm groups. You can create only one alarm group for
a board. The number of alarm entries in an alarm group must not exceed ten. You can set the
following items to which the alarm object corresponds: monitored object, sampling interval,
report mode (report in case of upper threshold-crossing, report in case of lower thresholdcrossing, report all), upper threshold, and lower threshold.
Monitored object
This specifies the port on which performance data is collected. You can set monitored
objects for each history table type.
Number of items
This specifies the number of history performance data entries that are stored in the Ethernet
board. Because the history performance data is stored in the wrap mode, the stored data is
the latest history performance data. For example, if the number of items is set to 10, the
Ethernet board stores the latest ten history performance data entries. You can set the number
of items for each history table type. The number of items can be set to 50 at most.
History Group
The history group specifies the methods of querying history performance data. The Ethernet
board filters the history performance data stored in the board according to the attributes of the
history group and returns the history performance data that meets the filtering conditions. The
history group has the following attributes:
l
Monitored object
This specifies the port to which the history performance data corresponds.
Performance entry
This specifies the performance entries to which the history performance data corresponds.
The list of performance entries is the same as the list of performance entries that can be
added into a statistics group.
31-4
Issue 02 (2010-09-24)
Query conditions
This specifies the relative time to which the history performance data corresponds. 1
represents the oldest item. You can query a maximum of ten entries at a time.
Description
DropEvent
UndersizePkts
OversizePkts
Fragments
Jabbers
FCSErrors
Basic performance
Issue 02 (2010-09-24)
31-5
Category of
Performance
Entries
Fragments (packets/second)
Jabbers (packets/second)
Octets received (bytes/second)
Packets received (packets/second)
Extended
performance
31-6
Issue 02 (2010-09-24)
Category of
Performance
Entries
NOTE
The PORTs of the EMS6 board, EFT4 board, and IFH2 board support basic performance entries and extended
performance entries. The VCTRUNKs of the EMS6 board support VCG performance entries. The VCTRUNKs
of the EFT4 board do not support RMON performance entries. The IDU 605 1F/2F PORT and IFUP support
basic performance and extended performance.
31.3 Availability
The RMON feature requires the support of the applicable equipment and boards.
Table 31-3 Availability of the RMON Feature
Applicable Board
Applicable Equipment
EFT4
RTN 610/620
EMS6
RTN 620
EFP6
Issue 02 (2010-09-24)
IFH2
RTN 620
RTN 605
31-7
Applicable Equipment
EM6T
EM6F
EM4T
RTN 910/950
EM4F
IFU2
IFX2
CSHA
CSHB
RTN 910
CSHC
NOTE
Statistics Group
The processing flow is as follows:
31-8
1.
2.
The NMS sends the corresponding request packet to the RMON agent.
3.
The RMON agent embedded in the Ethernet board resets the corresponding current
performance counting register and returns the corresponding response packet to the NMS
according to the information of the statistics group in the request packet.
4.
The NMS sends a request packet to the RMON agent at sampling intervals. The RMON
agent returns the value of the current performance counting register through the response
packet.
5.
6.
The NMS stops sending the corresponding request packet to the RMON agent.
Issue 02 (2010-09-24)
NOTE
l If the maintenance engineer clicks Start, the RMON agent does not reset the performance counting register.
l If the maintenance engineer does not select Display Accumulated Value, the NMS obtains the performance
value of a sampling interval by performing a subtraction operation between the sampled value returned at
the end of the sampling interval and the sampled value returned at the end of the previous sampling interval.
Alarm Group
The processing flow is as follows:
1.
2.
The NMS sends the corresponding request packet to the RMON agent.
3.
The RMON agent embedded in the Ethernet board monitors the corresponding alarm object
according to the information of the alarm group in the request packet.
4.
When the alarm object crosses the configured threshold in the corresponding direction, the
RMON agent sends the corresponding trap packet to the NMS.
5.
The NMS generates the corresponding RMON alarm according to the information in the
packet.
2.
The NMS sends the corresponding request packet to the RMON agent.
3.
The RMON agent embedded in the Ethernet board periodically counts the performance
value of the monitored object and stores the performance value in the corresponding history
performance register according to the information of the history control group in the request
packet.
History Group
The processing flow is as follows:
1.
2.
The NMS sends the corresponding request packet to the RMON agent.
3.
The RMON agent embedded in the Ethernet board queries the history performance registers
that meet the requirements and returns the performance values in the registers to the NMS
through the response packet according to the information of the history group in the request
packet.
31-9
After you configure an RMON alarm group for an Ethernet port, you can monitor whether the
performance value of the port crosses the configured thresholds in the long term.
31.5.3 Configuring a History Control Group
When configuring a history control group for an Ethernet port, you configure how the history
performance data of the port is monitored. The Ethernet board monitors the history performance
data of each port at the default sampling interval of 30 minutes. An Ethernet board stores 50
history performance data items.
31.5.4 Browsing the Performance Data in the History Group of an Ethernet Port
After you configure an RMON history group for an Ethernet port, you can browse the statistical
history performance data of the port.
31.5.5 Setting Performance Monitoring Status for an Ethernet Port
By setting status and period of the RMON performance monitoring, the performance data can
be periodically collected.
Prerequisite
The Ethernet board must be included in the slot layout.
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Performance > RMON Performance
from the Function Tree.
Step 2 Click the Statistics Group tab.
Step 3 Set the required parameters for the statistics group.
Step 4 Click Resetting begins.
NOTE
If you click Start, the register of the statistics group is not reset to clear the existing data.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet board must be included in the slot layout.
Applies to OptiX RTN 600 NEs.
31-10
Issue 02 (2010-09-24)
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Performance > RMON Performance
from the Function Tree.
Step 2 Click the Alarm Group tab.
Step 3 Set the required parameters for the alarm group.
Step 4 Click Apply.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet board must be included in the slot layout.
Procedure
Step 1 In the case of RTN 600 NEs:
1.
Select the Ethernet board in the NE Explorer. Choose Performance > RMON
Performance from the Function Tree.
2.
3.
4.
Click Apply.
Click the NE in the NE Explorer. Choose Performance > RMON History Control
Group from the Function Tree.
2.
3.
Click Query.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The Ethernet board must be included in the slot layout.
Issue 02 (2010-09-24)
31-11
The monitored objects and the corresponding history table type must be set in the History
Control Group tab.
Procedure
Step 1 Select the Ethernet board in the NE Explorer. Choose Performance > RMON Performance
from the Function Tree.
Step 2 Click the History Group tab.
Step 3 Set the required parameters for the history group.
Step 4 Click Query.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Performance > RMON
Performance from the Function Tree.
Step 2 Click the RMON Setting tab.
Step 3 Select ports in the upper pane, click Query.
Step 4 Select the object from Object, set the monitor status, and enable or disable each collecting period.
NOTE
Enable or disable the collecting period in the Object interface only after you enable the collecting period
in the RMON history control group interface.
Step 5 Select the performance event in Event and set the enable status for each monitor period.
Step 6 Click Apply. Click Close in the dialog box displayed.
----End
31-12
Issue 02 (2010-09-24)
32
Issue 02 (2010-09-24)
32-1
NE2
FE
FE/GE
Node B
RNC
FE
Ethernet link
32.2 Availability
The synchronous Ethernet feature requires the support of the applicable equipment and boards.
Table 32-1 Availability of the synchronous Ethernet feature
32-2
Applicable Board
Applicable Equipment
IFH2
RTN 620
RTN 605
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
Issue 02 (2010-09-24)
Applicable Board
EM6T
Applicable Equipment
RTN 910/950
EM6F
CSHA
CSHB
RTN 910
CSHC
The data sub-system extracts the clock information (namely, recovery clock) from the
packets that the upstream Ethernet port receives.
2.
The data sub-system sends the Ethernet recovery clock to the clock processing module.
Then, the clock processing module locks the Ethernet recovery clock to the local system
clock and provides the system synchronous clock.
3.
The system synchronous clock provides a reference clock for the other modules of the
system and the services (for example, microwave services or node B that is interconnected
with the downstream Ethernet port) so that the system is synchronized with the Ethernet.
Issue 02 (2010-09-24)
32-3
CPU sub-system
Orderwire
NMS
...
IF sub-system
Orderwire and
auxiliary
interface
module
Other
modules
System
synchronous clock
Ethernet
recovered
clock
Ethernet services
Data sub-system
32-4
In the case of the IDU 620, see 14.7.8 Configuring the Clock Sources to configure the
Ethernet clock source.
In the case of the IDU 605 1F/2F, see 14.7.9 Configuring the Ethernet Clock Source to
configure the Ethernet clock source.
Issue 02 (2010-09-24)
33
Issue 02 (2010-09-24)
33-1
Prerequisite
l
Precautions
CAUTION
Modifying the NE ID may interrupt NE communication and reset the NE.
33-2
Issue 02 (2010-09-24)
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > NE Attribute from the Function
Tree.
Step 2 Click Modify NE ID, and the Modify NE ID dialog box is displayed.
Step 3 Enter the New ID and the New Extended ID. Click OK.
Step 4 Click OK in the Warning dialog box.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > NE Attribute from the Function
Tree.
Step 2 In the NE Attribute dialog box, enter a new NE name in Name. Click Apply. A prompt is
displayed indicating that the operation is successful.
NOTE
An NE name consists of up to 64 characters, including letters, symbols, and numerals, except the following
special characters | : * ? " < >.
Prerequisite
You must be an NM user with "NM maintainer" authority or higher.
Context
When the NE is not logged in, you can delete the NE on the U2000.
CAUTION
If an NE is deleted, the links related to the NE are also deleted.
When a GNE is deleted, if no standby GNE is provided for the NEs that were originally managed
by the deleted GNE, the communication between those NEs and the U2000 is interrupted.
Issue 02 (2010-09-24)
33-3
Procedure
l
Right-click the NE on the Main Topology and choose Delete > Delete Device from
the shortcut menu. The Confirm dialog box is displayed.
2.
2.
3.
Select the NEs to be deleted, right-click and choose Delete from the shortcut menu.
The Delete the NE dialog box is displayed.
4.
Click OK.
----End
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Precautions
CAUTION
This is a potential service affecting operation. Specifically, it may interrupt the communication
between a GNE and the U2000, and the communication between the GNE and the non-gateway
NEs that are managed by the GNE.
Procedure
Step 1 Choose Administration > DCN Management from the main menu. Click the GNE tab.
Step 2 Select the GNE to be modified, right-click and choose Modify GNE from the shortcut menu.
Step 3 In the Modify GNE dialog box displayed, set Gateway Type .
l
33-4
Issue 02 (2010-09-24)
NOTE
Step 4 Click OK. In the Operation Result dialog box that is displayed, click Close.
----End
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Issue 02 (2010-09-24)
33-5
Precautions
CAUTION
This operation may interrupt the NE communication.
Procedure
Step 1 Choose Administration > DCN Management from the main menu.
Step 2 Click the NE tab.
Step 3 Select an NE. Double-click the Primary GNE1 field and select a GNE from the drop-down list.
Step 4 Click Apply. Click Close in the Operation Result dialog box.
Step 5 Click Refresh. Test the modification with reference to Checking the Network Communication
Status.
----End
Issue 02 (2010-09-24)
Prerequisite
l
Context
The physical boards are the actual boards inserted in the shelf. A logical board refers to a board
that is created on the U2000. After a logical board is created, you can configure the relevant
services. If the corresponding physical board is online, the configured services can be available.
NOTE
The NE panel is able to indicate the mapping relation between slots that house processing boards and
interface boards. When you click a processing board that is paired with an interface board in the NE panel,
the ID of the slot that houses the mapping interface board is displayed in orange.
Procedure
Step 1 Open the NE Panel.
For the RTN equipment, double-click the icon of the NE.
NOTE
Currently, the OptiX OSN 6800 and OptiX OSN 8800 T32 equipments can be managed individually as an
NE, and can also be managed in an optical NE. For the two equipments, you can double-click the NE On
the Main Topology, the NE Panel is displayed.
Step 2 Right-click the selected idle slot. Select the board you want to add from the drop-down list.
----End
Prerequisite
l
Procedure
Step 1 Open the NE Panel.
For the RTN equipment, double-click the icon of the NE.
Step 2 Right-click the board you want to delete and choose Delete from the shortcut menu.
NOTE
Certain boards, such as AUX boards, cannot be deleted. The boards that can be deleted vary with different
types of equipment. For details, see the Hardware Description of each type of the equipment.
33-7
Prerequisite
To modify different configuration parameters of different boards, you may need to operate as
NM users with different authorities. You must be an NM user with "NE operator" authority or
higher. must be available at least.
Procedure
Step 1 In the NE Explorer, select a board and choose a proper item from the Function Tree.
Board Type
Parameters
Application Scenario
SDH board
PDH board
Ethernet board
Step 2 In the right-hand pane, modify the existing parameter settings and click Apply.
----End
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Procedure
Step 1 Choose Inventory > Fiber/Cable > Fiber/Cable Management from the main menu. The
information of all fiber/cable is displayed in the pane on the right.
Step 2 Modifying the fiber/cable information.
l
In the Name column, right-click the value for a fiber/cable and choose Modify Fiber/
Cable from the shortcut menu. In the Modify Fiber/Cable dialog box displayed, enter a
proper name for the fiber/cable and click OK. Click Close in the Operation Result dialog
box.
In the Length(km) column, right-click the value for a fiber/cable and choose Modify Fiber/
Cable from the shortcut menu. In the Modify Fiber/Cable dialog box displayed, enter the
actual length for the fiber/cable and click OK. Click Close in the Operation Result dialog
box.
1.
In the Attenuation column, right-click the value for a fiber and choose Modify Fiber/
Cable from the shortcut menu.
2.
In the Modify Fiber/Cable dialog box, enter the actual loss and click OK. Click
Close in the Operation Result dialog box.
In the Type column, right-click the value for a fiber and choose Modify Fiber/
Cable from the shortcut menu.
2.
In the Modify Fiber/Cable dialog box displayed, select the actual type of the fiber
from the drop-down list and click OK. Click Close in the Operation Result dialog
box.
----End
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Procedure
Step 1 Choose Inventory > Fiber/Cable > Fiber/Cable Management from the main menu.
Step 2 Select the fiber you want to delete, right-click and choose Delete Fiber/Cable from the shortcut
menu. The Warning dialog box is displayed. Click OK to delete the fiber/cable.
Issue 02 (2010-09-24)
33-9
CAUTION
The deletion of the fiber/cable will delete the related protection subnets, trails and user-defined
information. Exercise caution before you delete the fiber/cable. You can export the script of the
entire network first to avoid deletion by mistake.
Step 3 Click Close in the Operation Result dialog box.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 On the Main Topology, select a cable, right-click and choose Delete from the shortcut menu.
Step 2 In the Delete Link dialog box displayed, click OK.
----End
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
CAUTION
Performing this operation interrupts the service that you modify.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > SDH Service Configuration
from the Function Tree.
Step 2 Select a cross-connection and choose Display > Expand to Unidirectional.
Step 3 Optional: If the service to be modified is active, you should deactivate the service. Select the
service that you want to modify, and click Deactivate.
CAUTION
Deactivation will interrupt services.
Step 4 Click OK in the Confirm dialog box is displayed twice. The Operation Result dialog box is
displayed telling you that the operation was successful.
Step 5 Click Close.
Step 6 After the cross-connection is deactivated, modify the SDH service in the mode in Step 7 or Step
8.
Issue 02 (2010-09-24)
33-11
l By using the mode in Step 7, you can modify the source or sink of a service, but the source and sink
must be on the same board before and after the modification.
l If the modification requirement cannot be met in the mode in Step 7 (for example, a pass-through
service needs to be configured to the local through modification), you can delete the original service
and create the cross-connection again in the mode in Step 8, to achieve the modification.
Step 7 Optional: To modify the SDH service, choose Modify from the shortcut menu.
1.
Select the service that you want to modify, right-click, and choose Modify from the shortcut
menu. The Modify SDH Service dialog box is displayed.
2.
Modify Source VC4 or Sink VC4, Source Timeslot Range, and Sink Timeslot Range.
NOTE
In this mode, you can modify only Source VC4 or Sink VC4. The source VC4 and sink VC4 cannot
be modified at the same time.
3.
Click OK. The Operation Result dialog box is displayed telling you that the operation
was successful.
4.
Click Close.
5.
6.
7.
Click Close.
Step 8 Optional: To modify the SDH service, delete the service and then create the service again.
1.
Select the service that you want to modify, and click Delete.
2.
Click OK and the Operation Result dialog box is displayed telling you that the operation
was successful.
3.
4.
Create the service again as required. For details, see Creating SDH Services.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > SDH Service Configuration
from the Function Tree.
Step 2 Click Query to query existing services.
Step 3 Optional: If the service to be deleted is active, you should deactivate the service. Select the
service that you want to delete and click Deactivate.
33-12
Issue 02 (2010-09-24)
CAUTION
Deactivation will interrupt services.
Step 4 Select the desired service and click Delete.
Step 5 In the Confirm dialog box displayed, click OK.
Step 6 In the Operation Result dialog box displayed, click Close.
----End
Prerequisite
l
Context
CAUTION
Deleting EPL services interrupts services.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Ethernet Service > Ethernet
Line Service from the Function Tree.
Step 2 Select the desired EPL service and click Delete.
Step 3 In the Warning dialog box displayed, click Yes.
Step 4 In the Operation Result dialog box displayed, click Close.
----End
Prerequisite
l
Issue 02 (2010-09-24)
33-13
Context
CAUTION
Deleting EVPL services interrupts services.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Ethernet Service > Ethernet
Line Service from the Function Tree.
Step 2 Select the desired EVPL service and click Delete.
Step 3 In the Warning dialog box displayed, click Yes.
Step 4 In the Operation Result dialog box displayed, click Close.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
The EPLAN service must be created
Context
CAUTION
Deleting EPLAN services interrupts services.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Ethernet Service > Ethernet
LAN Service from the Function Tree.
Step 2 Select the desired EPLAN service and click Delete.
Step 3 In the Hint dialog box displayed, click Yes.
Step 4 In the Operation Result dialog box displayed, click Close.
----End
33-14
Issue 02 (2010-09-24)
Prerequisite
The normal service must be created.
Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > SDH Service Configuration from
the Function Tree.
Step 2 Optional: Click Query to query the cross-connection services from the NE.
Step 3 Click Display and choose Expand from the drop-down list, to display every service.
Step 4 Right-click a non-SNCP service and choose Convert to SNCP from the shortcut menu.
Issue 02 (2010-09-24)
33-15
Prerequisite
The SNCP service must be created.
Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > SDH Service Configuration from
the Function Tree.
Step 2 Optional: Click Query to query the cross-connection services from the NE.
Step 3 Right-click an SNCP service and choose SNCP Working Service Change to Normal
Service from the shortcut menu. The protection service is then deleted.
NOTE
To convert the service in the protection path into a normal service, right-click the SNCP service and choose
SNCP Protection Service Change to Normal Service from the shortcut menu. The working service is
then deleted.
----End
33-16
Issue 02 (2010-09-24)
34
34-1
You can enable the automatic laser shut down function. In the event of a fiber cut, the laser at
an optical port is automatically off, to prevent hazardous laser radiation exposure from causing
permanent eye damage.
34.9 Disabling Service-Affecting Settings Automatically
Loopback and laser shutdown are useful NE maintenance functions. Performing these functions
may interrupt services at the port and may also interrupt the communication between the NE
and the U2000. Hence, you can set automatic disabling before performing loopback or laser
shutdown so that the NE automatically cancels the loopback or laser shutdown.
34.10 Performing a PRBS Test
You can perform a PRBS test on a path to check the quality of the path. The test result is displayed
in the coordinates pane.
34.11 Diagnosing Ethernet Protocol Faults
In the case of an Ethernet service fault, you can diagnose the Ethernet protocol and then restart
the protocol state machine by restoring the protocol, to remove the protocol faults.
34.12 Checking the Network Communication Status
On some occasions, the U2000 cannot manage some NEs during the running of the network. By
checking the communication status of the network, you can learn the communication status
between the U2000 and NEs.
34-2
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Context
l
When an NE uses IP over DCC, to check the NE communication status by using the ping
function, you can right-click the NE on the Main Topology and choose Ping from the
shortcut menu.
You can use the ping function after installing the OSI software on the NE that uses OSI
over DCC and the computer where the U2000 resides.
Check the communication status between the U2000 and a non-gateway NE.
Procedure
1.
2.
Click the NE tab. Click Refresh to view the communication status of all NEs.
3.
Select an NE. Right-click in the Communication Status column and choose Test
NE from the shortcut menu.
4.
The Operation Result dialog box is displayed indicating the test result of the nongateway NE.
Check the communication status between the U2000 and the GNE.
1.
2.
Click the GNE tab. Click Refresh to view the communication status of the GNE.
3.
4.
The Operation Result dialog box is displayed indicating the test result of the GNE.
----End
Prerequisite
l
Issue 02 (2010-09-24)
34-3
Context
CAUTION
If you turn off a laser, services may be interrupted or you may fail to log in to certain NEs.
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > SDH Interface from the
Function Tree.
Step 2 Click By Board/Port (channel) and select Port from the drop-down list.
Step 3 Double-click Laser Switch and set the laser status of each port to Open or Close as required.
Step 4 Click Apply. In the Operation Result dialog box, click Close.
NOTE
If you set Laser Switch to Close, you need to click OK in the Confirm dialog box. In the Prompt dialog
box, click OK.
----End
Prerequisite
You must be an NM user with "NM maintainer" authority or higher.
Background Information
If a large number of performance data need to be collected, this may cause communication
congestion and thus the communication between the U2000 and NEs stops. Hence, observe the
following rules to collect the performance data:
l
When creating a single performance data collection task, the number of NEs related to the
same GNE does not exceed 5.
Run the performance data collection task when network traffic is low.
Procedure
Step 1 Choose Administration > Task Schedule > Task Management from the main menu.
Step 2 Optional: Create a scheduled task.
34-4
1.
2.
Enter a task name and select the task type of the scheduled task and the run type. Then,
click Next.
3.
Issue 02 (2010-09-24)
4.
Follow the task creation wizard to set the parameters of the scheduled task and click
Next for several times until the Finish button is displayed.
5.
Step 3 Optional: Double-click a scheduled task to modify the parameters of the task.
Step 4 Optional: Right-click a scheduled task and choose Timely Suspend/Resume to set the suspend
time or the resume time for the task.
Step 5 Optional: Right-click a scheduled task and choose Run At Once to start executing the task.
NOTE
Run At Once means to immediately execute the task, no matter the scheduled time comes or not.
Resume means to start the scheduled task. The task is executed at the scheduled time.
----End
Background Information
To check the networkwide maintenance status, check the following:
l
34-5
You can view all alarms for which you configure alarm suppression in the network. You can
also restore the suppression status of an alarm to the default value, so that the alarm monitoring
of the service is not affected by improper settings.
34.4.6 Checking the DCC Enabling Status
You can view all ports where DCC is in the shutdown state in the network, and you can modify
the DCC enabling status for the ports.
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
Procedure
Step 1 Click the networkwide maintenance status icon
Maintenance Status dialog box is displayed.
Step 2 Choose Loopback Status, select the NEs from the Object Tree and click
loopback status for a path from U2000.
, view the
Step 3 Click Query, view the loopback status from the NE.
NOTE
Step 4 Optional: Select a loopback status and then click Apply. A prompt is displayed indicating that
the operation is successful. Click Close.
CAUTION
Setting a loopback may interrupt services. Exercise caution when you perform this operation.
NOTE
You must be an NM user with "NE operator" authority or higher to set loopback for a path.
----End
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
34-6
Issue 02 (2010-09-24)
You must be an NM user with "NE operator" authority or higher to set the laser status for an
optical port.
Procedure
Step 1 Click the networkwide maintenance status icon
Maintenance Status dialog box is displayed.
Step 2 Choose Laser Status, select the NEs from the Object Tree and click
status for an optical port from U2000.
Step 3 Click Query, view the laser status from the NE.
NOTE
If the queried information is null, it indicates that the laser of the equipment is not shut down.
Step 4 Optional: Set the laser status and then click Apply. If you want to enable the laser, in the OK
dialog box displayed, click OK. A prompt is displayed indicating that the operation is successful.
Click Close.
WARNING
Enabling a laser is a dangerous operation. Misoperation may cause injuries to human eyes.
Exercise caution when you perform this operation.
CAUTION
Close the Laser will interrupt the service.
----End
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
Procedure
Step 1 Click the networkwide maintenance status icon
Maintenance Status dialog box is displayed.
Step 2 Choose Maintenance Status > Path Loading and view the loading status for a path.
Issue 02 (2010-09-24)
34-7
NOTE
Step 3 Optional: Set the loading status and then click Apply. A prompt is displayed indicating that the
operation is successful. Click Close.
CAUTION
Set the path to be Non-Loaded will interrupt the service.
NOTE
You must be an NM user with "NE operator" authority or higher to set the loading status for a path.
----End
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
Applies to the MSTP, WDM, NA WDM, RTN, PTN, submarine equipment.
34-8
Issue 02 (2010-09-24)
Procedure
Step 1 Click the networkwide maintenance status icon
Maintenance Status dialog box is displayed.
Step 2 Choose Alarm Reversion, select one or more NEs from the Object Tree and click
view the alarm reversion status for a path.
NOTE
If the queried information is null, it indicates that the alarm reversion is not set for any port.
Step 3 Optional: Set the alarm reversion status and then click Apply. A prompt is displayed indicating
that the operation is successful. Click Close.
NOTE
l If the alarm reversion is set for a port, the alarm status of this port is opposite to the actual status. That
is, when an alarm exists, the status is displayed as normal. This setting helps filter out negligible alarms.
When alarm suppression is set for a LOS alarm of the port, you cannot set alarm reversion at the same
time.
l You must be an NM user with "NE operator" authority or higher to set the alarm reversion status for
a path.
----End
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
Applies to the MSTP, WDM, NA WDM, RTN, PTN, submarine equipment.
Procedure
Step 1 Click the networkwide maintenance status icon
Maintenance Status dialog box is displayed.
Step 2 Choose Alarm Suppression, select one or more NEs from the Object Tree and click
view the alarm suppression status for a path.
NOTE
If the queried information is null, it indicates that the alarm suppression is not set for any path.
Step 3 Optional: To restore the suppression status to the default value, right-click and choose
Default from the shortcut menu. Click Apply. A prompt is displayed indicating that the operation
is successful. Click Close.
Issue 02 (2010-09-24)
34-9
NOTE
You must be an NM user with "NE operator" authority or higher to set the alarm suppression status for a
path.
----End
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
Procedure
Step 1 Click the networkwide maintenance status icon
Maintenance Status dialog box is displayed.
Step 2 Choose Maintenance Status > DCC Enabling Status and view the DCC enabling status for
the ports where DCC is in the shutdown state.
Step 3 Optional: Select a port for which you want to modify its DCC enabling status, right-click and
choose Enabled from the shortcut menu to modify its status to Enabled. Click Apply. A prompt
is displayed indicating that the operation is successful. Click Close.
NOTE
You must be an NM user with "NE operator" authority or higher to modify the DCC enabling status for a
port.
----End
Issue 02 (2010-09-24)
If board 1+1 protection switching is triggered, it indicates that the protected board has failed.
The network maintenance engineers can check 1+1 board switching status to detect the faults
that caused the failure.
34.5.4 Checking the Switching Status of 1+1 Intermediate Frequency Protection
If 1+1 intermediate frequency switching takes place, it indicates that the protection intermediate
frequency board becomes faulty. By checking the switching status of 1+1 intermediate frequency
protection, you can know the fault timely and thus prevent it from affecting services.
34.5.5 Check the Switching Status of the N+1 Protection
After configuring the N+1 protection, you can query the switching status of the protection on
the U2000.
34.5.6 Checking GNE Switching Status
If the active GNE of an NE fails, and the NE has a standby GNE, the NE automatically
communicates with the U2000 through the standby GNE. To detect the GNE communication
failure in time, you need to check the GNE switching status to ensure that the NEs communicate
correctly with the U2000 through the GNE.
34.5.7 Checking the Clock Switching Status
Clock failure may interrupt services. To detect failure of the clock source in time, you need to
check the clock switching status.
Prerequisite
l
Context
Lockout switching means regardless of the status of the working and protection channels, the
services are locked in the working channel.
Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > SNCP Service Control from the
Function Tree.
All SNCP groups are displayed.
Step 2 Select an SNCP group, click Function and choose Query Switching Status from the drop-down
list.
----End
34-11
point where the fault is generated, according to the switching status of each NE in the protection
subnet.
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Linear MS from the Function
Tree.
Step 2 In the pane on the right, select an MSP protection group. The Status of each node in the protection
group is displayed in the pane on the right.
Step 3 Click Query and select Query Switching Status to query the switching status of the nodes.
----End
Prerequisite
You must be an NM user with "NE monitor" authority or higher.
The protection board must be created.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Board 1+1 Protection from the
Function Tree.
Step 2 Click Query to query the 1+1 board switching status.
Step 3 Click Close.
----End
Prerequisite
34-12
Issue 02 (2010-09-24)
Procedure
Step 1 In the NE Explorer, click an NE and choose Configuration > IF 1+1 Protection from the
Function Tree.
Step 2 Select a protection group, and click Query.
Step 3 View the Switching Status of NE and Switching Status of Channel.
----End
Prerequisite
l
Procedure
Step 1 Select the NE to be queried. In the NE Explorer, choose Configuration > N+1 Protection from
the Function Tree.
Step 2 Select the IF N+1 protection group and click Query. In Slot Mapping Relation, view Switching
Status.
NOTE
----End
Prerequisite
The active and standby GNEs must be created for an NE.
You must be an NM user with "NE maintainer" authority or higher.
Issue 02 (2010-09-24)
34-13
Procedure
Step 1 Choose Administration > DCN Management from the main menu.
Step 2 Click the NE tab.
Step 3 Click Refresh to query the GNE switching status.
----End
Prerequisite
l
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Clock Source
Switching from the Function Tree.
Step 2 Click the Clock Source Switching tab, and click Query to query the current switching status
of the current clock source.
Issue 02 (2010-09-24)
You can reset a non-SCC board by using the U2000. Resetting a board is a maintenance method
used in the case of an improper board working status.
34.6.4 Resetting a Board
You can reset a board by using the U2000. Resetting a board is a maintenance method used in
the case of an improper board working status.
34.6.1 Reset
Reset is a protection scheme for applications and data files on the equipment. When a board is
not running properly, you can reset the board so that it returns to the normal state. Reset is of
two types: warm reset and cold reset. A cold reset takes more time than a warm reset. After a
board is reset, the data on the board is not lost, but the resetting process may interrupt services.
l
Performing a warm reset restores the applications and data to the normal state. Warm reset
usually does not affect services.
Performing a cold reset restores the applications and data to the normal state before a CPU
power failure. Cold reset usually affects services.
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Background Information
When the SCC is being reset, network communication is interrupted temporarily until the SCC
returns to the normal state. This may affect service switching. You can reset the SCC in the
following three ways:
l
Performing a reset to the SCC by pushing the Reset button on the SCC.
Procedure
Step 1 Double-click an NE on the Main Topology and the slot layout is displayed.
Step 2 Right-click the SCC and choose SCC Reset from the shortcut menu.
Step 3 In the Warning dialog box displayed, click OK.
Step 4 Click Close in the dialog box displayed.
----End
34-15
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Background Information
Performing a warm reset usually does not affect services, but performing a cold reset usually
affects running services. You can reset a non-SCC board in the following two ways:
l
Procedure
Step 1 Double-click an NE on the Main Topology and the slot layout is displayed.
Step 2 Right-click a non-SCC board and choose Cold Reset or Warm Reset from the shortcut menu.
Step 3 In the Warning dialog box displayed, click OK.
Step 4 Click Close in the prompt dialog box.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
Performing a cold reset usually affects services. You can reset a board in the following two ways:
l
Procedure
Step 1 Double-click an NE on the Main Topology and the Slot Layout is displayed.
Step 2 Right-click a non-SCC board and choose Cold Reset or Warm Reset from the shortcut menu.
Click OK in the Warning dialog box to confirm the reset.
Step 3 Click Close in the prompt dialog box.
----End
Issue 02 (2010-09-24)
The support for loopback functions depends on equipment types. For details, refer to the specific
equipment manuals.
A loopback can be performed for different objects.
34.7.1 Setting a Loopback for an SDH Interface
You can set a loopback for an SDH interface by using the U2000. The SDH interface loopback
is a common fault location method used to test and maintain the SDH board. The SDH interface
loopback is used to test the fiber connections and interfaces on the SDH board, and is also used
to test the SDH service processing module and the cross-connect board.
34.7.2 Setting a Loopback for a PDH Interface
You can set a loopback for a PDH interface by using the U2000. The PDH interface loopback
is a common fault location method used to test and maintain the PDH board. The PDH interface
loopback is used to test the fiber connections and interfaces on the PDH board, and is also used
to test the PDH service processing module and the cross-connect board.
34.7.3 Setting a Loopback for an Ethernet Interface
You can set a loopback for an Ethernet interface by using the U2000. The Ethernet interface
loopback is a common fault location method used to test and maintain the Ethernet board. The
Ethernet interface loopback is used to test the fiber connections on the Ethernet board, physical
and MAC layers of the Ethernet interface, and SDH layer (that is, the line).
34.7.4 Setting a Loopback for an IF Interface
You can to set loopback for an intermediate frequency (IF) interface by using the U2000. The
IF interface loopback is a commonly used way of fault location during the test and maintenance
of the IF boards. By performing loopback for an IF interface, the system can determine whether
the IF interface and the fibers (cables) connected to the IF board are normal and whether the IF
board service processing module and the cross-connect board are normal.
34.7.5 Setting a Loopback for an ODU Interface
You can set a loopback for an ODU interface by using the U2000. The ODU interface loopback
is a common fault location method used to test and maintain the ODU board. The ODU interface
loopback is used to test the radio frequency (RF) link and interfaces on the ODU board, as well
as to test the ODU service processing module and the cross-connect board.
34.7.6 Setting a Loopback for a Digital Interface
This section describes how to set the loopback for the digital interface on the U2000. The digital
interface loopback is a commonly used way of fault location during the test and maintenance of
the IF boards. By performing the loopback at a digital interface, the system can determine
whether the IF interface and the fibers/cables connected to the IF board are normal and whether
the IF board service processing module and the cross-connect board are normal.
34.7.7 Setting a Loopback for a VC4 Path
You can set a loopback for a VC4 path by using the U2000. The VC4 path loopback is a common
fault location method used to test and maintain the SDH board. The VC4 path loopback is used
to test the fiber connections and interfaces on the SDH board, and is also used to test the SDH
service processing module and the cross-connect board.
34.7.8 Setting a Loopback for a VC3 Path
The VC3 path loopback is a common fault location method to test and maintain the board. The
VC3 path loopback is used to test the fiber connections and SDH interfaces on the board, and
is also used to test the SDH service processing module and the cross-connect board.
34-17
loopback is used to test the fiber connections and interfaces on the SDH board, and is also used
to test the SDH service processing module and the cross-connect board.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
The SDH interface loopback can be set to an outloop or an inloop.
l
When an outloop is used, the SDH signal received by the NE is returned at the SDH
interface. See Figure 34-1. An outloop is used to test the fibers connections and interfaces
on the SDH board.
Figure 34-1 Outloop
When an inloop is used, the SDH signal transmitted by the NE is returned to the crossconnect board at the SDH interface. See Figure 34-2. An inloop is used to test the SDH
service processing module and the cross-connect board.
Figure 34-2 Inloop
CAUTION
As a loopback interrupts services, it is only used for fault location and must be released after the
fault is removed.
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > SDH Interface from the
Function Tree.
34-18
Issue 02 (2010-09-24)
If you select the Non Loopback mode, click Apply. A prompt directly is displayed indicating that the
operation is successful because Non Loopback does not affect services.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Context
The PDH interface loopback can be set to an outloop or an inloop.
l
When an outloop is used, the PDH signal received by the NE is returned at the PDH
interface. See Figure 34-3. An outloop is used to test the fibers connections and interfaces
on the PDH board.
Figure 34-3 Outloop
Issue 02 (2010-09-24)
When an inloop is used, the PDH signal transmitted by the NE is returned to the crossconnect board at the PDH interface. See Figure 34-4. An inloop is used to test the PDH
service processing module and the cross-connect board.
34-19
CAUTION
As a loopback interrupts services, it is only used for fault location and must be released after the
fault is removed.
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > PDH Interface from the
Function Tree.
Step 2 Select By function and select Tributary Loopback.
Step 3 Select a PDH interface from the list and double-click Tributary Loopback to choose the
loopback mode.
Step 4 Click Apply and the Confirm dialog box is displayed.
Step 5 Click OK. A prompt is displayed indicating that the operation is successful.
Step 6 Click Close.
NOTE
If you select the Non Loopback mode, click Apply. A prompt directly is displayed indicating that the
operation is successful because Non Loopback does not affect services.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Background Information
You can perform an inloop for an Ethernet interface by using the U2000.
34-20
Issue 02 (2010-09-24)
When an inloop is used, the Ethernet signal transmitted by the NE is returned to the SDH layer
at the Ethernet interface. See Figure 34-5. The physical layer inloop is used to test the MAC
layer and the SDH layer. The MAC layer inloop is used to test the SDH layer.
Figure 34-5 Inloop
CAUTION
As a loopback interrupts services, it is only used for fault location and must be released after the
fault is removed.
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > Ethernet Interface
Management > Ethernet Interface from the Function Tree.
Step 2 Select External Port and click the Basic Attributes tab.
Step 3 Select an Ethernet interface from the list and double-click MAC Loopback or PHY
Loopback to choose the loopback mode.
Step 4 Click Apply and the U2000 prompts that this operation may interrupt the service.
Step 5 Click OK. A prompt is displayed indicating that the operation is successful. Click Close.
----End
Context
IF interface loopback can be set to an outloop or an inloop.
l
Issue 02 (2010-09-24)
When an outloop is used, the IF service received by NE is returned at the IF interface. See
Figure 34-6. An outloop can be used to test the IF interface and the fibers or cables
connected to the IF interface.
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
34-21
CAUTION
As a loopback interrupts services, it is only used for fault location and must be released after the
fault is removed.
Procedure
Step 1 In the NE Explorer, select an IF board and choose Configuration > IF Interface from the
Function Tree.
Step 2 Select By Function and select IF Port Loopback.
Step 3 Select an IF interface from the list and double-click IF Port Loopback to select a loopback
mode.
Step 4 Click Apply and the Confirm dialog box is displayed.
Step 5 Click OK. A prompt is displayed indicating that the operation is successful.
Step 6 Click Close.
34-22
Issue 02 (2010-09-24)
NOTE
If you select the Non Loopback mode, click Apply. A prompt directly is displayed indicating that the
operation is successful because Non Loopback does not affect services.
----End
Context
The ODU interface loopback can be set to an outloop or an inloop.
l
When an outloop is used, the RF service received by an NE is returned at the ODU interface.
See Figure 34-8. An outloop can be used to test the ODU interface and the RF link
connected to the ODU board.
Figure 34-8 Outloop
Issue 02 (2010-09-24)
34-23
CAUTION
As a loopback interrupts services, it is only used for fault location and must be released after the
fault is removed.
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > ODU Interface.
Step 2 Select By Function. Select RF Loopback.
Step 3 Select an RF interface from the list and double-click RF Loopback to select a loopback mode.
Step 4 Click Apply and the Confirm dialog box is displayed.
Step 5 Click OK. A prompt is displayed indicating that the operation is successful.
Step 6 Click Close.
NOTE
If you select the Non Loopback mode, click Apply. A prompt directly is displayed indicating that the
operation is successful because Non Loopback does not affect services.
----End
Context
The digital interface loopback includes the outloop and inloop.
l
When an outloop is used, the IF service received by the NE is returned at the IF interface.
See Figure 34-10. An outloop can be used to test the IF interface and the fibers/cables
connected to the IF interface.
Figure 34-10 Outloop
34-24
Issue 02 (2010-09-24)
When an inloop is used, the IF service transmitted by the NE is returned to the cross-connect
board at the IF interface. See Figure 34-11. An inloop can be used to test the IF board
service processing module and the cross-connect board.
Figure 34-11 Inloop
CAUTION
As a loopback interrupts services, it is only used for fault location and must be released after the
fault is removed.
Procedure
Step 1 In the NE Explorer, select an IF board and choose Configuration > Digital Interface from the
Function Tree.
Step 2 Select By Function. Select VC4 Loopback.
Step 3 Choose an digital interface from the list and double-click VC4 Loopback to select the loopback
mode.
Step 4 Click Apply and the Confirm dialog box is displayed.
Step 5 Click OK. A prompt is displayed indicating that the operation is successful.
Step 6 Click Close.
NOTE
If you select the Non Loopback mode, click Apply. A prompt directly is displayed indicating that the
operation is successful because Non Loopback does not affect services.
----End
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Issue 02 (2010-09-24)
34-25
Background Information
The VC4 path loopback can be set to an outloop or an inloop.
l
When an outloop is used, the VC4 signal received by the NE is returned over the VC4 path.
In Figure 34-12, an outloop is set for the first VC4 path on the line board. An outloop is
used to test the fibers connections and interfaces on the SDH board.
Figure 34-12 Outloop
When an inloop is used, the VC4 signal transmitted by the NE is returned to the crossconnect board over the VC4 path. In Figure 34-13, an inloop is set for the first VC4 path
on the line board. An inloop is used to test the SDH service processing module and the
cross-connect board.
Figure 34-13 Inloop
CAUTION
As a loopback interrupts services, it is only used for fault location and must be released after the
fault is removed.
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > SDH Interface from the
Function Tree.
NOTE
For the intermediate frequency board: In the NE Explorer, select the board and choose Configuration > Digital
Interface from the Function Tree.
34-26
Issue 02 (2010-09-24)
If you select the Non Loopback mode, click Apply. A prompt directly is displayed indicating that the
operation is successful because Non Loopback does not affect services.
----End
Prerequisite
l
Context
The VC3 path loopback can be set to an outloop or an inloop.
l
When an outloop is used, the VC3 signal received by the NE is returned over the VC3 path.
In Figure 34-14, an outloop is set for the first VC3 path in the first VC4 path on the STM-1
line board. An outloop is used to test the fibers connections and interfaces on the SDH
board.
Figure 34-14 Outloop
Issue 02 (2010-09-24)
When an inloop is used, the VC3 signal transmitted by the NE is returned over the VC3
path. In Figure 34-15, an inloop is set for the first VC3 path in the first VC4 path on the
STM-1 line board. An inloop is used to test the SDH service processing module and the
cross-connect board.
34-27
CAUTION
As a loopback interrupts services, it is only used for fault location and must be released after the
fault is removed.
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > SDH Interface from the
Function Tree.
NOTE
For the intermediate frequency board: In the NE Explorer, select the board and choose Configuration > Digital
Interface from the Function Tree.
If you select the Non Loopback mode, click Apply. A prompt directly is displayed indicating that the
operation is successful because Non Loopback does not affect services.
----End
Prerequisite
The optical interface board must be created.
34-28
Issue 02 (2010-09-24)
Procedure
Step 1 In the NE Explorer, click a board and choose Configuration > Automatic Laser Shutdown
from the Function Tree.
Step 2 Set Auto ShutDown to Enabled. Set the On Period (ms), Off Period (ms) and Continuously
On-Test Period (ms).
Prerequisite
You must be an NM user with "NE maintainer" authority or higher..
Background Information
If a port is the only way for an NE to communicate with the U2000, performing a loopback or
laser shutdown at the port results in the loss of communication. Before performing a loopback
or laser shutdown, you must set automatic disabling for this NE. Otherwise, after the
communication is lost, you cannot use the U2000 to log in to the NE to disable the loopback or
laser shutdown.
Procedure
Step 1 Choose Configuration > NE Batch Configuration > Automatic Disabling of NE Function
from the main menu.
Step 2 Select an NE and click the double-right-arrow button (red).
Step 3 Select a value in the Auto Disabling and Auto Disabling Time(min).
Step 4 Click Apply.
----End
34-29
Prerequisite
l
A service must be configured for the port for which you want to perform a PRBS test.
The opposite port must be looped back before you perform a PRBS test.
Precaution
CAUTION
Performing a PRBS test interrupts services.
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > PRBS Test from the Function
Tree.
Step 2 Select a channel or a port and set Duration and Measured in Time in the Set Test
Parameters area.
Step 3 Optional: Select Accumulating Mode. The test result is displayed in the coordinates pane in
an accumulative manner.
Step 4 Click Start to Test. A dialog box is displayed, indicating that this operation may interrupt the
service.
Step 5 Click Yes to start the PRBS test. After the test is complete, view the test result in the coordinates
pane.
----End
Postrequisite
You need to release loopback on the opposite port after the test is complete.
Prerequisite
You must be an NM user with "NE operator" authority or higher.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Configuration > Ethernet
Maintenance > Protocol Fault Management from the Function Tree.
Step 2 Click the Protocol Type tab and click Diagnosis.
34-30
Issue 02 (2010-09-24)
Prerequisite
You must be an NM user with "NE maintainer" authority or higher.
Context
l
When an NE uses IP over DCC, to check the NE communication status by using the ping
function, you can right-click the NE on the Main Topology and choose Ping from the
shortcut menu.
You can use the ping function after installing the OSI software on the NE that uses OSI
over DCC and the computer where the U2000 resides.
Check the communication status between the U2000 and a non-gateway NE.
Procedure
1.
2.
Click the NE tab. Click Refresh to view the communication status of all NEs.
3.
Select an NE. Right-click in the Communication Status column and choose Test
NE from the shortcut menu.
4.
The Operation Result dialog box is displayed indicating the test result of the nongateway NE.
Check the communication status between the U2000 and the GNE.
1.
2.
Click the GNE tab. Click Refresh to view the communication status of the GNE.
3.
4.
The Operation Result dialog box is displayed indicating the test result of the GNE.
----End
Issue 02 (2010-09-24)
34-31