Manual 6120s

ZXCTN 6120S
Product Description
Version: V3.00
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2014 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2014-06-30 ZXCTN 6120S(V3.00) Product Description Issued.
Serial Number: SJ-20140603170741-014
Publishing Date: 2014-06-30(R1.0)
SJ-20140603170741-014|2014-06-30(R1.0) ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
1.1 Overview .......................................................................................................... 1-1
1.2 Product Positioning ........................................................................................... 1-1
1.3 Product Features................................................................................................ 1-2
Chapter 2 Architecture............................................................................... 2-1

2.1 Logical Structure ............................................................................................... 2-1
2.2 Hardware Structure ........................................................................................... 2-3
2.3 Software Structure.............................................................................................. 2-3
Chapter 3 Services ..................................................................................... 3-1

3.1 Service Flow ...................................................................................................... 3-1
3.2 Service Processing Capacity............................................................................... 3-2
Chapter 4 Functions................................................................................... 4-1

4.1 MPLS-TP Function ............................................................................................ 4-1
4.2 MPLS ................................................................................................................ 4-2
4.2.1 Basic MPLS Protocols .............................................................................. 4-2
4.2.2 MPLS L2VPN........................................................................................... 4-3
4.2.3 BGP/MPLS L3VPN................................................................................... 4-6
4.3 L2 .................................................................................................................. 4-10
4.4 L3 .................................................................................................................. 4-12
4.5 OAM Function.................................................................................................. 4-12
4.5.1 MPLS-TP OAM Functions....................................................................... 4-13
4.5.2 MPLS OAM Function.............................................................................. 4-14
4.5.3 Ethernet OAM Functions......................................................................... 4-15
4.6 QoS Function................................................................................................... 4-18
4.7 Clock and Time ............................................................................................... 4-20
4.7.1 IEEE 1588 V2 Application ....................................................................... 4-21
4.7.2 IEEE 1588 ACR Application .................................................................... 4-23
4.7.3 Synchronous Ethernet Application ........................................................... 4-24
4.8 Safety and Reliability ........................................................................................ 4-25
4.8.1 Business Security................................................................................... 4-25
4.8.2 Equipment Security ................................................................................ 4-26
4.8.3 Authentication Management.................................................................... 4-27

4.8.4 User Authority Management.................................................................... 4-28
Chapter 5 Protection .................................................................................. 5-1

5.1 Equipment-Level Protection ................................................................................ 5-1
5.2 Network-Layer Protection.................................................................................... 5-2
5.2.1 MPLS-TP Static Tunneling Protection ........................................................ 5-2
5.2.2 Wrapping Protection ................................................................................. 5-4
5.2.3 Shared Ring Protection............................................................................. 5-5
5.2.4 Double-loop Dual-node Protection ............................................................. 5-5
5.2.5 PW Protection.......................................................................................... 5-6
5.2.6 MPLS Protection ...................................................................................... 5-8
5.2.7 FRR Protection ........................................................................................ 5-9
5.2.8 RSVP-TE Path-Option Protection ............................................................ 5-15
5.2.9 RSVP-TE Hot-Standby Protection ........................................................... 5-15
5.2.10 LAG Protection..................................................................................... 5-16
5.2.11 STP ..................................................................................................... 5-17
Chapter 6 Interfaces ................................................................................... 6-1

6.1 Board Service Interfaces..................................................................................... 6-1
6.2 External Interfaces ............................................................................................. 6-1
Chapter 7 Networking Applications.......................................................... 7-1

7.1 Service Networking Application ........................................................................... 7-1
7.1.1 MPLS L2 VPN Application ........................................................................ 7-1
7.1.2 TDM Service Networking Application ......................................................... 7-7
7.2 Integrated Solutions ........................................................................................... 7-8
7.2.1 Mobile Backhaul....................................................................................... 7-8
7.2.2 Application at LTE Network Stage.............................................................. 7-9
Chapter 8 Technical Specifications .......................................................... 8-1

8.1 System Performance .......................................................................................... 8-1
8.2 Physical Performance......................................................................................... 8-3
8.3 Power Consumption Specifications...................................................................... 8-4
8.4 Grounding Requirements .................................................................................... 8-4
8.5 Lightning Protection Requirements ...................................................................... 8-7
8.6 EMC Requirements ............................................................................................ 8-8
8.7 Reliability Specifications .................................................................................... 8-9
8.8 Security Authentication Requirement ................................................................... 8-9
8.9 Interface Specifications..................................................................................... 8-10
Chapter 9 Environment Requirements ..................................................... 9-1
II

9.1 Power Supply Requirements ............................................................................... 9-1
9.2 Operation Environment ...................................................................................... 9-1
9.3 Transportation Environment ................................................................................ 9-3
9.4 Storage Environment.......................................................................................... 9-5
Appendix A Standards and Recommendations ..................................... A-1

List of Figure................................................................................................... I
List of Table................................................................................................... III
Glossary .........................................................................................................V
III

This page intentionally left blank.
IV

About This Manual
Purpose
This manual provides information about the Unitrans ZXCTN 6120S (hereafter referred to
as ZXCTN 6120S).
Intended Audience
This manual is intended for:
l Maintenance engineers
l Network management personnel
What Is in This Manual

This manual contains the following chapters and appendix.
Chapter 1, Overview Describes an external view, features and position of the ZXCTN 6120S
in the network.
Chapter 2, Architecture Describes the logical, hardware and software architectures of the
ZXCTN 6120S.
Chapter 3, Services Describes the service flow and service processing capability of the
ZXCTN 6120S.
Chapter 4, Functions Describes the functions of the ZXCTN 6120S, including the MPLS-TP,
MPLS, L2, L3, OAM, QoS, clock and time, security and reliability,
microwave functions.
Chapter 5, Protection Describes the equipment level,, network side, and network edge
protections supported by the ZXCTN 6120S.
Chapter 6, Interfaces Describes the board service interfaces and external interfaces of the
ZXCTN 6120S.
Chapter 7, Networking Describes service network applications and integrated solutions of the
Applications ZXCTN 6120S.
Chapter 8, Technical Describes the technical specifications of the ZXCTN 6120S, including
Specifications system performance, physical performance, power consumption index,
grounding requirements, lightning-proof requirements, electromagnetic
compatibility requirements, reliability specifications, and interface
specifications.
Chapter 9, Environment Describes the environment requirements of the ZXCTN 6120S.

Requirements
Appendix A, Standards Describes the standards and recommendations that the ZXCTN 6120S
and Recommendations complies with.

Conventions
This manual uses the following conventions.
Caution: indicates a potentially hazardous situation. Failure to comply

can result in serious injury, equipment damage, or interruption of major
services.
Note: provides additional information about a topic.
II

Chapter 1
Overview
Table of Contents
Overview ...................................................................................................................1-1
Product Positioning ...................................................................................................1-1
Product Features........................................................................................................1-2
1.1 Overview
The ZXCTN 6120S is a carrier-class multi-service bearer product. It is dedicated to
carrying and transmitting services in an integrated mobile backhaul and multi-service
network.
For the overview of the ZXCTN 6120S, see Figure 1-1.
Figure 1-1 ZXCTN 6120S Overview
1.2 Product Positioning

The ZXCTN 6120S is located at the access layer of the metropolitan area network. For
the network application of the ZXCTN 6120S, see Figure 1-2.
1-1

ZXCTN 6120S Product Description
Figure 1-2 Network Application of the ZXCTN 6120S
1.3 Product Features

The ZXCTN 6120S has the following features:
Unified Bearer Platform

l Uses an all-packet architecture and the optimized connection-oriented Multi-Protocol
Label Switching Transport Profile (MPLS-TP) technology.
l Supports multi-service bearing through Pseudo Wire Emulation Edge-to-Edge
(PWE3) to meet the requirements for the full service development.
Synchronous Network
l Uses the G.8261 and 1588 V2 technologies to implement the accurate insertion and
extraction of timestamps in the 1588 protocol, which improves the accuracy of time
synchronization.
l Supports the Circuit Emulation Service (CES) clock transmission function and IEEE
1588 V2 Adaptive Clock Recovery (ACR) clock transparent transmission function.
l Supports flexible configuration of the boundary clock and transparent transmission
clock, out-of-band 1 Pulse Per Second (PPS) + Time of Delivery (ToD) interfaces,
and in-band synchronous Ethernet interfaces.
l Supports the synchronous Ethernet networking application. Each NE can be locked
to the same clock source, thus accomplishing synchronization in the entire network.
1-2

Chapter 1 Overview
l Uses the Synchronization Status Message (SSM) protocol and Best Master Clock
(BMC) algorithm to implement the automatic protection switching of the clock and
time link, to guarantee reliable transmission of synchronous signals.
End-to-End QoS
l Provides the end-to-end Quality of Service (QoS) management function to satisfy the
requirements of various services for the delay, jitter, and bandwidth.
l Supports the Differentiated Service (DS)-based QoS scheduling.
l Implements traffic classification and labeling according to the port, Virtual Local Area
Network (VLAN), 802.1p, Differentiated Services Code Point (DSCP)/Type of Service
(ToS), Medium Access Control (MAC), and Internet Protocol (IP) address.
l Supports traffic monitoring, queue scheduling, congestion control, and traffic
shaping to control the user-level multi-service bandwidth and guarantees customer’s
refinement operation.
IP/MPLS and MPLS-TP Dual-Stack Protocol

l ZXCTN 6120SUses the same hardware platform to support the IP/MPLS and
MPLS-TP dual-stack protocol and accommodate traditional transmission and data
networks.
l Flexibly applies to the development of various standards, reduces the technology
selection risk, and provides long-term support for the evaluation of the service
network.
Hierarchical OAM
l Supports MPLS-TP Operation, Administration and Maintenance (OAM), Ethernet
OAM, and Multi Protocol Label Switching (MPLS) OAM.
l Uses the hierarchical monitoring OAM mode based on hardware to implement
fast fault detection and location, performance monitoring, and end-to-end service
management.
l Supports active and on-demand OAM, and ensures carrier-class service quality in the
packet transport network.
l Supports various hierarchical OAM based on the logical link, Pseudo Wire (PW),
tunnel, and section, which makes the network operation and management more
transparent and convenient.
Protection Mechanism
The ZXCTN 6120S provides complete equipment-level protection, network-side
protection, and client-side protection.
l Supports the following types of equipment-level protection:
à 1+1 hot backup protection of the main boards.
à 1+1 hot backup protection of the DC power boards.
l Supports the following types of network-side protection:
1-3

à Link Aggregation Group (LAG) protection

à FRR protection, including IP FRR, LDP FRR and RSVP-TE FRR.
à Label Switched Path (LSP) protection based on MPLS-TP
à Wrapping protection based on MPLS-TP
à Dual-ring and dual-node protection based on MPLS-TP
à PW protection based on MPLS-TP, including PW dual-homing protection and
MS-PW protection
à Hot-standby protection based on RSVP-TE
à Path-Option protection based on RSVP-TE
à Spanning Tree Protocol (STP) protection based on Ethernet
l Supports client-side Link Aggregation Group (LAG) protection.
Compatibility
l Uses the open technical platform to accommodate traditional transmission and data
networks.
l Uses flexible system design, which applies to the development of various transmission
standards and supports the evolution of the service network.
Unified Network Management System

Uses the ZTE unified network management system NetNumen U31 R22 for management.
1-4

Chapter 2
Architecture
Table of Contents
Logical Structure .......................................................................................................2-1
Hardware Structure ...................................................................................................2-3
Software Structure......................................................................................................2-3
2.1 Logical Structure

Functional units of the ZXCTN 6120S include a service interface unit, service adaptation
unit, service switching unit, main control/clock unit, system interface unit, power supply
unit, and heat dissipation unit.
For the functional units of the ZXCTN 6120S, see Figure 2-1.
Figure 2-1 Functional Units of the ZXCTN 6120S
Service Interface Unit

It provides the following interfaces:
l Time Division Multiplexing (TDM) E1 interface

l Fast Ethernet (FE) optical/electrical interface
2-1

l Gigabit Ethernet (GE) optical/electrical interface

l 10GE optical interface
Service Adaptation Unit

It adapts various services by using the PWE3 technology.
Service Switching Unit

It implements packet switching and transfers data between different service processing
units.
Main Control/Clock Unit

l Main control unit: It is the core unit of the system and implements functions on the
management plane and control plane. Physically, the main control unit transfers
management and control information via the Ethernet communication network
between units.
à Management plane functions
Implements configuration, management, and maintenance for each board of the
system.
à Control plane functions
Implements protocol processing, alarm processing, and switching decision.
l Clock unit: It provides clock signals for boards, and implements 1588 time
synchronization.
System Interface Unit

It provides the following interfaces:
l Clock/time
l Alarm
l EMS
l Local Craft Terminal (LCT)
Power Supply Unit

It provides power to all boards. It supports lightning surge protection, filtering, inverse
connection protection, over-current protection, and 1+1 active/standby power supply
protection.
Heat Dissipation Unit

It consists of a fan module and a monitoring unit, providing forcible heat dissipation. The
fan speed can be intelligently adjusted according to the system temperature.
2-2

Chapter 2 Architecture
2.2 Hardware Structure

For the hardware structure of the ZXCTN 6120S, see Figure 2-2.
Figure 2-2 Hardware Structure of the ZXCTN 6120S
1. Power board area 3. Antistatic wrist strap jack

2. Board area 4. Fan area
For the subrack structure description of the ZXCTN 6120S, refer to Table 2-1.
Table 2-1 Subrack Structure Description of the ZXCTN 6120S
Serial Component Description

No.
1 Power board area The power board is inserted here to supply power to the
equipment.
2 Board area The system main board and the service boards are inserted
here. Among them, the main control board provides the control,
switching and clock processing of the system and the service
boards provides external service interfaces.
3 Antistatic wrist strap The antistatic wrist strap is inserted here.

jack
4 Fan area It is inserted in the fan module and dissipates the heat of the
subrack.
2.3 Software Structure

The software structure of the ZXCTN 6120S can be divided into the following three planes:
l Management plane
l Control plane
l Data plane
2-3

The ZXCTN 6120S system software uses layered structure design with each layer
implementing specific function and providing service to the upper layer. For the software
structure of the ZXCTN 6120S, see Figure 2-3.
Figure 2-3 Software Structure Diagram
Main Control Software Structure

For the structure of the main control software of the ZXCTN 6120S, see Figure 2-4.
Figure 2-4 Structure of ZXCTN 6120S Main Control Software
2-4

Chapter 2 Architecture
l Platform OAM sub-system: responsible for inter-communication between the platform

management interfaces (such as CLI/SNMP/TELNET) and service management
module, meanwhile, it responsible for save and restoration of part of EMS log and
configuration data.
l EMS management module: implements the inter-communication between the
EMS interface and service management module, meanwhile, it implements EMS
management, alarm and performance management, EMS data saving, upload and
download.
l DCN module: unified manages the establishment and maintenance of signalling path.
l Service management module: manages the service configuration, meanwhile
performs the inter-communication between protocol and supporting module.
l IP protocol module: includes TCP/IP protocol of platform and the operating system
itself.
l L2/L3 protocol module: L2/L3 protocol of platform
l OAM and protection module: includes OAM protocol and relevant protocols based on
MPLS-TP, MPLS and Ethernet.
l Supporting module: performs the inter-communication between service management
module, protocol stack module, OAM and protection module, and driving module.
l Driving module: configures the chip directly.
Board Software Structure

For the structure of board software of the ZXCTN 6120S, see Figure 2-5.
Figure 2-5 Structure of Board Software
l Board agent program: implements the inter-communication within the main control
board.
l Service processing module: implements the service configuration and
alarm&performance processing.
l IP protocol stack module: applicable to gateway NE boards.
l Supporting module: implements the inter-communication between the service
processing module, IP protocol stack module, special protocol module for board
running and driving module.
2-5

l Driving module: implements the configuration for the chip.
2-6

Chapter 3
Services
Table of Contents
Service Flow ..............................................................................................................3-1
Service Processing Capacity ......................................................................................3-2
3.1 Service Flow

For the service low of the ZXCTN 6120S, see Figure 3-1.
Figure 3-1 Service Flow of the ZXCTN 6120S
1. The ZXCTN 6120S connects Ethernet services and TDM services of CE devices
through UNI interfaces.
2. The ZXCTN 6120S adapts the connected services and converts them to the Ethernet
message format on the NNI side for transmission.
Physical Interface Layer

The physical interface layer provides external physical interfaces and receives/sends user
services.
Service Processing Layer

The service processing layer processes different services in accordance with different
service types and rules.
3-1

l For Ethernet services, this layer

à Processes the clock, OAM, and QoS.
à Determines the Matrix Flow Domain Fragment (MFDFr) in accordance with UNI
or UNI+CE VLAN.
l For TDM services, this layer
à Processes structured or unstructured simulations.
à Encapsulates/decapsulates TDM services into/from packet services based on
encapsulation delay.
à Uploads or downloads packet services to corresponding PWs or tunnels.
PW Processing Layer
l The PW processing layer encapsulates services into PWE3 packets.
l The PW processing layer decapsulates PWE3 packets to restore services.
l The PW processing layer identifies services through PW labels. Each service
corresponds to a unique PW label, that is, one service can only correspond to one
PW.
Tunnel Processing Layer

The tunnel processing layer provides paths for forwarding packet services. One tunnel
can carry multiple PWs, which are distinguished by PW labels.
Link Transport Layer

The link transport layer provides data links for the tunnel processing layer and transports
user services.
3.2 Service Processing Capacity

For the service processing capability of the ZXCTN 6120S, refer to Table 3-1.
Table 3-1 ZXCTN 6120S Service Processing Capability
Backplane Capacity Switching Capacity Packet Forwarding Rate
80 Gbps 60 Gbps 68.5 Mpps
3-2

Chapter 4
Functions
Table of Contents
MPLS-TP Function ....................................................................................................4-1
MPLS .........................................................................................................................4-2
L2 ............................................................................................................................4-10
L3 ............................................................................................................................4-12
OAM Function ..........................................................................................................4-12
QoS Function ...........................................................................................................4-18
Clock and Time .......................................................................................................4-20
Safety and Reliability................................................................................................4-25
4.1 MPLS-TP Function

For the capacities of ZXCTN 6120S to support the Multi-Protocol Label Switching Transport
Profile (MPLS-TP) function, refer to Table 4-1.
Table 4-1 MPLS-TP Functions
Function Description
MPLS-TP function l MPLS-TP PW function
à Adaption of Ethernet service to PW
à Adaption of TDM service to PW
l MPLS-TP LSP function
à Mapping of multiple PWs to LSP
à LSP label switching
à MPLS-TP message out-tunnel processing
l MPLS-TP Section function
à Mapping of LSP to Section
à Adaption of MPLS-TP message to the data link layer
l MPLS-TP tunnel routing function
MPLS-TP OAM Supports layered OAM functions: PW OAM, LSP OAM, and Section OAM
function
MPLS-TP l MPLS-TP-based tunnel protection

protection l MPLS-TP-based ring protection
function
4-1

4.2 MPLS
ZXCTN 6120S can implement seamless convergence of IP and L2 through MPLS.
Meanwhile, MPLS technology provides better solutions to the application of traffic
engineering and VPN.
The MPLS architecture of ZXCTN 6120S complies with Multiprotocol Label Switching
Architecture (RFC 3031).
4.2.1 Basic MPLS Protocols

For the functions of basic MPLS protocols, refer to Table 4-2.
Table 4-2 Functions of Basic MPLS Protocols
Basic Function l Support the label management function of each platform.

l Support the domain-based management of static/dynamic labels.
l Support processing services and labels on the ingress node.
l Support processing services and labels on the egress node.
l Support processing labels on the middle node.
l Support label stack nesting (3 layers).
LDP Protocol l Support the following distribution and management mode of LDP
labels: Downstream Unsolicited (DU) mode + Independent label
control mode + Liberal label retention mode
l Bind FEC and label by LDP, and announce the information to the
neighbor LSR to establish the LSP.
l Support MD5 encryption authentication, which complies with
RFC-3036 requirements.
l Use the LDP GR function to solve the problem of label data
forwarding which is caused by the restart of LSR control layer
(especially cause by the restart of LDP control layer).
RSVP-TE Protocol l Support creating and maintaining the RSVP-TE LSP.

l Support removing the RSVP-TE LSP.
l Support error notifications.
l Support the explicit path function.
l Support the RSVP MD5 authentication function.
l Support the confined routing calculation function.
l Support the interface TE bandwidth management function.
l Support the bidirectional LSP.
l Support cross-domain RSVP-TE.
l Support the RSVP-TE GR function
4-2

Chapter 4 Functions
4.2.2 MPLS L2VPN

MPLS L2VPN refers to transparently transmit layer-2 user data over the MPLS network.
VPWS
Virtual Private Wire Service (VPWS) is used to provide point-to-point VPN service
transmission. PE devices in the MPLS network receive user services from the CE
devices. After being encapsulated by the PE devices, the user services are transparently
transmitted in the MPLS network and then finally transmitted to the destination.
For a typical network architecture of the VPWS, see Figure 4-1.
Figure 4-1 VPWS Typical Network Diagram
VPLS
Virtual Private LAN Service (VPLS) is a multipoint-to-multipoint layer-2 VPN technology
that integrates the superiority of the Ethernet technology and MPLS technology. VPLS
simulates the traditional Local Area Network (LAN) function to connect multiple separate
Ethernet sites in regions through the operator's MPLS backbone network, so that these
sites appear to operate in the same LAN.
For a typical network architecture of VPLS, see Figure 4-2.
4-3

Figure 4-2 VPLS Typical Network Diagram
L2VPN in LDP Mode

To support L2VPN services, the ZXCTN 6120S expands the protocols (such as the LDP
specification RFC3036) that support the establishment of LSPs using LDP, so that the
expanded protocols support the establishment and maintenance of various types of PWs.
l The RFC 4447 and RFC 5287 protocols support VPWS services.
l The expanded LDP protocol (RFC 4762) based on RFC4447 supports VPLS services.
l Besides the original functions provided by the LDP protocol, the expanded protocols
also provide the following functions.
à The Type/Length/Value (TLV) of the expanded protocols are used to carry PW
IDs, including the 128-type PW ID FEC TLV.
à When a PW is established, label distribution sequence uses DU mode and the
label retention mode is liberal label retention.
à The protocols support the negotiation of PW data interface parameters. The
interface negotiation parameters include the Maximum Transfer Unit (MTU),
maximum number of ATM cell cascade, and fragmentation capability negotiation.
à The protocols support the control word negotiation function.
H-VPLS
The VPLS mode requires full connections between PEs. Therefore, if the VPLS network
is in a large scale, the number of PWs is huge, and the PW signaling overhead is great,
so the network management and expansion will be complex.
The H-VPLS divides the PEs into UPEs and NPEs, see Figure 4-3.
4-4

Chapter 4 Functions
Figure 4-3 H-VPLS Network Diagram
l As an Multi-Tenant Unit (MTU) for the users to access the VPN, a UPE is used to
connect the CEs and the service provider's network.
l The NPEs are located at the core domain edge of the VPLS network to provide trans-
parent transmission of user packets over the core network.
The UPEs do not need to establish full connections between all NPEs. It only needs
to establish full connections between NPEs. The H-VPLS hierarchically decreases the
number of PWs and the burden of PW signaling.
MS-PW
Multi-Segment Pseudo-Wire (MS-PW) refers to multiple segment pseudo wires between
the UPEs. For the application scenario of MS-PW, see Figure 4-4.
4-5

Figure 4-4 MS-PW Application Scenario
MS-PW has the following application solutions:

l The source UPE and destination PE of the service are not in the same AS. The
signaling connection or tunnel cannot be established between the two PEs.
l The source and destination PEs of the service use different signaling mechanisms.
For example, UPE uses the LDP protocol, and the other UPE uses the RSVP protocol.
l If the access device can run the MPLS protocol but cannot set up a mass of
LDP sessions, user Facing Provider Devices (UFPE) can serve as UPEs and the
high-performance equipment Switching PE (SPE) can serve as the switching node of
LDP sessions, similar to the signaling reflector, to achieve the tunnel convergence of
pseudo wires.
PW Status Notification
If the LDP protocol is used as PW signaling and the Attachment Circuit (AC) is down, LDP
signaling announces the information to the neighbors to remove PW labels. If the AC is
restored, the LDP renegotiates to create PW labels. When the AC oscillates, PW labels
may constantly be deleted and created, which affects network stability.
To protect PW labels from being constantly deleted and created because of the oscillation
of the access link, the ZXCTN 6120S prevents the LDP PW labels from being affected
by the AC. In other words, the status of the AC is not used as the criterion for creating or
deleting LDP PW labels. On the basis of Martini, dynamic PWs add the optional status
parameters in mapping messages and supports notification messages. If the network
is unstable, notification messages can be used to reduce the number of exchanged
messages.
4.2.3 BGP/MPLS L3VPN

The ZXCTN 6120S supports the RFC 4364 protocol. In this mechanism, the BGP protocol
is used to distribute VPN routing information in the operator’s backbone network and MPLS
4-6

Chapter 4 Functions
is used to forward VPN user data from one VPN site to another. The VPN implemented
by this technology is called BGP/MPLS VPN, which is an L3VPN mode for VPN devices.
For the basic network architecture of BGP/MPLS L3VPN, see Figure 4-5.
Figure 4-5 Network Architecture of BGP/MPLS L3VPN
A routing protocol is used between CEs and PEs for route interaction. The routing
protocol can be configured dynamically (based on RFC 4364, including RIP, BGP,
or OSPF) or statically. On PEs, each attachment circuit between a CE and a PE is
associated with one or multiple Virtual Route Forwarding (VRF) tables. Between PEs,
the route information belonging to the same MPLS VPN is interacted through the BGP
protocol for VRF synchronization. The SCN network or MPLS tunnels are used between
PEs for forwarding routes. For the VPN network information that the operator router P
does not need to know, this transparent mode can effectively reduce the load of route P
and improve network expandability and service flexibility.
Through the route interaction between PEs and between PEs and CEs, client routers and
PE devices can acquire network topology information in the same VPN, so that client
services can be interacted in different sites.
VRF
The ZXCTN 6120S supports VRF forwarding instances and supports VRF label per route
mode. MPLS L3VPN can be implemented on PE devices. The PEs establish a VRF table
for each VPN. All the clients and sites belonging to one VPN can access the corresponding
VRF table of this VPN only, so that the routing and forwarding of different clients can be
isolated.
L3VPN Access Modes

The ZXCTN 6120S supports the following L3VPN access modes:
l Based on VLAN
4-7

Different VLAN subinterfaces of the same physical interface can connect different user
services.
l Based on physical Ethernet port
Different physical Ethernet ports can connect different user services.
L3VPN Tunnels
The ZXCTN 6120S can use the following modes to pre-create the LSP tunnel between
PEs.
l Use RSVP-TE as the signalling protocol and supports traffic engineering.
l Use LDP as the signalling protocol and doesn’t support traffic engineering.
l Use the static tunnels configured manually on the management platform.
Routing Interaction Modes Between PEs and CEs

The ZXCTN 6120S supports the following routing interaction modes between PEs and
CEs:
l Based on static routing
l Based on the OSPF protocol
l Based on the BGP
l Based on the IS-IS protocol
Cross-Domain MPLS VPN

Cross-domain MPLS VPN is used to release routing information across the links between
operators’ networks.
The ZXCTN 6120S supports the Option A and Option B cross-domain MPLS VPN.
l Option A
Option A is also called back-to-back cross domain, meaning that two Autonomous
System Boundary Routers (ASBRs) act as the PE and CE for each other. ASBR1
works as a PE device of AS1, and ASBR2 is considered as a CE device connecting
with ASBR1, see Figure 4-6. In the same way, ASBR2 works as a PE device of AS2,
and ASBR1 is considered as a CE device connecting with ASBR2.
4-8

Chapter 4 Functions
Figure 4-6 Cross-Domain MPLS VPN Option A Diagram
l Option B
Option B is also called single hop MP-EBGP cross domain, see Figure 4-7. VPN
information is transported and the LSP tunnel is established by MPLS/BGP in AS
domains. VPN information is transported and the LSP tunnel is established by single
hop MP-EBGP protocol between AS domians.
Figure 4-7 Cross-Domain MPLS VPN Option B Diagram
4-9

L3VPN FRR
The ZXCTN 6120S supports the VPN FRR function, which can make the fault recovery
time of end-to-end service have nothing with the network scale of private routing. The
L3VPN FRR function is easy to deployment and reliable. For a typical network architecture
of L3VPN FRR, see Figure 4-8.
Figure 4-8 Typical Network Architecture of L3VPN FRR
In normal cases, CE1 accesses CE2 through path 1. If PE2 fails, CE1 accesses CE2
through converged path 2.
4.3 L2
Basic Ethernet The ZXCTN 6120S supports the following basic Ethernet functions.
functions l Supports the full-duplex working mode of interfaces.
l Supports MAC address learning, MAC address aging, and MAC address
filtering.
l Supports 1000Mbps electrical interfaces and the 10/100Mbps automatic
negotiation function.
l Supports setting the port rate, full-duplex mode, traffic control, and MTU.
l Supports the L2 switching function.
l Supports the interface traffic control function of the IEEE 802.3x Pause frame
mechanism based on full-duplex working mode.
l Supports the ingress and egress mirroring functions.
l Supports the storm suppression function of broadcast/multicast/unknown
unicast packets.
4-10

Chapter 4 Functions
l Supports the jumbo frame function.

The size of the jumbo frame is up to 9K bytes.
l Supports LLDP defined by the 802.1ab standard.
VLAN The ZXCTN 6120S supports the following VLAN functions.

l Supports the port-based VLAN.
l Supports QinQ-based forwarding
l Supports the ordinary QinQ function and port-based outer tags.
l Supports the selective QinQ function and traffic-based outer tags.
l Supports the selective QinQ inner priority mapping function.
l Supports modifying the TPID.
l Supports the QinQ function in 1:1, 1:2, and 2:1 modes.
Link The ZXCTN 6120S supports the following link aggregation functions.
aggregation l Supports the link aggregation in manual load balance mode
l Supports the link aggregation protocol (LACP) complying with the IEEE 802.3ad.
l Supports the binding function of FE and GE interfaces.
l Supports the load balance function based on the MAC and IP addresses.
l Supports the cross service board link aggregation.
STP The ZXCTN 6120S supports the following STP protocols.

l SSTP compliant with the IEEE802.1D standard
l MSTP compliant with the IEEE802.1s standard
l RSTP compliant with the IEEE802.1w standard
DHCP The ZXCTN 6120S supports DHCP relay.
Muticast The ZXCTN 6120S supports the following IGMP proxy/snooping multicast functions.
l Supports the IGMPv2 protocol.
l Supports configuring the static multicast table.
l Supports creating the multicast table based on IGMP proxy/snooping and then
forwarding multicast services based on the service interfaces in the multicast
table.
l If IGMP proxy/snooping is enabled, the ZXCTN 6120S forwards the created
multicast table based on the designated interface in the table and discards or
broadcasts unknown multicast as required.
l Supports dynamically creating, deleting, and maintaining the multicast table
based on VPLS/E-LAN services, and querying multicast.
4-11

4.4 L3
Basic functions The ZXCTN 6120S supports the following basic L3 functions.
l Supports the following L3 interface.
à L3 interface based on the VLAN
à L3 interface based on the Qx interface
à VLAN sub-interface based on the interface and VLAN
l Supports the ARP protocol.
à Supports dynamic ARP requests.
à Supports ARP response.
à Supports dynamic ARP aging and aging time configuration.
à Supports static ARP configuration
l Supports IPv4 unicast route forwarding.
à Supports IPv4 unicast route linear forwarding.
à Supports Best match of the hardware route table.
l Supports static routes.

l Supports the ECMP protocol.
l Supports the ICMP protocol.
l Supports the TCP protocol.
l Supports the UDP protocol.
l Supports IP FRR protection.
Routing protocols The ZXCTN 6120S supports the following routing protocols.
l The OSPF protocol
l The BGP protocol
l The IS-IS protocol
4.5 OAM Function

ZXCTN 6120S supplies multi-level OAM mechanism, supports MPLS-TP OAM, MPLS
OAM and Ethernet OAM, achieves fast fault detection to trigger protection switching, and
guarantees the carrier-class service quality of services.
As shown in Figure 4-9, the MPLS-TP divides the OAM into five layers, namely access
layer, service layer, PW layer, tunnel layer, and segment layer. The PW OAM, tunnel OAM,
and segment OAM belong to the network.
l PW-layer OAM (PW OAM): monitors the connections and performance of various
services and provides good conditions for end-to-end service management.
4-12

Chapter 4 Functions
l Tunnel-layer OAM (Tunnel OAM): monitors and protects the LSP layer, and avoids
performance degradation caused by increasing number of OAM services.
l Section-layer OAM (Section OAM): provides ring network protection and saves
bandwidth.
Figure 4-9 OAM Implementation Mechanism
4.5.1 MPLS-TP OAM Functions

ZXCTN 6120S supports the Operation, Administration and Maintenance (OAM) function
at MPLS-TP section layer, tunnel layer, and PW layer. It provides end-to-end fault
management functions, fault locating functions, performance monitoring functions, and
other OAM functions.
For MPLS-TP functions, refer to Table 4-3.
Table 4-3 MPLS-TP Functions Supported by the ZXCTN 6120S
Type Function Section Layer Tunnel PW

OAM OAM OAM
Active Fault Continuity and connectivity Check Supported Supported Sup-

management (CC) ported
Remote Defect Indication (RDI) Supported Supported Sup-

ported
Forward Defect Indication Not applicable Supported Sup-

(FDI)/Alarm Indication Signal ported
(AIS)
4-13

Type Function Section Layer Tunnel PW

OAM OAM OAM
Client Signal Failure (CSF) Not applicable Not Sup-

applicable ported
Performance Frame Loss Measurement (LM) Supported Supported Sup-

monitoring ported
On-demand Fault Loopback (LB) Supported Supported Sup-

management ported
Test (TST) Not applicable Supported Sup-

ported
Link Tracing (LT) Not applicable Supported Sup-

ported
Performance Frame Loss Measurement (LM) Supported Supported Sup-

monitoring ported
Delay Measurement (DM) Supported Supported Sup-

ported
Communi- Management Management control channel Optional Optional Optional

cation chan-
Signaling Signaling control channel Optional Optional Optional
nel
Protection Automatic linear protection switch Not applicable Supported Sup-
ported
Automatic ring protection switch Supported Not Not ap-

applicable plicable
4.5.2 MPLS OAM Function

For the MPLS OAM functions supported by the ZXCTN 6120S, refer to Table 4-4.
Table 4-4 MPLS OAM Function
Items Functions
LSP Ping LSP Ping is similar to IP Ping.

1. It sends MPLS Echo request packet in LSP.
2. If the packet arrives at the egress, it returns MPLS Echo reply packet at the egress
of MPLS domain.
3. If reply packet returns, you can know whether this LSP can be used for data
forwarding or not.
LSP Trace LSP Trace refers to sending a series of MPLS Echo request packets at the starting
point of LSP. TTLs of these packets are one to a certain value. Each node on LSP
respectively receives request packet and returns reply packet. Thus, LSP starting
point can collect the information on LSP path
4-14

Chapter 4 Functions
Items Functions
PW Ping PW Ping is similar to IP Ping. Realized by extending LSP Ping, PW Ping is a tool
which is used to manually detect virtual circuits connection status. PW Ping defined a
series of information to test the PW connectivity between PEs.
PW Trace PW Trace is similar to LSP Trace, but their layers are not same.
l LSP Trace uses LSP to forward MPLS Echo request, while PW Trace uses PW to
forward MPLS Echo request.
l PW Trace is classified into single section PW Trace and multi-section PW Trace.
VRF Ping / VRF Trace is similar to IP Ping/Trace, and is used to detect the reachability of L3
VRF Trace VPN private route.
Bidirectional Bidirectional Forwarding Detection (BFD) is a path connectivity detection protocol. It

Forwarding is also a simple Hello protocol which is similar to the Hello protocol used in routing
Detection protocol. Compared to the Hello protocol used in routing protocol, it can detect faults
(BFD) on the forwarding path in a short time.
ZXCTN 6120S supports the following BFD detection types:
l LSP/PW BFD
l OSPF/IS-IS BFD
l VRRP BFD
l TE FRR/IP FRR BFD
4.5.3 Ethernet OAM Functions

Ethernet OAM is classified into the following levels:
l Link-level Ethernet OAM (Ethernet in the First Mile (EFM))
l Network-level Ethernet OAM (Connectivity Fault Management (CFM))
The EFM supported by ZXCTN 6120S is an OAM function based on IEEE 802.3ah. For
the detailed function descriptions, refer to Table 4-5.
Table 4-5 Descriptions of the EFM Function
Remote discovery Discoveries peer end of the OAM automatically through automatic
negotiation at both ends of the OAM.
Lnk monitoring Both ends of the OAM exchange data messages periodically, to monitor
the link connectivity in real time.
Lopback Controls the forwarding of data messages by enabling the remote loopback
function.
The CFM function supported by the ZXCTN 6120S is the OAM function based on ITU-T
Y.1731/IEEE 802.1ag, which supports two layers of Y.1731OAM/802.1ag nesting. For the
detailed function descriptions, refer to Table 4-6 and Table 4-7.
4-15

Table 4-6 Descriptions of the CFM Function Based on ITU-T Y.1731
Ethernet Continuity As an active OAM function, ETH-CC is used to check the connectivity
Check (ETH-CC) between two ME Groups (MEGs), or between any two MEG End Points
(MEPs) in an MEG.
ETH-CC provides the following features:
l Continuity loss check
l Error combination check
l Abnormal MEG End Point (MEP) check
l Abnormal period check
Ethernet Loopback ETH-LB is used to check the connectivity between the MEP and the MIP, or
(ETH-LB) detection between two MEPs.
ETH-LB can be classified into unicast ETH-LB and multicast ETH-LB.
l As an OAM function on demand, unicast ETH-LB is used to verify the
bidirectional connectivity between the MEP and MIP. If bidirectional
serve or service interruption diagnosis test is implemented between two
MEPs, unicast ETH-LB is also used to detect bandwidth or bit error ratio.
l As an OAM function on demand, multicast ETH-LB is used to verify the
bidirectional connectivity between two peer MEPs.
Ethernet Link Tracing As an OAM function on demand, ETH-LT is used to locate errors and confirm
(ETH-LT) neighbor relations.
Ethernet Alarm If the MEP detects faults at server layer, ETH-AIS is used to suppress all
Indication Signal the associated alarms of the peer MEP, no matter whether there is any
(ETH-AIS) connectivity between the MEP and its peer MEP.
Ethernet Remote ETH-RDI is an OAM function for exchanging faults between one MEP and its
Defect Indication peer MEP. It is used in unicast error management and remote performance
(ETH-RDI) monitoring.
Ethernet Lock signal ETH-LCK is used to send the server-layer EMP administrative lock notification
(ETH-LCK) and data service flow interruption notification to the MEP, so that the MEP
can distinguish normal faults from the server-layer EMP administrative lock.
Ethernet Test signal ETH-Test is used in the on-demand unicast service period, or in the diagnosis
(ETH-Test) test of service interruption, such as bandwidth flow verification, frame loss
verification, and bit error verification.
Ethernet frame Based on implementation modes, ETH-LM can be classified into dual-end
Loss Measurement ETH-LM and single-end ETH-LM.
(ETH-LM) l Dual-end ETH-LM is an active OAM function used for error management.
l Single-end ETH-LM is an OAM function on demand.
4-16

Chapter 4 Functions
Ethernet frame As an OAM function on demand, it is used to measure the frame delay and
Delay Measurement its variation in the network. Based on implementation modes, ETH-DM can
(ETH-DM/ETH-DVM) be classified into Unidirectional ETH-DM and Bidirectional ETH-DM.
l Unidirectional ETH-DM is used to measure the unidirectional frame
delay and its variation.
l Bidirectional ETH-DM is used to measure the bidirectional frame delay
and its variation
Other functions Supports Ethernet Automatic Protection Switching (ETH-APS), Ethernet

Management Communication Channel (ETH-MCC), Ethernet Experiment
OAM (ETH-EXP), and Ethernet provider specific OAM (ETH-VSP) functions.
Table 4-7 Descriptions of the CFM Function Based on IEEE 802.1ag
Global CFM Used to enable/disable the global CFM function.

enable/disable
function
Maintenance domain Used to create/delete an maintenance domain, or configure maintenance

creation/deletion/con- domain parameters.
figuration
Maintenance joint Used to create/delete an maintenance joint, or configure maintenance joint

creation/deletion/con- parameters.
figuration
MEP creation Used to create an MEP.
MIP creation Used to create an MIP.
Remote MEP Used to configure remote MEP parameters.

configuration
MP database display Used to display information of the MP database.
Connectivity Check Send CCMs periodically to check the continuity.

Message (CCM)
Loopback (LB) As an OAM function on demand, it sends a unicast request to the destination
MP (MEP or MIP), and receives response messages from the destination MP,
in order to confirm the bidirectional connectivity between two maintenance
points.
Link Tracing (LT) As an OAM function on demand, it sends a multicast OAM messages, and
forwards the message along the route, in order to locate the fault.
Remote Defect Used to detect remote defects and send the CV frames with RDI.
Indication (RDI)
4-17

CFM MIB Supports command line configuration, displays CFM status, and supports
MIB Get mode.
4.6 QoS Function

Basic QoS Functions
The ZXCTN 6120S provides perfect support for Differentiated Services (DiffServ),
including traffic classification, traffic monitoring, traffic shaping, congestion management,
and queue scheduling. It provides hierarchical QoS models for different service traffic,
which enables network operators to provide users with services of different QoS levels.
ZXCTN 6120S has perfect QoS scheduling mechanism and provides high-quality service
transmission service.
For the basic QoS functions of the ZXCTN 6120S, refer to Table 4-8.
Table 4-8 Basic QoS Functions
Function Function Description
Traffic classification Traffic classification is to classify the data packets into several
priorities or types. The equipment provides differentiated services in
accordance with the service types.
The ZXCTN 6120S supports port, L2, L3, L4 packet header
content-based classification, including physical interface, source IP
address, destination IP address, MAC address, 802.1p, source IP,
sink IP address, IP protocol, port number of application program, and
combination of these classification modes.
Traffic monitoring Traffic monitoring is to limit the bandwidth of a service flow when it
enters a network, preventing it from exceeding the specified bandwidth
and causing impact to other service flows.
The ZXCTN 6120S supports the following traffic monitoring functions:
l Supports traffic monitoring based on input port or output port.
l Adopts Access Control List (ACL) to implement service traffic
access control.
l Implements Committed Information Rate (CIR), Committed Burst
Size (CBS), Excess Information Rate (EIR) and Excess Burst
Size (EBS) based on flow.
l Supports dual token bucket.
l Supports drop, color-mark and other policy actions for contracted
rate-beyond traffic.
l Supports ingress and egress traffic monitoring.
4-18

Chapter 4 Functions
Traffic shaping Typical function of traffic shaping is to limit the traffic and the packet
burst in a network, making the packet sent externally in an even rate.
The ZXCTN 6120S supports the following traffic shaping functions:
l Port-based traffic shaping function
l Priority-based traffic shaping function
Congestion management Congestion avoidance is mainly used to implement service cache and
dropping, drop a few packets selectively when congestion occurs on
network node, which can relieve network congestion.
The ZXCTN 6120S supports the following congestion avoidance
function:
l Supports the Weighted Random Early Detection (WRED) drop
policy.
l Supports setting the upper-limit drop threshold, lower-limit drop
threshold, and drop ratio.
l Supports the tail drop caching policy.
Queue scheduling The ZXCTN 6120S uses mixed and flexible queue scheduling based
on different types of services. Queue scheduling modes include:
l Weighted Round Robin (WRR)
l Deficit Weighted Round Robin (DWRR) function.
l Strict Priority (SP)
l SP+WRR
l Each interface supports 8 levels of queue scheduling.
l Each queue supports maximum/minimum bandwidth
management.
Advanced QoS Functions

For the advanced QoS functions of the ZXCTN 6120S, refer to Table 4-9.
Table 4-9 Advanced QoS Functions
Hierarchical QoS model If network congestion occurs, the data traffic with higher level has higher
priority during queue scheduling and resource occupation than the data
traffic with lower level.
DS domain creation The ZXCTN 6120S supports creating DS domains. It can create DS
domains on interfaces, PWs, and tunnels, and then set PHB groups
supported by the corresponding DS domain. Each DS domain supports
up to 8 PHBs.
Tunnel QoS model Qos models include:

l Uniform model
l Pipe model
l Short pipe model
4-19

NNI side, MPLS priority If the network passes through L2 Ethernet network, L2 Ethernet network
maps to VLAN priority provides transparent L2 connection for gateway device by Q-in-Q
encapsulation.
In order to guarantee the QoS end to end, the MPLS priority of gateway
device should be mapped to the priority of VLAN, thus, L2 Ethernet
network can implement differential service. The QoS of service can
be guaranteed.
The ZXCTN 6120S supports copying the MPLS EXP priority to VLAN
priority at NNI side.
Client service QoS and The ZXCTN 6120S supports the mapping between the client service
IPHB, OPHB QoS, Incoming PHB (IPHB) and Outgoing PHB (OPHB).
LSP QoS and IPHB The ZXCTN 6120S supports configuring the mapping between the LSP
QoS field (EXP) and IPHB on the middle node of the tunnel.
Mapping from OPHB to The ZXCTN 6120S supports configuring the mapping from OPHB to
tunnel-layer QoS, PW tunnel, PW, Section QoS at the ingress point and the middle point of
QoS, section QoS the LSP.
Reserved bandwidth For the repeated PW/LSP on the same path, the ZXCTN 6120S does
share not perform the CAC calculation repeatedly. It only calculates the CIR
bandwidth once.
4.7 Clock and Time

Clock Function
The ZXCTN 6120S provides network-level clock synchronization. The system has
multiple ways in selecting synchronous clock source as system clock to implement clock
synchronization of network.
Supports the following working modes:

l Fast pull-in
l Tracing
l Holdover
l Free-run
For the system clock functions of the ZXCTN 6120S, refer to Table 4-10.
Table 4-10 System Clock Functions
Function Clock signal
BITS Supports inputting and outputting BITS clock signals.
GPS Supports 1PPS+ToD signals.
4-20

Chapter 4 Functions
Function Clock signal
E1/Ethernet Transfers clock signals through E1 interfaces and

synchronous Ethernet interface.
IEEE 1588 V2/1pps Supports restoring the clock based on IEEE1588V2

or 1pps to implement the frequency synchronization
function.
CES clock Includes adaptive mode, differential mode, and retiming

mode
SSM Supports transferring the SSM clock.
BMC algorithm Supports automatically selecting the clock with higher

priority and avoiding timing looping.
Time Function
The ZXCTN 6120S uses the Ethernet interface to transfer time, which meets the
requirements of the IEEE 1588 V2 function.
The ZXCTN 6120S supports the following time transmission function:
l Supports setting the clock node type.
à Ordinary clock
à Border clock
à End-to-End (E2E) transparent transmission clock
à Peer-to-Peer (P2P) transparent transmission clock
à Ordinary clock + E2E transparent transmission clock
à Ordinary clock +P2P transparent transmission clock
l Supports setting the Precision Time Protocol (PTP) port mode.
à Master port
à Slave port
à Passive port
l Supports the switching of time format.
l Supports the time synchronization management function.
l Supports the TS protection switchover function.
l Supports the delay compensation function.
4.7.1 IEEE 1588 V2 Application

IEEE 1588 V2 is a kind of Precision Time Protocol (PTP).
IEEE 1588 V2 protocol supports the following working modes:
l Ordinary Clock (OC)
4-21

Only one port supports the IEEE 1588 V2 protocol. Users need to recover the clock.
Ordinary clock can work as a time source, that is master clock equipment, or the slave
equipment which is synchronized by other clock equipment.
l Border Clock (BC)
Multiple ports support IEEE 1588 V2 protocol. Users need to recover the clock. It can
work as an master/slave clock equipment.
l Transparent Clock (TC)
The node does not run IEEE 1588 V2 protocol but transparently transmits the clock
signal. Clock recovery is not needed. It needs to modify timestamp. It fills the time
at which the node processes one packet in the modification position when forwarding
time packet.
à E2E TC
A TC using the end-to-end delay measurement mechanism is used between the

master and slave clocks.
à P2P TC
A TC that uses the end-to-end delay measurement mechanism.
There can be only one master clock in one communication subnet. In the entire system,
the optimum clock is Grandmaster Clock (GMC). BMC automatically selects the master
clock for each subnet. In the system with only one subnet, GMC is the master clock. Each
system has only one GMC. slave clock keeps synchronous with master clock.
ZXCTN 6120S supports IEEE 1588 V2 protocol and implements clock and time
synchronization. For a typical network architecture, see Figure 4-10.
4-22

Chapter 4 Functions
Figure 4-10 Synchronization of IEEE 1588 V2 Clock
4.7.2 IEEE 1588 ACR Application

Adaptive clock recovery (ACR) is a frequency synchronization function of TDMservice.
If signals are sent across a middle network (meaning, the third-party network), 1588
frequency recovery function must be used to implement clock synchronization because
the middle network does not support synchronous Ethernet or 1588 mode. For the
application of IEEE 1588 ACR function, see Figure 4-11.
4-23

Figure 4-11 Application of IEEE 1588 ACR Function
4.7.3 Synchronous Ethernet Application

ZXCTN 6120S fully supports G.8261 standard and implements Ethernet clock
synchronization in physical layer.
ZXCTN devices form synchronous Ethernet, which enables synchronous Ethernet
interfaces to implement synchronization at Ethernet physical layer. For a typical network
application of synchronous Ethernet, see Figure 4-12.
4-24

Chapter 4 Functions
Figure 4-12 Typical Application of Synchronous Ethernet
In synchronous Ethernet, clock signals of Global Positioning System (GPS), Building

Integrated Timing Supply (BITS) and other devices are synchronized in clock for ZXCTN
devices throughout the network through synchronous Ethernet interfaces. ZXCTN device
is connected with Base Transceiver Station (BTS) or WCDMA Base Station (NodeB),
and transmits the abstracted clock signals to BTS or NodeB, BSC and Radio Network
Controller (RNC) through synchronous Ethernet interfaces, thus implementing Ethernet
clock synchronization over the entire network.
4.8 Safety and Reliability

4.8.1 Business Security
Business security of the ZXCTN 6120S can be classified into access security and protocol
security.
Access Security
The ZXCTN 6120S provides the following functions to ensure the access security:
4-25

Table 4-11 Access Security Supported by ZXCTN 6120S
ACL functions l standard ACL

l extended ACL
l Layer 2 ACL
l hybrid ACL
l ACL interval control
Port speed limit -
ARP anti-attacking -
MAC address restriction -
Storm suppression l Broadcast storm suppression

l Multicast storm suppression
l Unknown unicast storm suppression
Protocol Security
The ZXCTN 6120S provides the following functions to ensure the protocol security:
l Supports MD5 encryption and authentication.

l Supports LDP) encryption and authentication.
l Supports Simple Network Management Protocol (SNMP) encryption and
authentication.
4.8.2 Equipment Security

ZXCTN 6120S provides the following functions on equipment security:
Table 4-12 Equipment Security Supported by ZXCTN 6120S
Preventing DoS attacks If the number exceeds the set alarm value, ZXCTN 6120S will give out
an alarm, shield the IP, and throw away all the packets from the IP till
the alarm is released. Thus to resist the DoS attacks.
Preventing BPDU attacks If ZXCTN 6120S detects abnormal traffic in BPDU data packets, it will
filter these data packets automatically to prevent BPDU attacks.
Preventing ARP attacks ZXCTN 6120S monitors the number of ARP messages received by the
same physical interface in a time. If the number exceeds the set alarm
value, ZXCTN 6120S will give out an alarm, and stops processing the
packets till the alarm is released. Thus to resist the ARP attacks.
Preventing LAND attacks The ZXCTN 6120S can filter SYN packets with attack purpose to
prevent the LAND attack and protect the server host.
Preventing SMURF attacks The ZXCTN 6120S use the CAR to restrict the traffic of ICMP. Thus to
prevent SMURF attacks, and to protect the server machine.
4-26

Chapter 4 Functions
Preventing SYN FLOOD The ZXCTN 6120Sprevents SYN FLOOD attacks by limiting SYN
attacks timeout time and connection times through configuration.
Preventing PING FLOOD If the ZXCTN 6120S detects the PING FLOOD attack, the equipment
attacks filters ICMP packets with attack purpose to prevent the PING FLOOD
attack.
Preventing Teardrop ZXCTN 6120S can filter data packets with overlapped fragment offset to
attacks prevent the Teardrop attack.
Preventing Ping of Death If the ZXCTN 6120S detects the Ping of Death attack, the equipment
attacks filters PING packets with attack purpose automatically to prevent the
attack.
CPU security protection The ZXCTN 6120S judges if it is attacked by the CPU uploading rate
of protocol packets. It initiates corresponding protection measures
if attacked.
Command authority graded The ZXCTN 6120S supports 16 levels of command authorities. Different
protection authority levels are set for different login users. The lower the authority
level is, the fewer the available commands are; the higher the authority
level is, the more the available commands are. The administrator (the
highest level, being 15) can set different commands with different
authority levels, which achieves customized configuration of command
authorities and provides great ensurance of equipment security.
Preventing abnormal If the ZXCTN 6120S detects a large number of abnormal packets and
packets and error packets error packets, the equipment filters these packets to prevent the attack
on the target system.
4.8.3 Authentication Management

To ensure the safe operation of the system, only authenticated legal user can log into the
Network Element (NE). ZXCTN 6120S provides the following authentication functions:
Table 4-13 Authentication Functions Supported by ZXCTN 6120S
NE login management Only the user with legal account and password can log into
the NE.
NE user switching At one client end, only one user can operate the NE at one
time. To operate the NE by a different user, it needs to
switch the user to ensure the data uniqueness.
4-27

Forcing the NE user to log out To avoid the error caused by the simultaneous configuration
of multiple NE users or prevent other users from illegally
log in the NE, the NE user can force the NE user of a lower
level to exit the NE.
Querying the login user on the NE Including the login IP address, login time and login type of
the user.
Locking NE user If the wrong password input times of user login reaches the
preset value, the user's account will be locked.
Setting the user blacklist Users in the blacklist are forbidden to log into the system.
4.8.4 User Authority Management

Proper arrangement of different NE users' operation rights can achieve normal operations
of users over NEs and effectively protect the security of the NE system.
l According to different operation limits, NE users are classified into four levels: system
monitor, system operator, system maintainer and system administrator (from low to
high).
l According to different network management systems, NE users can be classified as:
Local Craft Terminal (LCT) NE users, Network Element Management System (EMS)
NE users, and CMD NE users.
NMS supports the following operations:
l Creates the NE user, assign user rights and designate the affiliated department of the
user.
l Modifies the user name, password, operation limit and affiliated department.
l Deletes the NE user.
4-28

Chapter 5
Protection
Table of Contents
Equipment-Level Protection........................................................................................5-1
Network-Layer Protection ...........................................................................................5-2
5.1 Equipment-Level Protection

1+1 Protection of DC Power Board
The ZXCTN 6120S subrack can be installed with two DC power boards. Two channels of
-48 V power supplies access the ZXCTN 6120S to form 1+1 hot backup protection mode.
If one of the power boards is faultyy or removed, it does not affect the normal operation of
the ZXCTN 6120S.
Over-Current Protection
ZXCTN 6120S supports the function of board over-current protection. As for over-current
protection function, it contains board over-current protection and device over-current
protection.
l Board over-current protection

After load current of functional card exceeds rated current, system will cut off load
power supply of functional card. The protection mode is non-restorable.
l Device over-current protection

Power board sets protection point according to rated current of the device. If partial
cards enable over-current protection, device can still power the other cards normally;
only when device internal current exceeds rated current of the device, power module
enables over-current protection and cuts off power supply to the device.
Power Loss Restoration

ZXCTN 6120S supports to save device management configuration information in storage
on main board in real time.
For restoration on AC/power loss, main board is restored firstly, service cards access
corresponding configuration information from storage on main board and thus services,
NM and clock get restored.
5-1

5.2 Network-Layer Protection

5.2.1 MPLS-TP Static Tunneling Protection
MPLS-TP static tunnel protection can be classified into 1:1 protection and 1+1 protection.
For the technology comparisons between 1:1 protection and 1+1 protection, refer to Table
5-1.
Table 5-1 Technology Comparisons Between 1:1 Protection and 1+1 Protection
Protection Mode Switching Time Bandwidth Implementation Implementation

Usage Complexity Mode
1:1 protection Less than 50 ms Protection The APS function End-to-end, same
bandwidth is needs to be source and source
available enabled. destination
1+1 protection Less than 50 ms Protection Relatively simple End-to-end, same

bandwidth is not source and source
available destination
1:1 Protection
In the 1:1 path protection mode, the protection path is for the dedicated usage of each work
path. The protected work service is transmitted by the work path or the protection path.
The service is transmitted to the destination end of the protection domain through the work
path. The destination end selects to receive the service on the work path according to the
preset constraint rules.
The 1:1 path protection is in bidirectional switching. That is, both the affected and
unaffected connection ways are switched to the protection path. For bidirectional
switching, the Automatic Protection Switching (APS) protocol needs to be enabled to
coordinate both ends of the service path. To avoid the single-point failure, routes should
go through the work path and the protection path separately.
For the schematic diagram of 1:1 path protection, see Figure 5-1. In normal cases, the
service is transmitted through the working channel from node A to node Z in normal status.
There is not service on the protection channel. If the working channel is faulty, the service
is switched to the protection channel for transmission on node A, node Z receives the
service on the protection channel.
5-2

Chapter 5 Protection
Figure 5-1 1:1 Path Protection Diagram
1+1 Protection
In the 1+1 path protection mode, the protection path is for the dedicated usage of each
work path. The work path and the protection path are bridged at the source end of the
protection domain. The service is transmitted to the destination end of the protection
domain through the work path and the protection path simultaneously. The destination
end selects to receive the service on the work path or the protection path according to the
preset constraint rules.
The 1+1 path protection is in unidirectional switching. That is, only the affected connection
way is switched to the protection path. To avoid the single-point failure, routes should go
through the work path and the protection path separately.
For the schematic diagram of 1+1 path protection, see Figure 5-2. In normal cases, the
service is transmitted through the working channel and the protection channel from node
A to node Z in normal status. Node Z selects to receive the service on the work channel
or the protection channel according to the preset constraint rules. If the working channel
is faulty, Node Z receives the service on the protection channel.
5-3

Figure 5-2 1+1 Path Protection Diagram
5.2.2 Wrapping Protection

ZXCTN 6120S supports wrapping ring protection. For the principle of wrapping protection,
see Figure 5-3.
Figure 5-3 Wrapping Mode Ring Network Protection Diagram
5-4

If the node on the network detects network failure, the fault adjacent node sends the
switching request to adjacent nodes through the APS protocol.
If a node detects the fails or receives the switching request, the service transmitted to the
failure node will be switched to another direction (far away from the failure node). If the
network failure or the APS protocol request disappears, the service returns to the previous
path.
5.2.3 Shared Ring Protection

Shared ring protection is the section layer protection, which is used to protect MPLS-TP
static tunnels in the ring network. The ZXCTN 6120S supports ring protection of share
channels. For the schematic diagram of shared ring protection, see Figure 5-4.
Figure 5-4 Schematic Diagram of Shared Ring Protection
This following uses the service transmission between A and D as an example.

In normal status, the service path from A to D is A→B→C→D. If the channel between B
and C is faulty, services on the B and C are switched to the protection channel. Then, the
service path from A to D changes to A→B→A→F→E→D→C→D. The channel between B
and C is faulty, services are sent over the protection channel. The link between C and D
is normal, services are still sent over the working channel.
5.2.4 Double-loop Dual-node Protection

If ring protection is adopted in the network, tangent loops and intersectant loops can be
used for the interworking of two loops. The tangent loops has only one interworking node.
Therefore, once the node fails, all span-loop interworking services are interrupted. The
reliability of inter-loop service protection can be raised through intersectant rings. That
5-5

is, two rings are interconnected through two nodes, so that the span-loop service can be
transferred by an intersectant node in case of failure in the other intersectant node.
For a typical network architecture of double-loop dual-node protection, see Figure
5-5. The ZXCTN 6120S supports A-B, A-C, B-D, E-C, E-F, F-D single-point fault or
two-point fault double-loop dual-node protection. C-D loop only supports single-point
fault double-loop dual-node protection, in which the protection mode is Wrapping and the
protection switching performance is 50 ms.
Figure 5-5 Typical Network Architecture of Double-loop Dual-node Protection
5.2.5 PW Protection
PW Dual-homing Protection
ZXCTN 6120S supports PW dual-homing protection and MS-PW protection.
Dual-homing protection is to protect the service transmitted over the work pseudo wire
(PW) by protecting the PW. In case of the work PW fault, peer-end single-point failure or
user side link fault, the service will be switched to the protection PW.
ZXCTN 6120S supports two dual-homing protection modes:
l 1+1 dual-homing protection
l 1:1 dual-homing protection
For a typical network architecture of dual-homing protection, see Figure 5-6. The PW
from P1 to P2 is the work PW, the PW from P1 to P3 is the protection PW. P2, P3 and
RNC set up the Multi-Chassis Link Aggregation Group (MC-LAG) protection. Normally, the
service of the base station (BTS) and RNC is transmitted through the work PW. In case
of P2 failure or the fault in the link between P2 and RNC, P1 will receive the CSF alarm
indication to trigger protection switching, and the service is then switched from the work
PW to the protection PW.
5-6

Figure 5-6 Typical Network Architecture of Dual-homing Protection
MS-PW Protection
MS-PW protection separates the management area of tunnel, which avoids the inter
communication between different routing areas.
For a typical network architecture of MS-PW protection, see Figure 5-7. There are multi
PWs between UPE and UPE. SPE switches the labels during transferring PW. That is,
SPE connects the single PW of two sides and switch the PW label.
Figure 5-7 Typical Network Architecture of MS-PW Protection
If the PW100 fails, the service will be switched to PW300. SPE switches the PW label.
Then the service will be carried by PW400 and sent to the user side.
5-7

5.2.6 MPLS Protection

1:1 Protection
For the schematic diagram of MPLS 1:1 protection, see Figure 5-8. In normal cases, the
service is transmitted through the working LSP from the source end to the destination end
and there is not service on the protection LSP.
If the working LSP is faulty, the service is switched to the protection LSP for transmission
on the source end, the destination end receives the service on the protection LSP.
Due to permanent merge and double receiving features of the destination end in MPLS
protection, there is no need to enable the APS protocol to switch.
Figure 5-8 Schematic Diagram of MPLS 1:1 Protection
1+1 Protection
For the schematic diagram of MPLS 1+1 protection, see Figure 5-9. In normal cases, the
service is transmitted through the working LSP and the protection LSP from the source
end to the destination end and the destination end selects to receive the service on the
work channel or the protection LSP based on the preset constraint rules. If the working
LSP is faulty, the destination end receives the service on the protection LSP.
5-8

Figure 5-9 Schematic Diagram of MPLS 1+1 Protection
5.2.7 FRR Protection

Fast Reroute (FRR) is a mode to achieve protection by reserving extra resources. Its
feature is fast partial protection. It is normally deployed in the network which has high
demands on reliability. If partial network fails, the FRR can quickly switch to the Bypass
Tunnel, so that the data service is less affected.
FRR protection is deployed in the network with high requirement for reliability. If the
network partially fails, FRR can fast switch to Bypass Tunnel. Thus, there is little impact
on the data services.
ZXCTN 6120S supports IP FRR, LDP FRR, PW FRR, VPN FRR, and RSVP-TE FRR
protection. IP FRR supports OSPF and IS-IS protocol, LDP FRR supports LDP protocol,
RSVP-TE FRR is based on RSVP-TE.
IP FRR and LDP FRR

l IP FRR
IP FRR is a most commonly used IP protection mode. The slave layer-3 port
protects the master layer-3 port. The detection mechanism of IP FRR is Bidirectional
Forwarding Detection (BFD), when BFD detects the fault, triggers the switch at
lsyer-3 port. IP FRR is deployed at the core layer.
5-9

For the schematic diagram of IP FRR protection, see Figure 5-10. If interface 12/8 of
PE2 is faulty, the system switches to standby IP FRR (PE2→PE3→CE2).
Figure 5-10 Schematic Diagram of IP FRR Protection
l LDP FRR
LDP FRR is based on LDP protocol. After the LDP protocol is configured, an FRR
table will be formed with MPLS out-label of master and slave. LDP FRR is performed
based on this FRR table. LDP FRR is deployed at the P device in the core network.
The ZXCTN 6120S supports FRR link protection and node protection. For the schematic
diagrams of FRR link protection and node protection, see Figure 5-11 and Figure 5-12
respectively.
5-10

Figure 5-11 Schematic Diagram of FRR Link Protection
5-11

Figure 5-12 Schematic Diagram of FRR Node Protection
PW FRR
PW FRR is a protection mode with same source and different destinations.
PW FRR is used to protect node or link by BFD mechanism.
Normally, PW FRR works together with tunnel protection. The tunnel protection is triggered
at first. If the tunnel protection is abnormal, then PW FRR starts to work. For the schematic
diagram of PW FRR protection, see Figure 5-13. The PW from P1 to P2 is the working
PW, PW from P1 to P3 is protection PW. Normally, the service between base station and
RNC is transported by the working PW. If the working PW or P2 is abnormal, P1 receives
the message which announces the P2 is disabled. Then the protection is triggered, the
service is switched from the working PW to the protection PW.
5-12

Figure 5-13 Schematic Diagram of PW FRR Protection
VPN FRR
Based on VPN routine fast switch technology, VPN FRR sets working and protection
transferring items on terminal PE in advance. The transferring items point to the working
PE and protection PE. Together with BFD, before finishing the VPN routine convergence,
switch the VPN traffic to the protection path. By this way , solve the problems about
recovering time of faulty node and the number of the routing carried by the faulty node.
Save the service interruption time of faulty node.
For the schematic diagram of VPN FRR protection, see Figure 5-14. If PE1 connecting
to CE1 transfers the message, PE1 can add the working routine message of PE2 in
the transferring item, meanwhile, it adds the protection routine message of PE3 in the
transferring item. If the PE2 is faulty, after PE1 gets the message that the working LSP
is disable by BFD check mechanism, PE1 will transfer the service through the protection
touting in the transferring item. So Perform the fast convergence when the PE2 is faulty.
5-13

Figure 5-14 Schematic Diagram of VPN FRR Protection
RSVP-TE FRR
RSVP-TE FRR can only protect single node or single link by bypass mode. Multi Bypass
tunnel protect the working tunnel. A is the head node of the working tunnel, B and C
are head nodes of Bypass tunnel. Bypass1 protects the link between B and C, Bypass2
protects the link between C and D. For the schematic diagram of RSVP-TE FRR protection,
see Figure 5-15.
Figure 5-15 Schematic Diagram of RSVP-TE FRR Protection
5-14

5.2.8 RSVP-TE Path-Option Protection

ZXCTN 6120S supports RSVP-TE Path-Option protection.
RSVP-TE Path-Option is used to improve RSVP-TE HotStandby protection. If the working
and protection LSPs are both fault, the service will be interrupted even there is accessible
routing. Under this condition, multi path-option is necessary.
Path1 work LSP (A-B-C-D) and Path1 HSB LSP (A-E-F-G-H-D) form a Hot-standby
protection group. If Path1 work LSP and Path1 HSB LSP are faulty, the service can be
protected by Path2 work LSP, see Figure 5-16.
Figure 5-16 Schematic Diagram of RSVP-TE Path-Option Protection
At the engineering application, multi path-options can be used as the supplementary

protection of RSVP-TE Hotstandby, so as to provide more effective routing protection.
5.2.9 RSVP-TE Hot-Standby Protection

ZXCTN 6120S supports RSVP-TE hot-standby protection.
RSVP-TE hot-standby protection is to configure two LSPs for a service. Once the working
LSP is faulty, the service is switched to the protection LSP, that is RSVP-TE Hot-Standby.
For the schematic diagram of RSVP-TE hot-standby protection, see Figure 5-17
5-15

Figure 5-17 Schematic of RSVP-TE Hot-Standby Protection
The working LSP and protection LSP are configured between PE1 and PE2. The LSP
BFD detection function is configured on the working LSP. In general, the service between
PE1 and PE2 is carried by the working LSP. If the working LSP is faulty, the BFD detects
the failure and sends alarm indication to PE1. PE1 triggers the switch after receiving the
alarm. Then the service is switched to the protection LSP.
Note:
During application, in order to guarantee the BFD can detect the fault as soon as possible,
the bidirectional routing of BFD between PE1 and PE2 should be consistent.
5.2.10 LAG Protection

The ZXCTN 6120S supports Link Aggregation Group (LAG) protection. The LAG
protection is to bind multiple Ethernet interfaces with the same properties to one logical
interface, to realize the load sharing of the Ethernet signals on the links, see Figure 5-18.
5-16

Figure 5-18 Ethernet LAG Protection (Normal Status)
If some member link in the aggregation group is faultyy, the service signals on the faulty
link are loaded by other normal links to protect services, see Figure 5-19.
Figure 5-19 Ethernet LAG Protection (Faulty Status)
5.2.11 STP
The ZXCTN 6120S supports various STP protocols to avoid network looping, including
Multiple Spanning Tree Protocol (MSTP) defined by IEEE802.1s, Single Spanning Tree
Protocol (SSTP) defined by IEEE802.1d, and Rapid Spanning Tree Protocol (RSTP)
defined by IEEE802.1w.
The STP protocol runs on the interface of the network switch. It prescribes that the switch
exchanges configuration information with other switches in the fixed time interval. The
network topology structure can be modified by modifying the interface status of switches
(forwarding or blocked) to optimize the data transmission path and avoid redundant paths
caused by network looping. If the network topology changes, the status of the original
redundant switch interface can quickly migrate.
5-17

5-18

Chapter 6
Interfaces
Table of Contents
Board Service Interfaces ............................................................................................6-1
External Interfaces .....................................................................................................6-1
6.1 Board Service Interfaces

For the service interface types supported by the ZXCTN 6120S, refer to Table 6-1.
Table 6-1 ZXCTN 6120S Board Interface Types
Interface Interface Name Interface ID Interface Type

Position
E1E16 E1 interface 1 to 16 Type-D 64-core 2 mm-spacing bent

PCB crimp shield socket (pin)
EIFGE8 FE electrical interface LA1, SP1 to LA8, RJ45

SP8
OEIFGE GE/FE optical Tx, Rx LC (SFP module)

interface
GE/FE electrical LA1/5, SP1/5 to RJ45

interface LA4/8, SP4/8
OIFGE8 FE optical interface Tx, Rx LC (SFP module)
FE electrical interface LA5, SP5 to LA8, RJ45

SP8
OIGE8 GE/FE optical Tx, Rx LC (SFP module)

interface
OIXG1 10GE optical interface Tx, Rx LC (SFP+ module)
OIXG2 10GE optical interface Tx, Rx LC (SFP+ module)
6.2 External Interfaces

Interfaces Descriptions
NMS interface ZXCTN 6120S provides one Qx interface for managing the equipment remotely.
The Qx interface is located on the system service main board. It uses the Ethernet
electrical interface of RJ45 type. The interface rate is self-adaptive.
6-1

Interfaces Descriptions
Local ZXCTN 6120S provides one external Local Craft Terminal (LCT) interface for the
Maintenance commissioning and maintenance of the local NEs.
Interface LCT interface is located on the system service main board. It uses the Ethernet
interface. The type of the interface is RJ45, and the rate is self-adaptive.
Alarm The ALM interface of the ZXCTN 6120S is located on the system service main
Interface board. It uses the Ethernet electrical interface of RJ45 type.
Each channel of alarm signals can be configured to alarm input signals, alarm output
signals, or alarm cascade input signals.
GPS Time Both the service main board and GPCB clock board provide two Global Positioning
Interface/BITS System (GPS) time interfaces/BITS interfaces.
Interface The GPS time interface/BITS interface of the service main board uses the Ethernet
electrical interface of RJ45 type.
The GPS time interface/BITS interface of the ZXCTN 6120S has the following
functions:
l Provides one BITS clock output (2.048 Mbit/s or 2.048 MHz) interface.
l Provides one BITS clock input (2.048 M bit/s or 2.048 MHz) interface.
l Provides the input of 1-path phase synchronization information and absolute
time for receiving time synchronization information.
l Provides the output of 1-path phase synchronization information and absolute
time for sending time synchronization information.
GPS Time Both the service main board and GPCB clock board provide GPS time interface.
Interface It uses the Ethernet electrical interface of RJ45 type.
The GPS time interface of the ZXCTN 6120S has the following functions:
l Provides 1-path BITS clock output (2.048 Mbit/s or 2.048 MHz) interface.
l Provides 1-channel BITS clock input (2.048 Mbit/s or 2.048 MHz) interface.
l Provides the input of 1-channel phase synchronization information and absolute
time for receiving time synchronization information.
l Provides the output of 1-channel phase synchronization information and
absolute time for sending time synchronization information.
1. The service main board supports two channels of GPS time signals. One is provided by the GPS time
interface (silkscreened as GPS), the other one is provided by the GPS time interface/BITS interface
(silkscreened as GPS/BITS).
6-2

Chapter 7
Networking Applications
Table of Contents
Service Networking Application ..................................................................................7-1
Integrated Solutions ...................................................................................................7-8
7.1 Service Networking Application

7.1.1 MPLS L2 VPN Application
7.1.1.1 EPL Networking Application
Ethernet Private Line (EPL) has two service access points, used to point-to-point
transparently transmit users’ Ethernet MAC frames. Each EPL service can contain
one Customer Interface Point (CIP) and one Virtual Interface Point (VIP) respectively
on source node and sink node. EPL services are carried on private tunnels. Different
services cannot share UNI interface, CIP, VIP, PW and tunnel. L2 switching function and
MAC learning capability are not needed for point-to-point transmission.
For a typical network architecture of an EPL service, see Figure 7-1. The Fast Ethernet
(FE) services between users CE1 and CE2 are transparently transmitted through devices
NE1 and NE10 and intermediate sites NE2, NE4, NE5, NE6, NE7 and NE9.
7-1

Figure 7-1 EPL Service Application Diagram
• The ZXCTN 6120S is used

at the access layer.
7.1.1.2 EVPL Networking Application

The essential difference between EVPL and EPL lies in that as for the former, different
services can share the same UNI port. Therefore, VLAN ID or other mechanisms shall
be used to distinguish data of different users. Each EVPL service contains one CIP and
one VIP on source node and sink node. Different services cannot share CIP, VIP and PW.
Tunnel can be shared or used exclusively in service transmission. To provide different
service qualities to different users, it needs to use corresponding QoS mechanism. EVPL
is also a point-to-point service.
For a typical application of EVPL service networking, see Figure 7-2. Services FE1 and
FE2 between users CE1 and CE2 are accessed through UNI ports of PE nodes NE1 and
NE10. FE1 and FE2 are isolated through VLAN's, allocated with exclusively used CIPs,
VIPs and PWs, and transmitted through tunnel between NE2, NE4, NE5, NE6, NE7 and
NE9.
7-2

Chapter 7 Networking Applications
Figure 7-2 EVPL Service Application Diagram

7.1.1.3 EPLAN Networking Application

EPLAN belongs to multipoint-to-multipoint Ethernet service. Two or more points are
involved for service connectivity. Each EPVLAN service can contain CIPs and VIPs on
source node and sink node. EPVLAN services are carried on private tunnels. Different
services cannot share UNI interface, CIP, VIP, PW and tunnel. Since multiple nodes are
involved, it is needed to forward data based on MAC addresses and thus MAC learning
function and L2 switching capability are necessary.
For a typical application of EPLAN service networking, see Figure 7-3. Exclusive UNI ports
are used on PE nodes NE1, NE2 and NE11 for FE1 service among users CE1, CE2 and
CE3. 1 CIP and 2 VIPs are enabled on each PE node. PW and tunnel are exclusively used
in transmission. FE2 service among users CE1, CE2 and CE3 is similar to FE1 service
except for different UNI port, CIP, VIP, PW and tunnel.
7-3

Figure 7-3 EPLAN Service Application Diagram

7.1.1.4 EVPLAN Networking Application

From the point of view of user, EVPLAN makes the carrier's network look like one LAN. The
essential difference between EPLAN and EVPLAN services is that as for the former, UNI
port can be shared and tunnel can be shared or used exclusively in service transmission.
EVPLAN owns specific bandwidth attribute, protection attribute and availability attribute,
as well as MAC learning capability and data forwarding capability.
For a typical application of EVPLAN service networking, see Figure 7-4. Services FE1
and FE2 between users CE1, CE2 and CE3 are accessed through UNI ports of PE nodes
NE1, NE2 and NE11. FE1 and FE2 are isolated through VLAN's, allocated with exclusively
7-4

used CIPs, VIPs and PWs, and transmitted through the same tunnel, thus implementing
isolation of services FE1 and FE2.
Figure 7-4 EVPLAN Service Application Diagram

7.1.1.5 EPTREE Networking Application

EPTREE is a point-to-multipoint service. Two or more points are involved for service
connectivity. In the topology structure, multiple point-to-point connections converge on
one Ethernet physical interface of a central node. Where central node is the root node
and other nodes are leaf nodes. Leaf node can only communicate with root node and leaf
nodes cannot intercommunicate.
Each EPTREE service can contain multiple CIPs and VIPs on source node and sink node.
EPVLAN services are carried on private tunnels. Different services cannot share UNI
7-5

interface, CIP, VIP, PW and tunnel. L2 switching function and MAC learning capability are
not needed for point-to-point transmission.
For a typical network architecture of an EPTREE service, see Figure 7-5. Services FE
of users CE1 and CE2 converge on core switch NE5 through network. On convergence
node NE5, CIP port is the root node and ports VIP1 and VIP2 are leaf nodes. On NE1 and
NE10, CIP port is the root node and VIP port is leaf node.
Figure 7-5 EPTREE Service Application Diagram

7.1.1.6 EVPTREE Networking Application

Services FE of users CE1 and CE2 are aggregated to core switch NE5 through network.
On convergence node NE5, CIP port is the root node and ports VIP1 and VIP2 are leaf
nodes. On NE1 and NE10, CIP port is the root node and VIP port is leaf node.
For a typical network architecture of an EVPTREE service, see Figure 7-6. Services FE1
and FE2 of users CE1 and CE2 converge on core switch NE5 through network. Services
FE1 of users CE1 and CE2 converge on UNI port of NE5 and services FE2 of users CE1
7-6

and CE2 converge on UNI port of NE5. On convergence node NE5, CIP1, and CIP2 of
NE5 are used as root node and VIP1, VIP2, VIP3 and VIP4 are used as leaf nodes. On
NE1 and NE10, ports CIP1 and CIP2 are used as root node and ports VIP1 and VIP2 are
used as leaf nodes. Services are isolated through VLAN tags on UNI port.
Figure 7-6 EVPTREE Service Application Diagram

7.1.2 TDM Service Networking Application

The ZXCTN 6120S provides E1 tributary simulation board for accessing TDM E1 service.
TDM function are used for mobile voice services and enterprise private line services. The
mobile device and enterprise private line access the ZXCTN 6120S through the TDM
service interface. Then, the ZXCTN 6120S encapsulates TDM services to PWs and sends
to the remote end through the network.
7-7

For a typical network architecture of a TDM service, see Figure 7-7. Company 1 and
company 2 send voice services and mobile services to each other through NE2 and NE3.
User services are converged on NE4 and then sent to the convergence layer.
Figure 7-7 TDM Service Application Diagram
7.2 Integrated Solutions

7.2.1 Mobile Backhaul
The ZXCTN 6120S is located on the access layer of metropolitan area transmission
network. It can be used with other equipment on ZTE convergence layer to form a hybrid
network to transmit the information between the base station and base station controller.
Using general packet switch as the core, the ZXCTN 6120S provides various interfaces,
and supports multiple services, and fully meets bearing demands of the mobile Backhaul.
For a typical network architecture of mobile Backhaul, see Figure 7-8. The ZXCTN 6120S
is applicable to access layer.
7-8

Figure 7-8 Application of ZXCTN 6120S in Mobile Backhaul

The networking application of ZXCTN 6120S in mobile Backhaul has the following features:
l Simulates various 2G/3G/LTE peer-to-peer services in Backhaul network through
PWE3.
l Supports efficient statistical multiplexing, meets the requirements of long-term
co-existence to guarantee the smooth evolution of the network.
l Provides carrier-level network protection and end-to end hierarchical OAM to
guarantee the high reliability of the Backhual service.
l Meets the various transmission requirements such as jitter and delay of different levels
of Backhaul services though service classification, priority marking, queue scheduling,
and peer-to-peer QoS deployment.
l Supports synchronous Ethernet (G.8261) and IEEE 1588V2 clock synchronization
technology, and meets the peer-to-peer lock synchronization requirement of Backhaul
network.
7.2.2 Application at LTE Network Stage

The ZXCTN 6120S can perfectly satisfy the requirements of the LTE) network to implement
the flatness of the mobile network. Meanwhile, the ZXCTN 6120S uses various interface at
7-9

the access layer to meet the requirements of the downstream service traffic of the mobile
base station.
Application Scheme
For a typical application in the LTE network, see Figure 7-9.
Figure 7-9 Application at LTE Network Stage

Application Features
Application at LTE network stage has the following features:
l It meets the characteristics of flat LTE network in logic, adapts to LTE service bearing,
and meanwhile is completely compatible with 3G services.
l It implements function distribution for LTE service network and P2P characteristics,
and supports L3 function and flexible scheduling of X2 and S1.
l It supports L1/L2/L3 function, meets the demand of carrying full services, and
implements Fixed Mobile Convergence (FMC).
l The application provides SDH network reliability, supports point-to-point OAM and
protection, shows high QoS/SLA support, and reduces OPEX.
l It supports to synchronous Ethernet (G.8261) and IEEE 1588 V2 clock synchronization
technology.
l It owns special signaling control plane, which make configuration of network and OAM
more flexible.
7-10

Chapter 8
Technical Specifications
Table of Contents
System Performance..................................................................................................8-1
Physical Performance ................................................................................................8-3
Power Consumption Specifications ............................................................................8-4
Grounding Requirements ...........................................................................................8-4
Lightning Protection Requirements.............................................................................8-7
EMC Requirements ....................................................................................................8-8
Reliability Specifications ............................................................................................8-9
Security Authentication Requirement..........................................................................8-9
Interface Specifications ............................................................................................8-10
8.1 System Performance

For the system performance specifications of the ZXCTN 6120S, refer to Table 8-1.
Table 8-1 System Performance Specifications of the ZXCTN 6120S
Item Performance
Specification
L2 feature MAC address table size 64K
MAC address learning speed 1500/s
MAC address filtering entry quantity 64 K
Static MAC address quantity 64K
QinQ 32K
VLAN quantity 4K
ARP table quantity 16K
ARP table learning speed 200/s
ARP table aging time 1s
L3 feature IPv4 host routing table 16K
IPv4 subnet routing table 32K
IPv4 static route table quantity 1K
L3 interface table 2K
8-1

Item Performance
Specification
Protocol LACP aggregation speed <200 ms

performance
Maximum number of LACP aggregation groups 12
Maximum interface number of each LACP aggregation 8

group
L2 multicast quantity 512
L2 multicast member quantity 8K
L2 multicast joining and leaving time 50/s
Spanning tree instance quantity 256
Spanning tree aggregation item 1s
OSPF neighbor quantity per node 64
OSPF area quantity per node 10
Maximum external route brought by OSPF 1K
IS-IS neighbor quantity per node 64
BGP neighbor quantity per node 64
LDP neighbor quantity per node 64
QoS Ingress ACL entries 2K
Egress ACL entries 512
DS template quantity 16
MPLS MPLS forwarding table 16K

performance
Static PW quantity (L2VPN) 4K
Static LSP quantity 4K
LDP LSP quantity 2K
RSVP-TE LSP quantity 2K
Service VLL/E-LINE quantity 2K

performance
VPLS/E-LAN/E-TREE quantity 256
Total MAC number of VPLS/E-LAN/E-Tree instance 64K
MAC quantity per VPLS/E-LAN/E-Tree instance 64K
AC quantity accessed by each VPLS/E-LAN instance 16
Member quantity per VPLS/E-LAN instance 64
L3 VPN VRF instance quantity 256
L3 VPN member quantity 16K
8-2

Chapter 8 Technical Specifications
Item Performance
Specification
Maximum IPv4 route number of each L3 VPN VRF 32K/16K (subnet

route/host route)
TDM E1 quantity E1: 16
OAM and Ethernet OAM instance quantity (fast-speed) 1K

protection
Ethernet OAM instance quantity (slow-speed) 512
property
MPLS-TP TMS/TMP/TMC OAM instance quantity 1K
(fast-speed)
MPLS-TP TMS/TMP/TMC OAM instance quantity 1K

(slow-speed)
MPLS-TP linear protection group 512
MPLS-TP ring instance quantity 16
Maximum node number supported by ring network 16

protection
Active/standby switchover time <50 ms
BFD connection quantity 1K
TST quantity/bandwidth quantity 1/200M
1588 OC/BC Slave link quantity 32
8.2 Physical Performance

For the physical performance specifications of the ZXCTN 6120S, refer to Table 8-2.
Table 8-2 Physical Performance Specification of the ZXCTN 6120S
Item Physical Performance

Specification
Equipment physical Subrack (width × height × 45 mm ×440 mm ×199 mm

dimensions depth,mm) (without ear)
Equipment physical Subrack (width × height × 45 mm ×482.6 mm ×199 mm

dimensions depth,mm) (with ear)
Parameters Weight 5 kg
Slot number Total slot number 6
Service slot 2
Noise <55 dB
Earthquake-resistance Resist earthquake of magnitude

9
8-3

8.3 Power Consumption Specifications

The ZXCTN 6120S supports 110 V/220 V AC, -48 V single-input DC, and -48 V
double-input DC power supplies.
One device cannot use the above two power modules at the same time.
For the input voltage specifications of the ZXCTN 6120S, refer to Table 8-3.
Table 8-3 ZXCTN 6120S Input Voltage Specifications
Power Module Input Voltage Voltage Fluctuation Rated Current Maximum

Name Range Power
Consumption
PWA -48 DC -48 V±20% DC 3.0 130
PWDC -48 DC -48 V±20% DC
PWB 110/220 AC 110.0 V to 240.0

V±10% AC
8.4 Grounding Requirements

Requirements for Internal Grounding of Device
l Each board in the device should be connected to the device cover through its front
panel. There should be no electrical connection inside each board.
l The covers of cabinet and subracks should be connected to the protection ground.
Note:
Cabinet is connected to the copper ground busbar in the equipment room through the
protection ground and thus maintains good electronic characteristics. Subrack is firmly
fastened to the cabinet back column for grounding.
Requirements for Grounding in Equipment Room

l If the user equipment room uses common bonding network, the ground resistances
should be no more than 1 Ω.
à When the user equipment room provides the working copper ground strap and
protection copper ground strap respectively, working ground of ZXCTN 6120S is
connected to the working copper ground strap. Ground terminal of the protection
ground and the ground terminal at the left side of the equipment room are
connected to the working ground busbar. Figure 8-1 uses the connection with
DC power as an example.
8-4

Figure 8-1 Electric Power Line and Grounding Cable Diagram (Common
Bonding Network)
à If the user equipment room only provides one grounding busbar, the working
ground, protection ground and the chassis shell of ZXCTN 6120S are all
connected to the grounding copper busbar. Figure 8-2 uses the connection with
DC power as an example.
Figure 8-2 Electric Power Line and Grounding Cable Diagram (Common
Bonding Network)
Note:
If the ZXCTN 6120S is installed in the cabinet, the power cable is connected to the
output port of the power supply of the cabinet, the protection cable is connected to the
protection grounding busbar.
8-5

l If the user equipment room uses independent grounding, the ground resistances
should meet the requirements listed in Table 8-4.
Table 8-4 Grounding Resistance Requirements in Independent Grounding Mode
Item Resistance (Unit: Ω)
AC working ground resistance ≤4
DC working ground resistance ≤4
Protection ground resistance ≤4
Lightning protection ground resistance ≤4
The voltage between protection grounding terminals and working ground terminals
should be smaller than 50 mV.
If independent grounding is used in the user equipment room, the working ground
of the ZXCTN 6120S equipment is connected to the DC working ground, and the
protection ground is connected to the safety protection ground, see Figure 8-3.
Figure 8-3 Electric Power Line and Grounding Cable Diagram (Independent
Grounding)
l Copper busbar with cross section area no less than 120 mm2 shall be used as
grounding busbar or grounding bar for grounding. Galvanized flat steel with the
dimension not less than 40 mm×4 mm can also be used.
l Be sure to use copper lugs, bolts and spring washers to fasten the connections
between the device grounding cable and the grounding busbar or grounding bar.
One bolt can only be used to connect one grounding cable. Determine the dimension
of grounding busbar and the number of screws according to the number of grounding
cables of devices in computer room.
8-6

Note:
If the equipment room provides working ground and protective earth separately, the
working ground and protective earth of the device shall be connected to corresponding
grounding copper busbar. If the equipment room provides only one grounding copper
busbar, the working ground and protective earth of the device can be jointed for grounding.
The ground resistance shall meet the above requirements.
8.5 Lightning Protection Requirements

For the typical lightning protection classes of power supplies of communication devices,
refer to Table 8-5.
Table 8-5 Typical Protection Classes of Power Supply Lightning
Lightning Protection Class Specifications Location of Lightning

Protection Circuit
Class B (Class I) 40 kA (8 μs /20 μs) AC Power Distribution

Panel/Box
Class C (Class II) 20 kA (8 μs /20 μs) DC Power Supply Cabinet
Class D (Class III) 6000 V (combination wave) -48 V Power Rectifier
Lightning Protection Requirements for Power Supply in Central Equipment Room

l Lead AC power cables underground into the equipment room.
l Because AC power distribution panel and DC power cabinet may be placed in the
same equipment room, the distance between Class B and Class C lightning arrestors
must meet the following decoupling distance requirements:
à If the protection ground cable is laid independently, the distance between Class
B and Class C lightning protection arrestors shall not be not less than 5 m.
à If the protection ground cable and power cable are laid in parallel, the distance
between Class B and Class C lightning protection arrestors shall be not less than
15 m.
l If the required decoupling distance cannot be met due to restricted conditions in

the equipment room, install additional decoupling inductance(s) before the Class C
lightning arrestor by 1.5 H/m.
l The ground cables of Class B and Class C lightning arrestors should employ stranded
copper wires with cross section areas no less than 95 mm2 to connect with Main
Earthing Terminal (MET) or Floor Equipotential earthing terminal Board (FEB). Keep
the length of ground cables as short as possible.
8-7

Requirements for Lightning Protection of Devices

l Connect the protection ground cable of ZXCTN 6120S subrack installed in a cabinet
to the protection ground busbar in the cabinet. Use stranded copper wire with cross
section area no less than 16 mm2 for the protection ground cable of the cabinet,
and connect the protection ground with the ground busbar or ground bar (including
column-head power cabinet).
l Short-circuit the protection ground of the transmission device with the DC power
ground, and then connect the protection ground to the protection ground busbar in
the cabinet if the device is powered by DC power source.
l Do not lead the protection ground of the transmission device out of the cabinet and
directly connect it to the ground busbar or ground bar (including column-head power
cabinet) in the equipment room.
l For the requirements of lightning protection, refer to Table 8-6.
Table 8-6 Requirements of Lightning Protection
Lightning Protection Port Requirements Specification
Input port of DC power supply 2 kV (1.2 µs/50 µs)
Inputting/outputting port of signal 1 kV (1.2 µs/50 µs)
8.6 EMC Requirements

For the requirements of EMC, refer to Table 8-7.
Table 8-7 EMC Requirements
Item Standard
ESD Comply with IEC 61000-4-2, GB/T 17626.2

and GR-1998
Radiated Susceptibility (RS) Immunity Comply with IEC 61000-4-3, GB/T 17626.3
Electrical DC Power Port Immunity (Direct Comply with IEC 61000-4-4, GB/T 17626.4.
Fast Coupling)
Transient
AC Power Port Immunity (Direct Comply with IEC 61000-4-4, GB/T 17626.4.
(EFT)
Coupling)
Immunity
Signal Cable Port and Control Cable Comply with IEC 61000-4-4, GB/T 17626.4.
Port Immunity (With Capacitive
Coupling Clamp)
8-8

Item Standard
Lightning Lightning Lightning Comply with IEC 61000-4-5, GB/T 17626.5.

Surge Surge surge immunity
Immunity Immunity specifications of DC
of Power power supply
Supply
Lightning Comply with IEC 61000-4-5, GB/T 17626.5.
surge immunity
specifications of AC
power supply
CS (Conducted Susceptibility) Immunity Comply with IEC 61000-4-6, GB/T 17626.6.
Voltage Dip and Short Interruption Immunity This item only applicable to DC power supply,
comply with IEC 61000-4-11, GB/T 17626.11.
Interfer- conducted emission The specifications conform to Class A

ence Perfor- requirements specified by CISPR22.
radiated emission
mances
8.7 Reliability Specifications

The reliability specifications of the ZXCTN 6120S include the product lifetime, board failure
rate, Mean Time To Recovery (MTTR), and Mean Time Between Failures (MTBF ).
For the reliability specifications of the ZXCTN 6120S, refer to Table 8-8.
Table 8-8 7 Reliability Specifications
Item Description
Product lifetime No less than 20 years
Board failure rate Less than 0.2%
MTBF 250000 hours
MTTR <0.5 hours
Reliability ≥99.999%
Hot plugging All boards support hot plugging
Power supply redundancy backup DC/AC 1+1 redundant protection
Heat load full load (BTU/h) 108
8.8 Security Authentication Requirement

ZXCTN 6120S complies with the security authentication requirements listed in Table 8-9.
8-9

Table 8-9 Security Authentication Requirements
Authentication Items Authentication Standards
EMC CISPR 22 Class A
EN55022 Class A
ETSI EN 300386
FCC Part 15
GB/T 9254 Class A
EN 61000-4-2
EN 61000-4-3
EN 61000-4-4
EN 61000-4-5
EN 61000-4-6
Security IEC 60950-1
EN 60590-1
UL 60950-1
GB/T 4943
Laser security IEC 60825-1
IEC 60825-2
EN 60825-1
EN 60825-2
GB/T 7247
Environmental protection ISO 3744
ETS 300 753
IEC 60068-2-1
IEC 60068-2-2
IEC 60068-2-6
IEC 60068-2-14
IEC 60068-2-29
IEC 60068-2-78
8.9 Interface Specifications

For the specifications of the E1 interfaces, refer to Table 8-10.
8-10

Table 8-10 E1 Interface Specifications
Item Performance Specification
Nominal Rate 2.048 Mbit/s
Coding Type High Density Bipolar of order 3 (HDB3)
Allowable attenuation at output port 0 dB to 6 dB, 1024 Hz

(square-root attenuation)
Permissible input interface frequency >±50 ppm

deviation
Bit ratio tolerance at the output port <±50 ppm
Jitter and wander at the output port Complies with ITU‐T G.823 Table 1/Figure 1
Pulse shape at output port Complies with ITU‐T G.703 Figure 15
Anti-interference capability at input port 18 dB

(SNR)
Input jitter/wander tolerance Complies with ITU‐T G.823 Figure 13
Input port reflection attenuation Complies with ITU‐T G.703 §9.3
For the specifications of 10Base-T/100Base-TX/1000Base-T interfaces, refer to Table

8-11.
Table 8-11 10/100Base-TX Interface Specifications
Item Specifications
Compliant standard IEEE 802.3z
Nominal rate 10/100/1000 Mbit/s
Coding Type 10 Mbit/s Manchester encoding
100 Mbit/s MLT-3 coding

1000 Mbit/s
Interface RJ45
Transmission distance The Max. distance is 100 m
Transmission Media Category-5 Unshielded Twisted Pairs (UTP)
For the specifications of FE optical interfaces, refer to Table 8-12.
Table 8-12 FE Optical Interface Specifications
Item Specifications
Nominal rate 100 Mbit/s
Optical interface type 100BASE-LX 100BASE-LX 100BASE-ZX

(10 km) (40 km) (80 km)
Connector type LC LC LC
8-11

Item Specifications
Optical fiber type Single mode Single mode Single mode
Central wavelength 1310 nm 1310 nm 1550 nm
Average transmitting -11.5 dBm to -8 dBm -5 dBm to 0 dBm -5 dBm to 0 dBm

optical power
Receiving sensitivity ≤-31 dBm ≤-34 dBm ≤-37 dBm
For the specifications of GE optical interfaces, refer to Table 8-13.
Table 8-13 GE Optical Interface Specifications
Item Specifications
Optical interface 1000BASE-SX 1000BASE-LX 1000BASE-LX 1000BASE-ZX

type (0.5 km) (10 km) (40 km) (80 km)
Connector type LC LC LC LC
Optical fiber type Multi-mode Single mode Single mode Single mode
Central 850 nm 1310 nm 1310 nm 1550 nm

wavelength
Average -9.5 dBm to -4 -9 dBm to -3 dBm -4 dBm to 5 dBm 0 dBm to 5 dBm

transmitting dBm
optical power
Receiving ≤-17 dBm ≤-20 dBm ≤-22 dBm ≤-22 dBm

sensitivity
For the specifications of 10GE optical interfaces, refer to Table 8-14.
Table 8-14 10GE Optical Interface Specifications
Item Specifications
Optical interface type 10GBASE-SR 10GBASE-LR 10GBASE-ER 10GBASE-ZR

(0.3 km) (10 km) (40 km) (80 km)
Connector type LC LC LC LC
Optical fiber type Multi-mode Single mode Single mode Single mode
Central wavelength 850 1310 1550 1550
Average transmitting -7.3 to -1 -5 to –1 0 to 2 1 to 4

optical power
Receiving sensitivity ≤-11.1 ≤-14 ≤-16.5 ≤-26
8-12

Chapter 9
Environment Requirements
Table of Contents
Power Supply Requirements ......................................................................................9-1
Operation Environment ..............................................................................................9-1
Transportation Environment .......................................................................................9-3
Storage Environment..................................................................................................9-5
9.1 Power Supply Requirements

The ZXCTN 6120S supports AC 110 V/220 V and DC -48 V power supply. For the range
of input voltage and power supply requirements, refer to Table 9-1.
Table 9-1 Power Supply Requirements of the ZXCTN 6120S
Power Input Voltage Voltage Range (V) Max. Input Max. Output Fuse spec-
Module (V) Current (A) Power (W) ification
Code (A)
PWA -48 DC -48±20% DC 3.0 ≥200 8
PWB 110/220 AC 110.0 to 240.0±10% 1.5 ≥200

AC, 50/60Hz
PWDC -48 DC -48±20% DC 8.8 ≥200
• PWA and PWB boards can not be used at the same time.
9.2 Operation Environment

Climate Requirement
For the temperature and relative humidity requirements during the operation of the
equipment, refer to Table 9-2. For the other climate requirements, refer to Table 9-3.
Table 9-2 Temperature and Humidity Requirements (Operation Environment)
Item Requirement
Environment temperature Long term running: -5 ℃ to +50 ℃
Short term running: -10 ℃ to +55 ℃
9-1

Item Requirement
Relative Humidity Long term running: 5% to 90%
Short term running: 5% to 95%
• The temperature and humidity are measured 1.5 m above the floor and 0.4 m in front of the equipm
ent.
• Short term running means that the equipment works continuously for no more than 96 hours and
works for no more than 15 days in one year.
Table 9-3 Requirements for Climate (Operation Environment)
Item Specifications
Altitude ≤ 4000 m
Air pressure 70 kPa to 106 kPa
Temperature variance ratio ≤30 ℃/h
Solar radiation ≤700 W/s2
Thermal radiation ≤600 W/s2
Wind speed ≤5 m/s
Biology Environment
l Avoid the propagation of animalcules, such as fungi and mold.
l Prevent rodents, such as mice.
Air Cleanness Requirement

l There should be no explosive, electrically conductive, magnetically conductive or
corrosive dust in the equipment room.
l For the requirements for the concentration of mechanical active materials in the
transportation environment, refer to Table 9-4.
Table 9-4 Requirements for Concentration of Mechanical Active Materials in

Transportation Environment (Operation Environment)
Mechanical Active Substance Concentration
Dust particle ≤3×105 particle/m3
Suspended dust ≤5.00 mg/m3
Degraded dust ≤20.0 mg/m2 h
Sand ≤300 mg/m3
l For the requirements of active chemical substance density, refer to Table 9-5.
9-2

Chapter 9 Environment Requirements
Table 9-5 Requirements for Concentration of Chemical Active Materials (Operation

Environment)
Chemical Active Substance Concentration (mg/m3)
SO2 ≤ 0.30
H2S ≤ 0.10
NO2 ≤ 0.50
NH3 ≤ 3.00
Cl2 ≤ 0.10
HCl ≤ 0.10
HF ≤ 0.01
O3 ≤ 0.05
NOx ≤ 0.50
9.3 Transportation Environment

Climate Requirement
For the requirements for climate during the transportation of the ZXCTN 6120S, refer to
Table 9-6.
Table 9-6 Requirements for Climate (Transportation Environment)
Item Specifications
Altitude ≤4000 m
Temperature -50 ℃ to +70 ℃
Temperature variance ratio ≤1 ℃/min
Relative humidity 10% to 100%
Hot radiation ≤600 W/s2
Wind speed ≤20 m/s
Waterproof Requirement
l Ensure that the packing of the equipment is in good condition without any damages.
l The transportation tool should have rainwater-proof measures, so that the rainwater
will not damage the pack of the equipment.
l If the equipment should be stored outside, the requirements are listed as follows:
9-3

à Ensure that the packing of the equipment is in good condition without any
damages.
à Rainwater-proof measures should be taken, so that the rainwater will not damage
the pack of the equipment.
à Ensure there is no water in the transportation tool.
Biology Environment
l Avoid the propagation of microorganism, such as fungi or mould.
l Avoid rodent (such as mouse) to damage the equipment.

l For the requirements for concentrations of mechanical active substances, refer to
Table 9-7.
Table 9-7 Requirements for Concentrations of Mechanical Active Substances

(Transportation Environment)
Suspended dust No special requirements
Degraded dust ≤3.0 mg/m2•h
Sand ≤100 mg/m3
l For the requirements for concentrations of chemical active substances, refer to Table
9-8.
Table 9-8 Requirements for Concentrations of Chemical Active Substances

(Transportation Environment)
Chemical Active Substance Concentration
SO2 ≤0.30 mg/m3
H2S ≤0.10 mg/m3
NO2 ≤0.50 mg/m3
NH3 ≤1.00 mg/m3
Cl2 ≤0.10 mg/m3
HCI ≤0.10 mg/m3
HF ≤0.01 mg/m3
O3 ≤0.05 mg/m3
9-4

Chapter 9 Environment Requirements
9.4 Storage Environment

Climate Requirement
For the climate requirements for storing the ZXCTN 6120S, refer to Table 9-9.
Table 9-9 Requirements for Climate (Storage Environment)
Item Specifications
Altitude ≤4000 m
Temperature -40 ℃ to +70 ℃
Temperature variance ratio ≤1 ℃/min
Relative humidity 5% to 95%
Hot radiation ≤600 W/s2
Wind speed ≤20 m/s
Waterproof Requirement
l Store the equipment indoor.
l Ensure that there is no water on the storage room floor, so that the water will not leak
on the packing container of the equipment.
l The storage position should be far away from the possible leaking positions of the
automatic fire fighting equipment and the heating system.
l If the equipment should be stored outside, the requirements are listed as follows:
à Ensure that the packing of the equipment is in good condition without any
damages.
à Rainwater-proof measures should be taken, so that the rainwater will not damage
the pack of the equipment.
à Ensure there is no water on the floor or in the packing container of the equipment.
à Do not expose the packing to direct sunlight.
Biology Environment
l Avoid the propagation of microorganism, such as fungi or mould.
l Avoid rodent (such as mouse) to damage the equipment.

l For the requirements of concentrations of mechanical active substances, refer to Table
9-10.
9-5


(Storage Environment)
Suspended dust ≤5.00 mg/m3
Degraded dust ≤20.0 mg/m2•h
Sand ≤300 mg/m3
l For the requirements for concentrations of chemical active substances, refer to Table
9-11.

(Storage Environment)
Chemical Active Substance Concentration
SO2 ≤0.30 mg/m3
H2S ≤0.10 mg/m3
NO2 ≤0.50 mg/m3
NH3 ≤1.00 mg/m3
Cl2 ≤0.10 mg/m3
HCI ≤0.10 mg/m3
HF ≤0.01 mg/m3
O3 ≤0.05 mg/m3
9-6

Appendix A
Standards and
Recommendations
For the standards and recommendations that the ZXCTN 6120S complies with, refer to
Table A-1.
Table A-1 ZXCTN 6120S Standards and Recommendations
Recommendation (Standard) Description
IET-F RFC1661 Point-to-Point Protocol
IET-F RFC1990 Multilink PPP
IET-F RFC2686 Multi-Class Extension to Multi-Link PPP
IET-F RFC3916 Requirements for PWE3
IET-F RFC3985 PWE3 Architecture
IET-F RFC4026 Provider Provisioned Virtual Private Network (VPN) Terminology
IET-F RFC4446 IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)
IET-F RFC4448 Encapsulation Methods for Transport of Ethernet Over MPLS Networks
IET-F RFC4553 Using Packet to Transport TDM Service with Unknown Structure
IET-F RFC4664 L2VPN Architecture
IET-F RFC4665 Requirements for L2VPN
IET-F RFC4717 Encapsulation Methods for Transport of ATM Over MPLS Networks
IET-F RFC4816 ATM cell transparent transmission service
IETF RFC5086 TDM Circuit Emulation Service with Unknown Structure over Packet Switch
Network
ITU-T G0.703 Physical/Electrical Characteristics Of Hierarchical Digital Interfaces
ITU-T G0.704 Synchronous Frame Structures Used at 1544, 6312, 2048, 8448, and
44736kbit/s Hierarchical Levels
ITU-T G0.706 Frame Alignment and Cyclic Redundancy Check (CRC) Procedures
Relating to Basic Frame Structures Defined in Recommendation G.704
ITU-T G0.707 Network Node Interface (V2003) for the Synchronous Digital Hierarchy
(SDH)
ITU-T G0.773 Protocol Suites for Q Interfaces for Management of Transmission Systems
ITU-T G0.774 SDH Information Model for the Network Element View
A-1

ITU-T G.774.01 SDH Performance Monitoring for Network Element View
ITU-T G.7740.02 SDH Configuration of the Payload Structure For the Network Element View
ITU-T G.7740.03 SDH Management of Multiplex-Section Protection for the Network Element
View
ITU-T G.7740.05 SDH Connection Monitoring for the Network Element View
ITU-T G.7740.06 SDH Unidirectional Performance Monitoring for the Network Element View
ITU-T G.7740.07 SDH Low-Order Path Trace and Interface Tag Management for the Network
Element View
ITU-T G0.7041 Generic Framing Procedure
ITU-T G0.7042 Virtual Cascade Signal Link Capacity Adjustment Method
ITU-T G0.780 Vocabulary of Terms for Synchronous Digital Hierarchy (SDH) Networks
and Equipment
ITU-T G0.783 Characteristics of Synchronous Digital Hierarchy (SDH) Equipment

Functional Blocks
ITU-T G0.784 Synchronous Digital Hierarchy (SDH) Management
ITU-T G0.803 Architecture of Transport Networks Based on the Synchronous Digital

Hierarchy (SDH)
ITU-T G0.805 Generic Functional Architecture of Transport Networks
ITU-T G0.810 Terms and Definitions for Synchronous Digital Hierarchy (SDH) Networks
ITU-T G0.811 Timing Characteristics of Primary Reference Clocks
ITU-T G0.812 Timing Characteristics of SDH Node Slave Clocks
ITU-T G0.813 Timing Characteristics of Slave Clocks Suitable for Operation in SDH
Equipment
ITU-T G0.823 The Control of Jitter and Wander Within Digital Networks Which are Based
on the 2048 kbit/s Hierarchy
ITU-T G0.825 The Control of Jitter and Wander Within Digital Networks Which are Based
on the Synchronous Digital Hierarchy (SDH)
ITU-T G0.826 Error Performance Parameters and Objectives for International, Constant
Bit Rate Digital Paths at or above the Primary Rate
ITU-T G0.831 Management Capabilities of Transport Networks Based on the Synchronous

Digital Hierarchy (SDH)
ITU-T G0.832 Transport of SDH Elements on SDH Networks - Frame and Multiplexing
Structures
ITU-T G0.841 Types and Characteristics of SDH Network Protection Architectures
ITU-T G0.842 Interworking of SDH Network Protection Architectures
A-2

Appendix A Standards and Recommendations
ITU-T G0.957 Optical Interfaces for Equipment and Systems Relating to the Synchronous
Digital Hierarchy (SDH)
ITU-T G0.958 Digital Line Systems Based on the Synchronous Digital Hierarchy for Use
on Optical Fibre Cables
ITU-T G0.8101 Terms and Definitions for Transport MPLS
ITU-T G0.81100.1 Architecture of Transport MPLS (MPLS-TP) Layer Network
ITU-T G0.8112 Transport MPLS Hierarchy Interfaces
ITU-T G0.8113 Requirement for OAM Functionality in MPLS Networks
ITU-T G0.8114 OAM Mechanism in MPLS-TP Networks
ITU-T G0.8121 Characteristics of Transport MPLS Equipment
ITU-T G0.8131 Linear Protection Switching for Transport MPLS (MPLS-TP) Networks
ITU-T G0.8132 Shared Protection Ring
ITU-T G0.8261 Timing and Synchronization Aspects in Packet Networks
ITU-T G0.8262 Timing Characteristics of SDH Equipment Slave Clocks (SEC)
ITU-T I.361 B-ISDN ATM Layer Specification
ITU-T K.41 Resistibility of Internal Interfaces of Telecommunication Centers to Surge

Overvoltages
ITU-T M.20 Maintenance Philosophy for Telecommunication Networks
ITU-T M.2100 Performance Limits for Bringing-into-Service and Maintenance of

International PDH Paths, Sections and Transmission Systems
Performance limits for bringing-into-service and maintenance of international

ITU-T M.2101
PDH paths, sections and transmission systems
PDH path, section and transmission system and SDH path and multiplex
ITU-T M.2120
section fault detection and localization procedures
ITU-T M.3010 Principles for a Telecommunications management network
ITU-T M.3400 Telecommunications Management Network (TMN) Management Function
MEF 2 Requirements and Framework for Ethernet Service Protection in Metro

Ethernet Networks
MEF 4 Metro Ethernet Network Architecture Framework-part 1: Generic Framework
MEF 6.1 Metro Ethernet Services Definitions Phase 2
MEF 7 EMS-NMS Information Model
MEF 8 Specification of Transmitting PDH Circuit Emulation Services over Metro

Ethernet Network
MEF 9 Test Suite for Ethernet Services at the UNI
A-3

MEF 10.1 Ethernet Services Attributes Phase 2
MEF 11 UNI Requirements and Framework
MEF 13 User Network Interface (UNI) Type 1 Implementation Agreement
MEF 14 Test Suite for Traffic Management Phase 1
MEF 18 Test Suite for Circuit Emulation Services
MEF 19 Test Suite for UNI Type 1
MEF 21 Test Suite for UNI Type 2 Part 1: Link OAM
ITU-T M.2101 Performance Limits and Objectives for Bringing-into-Service and

Maintenance of International SDH Paths and Multiplex Sections
ITU-T M.2120 PDH Path, Section and Transmission System and SDH Path and Multiplex
Section Fault Detection and Localization Procedures
ITU-T M.3010 Principles for a Telecommunications Management Network
ITU-T M.3400 TMN Management Functions
ITU-T Q.811 Lower Layer Protocol Profiles for the Q3 Interface
ITU-T Q0.812 Upper Layer Protocol Profiles for the Q3 Interface
ITU-T Y.1413 TDM-MPLS Network Internetworking-User Interoperation
ITU-T Y.1731 Ethernet OAM Functions and Mechanisms
ITU-T I.432.2 B-ISDN User Network Interface-Physical Layer Specification for 155520
kbit/s and 622080 kbit/s
ITU-T I.432.3 B-ISDN User Network Interface-Physical Layer Specification for -1544kbit/s
and 2048 kbit/s
ITU-T I.761 Inverse multiplexing over ATM (IMA)
IEEE 802.3 Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access
Method and Physical Layer Specifications
IEEE 802.1ad Virtual Bridge Local Area Network
IEEE 802.1ag Virtual Bridge Local Area Network-Connectivity Fault Management (CFM)
IEEE 802.3ah User Access Network MAC Parameter, Physical Layer Parameters and
Management Parameters
IEEE 1588v2 Precision Clock Synchronization Protocol for Networked Measurement and
Control Systems
YDN 099-1998 Optical Synchronous Transmission Network Technology System
YD/T 1238-2000 Technical Requirements for SDH Multi-Service Transport Platform
YD 5083-1999 Interim Provisions for Test of Anti-seismic Performances of Power Supply

Equipment for Telecommunications
A-4

Appendix A Standards and Recommendations
GB 4943 Information Equipment Security Standards
GB 9254 Information Technology Equipment - Radio Disturbance Characteristics -

Limits and Methods of Measurement
GB/T 2423 Basic Environmental Testing Procedures for Electric and Electronic Products
GB/T 4796-1984 Classification of Environmental Parameters and Their Severities of Electric

and Electronic Products
GB 7247.1-2001 Safety of laser Product Part 1: Equipment Classification, Requirements

and User's Guide
GB/T 17618-1998 Information Technology Equipment - Immunity Characteristics - Limits and

Methods of Measurement
GB 17625.1 The Limits for the Harmonic Current Emissions Caused by Low-Voltage
Electrical and Electronic Equipments (Equipment Input Current≤16A per
Phase)
GB 17625.2 Electromagnetic Compatibility -Limitation of Voltage Fluctuations and Flicker

in Low-Voltage Supply Systems for Equipment with Rated Current≤16A
GB/Z 17625.3 Electromagnetic Compatibility -Limitation of Voltage Fluctuations and Flicker

in Low-Voltage Supply Systems for Equipment with Rated Current>16A
GB/T 17626.2 Electromagnetic Compatibility-Testing and Measurement Techniques-

Electrostatic Discharge Immunity Test

Radiated, Radio-Frequency, Electromagnetic Field Immunity Test

Electrical Fast Transient/Burst Immunity Test
GB/T 17626.5 Electromagnetic Compatibility-Testing and Measurement Techniques-Surge

Immunity Test

Immunity to Conducted Disturbances Included by Radio-Frequency Fields
GB/T 17626.8 Electromagnetic Compatibility-Testing and Measurement Techniques-Power

Frequency Magnetic Field Immunity Test

Voltage Dips, Short Interruptions and Voltage Variations Immunity Test
GJB/Z 299B-1998 Reliability Prediction of Electronic Equipment
A-5

A-6

List of Figure
Figure 1-1 ZXCTN 6120S Overview ......................................................................... 1-1
Figure 1-2 Network Application of the ZXCTN 6120S................................................ 1-2
Figure 2-1 Functional Units of the ZXCTN 6120S ..................................................... 2-1
Figure 2-2 Hardware Structure of the ZXCTN 6120S ................................................ 2-3
Figure 2-3 Software Structure Diagram ..................................................................... 2-4
Figure 2-4 Structure of ZXCTN 6120S Main Control Software................................... 2-4
Figure 2-5 Structure of Board Software ..................................................................... 2-5
Figure 3-1 Service Flow of the ZXCTN 6120S........................................................... 3-1
Figure 4-1 VPWS Typical Network Diagram .............................................................. 4-3
Figure 4-2 VPLS Typical Network Diagram ............................................................... 4-4
Figure 4-3 H-VPLS Network Diagram ....................................................................... 4-5
Figure 4-4 MS-PW Application Scenario ................................................................... 4-6
Figure 4-5 Network Architecture of BGP/MPLS L3VPN ............................................ 4-7
Figure 4-6 Cross-Domain MPLS VPN Option A Diagram .......................................... 4-9
Figure 4-7 Cross-Domain MPLS VPN Option B Diagram .......................................... 4-9
Figure 4-8 Typical Network Architecture of L3VPN FRR.......................................... 4-10
Figure 4-9 OAM Implementation Mechanism .......................................................... 4-13
Figure 4-10 Synchronization of IEEE 1588 V2 Clock .............................................. 4-23
Figure 4-11 Application of IEEE 1588 ACR Function .............................................. 4-24
Figure 4-12 Typical Application of Synchronous Ethernet ....................................... 4-25
Figure 5-1 1:1 Path Protection Diagram .................................................................... 5-3
Figure 5-2 1+1 Path Protection Diagram ................................................................... 5-4
Figure 5-3 Wrapping Mode Ring Network Protection Diagram................................... 5-4
Figure 5-4 Schematic Diagram of Shared Ring Protection ....................................... 5-5
Figure 5-5 Typical Network Architecture of Double-loop Dual-node Protection
............................................................................................................... 5-6
Figure 5-6 Typical Network Architecture of Dual-homing Protection .......................... 5-7
Figure 5-7 Typical Network Architecture of MS-PW Protection .................................. 5-7
Figure 5-8 Schematic Diagram of MPLS 1:1 Protection ............................................ 5-8
Figure 5-9 Schematic Diagram of MPLS 1+1 Protection ........................................... 5-9
Figure 5-10 Schematic Diagram of IP FRR Protection............................................. 5-10
Figure 5-11 Schematic Diagram of FRR Link Protection ......................................... 5-11

Figure 5-12 Schematic Diagram of FRR Node Protection ...................................... 5-12

Figure 5-13 Schematic Diagram of PW FRR Protection ......................................... 5-13
Figure 5-14 Schematic Diagram of VPN FRR Protection ........................................ 5-14
Figure 5-15 Schematic Diagram of RSVP-TE FRR Protection ................................ 5-14
Figure 5-16 Schematic Diagram of RSVP-TE Path-Option Protection .................... 5-15
Figure 5-17 Schematic of RSVP-TE Hot-Standby Protection................................... 5-16
Figure 5-18 Ethernet LAG Protection (Normal Status)............................................. 5-17
Figure 5-19 Ethernet LAG Protection (Faulty Status) .............................................. 5-17
Figure 7-1 EPL Service Application Diagram............................................................. 7-2
Figure 7-2 EVPL Service Application Diagram .......................................................... 7-3
Figure 7-3 EPLAN Service Application Diagram........................................................ 7-4
Figure 7-4 EVPLAN Service Application Diagram ..................................................... 7-5
Figure 7-5 EPTREE Service Application Diagram ..................................................... 7-6
Figure 7-6 EVPTREE Service Application Diagram................................................... 7-7
Figure 7-7 TDM Service Application Diagram............................................................ 7-8
Figure 7-8 Application of ZXCTN 6120S in Mobile Backhaul .................................... 7-9
Figure 7-9 Application at LTE Network Stage .......................................................... 7-10
Figure 8-1 Electric Power Line and Grounding Cable Diagram (Common Bonding
Network) ................................................................................................. 8-5
Figure 8-2 Electric Power Line and Grounding Cable Diagram (Common Bonding
Network) ................................................................................................. 8-5
Figure 8-3 Electric Power Line and Grounding Cable Diagram (Independent
Grounding).............................................................................................. 8-6
II

List of Table
Table 2-1 Subrack Structure Description of the ZXCTN 6120S.................................. 2-3
Table 3-1 ZXCTN 6120S Service Processing Capability............................................ 3-2
Table 4-1 MPLS-TP Functions .................................................................................. 4-1
Table 4-2 Functions of Basic MPLS Protocols ........................................................... 4-2
Table 4-3 MPLS-TP Functions Supported by the ZXCTN 6120S ............................ 4-13
Table 4-4 MPLS OAM Function............................................................................... 4-14
Table 4-5 Descriptions of the EFM Function ........................................................... 4-15
Table 4-6 Descriptions of the CFM Function Based on ITU-T Y.1731 ...................... 4-16
Table 4-7 Descriptions of the CFM Function Based on IEEE 802.1ag .................... 4-17
Table 4-8 Basic QoS Functions ............................................................................... 4-18
Table 4-9 Advanced QoS Functions ....................................................................... 4-19
Table 4-10 System Clock Functions ........................................................................ 4-20
Table 4-11 Access Security Supported by ZXCTN 6120S ....................................... 4-26
Table 4-12 Equipment Security Supported by ZXCTN 6120S.................................. 4-26
Table 4-13 Authentication Functions Supported by ZXCTN 6120S.......................... 4-27
Table 5-1 Technology Comparisons Between 1:1 Protection and 1+1
Protection ................................................................................................ 5-2
Table 6-1 ZXCTN 6120S Board Interface Types........................................................ 6-1
Table 8-1 System Performance Specifications of the ZXCTN 6120S ........................ 8-1
Table 8-2 Physical Performance Specification of the ZXCTN 6120S ........................ 8-3
Table 8-3 ZXCTN 6120S Input Voltage Specifications ............................................... 8-4
Table 8-4 Grounding Resistance Requirements in Independent Grounding
Mode ....................................................................................................... 8-6
Table 8-5 Typical Protection Classes of Power Supply Lightning .............................. 8-7
Table 8-6 Requirements of Lightning Protection ........................................................ 8-8
Table 8-7 EMC Requirements ................................................................................... 8-8
Table 8-8 7 Reliability Specifications ......................................................................... 8-9
Table 8-9 Security Authentication Requirements ..................................................... 8-10
Table 8-10 E1 Interface Specifications .................................................................... 8-11
Table 8-11 10/100Base-TX Interface Specifications ................................................ 8-11
Table 8-12 FE Optical Interface Specifications ........................................................ 8-11
Table 8-13 GE Optical Interface Specifications........................................................ 8-12
III

Table 8-14 10GE Optical Interface Specifications.................................................... 8-12

Table 9-1 Power Supply Requirements of the ZXCTN 6120S ................................... 9-1
Table 9-2 Temperature and Humidity Requirements (Operation Environment) ........... 9-1
Table 9-3 Requirements for Climate (Operation Environment)................................... 9-2
Table 9-4 Requirements for Concentration of Mechanical Active Materials in
Transportation Environment (Operation Environment) .............................. 9-2
Table 9-5 Requirements for Concentration of Chemical Active Materials
(Operation Environment) .......................................................................... 9-3
Table 9-6 Requirements for Climate (Transportation Environment)............................ 9-3
(Transportation Environment)................................................................... 9-4
(Transportation Environment)................................................................... 9-4
Table 9-9 Requirements for Climate (Storage Environment)...................................... 9-5
(Storage Environment) ............................................................................. 9-6
(Storage Environment) ............................................................................. 9-6
Table A-1 ZXCTN 6120S Standards and Recommendations.....................................A-1
IV

Glossary
2G
- The 2nd Generation Mobile Communications
3G
- The 3rd Generation Mobile Communications
AC
- Attachment Circuit
ACL
- Access Control List
ACR
- Adaptive Clock Recovery
AIS
- Alarm Indication Signal
APS
- Automatic Protection Switching
ARP
- Address Resolution Protocol
AS
- Autonomous System
BC
- Boundary Clock
BFD
- Bidirectional Forwarding Detection
BGP
- Border Gateway Protocol
BITS
- Building Integrated Timing Supply
BMC
- Best Master Clock
BTS
- Base Transceiver Station
CBS
- Committed Burst Size
CC
- Continuity Check

CCM
- Continuity Check Message
CE
- Customer Edge
CES
- Circuit Emulation Service
CFM
- Connectivity Fault Management
CIP
- Customer Interface Point
CIR
- Committed Information Rate
CLI
- Command Line Interface
CS
- Conducted Susceptibility
CSF
- Client Signal Failure
DHCP
- Dynamic Host Configuration Protocol
DM
- Delay Measurement
DS
- Differentiated Service
DSCP
- Differentiated Services Code Point
DU
- Downstream Unsolicited
DWRR
- Deficit Weighted Round Robin
DiffServ
- Differentiated Service
E-LAN
- Ethernet Private LAN Service
E-LINE
- Ethernet Private Line
E-TREE
- Ethernet Private Tree Service
VI

Glossary
E2E
- End-to-End
EBS
- Excess Burst Size
ECMP
- Equal-Cost Multi-Path routing
EFM
- Ethernet in the First Mile
EFT
- Electrical Fast Transient
EIR
- Excess Information Rate
EMC
- Electromagnetic Compatibility
EMS
- Element Management System
EPL
- Ethernet Private Line
EPLAN
- Ethernet Private LAN
EPTREE
- Ethernet Private Tree
ESD
- Electrostatic Discharge
ETH-CC
- Ethernet Continuity Check
ETH-LB
- Ethernet Loopback
ETH-LT
- Ethernet Link Trace
ETS
- European Telecommunication Standard
ETSI
- European Telecommunications Standards Institute
EVPL
- Ethernet Virtual Private Line
EVPLAN
- Ethernet Virtual Private LAN
VII

EVPTREE
- Ethernet Virtual Private Tree
EXP
- Experimental
FCC
- Federal Communication Commission
FDI
- Forward Defect Indication
FE
- Fast Ethernet
FEB
- Floor Equipotential earthing terminal Board
FMC
- Fixed Mobile Convergence
FRR
- Fast Reroute
GE
- Gigabit Ethernet
GMC
- Grandmaster Clock
GPS
- Global Positioning System
H-VPLS
- Hierarchy of VPLS
HDB3
- High Density Bipolar of order 3
HSB
- Hot Standby
ICMP
- Internet Control Message Protocol
IEC
- International Electrotechnical Commission
IEEE
- Institute of Electrical and Electronics Engineers
IGMP
- Internet Group Management Protocol
IP
- Internet Protocol
VIII

Glossary
IPHB
- Incoming PHB
IPv4
- Internet Protocol version 4
IS-IS
- Intermediate System-to-Intermediate System
ISO
- International Organization for Standardization
ITU-T
- International Telecommunication Union - Telecommunication Standardization
Sector
L1
- Layer 1
L2
- Layer 2
L2VPN
- Layer 2 Virtual Private Network
L3
- Layer 3
LACP
- Link Aggregation Control Protocol
LAG
- Link Aggregation Group
LAN
- Local Area Network
LB
- Loopback
LCT
- Local Craft Terminal
LDP
- Label Distribution Protocol
LLDP
- Link Layer Discovery Protocol
LM
- Loss Measurement
LSP
- Label Switched Path
LT
- Link Trace
IX

LTE
- Long Term Evolution
MAC
- Media Access Control
MC-LAG
- Multi-Chassis Link Aggregation Group
MCC
- Management Communication Channel
MD5
- Message Digest 5 Algorithm
MEG
- Maintenance Entity Group
MEP
- MEG End Point
MET
- Main Earthing Terminal
MFDFr
- Matrix Flow Domain Fragment
MIB
- Management Information Base
MIP
- MEG Intermediate Point
MPLS
- Multiprotocol Label Switching
MPLS-TP
- Multi-Protocol Label Switching Transport Profile
MS-PW
- Multi-Segment Pseudo Wire
MSTP
- Multiple Spanning Tree Protocol
MTBF
- Mean Time Between Failures
MTTR
- Mean Time To Recovery
MTU
- Maximum Transfer Unit
MTU
- Multi-Tenant Unit

Glossary
NNI
- Network Node Interface
NPE
- Network Provider Edge
OAM
- Operation, Administration and Maintenance
OC
- Ordinary Clock
OPEX
- Operating Expenditure
OPHB
- Outgoing PHB
OSPF
- Open Shortest Path First
P2P
- Peer-to-Peer
PE
- Provider Edge
PPS
- Pulse Per Second
PTP
- Precision Time Protocol
PTP
- Point-To-Point
PW
- Pseudo Wire
PWE3
- Pseudo Wire Emulation Edge-to-Edge
QoS
- Quality of Service
RDI
- Remote Defect Indication
RIP
- Routing Information Protocol
RNC
- Radio Network Controller
RS
- Radiated Susceptiblility
XI

RSTP
- Rapid Spanning Tree Protocol
RSVP
- Resource Reservation Protocol
RSVP-TE
- Resource Reservation Protocol - Traffic Engineering
SCN
- Switched Circuit Network
SDH
- Synchronous Digital Hierarchy
SFP
- Small Form-factor Pluggable
SFP+
- Small Form-factor Pluggable Plus
SLA
- Service Level Agreement
SNMP
- Simple Network Management Protocol
SP
- Strict Priority
SPE
- Switching PE
SSM
- Synchronization Status Message
SSTP
- Single Spanning Tree Protocol
STP
- Spanning Tree Protocol
STP
- Signaling Transfer Point
TC
- Transparent Clock
TCP
- Transmission Control Protocol
TDM
- Time Division Multiplexing
TE
- Traffic Engineering
XII

Glossary
TELNET
- Telecommunication Network Protocol
TLV
- Tag, Length, Value
TMC
- T-MPLS Channel
TMP
- T-MPLS Path
ToD
- Time of Delivery
ToS
- Type of Service
UDP
- User Datagram Protocol
UNI
- User Network Interface
UPE
- User facing Provider Edge
UTP
- Unshielded Twisted Pair
VIP
- Virtual Interface Point
VLAN
- Virtual Local Area Network
VLL
- Virtual Leased Line
VPLS
- Virtual Private LAN Service
VPN
- Virtual Private Network
VPWS
- Virtual Private Wire Service
VRF
- Virtual Route Forwarding
VRRP
- Virtual Router Redundancy Protocol
WRED
- Weighted Random Early Detection
XIII

WRR
- Weighted Round Robin
XIV

Manual 6120s

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Manual 6120s

Enviado por

Direitos autorais:

Formatos disponíveis

ZXCTN 6120S

Revision No. Revision Date Revision Reason

R1.0 2014-06-30 ZXCTN 6120S(V3.00) Product Description Issued.

Serial Number: SJ-20140603170741-014

Publishing Date: 2014-06-30(R1.0)

SJ-20140603170741-014|2014-06-30(R1.0) ZTE Proprietary and Confidential

Chapter 2 Architecture............................................................................... 2-1

Chapter 3 Services ..................................................................................... 3-1

Chapter 4 Functions................................................................................... 4-1

SJ-20140603170741-014|2014-06-30(R1.0) ZTE Proprietary and Confidential

Chapter 5 Protection .................................................................................. 5-1

Chapter 6 Interfaces ................................................................................... 6-1

Chapter 7 Networking Applications.......................................................... 7-1

Chapter 8 Technical Specifications .......................................................... 8-1

Chapter 9 Environment Requirements ..................................................... 9-1

SJ-20140603170741-014|2014-06-30(R1.0) ZTE Proprietary and Confidential

Appendix A Standards and Recommendations ..................................... A-1

SJ-20140603170741-014|2014-06-30(R1.0) ZTE Proprietary and Confidential

SJ-20140603170741-014|2014-06-30(R1.0) ZTE Proprietary and Confidential

What Is in This Manual

Chapter 9, Environment Describes the environment requirements of the ZXCTN 6120S.

SJ-20140603170741-014|2014-06-30(R1.0) ZTE Proprietary and Confidential

Caution: indicates a potentially hazardous situation. Failure to comply

Note: provides additional information about a topic.

SJ-20140603170741-014|2014-06-30(R1.0) ZTE Proprietary and Confidential

Figure 1-1 ZXCTN 6120S Overview

1.2 Product Positioning

SJ-20140603170741-014|2014-06-30(R1.0) ZTE Proprietary and Confidential

Figure 1-2 Network Application of the ZXCTN 6120S

1.3 Product Features

Unified Bearer Platform

SJ-20140603170741-014|2014-06-30(R1.0) ZTE Proprietary and Confidential

IP/MPLS and MPLS-TP Dual-Stack Protocol

SJ-20140603170741-014|2014-06-30(R1.0) ZTE Proprietary and Confidential

à Link Aggregation Group (LAG) protection

Unified Network Management System

SJ-20140603170741-014|2014-06-30(R1.0) ZTE Proprietary and Confidential

2.1 Logical Structure

Figure 2-1 Functional Units of the ZXCTN 6120S

Service Interface Unit

l Time Division Multiplexing (TDM) E1 interface

SJ-20140603170741-014|2014-06-30(R1.0) ZTE Proprietary and Confidential

l Gigabit Ethernet (GE) optical/electrical interface

Service Adaptation Unit

Service Switching Unit

Main Control/Clock Unit

System Interface Unit

Power Supply Unit

Heat Dissipation Unit

SJ-20140603170741-014|2014-06-30(R1.0) ZTE Proprietary and Confidential

2.2 Hardware Structure

Figure 2-2 Hardware Structure of the ZXCTN 6120S

1. Power board area 3. Antistatic wrist strap jack

Table 2-1 Subrack Structure Description of the ZXCTN 6120S

Serial Component Description

3 Antistatic wrist strap The antistatic wrist strap is inserted here.

2.3 Software Structure

SJ-20140603170741-014|2014-06-30(R1.0) ZTE Proprietary and Confidential

Figure 2-3 Software Structure Diagram

Main Control Software Structure

Figure 2-4 Structure of ZXCTN 6120S Main Control Software

SJ-20140603170741-014|2014-06-30(R1.0) ZTE Proprietary and Confidential

l Platform OAM sub-system: responsible for inter-communication between the platform

Board Software Structure