CiTRANS 610A Packet Transfer Platform User Manual

CiTRANS 610A
Packet Transfer Platform
User Manual
Version: B
Code: MN000003272
FiberHome Telecommunication Technologies Co., Ltd.
May 2017
Thank you for choosing our products.
We appreciate your business. Your satisfaction is our goal.

We will provide you with comprehensive technical support
and after-sales service. Please contact your local sales
representative, service representative or distributor for any
help needed at the contact information shown below.
Fiberhome Telecommunication Technologies Co., Ltd.
Address: No. 67, Guanggu Chuangye Jie, Wuhan, Hubei, China

Zip code: 430073
Tel: +6 03 7960 0860/0884 (for Malaysia)
+91 98 9985 5448 (for South Asia)
+593 4 501 4529 (for South America)
Fax: +86 27 8717 8521
Website: http://www.fiberhomegroup.com
Legal Notice
are trademarks of FiberHome Telecommunication Technologies Co., Ltd.

(Hereinafter referred to as FiberHome)
All brand names and product names used in this document are used for
identification purposes only and are trademarks or registered trademarks
of their respective holders.
All rights reserved
No part of this document (including the electronic version) may be

reproduced or transmitted in any form or by any means without prior
written permission from FiberHome.
Information in this document is subject to change without notice.
Preface
Related Documentation
The product manual supports retrieving the relevant content according to the
specific phase of the product life cycle. The product life cycle can be divided into
four phases (network planning, installation and network commissioning, network
configuration and management, and network operation and maintenance). You can
retrieve and view the relevant manual according to the phase of the product life
cycle.
I
Document Description
Includes the chapters such as product description, hardware

CiTRANS 610A Packet
description, equipment commissioning, equipment
Transfer Platform User
configuration and equipment maintenance, all of which are
Manual
aimed at introducing the CiTRANS 610A in details.
CiTRANS 610A Packet

Introduces the installation process of the equipment in graphic
Transfer Platform Quick
mode.
Installation Guide
Includes manuals such as product description, operation
e-Fim OTNM2000 Element guide, routine maintenance, and installation guide. All of them
Management System Manual aim at introducing common and fundamental contents of the
Set OTNM2000 for a better understanding and proficient use of
the network management system.
II
Version
Version Description
A Initial version.
Product version: CiTRANS 610A V1R5.
B
Corresponds to the OTNM2000 version V2.0R5(Build04.20.05.56).
Intended Readers
This manual is intended for the following readers:
u Planning and designing engineers
u Commissioning engineers
u Operation and maintenance engineers
To utilize this manual, these prerequisite skills are necessary:
u MPLS-TP related technology
u Data communication technology
u Ethernet technology
III
Conventions
Terminology Conventions
Terminology Convention
CiTRANS 610A FiberHome CiTRANS 610A Packet Transfer Platform

OTNM2000 FiberHome e-Fim OTNM2000 Element Management System
Symbol Conventions
Symbol Convention Description
Note Important features or operation guide.
Possible injury to persons or systems, or cause traffic

Caution
interruption or loss.
Warning May cause severe bodily injuries.
➔ Jump Jumps to another step.
Cascading
→ Connects multi-level menu options.
menu
Bidirectional
↔ The service signal is bidirectional.
service
Unidirectional
→ The service signal is unidirectional.
service
IV
Contents
Preface...................................................................................................................I
Related Documentation ...................................................................................I
Version ..........................................................................................................III
Intended Readers ..........................................................................................III
Conventions ................................................................................................. IV
1 Product Description ........................................................................................1
1.1 Product Application...........................................................................2
1.2 List of Product Features ....................................................................4
1.3 Technical Specifications....................................................................5
1.3.1 Dimensions and Weight ......................................................6

1.3.2 Power Consumption and Voltage ........................................6
1.3.3 Performance and Capacity..................................................6
1.3.4 Technical Specifications of Optical Interfaces ......................8
1.3.5 Technical Specifications of Electrical Interfaces ...................8
1.3.6 Reliability............................................................................9
1.4 Standards and Protocols...................................................................9
1.4.1 International Standards .....................................................10

1.4.2 Safety Standards of Laser.................................................14
1.4.3 Relevant Safety Standards................................................14
1.4.4 Relevant EMC Standards..................................................15
1.4.5 Relevant Environment Standards ......................................16
1.4.6 Relevant Grounding Standards .........................................17
1.4.7 Relevant Noise Standards ................................................17
1.4.8 Relevant Fire Protection Standards ...................................17
1.4.9 Relevant Packaging Standards .........................................18
1.5 Environment Requirements.............................................................18
1.5.1 Operating Environment .....................................................19

1.5.2 Storage Environment ........................................................21
1.5.3 Transport Environment......................................................22
2 Hardware Description ...................................................................................25
2.1 Appearance and Structure ..............................................................26
2.2 Panel Description ...........................................................................28
2.3 Safety Signs ...................................................................................30
2.4 Pluggable Optical Modules..............................................................31
2.5 Optical Fibers and Cables ...............................................................34
2.5.1 Patch Cord .......................................................................34

2.5.2 Service / Management Cable ............................................37
2.5.3 Clock Cable ......................................................................39
2.5.4 E1 Cable ..........................................................................41
2.5.5 AC Power Cable ...............................................................43
2.5.6 DC Power Cable ...............................................................44
2.6 Mounting Ears ................................................................................45
3 Equipment Commissioning ...........................................................................47
3.1 Commissioning Flow.......................................................................48
3.2 Creating Network Topology .............................................................50
3.2.1 Connecting the EMS and the Equipment ...........................50

3.2.2 Checking the Network Management Process ....................51
3.2.3 Basic Configuration...........................................................53
3.2.4 Configuring NE IP Address Based on SN ..........................68
3.3 Testing the NE Connectivity ............................................................80
3.4 Performing Time Calibration and Downloading Configuration...........81
4 Equipment Configuration...............................................................................84
4.1 Configuring Interfaces.....................................................................85
4.1.1 Basic Concepts and Configuration Rules of Interfaces.......85

4.1.2 Configuring Interface Types ..............................................87
4.1.3 Configuring a LAG Interface ..............................................89
4.2 Configuring Tunnels and Tunnel Protection .....................................95
4.2.1 Basic Concepts and Configuration Rules of Tunnels..........95

4.2.2 Configuring Tunnels..........................................................98
4.2.3 Configuring an LSP 1:1 Protection...................................106
4.3 Configuring PWs and PW Protection ............................................. 118
4.3.1 Basic Concepts and Configuration Rules of PWs............. 118

4.3.2 Configuring PWs.............................................................121
4.3.3 Configuring a PW 1:1 Protection .....................................127
4.4 Configuring Ethernet Services.......................................................132
4.4.1 Basic Concepts and Configuration Rules of Ethernet

Services .........................................................................132
4.4.2 Basic Concepts and Configuration Rules of VLAN ...........136
4.4.3 Basic Concepts and Configuration Rules of Multicast ......139
4.4.4 Configuring E-Line Services............................................141
4.4.5 Configuring User-to-User E-LAN Services .......................150
4.4.6 Configuring User-to-Network E-LAN Services..................156
4.4.7 Configuring E-Tree Services ...........................................165
4.4.8 Configuring Multicast ......................................................173
4.5 Configuring CES Services.............................................................181
4.5.1 Basic Concepts and Configuration Rules of CES.............181

4.5.2 Configuring CES Services...............................................183
4.6 Saving and Delivering Services.....................................................189
4.7 Configuring Clock Synchronization................................................193
4.7.1 Basic Concepts and Configuration Rules of Clock

Synchronization ..............................................................193
4.7.2 Configuring Clock Synchronization..................................195
4.8 Configuring MTU...........................................................................200
4.9 Configuring QoS ...........................................................................203
4.10 Configuring Typical Scenarios .......................................................217
4.10.1 Introduction to Service Model ..........................................217

4.10.2 Configuring the NNI Model Service..................................220
4.10.3 Configuring the Overlay Model Service............................226
5 Equipment Maintenance .............................................................................236
5.1 Replacement of Parts ...................................................................237
5.1.1 Precautions ....................................................................237

5.1.2 Replacing Equipment......................................................237
5.1.3 Replacing a Pluggable Optical Module ............................239
5.2 Daily Operation.............................................................................241
5.2.1 Maintenance Worksheet .................................................241

5.2.2 Querying Alarms .............................................................242
5.2.3 Enabling the Performance Collection Function ................244
5.2.4 Querying the Performance ..............................................246
5.2.5 Setting Alarm / Performance Filter...................................248
5.2.6 Querying the OTNM2000's Operating Log .......................250
5.2.7 Checking the Indicator Status..........................................252
5.2.8 Checking the Ethernet Port Status...................................254
5.2.9 Checking the Optical Power ............................................256
5.2.10 Testing the LSP 1:1 Protection Switching.........................256
5.2.11 Testing the PW 1:1 Protection Switching..........................260
5.2.12 Powering on the Equipment ............................................264
5.2.13 Powering off the Equipment ............................................264
5.3 Handling High Temperature Issues................................................265
5.3.1 Impact and Cause of High Temperature Issues................265

5.3.2 Solution and Preventive Measures for High Temperature
Issues.............................................................................266
Appendix A Abbreviations ..........................................................................267

1 Product Description
This chapter introduces the equipment from the following aspects.
Product Application
List of Product Features
Technical Specifications
Standards and Protocols
Environment Requirements
Version: B 1
CiTRANS 610A Packet Transfer Platform User Manual
1.1 Product Application
The CiTRANS 610A is a new generation of packet transfer platform designed by

FiberHome for packet transport based on MPLS-TP.
Overview of Equipment
The CiTRANS 610A a new generation of packet transfer platform designed by

FiberHome for packet transport based on MPLS-TP. The CiTRANS 610A provides a
switching capacity up to 6G and provides various types of interfaces such as GE,
FE, E1, and clock and time synchronization interfaces. It is located at the remote
access layer of the PTN, meeting the growing bandwidth requirements of the IP-
based services and implementing flexible scheduling of bandwidth resources.
The CiTRANS 610A has the following features:
u Adopts the packet transport technology to meet the growing requirements of

operators for bandwidth and the increasing requirements for flexible bandwidth
scheduling.
u Adopts the PWE3 technology to carry connection-oriented services.
The CiTRANS 610A includes CiTRANS 610A-8A (AC type) and CiTRANS 610A-8D
(DC type). Figure 1-1 and Figure 1-2 show the equipment appearance.
Figure 1-1 Appearance of AC Chassis
2 Version: B
Figure 1-2 Appearance of DC Chassis
Network Application
The CiTRANS 610A is located at the remote access layer of the PTN to aggregate
services of the access / edge layer.
Figure 1-3 shows the typical network of the CiTRANS 610A.
Version: B 3
Figure 1-3 Typical Network
1.2 List of Product Features

Feature Description
u E-Line (carried by PW)

Ethernet
u E-LAN (carried by PW)
Service service
u E-TREE (carried by PW)
CES service (carried by PW)
Multicast Layer 2 multicast
Traffic u Simple traffic classification

classification u Complex traffic classification
PHB (eight priorities: CS7, CS6, EF, AF4 to AF1 and BE)
Committed access rate (CAR)

QoS
Queue u WFQ scheduling
scheduling u PQ scheduling
Congestion u Tail drop

management u Port WRED
4 Version: B
Feature Description
Traffic
token bucket
shaping
Logical
LAG
interface
Tunnel Static bidirectional MPLS Tunnel
PW Single-hop PW (static)
Protocol Layer 2 protocol: LACP
User side
Ethernet LAG protection
protection
Tunnel-level
Network side 1:1 MPLS Tunnel APS
protection
protection
PW protection PW 1:1 protection
u Suppression of broadcast traffic

Service
u Suppression of unknown unicast or multicast traffic
security
u Limitation on capacity of MAC address forwarding table
Clock
u TDM clock synchronization
synchroniza-
u Synchronous Ethernet clock synchronization
tion
Real-time
monitoring
MPLS-TP OAM
and fault
detection
Service mirroring
Operation and DCN
maintenance u Real-time reporting of alarms
u Monitoring of performance on equipment and ports
u Query of alarm and performance using SNMP V1 / V2
Others
u Link searching (Ethernet port)
u Power-off prompt (receive and report, or transmit the
power-off prompt alarm of the adjacent equipment)
1.3 Technical Specifications
This section introduces various technical specifications of the equipment.
Version: B 5
1.3.1 Dimensions and Weight
Type Dimensions (H × W × D) Weight (kg)

(mm)
CiTRANS 610A-8D 43.5 × 254 × 225 1.3

CiTRANS 610A-8A 43.5 × 254 × 225 1.3
1.3.2 Power Consumption and Voltage
Type Power Voltage

Consumption (W)
CiTRANS 610A-8D 15 DC: -36V to -72V

CiTRANS 610A-8A 16 AC: 100V to 240V
1.3.3 Performance and Capacity
Attribute Feature Technical Specification
Performance of Packet switching capacity 6 Gbit/s

integrated equipment Packet processing capability 8.928 Mpps
Maximum number of the performance

Alarm performance 512
objects supported by the equipment
Quantity of E-Line services supported by

E-Line service 128
the equipment
Quantity of E-LAN services (i.e., quantity of

E-LAN service VSIs) supported by the 64
equipment
E-LAN service Quantity of MAC address forwarding table

32640
entries supported by each VSI
Quantity of MAC address forwarding table

32640
entries supported by the equipment
Layer 2 multicast (E- Quantity of Layer 2 multicast supported by

256
Tree) the equipment
Quantity of CES services supported by the

CES service 4
equipment
Quantity of PWs supported by the

PW 128
equipment
6 Version: B
Attribute Feature Technical Specification
Quantity of MPLS Tunnel OAM supported

MPLS Tunnel OAM 128
by the equipment
Quantity of PW OAM supported by the

PW OAM 256
equipment
Quantity of 1:1 MPLS Tunnel APS

64
supported by the equipment
MPLS Tunnel APS
< 50 ms (CC detection with a period of 3.3
1:1 MPLS Tunnel APS switching time
ms is used)
Quantity of 1:1 PW APS supported by the

64
equipment
PW APS < 50 ms (CC detection with a period of 3.3

1:1 PW APS switching time
ms is used)
Number of members in PW protection 256

Quantity of LAGs supported by the
2
equipment
Number of members in each LAG 4

u When a link fails in both directions, the
LAG protection switching time is less
than 200 ms in the dual-receiving
LAG
mode; the LAG protection switching
Switching time time is less than 200 ms in the single-
receiving mode.
u When a link fails in one direction, the
LAG protection switching time is less
than 200 ms.
Quantity of complex traffic classifications
256
QOS Quantity of CAR for traffic classification

256
CAR/Shaping accuracy (granularity) 64K bps
The timing and synchronization

performance of the equipment comply with
Clock standard the ITU-T G.813 standard, and those of the
Physical-layer clock network comply with the ITU-T G.823 SEC
synchronization standard.
Clock level Stratum 3
Accuracy of free running mode Better than ±4.6ppm within 20 years
Accuracy of holdover mode Better than ±0.05ppm within 24 hours
Version: B 7
1.3.4 Technical Specifications of Optical Interfaces
Table 1-1 Specifications of the GE Optical Interface
Item Specification
Optical interface type 1000BASE-LX 1000BASE-EX 1000BASE-ZX1

Target distance 10km 40km 80km
Mean launched
-8 to -3 -5 to 0 -2 to 3
power (dBm)
Central wavelength
1275 to 1350 1275 to 1350 1500 to 1580
(nm)
Overload optical
-3 -3 -3
power (dBm)
Receiving sensitivity
-20 -23 -25
(dBm)
Extinction ratio (dB) 9 to 15 9 to 15 9 to 15
1.3.5 Technical Specifications of Electrical Interfaces
Table 1-2 Specifications of the GE/FE Electrical Interface
Item Specification
Module type 100/1000Base-T

Interface type RJ-45
Interface rate 100/1000Mbit/s auto negotiation
Transmission media CAT-5 twisted pair
Standard compliance IEEE Std 802.3TM-2002

Transmission distance 100m
Working temperature range 0℃ to 70℃
Table 1-3 Specifications of the E1 Interface
Parameter Description
Nominal bit rate 2048 kbit/s

Bit rate accuracy ±50 ppm (±102.4 bit/s)
Code HDB3
All marks of a valid signal must conform with the
Pulse shape (nominal rectangle)
mask in ITU-T Rec. G.703 irrespective of the sign.
Pair(s) in each direction One symmetrical pair
8 Version: B
Table 1-3 Specifications of the E1 Interface (Continued)
Parameter Description
Test load impedance 120Ω

Nominal peak voltage of a mark (pulse) 3V
Peak voltage of a space (no pulse) 0±0.3V
Nominal pulse width 244ns
Ratio of the amplitudes of positive and
negative pulses at the center of the pulse 0.95 to 1.05
interval
Ratio of the widths of positive and negative
0.95 to 1.05
pulses at the nominal half amplitude
Jitter at input and output ports ITU-T Rec. G.823 compliant
Return loss in the following frequency ranges:

Return loss at the output port (dB) (51kHz to 102kHz) ≥ 6dB
(102kHz to 3072kHz) ≥ 8dB
Return loss in the following frequency ranges:

(51kHz to 102kHz) ≥ 12dB
Return loss at the input port (dB)
(102kHz to 2048kHz) ≥ 18dB
(2048kHz to 3072kHz) ≥ 14dB
Attenuation of the input port 0 to 6dB (1024kHz)
1.3.6 Reliability
Item Requirement
0.9999972. The downtime of the equipment should not be

System availability
more than 5 minutes in each year.
Annual average repair rate of the

Less than 1.5％
system
Mean Time to Repair (MTTR) of

2 hours
the system
Mean Time Between Failure

81.59 years
(MTBF) of the system
1.4 Standards and Protocols
This section introduces the international standards that the equipment should
comply with.
Version: B 9
1.4.1 International Standards
Standards and Protocols for Ethernet Services

Number Title
IEEE802.1D Media access control (MAC) bridges
IEEE802.1Q Virtual bridged local area networks
IEEE802.1ad Provider bridges
IEEE802.1ag Connectivity fault management
IEEE802.1ah Provider backbone bridges
Carrier sense multiple access with collision detection (CSMA/CD)

IEEE802.3
access method and physical layer specifications
ITU-T G.8012 Ethernet UNI and Ethernet over transport NNI
Requirements for OAM functions in Ethernet based networks and

ITU-T G.1730
Ethernet services
ITU-T G.8113.1 OAM functions and mechanisms for Ethernet based networks
ITU-T G.8031 Ethernet protection switching
ITU-T G.8010 Architecture of Ethernet layer networks
Characteristics of Ethernet transport network equipment functional

ITU-T G.8021
blocks
Requirements and framework for Ethernet service protection in
MEF MEF2
metro Ethernet networks
Metro Ethernet network architecture framework - Part 1: generic
MEF MEF4
framework
ITU-T G.8011 Ethernet over Transport - Ethernet services framework
draft-ietf-l2vpn-oam-req-
L2VPN OAM requirements and framework
frmk-05
draft-ietf-l2vpn-
Provisioning, autodiscovery, and signaling in L2VPNs
signaling-08
RFC 4664 Framework for layer 2 virtual private networks (L2VPNs)
Service Requirements for Layer 2 Provider-Provisioned Virtual

RFC 4665
Private Networks
Virtual Private LAN Service (VPLS) Using Label Distribution
RFC 4762
Protocol (LDP) Signaling
Standards and Protocols for MPLS

Number Title
ITU-T G.8112 Interfaces for the transport MPLS (T-MPLS) hierarchy
ITU-T G.8131 Protection switching for transport MPLS (T-MPLS) networks
10 Version: B
Number Title
ITU-T Y.1711 Operation & Maintenance mechanism for MPLS networks
ITU-T Y.1720 Protection switching for MPLS networks
ITU-T Y.1561 Performance and availability parameters for MPLS networks
ITU-T G.8110 MPLS layer network architecture
ITU-T G.8110.1 Application of MPLS in the transport network
ITU-T G.8121 Characteristics of transport MPLS equipment functional blocks
ITU-T Y.1710 Requirements for OAM functionality for MPLS networks
RFC 2702 Requirements for traffic engineering over MPLS
Resource Reservation protocol (RSVP)-version 1 functional

RFC 2205
specification
RFC 3031 MPLS architecture

Framework for multi-protocol label switching (MPLS)-based
RFC 3469
recovery
Definitions of textual conventions for multiprotocol label switching

RFC 3811
(MPLS) management
Multiprotocol label switching (MPLS) traffic engineering

RFC 3812
management information base
Multiprotocol label switching (MPLS) label switching router (LSR)

RFC 3813
management information base
Multiprotocol label switching (MPLS) forwarding equivalence class

RFC 3814 to next hop label forwarding entry (FEC-To-NHLFE) management
information base
RFC 4220 Traffic engineering link management information base
RFC 4221 Multiprotocol label switching (MPLS) management overview
Operations and management (OAM) requirements for multi-protocol

RFC 4377
label switched (MPLS) networks
A framework for multi-protocol label switching (MPLS) operations

RFC 4378
and management (OAM)
ITU-T G.8113.1 OAM functions and mechanisms for Ethernet based networks
RFC 3032 MPLS label stack encoding
RFC 3036 LDP specification
RFC 3037 LDP applicability
RFC 3209 Extensions to RSVP for LSP tunnels

RFC 3210 Applicability statement for extensions to RSVP for LSP tunnels
RFC 3215 LDP state machine

Time to live (TTL) processing in multi-protocol label switching
RFC 3443
(MPLS) networks
Version: B 11
Number Title
Signalling unnumbered links in resource Reservation protocol -
RFC 3477
traffic engineering (RSVP-TE)
RFC 3478 Graceful restart mechanism for label distribution protocol
Applicability statement for restart mechanisms for the label

RFC 3612
distribution protocol (LDP)
Definitions of managed objects for the multiprotocol label switching

RFC 3815
(MPLS), label distribution protocol(LDP)
RFC 3936 Procedures for modifying the resource reservation protocol(RSVP)
RFC 4090 Fast reroute extensions to RSVP-TE for LSP tunnels

RFC 4182 Removing a restriction on the use of MPLS explicit NULL
RFC 4201 Link bundling in MPLS traffic engineering (TE)
draft-ietf-mpls-soft-
MPLS traffic engineering soft preemption
preemption-08
RFC 3609 Tracing requirements for generic tunnels
RFC 4204 Link management protocol (LMP)
Link management protocol (LMP) management information base

RFC 4327
(MIB)
Standards and Protocols for PWE3

Number Title
RFC 3916 Requirements for pseudo-wire emulation edge-to-edge (PWE3)
RFC 3985 Pseudo wire emulation edge-to-edge (PWE3) architecture
Requirements for edge-to-edge emulation of time division

RFC 4197
multiplexed (TDM) circuits over packet switching networks
Pseudowire emulation edge-to-edge (PWE3) control word for use

RFC 4385
over an MPLS PSN
RFC 4446 IANA allocations for pseudowire edge to edge emulation (PWE3)
Pseudowire setup and maintenance using the label distribution

RFC 4447
Protocol (LDP)
Encapsulation methods for transport of Ethernet over MPLS

RFC 4448
networks
Pseudowire emulation edge-to-edge (PWE3) frame check sequence
RFC 4720
retention
Structure-agnostic time division multiplexing (TDM) over packet
RFC 4553
(SAToP)
draft-ietf-pwe3- Structure-aware TDM circuit emulation service over packet switched

cesopsn-07 network (CESoPSN)
12 Version: B
Number Title
draft-ietf-pwe3-vccv-11 Pseudo wire virtual circuit connectivity verification (VCCV)
draft-ietf-pwe3-
Segmented pseudo wire
segmented-pw-03
draft-ietf-pwe3-ms-pw-
Requirements for inter domain pseudo-wires
requirements-03
draft-ietf-pwe3-ms-pw- An architecture for multi-segment pseudo wire emulation edge-to-

arch-02 edge
Standards and Protocols for MPLS Tunnel APS

Number Title
ITU-T G.8113.1/Y.1372. Operations, administration and maintenance mechanism for MPLS-

1 TP in packet transport networks
ITU-T G.8131/Y.1382 Linear protection switching for MPLS transport profile (MPLS-TP)
Standards and Protocols for PW APS

Number Title
ITU-T G.8113.1/Y.1372. Operations, administration and maintenance mechanism for MPLS-

1 TP in packet transport networks
ITU-T G.8131/Y.1382 Linear protection switching for MPLS transport profile (MPLS-TP)
Standards and Protocols for Physical Layer Synchronization
Number Title
ITU-T G.813 Timing characteristics of SDH equipment slave clocks (SEC)
The control of jitter and wander within digital networks which are
ITU-T G.823
based on the 2048 kbit/s hierarchy
ITU-T G.8261 Timing and synchronization aspects in Packet Networks
Timing characteristics of synchronous ethernet equipment slave

ITU-T G.8262
clock
ITU-T G.8264 Distribution of timing through packet networks
Structure of Recommendations on equipment for the Synchronous

ITU-T G.781
Digital Hierarchy (SDH)
ITU-T G.703 Physical/electrical characteristics of hierarchy digital interfaces
Version: B 13
Number Title
Bellcore GR-1224-
General standards for the synchronization of network clocks (1995)
CORE
- Both the standard SSM protocol and extended SSM protocol
Standards and Protocols for IEEE 1588 V2

Number Title
Standards for a Precision Clock Synchronization Protocol for
IEEE-1588
Networked Measurement and Control Systems
1.4.2 Safety Standards of Laser
Standard Description
Safety of laser products-Part 1: Equipment classification, requirements and

IEC 60825-1
user's guide
Safety of laser products-Part2: Safety of optical fiber communication

IEC 60825-2
systems
1.4.3 Relevant Safety Standards
IEC 60215 Safety requirements for radio transmitting equipment
Safety of Information Technology Equipment Including Electrical

EN 60950-1
Business Equipment
Safety of Information Technology Equipment Including Electrical

IEC 60950-1
Business Equipment
CAN/CSA-C22.2 No Safety of Information Technology Equipment Including Electrical

60950-1 Business Equipment
3:rd edition Safety of Information Technology Equipment

UL 60950-1
Including Electrical Business Equipment
IEC Publication 479-1 Guide on the effects of current passing through the human body
IS 8437 {1993} Guide on the effects of current passing through the human body
Safety of information technology equipment including electrical

IS 13252 {1993}
business equipment
14 Version: B
1.4.4 Relevant EMC Standards
Information technology equipment-Radio disturbance

EN 55022
characteristics-Limits and methods of measurement
Information technology equipment-Immunity characteristics-Limits
EN 55024
and methods of measurement
Electromagnetic compatibility - Limits - Limits for harmonic current
IEC 61000-3-2
emissions (equipment input current ≤ 16 A per phase)
Electromagnetic compatibility- Limits - Limitation of voltage changes,

voltage fluctuation and flicker in public low-voltage supply systems,
IEC 61000-3-3
for equipment with rated current ≤16A per phase and not subject to
conditional connection
Testing and measurement techniques -Electrostatic discharge
IEC 61000-4-2
immunity test
Testing and measurement techniques - Radiated, radio-frequency,

IEC 61000-4-3
electromagnetic field immunity test
Testing and measurement techniques - Electrical fast transient/burst

IEC 61000-4-4
immunity test
IEC 61000-4-5 Testing and measurement techniques - Surge immunity test
Testing and measurement techniques - Immunity to conducted

IEC 61000-4-6
disturbances, induced by radio-frequency fields
Electromagnetic compatibility - Testing and measurement techniques

EN 61000-4-8
Power frequency magnetic field immunity test
Electromagnetic compatibility-Testing and measurement techniques-

IEC 61000-4-11
Voltage dips, short interruption and voltage variations immunity tests
Testing and measurement techniques - Voltage dips, short

IEC 61000-4-29
interruptions
Electromagnetic compatibility and Radio spectrum Matters (ERM);

ETSI EN 300 386 Telecommunication network equipment; Electro Magnetic
Compatibility (EMC) requirements
Elecromagnetic compatibility and Radio spectrum Matters (ERM);

ETSI EN 201468 Additional ElectroMagnetic Compatibility (EMC) telecommunications
equipment for enhanced availability of service in specific applications
Electromagnetic compatibility and Radio spectrum Matters (ERM);

ETSI EN 300127 Radiated emission testing of physically large telecommunication
systems
Power supply interface at the input to telecommunications

ETSI EN 300-132-2
equipment; Part 2: Operated by direct current (dc)
Version: B 15
Electromagnetic compatibility and electrical safety - generic criteria

GR-1089-CORE
for network telecommunications equipment
Resistibility of telecommunication equipment installed in installed in a

ITU-T K.20
telecommunications centre
1.4.5 Relevant Environment Standards
Environmental Engineering (EE)

Environmental conditions and environmental tests for
telecommunications equipment
Part 1-1: Classification of environmental conditions: Storage
ETSI EN 300 019-1-1
Class 1.1: Weather protected, partly temperature-controlled
storage locations
Class 1.2: Weather protected, not temperature-controlled storage
locations
ETSI EN 300 019-1-2
Part 1-2: Classification of environmental conditions: Transportation
Class 2.1: Very careful transportation
Class 2.2: Careful transportation

ETSI EN 300 019-1-3 Part 1-3: Classification of environmental conditions: Stationary use
at weather protected locations
Class 3.1: Temperature-controlled locations
Class 3.2: Partly temperature-controlled location
IEC 60068-2 Basic Environmental Testing Procedures
Environmental conditions appearing in nature - Earthquake

IEC 60721-2-6
vibration
Classification of environmental conditions - Part 3: Classification of
IEC 60721-3-1 groups of environmental parameters and their severities - Section
1: Storage
Classification of environmental conditions - Part 3: Classification of

IEC 60721-3-3 groups of environmental parameters and their severities - Section
3: Stationary use at weather protected locations
16 Version: B
Equipment Engineering (EE)

ETSI EN 300 753
Acoustic noise emitted by telecommunications equipment
Network Equipment-Building System (NEBS) Requirements:

NEBS GR-63-CORE
Physical Protection
Restriction of the use of certain hazardous substance in electrical

ROHS
and electronic equipment.
1.4.6 Relevant Grounding Standards
Earthing and bonding of telecommunication equipment in

ETS 300 253
telecommunication centres
Electromagnetic Compatibility and Electrical Safety - Generic Criteria
GR 1089 CORE
for Network Telecommunications Equipment
1.4.7 Relevant Noise Standards
ETSI EN 300 753 Acoustic noise emitted by telecommunications equipment
NEBS GR63-CORE NEBS Physical Protection
1.4.8 Relevant Fire Protection Standards
EN 60950 - 1(Europe) Safety of information technology equipment
ANSI/UL 60950 Safety of information technology equipment
CAN/CSA-C22.2 No.950-95 (North

Audio, Video and Similar Electronic Equipment
America)
IEC 60950 (International) Safety of information technology equipment
73/23/EEC (Europe) Low Voltage Directive
Version: B 17
1.4.9 Relevant Packaging Standards
ISO 780:1997 Packaging-pictorial marking for handling of goods
Packaging - Complete, filled transport packages and unit loads -

ISO 2234:2000
Stacking tests using a static load
Packaging - Complete, filled transport packages and unit loads -

ISO 2247:2000
Vibration tests at fixed low frequency
Packaging - Complete, filled transport packages - Vertical impact

ISO 2248:1985
test by dropping
ISO 3394:1984 Dimensions of rigid rectangular packages - Transport packages
ISO 3676:1983 Packaging - Unit load sizes - Dimension
Complete, filled transport packages - Distribution trials - Information

ISO 4178:1980
to be recorded
Complete, filled transport packages - General rules for the
ISO 4180:1980
compilation of performance test schedules
ETSI EN 300 019-2-3 Environment conditions and environmental test for

v2.1.2 telecommunications equipment
Non-Simulation Integrity Performance Test:

ISTA 1A
Procedure Packaged-Products 150 lb (68 kg) or Less
Partial-Simulation Performance Test:

ISTA 2A
Procedure Packaged-Products 150 lb (68 kg) or Less
General Simulation Performance Test:

ISTA 3A Procedure Packaged-Products for Parcel Delivery System Shipment
70 kg (150 lb) or Less
General specifications for products packaging of communication

EN 3873-83
equipments
EN 5034-85 Corrugated fibre board for export products
EN 6543-86 Corrugated box for export products
EN 8166-87 Package cushioning design method
1.5 Environment Requirements
This section introduces the operating, storage and transport environment

requirements of the equipment.
18 Version: B
1.5.1 Operating Environment
The operating environment should comply with the ETSI EN 300 019-1-3 and NEBS
GR-63-CORE standards.
Climate
The requirements of climate when the equipment is operating are described below.
Table 1-4 Requirements of Equipment Operating Humidity and Temperature
Item Requirement
Long-term operating temperature 0°C to 45°C

Long-term operating humidity 5% to 85%
Short-term operating temperature -10°C to 55°C

Short-term operating humidity 5% to 90%
Altitude -60 m to 4000 m
Temperature change rate ≤ 0.5℃/min
Air speed ≤ 5 m/s
Atmospheric pressure 70 kPa to 106 kPa
Solar radiation ≤ 700W/m2
Heat radiation ≤ 600W/m2
Note
u If the equipment is installed in a cabinet, the effect of radiation can be ignored. If the
equipment is installed outdoors, the effect of radiation should be considered, and
protection measures must be provided for the equipment.
u The temperature and humidity of the product should be measured at the positions 1.5m
above the floor and 0.4m away from the front of the cabinet in case that the cabinet is not
surrounded by protection boards.
u Short-term indicates that the continuous operating time does not exceed 96 hours or the
annual accumulative operating time does not exceed 15 days.
u When the altitude is between 1800m and 4000m, the operation temperature of the
equipment decreases by 1℃ each time the altitude increases by 220m.
To improve the reliability of product application, the equipment room should be

equipped with dedicated precision air conditioner to control the temperature and
humidity to the following range:
u Air conditioner control temperature: 15°C to 30°C
u Air conditioner control humidity: 40% to 75%
Version: B 19
Note:
The air conditioner should never be installed above the equipment, and
the air outlet should not face the equipment directly. The air conditioner
should be installed far away from windows to avoid blowing the moisture
outside the window to the equipment.
Biological Environment
u Microbe such as fungus and mould must be avoided.
u Rodents such as mice must be prevented.
Air Cleanliness
u The air must be free of explosive, electric-conductive, magnetic-conductive, or

corrosive dust.
u The concentration requirements for mechanically active substances are

described below in the table.
Mechanically Active Substance Content
Suspending dust ≤ 0.4mg/m3
Precipitable dust ≤ 15mg/(m2·h)
Gravel ≤ 300mg/m3
u The concentration requirements for chemically active substances are described

below in the table.
Chemically Active Substance Content
SO2 ≤ 0.30mg/m3
H2S ≤ 0.10mg/m3
NOx ≤ 0.50mg/m3
NH3 ≤ 1.00mg/m3
Cl2 ≤ 0.10mg/m3
HCl ≤ 0.10mg/m3
HF ≤ 0.01mg/m3
O3 ≤ 0.05mg/m3
20 Version: B
1.5.2 Storage Environment
The storage environment should comply with the ETSI EN 300 019-1-1 and NEBS
Climate
The climatic environment requirements for the storage of the equipment are as
described below.
Table 1-5 Climatic Environment Requirements for Equipment Storage
Item Requirement
Temperature -40℃ to +70℃

Relative humidity 5% to 100%
Temperature change rate ≤ 1℃/min
Solar radiation ≤ 1120 W/m2
Water Proofing
u The equipment on the site should be generally placed indoors.
u When the equipment is placed indoors, make sure the ground where the
equipment is placed is free of accumulated water, and there is no water
leakage to the packing case. The equipment should be placed away from
places where water leakage is possible, such as the fire control facilities and
heating facilities.
u For indoor storage of the equipment, make sure that the following requirements
are met at the same time:
4 The packing case is intact.
4 Necessary shelter measures should be taken to prevent rain water from

entering the packing case.
4 The place where the packing case is kept should be free of accumulated
water. More importantly, no accumulated water is allowed inside the
packing case.
4 The packing case should not be exposed to the sun directly.
Version: B 21
Air Cleanliness

corrosive dust.

Gravel ≤ 300mg/m3

below in the table.
SO2 ≤ 0.30mg/m3
H2S ≤ 0.10mg/m3
NO2 ≤ 0.50mg/m3
NH3 ≤ 1.00mg/m3
Cl2 ≤ 0.10mg/m3
HCI ≤ 0.10mg/m3
HF ≤ 0.01mg/m3
O3 ≤ 0.05mg/m3
1.5.3 Transport Environment
The transport environment should comply with the ETSI EN 300 019-1-2 and NEBS
Climate
The requirements of climate are described below.
22 Version: B
Table 1-6 Climatic Environment Requirements for Equipment Transport
Item Requirement
Temperature -40℃ to +70℃

Relative humidity 5% to 95%
Temperature change rate ≤ 1℃/min
Solar radiation ≤ 1120 W/m2
Water Proofing
The following requirements should be met at the same time during transport.
u The packing case is intact.
u Necessary shelter measures should be taken for the means of transport to

prevent rain water from entering the packing case.
u No accumulated water in the means of transport.
Air Cleanliness

corrosive dust.

Gravel ≤ 100mg/m3

below in the table.
Version: B 23
SO2 ≤ 1.00mg/m3
H2S ≤ 0.50mg/m3
NO2 ≤ 1.00mg/m3
HCl ≤ 0.50mg/m3
NH3 ≤ 3.00mg/m3
HF ≤ 0.03mg/m3
O3 ≤ 0.10mg/m3
Cl2 -
24 Version: B
2 Hardware Description
This chapter introduces the hardware of the product from the following aspects.
Appearance and Structure
Panel Description
Safety Signs
Pluggable Optical Modules
Optical Fibers and Cables
Mounting Ears
Version: B 25
2.1 Appearance and Structure
The CiTRANS 610A uses the box-shaped structure for flexible deployment.
The CiTRANS 610A consists of a subrack and a board secured in the subrack. It
can be classified into AC chassis and DC chassis according to the type of power
input/output interfaces.
Structure
Figure 2-1 and Figure 2-2 show the structure of the AC chassis and DC chassis.
Table 2-1 describes the structure.
(1) Heat vents (2) Subrack (3) Subrack earth ground

point
(4) AC power input (5) Automatic circuit breaker (6) Board

interface (ACB) for AC power supply
(7) Service Interface (8) Auxiliary interface and (9) Button

service interface
(10) Indicator LEDs
Figure 2-1 Structure of AC Chassis
26 Version: B
(1) Heat vents (2) Subrack (3) Subrack earth ground point
(4) DC power input (5) Automatic circuit breaker (6) Board

interface (ACB) for DC power supply
(7) Service Interface (8) Auxiliary interface and (9) Hidden button
service interface
(10) Indicator LEDs
Figure 2-2 Structure of DC Chassis
Table 2-1 Description of Structure
SN Name Function
The air outlet of the equipment for heat dissipation when
(1) Heat vent
the equipment is working.
The subrack height is 1U (1U=44.5mm) and it is fixed with

(2) Subrack
the panel.
Earth ground point of Connects the cabinet vertical mounting flange with the
(3)
the subrack subrack.
The AC power input interface receives AC power and
AC/DC power input supplies the power to the built-in AC power supply system.
(4)
interface The DC power input interface receives DC power and
supplies the power to the built-in power supply system.
Automatic circuit
Disconnects or connects the AC/DC power supply of the
(5) breakers (ACBs) for
equipment.
AC/DC power supply
Version: B 27
Table 2-1 Description of Structure (Continued)
SN Name Function
The board is secured in the subrack. Power input
(6) Board interfaces, indicator LEDs, buttons, auxiliary interfaces
and service interfaces are located on the panel.
u Two GE/FE adaptive optical interfaces (GE/FE3 to

GE/FE4)
(7) Service Interface
u Two GE optical interfaces (GE5 and GE6)
For detailed function descriptions, see Panel Description.
u Two E1 service interfaces, four GE/FE electrical

Auxiliary interface interfaces (GE/FE1 to GE/FE4)
(8)
and service interface u One TOD/CLK (external time / external clock)
interface
Resets the board. For detailed function descriptions, see
(9) Hidden button
Panel Description.
Indicates the status of the equipment and interfaces. For

(10) Indicator LED
detailed function descriptions, see Panel Description.
2.2 Panel Description
The subrack provides indicator LEDs, buttons and various interfaces on the panel.
Figure 2-3 shows the panel of the CiTRANS 610A.
Figure 2-3 Panel
Indicator LED
Table 2-2 lists the meanings of indicator LEDs on the equipment.
28 Version: B
Table 2-2 Meanings of Indicator LEDs
Indicator LED Description
Power indicator: ON indicates that the power supply is

PWR (green)
normal.
Working indicator: Blinking indicates the equipment is
RUN (green)
operating.
Alarm indicator: ON indicates that a alarm occurs on the

ALM (red)
equipment.
Link indicator of the optical interface: ON indicates that the

L/A3 to L/A6 (green)
port is linked up normally.
u Yellow indicator: ON indicates that the port is linked

Status indicator of RJ45 interface up normally.
(yellow and green) u Green indicator: Blinking indicates that the port is
receiving / transmitting data.
Button
The RST button, which is a hidden button, is located on the panel. When this button
is pressed down, the equipment will be soft reset.
Note:
The operation of the hidden button requires threadlike tools such as a nib
or a needle.
Sign
The equipment label is attached to the panel of the equipment. The label contains
information such as SN and MAC address of the equipment.
Interface
Table 2-3 lists the quantity and usage of various interfaces on the equipment.
Version: B 29
Table 2-3 Interface Description
Interface Name Interface type Usage Description of

Interface Pins and
Corresponding
Cables
Network management See Service /
F RJ45
interface Management Cable.
Input / output interface of E1

E1 RJ45 See E1 Cable.
service
Input/output interface of
TOD/CLK RJ45 See Clock Cable.
external clock/time signals
Input/output interface of GE/ See Optical Fibers

GE/FE1 to GE/FE4 RJ45
FE electrical signals and Cables.
GE/FE3 to GE/ Input/output interface of GE/

Note 1
SFP
FE4 FE optical signals
See Patch Cord.
Input / output interface of
GE5 and GE6 SFP
GE/FE optical signals
Accesses 110V or 220V AC

AC power See AC Power
AC power supply for the
interface Cable.
equipment
DC power Accesses -48V DC power See DC Power

DC
interface supply for the equipment Cable.
Note 1:
u The GE/FE3 RJ45 interface and GE/FE3 SFP interface constitute a Combo
interface group. You can use one of them as required, but the two interfaces
cannot work at the same time. When one interface is enabled, the other one is
automatically disabled.
u The GE/FE4 RJ45 interface and GE/FE4 SFP interface constitute a Combo
interface group. You can use one of them as required, but the two interfaces
cannot work at the same time. When one interface is enabled, the other one is
automatically disabled.
2.3 Safety Signs
The safety and warning signs on the front panel remind users to operate and
maintain the equipment safely and avoid bodily harm. Table 2-4 describes the
meanings of these signs.
30 Version: B
Table 2-4 Safety and Warning Signs
Label Position (Using an AC Chassis

Sign Description
for Example)
The subrack earth ground sign. This

sign marks the location of the
subrack earth ground pole.
The laser class sign. This sign

marks the optical source class of the
optical interface on a card. The
maintenance staff must prevent the
Note 1 optical source from entering eyes
directly to avoid bodily harm.
Note 1: CLASS1 indicates that the laser is safe without radiation under normal conditions.
2.4 Pluggable Optical Modules
The optical interface of the CiTRANS 610A uses the pluggable SFP optical module.
The SFP optical module is a protocol-independent optical transceiver used for
optical communication. It implements O/E and E/O conversion of signals, and
supports query of information such as the transceiver performance and
manufacturer.
Table 2-5 lists the interfaces applicable to the SFP optical module.
Table 2-5 Interfaces Applicable to the SFP Optical Module
Interface type Interface Name
GE/FE optical interface GE/FE3 to GE/FE4

GE optical interface GE5 and GE6
Appearance of Optical Module
Figure 2-4 shows the appearance of the SFP optical module.
Version: B 31
Figure 2-4 Appearance of SFP Optical Module
Optical Module Label
The optical module labels are attached to the optical modules for identifying different
types of optical modules. Figure 2-5 shows the optical module label.
32 Version: B
(1) Material number (2) Order number (3) Fiber connector type
(4) Rate (5) Transmission distance (6) Operating wavelength
(7) Material code of module

part
Figure 2-5 Optical Module Label
Each type of optical module corresponds to a specific code. Table 2-6 describes the
optical module codes and types. For the technical specifications of optical interfaces,
see Technical Specifications of Optical Interfaces.
Table 2-6 Optical Module Types
Optical Interface Type Basic Information
1000BASE-LX (10km) Optical module, SFP, 1310nm, GE, LC, single-mode, 10 km
1000BASE-EX (40km) Optical module, SFP, 1310nm, GE, LC, single-mode, 40km
1000BASE-ZX1 (80km) Optical module, SFP, 1540nm, GE, LC, single-mode, 80 km
Version: B 33
2.5 Optical Fibers and Cables
This section describes the optical fibers and cables used by the equipment.
2.5.1 Patch Cord
The CiTRANS 610A uses optical fibers to input/output Ethernet service signals.
Table 2-7 describes the commonly used optical fiber connectors (LC/PC, FC/PC
and SC/PC types).
Table 2-7 Type and Usage of Commonly Used Optical Fiber Connectors
Type Description Usage
Used at all the optical interfaces

Plug-in square optical fiber connector/
LC/PC on the CiTRANS 610A or at the
protruding polished
client-side optical interfaces
Round optical fiber connector/protruding

FC/PC Used at the client-side ODF or at
polished
the optical interfaces on other
Square optical fiber connector/protruding
SC/PC equipment
polished
Structure of LC/PC-type Optical Fiber Connector
Figure 2-6 shows the LC/PC-type optical fiber connector.
Figure 2-6 LC/PC-type Optical Fiber Connector
Only axial operations instead of rotation are required to insert or remove the LC/PC-
type optical fiber connector. The procedures of inserting or removing an LC/PC-type
optical fiber connector are described as follows:
u To insert the fiber into the LC/PC-type connector, align the head of the fiber with
the optical interface and push the fiber into the connector with proper force.
34 Version: B
u To remove the fiber, press the clip first, push the fiber connector inward slightly,
and then pull out the connector.
Structure of FC/PC-type Optical Fiber Connector
Figure 2-7 shows the appearance of the FC/PC-type optical fiber connector.
Figure 2-7 FC/PC-type Optical Fiber Connector
The procedures of inserting or removing an FC/PC-type optical fiber connector are

described as follows:
u To insert the fiber into the FC/PC-type connector, align the head of the fiber with
the optical interface carefully to avoid damaging the internal ceramic pipe. After
inserting the fiber to the bottom of the optical interface, rotate the external
screw clockwise to tighten the optical interface.
u To remove the fiber, rotate the external screw of the optical interface
counterclockwise. When the screw is loosened, remove the fiber from the
optical interface with proper force.
Structure of SC/PC-type Optical Fiber Connector
Figure 2-8 shows the appearance of the SC/PC-type optical fiber connector.
Figure 2-8 SC/PC-type Optical Fiber Connector
The procedures of inserting or removing an SC/PC-type optical fiber connector are

described as follows:
Version: B 35
u To insert the fiber into the SC/PC-type connector, align the head of the fiber with
the optical interface and push the fiber into the connector with proper force.
u To remove the fiber, press the clip first, push the fiber connector inward slightly,
and then pull out the connector.
Connection
Table 2-8 Connection of Patch Cord
Connector Description
LC/PC-type Optical Fiber

Used for all the optical interfaces on the CiTRANS 610A
Connector
u LC/PC-type Optical
Fiber Connector
u SC/PC-type Optical Used at the client-side ODF or at the optical interfaces on other
Fiber Connector equipment
u FC/PC-type Optical
Fiber Connector
Note:
All the optical interfaces on the equipment use the LC/PC-type optical
fiber connector. If the interface on the opposite end equipment is of
another type, you can select an optical fiber with one end of LC/PC
connector and the other end of other type of connector.
Table 2-9 describes the technical specifications of the patch cord.
Table 2-9 Technical Specifications of the Patch Cord
Name Cable Type Interface Type
2.0mm single-mode optical fiber (LC/PC-LC/PC-S-20) LC/PC-LC/PC

Patch cord
2.0mm single-mode optical fiber (LC/PC-FC/PC-S-20) LC/PC-FC/PC
2.0mm single-mode optical fiber (LC/PC-SC/PC-S-20) LC/PC-SC/PC
36 Version: B
2.5.2 Service / Management Cable
The service / management cable uses the Ethernet cable to input and output
Ethernet signals / network management signals.
The Ethernet cable is also called network cable. It can be classified into straight-
through cable and cross-over cable according to the connection scheme of copper
wires in the cable.
The Ethernet cable should be made on site.
Structure
Figure 2-9 shows the appearance of the Ethernet cable.
Figure 2-9 Appearance of Ethernet Cable
The Ethernet cable uses the RJ45 connector, as shown in Figure 2-10.
Figure 2-10 The RJ45 Connector
Connection
Table 2-10 and Table 2-11 list the connection of the Ethernet cable.
Version: B 37
Table 2-10 Pinout and Wiring of Straight-through Cable
Pin of Connector Pin of Connector

Color Relationship
X1 X2
X1.1 X2.1 White / orange
Twisted pair
X1.2 X2.2 Orange
X1.3 X2.3 White / green

Twisted pair
X1.6 X2.6 Green
X1.4 X2.4 Blue
Twisted pair
X1.5 X2.5 White / blue
X1.7 X2.7 White / brown
Twisted pair
X1.8 X2.8 Brown
Table 2-11 Pinout and Wiring of Cross-over Cable
Cross-over Cable of FE Interface Cross-over Cable of GE Interface

Pin of Pin of Rela- Pin of Pin of
Rela-
Connec- Connector Color tion- Connec- Connec- Color
tionship
tor X1 X2 ship tor X1 tor X2
White / White /
X1.1 X2.3 Twisted X1.1 X2.3 Twisted
orange orange
pair pair
X1.2 X2.6 Orange X1.2 X2.6 Orange
White / White /
X1.3 X2.1 Twisted X1.3 X2.1 Twisted
green green
pair pair
X1.6 X2.2 Green X1.6 X2.2 Green
X1.4 X2.4 Blue X1.4 X2.7 Blue
Twisted Twisted
White / White /
X1.5 X2.5 pair X1.5 X2.8 pair
blue blue
White / Twisted White / Twisted
X1.7 X2.7 X1.7 X2.4
brown pair brown pair
X1.8 X2.8 Brown X1.8 X2.5 Brown
The management interface F is a hybrid interface integrating management network

interface and management Console interface. Table 2-12 describes the connection
of the management cable.
38 Version: B
Table 2-12 Pinout and Wiring of Management Cable
Pins of Relation-
Color Usage
Connector ship
Transmit positive of the network

1 White / orange
Twisted management interface
pair Transmit negative of the
2 Orange
network management interface
Receive positive of the network

3 White / green
Twisted management interface
pair Receive negative of the network
4 Green
management interface
5 Blue Twisted Console earth ground terminal
6 White / blue pair Console receive end

7 White / brown Twisted Undefined
8 Brown pair Console transmit end
Table 2-13 describes the technical specifications of the Ethernet cable.
Table 2-13 Technical Specifications
Item Parameter
Network interface connector, 8PIN, 8bit,
Connector X1 / X2
crystal head
Communication cable, CAT-5 twisted pair,

Cable type
24AWG
Number of core 8
2.5.3 Clock Cable
The CiTRANS 610A uses the external clock cable with the RJ45 connector to input
and output clock signals.
The clock cable is used for the TOD/CLK interface of the subrack. It should be made
on site.
Version: B 39
Structure
Figure 2-11 shows the appearance of the clock cable.
Figure 2-11 Appearance of Clock Cable
The clock cable uses the RJ45 connector, as shown in Figure 2-12.
Connection
Table 2-14 lists the connection of the clock cable.
Table 2-14 Pinout and Wiring of Clock Cable
Pins of Relation-
Color Usage
Connector ship
1 White / orange Twisted Receive negative of the CLK
2 Orange pair Receive positive of the CLK
3 White / green Twisted Negative of 1PPS signal
4 Green pair Positive of 1PPS signal
Twisted
5 Blue Transmit negative of the CLK
pair
40 Version: B
Table 2-14 Pinout and Wiring of Clock Cable (Continued)
Pins of Relation-
Color Usage
Connector ship
6 White / blue Transmit positive of the CLK
7 White / brown Twisted Time information negative
8 Brown pair Time information positive
Table 2-15 describes the technical specifications of the clock cable.
Table 2-15 Technical Specifications of the Clock Cable
Item Parameter
Network interface connector, 8PIN, 8bit,
RJ-45 connector
crystal head
Cable type Ethernet cable & coaxial cable

Number of core 8
2.5.4 E1 Cable
The E1 cable is used to connect the equipment with the DDF for inputting and
outputting E1 signals. You need to make the E1 cable on site.
Structure
Figure 2-13 shows the appearance of the E1 cable.
Figure 2-13 Appearance of E1 Cable
Version: B 41
The E1 cable uses the RJ45 connector, as shown in Figure 2-14.
Connection
Table 2-16 lists the connection of the E1 cable.
Table 2-16 Pinout and Wiring of E1 Cable
Pins of
Color Relationship Usage
Connector
1 White Transmit positive of the interface 1
Twisted pair
2 Orange Transmit negative of the interface 1
3 White Transmit positive of the interface 2

Twisted pair
4 Green Receive negative of the interface 1
5 Blue Receive negative of the interface 1

Twisted pair
6 White Transmit negative of the interface 2
7 White Receive positive of the interface 2

Twisted pair
8 Brown Receive negative of the interface 2
Table 2-17 lists the technical specifications of the E1 cable.
Table 2-17 Technical Specifications of the E1 Cable
Item Parameter
RJ-45 connector Network interface connector, 8PIN, 8bit, crystal head
Cable type Balanced cable, 120Ω, SEYVP 4×2×0.4, grey
Number of core 8
42 Version: B
2.5.5 AC Power Cable
The CiTRANS 610A uses the AC power cable to access the external power supply.
Structure
Figure 2-15 shows the structure of the AC power cable.
Figure 2-15 Appearance of AC Power Cable
Connection
Table 2-18 describes the connection of the AC power cable.
Table 2-18 Connection of AC Power Cable
Three-conductor connector Connects with the equipment power interface
Small three-conductor South

Connects with the external AC power supply
Africa plug
Table 2-19 describes the technical specifications of the AC power cable.
Version: B 43
Table 2-19 Technical Specifications of AC Power Cable
Item Parameter
Cable type Three-conductor AC power cable/3 × 0.75/30m
Connector Small three-conductor South Africa plug
2.5.6 DC Power Cable
The CiTRANS 610A uses the DC power cable to access the external DC power
supply.
Structure
Figure 2-16 shows the structure of the DC power cable.
(1) Bare wire (2) Three-conductor plug
Figure 2-16 Appearance of DC Power Cable
Connection
Table 2-20 describes the connection of the DC power cable.
Table 2-20 Connection of DC Power Cable
Three-conductor plug Connects with the DC power interface of the equipment
Bare wire Connects with the external DC power supply
44 Version: B
Table 2-21 describes the technical specifications of the DC power cable.
Table 2-21 Technical Specifications of DC Power Cable
Item Parameter
Cable type Power cable (RVV 3 × 0.5)
Connector Round three-conductor plug
2.6 Mounting Ears
The mounting ears are optional components. You can select the desired type of
mounting ear as required.
Table 2-22 lists the mounting ears used for installing the CiTRANS 610A in a
cabinet.
Table 2-22 Introduction to Mounting Ears
Appearance Application Scenario Dimensions
Left side of the subrack See Figure 2-17
Right side of the

See Figure 2-18
subrackNote
Note 1: The length of the mounting ear at the right side of the subrack can be adjusted to fit for
the 19-inch cabinet and 21-inch cabinet according to the application scenarios.
Version: B 45
Figure 2-17 Mounting Ear with Non-adjustable Dimensions (Unit: mm)
Figure 2-18 Mounting Ear with Adjustable Dimensions (Unit: mm)
46 Version: B
3 Equipment Commissioning
This chapter introduces how to create network topology and connect the equipment
with the OTNM2000 by commissioning. Besides, this chapter introduces the
detailed configuration and test methods with examples.
Commissioning Flow
Creating Network Topology
Testing the NE Connectivity
Performing Time Calibration and Downloading Configuration
Version: B 47
3.1 Commissioning Flow

Prerequisite
u You have installed the equipment referring to CiTRANS 610A Packet Transfer
Platform Quick Installation Guide.
u You have installed the OTNM2000 referring to e-Fim OTNM2000 Element

Management System Installation Guide.
u The management channel and service channel offered by another vendor must
be the VPWS private line service channels.
u The MTU of the channel offered by another vendor should be set to a value
larger than 1600.
u It is advisable to disable the broadcast suppression function of another vendor.
Commissioning Flow
Figure 3-1 shows the commissioning flow of the CiTRANS 610A.
Figure 3-1 Commissioning Flow
48 Version: B
Table 3-1 Commissioning Flow of the CiTRANS 610A
Commissioning Flow Description
The OTNM2000 can communicate

with the equipment only after the
Connecting the EMS and the Equipment
OTNM2000 server is connected with
the equipment.
Check the services relevant to the

Checking the Network Management Process OTNM2000 to ensure the normal
operation of the OTNM2000.
Configuring the
Management Program Create network topology in the
Configuring the Project, OTNM2000 and complete the basic
Network Block, NE and configuration including the
Basic Configuration
Virtual NE management program configuration,
Configuring Cards NE configuration and topology
connection configuration.
Configuring Topology
Connections
Configuring IP Address of Set the IP addresses of the local NE
Local NE and adjacent NE based on SN. If the
Configuring IP Address of MAN uses the equipment offered by
Configuring NE IP Adjacent NE another vendor, the MCC VLAN
Address Based on SN should be set. See CiTRANS 650
Configuration Method of Small Flexible Optical Transport
MCC VLAN Platform Configuration Guide for the

configuration method.
Test whether the communication

Testing the NE Connectivity between the OTNM2000 and NE is
normal.
Calibrate the NE time. After the NE
time is synchronized with the
Performing Time Calibration and Downloading
OTNM2000, deliver the
Configuration
management configuration and
equipment configuration.
Version: B 49
3.2 Creating Network Topology
Creating network topology indicates configuring equipment networking data

according to the actual networking condition of the equipment and implementing
communication between the OTNM2000 and the equipment, so that you can
configure the equipment via the OTNM2000.
3.2.1 Connecting the EMS and the Equipment
The OTNM2000 can communicate with the equipment only after the OTNM2000
server is connected with the equipment. This section introduces how to connect the
OTNM2000 server with the equipment via the Hub or an Ethernet cable.
Prerequisite
The OTNM2000 server and the equipment have been started normally.
Procedure
1. Perform physical connection.
4 Connection via the Hub:
a) Insert one end of the straight-through cable into the network interface
on the network card of the OTNM2000 server. Connect the other end
to the network interface of the Hub.
b) Take another straight-through cable. Connect one end of the cable to

the network interface of the Hub and insert the other end to the F
interface on the panel of the CiTRANS 610A.
4 Connection via the Ethernet cable:
Connect one end of a cross-over cable to the network interface on the

network card of the OTNM2000 server and insert the other end to the F
interface on the panel of the CiTRANS 610A.
2. Check on the OTNM2000 server whether the network card connected by the
Ethernet cable is the device network card. If not, connect the Ethernet cable to
another network card of the OTNM2000 server.
50 Version: B
Note:
The local area connection status of the device network card is Ethernet
cable unplugged when no Ethernet cable is connected to it.
3. Observe the indicator LED of the network interface on the network card of the
OTNM2000 server and that of the F interface on the panel of the CiTRANS
610A.
4 Normal: The indicator LED is solid green or blinks quickly in yellow.
4 Abnormal: The status of the interface indicator is not as the above

described. In this case, replace the Ethernet cable or reboot the equipment.
If the fault persists, contact FiberHome engineers for troubleshooting.
3.2.2 Checking the Network Management Process
The system will add OTNM2000-related services with the prefix EMS such as
EMS_DataBusServer and EMS_DispServer after the OTNM2000 and the MySQL
database are successfully installed. Make sure the services listed in Table 3-2 are
started to prevent the OTNM2000 operation abnormality.
Prerequisite
The server installed with the OTNM2000 has been started normally.
Procedure
1. On the OTNM2000 server, click Start→Run.
2. Enter services.msc in the Run dialog box that appears, and click OK to bring
up the Services window.
Version: B 51
3. Check whether the services listed in Table 3-2 are Started in the Services
window. If any service is not started, right-click it and select Start from the
shortcut menu to start the service.
Table 3-2 The OTNM2000 Services List
Number Name Remark

Optional. The northbound interface related service,
1 EMS_ArmyApi which should be started when the third party network
management system is connected.
2 EMS_cfgdatamgr The configuration data import/export service.
The data communication infrastructure component; the

3 EMS_DataBusServer message bus responsible for communication between
component and module.
The data distribution component which implements

4 EMS_DispServer
distribution of data processing result.
The data processing component which receives and

5 EMS_Dtserver
processes the commands from other components.
The data save service which manages the database

6 EMS_Dumper
capacity.
7 EMS_FileServer The FTP file transfer service.

The FTP service which is responsible for
8 EMS_FileZilla Server
communication with the equipment in the FTP mode.
9 EMS_IceNode The ICE node management component.
10 EMS_IceRegistry The ICE registration service.
11 EMS_Manager2 The equipment communication management service.
The monitoring service which is used for monitoring the

12 EMS_Monitor running status of other services and providing the
OTNM Ping function.
13 EMS_MsmpProxyServer The multi-service proxy server component.
52 Version: B
Table 3-2 The OTNM2000 Services List (Continued)
Number Name Remark

14 EMS_MSMPServer The multi-service management service.
15 EMS_NeCfgServer The NE configuration service.
Optional. The API interface component which provides

data interfaces externally based on the RPC mode. It
16 EMS_OtnmApiServer
should be started when the OTNM2100 or the third
party network management system is connected.
17 EMS_OtnmCfgServer The configuration management service.
Optional. The SMS proxy service. It should be started

18 EMS_OtnmSms_Agent
when the remote alarm notification function is enabled.
Optional. The performance data collection service. It
19 EMS_PmDataGather should be started when the second-level performance
collection function is enabled.
The query service component which provides alarm,
20 EMS_QueryServer
performance and log query service.
21 EMS_RsyncServer The file synchronization service.
22 EMS_unmcmagent The client end of service management.
23 EMS_unmcmservice The server end of service management.
24 MySQL The MySQL database service.
Optional. The Tomcat service which should be started

25 Apache Tomcat tomcat
when you view the on-line help file.
Note:
If you fail to log into the OTNM2000 after the required services are all
started, the OTNM2000 program may be installed incorrectly. If the fault
persists after the re-installation, contact with FiberHome engineers.
3.2.3 Basic Configuration
In the OTNM2000, complete the basic configuration of all the NEs in the entire
network, including the management program configuration, network block and NE
configuration, card configuration and topology connection configuration.
Version: B 53
3.2.3.1 Logging into the OTNM2000
You can configure and manage the network after logging into the OTNM2000.
Prerequisite
u The server installed with the OTNM2000 has been started normally.
u The OTNM2000-related services are started normally.
Procedure
1. Double-click on the desktop of the network management server to

open the OTNM2000 login dialog box.
2. Enter the user name and password.
Note:
The default user name and password for the advanced user are both
admin after the installation of the OTNM2000.
3. Click OK to bring up the OTNM2000 window.
54 Version: B
Note:
Modify the password for advanced user immediately after logging into the
OTNM2000 to ensure the security of the network management system.
3.2.3.2 Configuring the Management Program
Configure the management program and set the parameters such as the database
IP address, and the IP address and port of the network management server for
communicating with equipment.
Prerequisite
u You have logged into the OTNM2000.
u You have learned about the project network planning.
u You are an EMS user with Operator Group authority or higher.
Procedure
1. In the OTNM2000 window, click Configuration→Manager Service Config in

the menu bar to bring up the Manager Service Config tab.
2. Click Add to bring up the Add Manager Service dialog box. Set the relevant
parameters of the management service in the Add Manager Service dialog
box according to the project planning.
Version: B 55
Item Value Range Parameter Description
Sets the management program number.

Generally the default value on the OTNM2000
Manager No -
is used. And you can also set it to another
number.
The IP address of the database network card
Server IP - on the OTNM2000 server. It should be unique
within the entire project.
UDP_ASON, UDP_
SDH and TP4_2 The type of the communication protocol. Select
Protocol Type
Default value: UDP_ UDP_ASON for the PAN equipment.
ASON
The IP address of the equipment network card
of the OTNM2000 server, that is, the IP
Listen IP Of Network address of the network card communicating
-
Card with the local NE, which is in the same network
segment as the local NE. It should be unique
within the entire project.
The monitoring port of the equipment network

Listen Port Of 7889, 7888
card of the OTNM2000 server. Select 7889 for
Network Card Default value: 7889
the PAN equipment.
3. Click OK. Then click OK in the alert box that appears.
56 Version: B
4. You can view the configured management program parameters in the Manager
Service Config tab.
3.2.3.3 Configuring the Project, Network Block, NE and Virtual NE
Each actual equipment is represented as an NE in the OTNM2000. You should

create the project, network block and corresponding NE in the OTNM2000 so that
the OTNM2000 can manage the actual equipment.
Prerequisite
u You have learned about the project network planning.
u You have completed the management program configuration.
Procedure
Note:
u If the CiTRANS 610A and the CiTRANS 650 are networked together,
you should set independent network block for the CiTRANS 610A
and the CiTRANS 650 respectively.
u To emulate the interconnection with the MAN offered by another

vendor, you can create virtual NEs to emulate the MAN offered by
another vendor. Virtual NEs represents no actual equipment and
performs no service delivery, but only serve for the end-to-end
service configuration between the CiTRANS 610As.
1. Set the project property. In the OTNM2000 window, right-click a project object
in Logical Tree and select Property from the shortcut menu. Modify Project
Name according to the project planning and click OK.
Version: B 57
2. Create a network block.
1) Right-click a project object in Logical Tree and select New Network

Block from the shortcut menu. Then set Part No, Part Name and
Manager Service according to the project planning.
58 Version: B
Table 3-3 Configuration Parameters of Network Block
Sets the network block number. Generally the number

automatically assigned by the OTNM2000 is used. And
Part No -
you can also set it to another number. The network block
number should be unique in the entire project.
Sets the network block name. You can modify the default
Part Name - network block name according to the project planning. The
network block name should be unique in the entire project.
Selects the Manager Service. The first configured

Manager Service is selected by default. And you can also
Manager Service -
select another Manager Service according to the project
planning.
2) Add an MA NE. You should add an MA NE when creating a network block.
Click at the right side of Ma NE No to bring up the Add Ma Ne dialog

box. Set the parameters such as NE No, NE Type and IP Address
according to the project planning and click OK.
Table 3-4 Configuration Parameters of NE
Item Value Parameter Description

Range
Sets the NE No. Generally keep the default setting. The NE No.
NE No 1 to 255
under the same network block should not be duplicated.
NE Type - Sets NE Type of the CiTRANS 610A to CiTRANS 610A.
Sets the bureau name. You can modify the default Bureau Name
Bureau
- according to the project planning. The Bureau Name under the
Name
same network block should not be duplicated.
Version: B 59
Table 3-4 Configuration Parameters of NE (Continued)
Item Value Parameter Description

Range
Sets the NE name. You can modify the default NE Name

NE Name - according to the project planning. The NE Name under the same
network block should not be duplicated.
The IP address of the NE. It should be unique in the entire

network.
If the NE is connected to the EMS server using an Ethernet
IP Address -
cable, the NE IP address should be on the same subnet as the
IP address of the network card on the EMS server. Otherwise,
SN discovery of adjacent NEs will be affected.
Sets the IP mask address of an NE. 255.255.255.0 is

IP Mask -
recommended.
Switch1 and Switch2 consist of the IDs of NE in the hexadecimal
Switch1/-
0x1 to 0xFF format. The combination of Switch1 and Switch2 should be
Switch2
unique in the entire network.
Note:
u Items not listed in the table are usually set by default.
u The parameters such as IP Address and IP Mask set during the

creation of network block and NE will be mapped to the NE Ip
Remote Config window synchronously.
3) In the Add Part dialog box, confirm that the Ma NE No is updated, and
click OK to view the configuration result.
60 Version: B
3. Create an NE.
1) Right-click a desired network block in Logical Tree and select New NE to

bring up the Add Ne dialog box. Set the parameters such as NE No, NE
Type and IP Address according to the project planning and click OK. See
Table 3-4 for the NE configuration parameters.
2) View the configuration result in the Logical Tree pane.
4. (Optional) Create a virtual NE.
1) Right-click a desired network block in Logical Tree and select New NE to

bring up the Add Ne dialog box. Set the parameters such as NE No and
NE Type according to the project planning and click OK.
Version: B 61
Table 3-5 Configuration Parameters of Virtual NE
Sets the NE No. Generally keep the default setting. The NE

NE No 1 to 255
No. under the same network block should not be duplicated.
Sets the network element type. Set the NE Type of the

NE Type -
virtual NE to Virtual NE.
Sets the bureau name. You can modify the default Bureau
Name according to the project planning. The Bureau Name
Bureau Name -
under the same network block should not be duplicated. It is
set to Virtual NE3 in this example.
Sets the NE name. You can modify the default NE Name

according to the project planning. The NE Name under the
NE Name -
same network block should not be duplicated. It is set to
Virtual NE3 in this example.
Select or
clear the
When the item is selected, configuration items such IP
check box.
Virtual NE address are invalid. For virtual NEs, selecting the check box
The check
is recommended.
box is cleared
by default.
2) View the configuration result in the Logical Tree pane.
62 Version: B
3.2.3.4 Configuring Cards
Prerequisite
You have completed the NE configuration.
Procedure
1. In the OTNM2000 window, double-click the desired NE in the Logical Tree

pane to bring up the subrack view of the NE.
Version: B 63
2. Right-click the corresponding slot in the subrack view, select Replace the
Board→Replace the XCTR2 Board, and click Replace in the alert box that
appears.
3. Click OK in the Operation Warning alert box that appears and view the
configuration result.
3.2.3.5 Configuring Topology Connections
You need to create network topology between NEs to ensure that the configuration
in the OTNM2000 consists with the network arrangement on the project site.
Prerequisite
You have completed the card configuration.
Procedure
1. Select the NE or network block of a project in the Logical Tree pane, press the
left key on mouse and drag it to the topology view.
64 Version: B
Note:
Selecting the network block of a project means selecting all its contained
NEs.
2. Click to enable the edit function. Select the corresponding NE, and drag it
to the proper position.
3. Right-click the source NE to be connected and select Add Link from the
shortcut menu.
4. Mouse over the sink source to be connected and click it to bring up the Add
Link... dialog box.
Version: B 65
5. Set the parameters such as Board and Port in the Add Link... dialog box.
4 If the source and sink NEs to be connected are normal NEs:
According to the project planning, set Board and Port of the source and
sink NEs to be connected, and click Add to save the setting. Then you can
view the added link on the topology view.
66 Version: B
Table 3-6 Parameters of Add Link
The Board in Source port info is the name of card

corresponding to the source NE to be connected. The Board
Board - in Dest port info is the name of card corresponding to the
sink NE to be connected. You can click following the card
name to select in the drop-down list.
The Port in Source port info shows the port on the card
corresponding to the source NE. The Port in Dest port info
shows the port on the card corresponding to the sink NE. As
Port -
long as you select the correct card, the corresponding ports
will be displayed automatically in the system and you can
select the port needed from the drop-down menu.
Note: Source port info shows the information of the source NE to be connected and Dest port
info shows that of the sink NE.
4 If the source and sink NEs to be connected are virtual NEs:
According to the project planning, set Board and Port of the normal NEs,
set Port and Type of the virtual NEs, and click Add to save the setting.
Then you can view the added link on the topology view.
Version: B 67
Table 3-7 Parameters of Add Link (Virtual NE)
Value
Item Parameter Description
Range
The Board is the name of the card corresponding to the

Board - source or sink NE to be connected. You can click at the
right side of the card name to select in the drop-down list.
The Port is the port on the card corresponding to the source

or sink NE to be connected. As long as you select the correct
Port - card, the corresponding ports will be displayed automatically
in the system and you can select the port needed from the
drop-down menu.
Sets the port name according to the network block number

Port (Virtual NE) - and NE number of the equipment interconnected with the
virtual NE, or according to the project planning.
Sets the port type according to the project planning or remain

Type (Virtual NE) -
the default settings, which will not influence the service.
3.2.4 Configuring NE IP Address Based on SN
The CiTRANS 610A writes the NE IP address to the equipment based on SN.
Basic Concepts
u SN
The SN is a 12-bit serial number of the equipment, which is similar to the MAC
address of a computer, so as to guarantee its uniqueness in the entire network.
The SN of the CiTRANS 610A has been downloaded to the equipment before
delivery. Generally the SN label is attached to the front panel of the equipment.
u Local NE
The local NE indicates the NE connected to the OTNM2000 computer directly

via an Ethernet cable (the connection port is F port).
u Source NE
The source NE indicates the NE whose IP address has been configured

successfully and is connected to the OTNM2000.
u Adjacent NE
68 Version: B
The adjacent NE indicates the NE connected with source NE via optical path or
Ethernet cable without any other NE between them; or the NE interconnected
with the source NE via the MAN offered by another vendor in the Overlay mode.
u Overlay
The Overlay mode indicates encapsulating the management MCC packets and
service packets sent by the FiberHome PAN equipment with a VLAN tag of the
MAN channel offered by another vendor when the MAN provides the
management channel and service channel. Therefore, the packets will be
transparently transmitted through the MAN offered by another vendor.
The management channel and service channel offered by another vendor must
be the VPWS private line service channels.
Configuration Method for the NE IP Address
You can set the NE IP address in local mode or remote mode. The NEs directly
connected with the OTNM2000 can be set using the method of setting the local NE
IP address, while the NEs not directly connected with the OTNM2000 can be set
using the method of setting the adjacent NE IP address. The following introduces
both modes, as shown in Figure 3-2.
Figure 3-2 Network Diagram for Configuring the NE IP Address Based on SN
u Configuring the IP address of local NE (local download mode)
Connect the OTNM2000 computer with NE1 directly, and the OTNM2000 will
obtain the SN of the local NE (NE1). Configure the IP addresses and switches
using the OTNM2000 and download the mappings between SN numbers and
IP addresses to the local NE.
Version: B 69
u Configuring the IP address of adjacent NE (remote download mode)
1) After the IP address of local NE (NE1) is correctly configured, the

OTNM2000 will find the SN of the adjacent NEs (NE2 and NE3) via the SN
of NE1. After completing settings such as IP address and switch of the
adjacent NEs, you can deliver the corresponding relationship between
SNs and IP addresses to the adjacent NEs.
2) Find the adjacent NE4 and NE5 via the SN of NE3 and complete the
configuration of their IP addresses.
3) Repeat Step 2) to find all NEs step by step, and complete the configuration
of IP addresses for all NEs in the entire network.
Note:
u The adjacent NE can be discovered by the source NE only when it is

communicating with the MCC of the source NE normally.
u If the devices offered by FiberHome are interconnected with each

other via optical fibers and the connection is normal, the MCC
communication is normal. If the Overlay mode is used, configure a
MCC VLAN. See CiTRANS 650 Small Flexible Optical Transport
Platform Configuration Guide for the configuration method.
u If multiple adjacent NEs are found in one time, you need to check the
relevant project design document (namely, a spreadsheet that
describes mappings between NEs and SNs) to determine the
specific NE.
Method of Connecting the CiTRANS 610A to the OTNM2000
u Connecting the CiTRANS 610A to the OTNM2000 via the MAN offered by
FiberHome
70 Version: B
Figure 3-3 Connecting the CiTRANS 610A to the OTNM2000 via the MAN Offered by
FiberHome
As shown in Figure 3-3, if the MAN uses the FiberHome equipment, the
CiTRANS 610A interconnects with the NNI of the FiberHome MAN and
connects with the OTNM2000 via the in-band MCC. In this example, NE1 is the
local NE, NE2 is the adjacent NE of NE1, and NE4 is the adjacent NE of NE3.
u Connecting the CiTRANS 610A to the OTNM2000 via the MAN offered by
another vendor
Figure 3-4 Connecting the CiTRANS 610A to the OTNM2000 via the MAN Offered by Another
Vendor
As shown in Figure 3-4, if the MAN uses the equipment offered by another
vendor, the CiTRANS 610A interconnects with the UNI of the MAN offered by
another vendor and connects with the OTNM2000 via the Overlay mode. In this
example, NE1 is the local NE, NE2 is the adjacent NE of NE1, and NE3 is the
adjacent NE of NE2.
If the equipment connects to the OTNM2000 via the MAN offered by another
vendor, this vendor should create the VPWS channel that transparently
transmits the specified VLAN IDs and inform FiberHome. Then, FiberHome
uses the CiTRANS 650 to transmit the management packets with this VLAN ID
according to the management channel information offered by another vendor.
In this way, the CiTRANS 650 can manage the remote CiTRANS 610A by
passing through the MAN offered by another vendor.
Version: B 71
Each VPWS channel of the MAN offered by another vendor transparently

transmits one VLAN to the remote end, and each set of CiTRANS 610A
performs matching by learning this VLAN.
3.2.4.1 Configuring IP Address of Local NE
This section introduces the mapping between IP addresses and SNs of the local NE
using the NE1 shown in Figure 3-5 as an example.
Figure 3-5 Network Diagram for Configuring IP Address of Local NE
Prerequisite
u Users have learned about the project network planning, NE IP address and the
domain planning.
u You have completed the configuration of the project, network block and NE.
u You have completed the physical connection between the OTNM2000

computer and the local NE.
Planning Data
The parameters (such as IP addresses and switches) of the local NE (NE1) are
listed in the table below. Assign NE1 to the default domain. No extension domain
configuration is needed.
72 Version: B
Item Parameter
Switch1 2
Switch2 1
IP Address 10.171.2.1
IP Mask 255.255.255.0
Default Domain DEFAULT DOMAIN
Procedure
1. In the OTNM2000 window, click Configuration→NE Ip Remote Config in the

menu bar to bring up the NE Ip Remote Config window.
Note:
The NE entries shown in the NE Ip Remote Config window are the NE

data after the basic configuration is completed.
2. In the NE Ip Remote Config window, select the local NE (NE1) entry and
select Settings→Set as Local Ne in the main menu. After the setting is
completed, the ! column of the local NE (NE1) is shown as , and the
command log will be displayed in the log bar.
Note:
If multiple NEs are displayed in the NE Ip Remote Config window, only

one NE can be configured as the local NE.
Version: B 73
3. Click Config Local NE→Read Local Ne SN in the main menu. If the query is
successful, the EMU SN column of the local NE (NE1) will display the queried
SN and the log bar will display Query Successful.
Note:
u If the query fails, the EMU SN column displays no SN and the log bar
displays Command return timeout.
u If the network management server is connected to multiple local NEs

via the Hub, the queried SN will be random. You need to confirm the
equipment corresponding to the SN through the SN label on the
equipment panel.
4. Click the parameters to check and confirm that the parameters such as IP
address of the local NE (NE1) are consistent with the planning data.
74 Version: B
Note:
The parameters such as IP address displayed in the NE entry are the

data configured during creation of the network block and NE.
Table 3-8 Parameters of NE IP Remote Config
No - A default item that needs no editing.
This item displays the part number and NE number stored

Object -
in the database.
EMU SN - The SN of the equipment.
The IP address of the source NE.

For example, the IP address of NE1 is 11.18.1.1 and NE2
Source Ne IP -
is the adjacent NE of NE1, so that the Source Ne IP of
NE2 is 11.18.1.1.
Switch1/- 0x1 to 0xFF Switch1 and Switch2 consist of the IDs of NE. The
Switch2 combination of Switch1 and Switch2 should be unique in
the entire network.
Default DEFAULT u DEDAULT DOMAIN: The first two bytes of the IP
Domain DOMAIN and address are set to be the associated domain ID. All
NOT ports of the NE are associated to this domain.
DEFAULT Generally, all NEs of the access layer are assigned to
DOMAIN the default domain (local domain).
u NOT DEFAULT DOMAIN: You need to set the
extension domain and extension domain port in the
Extdomain Configuration dialog box.
IP Address - The IP address of the NE. It should be unique in the entire

network.
The local NE is connected to the EMS server using an
Ethernet cable. Therefore, the NE IP address must be on
the same subnet as the IP address of the network card on
the EMS server. Otherwise, SN discovery of adjacent NEs
will be affected.
IP Mask - Sets the IP mask address of an NE. 255.255.255.0 is
recommended.
IP Gateway - Sets the IP gateway. Generally no setting is required.
Extdomain Set this item if the Default Domain is set to NOT

-
Configuration DEFAULT DOMAIN.
Note 1: Items not listed in the table are usually set by default.
Version: B 75
5. Click Config Local NE→Write Local Ne IP in the main menu. If the log bar
shows Config Successful, the parameters such as IP address of the local NE
(NE1) are delivered to the equipment successfully.
3.2.4.2 Configuring IP Address of Adjacent NE
This section introduces the mapping between IP addresses and SNs of the remote
NE using NE2 to NE6 shown in Figure 3-6 as an example.
Figure 3-6 Network Diagram for Configuring IP Address of Adjacent NE
Prerequisite
u Users have learned about the project network planning, NE IP address and the
domain planning.
u You have completed the configuration of the project, network block and NE.
76 Version: B
u You have configured the IP address of the local NE.
u The communication of the MCC channel between the source NE and the
adjacent NE is normal.
Planning Data
The parameters (such as IP addresses and switches) of NE2 to NE6 are listed in
the table below. Assign NE2 to NE6 to the default domain. No extension domain
configuration is needed.
NE Switch1 Switch2 IP Address IP Mask

NE2 3 1 10.171.3.1 255.255.255.0
NE3 4 1 10.171.4.1 255.255.255.0
NE4 5 1 10.171.5.1 255.255.255.0
NE5 6 1 10.171.6.1 255.255.255.0
NE6 7 1 10.171.7.1 255.255.255.0
Procedure
1. Click the parameter column in the NE Ip Remote Config window to check and
confirm that the parameters such as IP addresses of NE2 to NE6 are consistent
with the planning data.
Note:
The NE entries and parameters such as IP addresses shown in the NE Ip

Remote Config window are the NE data after the basic configuration is
completed.
Version: B 77
2. Select the entry of NE1 (the source NE), click Query→Find Near Ne by SN in
the main menu. If the query successes, the Get Neighbor NE by SN dialog
box appears to display the adjacent NE and its SN found via NE1.
Note:
The NE number of the automatically discovered NEs increments

according to the sequence that the adjacent NEs are found.
3. Contact with engineers at the station to confirm the corresponding relationship

between the automatically discovered SN and the created NEs on the
OTNM2000. The automatically discovered SN 150128690027 corresponds to
NE2 and the SN 150128690021 corresponds to NE3.
Note:
The SN label of the CiTRANS 610A is attached to the front panel of the
equipment.
4. Copy the automatically discovered SNs and paste them into EMU SN of NE2
and NE3, and set the Source Ne IP of NE2 and NE3 to the IP address of the
source NE.
78 Version: B
5. Select NE2 whose IP address needs to be delivered and click Settings→Write

Remote Ne IP in the main menu. If the log bar shows Config Successful, the
parameters such as IP address of the remote NE2 are delivered to the
equipment successfully.
Caution:
u Write Remote Ne IP indicates delivering the corresponding

relationship between SNs and IP addresses.
u After the parameters such as the IP address are delivered to the

equipment successfully, the equipment will be rebooted.
6. Repeat Step 5 to complete the IP address configuration of NE3.
7. Repeat Steps 2 to 5, setting NE3 and NE5 as the source NEs. Configure the IP
addresses of NE2 to NE6 and close the NE Ip Remote Config window.
Version: B 79
3.3 Testing the NE Connectivity
Test whether the communication between the OTNM2000 and NE is normal.
Prerequisite
You have set the IP addresses of all NEs in the entire network.
Procedure
1. In the Logical Tree pane, right-click the NE and select OTNM Ping from the
shortcut menu to bring up the otnmping window.
2. Check whether the IP address of the NE can be pinged successfully. If the ping
fails, check whether the NE IP address is set correctly. If the fault persists,
contact FiberHome engineers for troubleshooting.
3. Close the otnmping window.
80 Version: B
3.4 Performing Time Calibration and

Downloading Configuration
After the IP addresses of NEs in the entire network are downloaded, you need to
perform time calibration (synchronizing the time of NEs with that of the OTNM2000)
in the OTNM2000 GUI and download the management configuration and equipment
configuration. In this way, the OTNM2000 can normally monitor and manage all NEs
and their cards.
Prerequisite
u All NEs in the entire network can be pinged successfully.
Procedure
1. Download management configuration.
1) In the Logical Tree pane, right-click the name of network block and select
Config→Download Management Config from the shortcut menu. Click
Yes in the alert box that appears.
2) Check whether the command has been successfully delivered in the

Command Manager GUI that appears.
2. Perform time calibration.
Version: B 81
Config→Time Calibration from the shortcut menu. Click Yes in the alert
box that appears.

Command Manager GUI that appears subsequently ( indicates that the
command is being delivered; indicates that command delivering has
failed; indicates that the command has been successfully delivered).
3. Download equipment configuration.
Config→Time Calibration from the shortcut menu. Click Yes in the alert
box that appears.
82 Version: B

command is being delivered; indicates that command delivering has
failed; indicates that the command has been successfully delivered).
Version: B 83
4 Equipment Configuration
This chapter introduces how to configure various services and typical scenarios on
the equipment, including related concepts and configuration procedures. Besides,
this chapter describes the configuration methods of detailed parameters via
configuration examples.
Configuring Interfaces
Configuring Tunnels and Tunnel Protection
Configuring PWs and PW Protection
Configuring Ethernet Services
Configuring CES Services
Saving and Delivering Services
Configuring Clock Synchronization
Configuring MTU
Configuring QoS
Configuring Typical Scenarios
84 Version: B
4.1 Configuring Interfaces
This section introduces the common interface types supported by the CiTRANS
610A, and the configuration methods of common interfaces.
4.1.1 Basic Concepts and Configuration Rules of Interfaces
The common interface types on the CiTRANS 610A include UNI interfaces, NNI
interfaces, LAG interfaces and E1 emulation interfaces.
Basic Concepts
u UNI interface
The UNI interface, also known as user side interface, is used for connecting a
network device with a user device.
u NNI interface
The NNI interface, also known as network side interface, is used for
interconnection between network devices (including network devices of the
same vendor or those of different vendors).
u LAG Interface
The LAG interface is special logical interface that bundles a group of physical
Ethernet interfaces to a logical aggregation group. All the member lines in the
port aggregation group share the bandwidth and provide protection to one
another.
u E1 emulation interface
The E1 emulation interface is used for configuring CES services.
Configuration Rule
u The naming rules for the interfaces of CiTRANS 610A are described as follows:
4 Ethernet interface: port rate + port number; for example, GE1 refers to the
GE interface whose port number is 1.
4 LAG interface: LAG + ID; for example, LAG1 refers to the aggregation port
whose ID is 1.
Version: B 85
4 E1 emulation interface: E1-CES shelf number/slot number/port number; for

example, E-CES0/1/1 refers to the E1 emulation interface with port number
1 in slot 1 of the first shelf under the rack.
Note:
The shelf number is a decimal number starting from 0. 0 indicates the 1st
shelf under the rack, 1 indicates the 2nd shelf under the rack, and so on.
u When an Ethernet interface is used for connecting a user device or a device

offered by another vendor to carry user side Ethernet services, set its interface
type to UNI.
u When an Ethernet interface is used for connecting network devices (including

network devices of the same vendor or those of different vendors), set its
interface type to NNI (for connecting network devices of the same vendor) or E-
NNI (for connecting network devices of different vendors).
u When the port aggregation protection is required, you can add and configure an
LAG interface in the Port-Aggregation-Config tab. Follow the configuration
rules described as below.
4 Each LAG interface contains up to four member interfaces. When the non-
load sharing mode is set for the LAG interface, each LAG interface
contains up to two member interfaces.
4 An LAG interface can be used as a UNI interface. In this case, you need to
set the interface type of its member interfaces to UNI. You can also
configure the MAC address attribute.
4 When the load sharing mode of an LAG interface is set to static load
sharing / static non-load sharing, you need to configure the equipment
priority. Generally, the priority of an LAG interface on the local equipment
should be different from that on the opposite end equipment. The smaller is
the value, the higher is the priority.
4 You need to enable the LACP protocol when the load sharing mode of an
LAG interface is set to static load sharing / static non-load sharing.
u If you need to configure an E1 emulation service, you can add and configure an
E1 emulation interface in the E1 emulation configuration tab.
86 Version: B
4.1.2 Configuring Interface Types
Network Diagram
As shown in the figure, NE1 and NE2 use the CiTRANS 610A as access equipment.
It is required that the types of the network-side and user-side interfaces of NE1 and
NE2 should be configured by using the NE global settings.
Prerequisite
u The network topology has been created as per the planning data.
u The OTNM2000 is in normal communication with the equipment.
Planning Data
The planning data of interface types are listed as follows, using NE1 and NE2 for
example.
NE Name Interface Name Interface Type
GE5 NNI
NE1
GE1 UNI
GE6 NNI
NE2
GE1 UNI
Procedure
The following introduces how to set interface types by using the NE global settings,
using NE1 as an example.
1. In the OTNM2000 window, click Business Configuration→Service Global

Settings→SDH/PTN NE Global Settings in the menu bar to bring up the SDH/
PTN NE Global Settings dialog box.
2. In the SDH/PTN NE Global Settings dialog box, set the interface types of GE1
and GE5 of NE1.
Version: B 87
UNI, NNI and E-

NNI Set the interface types. Options includes NNI, E-NNI
Interface type
The default and UNI.
value: UNI
3. Check whether the interface type has been updated, and then click OK.
88 Version: B
4.1.3 Configuring a LAG Interface
Network Diagram
As shown in the figure, NE1 and NE2 use the CiTRANS 610A as access equipment.
It is required that an LAG interface should be applied at the client side of NE1.
Prerequisite
You have configured the type of member interfaces under the LAG logical interface
of an NE.
Planning Data
The planning data of an LAG interface are listed below, using NE1 as an example.
Parameters of an LAG NE1

Interface
LACP-Protocol-Switch On
Local-Device-Priority 1
Note 1
ID 1
Aggregation-Mode Based-Source-Mac
Aggregation_Member-Port1 PORT1 (GE1)
Aggregation_Member-Port2 PORT2 (GE2)
Aggregation-Group-Work-
Static-Load-Sharing
Mode
Aggregation-Port1-Protocol-
ON
Switch
Aggregation-Port2-Protocol-
ON
Switch
Note 1: The format of the name of an LAG interface is LAG+ID. For example, LAG1 refers to
the aggregation port whose LAG ID is 1.
Version: B 89
Procedure
The following introduces how to configure a user-side LAG interface, using NE1 as
an example.
1. In the OTNM2000 window, double-click NE1 in the Logical Tree pane to bring
up the subrack view of NE1.
2. Click the XCTR2 card in the subrack view of NE1, and select Board
Configuration in the Task Panel pane.
90 Version: B
3. Click the Port-Aggregation-Config tab. Right-click a blank area in the tab and
select Add-Item. Set parameters such as LACP-Protocol-Switch, ID,
Aggregation-Mode and Aggregation_Member-Port of the user-side LAG
interface of NE1.
Version: B 91
Table 4-1 Parameters of the Port-Aggregation-Config Configuration Block
Sets whether to enable the LACP

protocol globally or not. The LACP
protocol is disabled for manual
aggregation but enabled for static
LACP-Protocol- Off and On
aggregation. When the Aggregation-
Switch The default value: Off
Group-Work-Mode is set to static
aggregation (static load / non-load
sharing), you need to enable the LACP
protocol globally.
Sets the priorities of an LAG on the local

equipment. This item is valid only when
the Aggregation-Group-Work-Mode is
set to static aggregation. When an LAG
on the local equipment negotiates with an
Local-Device- 1 to 65535
LAG on the peer equipment using the
Priority The default value: 1
LACP protocol, the local equipment and
peer equipment can obtain the LAG
priorities of each other. In this way, the
system will choose the calculation result
of the LAG with a higher priority.
ID 1 to 2 It is the number of an LAG.

Closed, Based-Source-Mac,
Based-Destination-Mac,
Sets the load balancing algorithm. It is
Based-Source-Destination-
Aggregation- valid only when Aggregation-Group-
Mac, Based-Source-IP,
Mode Work-Mode is set to static non-load
Based-Destination-IP and
sharing or manual non-load sharing.
Based-Source-Destination-IP
The default value: Closed
Sets the member ports of an LAG when
Aggregation_ the Aggregation-Group-Work-Mode is
-
Member-Port set to static load sharing or manual load
sharing.
Off, Manual-Load-Sharing,
Static-Load-Sharing, Manual-
Aggregation-
No-Load-Sharing and Static-
Group-Work- Sets the working mode of a LAG.
No-Load-Sharing
Mode
The default value: Manual-
Load-Sharing
92 Version: B
Table 4-1 Parameters of the Port-Aggregation-Config Configuration Block (Continued)
Sets whether to enable the LACP

protocol for the member ports of an LAG
or not. The LACP protocol is disabled for
manual aggregation but enabled for static
Aggregation-Port- Off and On aggregation. When the Aggregation-
Protocol-Switch The default value: Off Group-Work-Mode is set to static
aggregation, you need to enable the
LACP protocol globally and enable the
protocol for the member ports at the
same time.
Sets the return mode when the
Aggregation-Group-Work-Mode is set
No-Load-Sharing- Return and No-Return
to static non-load sharing or manual non-
return-Mode The default value: Return
load sharing. Generally, keep the default
settings.
Specifies the main member interface of

an LAG when the Aggregation-Group-
Work-Mode is set to static non-load
Primary-
Aggregation_ -
When the Aggregation-Group-Work-
Member_Port
Mode is set to static non-load sharing,
the main member interface is enabled
with LACP protocol by default.
Specifies the backup member interface of

an LAG when the Aggregation-Group-
Work-Mode is set to static non-load
Slave-
Aggregation_ -
When the Aggregation-Group-Work-
Member_Port
Mode is set to static non-load sharing,
the backup member interface is enabled
with LACP protocol by default.
Set this item when the Aggregation-

Wait-Recover- 0 to 12 minutes
Group-Work-Mode is set to static non-
Time The default value: 0
load sharing or manual non-load sharing.
4. Click Write to DB / Write to Device, and click OK in the alert box that appears.
Version: B 93
Note:
u Write to DB: Saves the configuration data to the database. When

the OTNM2000 is disconnected with the equipment, you can also
use the Write to DB function to avoid loss of configuration data.
u Write to Device: Delivers the configuration data to the equipment

and saves the data to the database.
5. Check whether the command has been successfully delivered in the

command is being delivered; indicates that command delivering has failed;
indicates that the command has been successfully delivered).
94 Version: B
4.2 Configuring Tunnels and Tunnel Protection
This section introduces the basic concepts of Tunnels, and the configuration
methods of Tunnels and LSP 1:1 protection.
4.2.1 Basic Concepts and Configuration Rules of Tunnels
You need to know about the basic concepts and application scenarios of Tunnels
and LSPs before configuring Tunnels and LSP 1:1 protection.
Basic Concepts
u Tunnel
A Tunnel is a virtual point-to-point connection created between NNI interfaces.

As the carrier of PWs in the network, it provides a service Tunnel to
transparently transmit point-to-point service packets. A Tunnel can carry
various services, such as CES services and Ethernet services. It is used as the
service transmission channel in the network, as shown in Figure 4-1.
Figure 4-1 The Tunnel
u LSP
Several Tunnels constitute an LSP. An LSP is a packet forwarding path created

using the MPLS protocol. This path is composed of multiple LSRs between the
source LSR and destination LSR and the links between these LSRs.
u LSP 1:1
Version: B 95
LSP 1:1 refers to the LSP 1:1 protection, which is a common Tunnel protection
type. In the LSP 1:1 protection mode, the protection path is used to protect the
services transmitted over the working path. The services are single-fed and
single-received. Under normal condition, services are transmitted over the
working path. When the working path is faulty, services are switched over to the
protection path, so as to ensure the normal transmission of services. Figure 4-2
shows the LSP 1:1 protection.
Figure 4-2 LSP 1:1 Protection
Configuration Rule
u You need to select the UNI interface for the source and sink ports when using
the CiTRANS 610A as source/sink node to create a Tunnel.
u When using the CiTRANS 610A as a source / sink node to create a Tunnel that
carries ELine services, make sure the source and sink ports of the Tunnel are
consistent with those of ELine services.
96 Version: B
u When using the CiTRANS 610A as a source / sink node to create a Tunnel that
carries CES services, select E1 for the source and sink ports of the Tunnel.
u When the source or the sink UNI interface is a LAG interface, select a member
of the UNI interface as the source of the sink port of the Tunnel.
u The PAN equipment supports static Tunnels.
u During configuration of a Tunnel, it is required that all nodes along the Tunnel
should support MPLS.
u If other nodes (cross-node Tunnels) exist between the source node and
destination node, you can specify the nodes and ports that the Tunnel passes
using routing constraints.
u When configuring a Tunnel, comply with the following rule to distribute labels for
each node: the value of outgoing label for the previous node is equal to the
value of incoming label for the next node.
u Two identical incoming labels are not allowed in the label forwarding table of
one node.
u The OTNM2000 supports manual configuration or automatic distribution of

labels.
u If the NNI interface that a Tunnel passes by is a VLAN sub-interface, the VLAN
ID of the local sub-interface should be the same with that of the connected
opposite end sub-interface.
Version: B 97
4.2.2 Configuring Tunnels
Network Diagram
As shown in the figure, NE1 to NE3 use the CiTRANS 610A as access equipment. It
is required that a Tunnel should be configured between NE1 and NE2.
Prerequisite
The interface type has been configured.
Planning Data
The planning data are described as follows, using the Tunnel between NE1 and
NE2 as an example.
Item Specification
Path Name T1-2

Signaling Static
Protection No Protection
Source LSR NE1
Source PortNote 1 GE1
Sink LSR NE2
Sink PortNote 1 GE1
Forward 1001
98 Version: B
Item Specification
Reverse 1002
Note 1: You need to select the UNI interface for the source and sink ports when using the
CiTRANS 610A as a source/sink node to create a Tunnel. When configuring a Tunnel
that carries CES services, select E1 for the source and the sink ports of the Tunnel.
Procedure
The following introduces how to configure a Tunnel, using the Tunnel between NE1
and NE2 as an example.
1. In the OTNM2000 window, click Business Configuration→PTN/IPRAN→

Tunnel in the menu bar to bring up the Static/Dynamic Tunnel Config dialog
box.
2. In the Static/Dynamic Tunnel Config dialog box, set parameters such as Path
Name and Signaling and enable or disable QoS of the Tunnel.
4 Configure basic properties of the Tunnel
Version: B 99
Table 4-2 Parameters of Basic Properties of a Tunnel
Sets the name of Tunnel according to the project

Path Name -
planning.
Static and Dynamic

Selects the signaling type of a Tunnel. The
Signaling The default value:
CiTRANS 610 supports the Static Tunnel.
Static
No Protection and
Sets the type of protection of a Tunnel. Select 1:1
1:1 Trail Protection
Protection Trail Protection if the Tunnel is configured with a
The default value:
LSP 1:1 protection.
No Protection
4 Enable or disable QoS
Table 4-3 Parameters of Enabling or Disable QoS
u Select Disable when QoS properties are not

required for a Tunnel.
u Select Enable QoS in work path to set QoS
properties of the active Tunnel. And then
Disable, Enable
Advanced QoS will appear in the
QoS in work path
configuration screens of the source and the
and Enable QoS in
Bandwidth sink LSRs of the active Tunnel.
all path
u Select Enable QoS in all path to set QoS
The default value:
properties of the active and the standby
Disable
Tunnels. And then Advanced QoS will
appear in the configuration screens of the
source and the sink LSRs of the active and
the standby Tunnels.
3. Click Next and set parameters such as source/sink nodes, ports and QoS
policy of the Tunnel.
100 Version: B
4 Configure related properties of the source and the sink nodes of the
Tunnel.
Table 4-4 Parameters of Source / Sink Node Properties of a Tunnel
Sets the source node of the working / protection

Tunnel in the following two ways.
u Click following Source LSR and select
from the drop-down menu.
u In the topology view, click the corresponding
Source LSR -
NE, and the NE will be automatically
displayed in the configuration item of Source
LSR or Sink LSR. The NE which is clicked
for the first time is the source node, and the
one clicked again is the sink node.
Source PortNote 1 - Sets the source port of a Tunnel.
Sets the sink port of a Tunnel basically in the

Sink LSR -
same way as that of configuring Source LSR.
Version: B 101
Table 4-4 Parameters of Source / Sink Node Properties of a Tunnel (Continued)
Sink PortNote 1 - Sets the sink port of the Tunnel.
It is the positive label, which can be set manually

according to project planning. When this item is
Forward 301 to 1048575
not configurable, the OTNM2000 will assign a
label automatically.
It is the reverse label. When the positive label

value is set manually, the reverse label value will
Reverse 301 to 1048575 be modified automatically to the value of positive
label plus one. When this item is not configurable,
the OTNM2000 will assign a label automatically.
Sets whether to enable OAM. When the Tunnel is

LSP 1:1 protected, select the check box.
Enable Proactive Select or clear the u This item is cleared by default when the
OAM check box protection type is set to No Protection.
u This item is selected by default when the
protection type is set to 1:1 Trail Protection.
CiTRANS 610A as source/sink node to create a Tunnel.
4 Configuring QoS Policy of Tunnel
Click following Advanced QoS, set QoS policy of the Tunnel and click
OK to complete the configuration. See Table 4-11 for specific descriptions
of parameters.
102 Version: B
Note:
The QoS related traffic bandwidth control and service priority are
deployed at the service layer (L2VPN flow layer and PW layer).
Deploying at the Tunnel layer is not recommended.
4. Click Next, and set parameters such as the routing policy and route constraints
of the Tunnel.
Version: B 103
Table 4-5 Parameter Description of Routing Policy
Min NE Quantity,
Minimal Length,
Lowest Cost and Sets Static Policy based on the project
Static Policy
Load Balance planning.
The default value: Min
NE Quantity
Not pass the same When the protection type is set to 1:1 Trail
NE, Not pass the Protection, configure the standby Tunnel path
Routing Policy same card and Not not to pass the NEs, cards or ports that the
Settings pass the same port active Tunnel path passes according to the
The default value: Not project planning. This item is valid only for the
pass the same port standby Tunnel.
Positive When you have selected the specified NE and

Routing set the Constraints to included or excluded,
NE -
Con- the Tunnel path will include or exclude this NE.
straints Set this item according to project planning.
104 Version: B
Table 4-5 Parameter Description of Routing Policy (Continued)
Pass Sets whether the Tunnel path passes the LAG

Yes and No
LAG port or not. Keep the default value No for the
The default value: No
Port CiTRANS 610A.
When you have selected the ingress port of the
specified NE and set the Constraints to
Ingress
- included or excluded, the Tunnel path will
Port
include or exclude the ingress port of the NE.
Set this item according to project planning.
You can set this item to included or excluded

Excluded and according to the corresponding settings in NE
Con- Included and Ingress Port. It indicates that the Tunnel
straints The default value: path includes or excludes the specified NE or
Included ingress port. Set this item according to project
planning.
5. Click Next and check the routing information of the Tunnel to be created. The
Tunnel path to be created will be highlighted in the topology view.
Version: B 105
6. Click Completed to complete the creation of Tunnel and bring up the Business
Management dialog box, in which you can view or activate the created Tunnel.
4.2.3 Configuring an LSP 1:1 Protection
Network Diagram
is required that a Tunnel should be created between NE1 and NE2 and the LSP 1:1
protection be applied.
Prerequisite
The interface type has been configured.
106 Version: B
Planning Data
The planning data are described as follows, using the creation of a Tunnel between
NE1 and NE2 with LSP 1:1 protection applied as an example.
Item Specification
Path Name T1-2

Signaling Static
Protection 1:1 Trail Protection
Source LSR NE1
Source PortNote 1 GE1
Sink LSR NE2
Sink PortNote 1 GE1
Forward 1001
Working Path
Reverse 1002
Forward 1003
Protection Path
Reverse 1004
CiTRANS 610A as source/sink node to create a Tunnel.
Procedure
The following introduces how to configure the LSP 1:1 protection, using the creation
of a Tunnel between NE1 and NE2 with LSP 1:1 protection applied as an example.

Tunnel in the menu bar to bring up the Static/Dynamic Tunnel Config dialog
box.
2. In the Static/Dynamic Tunnel Config dialog box, set parameters such as Path
Name and Protection and enable or disable QoS of the Tunnel.
Version: B 107
4 Configure basic properties of the Tunnel. See Table 4-2 for specific
descriptions of parameters.
4 Enable or disable QoS. See Table 4-3 for specific descriptions of

parameters.
3. Click Next and set parameters such as source/sink nodes, ports and QoS
policy of the active Tunnel.
108 Version: B
4 Configure related properties of the source and the sink nodes of the active
Tunnel. See Table 4-4 for specific descriptions of parameters.
4 Configure QoS policy of the active tunnel
Click following Advanced QoS, set QoS policy of the active Tunnel and
click OK to complete the configuration. See Table 4-11 for specific
Version: B 109
Note:
4. Click Next and set the routing policy and route constraints of the active Tunnel.
See Table 4-5 for the parameter descriptions.
110 Version: B
5. Click Next and check the routing information of the active Tunnel to be created.
The trail of the active Tunnel to be created will be highlighted in the topology
view.
Version: B 111
6. Click Next, and the OTNM2000 will automatically set parameters of the
standby Tunnel such as source and sink nodes according to the configured
parameters of the active Tunnel. You can modify the parameters according to
the project planning. Generally, no configuration is required.
112 Version: B
4 Configure the source and the sink nodes and ports of the standby Tunnel.
See Table 4-4 for the parameter description.
4 Configure QoS policy of the standby Tunnel
Click following Advanced QoS, set QoS policy of the standby Tunnel
and click OK to complete the configuration. See Table 4-11 for specific
Version: B 113
Note:
7. Click Next to set the routing policy and route constraints of the standby Tunnel.
See Table 4-5 for the parameter description.
114 Version: B
8. Click Next and click OK in the alert box that appears.
9. Check the routing information of the standby Tunnel. The paths of the active
and standby Tunnels created will be highlighted in the topology view. Set the
return properties.
Version: B 115
Return, Non
Revertive Selects whether to switch the service back to the
Return Type
The default value: active Tunnel after the fault is eliminated.
Return
The WTR time refers to the period from the time
when the original active path is restored to the
1 to 12 minutes
WRT time when the services are switched from the
The default value: 5
standby path to the original active path. Set this
item according to the project planning.
The hold-off time refers to the period from the

0 to 255. The unit is
time when the equipment detects a fault to the
Hold-off Time 10ms.
time when the switching operation is performed.
Set this item according to the project planning.
10. Click Next to set the OAM property. When the OAM is used as a protection
switching detection policy in LSP 1:1 protection, CV frames should be enabled
for the working (active) path, and APS and CV frames should be enabled for
the protection (standby) path. You can keep the default settings.
116 Version: B
Sets the ID of a local end MEP. The MEP ID

Source MEP ID -
should be unique in a MEG group.
Sets the six least significant bits of a MEG ID.

MEG ICC - MEG ICC configurations should be consistent for
the source and sink NEs.
Sets the six most significant bits of a MEG ID.
MEG UMC configurations should be consistent for
MEG UMC - the source and sink NEs. The combination of MEG
ICC and MEG UMC identifies different MEG
groups.
0 to 7 Sets the EXP level, from 0 to 7 in the ascending

MEG Level
The default value: 7 order.
Enables or disables the APS protocol. This item is
disabled for the source and sink nodes of the
APS Enable Disable and Enable
active path by default, and enabled for the source
and sink nodes of the standby path.
Version: B 117
Enables or disables the CV frame. This item is

CV Frame
Disable and Enable enabled for the source and sink nodes of both the
Enabling
active path and the standby path by default.
3.33ms, 10ms,
CV Frame
100ms, 1s Sets the transmission cycle of the CV frame
Transmission
The default value is 3. detection of message.
Period
33ms
11. Click Completed to complete the creation of the Tunnel and protection and
bring up the Business Management dialog box, in which you can view or
activate the created Tunnel.
4.3 Configuring PWs and PW Protection
This section introduces the basic concepts of PWs, and the configuration methods
of PWs and PW protection.
4.3.1 Basic Concepts and Configuration Rules of PWs
You need to know about the basic concepts and application scenarios of PWs
before configuring PWs and PW protection.
Basic Concepts
u PW
118 Version: B
The PW is a transparent transmission tunnel between PEs as defined in the

PWE3 technology. The PWE3 technology is a point-to-point L2VPN technology,
which provides an MPLS solution that transparently transmits various user
services over the packet switched network (PSN). PWE3 emulates various
user services such as TDM signals and Ethernet packets, and transmits these
services in end-to-end mode over a PW on the PSN.
In an MPLS network, double labels are required for the PW. The outer label
(Tunnel label) is used for forwarding of LSP in an MPLS network. The inner
label (PW label) is used for binding the PW. One MPLS Tunnel can carry
multiple PWs.
Figure 4-3 shows the basic framework of PWE3.
Figure 4-3 Basic Framework of PWE3
The concepts related to basic framework of PWE3 are described as follows:
4 PE: It is an edge device in a provider network.
4 CE: It is a customer edge device.
4 P: It is a device on the backbone network of a service provider.
4 AC: it refers to attachment circuit. It is an independent link or circuit that

connects a CE to a PE. The attributes of an AC include the encapsulation
type, MTU, and interface parameters of a specific link type.
4 Tunnel: It refers to the tunnel.
4 PW: Pseudo-Wire. It is a virtual connection.
u PW 1:1 Protection
Version: B 119
In the PW 11 protection mode, when the working PW is faulty, the service will
be switched to the protection PW which has been created beforehand, so as to
protect the service. A PW 1:1 protection is applicable when the working PW
and the protection PW have the same source node and the same sink node, as
shown in Figure 4-4.
Figure 4-4 PW 1:1 Protection
Configuration Rule
u The PAN equipment supports static PWs.
u The configuration method of PW 1:1 protection is to configure a standby PW on

the basis of the active PW.
u If the PW 1:1 protection is applied, you do not need to set the protection type
when configuring the L2VPN service. Select the active PW as the PW
associated with service.
u You must complete the configuration of Tunnel used by PW before configuring

the PW.
u You can create multiple PWs in a batch manner when configuring the PW.
u When configuring a PW, comply with the following rule to distribute PW labels
for each PE: the value of outgoing label for the previous node is equal to the
value of incoming label for the next node.
120 Version: B
u Two identical incoming labels are not allowed in the label forwarding table of
one node.
u The OTNM2000 supports manual configuration or automatic distribution of

labels.
u Generally, the static PWs created in a batch manner select to use the same
Tunnel.
u The PW cannot be delivered to the equipment independently, but can be

delivered together with L2VPN service.
4.3.2 Configuring PWs
Network Diagram
is required that a PW should be configured between NE1 and NE2.
Prerequisite
The Tunnel between NE1 and NE2 has been configured.
Planning Data
The planning data are described as follows, using the PW between NE1 and NE2
as an example.
Version: B 121
Item Specification
PW Name V1-2
Signaling Static
Source NE1
Sink NE2
Positive 3001
Reverse 3001
Procedure
The following introduces how to configure a PW, using the PW between NE1 and
NE2 as an example.
1. In the OTNM2000 window, click Business Configuration→PTN/IPRAN→PW

in the menu bar to bring up the Static/Dynamic PW Config dialog box.
2. In the Static/Dynamic PW Config dialog box, set parameters such as name,

source node and sink node of the PW.
You can set the source and sink nodes of PW using the following two methods:
4 Click on the right of Source or Sink and select from the drop-down
menu.
4 In the topology view, click the corresponding NE, and the NE will be
automatically displayed in the configuration item of Source or Sink. The
NE which is clicked for the first time is the source node, and the one
clicked again is the sink node.
122 Version: B
PW Name - Sets the name of PW according to the project planning.
Static and
Dynamic Sets the signaling type of the PW. The CiTRANS 610
Signaling
The default supports the Static PW.
value: Static
Source - Sets the source node of PW.
Sink - Sets the sink node of PW.
Sets the positive label of PW, which can be set
Positive 301 to 1048575 manually. If this item is not configured, the OTNM2000
will assign a label automatically.
Version: B 123
Sets the reverse label. When the positive label value is

set manually, the reverse label value will be modified
automatically. By default, the value of positive label is
Reverse 301 to 1048575
the same with that of the reverse label. When this item
is not configurable, the OTNM2000 will assign a label
automatically.
Select or clear
the check box. Enables or disables OAM. When configuring the active
Enable Proactive
The check box and the standby PWs in a PW APS protection, select
OAM (optional)
is cleared by the check box preceding Enable Proactive OAM.
default.
3. Click Next, and select the Tunnel circuit that carries the PW. You can set the
number of PWs to be created and QoS policy of the PWs in a batch manner
according to the project requirements.
4 Set the quantity of PWs to be created in a batch manner
124 Version: B
1 to 256 Sets the number of PWs to be created in a batch

Lot Size The default manner. The CiTRANS 610A supports creating up to
value: 1 256 PWs in a batch manner.
Set Advanced Sets the QoS property of PW, including the traffic
-
(optional) bandwidth policy and mapping policy.
4 Configure QoS policy of the PWs
Click following Set Advanced, set QoS policy of the PWs and click
Previous to complete the configuration. See Table 4-12 for specific
4. (Optional) If you have selected the check box preceding Enable Proactive
OAM in Step 2, click Next to set OAM properties. When a PW 1:1 protection
uses OAM as a detection policy of protection switching , enable CV frames for
the active path and enable APS and CV frames for the standby path.
Version: B 125
Sets the ID of a local end MEP. The MEP ID

Source MEP ID -
should be unique in a MEG group.
Sets the six least significant bits of a MEG ID.

MEG ICC - MEG ICC configurations should be consistent for
the source and sink NEs.
Sets the six most significant bits of a MEG ID.
MEG UMC configurations should be consistent
MEG UMC - for the source and sink NEs. The combination of
MEG ICC and MEG UMC identifies different
MEG groups.
0 to 7 Sets the EXP level, from 0 to 7 in the ascending

MEG Level
The default value: 7 order.
Enables or disables the APS protocol. This item
is disabled for the source and sink nodes of the
APS Enable Disable and Enable
active path by default, and enabled for the
source and sink nodes of the standby path.
126 Version: B
Enables or disables the CV frame. This item is

CV Frame Enabling Disable and Enable enabled for the source and sink nodes of both
the active path and the standby path by default.
3.33ms, 10ms,
CV Frame 100ms, 1s Sets the transmission cycle of the CV frame
Transmission Period The default value is detection of message.
3.33ms
5. Click Completed complete the creation of PW and bring up the Business

Management dialog box, in which you can view or activate the created PW.
4.3.3 Configuring a PW 1:1 Protection
Network Diagram
Version: B 127
is required that a PW 1:1 protection should be configured between NE1 and NE2.
Prerequisite
The Tunnels which carry the active and standby PWs have been configured.
Planning Data
The planning data are described as follows, using the PW 1:1 protection configured
for the active PW between NE1 and NE2 as an example.
PW Configuration Item NE1↔NE2 (Active)Note 1 NE1↔NE2 (Standby)Note 2
PW Name V1-2-M V1-2-B

Signaling Static Static
Source NE1 NE1
Sink NE2 NE2

Positive 3001 3002
Reverse 3001 3002
Select the Service Layer T1-2 T1-3-2
Enable Proactive OAM Select Select
Note 1
APS Enable Disable Enable
CV Frame Enabling Enable Enable
Note 1: The CV frame should be enabled for the active PW.
Note 2: The APS and CV frames should be enabled for the standby PW.
Configuration Item of PW 1:1 Protection Parameter
Protection Type PW 1:1 (APS Enable)
Standby PW Path Config V1-2-B

Return Type Return
WRT 5
Hold-off 0
Procedure
The following introduces how to configure the PW 1:1 protection, using the PW 1:1
protection configured for the active PW between NE1 and NE2 as an example.
128 Version: B
Note:
You do not need to set the protection type when configuring the L2VPN
service. Select the active PW as the PW associated with service.
1. Configure the active PW and standby PW between NE1 and NE2 respectively
according to the planning data. See Configuring PWs for the configuration
methods.
2. In the OTNM2000 window, click Business Management→PW in the menu bar

to bring up the PW dialog box.
3. In the PW dialog box, click Filter and all the configured PWs will be displayed
by default. You can also set the filter conditions to query the configured PW as
required.
Version: B 129
4. In the PW tab, select the active PW (V1-2-M) between NE1 and NE2. Right-
click the PW and select PW Protection→Add a PW Protection to bring up the
PW Protection Config dialog box.
5. Set the PW protection parameters in the PW Protection Config dialog box.
130 Version: B
PW 1:1 (APS Enable) and

Sets the protection type. Select PW 1:1 (APS
Protection Type PW Redundancy (APS
Enable) for a PW 1:1 protection.
Protocol)
Standby PW Selects the standby PW according to the

-
Path Config project planning.
Sets whether to switch the service back to

Return, Non Revertive
Return Type the original active PW after the fault is
The default value: Return
eliminated.
The WTR time refers to the period from the
time when the original working path is
1 to 12 minutes restored to the time when the services are
WRT
The default value: 5 switched from the protection path to the
original working path. Set this item according
to the project planning.
The hold-off time refers to the period from the

time when the equipment detects a fault to
0 to 255. The unit is 10ms.
Hold-off the time when the switching operation is
performed. Set this item according to the
project planning.
6. Click OK to bring up the The PW protection was added successfully! alert

box.
7. Check the information of PW entry, and the Protection Type changes into
Protection Pair.
Version: B 131
4.4 Configuring Ethernet Services
This section introduces the Ethernet related concepts and configuration methods of
Ethernet services (E-Line, E-LAN and E-Tree).
4.4.1 Basic Concepts and Configuration Rules of Ethernet

Services
You need to know about the basic concepts and application scenarios of E-Line, E-
LAN and E-Tree services before configuring the Ethernet services.
Basic Concepts
u E-Line
The E-Line service is a point-to-point service. It belongs to MPLS L2VPN in

VPWS mode.
Figure 4-5 shows the network mode of the E-Line service. To implement the
communication between Site 1 and Site 2, you can configure the user-to-
network E-line service carried by PW. In this case, the service accessed to the
user side is encapsulated into PW, and then carried by Tunnel.
Figure 4-5 Network Diagram of E-Line Service
u E-LAN
132 Version: B
The E-LAN service is a multipoint-to-multipoint service. It belongs to MPLS

L2VPN in VPLS mode. After an E-LAN service is created on the equipment, the
equipment creates a VSI for the service and binds all the points that need to
communicate with each other to the VSI. These points are called VSI leaf
nodes. A VSI leaf node can be an Ethernet port (UNI) or a PW.
E-LAN services can be classified into user-to-user E-LAN services and user-to-
network E-LAN services.
4 The VSI leaf nodes of a user-to-user E-LAN service are UNI interfaces.
Figure 4-6 shows the network mode. A user-to-user E-LAN service is
created on PE to implement mutual communication of Site 1, Site 2 and
Site 3. The VSI on PE1 functions as a layer 2 switch to forward service
packets.
Figure 4-6 Network Diagram of User-to-User E-LAN Service
4 Figure 4-7 shows the network mode of user-to-network E-LAN service.

The user-to-network E-LAN service is created on PE1, PE2 and PE3
respectively to implement mutual communication among Site 1, Site 2 and
Site 3. The VSIs on PE1, PE2, and PE3 and the network-side channels
function as a layer 2 switch to forward service packets.
Version: B 133
Figure 4-7 Network Diagram of User-to-Network E-LAN Service
u E-Tree
The E-Tree service is a point-to-multipoint service. It belongs to MPLS L2VPN

in VPLS mode. The difference between E-Tree and E-LAN is listed as follows:
4 Different nodes in the E-LAN service network can communicate with each
other.
4 The E-Tree service network includes one root node and multiple leaf
nodes. The root node can communicate with several leaf nodes, whereas
a leaf node cannot communicate with another leaf node.
shows the network mode of E-Tree service. The E-Tree service is created on
PE1, PE2 and PE3 respectively to implement communication between Site 1
and Site 2 and between Site 1 and Site 3. Site 2 cannot communicate with Site
3.
134 Version: B
Figure 4-8 Network Diagram of E-Tree Service
Configuration Rule
u E-Line
4 You must complete configuration of the Tunnel and PW used by the E-Line
before configuring the E-Line service.
4 Each E-Line service exclusively occupies a PW.
4 Each E-Line service should be configured with a pair of UNI interfaces.
4 When the UNI interface is a LAG port, select the corresponding LAG port
as the source or sink port of the E-Line service.
u E-LAN
4 In the user-to-network mode, a Tunnel and a PW should be configured

between two NEs.
4 In the user-to-user mode, only one NE is required, and the NE should be

configured with at least two interfaces.
4 By default, the split horizon function is disabled on UNI interfaces of each

NE and this function is enabled for the NNI interfaces.
u E-Tree
4 You must complete configuration of the Tunnel and PW used by the E-Tree
before configuring the E-Tree service.
Version: B 135
4 You need to configure one root node and at least two leaf nodes when
configuring the E-Tree service.
4.4.2 Basic Concepts and Configuration Rules of VLAN
This section introduces the basic concepts and configuration rules of VLAN.
Basic Concepts
u VLAN
The VLAN refers to the VLAN ID carried in a TAG added to an Ethernet frame.
VLAN indicates dividing a physical network into logical subnets according to
specific rules. Broadcast packets in each VLAN can only be transmitted within
the VLAN, which means a VLAN corresponds a broadcast domain.
u QinQ
QinQ is a layer 2 VPN solution. With the VLAN nesting technology, data
packets carry two different VLAN tags to identify different data packets. This
eliminates the limitation of the original solution in which only one VLAN tag is
used to identify different data packets. In this way, VLAN IDs are extended. The
inner VLAN tag is referred to as C-VLAN, indicating the customer VLAN. The
outer VLAN tag is referred to as S-VLAN, indicating the carrier VLAN.
u VLAN RANGE
VLAN RANGE refers to the VLAN within a specific range. When the VLAN of
the user packets received by UNI is within a specific range, you need to
perform settings on the equipment to allow the VLAN within a specific range to
enter the corresponding layer 2 service.
Configuration Rule
u UNI ingress traffic classification
UNI ingress traffic classification (based on VLAN) indicates classifying user

packets according to the VLAN carried by the packets. Only the user packets
with matched VLAN can enter the corresponding layer 2 service for forwarding.
136 Version: B
UNI Ingress
Traffic Effect
Classification
All user packets can enter the corresponding layer 2 service no matter
Based on port
whether the packets carry VLAN or not.
A user packet must carry a VLAN. Only the packet with its outer VLAN
Based on VLAN matching the configured VLAN can enter the corresponding layer 2
service.
A user packet must carry a VLAN. Only the packet with its outer VLAN
Based on VLAN
being contained in the configured VLAN range can enter the
RANGE
corresponding layer 2 service.
A user packets must carry double VLANs. Only the packet with its outer
Based on QINQ VLAN and inner VLAN matching the configured VLANs respectively can
enter the corresponding layer 2 service.
u VLAN operation
VLAN operation indicates processing the VLAN carried by a user packet,

including transparently transmitting or modifying the VLAN of the user packet.
VLAN operation includes ingress VLAN identification and egress VLAN action.
4 Ingress VLAN identification: Includes Identify and Not Identify, indicating

identifying or not identifying the VLAN carried in the packet received at the
ingress respectively.
4 Egress VLAN action: Includes NOP (no action), Add and Delete, indicating
performing no action on VLAN of the packet, adding an outer VLAN to the
packet and deleting the outer VLAN of the packet when the packet is
transmitted via the egress, respectively.
Ingress VLAN Egress VLAN
Effect
Identification Action
Delete Delete the outer VLAN of the user packet
If the user packet carries an outer VLAN, the VLAN will

Identify
Add not be modified; if the user packet carries no outer
VLAN, a VLAN will be added
NOP Perform no operation on VLAN
Add a customer VLAN no matter whether the user

Not Identify Add
packet carries a VLAN or not
Delete Invalid action
Version: B 137
The ingress VLAN identification and egress VLAN action need to be configured
on the same station. For one direction of a service, the ingress VLAN
identification of a UNI is used together with the egress VLAN action of a NNI.
For another direction of a service, the ingress VLAN identification of a NNI is
used together with the egress VLAN action of a UNI. See the figure below.
Figure 4-9 VLAN Operation
Configuration Method
u For the configuration methods of UNI ingress traffic classification and VLAN
operation of the E-Line service, see Step 5 of the configuration procedures in
Configuring E-Line Services.
operation of the user-to-user E-LAN service, see Step 4 of the configuration
procedures in Configuring User-to-User E-LAN Services.
operation of the user-to-network E-LAN service, see Step 7 of the configuration
procedures in Configuring User-to-Network E-LAN Services.
operation of the E-Tree service, see Step 6 of the configuration procedures in
Configuring E-Tree Services.
138 Version: B
4.4.3 Basic Concepts and Configuration Rules of Multicast
You need to know about the basic concepts and application scenarios of static
multicast and IGMP before configuring the multicast function.
Basic Concepts
u IGMP
In the TCP/IP protocol suite, the Internet Group Management Protocol (IGMP)
manages the IP multicast group members. It establishes and maintains the
member relationship between IP hosts and multicast routers that are directly
connected to the IP hosts.
At present, IGMP has three versions:
4 IGMPv1 (defined in RFC 1112)
All IGMP versions support the ASM model. IGMPv3 can be directly applied to
the SSM model; IGMPv1 and IGMPv2 can be applied to the SSM model with
the technical support of IGMP SSM Mapping.
u IGMP Snooping
Internet Group Management Protocol Snooping (IGMP Snooping) is a multicast

constraint mechanism running on layer 2 devices. It is used for managing and
controlling multicast groups.
By listening to and analyzing IGMP packets, a layer 2 device running IGMP

Snooping establishes mappings between ports and multicast MAC addresses
and forwards multicast data based on these mappings.
As shown in the figure below, when IGMP Snooping is not running on the layer
2 device, multicast packets are broadcast to all devices at layer 2. When IGMP
Snooping is running on the layer 2 device, multicast packets for known
multicast groups are multicast to the receivers, rather than broadcast to all
hosts, at layer 2.
Version: B 139
Figure 4-10 Comparison Before and After the IGMP Snooping Is Running on the Layer 2
Equipment
u Layer 2 multicast
In a layer 2 network (VPLS), IGMP Snooping can be used to monitor IGMP

protocol packets, learn multicast group ports, and create layer 2 multicast
forwarding tables which indicate the mappings among interfaces, broadcast
domains (VSI), and multicast groups, thus guiding the forwarding of multicast
data.
u Layer 2 static multicast
Layer 2 static multicast indicates that the multicast forwarding table entries are
configured manually so that the interfaces are mapped to multicast group
addresses for guiding the forwarding of multicast data.
Configuration Rule
u The multicast function is applied to the VPLS network (E-LAN and E-Tree).
u Configure VPLS L2VPN (E-LAN and E-Tree) service before configuring the
multicast function.
u You need to set the multicast function in the Board Configuration of the
specified NE according to the project requirements.
140 Version: B
4.4.4 Configuring E-Line Services
Network Diagram
is required that an E-Line service should be created between NE1 and NE2 and the
LSP 1:1 protection be applied.
Prerequisite
u The LSP 1:1 protection has been configured between NE1 and NE2.
u The PW between NE1 and NE2 has been configured.
Note:
When configuring a Tunnel that carries ELine services, make sure the
source and sink ports of the Tunnel are consistent with those of ELine
services.
Planning Data
The planning data are described as follows, using the E-Line service between NE1
Version: B 141
Item Specification
Service Name ELine1-2

Service Type E-Line
Direction User to Network
Source NE NE1
Source Port GE1
Sink NE NE2
Sink Port GE1

PW Info V1-2
Procedure
The following introduces how to configure the E-Line service, using the E-Line
service between NE1 and NE2 as an example.

L2VPN service in the menu bar to bring up the Layer-2 VPN Config dialog
box.
2. In the Layer-2 VPN Config dialog box, set the parameters such as service
name and service type.
142 Version: B
Table 4-6 Parameter Description of the Basic L2VPN Configuration
Service Name - Sets the name of L2VPN service.

E-LINE, E-LAN, E-TREE,
Service Type Sets the type of L2VPN service.
E-CES
Sets the service direction. This item can be
set if the service type is E-LINE or E-LAN.
u Set the service direction of the E-LINE-
User to Network and
type L2VPN to User to Network.
User to User
Direction u Set the service direction of the user-to-
The default value: User
user E-LAN-type L2VPN to User to User.
to Network
u Set the service direction of the user-to-
network E-LAN-type L2VPN to User to
Network.
No Protection and PW
Redundancy Protect+MC Sets the APS protection type. Set this item to
APS LAG PW Redundancy Protect+MC LAG for the
The default value: No PW redundancy protection.
Protection
Version: B 143
3. Click Next and set the parameters such as source and sink nodes, ports and
constraints of the E-Line service.
You can set the source and sink nodes of E-Line service using the following two
methods:
4 Click on the right of Source NE or Sink NE and select from the drop-
down menu.
automatically displayed in the configuration item of Source NE or Sink NE.
The NE which is clicked for the first time is the source node, and the one
Source NE - Sets the source node of the E-Line service.
Source Port - Sets the source port of the E-Line service.
Sink NE - Sets the sink node of the E-Line service.
Sink Port - Sets the sink port of the E-Line service.
144 Version: B
When you have selected the specified NE

and set the Constraints to included or
NE - excluded, the E-Line service path will
include or exclude this NE. Set this item
according to project planning.
When you have selected the port of the

specified NE and set the Constraints to
included or excluded, the E-Line service
Port -
Constraints path will include or exclude the ingress port
of the NE. Set this item according to project
planning.
You can set this item to included or

Excluded and excluded according to the corresponding
Included settings in NE and Port. It indicates that the
Constraints
The default value: E-Line service path includes or excludes the
Included specified NE or port. Set this item according
to project planning.
4. Click Next and select the PW circuit that carries the E-Line service.
Version: B 145
Selects the PW circuit that carries the E-Line

PW Info - service. Each E-Line service exclusively occupies a
PW.
5. Click Next and set the traffic classification, interface VLAN operation and QoS
policies of the source or sink node according to the project requirements.
4 If you need to set the traffic classification, ➔ Step 6.
4 If you need to set the interface VLAN operation, ➔ Step 7.
4 If you need to set the QoS policy, ➔ Step 8.
4 If you do not need to set the traffic classification, interface VLAN operation
and QoS policy, ➔ Step 9.
146 Version: B
6. (Optional) Select the source or sink node, and set the flow VLAN and flow type
of UNI interface of the source or sink node in the Flow Settings and Flow
Classification respectively.
The flow classification (flow VLAN and flow type) is used to classify user
packets. Only the matched user packets can enter the corresponding layer 2
service.
4 When the accessed packets are based on port, keep the default value of
Flow Settings. No configuration is required for Flow Classification.
4 When the accessed user packets are based on VLAN, you need to set
VLAN ID in the Flow Settings, and select VLAN in the Flow
Classification.
4 When the accessed user packets are based on QinQ, you need to set
VLAN ID (outer VLAN) and Inner vlan (inner VLAN) in the Flow Settings,
and select QinQ in the Flow Classification.
4 When the accessed user packets are based on VLAN Range, you need to
set Outside vlan start and Outside vlan end in the Flow Settings, and
select VLAN Range in the Flow Classification.
Version: B 147
7. (Optional) Select the source or sink node, and set the VLAN operations on UNI/
NNI interface of the node in the UNI Interface Settings and NNI Interface
Settings tabs respectively.
Table 4-7 Parameter Description of the UNI and NNI Interfaces
Not Identify and Sets whether the UNI identifies the

The Add Traffic
Identified VLAN TAG in the add packet. This
TAG
The default value: item is generally used together with
Identification
Not Identify the add traffic TAG action of the NNI.
UNI NOP, Add and Sets the operation on the VLAN TAG
Interface The Drop TAG Delete in the dropping packet of UNI. This
Settings Action The default setting function is generally used together
is NOP (no cation). with the drop TAG identification of NNI.
Incremental Sets the VLAN ID added at the drop

VLAN-ID at the - when the drop TAG action of UNI is
Drop set to Add.
Not Identify and Sets whether the NNI identifies the
Identify the Drop Identified VLAN TAG in the drop packet. This
TAG The default value: item is generally used together with
Not Identify the drop TAG action of the UNI.
NNI NOP, Add and Sets the operation on the VLAN TAG
Interface The Add Traffic Delete in the add packet of NNI. This function
Settings TAG Action The default setting is generally used together with the add
is NOP (no cation). traffic TAG identification of UNI.
Incremental Sets the VLAN ID added at the add
VLAN-ID at the - when the add traffic TAG action of NNI
Add is set to Add.
148 Version: B
Note:
For the add packet (in uplink direction), the add traffic TAG identification
of UNI is used together with the add traffic TAG action of NNI. For the
drop packet (in downlink direction), the drop TAG identification of NNI is
used together with the drop TAG action of UNI.
8. (Optional) In the Flow Settings tab, set the QoS policy of UNI interface of the
source or sink node of E-Line service. You can also set the QoS policy after
completing the configuration of E-Line service. For the configuration method
and parameters, see Table 4-13.
Version: B 149
9. Click Completed to bring up the Business Management dialog box, in which

you can view or activate the created E-Line service.
4.4.5 Configuring User-to-User E-LAN Services
Network Diagram
As shown in the figure, NE1 uses the CiTRANS 610A as access equipment. It is
required that the user-to-user E-LAN service should be created for NE1 to
implement mutual communication between UNI interfaces (GE1 and GE5) of NE1.
Prerequisite
The interface type of NE1 has been configured.
Planning Data
The user-to-user E-LAN service for NE1 is used as an example. The planning data
are listed as follows:
Item Specification
Service Name ELAN-1

Service Type E-LAN
Direction User to User
Source NE NE1
Source Port GE1, GE5
150 Version: B
Procedure
The following introduces how to configure the user-to-user E-LAN service, using the
user-to-user E-LAN service for NE1 as an example.

box.
2. In the Layer-2 VPN Config dialog box, set the parameters such as Service
Name and Service Type. See Table 4-6 for specific descriptions of them.
3. Click Next and set the source nodes and ports of the E-LAN service.
You can set the source nodes using the following two methods:
4 Click on the right of Source NE and select from the drop-down menu.
automatically displayed in the configuration item of Source NE.
Version: B 151
Source NE - Sets the source node of the E-LAN service.
Sets the port of the E-LAN service. You need to select

Source Port -
at least two UNI ports.
policies of the node NE1 included in the E-LAN service according to the project
requirements.
152 Version: B
5. (Optional) Select the source node NE1, and set the flow VLAN and flow type of
the specified UNI interface (GE1 or GE5) in the Flow Settings and Flow
service.
Classification.
Version: B 153
6. (Optional) Select the specified port (GE1 or GE5) of source node NE1. Set the
UNI interface VLAN operation in the UNI Interface Settings tab. See Table 4-7
for specific descriptions.
154 Version: B
Note:
All the ports of the user-to-user E-LAN service are UNI ports. For the
uplink or downlink direction of data, the add traffic TAG identification of
one UNI port is used together with the drop TAG action of another UNI
port. NE1 is taken as an example for introduction.
u In the data uplink direction, the add traffic TAG identification of GE1
is used together with the drop TAG action of GE5.
u In the data downlink direction, the add traffic TAG identification of

GE5 is used together with the drop TAG action of GE1.
7. (Optional) In the Flow Settings tab, set the QoS policy of the specified port
(GE1 or GE5) of the source node NE1 of E-LAN service. You can also set the
QoS policy after completing the configuration of E-LAN service. For the
configuration method and parameters, see Table 4-13.

you can view or activate the created E-LAN service.
Version: B 155
4.4.6 Configuring User-to-Network E-LAN Services
Network Diagram
is required that the user-to-network E-LAN service should be created among NE1,
NE2 and NE3 to implement mutual communication among UNI interfaces of NE1,
NE2 and NE3.
Prerequisite
u The Tunnels between NE1 and NE2, between NE1 and NE3 and between NE2
and NE3 have been configured.
u The PWs between NE1 and NE2, between NE1 and NE3 and between NE2
and NE3 have been configured.
156 Version: B
Planning Data
The user-to-network E-LAN service among NE1, NE2 and NE3 is used as an
example. The planning data are listed as follows:
Item Specification
Service Name ELAN-123

Service Type E-LAN
NE1: GE1
Set an NE NE2: GE1
NE3: GE1
Service topology
NE1↔NE2 NE1↔NE3 NE2↔NE3
structure
Select the Service
V1-2 V1-3 V2-3
Layer Circuit
Procedure
The following introduces how to configure the user-to-network E-LAN service, using
the user-to-network E-LAN service among NE1, NE2 and NE3 as an example.

box.
Version: B 157
3. Click Next and set the nodes and ports of the E-LAN service.
158 Version: B
NE - Sets the nodes of the E-LAN service.

Set an
Sets the ports of the user-to-network E-LAN
NE Port -
service.
4. Click Next and set the routing topology attributes of the user-to-network E-LAN
service.
4 When there are multiple PWs between the source NE and sink NE and you
need to select the desired PW entry by filtering, select Set PW Filter, ➔
Step 5.
4 If you do not need to select the desired PW entry by filtering, clear the Set
PW Filter option, ➔ Step 6.
Version: B 159
Selects all the connected NEs in the topology

Service topology
- structure of user-to-network E-LAN service
structure
5. (Optional) Select Set PW Filter. In the Set PW Filter dialog box that appears,
set the filtering conditions of PWs between connected NEs, and the desired
PW entries will be displayed in the Select the Service Layer Circuit list. If you
clear the Set PW Filter option, all PW entries between connected NEs will be
displayed in the Select the Service Layer Circuit list.
160 Version: B
Excluded and
Sets the filtering conditions of PWs between
Set PW Filter Included
connected NEs to including or excluding the
(Constraints) The default value:
specified NE or interface.
Included
6. Click Next and select the PW circuit that carries the E-LAN service.
Version: B 161
Select the Service Layer Selects the PW circuit that carries E-LAN
-
Circuit services.
policies of the nodes included in the E-LAN service according to the project
requirements.
8. (Optional) Select the specified node (NE1, NE2 or NE3), and set the flow VLAN
and flow type of UNI interface of the node in the Flow Settings and Flow
162 Version: B
service.
Classification.
9. (Optional) Select the specified node (NE1, NE2 or NE3), and set the VLAN
operations on UNI/NNI interface of the node in the UNI Interface Settings and
NNI Interface Settings tabs respectively. See Table 4-7 for specific
descriptions.
Version: B 163
Note:
10. (Optional) In the Flow Settings tab, set the QoS policy of UNI port of the
specified node (NE1, NE2 or NE3) of the E-LAN service. You can also set the
QoS policy after completing the configuration of E-LAN service. For the
164 Version: B
you can view or activate the created E-LAN service.
4.4.7 Configuring E-Tree Services
Network Diagram
is required that the E-Tree service should be created among NE1, NE2 and NE3 to
implement communication between NE1 and NE2 and between NE1 and NE3. No
communication is required between NE2 and NE3.
Prerequisite
u The Tunnel between NE1 and NE2 and that between NE1 and NE3 have been
configured.
Version: B 165
u The PW between NE1 and NE2 and that between NE1 and NE3 have been
configured.
Planning Data
The user-to-network E-Tree service among NE1, NE2 and NE3 is used as an
example. The planning data are listed as follows:
Item Specification
Service Name ETree-123

Service Type E-Tree
NE1: GE1 (root node)
Set an NE NE2: GE1 (leaf node)
NE3: GE1 (leaf node)
Select the Service Layer

NE1↔NE2: V1-2 NE1↔NE3: V1-3
Circuit
Procedure
The following introduces how to configure the user-to-network E-Tree service, using
the user-to-network E-Tree service among NE1, NE2 and NE3 as an example.

box.
166 Version: B
3. Click Next, and set the nodes and ports of E-Tree service. The first selected
node (displayed in blue) is regarded as the root node by default.
4 When there are multiple PWs between the root node and leaf node and
you need to select the desired PW entry by filtering, select Set PW Filter,
➔ Step 4.
4 If you do not need to select the desired PW entry by filtering, clear the Set
PW Filter option, ➔ Step 5.
Version: B 167
Set an NE - Set the root node and leaf node of E-Tree service.
NE Port - Set the ports of E-Tree service.
Note:
You must select one root node (displayed in blue) and at least two leaf
nodes (displayed in black) for the E-Tree service.
4. (Optional) Select Set PW Filter. In the Set PW Filter dialog box that appears,
set the filtering conditions of PWs between root node and leaf nodes, and the
desired PW entries will be displayed in the Select the Service Layer Circuit
list. If you clear the Set PW Filter option, all PW entries between root node and
leaf nodes will be displayed in the Select the Service Layer Circuit list.
168 Version: B
Set the filtering conditions of PWs between root node

Set PW Filter
- and leaf nodes to including or excluding the specified
(Constraints)
NE or interface.
5. Click Next and select the PW circuit that carries the E-Tree service.
Version: B 169
Select the Service

- Select the PW circuit that carries E-Tree services.
Layer Circuit
policies of the nodes included in the E-Tree service according to the project
requirements.
7. (Optional) Select the specified node (NE1, NE2 or NE3), and set the flow VLAN
and flow type of UNI interface of the node in the Flow Settings and Flow
service.
170 Version: B
Classification.
8. (Optional) Select the specified node (NE1, NE2 or NE3), and set the VLAN
operations on UNI/NNI interface of the node in the UNI Interface Settings and
NNI Interface Settings tabs respectively. See Table 4-7 for specific
descriptions.
Version: B 171
Note:
9. (Optional) In the Flow Settings tab, set the QoS policy of UNI port of the
specified node (NE1, NE2 or NE3) of the E-Tree service. You can also set the
QoS policy after completing the configuration of E-Tree service. For the
172 Version: B
you can view or activate the created E-Tree service.
4.4.8 Configuring Multicast
Network Diagram
As shown in the figure, NE1 to NE4 use the CiTRANS 610A as access equipment.
An E-Tree service has been created between NE1 and NE4 with NE1 as root node
and NE2 to NE4 as leaf nodes. NE2 to NE4 are connected to the users respectively.
NE1 is interconnected with NE2, NE3 and NE4 via the VPLS network.
In this VPLS network, if the IGMP Snooping is not configured on NE1, the multicast
data flow will be broadcast within the VSI, wasting the bandwidth. To ensure that the
multicast data will not be forwarded on the PW without a receiver, you need to
enable the IGMP Snooping within the VSI of NE1. Besides, you need to configure
the static multicast to add the PW with receivers into the multicast group.
Version: B 173
Prerequisite
You have configured the E-Tree service between NE1 and NE4.
Planning Data
In this example, you only need to configure the multicast function for the root node
NE1. The planning data of NE1 are listed as follows.
Table 4-8 Configuration of IGMP-SNOOPING
Item Specification
VPN-ID 1
IGMP-SNOOPING Enable
type V1
Table 4-9 Static Multicast
Item Specification
VPLS-VS-Select VS1
eLAN1: Join
Port-SelectNote 1
eLAN3: Join
Note 2
MAC-Address 00-00-00-00-00-01
Note 1: Set the members which need to join the multicast group.
Note 2: The MAC address in the planning data is only an example. You need to set the source
MAC address of the multicast group according to the project requirements.
Procedure
The following introduces how to configure the IGMP-SNOOPING and static

multicast, using the configuration of multicast function for the root node NE1 as an
example.
174 Version: B
2. Click the XCTR2 card in the subrack view of NE1, and select Board
3. Click the VPLS-VS tab, and view the VS ID of VPLS service, the LAN-ID of
LAN entry and the LAN-ID of the emulation LAN port entry.
Version: B 175
Item Description
The ID of VSI corresponding to the VPLS service on the

VS-ID
NE
The entry information about the leaf node on the UNI side
LAN
of VSI
LAN LAN-ID The LAN ID of the leaf node on the UNI side
The entry information about the leaf node on the NNI side
LAN
of VSI
LAN LAN-ID The LAN ID of the leaf node on the NNI side
4 After completing the configuration of VPLS L2VPN (E-LAN / E-Tree)

service via Business Configuration and saving and delivering the
configuration data, the VPLS service data will be automatically mapped to
the VPLS-VS tab in the corresponding card configuration GUI.
4 You can view the VSI information of each NE node of VPLS service via the
following method:
a) In the OTNM2000 window, click Business Management→L2VPN in

the menu bar to bring up the L2VPN Service dialog box.
b) In the L2VPN Service tab, right-click the desired VPLS entry and
select Display Properties from the shortcut menu to bring up the
L2VPN Properties dialog box.
176 Version: B
c) In the L2VPN Properties dialog box, check the VSI information of

each NE node, including the VSI ID (VS-ID), UNI side information (LAN)
and NNI side information (emulation LAN port).
4. Click the IGMP-SNOOPING-Config tab. Right-click the blank area and select
Add-Item from the shortcut menu to add the IGMP Snooping configuration
entry. Set parameters such as VPN-ID, IGMP-SNOOPING and type. You can
also add and configure multiple IGMP Snooping entries according to project
planning.
Version: B 177
Sets the ID of the VSI which should be enabled with the

VPN-ID -
IGMP Snooping, namely the VS ID in the VPLS-VS tab.
IGMP- Disable and Enables or disables the IGMP Snooping within the current
SNOOPING Enable VSI.
V1, V2 and V3 Sets the version of IGMP packets that can be processed by
type The default IGMP Snooping within the current VSI. V1, V2 and V3 refer
value: V1 to IGMPv1, IGMPv2 and IGMPv3 respectively.
5. Click the Static-Group-Cast-Config tab, and set the static multicast function.
1) Right-click the blank area and select "Add-Item" from the shortcut menu to
add the configuration entry. You can also add and configure multiple static
multicast entries according to project planning.
2) Set parameters such as VPLS-VS-Select and MAC-Address.
178 Version: B
Value
Range
Selects the ID of the VSI which should be enabled with the

VPLS-VS-Select -
static multicast, namely the VS ID in the VPLS-VS tab.
MAC-Address - Sets the source MAC address of the multicast group.
3) Sets the Port-Select parameters, and selects the ID of the LAN or eLAN
which will join the multicast group.
a) Click to bring up the Port-Select dialog box.
b) In the Choice item box on the left, select the desired LAN ID or eLAN
ID. Click , and the selected items will be displayed in the item to
be modified box on the right.
Version: B 179
c) Select Join, and click Modify to close the dialog box, completing the
settings of parameters in Port-Select.
Value
Range
Sets the ID of LAN or eLAN which will join the multicast group.
LAN ID is the LAN-ID of LAN entry in the VPLS-VS tab, and
Port-Select -
eLAN ID is the LAN-ID of the emulation LAN port entry in the
VPLS-VS tab.
4) (Optional) Right-click Item and select Style to modify the display style of
parameters.
180 Version: B
Note:



4.5 Configuring CES Services
This section introduces the basic concepts and configuration method of CES
service.
4.5.1 Basic Concepts and Configuration Rules of CES
You need to know about the basic concepts and application scenarios of CES
services before configuration.
Version: B 181
Basic Concepts
E-CES service is a type of point-to-point service. It is mainly applied in wireless

service and enterprise private line service. It belongs to the MPLS L2VPN in VPWS
mode.
Figure 4-11 shows the network of the E-Line service. The difference between E-
CES and E-Line is described as follows:
u E-Line service transparently transmits the Ethernet service in the MPLS

network, using the Ethernet interface as the UNI interface.
u E-CES service transparently transmits the TDM service in the MPLS network,
using the E1 or STM-1 interface as the UNI interface.
Figure 4-11 Network Diagram of E-CES Service
Configuration Rule
u You must complete configuration of the Tunnel and PW used by the E-CES
before configuring the E-CES service.
u Each E-CES service exclusively occupies a PW.
u Each E-CES service should be configured with a pair of UNI interfaces.
182 Version: B
4.5.2 Configuring CES Services
Network Diagram
is required that a CES service should be created between NE1 and NE2.
Prerequisite
u The Tunnel between NE1 and NE2 has been configured.
u The PW between NE1 and NE2 has been configured.
Note:
When configuring a Tunnel that carries CES services, select E1 for the
source and sink ports of the Tunnel.
Planning Data
The planning data are described as follows, using the CES service between NE1
Item Specification
Service Name CES1-2

Service Type E-CES
Version: B 183
Item Specification
Source NE NE1
Source Port E-CES0/1/1
Sink NE NE2
Sink Port E-CES0/1/1

Select the Service Layer (PW) V1-2
Procedure
The following introduces how to configure the CES service, using the CES service
between NE1 and NE2 as an example.

box.
184 Version: B
3. Click Next and set the parameters such as source and sink nodes, ports and
constraints of the CES service.
You can set the source and sink nodes using the following two methods:
4 Click on the right of Source NE or Sink NE and select from the drop-
down menu.
automatically displayed in the configuration item of Source NE or Sink NE.
The NE which is clicked for the first time is the source node, and the one
Sets the bandwidth type of the CES service to lower

Bandwidth Type VC12
order path VC12.
Source NE - Sets the source node of CES service.
Version: B 185
Sets the source port of CES service. When you

need to create multiple CES services in a batch
Source Port -
manner, select multiple ports. And you need to
create enough PWs in advance.
Sink NE - Sets the sink node of CES service.
Sets the sink port of CES service. When you need

to create multiple CES services in a batch manner,
Sink Port - and you have selected multiple ports as source
ports, you need to select the sink ports of the same
quantity as that of source ports.
PDH E1,
u Set this item to PDH E1 for the E1 interface.
Port Type STM1, STM4
u Set this item to STM1 for the STM1 interface.
and STM16
When you have selected the specified NE and set
the Constraints to included or excluded, the CES
NE -
service path will include or exclude this NE. Set this
item according to project planning.
When you have selected the port of the specified

NE and set the Constraints to included or
Con- Port - excluded, the CES service path will include or
straints exclude the ingress port of the NE. Set this item
Excluded and You can set this item to included or excluded

Included according to the corresponding settings in NE and
Con-
The default Port. It indicates that the CES service path includes
straints
value: or excludes the specified NE or port. Set this item
Included according to project planning.
4. Click Next and select the PW circuit that carries the CES service.
186 Version: B
Selects the PW circuit that carries CES services.

Select the Service You need to select the corresponding number of
-
Layer (PW) PWs when creating multiple CES services. Each
CES service occupies one PW.
5. Click Next and you can set the QoS policy of source or sink node according to
project requirements.
4 If you do not need to set the QoS policy, ➔ Step 7.
Version: B 187
6. (Optional) In the CE Properties tab, set the QoS policy of the source or sink
node of CES service. You can set the QoS policy after completing configuration
of CES service. For the configuration method and parameter description, see
Table 4-13.
188 Version: B

you can view or activate the created CES service.
4.6 Saving and Delivering Services
Save the configured data to the database and deliver the data to the equipment. For
the configuration data to be modified, the following introduces the general deleting
rules.
Version: B 189
Prerequisite
The configuring data have been confirmed to be correct.
Configuring Delivery Rules
u The configuration data are delivered in this sequence: Tunnel→L2VPN.
u The single-segment PW cannot be delivered to the equipment independently,

but can be delivered together with L2VPN service.
u The configuration data are delivered successfully when the Active item is
displayed as Activated.
u After performing operations such as modifying or deleting the configuration

data, you need to deliver the configuration data so that the corresponding
operation will be validated.
u You can select multiple configuration data items by pressing the <Ctrl> key and
selecting the data items in the lower pane of the business management view,
so as to deliver, delete or save these data items in a batch manner.
u Save the configuration data to the database after completing delivery of data.
u To modify the path of the Tunnel (configured with the LSP 1:1 protection)
associated with L2VPN, use the following methods.
4 When modifying the standby Tunnel path, you can unbind the LSP
protection, then modify the standby LSP path, and finally configure the
LSP protection for the active tunnel again.
4 When modifying the active Tunnel, you can unbind the LSP protection,
then modify the active LSP path, and finally configure the LSP protection
for the active Tunnel again.
Procedure
1. Access the GUIs for saving and delivering the cross-connect data according to
Table 4-10.
190 Version: B
Table 4-10 Access Method for Saving and Delivering the Cross-connect Data
Item Access Method Description
Applies to all the circuit data

In the OTNM2000 window, click Business that can be saved. You can
Save Cross- Management→Tunnel/L2VPN in the menu select one or more circuit
connect of the bar. In the tab that appears, right-click a circuit data items to save. Saving
Select Path item and select Save Cross-connect of the the selected circuit data will
Select Path from the shortcut menu. associate with the NE
cross-connect data.
Applies to all the circuit data
that can be delivered. You
In the OTNM2000 window, click Business
can select one or more
Deliver Cross- Management→Tunnel/L2VPN in the menu
circuit data items to deliver.
connect of the bar. In the tab that appears, right-click a circuit
Delivering the selected
Select Path item and select Deliver Cross-connect of the
circuit data will associate
Select Path from the shortcut menu.
with the NE cross-connect
data.
In the OTNM2000 window, click Business Saves the cross-connect
Save Cross-
Management→Full Download→Save Cross- data of all or the selected
connect (NE)
connect (NE) in the menu bar. NEs under a project.
In the OTNM2000 window, click Business Delivers the cross-connect

Deliver Cross-
Management→Full Download→Deliver data of all or the selected
connect (NE)
Cross-connect (NE) in the menu bar. NEs under a project.
Note:
u Saving cross-connect data: Save the configuration data to the

database. When the OTNM2000 is disconnected with the equipment,
you can save the cross-connect data to avoid loss of configuration
data.
u Delivering cross-connect data: Deliver the configuration data to the

equipment and save the data to the database.
2. (Optional) In the The NE cross-connect script will be generated and saved

to the database, Continue? or The cross-connect config will be deliver to
the equipment, Continue? alert box that appears, click Yes.
Version: B 191
3. In the Save NE Cross-connect or Download NE Cross-connect dialog box

that appears, select the desired object, and click Start or Download.
Note:
Click No in the Compare NE Cross-connect Script? alert box that

appears.
192 Version: B
4.7 Configuring Clock Synchronization
This section introduces the basic concepts and configuration methods for clock
synchronization.
4.7.1 Basic Concepts and Configuration Rules of Clock

Synchronization
This section introduces the basic concepts and configuration rules of clock
synchronization.
Basic Concepts
Clock synchronization refers to the attaining of synchronism between the

frequencies or phases of two or more signals; the obtaining of a desired, fixed
relationship among corresponding significant instants of two or more signals; the
valid moment occurs at the same rate. In this way, all the equipment in the
communication network can work at the same rate.
The CiTRANS 610A supports the following clock synchronization functions.
u Supports three clock working modes: locked, holdover and free running.
u Supports extracting clock from interfaces for tracing; supports tracing the
external clock.
u Provides one channel of external clock input / output, supports 120Ω clock
interfaces, and provides 2048 kHz / 2048 kbit/s (HDB3) clock signals.
u Processes and transmits synchronization status messages (SSM).
Configuration Rule
Configuration rules of the clock synchronization are as follows:
1. Synchronization reference source selection:
4 If BITS or other high-precision external clock equipment exists, configure

the NE to trace the external synchronization reference source.
4 If no BITS or other high-precision external clock equipment exists,

configure the NE to trace the line synchronization reference source.
Version: B 193
4 It is advisable to use the internal synchronization reference source as the

synchronization reference source of the lowest level.
2. Trace the line clock following the shortest path rule.
4 For the ring network composed of less than six NEs, trace the reference
source in one direction.
4 For the ring network composed of six NEs or more than six NEs, the line
clock should trace the shortest path. For example, if the network is
composed of N NEs, there should be N/2 NEs that trace the reference
clock in one direction, and the other N/2 NEs that trace the reference clock
in another direction (if the N is an odd number, the middle NE can trace the
reference clock in any direction).
3. The maximum hop number of clock tracing should be no more than 20.
4. Enable the standard SSM protocol.
5. For the equipment configured with multiple clock sources, set the clock source
restoration mode to auto mode.
194 Version: B
4.7.2 Configuring Clock Synchronization
Network Diagram
As shown in the figure, NE1 and NE2 are CiTRANS 650, and NE3 and NE4 are
CiTRANS 610A. The requirements of clock synchronization are described as
follows.
u NE1 and NE2 are connected to the active and standby clock sources (2048kHz)
respectively. The clock precisions are in compliance with G.811 standards and
G.812 standards respectively.
u The clock transfer direction is as follows: NE1→NE3→NE4→NE2 (active);

NE2→NE4→NE3→NE1 (standby).
Version: B 195
Prerequisite
u You have known about the clock synchronization planning.
Planning Data
The planning data are listed as follows, using the clock synchronization of NE1 to
NE4 for example.
Item NE1 NE2 NE3 NE4

CKU-Payload Auto Auto Auto Auto
QL-Mode QL_Enable QL_Enable QL_Enable QL_Enable
EXT-
GE0/9/0/1>EXT- Port-6>Port- Port-6>Port-
CLK-PriorityNote 1 CLK>G-
CLK>NULL 5>NULL 5>NULL
E0/10/0/1>NULL
EXT-CLK1-Type Hz Hz - -
EXT-CLK-S1: GE0/9/0/1: Auto_ Port-5: Auto_ Port-5: Auto_
G811 pick_S1 pick_S1 pick_S1
QL-Input-Set
GE0/10/0/1: EXT-CLK-S1: Port-6: Auto_ Port-6: Auto_
Auto_pick_S1 G812 pick_S1 pick_S1
Port-5: Auto_ Port-5: Auto_

GE0/10/0/1: GE0/9/0/1: Auto_ pick_S1 pick_S1
QL-Output-Set
Auto_pick_S1 pick_S1 Port-6: Auto_ Port-6: Auto_
pick_S1 pick_S1
Note 1: > indicates the priority level. The value above NULL indicates a valid clock source. For
example, Port-6>Port-5> NULL means that the line clock source of Port-6 is superior
to that of Port-5 when the clock source is selected, and both are valid clock sources.
Procedure
This example only introduces how to configure clock synchronization for the
CiTRANS 610A, using NE3 for example.
196 Version: B
2. Click the desired card in the subrack view of NE3, and select Board
3. Click the Clock-Config tab, and set parameters such as CLK_Work_Mode and
QL-Mode.
Version: B 197
Sets the clock working mode.

u AUTO: When there is a qualified clock source, the
slave clock will enter the locked state; if all current
AUTO, HOLD and clock sources are interrupted, the slave clock will
CLK_
FREE enter the holdover or free running state depending
Work_
The default value: on its state before interruption.
Mode
AUTO u HOLD: Forces the clock to enter the holdover
mode.
u FREE: Forces the clock to enter the free running
mode.
Sets whether to enable the SSM function.
u QL-Enable: In this mode, the clock module will
select the superlative clock source as the clock
QL-Enable and QL- lock source according to the QL value. If the QL
Disable value is the same, the clock source with a higher
QL-Mode
The default value: QL- priority will be selected as the reference source
Disable preferentially according to the clock priority list.
u QL-Disable: In this mode, the clock module will
select the clock source with the highest priority in
the clock priority list as the clock lock source.
198 Version: B
Sets the priority level of the clock source according to

the actually accessed clock source. The options above
CLK-
- NULL indicate used clock sources, while the options
Priority
below NULL indicate unused clock sources. The
priority descends from the top down.
EXT-CLK1- Hz and HDB3 Sets the type of external clock according to the type of
Type The default value: Hz external clock synchronization source.
Sets the quality level of input source. When there is an

UnKnow, G811,
external clock input, you need to set the QL value for
G812Local, G813 and
QL-Input- the external clock; otherwise, keep the default setting.
Auto-pick-S1
Set If the lines involve in synchronization and serve as
The default value:
clock input, set this item to Auto_pick_S1; otherwise,
G813
keep the default setting.
Sets the quality level of output source. When there is

UnKnow, G811,
an external clock output, you need to set the QL value
G812Local, G813 and
QL-Output- for the external clock; otherwise, keep the default
Auto-pick-S1
Set setting. If the lines involve in synchronization and
The default value:
serve as clock output, set this item to Auto_pick_S1;
G813
otherwise, keep the default setting.
Version: B 199
Note:



4.8 Configuring MTU

Background Information
MTU is short for Maximum Transmission Unit. It refers to the maximum number of
bytes of a data packet that can be transmitted by an interface.
When two sets of equipment on the same network interconnect with each other, if
the MTU set at the transmit end exceeds the maximum number of bytes supported
by the receive end or a transit equipment, data packets will be discarded during the
course of forwarding.
When the CiTRANS 610A interconnects with the MAN offered by another vendor, it
is recommended that the MTU of the channel offered by the MAN of another vendor
be set to a value larger than 1600. When the MTU setting of another vendor
includes the interface MTU and PWE3 MTU, it is recommended that both MTUs be
set to a value larger than 1600.
Prerequisite
You have configured the interfaces.
200 Version: B
Configuration Rule
The value of MTU must be larger than the maximum number of bytes of the packets
transmitted on the network.
Procedure
2. Click the desired card in the subrack view, and select Board Configuration in
the Task Panel pane.
Version: B 201
3. Click the SYS-Port-Config tab, and select the desired interface. Set the MTU
according to the project planning.
1518 to 9600 bytes The value of MTU must be larger than the maximum
MTU The default value: number of bytes of the packets transmitted on the
1518 network. Generally the default value 1518 is used.
202 Version: B
Note:



4.9 Configuring QoS
QoS policies of a Tunnel, a PW or a L2VPN can be configured in one of the

following two ways:
u Set QoS in course of configuring a Tunnel, a PW or a L2VPN. See Configuring

Tunnels, Configuring PWs and Configuring E-Line Services for the
configuration methods.
u Set QoS after you finish configuring a Tunnel, a PW or a L2VPN.
This section describes how to set QoS after you finish configuring a Tunnel, a PW or
a L2VPN.
Background Information
Quality of service (QoS) is a mechanism that guarantees a required level for

services in terms of bandwidth, delay, jitter, and packet loss ratio in a
communication network. In this way, the request and response of a user or an
application can satisfy the expected level of service. QoS does not contribute to
increase of bandwidth but it can be used to allocate and monitor network resources
properly to minimize network delay and jitter and ensure the quality of key services.
Version: B 203
Figure 4-12　shows the processing sequence of QoS technology on the equipment.

Traffic classification (which is the prerequisite for providing DiffServ for different
services) is applied on the equipment first, and then other QoS technologies such
as traffic policing, congestion avoidance, congestion management and traffic
shaping are applied, providing committed QoS for various services that have
different network requirements.
Figure 4-12 Processing Sequence of QoS Technology on the Equipment
u Traffic classification indicates classifying packets according to the matching

rules defined based on some specific information contained in the packets, and
implementing different QoS policies for the packets matching different rules.
The traffic classification is the basis of QoS application.
u Traffic policing indicates controlling the incoming traffic to ensure that the
network resources are properly allocated. In the traffic policing mechanism, the
committed access rate (CAR) is used to control traffic.
u Congestion avoidance is a traffic control mechanism which automatically

discards packets based on packet discarding policies when network congestion
occurs.
u Congestion management indicates making policies to decide the processing

sequence and discarding rules for packet forwarding when network congestion
occurs. The queue scheduling technology is generally used for congestion
management. Packets sent from one interface are placed into multiple queues
with different priorities. The packets are sent based on the priorities. Different
queue scheduling algorithms are used for different situations and result in
different results.
u Traffic shaping limits the traffic and burst of an outgoing connection in the
network, and ensures that the packets are transmitted out of the network in a
uniform rate.
204 Version: B
The technology which implements traffic classification according to different

methods can be classified into simple traffic classification and complex traffic
classification. The CiTRANS 610A generally uses the simple traffic classification.
The basic principles of the simple traffic classification are described as follows.
u The simple traffic classification implements the mapping between the internal
priority and external priority. Firstly, packets are classified based on the EXP
values of MPLS packets and the 802.1P values of VLAN packets. Then, the
mapping between the priorities of the packets on different networks is created.
u Simple traffic classification can be classified into uplink simple traffic

classification and downlink simple traffic classification.
4 Uplink simple traffic classification: The packets are classified into eight
CoSs (CS7, CS6, EF, AF4 to AF1, and BE) and marked with three colors
(green, yellow and red) based on the EXP values of MPLS packets and
802.1P values of VLAN packets. When the CoS of packets is EF, BE, CS6
or CS7, the packets are marked in green by default. The uplink simple
traffic classification is used to differentiate services such as voice, video
and data services.
In the process of congestion management and queue scheduling, different

services enter different queues to implement different scheduling solutions.
For example, voice services can enter the PQ queues with a higher priority
to ensure a low latency. If the uplink simple traffic classification is not
implemented, the service type of all the packets is BE.
4 Downlink simple traffic classification: Based on the CoSs (CS7, CS6, EF,
AF4 to AF1, and BE) and three colors (green, yellow and red), the EXP
values of MPLS packets, and the 802.1P values of VLAN packets are
reset. The downlink simple traffic classification implements the function of
re-marking, which means re-marking the EXP values of MPLS packets or
the 802.1P values of VLAN packets.
Prerequisite
u You have configured the L2VPN service (E-Line, E-LAN, E-Tree or E-CES).
Version: B 205
Configuration Rule
u The QoS related traffic bandwidth control and service priority are deployed at
the service layer (L2VPN flow layer and PW layer). Deploying at the Tunnel
layer is not recommended.
u As for the QoS related queue scheduling and congestion avoidance, you are
advised to keep the default settings. Manual configuration is not recommended.
u The common QoS functions used for the CiTRANS 610A include simple traffic
classification (service priority), traffic policing (traffic bandwidth policy),
congestion avoidance (queue buffering policy) and congestion management
(queue scheduling policy). Figure 4-13 shows the application of QoS in the
service network.
Figure 4-13 Application of QoS
Configuring QoS Policy of Tunnel
1. In the OTNM2000 window, click Business Management→Tunnel in the menu

bar to bring up the Tunnel dialog box.
2. In the Tunnel dialog box, click Filter and all the configured Tunnels will be
displayed by default. You can also set the filter conditions to query the
configured Tunnel as required.
3. In the Tunnel tab, right-click the desired Tunnel entry and select Display
Properties from the shortcut menu to bring up the Path Properties dialog box.
206 Version: B
4. In the Property Settings tab, set the traffic bandwidth policy of a Tunnel, and
click OK.
Version: B 207
Table 4-11 QoS Policy Parameters of a Tunnel
Disable and
Only when this item is set to Enable can the
Bandwidth Control Enable
committed bandwidth and peak bandwidth be
Enabling The default value:
set.
Disable
Sets the committed bandwidth, the rate that
Committed Bandwidth Value range: 0 to
allows the service to pass through. It is set
(CIR) 1000; unit: Mbps.
Sets the peak bandwidth, which is the maximum

Value range: 0 to
Peak Bandwidth (PIR) rate for the service to pass. It is set according to
1000; unit: Mbps.
the project planning.
32 to 1024 (unit: The committed burst size, the committed traffic

CBS
KB) that can pass through instantly.
Peak burst size, the peak traffic that can pass

32 to 1024 (unit:
PBS through instantly. PBS should be larger than
KB)
CBS.
208 Version: B
Configure QoS policy of the PWs
1. In the OTNM2000 window, click Business Management→PW in the menu bar

to bring up the PW dialog box.
2. In the PW dialog box, click Filter and all the configured PWs will be displayed
by default. You can also set the filter conditions to query the configured PW as
required.
3. In the PW tab, right-click the desired PW entry and select Display Properties
from the shortcut menu to bring up the Path Properties dialog box.
4. In the Property Settings tab, set the traffic bandwidth policy, PHB/EXP
mapping policy and EXP/PHB mapping policy of a PW, and click OK.
Version: B 209
Table 4-12 QoS Policy Parameters of a PW
Sets the control mode of the traffic shaping.

Disable, trTCM and
trTCM is recommended.
Modified trTCM
Mode u trTCM: a two rate two bucket algorithm.
The default value:
u Modified trTCM: a single rate single bucket
Disable
algorithm.
Sets the color mode of the packets. The default

value is recommended.
Color-blind, Color-aware
u Color-blind: Do not recognize the message
CM The default setting is
color in course of scheduling.
Color-blind.
u Color-aware: Recognize the message color
in course of scheduling.

Value range: 0 to 1000;
CIR allows the service to pass through. It is set
unit: Mbps.

PIR rate for the service to pass. It is set according to
unit: Mbps.
210 Version: B
Table 4-12 QoS Policy Parameters of a PW (Continued)
The committed burst size, the committed traffic

CBS 32 to 1024 (unit: KB)
that can pass through instantly.

PBS 32 to 1024 (unit: KB) through instantly. PBS should be larger than
CBS.
Sets the PHB-to-EXP mapping policy. PHB To
Assign EXP and PHB TMC/TMP EXP is recommended.
PHB To
To TMC/TMP EXP u Assign EXP: Assign an EXP value manually.
TMC/TMP EXP
The default value: u PHB To TMC/TMP EXP: use a EXP value
Mapping: Policy
Assign EXP generated by the default PHB2EXP mapping
table of the equipment.
It is valid when the PHB-to-EXP mapping policy is

0 to 7
Assign EXP set to Assign EXP. Assign an EXP value
manually.
It is valid when the PHB-to-EXP mapping policy is

1 to 15
PHB2EXP_ID set to PHB To TMC/TMP EXP. Generally the
PHB2EXP mapping table with ID 1 is used.
Sets the PHB-to-EXP mapping policy. TMC/TMP

EXP To PHB is recommended.
Select PHB and
TMC/TMP EXP u Select PHB: Specify a PHB service level
TMC/TMP EXP To PHB
To PHB manually.
The default value:
Mapping: Policy u TMC/TMP EXP To PHB: Use a PHB service
Select PHB
level generated by the default EXP2PHB
mapping table of the equipment.
BE, AF1, AF2, AF3,

It is valid when the EXP-to-PHB mapping policy is
AF4, EF, CS6 and CS7
Select PHB set to Select PHB. Specify a PHB service level
The default setting is
manually.
BE.
It is valid when the EXP-to-PHB mapping policy is
1 to 15
EXP2PHB_ID set to TMC/TMP EXP To PHB. Generally the
EXP2PHB mapping table with ID 1 is used.
Configuring QoS Policy of L2VPN
1. In the OTNM2000 window, click Business Management→L2VPN Service in

the menu bar to bring up the L2VPN dialog box.
Version: B 211
2. In the L2VPN dialog box, click Filter and all the configured L2VPNs will be
displayed by default. You can also set the filter conditions to query the
configured L2VPN as required.
3. Click the desired L2VPN entry and the Flow Info tab will display the flow
information entries of the L2VPN. Right-click the desired flow entry and select
Display Properties from the shortcut menu.
4. In the PTN Ethernet Service Flow Data Properties dialog box that appears,
set the traffic bandwidth policy, and PHB policy of this flow entry of the L2VPN,
and click OK.
212 Version: B
Table 4-13 QoS Policy Parameters of a L2VPN flow
Sets the PHB service level of user packets.

Select PHB and Base
u Select PHB: Specify the PHB service level of
On Customer Priority
Policy user packets manually.
The default value: Select
u Base On Customer Priority: Trust the priority
PHB
set in user packets.
BE, AF1, AF2, AF3,

AF4, EF, CS6 and CS7 It is valid when the Policy is set to Select PHB.
Select PHB
The default setting is Specify a PHB service level manually.
BE.
Sets the control mode of the traffic shaping.
Disable, trTCM and
trTCM is recommended.
Modified trTCM
Mode u trTCM: a two rate two bucket algorithm.
The default value:
u Modified trTCM: a single rate single bucket
Disable
algorithm.
Version: B 213
Table 4-13 QoS Policy Parameters of a L2VPN flow (Continued)
Sets the color mode of the packets. The default

value is recommended.
Color-blind, Color-aware
u Color-blind: Do not recognize the message
CM The default setting is
color in course of scheduling.
Color-blind.
u Color-aware: Recognize the message color
in course of scheduling.

CIR allows the service to pass through. It is set
unit: Mbps.

PIR rate for the service to pass. It is set according to
unit: Mbps.
The committed burst size, the committed traffic

CBS 32 to 1024 (unit: KB)
that can pass through instantly.

PBS 32 to 1024 (unit: KB) through instantly. PBS should be larger than
CBS.
Disable and Enable Only when this item is set to Enable can the
Flow Monitor
The default value: committed bandwidth and the committed burst
Enabling
Disable size be set.
Configuring QoS Policy of Port
1. In the OTNM2000 window, double-click the desired NE in the Logical Tree

pane to bring up the subrack view.
2. Click the desired card in the subrack view, and select Board Configuration in
the Task Panel pane.
214 Version: B
3. Click the Port-Senior-Config tab, and select the desired interface. Set the
buffering policy and scheduling policy of the specified queue according to the
project planning.
Version: B 215
Sets the scheduling policy of a queue based on the

project planning.
u SP: Strict priority queue scheduling strategy
Out-
SP and WFQ means scheduling the messages in the queue
Queu-
Mode The default strictly according to the priority.
e-
value: SP u WFQ: Weighted fair queuing scheduling strategy
Sche-
means implementing fair scheduling on the
dule-
queues according to the weights assigned to the
Strat-
queues.
egy
1 to 127
Set the weight value for the data in each queue
Weight The default
under the WFQ mode.
value: 1
Sets the buffering policy of a queue based on the
project planning.
u Tail-Drop: When the queue is filled to its
maximum capacity, the newly arriving packets
are dropped until the queue has enough room to
Tail-Drop and accept incoming traffic.
WRED u WRED: Before the number of data packets in
Mode
Queu- The default the output buffer area reaches the START
e- value: Tail-Drop threshold, no packet will be discarded; when it
Cache- crosses the END threshold, all packets will be
Man- discarded. when it is between the START and
age- the END thresholds, all packets face a
Pole probability of being dropped based on an

average-queue-length function.
0 to 100 When the data volume in the output buffer area is

START-
The default larger than the START threshold but lower than the
Limit
value: 50 END threshold, the data will be dropped randomly.
0 to 100 This value should be larger than the START Limit.

END-Limit The default When the data volume in the output buffer area
value: 100 exceeds this threshold, all data will be discarded.
216 Version: B
Note:



4.10 Configuring Typical Scenarios
This section introduces the service model and configuration method of typical
scenarios.
4.10.1 Introduction to Service Model
The basic topology of the client service model include NNI and Overlay models.
Version: B 217
4.10.1.1 NNI Model
Network Model
Figure 4-14 Network Diagram of NNI Model
As shown in Figure 4-14, the NNI model indicates that the NNI interface of the
CiTRANS 610A interconnects with the NNI interface of the MAN equipment offered
by FiberHome.
Service Implementation
u The NNI model is applicable to the scenario that the MAN only uses the
equipment offered by FiberHome. This model features the whole-course
application of MPLS-TP technology in the entire network.
u The access point B1/B2 of MAN uses the NNI interface to connect with the NNI
interface of the CiTRANS 610A.
u The network management packets are encapsulated in the MCC format of

MPLS-TP standard (without svlan), and are aggregated in in-band mode
globally.
218 Version: B
u The service packets are encapsulated in the TUNNEL+PW format of the

MPLS-TP standard (without svlan).
u The PAN network is under unified management of the network management

system of MAN.
u An end-to-end LSP from the CiTRANS 610A to A1 is created directly at the

client service access point. The LSP aggregates client services to the UNI
interface of A1 and then directly terminates the services at the IP/MPLS Core.
u The network management MCC packets of the CiTRANS 610A are aggregated
to the F interface of A2 through the OSPF automatic routing of each NE in MAN,
and then aggregated to the OTNM2000 server of NOC.
4.10.1.2 Overlay Model
Network Model
Figure 4-15 Network Diagram of Overlay Model
Version: B 219
As shown in Figure 4-15, the Overlay model indicates that the NNI interface of the
CiTRANS 610A interconnects with the UNI interface of the MAN equipment offered
by another vendor.
Service Implementation
u The Overlay model is applicable to the scenario that the MAN uses the
equipment offered by other vendors instead of FiberHome. This model features
that the FiberHome PAN equipment uses end-to-end MPLS-TP technology.
u Both the IP/MPLS Core and NOC (Network Operations Center) OTNM2000
require the HUB-PAN.
u The access point B1/B2 of MAN uses the UNI interface to connect with the NNI
interface of the CiTRANS 610A.
u The network management packets are encapsulated in the MCC format of

MPLS-TP standard (with svlan), and are aggregated in out-of-band mode in
MAN.
u The service packet are encapsulated in the TUNNEL+PW format of the MPLS-
TP standard (with svlan).
u The PAN network is separately managed independent of the MAN.
u In the PAN network, an end-to-end LSP from the CiTRANS 610A to the IP/
MPLS Core CiTRANS 650 is created at the client service access point. The
LSP aggregates client services to the UNI interface of the CiTRANS 650 and
terminates the services at the IP/MPLS Core.
u In the MAN, all the uplink service packets and network management packets of
the CiTRANS 610A are regarded as ordinary Ethernet packets. An LSP is
created based on the port+vlan traffic classification rules. At the UNI interface
of access point B1/B2, the LSP aggregates the service packets to A1, and
aggregates the network management packets to A2.
4.10.2 Configuring the NNI Model Service
This section introduces how to configure the client service in typical scenario of NNI
model using an example.
220 Version: B
Network Diagram
Figure 4-16 Typical Scenario of NNI Model
As shown in the figure, the NNI interface of the access network equipment
CiTRANS 610A interconnects with the NNI interface of the FiberHome MAN
equipment CiTRANS 660. The access network PAN equipment CiTRANS 610A is
under unified management of MAN.
It is required that the eNode B and IP/MPLS Core should be able to communicate
with each other. This can be implemented by configuring an E-Line service between
NE1↔NE6. The service route between eNode B and IP/MPLS Core is descried as
follows.
u In uplink direction
The uplink data packets of the eNode B carry no VLANs. The packets are
transmitted from NE6 to NE1, added with the VLAN ID 601 at NE1, and finally
received at the IP/MPLS Core.
Version: B 221
u In downlink direction
The IP/MPLS Core downlink data packets carry the VLAN ID 601. After being
processed by traffic classification at NE1, the packets are transmitted from NE1
to NE6. The packets are stripped of the VLAN ID 601 at NE6 and finally
received at eNode B.
Note:
u If NE21 connects with the IP/MPLS Core via one port and multiple
VLANs, you need to configure flow classification (flow VLAN and
flow type) on NE1 to identify different services.
u The VLAN operations such as identification of incoming VLAN or

action of outgoing VLAN can be configured only on NE1 or NE6, or
configured on NE1 and NE6 respectively. This example introduces
how to configure the VLAN operation on NE3 and NE6 respectively.
u The network management MCC packets of the NNI model are

aggregated in in-band mode, so that you need not set the MCC
VLAN. If the MCC　VLAN has been set, you need to disable this
function. For the methods of checking and setting MCC VLAN, see
CiTRANS 650 Small Flexible Optical Transport Platform
Configuration Guide.
Configuration Flow
The configuration flow of NNI model service is as shown below, using the
configuration of E-Line service between NE1↔NE6 as an example.
222 Version: B
Procedure
The following introduces how to configure the client service in NNI model, using
NE1 and NE6 for example.
1. Set the interface types of NE1 and NE6 according to the following items. For
the configuration method, see Configuring Interface Types.
NE Name Interface Name Interface type
S12 GE_1 UNI

NE1
S08 GE_1 NNI
GE1 UNI
NE6
GE5 NNI
2. Configure the service Tunnel between NE1↔NE6 according to the following

items. For the configuration method, see Configuring Tunnels.
Item Specification
Path Name T1-6

Signaling Static
Version: B 223
Item Specification
Source LSR NE1

Note 1 S12 GE_1
Source Port
Sink LSR NE6
Sink Port GE1
Forward 1001
Reverse 1002
Note 1: You need to select the UNI interface for the source and sink ports when creating
Tunnels for the CiTRANS 660 / 610A.
3. Configure the service PW between NE1↔NE6 according to the following items.

For the configuration method, see Configuring PWs.
Item Specification
PW Name V1-6
Signaling Static
Source NE1
Sink NE6
Positive 3001
Reverse 3001
4. Configure the E-LINE service between NE1↔NE6. For the configuration

method, see Configuring E-Line Services.
1) In the OTNM2000 window, click Business Configuration→PTN/IPRAN→

L2VPN servicein the menu bar. Configure the following items in
configuration pages of different steps.
Item Specification

Service Type E-Line
Source NE NE1
Source Port S12 GE_1
Sink NE NE6
Sink Port GE1

PW Info V1-6
2) Set the flow VLAN and flow type of the UNI interface of NE1.
224 Version: B
Item Specification
Flow Setting VLAN ID: 601

NE1
Flow Classification VLAN
Note:
If NE21 connects with the IP/MPLS Core via one port and multiple
VLANs, you need to configure flow classification (flow VLAN and flow type)
on NE1 to identify different services.
3) Set the VLAN operation on the UNI and NNI interfaces of NE1 or NE6.
Version: B 225
Item NE1 NE6
UNI The Add Traffic TAG Identification Not Identify Not Identify
Interface The Drop TAG Action Add Delete

Settings Incremental VLAN-ID at the Drop 601 -
NNI Identify the Drop TAG Not Identify Identified

Interface The Add Traffic TAG Action NOP NOP
Settings Incremental VLAN-ID at the Add - -
Note:
The VLAN operations such as identification of incoming VLAN or action

of outgoing VLAN can be configured only on NE1 or NE6, or configured
on NE1 and NE6 respectively. This example introduces how to configure
the VLAN operation on NE3 and NE6 respectively.
4) Click Completed to complete the configuration of E-Line service between

NE1↔NE6.
5. Check and deliver the data to the equipment. For the operation procedures,
see Saving and Delivering Services.
4.10.3 Configuring the Overlay Model Service
This section introduces how to configure the client service in typical scenario of
Overlay model using an example.
226 Version: B
Network Diagram
Figure 4-17 Typical Scenario of Overlay Model
As shown in the above figure, the NNI interface of the access network equipment
CiTRANS 610A offered by FiberHome interconnects with the UNI interface of the
MAN equipment offered by another vendor. The access network PAN equipment is
separately managed by the OTNM2000 of FiberHome. When creating the network
topology using the OTNM2000, you need to create a virtual NE to simulate the MAN
offered by another vendor and connect it with the PAN equipment at both ends of
the MAN.
Version: B 227
It is required that the eNode B and IP/MPLS Core should be able to communicate
with each other. This can be implemented by configuring an E-Line service between
NE1↔NE3. The service route between eNode B and IP/MPLS Core is descried as
follows.
u In uplink direction
The uplink data packets of the eNode B carry no VLANs. After being added
with the VLAN ID 601 at NE3, the packets are transmitted from NE3 to NE1 by
passing through the VPWS channel offered by another vendor for transparently
transmitting service packets, and finally received at the IP/MPLS Core.
u In downlink direction
The IP/MPLS Core downlink data packets carry the VLAN ID 601. After being
processed by traffic classification at NE1, the packets are transmitted from NE1
to NE3 by passing through the VPWS channel offered by another vendor for
transparently transmitting service packets. The packets are stripped of the
VLAN ID 601 at NE3 and finally received at eNode B.
228 Version: B
Note:
u The channel for transmitting service packets and that for transmitting
network management MCC packets offered by the MAN of another
vendor should be the VPWS private line service channels used for
transparently transmitting specific VLAN IDs.
u The service Tunnel between NE1↔NE3 should use the VLAN sub-
interface whose VLAN ID is 800, so that it can transparently pass
through the VPWS channel with VLAN ID 800 offered by the MAN of
another vendor. Configure a NNI VLAN sub-interface whose VLAN
ID is 800 for NE1 (the CiTRANS 650) and configure static ARP of the
NNI VLAN sub-interface. See CiTRANS 650 Small Flexible Optical
Transport Platform Configuration Guide for configuration methods.
u NE2 (the CiTRANS 650) should be configured with an MCC VLAN

according to the VLAN ID of the channel used for transmitting
network management MCC packets. In this case, NE2 can transmit
the network management MCC packets which carry this VLAN ID,
and manage the remote end PAN equipment such as NE3 (the
CiTRANS 610) by passing through the MAN offered by another
vendor. For methods to view and configure a MCC VLAN, see
CiTRANS 650 Small Flexible Optical Transport Platform
Configuration Guide.
u The VLAN operations such as identification of incoming VLAN or

action of outgoing VLAN can be configured only on NE1 or NE3, or
configured on NE1 and NE3 respectively. This example introduces
how to configure the VLAN operation on NE3.
Configuration Flow
The configuration flow of Overlay model service is as shown below, using the
configuration of E-Line service between NE1↔NE3 as an example.
Version: B 229
Procedure
The following introduces how to configure the client service in Overlay model, using
NE1 and NE3 for example.
1. Set the interface types of NE1 and NE3.
4 NE3 (the CiTRANS 610)
Set the interface type of NE3 according to the following items. For the
configuration method, see Configuring Interface Types.
NE Name Interface Name Interface type
GE1 UNI
NE3
GE5 NNI
4 NE1 (the CiTRANS 650)
Set the interface type of NE1 according to the following items. For the
configuration method, see CiTRANS 650 Small Flexible Optical Transport
Platform Configuration Guide.
NE1 GE0/9/0/1 L2 (UNI)
230 Version: B
GE0/7/0/1 TP (NNI)
GE0/7/0/1.800 TP (NNI)
2. Configure the service Tunnel between NE1↔NE3. For the configuration

method, see Configuring Tunnels.
1) In the OTNM2000 window, click Business Configuration→PTN/IPRAN→

Tunnel in the menu bar. Configure the following items in configuration
pages of different steps.
Item Specification
Use VLAN Sub-interface Select

Path Name T1-3
Signaling Static
Source LSR NE1
Note 1 -
Source Port
Sink LSR NE3
Note 2
Sink Port GE1
Forward 1001
Version: B 231
Item Specification
Reverse 1002
Note 1: You do not need to set the source and sink ports when creating Tunnels for the
CiTRANS 650.
Note 2: You need to select the UNI interface for the source and sink ports when creating
Tunnels for the CiTRANS 610A.
2) In the Ingress Direction VLAN ID and Egress Direction VLAN ID of

Route Info, set the VLAN ID of the Tunnel to 800, so that the service
Tunnel can transparently pass through the channel offered by the MAN of
another vendor.
a) In the path W_F, set the VLAN ID of the Tunnel forward path to 800.
b) In the path W_R, set the VLAN ID of the Tunnel reverse path to 800.
232 Version: B
Note:
The alert box will appear during the setting of egress/ingress direction
VLAN ID. Click Yes and the OTNM2000 will modify the ingress / egress
label (VLAN ID) of other nodes on the path to the same value
automatically; click No and the OTNM2000 will only modify the ingress
label (VLAN ID) of the next station on the path automatically.
3) Click Completed to complete the Tunnel creation.
3. Configure the service PW between NE1↔NE3 according to the following items.

For the configuration method, see Configuring PWs.
Item Specification
PW Name V1-3
Signaling Static
Source NE1
Sink NE3
Positive 3001
Reverse 3001
4. Configure the E-LINE service between NE1↔NE3. For the configuration

method, see Configuring E-Line Services.
Version: B 233
1) In the OTNM2000 window, click Business ConfigurationPTN/

IPRANL2VPN service in the menu bar. Configure the following items in
configuration pages of different steps.
Item Specification

Service Type E-Line
Source NE NE1
Source Port GE0/9/0/1
Sink NE NE3
Sink Port GE1
PW Info V1-3
2) Set the VLAN operation on the UNI and NNI interfaces of NE3.
Item NE3
The Add Traffic TAG Identification Not Identify
UNI Interface
The Drop TAG Action Delete
Settings
Incremental VLAN-ID at the Drop -
Identify the Drop TAG Identified
NNI Interface
The Add Traffic TAG Action Add
Settings
Incremental VLAN-ID at the Add 601
Note:
For the CiTRANS 610A, you only need to set the traffic classification and
VLAN operation on NNI and UNI interfaces. For the CiTRANS 650, no
configuration of traffic classification and VLAN operation are required.
3) Click Completed to complete the configuration of E-Line service between

NE1↔NE3.
234 Version: B
5. Check and deliver the data to the equipment. For the operation procedures,
see Saving and Delivering Services.
Version: B 235
5 Equipment Maintenance
This chapter introduces the replacement of parts, common operations and handling
method of high temperature issues during the maintenance of equipment.
Replacement of Parts
Daily Operation
Handling High Temperature Issues
236 Version: B
5.1 Replacement of Parts
Replacement of parts refers to the replacement of an equipment or pluggable

optical module during the maintenance or capacity expansion of the equipment.
This operation is performed on the equipment site and requires the support from the
OTNM2000.
5.1.1 Precautions
During capacity expansion or maintenance of equipment, you always need to

replace parts. Improper operations may cause accidents. This section describes the
precautions for replacement of parts.
Table 5-1 describes the precautions for replacement of parts.
Table 5-1 Precautions for Replacement of Parts.
Sequence Precautions
u The new parts and operation tools should be prepared.

u Check whether the label of the outgoing cable of the equipment is
Before the complete. If not, provide additional information.
replacement u Query the related alarms and performance events via the OTNM2000.
u Shut off or disconnect the power supply before replacing the
equipment.
During the u Wear an ESD protection wrist strap or a pair of ESD protection gloves.
replacement u Avoid direct eye exposure to laser beams.
u Ensure that the fibers and cables are properly connected.

u Check the status of indicators on the equipment and ensure that the
equipment is working normally.
After the
u Query the related alarms and performance events via the OTNM2000
replacement
and ensure that there are no abnormal alarms.
u Attach a maintenance label which indicates the fault symptom on the
replaced equipment.
5.1.2 Replacing Equipment
Prerequisite
u You have known about the Precautions.
Version: B 237
u You are an EMS user with "Operator Group" authority or higher.
u The configuration database of the faulty NE has been backed up to the

OTNM2000 server or client end.
u Information about the faulty NE including the version information and database
backup directory has been recorded.
Influence on the System
After the equipment is replaced, you need to restore service configurations from the
backup configuration database. If the configuration database is not backed up in
advance, services must be re-configured.
Precautions
u When you take the equipment from a place with low temperature to a place with
high temperature, condensation occurs on the equipment. In this case, if you
power on the equipment directly, the equipment will be short-circuited.
Therefore, you need to place the equipment in the new place for a period of
time and remove the condensation on the equipment manually.
u Do not operate the equipment while it is powered on. Power off the faulty
equipment before replacing it.
u The laser beam launched through a fiber may cause injuries to eyes. Never
look at the optical interfaces or end face of the optical fibers directly .
u The optical interfaces and patch cord connectors must be kept clean. The fiber
connectors must be installed with anti-dust caps.
Tools
u OTNM2000
u The new equipment to be installed
Procedure
1. The hardware installation engineer takes the new CiTRANS 610A equipment to
the site for replacement. For the details on how to replace the equipment, see
Quick Installation Guide.
238 Version: B
2. Check whether the hardware of the faulty CiTRANS 610A equipment has been
replaced. If so, you can find the new CiTRANS 610A NE in the OTNM2000 via
the SN referring to Configuring NE IP Address Based on SN.
3. Delete the faulty NE in the OTNM2000.
4. Set the IP address of the new NE, which should be the same with that of the
faulty NE.
5. Restore service configurations to the new NE from the backup configuration

database. See e-Fim OTNM2000 Element Management System Manual Set
for specific information.
5.1.3 Replacing a Pluggable Optical Module
Prerequisite
u You have known about the Precautions.
u You are an EMS user with "Maintenance Group" authority or higher.
u See Technical Specifications of Optical Interfaces for the optical modules used
by the CiTRANS 610A.
Influence on the System
Replacement of pluggable optical modules may cause service interruption.
Tools and Instruments
ESD protection bag, ESD protection wrist strap and the OTNM2000
Precautions
Before replacing the pluggable optical module, check the optical power and make
sure that the input / output optical power is within the normal range to avoid
exceeding the overload point which may damage the optical module.
Procedure
1. Prepare a spare part. The model and specifications of the spare part must be
the same as those of the optical module to be replaced. For any mismatch,
contact FiberHome engineers.
Version: B 239
2. Query and record the current alarms of the NE. For details, see Querying
Alarms.
3. Check the optical power and make sure that the input/output optical power is
within the normal range to avoid exceeding the overload point which may
damage the optical module.
4. Notify the on-site maintenance engineers to replace the optical module.

Figure 5-1 and Figure 5-2 show the methods of inserting and removing optical
modules.
Figure 5-1 Removing the Optical Module
Figure 5-2 Inserting the Optical Module
240 Version: B
Caution:
u Before removing an optical module, you need to remove the patch

cords that connect to it.
u No patch cord should be connecting to the optical interfaces when

you insert a new optical module.
u When you insert the new optical module, avoid excessive force;
otherwise, the interface circuit might be damaged.
5. After replacing the optical module, check the Link indicator of the optical
interface. If the Link indicator is in abnormal status, you need to reinsert the
optical module, or replace the optical module again.
6. Query NE alarms in the OTNM2000 and make sure that the original alarms of
the NE are cleared and no new alarms are generated. Check whether the
module is online, and whether the input/output optical power of the module is in
the normal range.
5.2 Daily Operation
This section introduces the common operation items and methods during
maintenance.
5.2.1 Maintenance Worksheet
Maintenance Worksheet
Maintenance Date:
Maintenance Maintenance Maintenance Remark Maintainer
Item Cycle Status
Querying □Normal
Daily
Current Alarms □Abnormal
Querying Alarm □Normal
Daily
History □Abnormal
Querying □Normal
Current Daily
□Abnormal
Performance
Version: B 241
Maintenance Worksheet
Maintenance Date:
Maintenance Maintenance Maintenance Remark Maintainer
Item Cycle Status
Querying □Normal
Performance Daily
□Abnormal
History
Querying the □Normal

OTNM2000's Daily
□Abnormal
Operating Log
Checking the □Normal

Monthly
Indicator Status □Abnormal
Ethernet Port Monthly
□Abnormal
Status
Monthly
Optical Power □Abnormal
Enabling the □Normal
Performance
Annually
Collection □Abnormal
Function
Setting Alarm / □Normal
Performance Annually
□Abnormal
Filter
5.2.2 Querying Alarms
This section introduces how to query alarms in the OTNM2000.
5.2.2.1 Querying Current Alarms
View the current alarms regularly to isolate and eliminate faults in a timely manner.
OTNM2000
242 Version: B
Maintenance Cycle
Daily
Prerequisite
u The OTNM2000 can manage, configure and monitor the entire network
normally.
Procedure
1. Double-click the icon on the network management server desktop

and enter the user name and password to access the OTNM2000 window.
2. Access the current alarm GUI.
4 Query the alarms of a network block or an NE: Right-click the desired

network block or NE in the Logical Tree on the left side of the OTNM2000
GUI, and select Current Alarm from the shortcut menu to bring up the
current alarm GUI.
4 Query the current alarms of a card: Click the XCTR2 card in the subrack
view, and select Current Alarm in the task panel on the right side of the
GUI to bring up the current alarm GUI of the card.
5.2.2.2 Querying Alarm History
The maintenance staff can query the alarm history to get the abnormal data of the
equipment in a specific period of time, so as to facilitate the current maintenance
operations.
OTNM2000
Maintenance Cycle
Daily
Version: B 243
Prerequisite
normally.
Procedure

2. Access the alarm history GUI.
4 Query the alarm history of a network block or an NE: Right-click the

desired network block or NE in the Logical Tree on the left side of the
OTNM2000 GUI, and select Alarm History from the shortcut menu to
bring up the alarm history GUI.
4 Query the alarm history of a card: Click the XCTR2 card in the subrack
view, and select Alarm History in the task panel on the right side of the
GUI to bring up the alarm history GUI of the card.
5.2.3 Enabling the Performance Collection Function
The OTNM2000 only collects the performance history of the NE configured with the
performance collection function. For the performance history of other NEs, you need
to configure the performance collection function for them first.
OTNM2000
Maintenance Cycle
Annually
Prerequisite
244 Version: B
u You have logged into the OTNM2000.
u The time calibration for the OTNM2000 has been completed.
Procedure

2. Select an access method listed in Table 5-2 to open the PM Collection tab as
shown in Figure 5-3.
Table 5-2 Access Methods for Enabling the Performance Collection Function
Item Access Method

Click Performance→Collection Task Settings in the main menu to open the PM Collection
Opening the PM tab.
Collection tab Click Management Tool→Performance Management→Collection Task Settings from the
Operational Tree pane to open the PM Collection tab.
Figure 5-3 Performance Collection
3. In the Operational Tree pane, select the desired NE or network block, and
click Add in the PM Collection tab. The configuration items of the selected NE
or network block will be displayed in the PM Collection tab.
Version: B 245
4. Double-click the From Time and To Time items for the NEs or network blocks
in the PM Collection tab to set the collection time. Select 15-minute
Performance Collection Enable or 24-Hour Performance Collection
Enable.
Note:
The From Time must be later than the current time of the network
management system and the NE.
5. After completing the settings of NE performance collection time, click Save,

and then click OK in the Command Warning alert box that appears to save the
settings.
5.2.4 Querying the Performance
This section introduces how to query the performance in the OTNM2000.
5.2.4.1 Querying Current Performance
By querying the reported performance, you can ascertain whether the equipment is
in normal operation and eliminate silent failures in a timely manner.
OTNM2000
Maintenance Cycle
Daily
Prerequisite
normally.
u The performance collection function is enabled.
246 Version: B
Procedure

2. Access the current performance GUI.
4 Query the current performance of a network block or an NE: Right-click the

OTNM2000 GUI, and select Current Performance from the shortcut
menu to bring up the current performance GUI.
4 Query the current performance of a card: Click the desired card in the
subrack view, and select Performance in the task panel on the right to
bring up the current performance GUI.
5.2.4.2 Querying Performance History
The maintenance staff can obtain the network operation efficiency data by querying
and analyzing the performance history data of the equipment, and predict the future
performance of the network based on the obtained data, providing reference for
further network planning.
OTNM2000
Maintenance Cycle
Daily
Prerequisite
normally.
Version: B 247
Note:
The performance collection function should be enabled on the

OTNM2000 before you can query the performance history.
Procedure

2. Access the performance history GUI.
4 Query the performance history of a network block or an NE: Right-click the

OTNM2000 GUI, and select Performance History from the shortcut menu.
Set the query conditions in the dialog box that appears and click OK to
display the performance history.
4 Query the performance history of a card: Click the corresponding card in

the subrack view, and select History Performance in the task panel on
the right side of the GUI. In the dialog box that appears, set the
performance query conditions and click OK to display the performance
history of the card.
5.2.5 Setting Alarm / Performance Filter
During equipment commissioning and operations, some redundant performance

events or alarms will be generated. Filtering the redundant performance events or
alarms can facilitate the maintenance of the equipment.
OTNM2000
248 Version: B
Prerequisite
normally.
u The operator is knowledgeable of the suppression relationship of alarms.
Procedure

2. Right-click the desired NE and select Configuration→Mask Setting in the

Task Panel pane.
3. Set Filter Mode in the "Filter Settings" pane that appears and select alarm /
performance information to be filtered.
Version: B 249
4. Click Save to the database / Save to the device to save the filter settings.
5.2.6 Querying the OTNM2000's Operating Log
This section introduces the operation methods of querying the OTNM2000's

operating log to check whether there is an abnormal user login or abnormal
operation in the OTNM2000.
Prerequisite
u The OTNM2000 server is powered on and operating normally.
Maintenance Cycle
Daily
250 Version: B
Procedure

2. As shown in Figure 5-4, click Security→View User Log in the main menu to
bring up the View User Log tab.
Figure 5-4 Access Method of Log View GUI
3. View the user logs, as shown in the figure below.
4. Record the check result in the routine maintenance worksheet.
Reference Standard
u No abnormal login records exist.
u No abnormal operation records exist.
Exception Handling
Modify the OTNM2000 login password in a timely manner, and confirm that the
equipment configuration is correct.
Version: B 251
5.2.7 Checking the Indicator Status
Prerequisite
u The OTNM2000 server is powered on and operating normally.
Maintenance Cycle
Monthly
Procedure

2. Check the status of NEs in the Logical Tree pane of the OTNM2000.
4 Normally the icon of an NE is green. If it is of other colors, the NE has

alarms or is abnormal. See the figure below for specific meanings of
different colors of the NE icons.
4 Normally no additional icon appears on the upper right corner of the NE

icon. When an interruption alarm or an alarm which users focus on
appears, an alert icon will appear on the upper right corner of the NE icon.
Figure 5-5 and Figure 5-6 define the icons standing for interruption alarms
and alarms which users focus on.
Figure 5-5 Interruption Alarm Icons
252 Version: B
Note 1: Icons of alarms which users focus on are customized by users. Click Alarm→Alarm
Report Settings in the menu bar of the OTNM2000 to set the alert icons for alarms which
users focus on. When a certain alarm appear on the equipment, the corresponding alarm
icon will be displayed on the upper right corner of the NE icon. When both the interruption
alarm and the alarm which users focus on appear, and the icon of the latter is displayed.
Figure 5-6 Icons of Alarms Which Users Focus On
3. Double-click an NE in the Logical Tree pane to bring up the subrack view.

Check the operating status of cards.
4 Normally the indicator of a card is green. If it is of other colors, the card has
alarms or is abnormal. See the figure below for specific meanings of
different colors of the card indicators.
4 Normally no additional icon appears on the right side of the card indicator.
When an alarm which users focus on appears, the corresponding alarm
Version: B 253
icon will be displayed on the right side of the card indicator. Icons of alarms
which user focus on are shown in the figure below.
Note 1: Icons of alarms which users focus on are customized by users. Click Alarm→Alarm
Report Settings in the menu bar of the OTNM2000 to set the alert icons for alarms which
users focus on. When a certain alarm appear on the card, the corresponding alert icon will
be displayed on the right side of the card indicator.
Reference Standard
The NE icons and card indicators on the OTNM2000 are green and the operating
status of cards is normal.
5.2.8 Checking the Ethernet Port Status
Prerequisite
normally.
254 Version: B
Maintenance Cycle
Monthly
Procedure

2. Select the desired NE and click Task Panel→Status at the right side of the NE
to bring up the NE status pane.
3. Select Port_Status_Info tab in the NE status pane to check the status of the
Ethernet port.
Figure 5-7 Status Information of the Ethernet Port
Reference Standard
The status of the working Ethernet port is Link Up.
Version: B 255
5.2.9 Checking the Optical Power
Prerequisite
normally.
Maintenance Cycle
Monthly
Procedure

2. Right-click the desired NE in the Logical Tree on the left side of the
OTNM2000 GUI, and select Current Performance from the shortcut menu to
bring up the current performance GUI.
3. Make sure that the performance values of input optical power and output
optical power are in a normal range.
4. If the performance values of the laser are not within the specified range, contact
FiberHome engineers for troubleshooting.
Reference Standard
See Technical Specifications of Optical Interfaces for the average transmit and
receive optical power of different optical interfaces.
5.2.10 Testing the LSP 1:1 Protection Switching
Prerequisite
u The OTNM2000 can normally configure, manage, and monitor the entire
network.
256 Version: B
u The LSP 1:1 protection and service have been created. The service is in
normal status without bit errors or packet loss.
u A data analyzer
u LC patch cords or CAT-5 unshielded cross-connect / straight-through cables
u OTNM2000
Connection Diagram
Figure 5-8 Connection of LSP 1:1 Protection Switching Test
Procedure
1. According to Figure 5-8, connect the data analyzer to NE1 and NE2 and set the
test data stream based on service types. Make sure the service is in normal
status.
2. Trigger the protection switching using either of the following two methods.
4 Pulling fiber: Disconnect the optical fiber connection between NE1 and
NE2.
4 Deliver the switching command via the OTNM2000.
Version: B 257
a) Select NE1 or NE2 (on one set of equipment in the protection) in the
Logical Tree and select Control Command in the Task Panel pane
on the right side to bring up the Control Command tab.
b) In the Control Command tab, select LSP_CONTROL and select the

corresponding Command-Type and LSPID. Click the button on
the right side to execute the switching command.
Note 1: Select the desired NE in the OTNM2000 and select Task Panel→Board Configuration
→Tunnel-Table-Config to check the LSPID of the related Tunnel.
Figure 5-9 LSP 1:1 Switching Command
3. Obtain the number of lost packets or bit errors of the service during switching
using the test instrument and calculate the switching time via the number of lost
packets or bit errors / service transmission rate. The switching time should be
less than 50 ms.
4 If the service is switched successfully, ➔ Step 4.
4 If the service switching fails, contact FiberHome engineers for

troubleshooting.
4. In the OTNM2000, click Task Panel→Alarm→Current Alarm on the right side

of the NE to view the current alarms of NE1 and NE2.
Note:
The switching alarms (SWR and MANUAL_SWITCH) and OAM alarms

(VP_LOC and VP_RDI) occur, and the OAM alarms occur only in the
fiber pulling mode.
258 Version: B
5. Test the switched service for 10 minutes using the data analyzer, so as to
check the protection path performance in the switching status.
4 If the test result shows no packet loss and no errors, ➔ Step 6.
4 If the test result shows packet loss and errors, contact FiberHome
engineers for troubleshooting till the test result shows no packet loss and
no errors.
6. Restore the working path (select the method to restore the working service path
according to the method used in Step 2).
4 Fiber pulling mode: Recover the fiber connection between NE1 and NE2. If
the return type is set to non-revertive, you need to set the path according
to the command described in Step 2, and deliver the Restore-Main
command to the LSP protection to return the service to the active LSP.
4 Command delivery mode: Set the path according the command described
in Step 2, and deliver the Restore-Main command to the LSP protection.
7. Wait until the switching and restoration are completed (five minutes by default).
In the OTNM2000, check the current alarms of the XCTR2 cards of NE1 and
NE2.
4 If the MANUAL_SWITCH alarm occurs and there is no OAM alarms

(VP_LOC and VP_RDI), it is a normal condition.
4 If other alarms occur, it is an abnormal condition. You need to contact

FiberHome engineers for troubleshooting according to the displayed
alarms until the alarms disappear.
8. Complete the switching protection test for each station in the entire network
according to the steps 1 to 8.
Version: B 259
Subsequent Handling
Disconnect the test connection and clear up the testing environment after the test is
completed.
5.2.11 Testing the PW 1:1 Protection Switching
Prerequisite
u The OTNM2000 can normally configure, manage, and monitor the entire
network.
u The PW 1:1 protection and service configuration have been completed.
u A data analyzer
u LC patch cords or CAT-5 unshielded cross-connect / straight-through cables
u OTNM2000
Connection Diagram
The figure below shows the connection of the protection switching test.
u A GE service is configured between NE1 and NE3. The network and port
planning are shown in the figure below. Assuming that the service UNI
interfaces of NE1 and NE3 are connected with the port 1 and port 3 of the
analyzer respectively.
u The active and standby PW paths corresponding to the service are configured
with the PW 1:1 protection. The active PW path of the protection is
NE1↔NE4↔NE3, and the standby PW path is NE1↔NE2↔NE3.
260 Version: B
Figure 5-10 Connection of PW 1:1 Protection Switching Test
Procedure
1. Connect the test instrument according to the above figure. Configure the
bidirectional data stream between port 1 and port 3 (port 1→port 3 and port
3→port 1). The stream should be in normal status without packet loss. Query
the current alarms of the NE. No alarms related to protection switching should
be reported.
2. Trigger the protection switching using either of the following two methods.
4 Fiber pulling mode: Disconnect the optical fiber on the active PW path (for
example, disconnect the fiber connection between NE1 and NE4, either Tx
fiber or Rx fiber).
4 Deliver the switching command via the OTNM2000.
a) Select NE1 or NE3 (on one set of equipment in the protection) in the
Logical Tree and select Control Command in the Task Panel pane
on the right side to bring up the Control Command tab.
b) In the Control Command tab, select VC_CONTROL and select the

corresponding Command-Type and TCM_Protection_ID. Click the
button on the right side to execute the switching command.
Version: B 261
Note 1: Select the desired NE in the OTNM2000 and select Task Panel→Board Configuration
→PW-Config to check the PW-ID of the related PW.
Figure 5-11 PW 1:1 Switching Command
3. Obtain the number of lost packets or bit errors of the service during switching
using the test instrument and calculate the switching time via the number of lost
packets or bit errors / service transmission rate. The switching time should be
less than 50 ms.
4 If the service is switched successfully, ➔ Step 4.
4 If the service switching fails, contact FiberHome engineers for

troubleshooting.
4. Query the current alarms of the corresponding NE after the switching.
Note:
u Trigger switching using the fiber pulling mode: the switching alarm
(SWR) and OAM alarms (VC_LOC and VC_RDI) will occur on NE1
and NE3. The LINK_LOS alarm will occur on the line interface of
NE4.
u Trigger switching via delivering control command: the switching

alarms (SWR and MANUAL_SWITCH) will occur on the XCTR2
cards of NE1 and NE3.
262 Version: B
5. Test the switched service for 10 minutes using the data analyzer, so as to
check the protection path performance in the switching status.
4 If the test result shows no packet loss and no errors, ➔ Step 6.
4 If the test result shows packet loss and errors, contact FiberHome
engineers for troubleshooting.
6. Restore the working path (select the method to restore the working service path
according to the method used in Step 2).
4 Fiber pulling mode: Recover the fiber connection between NE1 and NE4. If
the return type is set to non-revertive, you need to set the path according
to the command described in Step 2, and deliver the Restore-Main
command to the PW protection to return the service to the active PW.
4 Command delivery mode: Set the path according the command described
in Step 2, and deliver the Restore-Main command to the PW protection.
7. Wait until the switching and restoration are completed (five minutes by default).
In the OTNM2000, check the current alarms of the XCTR2 cards of NE1 and
NE3.
4 If the MANUAL_SWITCH alarm occurs and there is no OAM alarms

(VC_LOC and VC_RDI), it is a normal condition. ➔ Step 8.
4 If other alarms occur, it is an abnormal condition. You need to eliminate the

fault according to the displayed alarm referring to Fault and Alarm
Handling until the alarms disappear.
8. Complete the switching protection test for each station in the entire network
according to the steps 1 to 7.
Subsequent Handling
Disconnect the test connection and clear up the testing environment after the test is
completed.
Version: B 263
5.2.12 Powering on the Equipment
Prerequisite
The external power supply has been connected.
A screwdriver
Precautions
u Do not insert or remove any power plugs when the power is on.
u Wear an ESD protection wrist strap during operations.
Procedure
1. Make sure that the power voltage is sufficient to the equipment so as to avoid
excessively high voltage damaging the equipment.
2. Check the power cable of the equipment. Make sure that the power cable is
correctly connected to the AC/DC power input interface of the equipment.
3. Turn on the external power supply.
4. Turn on the automatic circuit breaker of the AC/DC power supply.
5. Observe the PWR indicator on the equipment. ON indicates that the power
supply is in normal status.
5.2.13 Powering off the Equipment
Precautions
u Do not insert or remove any power plugs when the power is on.
u If the equipment is powered off, it stops running and all the services on this
equipment will be interrupted.
Procedure
1. Turn off the automatic circuit breaker of AC/DC power supply, and confirm that
indicators on the equipment are off.
264 Version: B
2. Turn off the external power supply.
5.3 Handling High Temperature Issues
The high temperature issues have severe influence on the network running. This
section introduces the cause, impact, solution and preventive measures of the high
temperature issues.
5.3.1 Impact and Cause of High Temperature Issues
The high temperature increases the failure rate and reduces the lifetime of an
equipment, increasing the OPEX. The high temperature also leads to noise which is
harmful to human body.
Impact of High Temperature Issues
Increasing failure rate of equipment: Failure rate refers to the inherent failure
probability of a component in its lifetime. Within its working temperature, the failure
rate is stable. However, if the working temperature is excessively high, the failure
rate increases exponentially with the increase of temperature.
Cause of High Temperature Issues
The high temperature issues may be caused by installation or maintenance.
u Installation
4 When the equipment is installed on roofs or in weak current wells, the

ambient temperature rises with the outside temperature.
4 The equipment is installed in closed environments, such as closed

cabinets or battery compartment, causing poor heat dissipation.
u Maintenance
4 The heat vents of the equipment are not cleaned regularly.
4 The air conditioner in the equipment room is faulty or powered off and is
not handled in a timely manner.
Version: B 265
5.3.2 Solution and Preventive Measures for High

Temperature Issues
Solution
u Solution to Improving Equipment Installation
4 It is advisable to install the equipment in an equipment room equipped with

air conditioners.
4 It is advisable to use the outdoor cabinet when installing the case-shaped

equipment in an outdoor environment.
u Solution to Improving Equipment Maintenance
4 Clean the equipment regularly to prevent the heat vents from being
blocked and ensure the heat dissipation of the equipment.
4 Repair the air conditioner in a timely manner when it is faulty or powered

off.
Preventive Measures
Perform the following operations to check the faults of the risky NEs.
1. Check whether the air conditioners work properly. If not, repair the air
conditioners.
2. Check whether the equipment room temperature is lower than 45°C. If not,
lower the temperature and ensure the temperature is lower than 45°C.
3. Check whether the heat ducts of the equipment are blocked. If yes, clean the
heat ducts.
266 Version: B
Appendix A Abbreviations
AC Attachment Circuit
APS Automatic Protection Switching
BC Boundary Clock
BFD Bidirectional Forwarding Detection
BMC Best Master Clock

BSC Base Station Controller
BTS Base Transceiver Station
CAR Committed Access Rate
CAS Channel Associated Signaling
CBS Committed Burst Size

CC Continuity Check
CCS Common Channel Signaling
CE Carrier Ethernet
CE Customer Edge
CES Circuit Emulation Service

CIR Committed Information Rate
CoS Class of Service
CPE Customer Premise Equipment
CRC Cyclic Redundancy Check
DCC Data Communication Channel

DCM Dispersion Compensation Module
DCN Digital Communication Network
DDF Digital Distribution Frame
DiffServ Differentiated Services

DSLAM Digital Subscriber Line Access Multiplexer
ECMP Equal-Cost Multi-Path
E-LAN Ethernet Local Area Network

EMC Electromagnetic Compatibility
EMI Electromagnetic Interference
ESC Electrical Supervisory Channel
ESD Electrostatic Discharge
ETSI European Telecommunications Standards Institute
EVC Ethernet Virtual Connection
Version: B 267
FC Fiber Channel
FCS Frame Check Sequence
FE Fast Ethernet
FEC Forward Error Correction
FPGA Field-Programmable Gate Array
FTTH Fiber To The Home

GE Gigabit Ethernet
GMC Grandmaster Clock

GPS Global Positioning System
GUI Graphical User Interface
HDB3 High Density Bipolar 3 Code
IC Integrated Circuit
IEEE Institute of Electrical and Electronics Engineers
IP Internet Protocol
IPTV Internet Protocol Television
ISO International Standardization Organization
ITU International Telecommunication Union

International Telecommunication Union - Telecommunication
ITU-T
Standardization Sector
LACP Link Aggregation Control Protocol
LAG Link Aggregation Group
LSP Label Switched Path

LSR Label Switching Router
MAC Media Access Control

MCC Management Communication Channel
MCN Management Communication Network
MDF Main Distribution Frame

ME Maintenance Entity
MEG Maintenance Entity Group
MEN Metropolitan Ethernet
MEP Maintenance End Point

MIB Management Information Base
MIMO Multiple-Input Multiple-Out-put
MIP Maintenance Intermediate Point

MME Mobility Management Entity
MPLS Multi-Protocol Label Switching
MPLS-TP Multi-Protocol Label Switching-Transport Profile
268 Version: B
Appendix A Abbreviations
MSAN Multi-Service Access Network

MSP Multiplex Section Protection
MSTP Multi-Service Transfer Platform

MTU Maximum Transmission Unit
NDF New Data Flag
NNI Network Node Interface

NTP Network Time Protocol
OAM Operation, Administration and Maintenance
OC Ordinary Clock
OLT Optical Line Terminal
OSC Optical Supervisory Channel
OSI Open System Interconnection
OSPF Open Shortest Path First
P Provider
PBS Peak Burst Size
PBT Provider Backbone Transport
PDP Power Distribution Panel

PE Provider Edge
PHB Per-Hop Behavior
PHP Penultimate Hop Popping
PIR Peak Information Rate

PON Passive Optical Network
POP PoP Point of Presence

PPS Pulse Per Second
PRC Primary Reference Clock
PTP Precision Time Protocol

PW Pseudo Wire
PWE3 Pseudo Wire Emulation Edge-to-Edge
QoS Quality of Service
RAN Radio Access Network

RDI Remote Defect Indication
RFC Request for Comments
RNC Radio Network Controller

RPR Resilient Packet Ring
RSVP Resource Reservation Protocol

RTP Real-time Transport Protocol
SCC Signaling Communication Channel
Version: B 269
SCN Signaling Communication Network
SES Severely Errored Second
SFP Small Form-Factor Pluggable
SGW Signaling Gateway
SNCP Sub-Network Connection Protection

SONET Synchronous Optical Network
SN Serial Number
SNMP Simple Network Management Protocol
SP Strict Priority
SSM Synchronization Status Message
TC Transparent Clock
TCO Total Cost of Ownership
TCP Transmission Control Protocol

TDM Time Division Multiplexing
TMC T-MPLS Channel

TMP T-MPLS Path
TMP Transmission Maintenance Point
TMN Telecommunication Management Network
TNC Threaded Neill-Concelman

TOD Time of Day
TPID Tag Protocol Identifier
UAS Unavailable Second

UNI User Network Interface
UPS Uninterruptible Power Supply
VC Virtual Channel
VLAN Virtual Local Area Network
VoIP Voice over Internet Protocol
VPLS Virtual Private LAN Service
VP Virtual Path
VPN Virtual Private Network
VPWS Virtual Private Wire Service
VSI Virtual Switching Instance
WiMAX Worldwide Interoperability for Microwave Access
WFQ Weighted Fair Queuing
WRED Weighted Random Early Detection
270 Version: B
Product Documentation Customer Satisfaction Survey
Thank you for reading and using the product documentation provided by FiberHome. Please take a moment to
complete this survey. Your answers will help us to improve the documentation and better suit your needs. Your
responses will be confidential and given serious consideration. The personal information requested is used for
no other purposes than to respond to your feedback.
Name
Phone Number
Email Address
Company
To help us better understand your needs, please focus your answers on a single documentation or a complete
documentation set.
Documentation Name
Code and Version
Usage of the product documentation:

1. How often do you use the documentation?
□ Frequently □ Rarely □ Never □ Other (please specify)
2. When do you use the documentation?
□ in starting up a project □ in installing the product □ in daily maintenance □ in trouble
shooting □ Other (please specify)
3. What is the percentage of the operations on the product for which you can get instruction from the
documentation?
□ 100% □ 80% □ 50% □ 0% □ Other (please specify)
4. Are you satisfied with the promptness with which we update the documentation?
□ Satisfied □ Unsatisfied (your advice)
5. Which documentation form do you prefer?
□ Print edition □ Electronic edition □ Other (please specify)
Quality of the product documentation:
1. Is the information organized and presented clearly?
□ Very □ Somewhat □ Not at all (your advice)
2. How do you like the language style of the documentation?
□ Good □ Normal □ Poor (please specify)
3. Are any contents in the documentation inconsistent with the product?
4. Is the information complete in the documentation?
□ Yes
□ No (Please specify)
5. Are the product working principles and the relevant technologies covered in the documentation sufficient for
you to get known and use the product?
□ Yes
□ No (Please specify)
6. Can you successfully implement a task following the operation steps given in the documentation?
□ Yes (Please give an example)
□ No (Please specify the reason)
7. Which parts of the documentation are you satisfied with?
8. Which parts of the documentation are you unsatisfied with?Why?
9. What is your opinion on the Figures in the documentation?
□ Beautiful □ Unbeautiful (your advice)
□ Practical □ Unpractical (your advice)
10. What is your opinion on the layout of the documentation?

□ Beautiful □ Unbeautiful (your advice)
11. Thinking of the documentations you have ever read offered by other companies, how would you compare
our documentation to them?
Product documentations from other companies:
Satisfied (please specify)
Unsatisfied (please specify)
12. Additional comments about our documentation or suggestions on how we can improve:
Thank you for your assistance. Please fax or send the completed survey to us at the contact information
included in the documentation. If you have any questions or concerns about this survey please email at
edit@fiberhome.com

CiTRANS 610A Packet Transfer Platform User Manual

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

CiTRANS 610A Packet Transfer Platform User Manual

Загружено:

Авторское право:

Доступные форматы

CiTRANS 610A

Packet Transfer Platform

FiberHome Telecommunication Technologies Co., Ltd.

We appreciate your business. Your satisfaction is our goal.

Fiberhome Telecommunication Technologies Co., Ltd.

Address: No. 67, Guanggu Chuangye Jie, Wuhan, Hubei, China

are trademarks of FiberHome Telecommunication Technologies Co., Ltd.

All rights reserved

No part of this document (including the electronic version) may be

Includes the chapters such as product description, hardware

CiTRANS 610A Packet

This manual is intended for the following readers:

u Planning and designing engineers

u Operation and maintenance engineers

To utilize this manual, these prerequisite skills are necessary:

u MPLS-TP related technology

u Data communication technology

CiTRANS 610A FiberHome CiTRANS 610A Packet Transfer Platform

Symbol Convention Description

Note Important features or operation guide.

Possible injury to persons or systems, or cause traffic

Warning May cause severe bodily injuries.

➔ Jump Jumps to another step.

Related Documentation ...................................................................................I

Intended Readers ..........................................................................................III

1 Product Description ........................................................................................1

1.1 Product Application...........................................................................2

1.2 List of Product Features ....................................................................4

1.3 Technical Specifications....................................................................5

1.3.1 Dimensions and Weight ......................................................6

1.4 Standards and Protocols...................................................................9

1.4.1 International Standards .....................................................10

1.5 Environment Requirements.............................................................18

1.5.1 Operating Environment .....................................................19

2.1 Appearance and Structure ..............................................................26

2.2 Panel Description ...........................................................................28

2.3 Safety Signs ...................................................................................30

2.4 Pluggable Optical Modules..............................................................31

2.5 Optical Fibers and Cables ...............................................................34

2.5.1 Patch Cord .......................................................................34

2.6 Mounting Ears ................................................................................45

3 Equipment Commissioning ...........................................................................47

3.1 Commissioning Flow.......................................................................48

3.2 Creating Network Topology .............................................................50

3.2.1 Connecting the EMS and the Equipment ...........................50

3.3 Testing the NE Connectivity ............................................................80

3.4 Performing Time Calibration and Downloading Configuration...........81

4.1 Configuring Interfaces.....................................................................85

4.1.1 Basic Concepts and Configuration Rules of Interfaces.......85

4.2 Configuring Tunnels and Tunnel Protection .....................................95

4.2.1 Basic Concepts and Configuration Rules of Tunnels..........95

4.3 Configuring PWs and PW Protection ............................................. 118

4.3.1 Basic Concepts and Configuration Rules of PWs............. 118

4.4 Configuring Ethernet Services.......................................................132

4.4.1 Basic Concepts and Configuration Rules of Ethernet

4.5 Configuring CES Services.............................................................181

4.5.1 Basic Concepts and Configuration Rules of CES.............181

4.6 Saving and Delivering Services.....................................................189

4.7 Configuring Clock Synchronization................................................193

4.7.1 Basic Concepts and Configuration Rules of Clock

4.8 Configuring MTU...........................................................................200

4.9 Configuring QoS ...........................................................................203

4.10 Configuring Typical Scenarios .......................................................217

4.10.1 Introduction to Service Model ..........................................217