ZXCTN 6150 V3.00 Product Description - 20140106 - EN

ZXCTN 6150 V3.
0 Product
Description
ZXCTN 6150 V3.0 Product Description

Version Date Author Reviewer Notes
Zhao Yue, Pan

V1.0 2014/01/06 Gao Yang Not open to the third party
Xiaohui
© 2018 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used
without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is subjected to
change without notice.
ZTE Confidential & Proprietary 1

TABLE OF CONTENTS
1 Overview ............................................................................................................ 9
2 Highlights........................................................................................................... 9
3 Functions and features ................................................................................... 11

3.1 Capacity and interfaces...................................................................................... 11
3.1.1 Service processing capability ............................................................................. 11
3.1.2 Switching capability............................................................................................ 12
3.1.3 Interface type ..................................................................................................... 13
3.2 Multiservice bearing capability ........................................................................... 14
3.2.1 TDM service....................................................................................................... 14
3.2.2 Ethernet service ................................................................................................. 15
3.3 Basic L2 Service ................................................................................................ 18
3.3.1 Basic Ethernet Service ....................................................................................... 18
3.3.2 VLAN and VLAN Extension Features ................................................................. 18
3.3.3 Link aggregation function ................................................................................... 19
3.3.4 STP function ...................................................................................................... 20
3.3.5 DHCP Relay function ......................................................................................... 21
3.3.6 Multicast ............................................................................................................ 21
3.4 L3 function ......................................................................................................... 23
3.4.1 L3 basic function ................................................................................................ 23
3.4.2 L3 route protocol ................................................................................................ 27
3.5 MPLS ................................................................................................................. 33
3.5.1 MPLS Overview ................................................................................................. 33
3.5.2 MPLS Network Architecture ............................................................................... 33
3.5.3 MPLS Basic Functions ....................................................................................... 34
3.5.4 LDP.................................................................................................................... 35
3.5.5 RSVP-TE ........................................................................................................... 40
3.6 MPLS L2 VPN .................................................................................................... 45
3.6.1 VPWS ................................................................................................................ 45
3.6.2 VPLS ................................................................................................................. 46
3.6.3 H-VPLS (Hub-Spoke) ......................................................................................... 48
3.6.4 Multi-Segment Pseudo-Wire .............................................................................. 50
3.6.5 PW State Notification ......................................................................................... 51
3.7 BGP/MPLS L3 VPN ........................................................................................... 51
3.7.1 VRF ................................................................................................................... 52
3.7.2 L3 VPN Access .................................................................................................. 52
3.7.3 L3 VPN Tunnel .................................................................................................. 53
3.7.4 Customer Route Learning and Launching .......................................................... 53
3.7.5 Cross-domain VPN ............................................................................................ 54
2 ZTE Confidential & Proprietary

3.7.6 VPN FRR ........................................................................................................... 54

3.8 QoS feature ....................................................................................................... 54
3.8.1 QoS function ...................................................................................................... 54
3.8.2 MPLS QoS feature ............................................................................................. 56
3.8.3 Ethernet QoS feature ......................................................................................... 57
3.9 OAM Features ................................................................................................... 57
3.9.1 MPLS OAM ........................................................................................................ 57
3.9.2 MPLS-TP OAM Function.................................................................................... 59
3.9.3 Ethernet OAM .................................................................................................... 61
3.9.4 Ethernet Link OAM............................................................................................. 64
3.9.5 BFD ................................................................................................................... 64
3.10 Protection Features............................................................................................ 66
3.10.1 Equipment-level protection ................................................................................. 66
3.10.2 MPLS Network-level protection .......................................................................... 67
3.10.3 MPLS-TP Network-Level Protection ................................................................... 70
3.10.4 Other Protection Manners .................................................................................. 77
3.11 Synchronization feature ..................................................................................... 77
3.11.1 System clock function ........................................................................................ 77
3.11.2 Synchronous Ethernet clock .............................................................................. 78
3.11.3 IEEE 1588v2 clock ............................................................................................. 78
3.11.4 Time synchronization Ethernet function ............................................................. 79
3.11.5 1588 frequency recovery.................................................................................... 79
3.11.6 Clock protection function .................................................................................... 79
3.11.7 Clock synchronization way for CES service ....................................................... 80
3.12 Security.............................................................................................................. 80
3.12.1 AAA ID verification ............................................................................................. 80
3.12.2 Network security ................................................................................................ 82
4 System structure ............................................................................................. 83

4.1 System hardware ............................................................................................... 83
4.1.1 Hardware architecture ........................................................................................ 83
4.1.2 Working principle of ZXCTN 6150 hardware system .......................................... 84
4.2 System boards ................................................................................................... 86
4.2.1 ZXCTN 6150 boards .......................................................................................... 86
4.3 Software architecture ....................................................................................... 105
4.3.1 EMS software .................................................................................................. 105
4.3.2 Communication protocols and interfaces ......................................................... 106
4.3.3 Brief introduction to ZXROS platform ............................................................... 107
5 Technical indices and specifications ........................................................... 119

5.1 Physical performance ...................................................................................... 119
5.2 Interface indices ............................................................................................... 120

5.3 System Function List ........................................................................................ 124

5.3.1 L2 Feature ....................................................................................................... 124
5.3.2 L3 Feature ....................................................................................................... 125
5.3.3 QoS Feature .................................................................................................... 126
5.3.4 Service Management ....................................................................................... 127
5.3.5 Reliability ......................................................................................................... 127
5.3.6 Clock Synchronization ..................................................................................... 128
5.3.7 Tunnel Feature ................................................................................................ 128
5.3.8 Security Feature .............................................................................................. 129
5.3.9 Operation and Maintenance ............................................................................. 130
6 Operation and maintenance ......................................................................... 131

6.1 Unified NM platform ......................................................................................... 131
6.2 Maintenance and management ........................................................................ 131
6.2.1 Equipment management .................................................................................. 131
6.2.2 Supervision and maintenance .......................................................................... 132
6.2.3 Diagnosis and debugging................................................................................. 133
6.2.4 Software upgrade............................................................................................. 134
7 Environment indices ..................................................................................... 134

7.1 Storage ............................................................................................................ 134
7.1.1 Climate environment ........................................................................................ 134
7.1.2 Water-proof requirement .................................................................................. 135
7.2 Transportation.................................................................................................. 135
7.2.1 Climate environment ........................................................................................ 135
7.2.2 Water-proof requirements ................................................................................ 136
7.3 Running ........................................................................................................... 136
7.4 Electromagnetic compatibility (EMC)................................................................ 137
7.4.1 Criteria ............................................................................................................. 137
7.4.2 Anti-interference .............................................................................................. 138
7.4.3 Interference...................................................................................................... 143
8 Abbreviation .................................................................................................. 144
9 Standards and recommendations ................................................................ 148

9.1 IETF ................................................................................................................. 148
9.2 ITU-T ............................................................................................................... 149
9.3 IEEE ................................................................................................................ 153
9.4 MEF ................................................................................................................. 153

FIGURES
Figure 3-1 ZXCTN 6000 E-LINE service model..................................................................16

Figure 3-2 ZXCTN 6000 E-LAN service model...................................................................17
Figure 3-3 ZXCTN 6000 E-Tree service model ..................................................................17
Figure 3-4 IGMP proxy/snooping .......................................................................................22
Figure 3-5 VPLS-based multicast service model ................................................................23
Figure 3-6 VRRP ...............................................................................................................26
Figure 3-7 Virtual Link ........................................................................................................28
Figure 3-8 IPv4 label route release ....................................................................................32
Figure 3-9 MPLS network architecture ...............................................................................34
Figure 3-10 Downstream Unsolicited .................................................................................36
Figure 3-11 Downstream on Demand ................................................................................37
Figure 3-12 Liberal Label Retention Mode .........................................................................38
Figure 3-13 Conservative Label Retention Mode ...............................................................38
Figure 3-14 Cross-domain RSVP-TE .................................................................................44
Figure 3-15 VPWS basic model .........................................................................................45
Figure 3-16 VPLS basic model ..........................................................................................47
Figure 3-17 H-VPLS (Hub-Spoke)......................................................................................49
Figure 3-18 Multi-Segment pseudo-wire ............................................................................50
Figure 3-19 BGP/MPLS VPN network architecture ............................................................51
Figure 3-20 Distributing VRF per route mode .....................................................................52
Figure 3-21 Route exchange between PE and CE .............................................................53
Figure 3-22 VRF-to-VRF ....................................................................................................54
Figure 3-23 OAM PDU coding format ................................................................................60
Figure 3-24 Ethernet OAM implementation in hierarchy .....................................................62
Figure 3-25 MPLS Tunnel 1:1 protection............................................................................68
Figure 3-26 FRR protection................................................................................................69
Figure 3-27 Unidirectional 1+1 protection switching ...........................................................71
Figure 3-28 Unidirectional 1+1 Tunnel Protection Switching (Working Link Fault) ..............71

Figure 3-29 Bidirectional 1: 1 Tunnel Protection Switching Architecture)............................71

Figure 3-30 Bidirectional 1:1 Tunnel Protection Switching (Working Connection Z-A Fails)
.............................................................................................................................................72
Figure 3-31 Wrapping Protection .......................................................................................73
Figure 3-32 Dual-Homing Protection ..................................................................................75
Figure 3-33 DNI Protection ................................................................................................76
Figure 4-1 ZXCTN 6150 subrack structure.........................................................................84
Figure 4-2 ZXCTN 6150 subrack slot .................................................................................84
Figure 4-3 XGEx2(O) panel ...............................................................................................88
Figure 4-4 XGEx1(O) panel ...............................................................................................89
Figure 4-5 GEx8(O) panel ....................................................................................................90
Figure 4-6 GECHx4(O) panel.............................................................................................92
Figure 4-7 GECx4(O) panel ...............................................................................................94
Figure 4-8 FEx8(E) panel ...................................................................................................95
Figure 4-9 FEx8(OE) panel ................................................................................................96
9. Figure 4-10 STM-1x4(O) panel ......................................................................99
Figure 4-11 E1x16-75 panel.............................................................................................101
Figure 4-12 E1x16-120 panel...........................................................................................102
Figure 4-13 GPCB panel ..................................................................................................103
Figure 4-14 SME panel ....................................................................................................103
Figure 4-15 ZXCTN 6150 DC power module....................................................................104
Figure 4-16 ZXCTN 6150 FAN panel ...............................................................................104
Figure 4-17 EMS software architecture ............................................................................105
Figure 4-18 Software architecture ....................................................................................107
TABLES
Table 3-1 ZXCTN 6150 switching capability .......................................................................12
Table 3-2 ZXCTN 6150 maximum access capability ..........................................................12
Table 3-3 ZXCTN 6150 service interface ...........................................................................13
Table 3-4 ZXCTN 6150 auxiliary interface type and number ..............................................13

Table 3-5 EVC (Ethernet Virtual Connection) service supported by ZXCTN 6150 ..............15
Table 3-6 VLAN feature .....................................................................................................19
Table 3-7 OSPF packet types ............................................................................................27
Table 3-8 MPLS-TP OAM failure management functions ...................................................59
Table 3-9 MPLS-TP performance management functions ..................................................59
Table 3-10 OAM types that ZXCTN 6150 supports ............................................................60
Table 3-11 Typical Ethernet OAM protocol ........................................................................62
Table 3-12 ZXCTN 6150 Ethernet OAM functions .............................................................63
Table 3-13 Ethernet Link OAM ...........................................................................................64
Table 3-14 ZXCTN 6150 equipment-level protection..........................................................67
Table 4-1 ZXCTN 6150 board type and functio ..................................................................86
Table 4-2 XGEx2(O) board function ...................................................................................87
Table 4-3 XGEx1 board function ........................................................................................88
Table 4-4 GEx8(O) board function ........................................................................................90
Table 4-5 GECHx4(O) board function ................................................................................91
Table 4-6 GECx4 V2 board function ..................................................................................92
Table 4-7 FEx8(E) board function....................................................................................94
Table 4-8 FEx8(OE) board function .................................................................................95
Table 4-9 ZXCTN 6150 software system interface description .........................................106
Table 5-1 Equipment physical performance list ................................................................119
Table 5-2 E1 interface electric performance .....................................................................120
Table 5-3 STM-1 optical interface performance ...............................................................121
Table 5-4 STM-1/OC-12 optical interface performance ....................................................122
Table 5-5 10/100Base-TX interface electric performance ................................................122
Table 5-6 GE interface optical performance .....................................................................123
Table 5-7 10GE interface optical performance .................................................................123
Table 5-8 L2 Feature .......................................................................................................124
Table 5-9 L3 Feature .......................................................................................................125
Table 5-10 QoS Feature ..................................................................................................126
Table 5-11 Service Management .....................................................................................127

Table 5-12 Reliability .......................................................................................................127

Table 5-13 Clock Synchronization....................................................................................128
Table 5-14 Tunnel Feature...............................................................................................128
Table 5-15 Security Feature.............................................................................................129
Table 5-16 Operation and Maintenance ...........................................................................130
Table 7-1 Requirements for climate (storage environment) ..............................................134
Table 7-2 Requirements for climate (transportation environment) ....................................136
Table 7-3 Temperature and humidity requirements (running environment) ......................137
Table 7-4 Other climate environment requirements (running environment) ......................137
Table 7-5 Criteria for test results ......................................................................................137
Table 7-6 ESD immunity ..................................................................................................138
Table 7-7 RF electromagnetic field radiation immunity Resistance ..................................139
Table 7-8 DC port immunity .............................................................................................139
Table 7-9 AC port immunity .............................................................................................139
Table 7-10 Signal line and control line port immunity .......................................................140
Table 7-11 DC lightning surge immunity ..........................................................................140
Table 7-12 AC lightning surge immunity...........................................................................140
Table 7-13 Outdoor signal line surge immunity ................................................................141
Table 7-14 Signal line (>10m) surge immunity .................................................................141
Table 7-15 RF field conductivity immunity ........................................................................141
Table 7-16 AC transient voltage dip and short interruption immunity................................141
Table 7-17 DC transient voltage dip and short interruption immunity ...............................142
Table 7-18 AC port voltage fluctuation immunity ..............................................................143
Table 7-19 DC/AC port conducted emission ....................................................................143
Table 7-20 Ethernet/E1 port conducted emission.............................................................143
Table 7-21 Radiated emission strength ............................................................................144

1 Overview
ZXCTN 6000 series is ZTE’s Carrier class Multi-service Packet-based Platform (CMPP)
in compliance with IP-based service development trend. The packet-based multiservice
bearer platform provides Mobile Backhaul end-to-end solution and supports smooth
network evolution to lower CAPEX and OPEX for carriers.
ZXCTN 6000, applied to network access layer, integrates packet and transport
technologies to meet complex service demands. As the platform based on packet
switching, ZXCTN 6000 support multiservice interfaces, network synchronization,
carrier-class OAM & protection, and many other functions, which make ZXCTN 6000 as
a powerful platform to process and transmit carrier-class Ethernet, ATM and TDM
services.
ZXCTN 6000 series consists of ZXCTN 6110(F), ZXCTN 6120, ZXCTN 6120S, ZXCTN
6130XG-S, ZXCTN 6150, ZXCTN 6180, ZXCTN 6200, ZXCTN 6220 and ZXCTN 6300.
ZXCTN 6110(F)/6120/6120S/6130XG-S is the compact IP transport network platform.

Each of them is 1U-high box equipments and applied to network access layer, as
multiservice access and edge gateways.
The rack-type equipment ZXCTN 6150, 6180, 6200, 6220 and 6300 provide redundant
protection for equipment-level key units in the ASIC-based centralized packet switching
structure. ZXCTN 6150, 6180, 6200 and 6220 are applied to large capacity network
access layer.
ZXCTN 6000 series are often used for:
 Mobile Backhaul
 VIP access and VPN service
2 Highlights
 Multiservice bearer platform to meet full-service demands
Based on full-packet structure and PWE3 technology, ZXCTN 6150 supports

IP/MPLS & MPLS-TP technology to bear services such as TDM and Ethernet with
high efficiency, which can meet full-service demands and significantly lower the
network TCO of customers.
 Leading time synchronization technology to achieve high-precision synchronization

networks
Combining G.8261 and 1588V2 technologies, ZTE proposes the leading "time
synchronization Ethernet" solution to save network resource and convergence time
for network synchronization. Hardware based time stamp injection and extraction
for 1588v2 protocol can efficiently improve time synchronization performance.
ZXCTN products can provide flexible synchronization solutions including ordinary
clock, boundary clock, transparently transport clock, outband 1PPS+TOD and
inband Ethernet synchronization or long-term network evolution. SSM and BMC
algorithm are available for automatic protection switching of clock and time link to
ensure reliable synchronous transmission.
 Good end-to-end QoS to provide differentiated service (Differ-Serv)

ZXCTN supports end-to-end QoS management to provide the required delay, jitter
and bandwidth for different services. It also supports Diff-Serv-based QoS
scheduling, port, VLAN, DSCP/TOS, MAC & IP address based classifier and
labeling, the traffic policing, queue scheduling, congestion control and traffic
shaping. ZXCTN can support user-level multiservice bandwidth control and service
access SLA to guarantee better operation of carrier network.
 Powerful hierarchical OAM to increase network availability

ZXCTN 6150 supports the MPLS-TP, IP/MPLS and Ethernet OAM, the hierarchical
monitoring based on hardware mechanism to fast detect and locate faults, monitor
the performance and manage end-to-end (ETE) services, and the continuous and
on-demand OAM to guarantee carrier class service QoS in Packet Transport
Network. The hierarchical OAM, based on physical port, logic link, pseudowire and
tunnel, can make network operation, administration and maintenance more
transparent and simpler.
 Multiple reliability mechanisms to guarantee network security

ZXCTN 6150 supports a full range equipment-level, network-level and network
edge-level protection. The equipment-level protection supports 1+1 hot-standby for

control, clock and power module to improve disaster restoration and fault solving.
The network protection provides layered and sectioned LSP, and
connection-oriented ring protection for complex full-service applications to
guarantee protection switching in 50ms. The network edge-level protection includes
LAG protections. These protections lead to the carrier-class reliability of 99.999%.
ZXCTN 6150 offers a wide variety of security and anti-attack features, forwards
full-rate services in the configuration of tens of thousands of ACL, support packet
check, traffic classification, CPU protection, limited-rate protocol message, route
authentication, DdoS attack monitoring and hierarchical NM, and shields network
attack risks.
 Open technology platform to support high growth of service network

ZXCTN 6150, the open technology platform, is compatible with conventional
transmission and data network and is compliant with MPLS-TP and IP/MPLS
technologies to reduce the risk in technology selection for future network evolution.
 Unified NMS to simplify OAM

ZTE’s unified network management platform NetNumen U31 can manage ZXCTN
6150 as well as SDH/MSTP, ASON, WDM and OTN equipment at the same time. It
creates and manages ETE path, offers powerful QoS, OAM, fulfill realtime alarm
and performance monitoring. With traditional style NE management functions and
user friendly GUI, NetNumen U31 makes ZXCTN manageable and maintainable
easily.
3 Functions and features
3.1 Capacity and interfaces
3.1.1 Service processing capability
ZXCTN 6150 service processing capability includes switching capability and service
access capability.

3.1.2 Switching capability
ZXCTN 6150 supports the packet-based service switching. ZXCTN 6150 service
switching capability is shown in Table 3-1.
Table 3-1 ZXCTN 6150 switching capability
Service processing ZXCTN 6150
Switching capacity 90 Gbps(Unidirectional)
Access capacity 60~90G Gbps
Packet forwarding rate 89.28~133.92Mpps
3.1.2.1 Access capability
ZXCTN 6150 can access multiple services via different types of interfaces. The type and
access capacity of ZXCTN 6150 service interface are shown in Table 3-2.
Note: Ch. =Channelized.
Table 3-2 ZXCTN 6150 maximum access capability
Interface Board port Overall port

Type
number number
Ethernet 10GE(Optical) 1 6~9
GE(Optical) 8 56
GE(Electrical) 4 28
FE(Optical) 8 56
FE(Electrical) 8 56
PDH TDM E1 16 112
STM-N Ch. STM-1 4 28
CEP STM-1 4 28

3.1.3 Interface type
3.1.3.1 ZXCTN 6150 interface type and number
ZXCTN 6150 supports multiple interfaces, as shown in Table 3-3. 8 ports FE interface
card just support UNI function now.
Table 3-3 ZXCTN 6150 service interface
Type Description Remark
FE interface Electrical UNI/NNI

interface:10/100BASE-TX
Optical interface:100BASE-FX
GE interface Electrical interface:1000BASE-T UNI/NNI

Optical interface: 1000BASE-SX,
1000BASE-LX, 1000BASE-ZX
10GE interface Optical interface: 10GBASE-SR, UNI/NNI

10GBASE-LR, 10GBASE-ER
STM-1 interface Ch. STM-1 optical interface Ch.STM-1 optical interface

CEP STM-1 optical interface works as UNI;
CEP STM-1 optical
interface works as UNI
E1 interface E1 interface UNI (TDM E1)
ZXCTN 6150 also supports NM interface, clock interface and alarm interface, as shown
in Table 3-4.
Table 3-4 ZXCTN 6150 auxiliary interface type and number
Auxiliary interface Number Parameter Remark
1 Support 1 Qx NM RJ45 physical

NM interface
interface interface
1 Support 1x LCT RJ45 physical

LCT interface
interface interface
External alarm 1
Support 4*external RJ45 physical
input/output
alarm input/output interface
interface

Auxiliary interface Number Parameter Remark
1/1 Interface is
Support 2M BITS/Hz RS422 interface
BITS
input and output (RJ45 physical
interface)
2 Interface is
Support 1PPS+TOD
RS422 interface
GPS interface interface (input or
(RJ45 physical
output,)
interface)
3.2 Multiservice bearing capability
ZXCTN 6150 bears TDM/ETH services through PWE3 (Pseudo Wire Emulation
Edge-to-Edge) and provides a transparent transport channel for various services in PSN
(Packet Switching Network). In the channel, user services are isolated from each other
and service attributes keep unchanged during the transport.
PWE3 integrates the original access modes and the existing IP backbone network to
reduce CAPEX and OPEX.
3.2.1 TDM service
ZXCTN 6150 supports TDM service via TDM E1 interface and STM-N interface. ZXCTN
6150 supports Structure-aware and Structure-agnostic Emulation of TDM service, and
CEP Emulation of VC-4.
 Structure-aware Emulation has the following functions.
 The equipment can be aware of frame structure, framing mode and

timeslot information in TDM circuit.
 The equipment processes TDM frame overheads, extracts payloads and

puts the timeslots into packet message payloads in a certain sequence,
so each service in the message is fixed.
 Compared with Structure-agnostic Emulation, the latency of

Structure-aware Emulation is longer, as TDM service need to be

processed in PE (Provider Edge) node. However, Structure-aware

Emulation can save the bandwidth of backbone network.
 Structure-agnostic Emulation has the following functions.
 The equipment can be agnostic about any structure in TDM signal. It

treats TDM signal as constant-rate bit stream and emulates the TDM
signal.
 Overheads and payloads in TDM signal are transmitted transparently.
 Compared with Structure-aware Emulation, the latency of

Structure-agnostic Emulation is shorter. However, Structure-agnostic
Emulation needs larger bandwidth of backbone network than
Structure-aware Emulation.
 CEP emulation has the following functions.
 Support VC4 emulation and one to one mapping between VC4 and PW
 The default payload of CEP is 783 bytes (TUG-3) which can be

configured between 783-9170 bytes
ZXCTN 6150 supports flexible configuration of TDM CES. Each E1 interface can be
configured as Structure-aware or Structure-agnostic independently.
3.2.2 Ethernet service
ZXCTN 6150 supports access and transmission of Ethernet service via Fast Ethernet
interfaces, Gigabit Ethernet interface, etc.
ZXCTN 6150 offers the following three types of Ethernet services that are compliant with
ITU-T, MEF6.
Table 3-5 EVC (Ethernet Virtual Connection) service supported by ZXCTN 6150
Port-Based(All to
Service Type VLAN-Based(Service multiplexed)
one bundling)
E-Line EPL EVPL

Port-Based(All to
Service Type VLAN-Based(Service multiplexed)
one bundling)
E-LAN EP-LAN EVP-LAN
E-Tree EP-Tree EVP-Tree
3.2.2.1 E-Line
E-Line is the point-to-point (PTP) service and consists of EPLine and EVPLine.
Figure 3-1 ZXCTN 6000 E-LINE service model
3.2.2.2 E-LAN
E-LAN is the multipoint-to-multipoint service and consists of EPLAN and EVPLAN.

Figure 3-2 ZXCTN 6000 E-LAN service model
3.2.2.3 E-Tree
E-Tree is the point-to-multipoint service and consists of EPTree and EVPTree.
Figure 3-3 ZXCTN 6000 E-Tree service model

3.3 Basic L2 Service
3.3.1 Basic Ethernet Service
ZXCTN 6150 supports the following basic Ethernet functions:
 Support full-duplex working mode of the port.
 Support 10/100/1000M automatic negotiation of the port (electrical port only).
 Support the following L2 Switch functions:
 MAC address learning
 MAC address binding
 MAC address filtering
 Support the following port traffic control functions based on full-duplex IEEE 802.3x
Pause frame mechanism.
 Support mirroring function based on port.
 Support storm suppression of broadcast/multicast/unknown unicast packets,

including:
 Port based
 Controlled by percentage or specified rate
 Support at most 9Kbyte Jumbo frame.
 Support LLDP based on 802.1ab.
3.3.2 VLAN and VLAN Extension Features
ZXCTN 6150 supports powerful VLAN function to divide virtual working groups.

Table 3-6 VLAN feature
Attribute Description
VLAN Support VLAN based on port and MAC address.
Support QinQ-based forwarding.

Support ordinary QinQ and port-based external label.
VLAN Support Selective QinQ and flow-based external
Features QinQ label.
Support Selective QinQ internal priority mapping.
Support TPID modification.
Support 1:1, 1:2 and 2:1 QinQ functions.
ZXCTN 6150 supports port based VLAN separation and provides multiple types of
interfaces according to whether the received messages are encapsulated with VLAN Tag.
ZXCTN 6150 is connected to user host via Access interface, to other ZXCTN equipment
via Trunk interface, and to user host or other ZXCTN or Ethernet switch via Hybrid
interface. The equipments connected via Trunk interface can connect with each other
through VLAN Trunk connection and transport multiple VLAN data stream. As a result,
the VLAN interworking can be achieved in the whole metro network.
In 802.1Q VLAN protocol, VLAN ID is based on 12 bits, which limits VLAN number up to
4096. In order to extend VLAN ID address space and improve security, ZXCTN extends
VLAN on the basis of IEEE802.1Q (QinQ). QinQ is also called Stacked VLAN or Double
VLAN, which encapsulates VLAN Tag of the private network into VLAN Tag of the public
network so that the packets go through backbone network (public network) of the carriers
with two layers of VLAN Tag. Because QinQ has two layers of tag, it extends VLAN
range of metro backbone network.
3.3.3 Link aggregation function
ZXCTN 6150 supports link aggregation to bind a group of physical interfaces, which can
make the interfaces group as same as the single link logically.
Link aggregation is an approach to increase bandwidth and improve reliability by binding

physical links. Because link aggregation can multiply the bandwidth between different
devices, it is an important technology to create link transmission resilience and
redundancy. Meanwhile, when some links of the link aggregation group failed, link

aggregation function can protect transmission on the fault links and switch the service to
the working links of the same link aggregation group, which can remarkably increase the
transmission reliability.
There are manual aggregation and static aggregation according to implementation mode.
Manual aggregation does not need LACP (Link Aggregation Control Protocol), but static
aggregation does.
Link aggregation supports the traffic sharing option by adopting load-sharing or

non-load-sharing mode. If load-sharing mode is adopted, the traffic load will be
automatically shared among the physical link in the same link aggregation group. When
one of the physical links failed, its traffic will be shared among other links in this group
and the traffic will be reallocated after the link fault is resolved. If non-load-sharing mode
is adopted, only active link has traffic and standby link is in the standby status, which is
actually a backup mechanism. When the active link fails, the traffic will be switched to the
standby link to protect links failure.
ZXCTN 6150 supports manual load-sharing link aggregation and LACP defined by IEEE
802.3ad, which can bind FE and GE interfaces, and support link aggregation across
service boards based on MAC, VLAN & IP load balancing.
3.3.4 STP function
ZXCTN 6150 supports STP complying with IEEE802.1D, RSTP complying with
IEEE802.1w, and MSTP complying with IEEE802.1s.
Without authentication mechanism, STP cannot authenticate and limit new added BPDU
packets, which will impact network topology and stability. ZXCTN 6150 uses BPDU
protection, root protection and ring protection to stabilize L2 switching network topology.
In the simple network (e.g., small network composed of several switches) or the special
port (e.g., the port connected to PC), which STP is not needed, STP can be disabled
manually to meet the network and management requirements. ZXCTN 6150 provides the
protocol disable function based on port.

3.3.5 DHCP Relay function
DHCP (Dynamic Host Configuration Protocol) automatically allocates IP address to the

host. After getting the IP address, the host can initiates an IP communication via the IP
address. In the LTE stage, it is required that DHCP dynamically allocates the address to
eNB to enhance network automatization.
ZXCTN 6150 supports DHCP Relay. DHCP Server is usually deployed in the
convergence layer or core layer equipment, thus it is required that DHCP packet of the
host can penetrate different subnets to reach DHCP Server. In order to support the
penetration, ZXCTN 6150 can snoop and relay DHCP packet, which is DHCP Relay
function.
3.3.6 Multicast
IGMP proxy/snooping is the L2 multicast mechanism which manage and control

multicast group. The equipment with IGMP proxy/snooping function analyzes the
received IGMP packet to establish the mapping relationship between ports and MAC
multicast addresses, and forward multicast data according to the relationship.
IGMP proxy/snooping uses L2 multicast to forward the information only to the receiver in
demand and has the following advantages:
 Reduce the broadcast messages in L2 network and save network bandwidth.
 Enhance the security of multicast information.
 Independent charging ability of each host.

Figure 3-4 IGMP proxy/snooping
ZXCTN 6150 support the following IGMP proxy/snooping functions:
 Support IGMPv2 protocol.
 Support static multicast table configuration.
 Create the multicast table based on IGMP proxy/snooping and forward multicast
services according to service ports registered in the multicast table.
 When IGMP proxy/snooping are available, the multicast table is transmitted

according to the specified ports, and the unknown multicast service can be
discarded or broadcasted according to the configuration.
 Dynamically create, delete and maintain multicast table, and multicast query based
on VPLS/E-LAN service.

Figure 3-5 VPLS-based multicast service model
3.4 L3 function
3.4.1 L3 basic function
3.4.1.1 L3 interface
ZXCTN 6150 supports the following L3 interface:
 VLAN-based L3 interface.
 Qx-based L3 interface.
 Qx interface is the Ethernet interface of outband NM. It forwards NM packets from

outband to inband.

3.4.1.2 ARP protocol
ZXCTN 6150 support ARP (Address Resolution Protocol). The basic function of ARP is
to query MAC address of target equipment according to its IP address to assure smooth
communication.
 Support dynamic ARP request.
 Support ARP reply.
 Support dynamic ARP aging.
 Support static ARP configuration.
3.4.1.3 IPv4 unicast route forwarding
ZXCTN 6150 supports IPv4 unicast route forwarding:
 Support IPv4 basic unicast route forwarding.
 Support IPv4 unicast route full-rate forwarding.
 Support the best matching of hardware routing table.
3.4.1.4 Static route
ZXCTN 6150 support static route. Static route is manually configured by the
administrator and can be configured to make simple network run normally. Static route
can be set and used properly to improve network performance, and guarantee the
sufficient bandwidth for important networks.
3.4.1.5 Route forwarding load sharing (ECMP)
ZXCTN 6150 supports route forwarding load sharing (Equal Cost of Multi-path). When IP
network uses route protocol or static configuration to reach a destination network,
multiple equivalent next hops share the load in IP route forwarding. ECMP can share the
load of IP packets for services and NM to increase the forwarding capability. Each ECMP
group supports up to 8 routes.

3.4.1.6 ICMP protocol
ZXCTN 6150 follows ICMP (Internet Control Message Protocol) and has the following
functions in the network:
 Host probe
 Route maintenance
 Route selection
 Traffic control
3.4.1.7 UDP protocol
ZXCTN 6150 follows UDP (User Datagram Protocol). As basic connectionless transport
protocol, UDP is the transports means of many protocols. For example, it is used by
protocols such as OSPF and LDP to transmit Hello protocol packets. The basic function
follows RFC 768 - User Datagram Protocol.
3.4.1.8 TCP protocol
ZXCTN 6150 follows TCP (Transmission Control Protocol). As basic connection

transport protocol, TCP is the transports means of many upper-level protocols. For
example, it is used by such protocols as BGP, LDP and Telnet to transmit datagram
packets. The basic function follows RFC 793 - Transmission Control Protocol.
3.4.1.9 VRRP protocol
VRRP is the protocol about gateway node redundancy protection. As shown in Figure
3-6, CE is dual-homed to PE1 and PE2 via two links. PE1 address is 30.1.1.2, MAC1 and
PE2 address is 30.1.1.4, MAC2.

Figure 3-6 VRRP
After running VRRP, PE1 and PE2 virtualize an IP address 30.1.1.1. When CE is
configured with routes, next hop is designated as VRRP virtual address. Thus CE shields
the IP address of the actual port with virtual address.
After running VRRP, PE1 and PE2 exchange VRRP packets with each other to select the
active equipment. When the network is in operation, only the active equipment virtualizes
ARP request packets of the address 30.1.1.1. Thus the MAC address learnt by CE is the
MAC address of the active, the packets will be forwarded to the active.
When the active is found going wrong in VRRP packet check, the standby will work as
the active and send a free ARP packet to virtual address. After receiving the packet, CE
updates ARP table to refresh forwarding paths and send service packets to the new
active. ZXCTN 6150 follows Virtual Router Redundancy Protocol (RFC 3768).
VRRP supports multi-backup configuration, backup priority setting, VRRP switching

authentication and priority replacement mode.
3.4.1.10 IP FRR
ZXCTN 6150 supports BFD-based fast IP rerouting to convergence routes rapidly in the
Native IP networking.

3.4.2 L3 route protocol
3.4.2.1 OSPF protocol
OSPF, an Internal Gateway Protocol (IGP), releases route information between routers
in the single Autonomous System (AS). OSPF supports large networks and fast route
convergence and occupies few network resources. It plays a very important role in
current route protocols.
OSPF is a typical route link status protocol. It adopts OSPF routers to exchange and
save links information of the entire network, discover network topology and calculate
routes independently.
ZXCTN 6150 supports the following OSPF functions:
 Support OSPF basic functions and OSPF Version 2 (RFC 2328).
 Support neighbor discovery.
 Select Designated Route (DR) and Backup Designated Route (BDR)

through Hello protocol.
 Support various OSPF packets. Please refer to Table 8 for more details.
 Support LSA broadcast mechanism.
 Support inter-neighbor LSDB synchronization mechanism.
 Support OSPF layered route calculation.
 Support OSPF DEBUG.
Table 3-7 OSPF packet types
Type Packet name Protocol function

Neighbor relationship
1 Hello
discovery/maintenance
2 Database Description (DD) Database content collection
3 Link State Request (LSR) Database download

Type Packet name Protocol function
4 Link State Update (LSU) Database update
5 Link State Ack (LSAck) Broadcast acknowledge
 Support different OSPF link types:
 Broadcast: When link-layer protocol is Ethernet and FDDI, the default

network type is broadcast for OSPF. The protocol packets are transmitted
in the form of multicast (224.0.0.5 and 224.0.0.6).
 P2P: When link-layer protocol is PPP, HDLC, DCC link and VCG link, the
default network type is P2P for OSPF. The protocol packets are
transmitted in the form of multicast (224.0.0.5).
 Support Virtual Link and provide virtual connection between Area and Backbone.
Figure 3-7 Virtual Link
 Support Stub area and follow OSPF Stub Router Advertisement (RFC 3137).
 Support NSSA (Not-So-Stubby Area) and OSPF Not-So-Stubby Area (NSSA)

Option (RFC 3101).
 Support OSPF-TE extension functions. Link parameters are added in OSPF

notification and opaque LSA header can be adopted as standard OSPF LSA header.
OSPF-TE extends the information transferred through the protocol to build an
extension link status database which is called Traffic Engineering (TE) database.
The database has additional link attributes. According to the traditional link status
database and traffic engineering database, the equipment uses CSPF

(Constraint-based SPF) to calculate the best ETE path. OSPF-TE extension

functions comply with the following recommendations:
 Traffic Engineering (TE) Extensions to OSPF Version 2 (RFC 3630)
 The OSPF Opaque LSA Option (RFC 5250)
 Support OSPF GR functions and provide Graceful OSPF Restart (RFC 3623):
 Support GR negotiation in neighbor creation.
 After restart, the restarted node relearns the pre-restart route information
from neighbors and ages the forwarding table items of forwarding plane.
The neighbors of restart nodes can send the route information, which was
sent to neighbors before restart, to the restarted node.
 When control plane restarts, forwarding plane will not be affected.
 Support OSPF-TE GR functions and meet GR requirements of the entire TE.
 Support OSPF plain-code authentication:
 Enable or disable plain-code authentication according to interfaces.
 Configure plain-code authentication for the interface.
 Discard the received packets after interface authentication failure.
 Support OSPF MD-5 authentication.
 Enable or disable cipher-code authentication according to interfaces.
 Configure the cipher -code authentication for the interface.
 Support MD-5 authentication.
 Discard the received packets after interface authentication failure.

3.4.2.2 ISIS protocol
IS-IS is a dynamic route protocol designed by ISO for CLNP (Connectionless Network
Protocol). In order to support IP routes, IETF extends and modifies IS-IS in RFC 1195 to
apply it to TCP/IP and OSI environment simultaneously.
IS-IS, an Internal Gateway Protocol (IGP), is used in Autonomous System (AS) and is a
link status protocol using SPF algorithm to calculate the routes.
ZXCTN 6150 supports the following ISIS functions:
 Support IS-IS basic functions and follow RFC 1195.
 Support area hierarchical management. In IS-IS the area is divided into

Level1 and Level2.
 Support Hello protocol. Discover neighbors through Hello message select

DIS and create neighbor relations between DIS & all devices.
 Support broadcast link, e.g., Ethernet and Token-Ring, and P2P link, e.g.,
PPP and HDLC.
 Exchange LSP (Link State PDU) packets for Routing diffusion and LSDB
(LSP database) synchronization.
 Support ISIS protocol Debug.
 Support IS-IS TE extension functions. Exchange link information to build an

extension link status database or TE database to calculate the explicit path with
constraint conditions.
 Configure and manage TE resource attributes of local link, including TE

Router-id, link attribute/appetency, IPv4 interface address, IPv4 neighbor
address, maximum link bandwidth, reserved link bandwidth, unused link
bandwidth and TE metric.
 Distribute link TE resource information.
 Calculate TE CSPF path with CSPF algorithm.

 Support IS-IS plain-code authentication.
 Support IS-IS GR functions:
 After restart, restart node relearns the pre-restart route from neighbors
and ages the forwarding table items of forwarding plane and the
neighbors of restart nodes can resend the route which was sent to
neighbors before.
 When control plane restarts, forwarding plane is not affected.
 Support IS-IS TE GR functions and meets GR requirements of the entire TE.
3.4.2.3 BGP protocol
BGP (Border Gateway Protocol) is a dynamic route protocol between ASs. Different from
IGP such as OSPF and RIP, BGP focuses on control route transmission and best route
selection instead of route discovery and calculation. BGP runs in two ways: It is called
IBGP when it runs in one AS and EBGP when it runs between different ASs. As the
actual Internet external route protocol standard, BGP-4 is widely used between ISPs
(Internet Service Provider).
ZXCTN 6150 is able to release L3 VPN route information through BGP in MPLS network.
It supports the following BGP functions:
 Support BGP-4 basic functions and follow A Border Gateway Protocol 4 (RFC
4271).
 Support BGP message type: Open Update, Notification and Keepalive.
 Negotiate, create and maintain the parameters with BGP neighbors.
 Support IBGP and EBGP and follow their route release rules.
 Support BGP path attributes, including ORIGIN, AS path, NEXTHOP,

MED and LOCALPREFERENCE.

 Support route attribute control and policy.
 Support route aggregation.
 Support reflector functions and BGP full-connection, and follow RFC

4556.
 Support BGP MD-5 authentication and independent password configuration for

each neighbor, and follow Protection of BGP Sessions via the TCP MD5 Signature
Option (RFC 2385).
 Support BGP MP extension (L3 VPN) and follow Multiprotocol Extensions for
BGP-4 (RFC 4760). ZXCTN 6150 supports MP-BGP and uses MP-BGP as
signaling protocol in BGP/MPLS L3 VPN to transmit packets via L3 VPN route in
backbone network, and transmit VPN member information and VPN-IPV4 table
items between L3 VPN PEs.
 Support BGP to transfer IPv4 label route and follow Carrying Label Information in
BGP-4 (RFC 3107). When creating cross-domain LSP, the equipment transfers
public network routes in AS or between ASs through BGP, while carrying labels to
work with LDP or RSVP to create ETE cross-domain LSP.
Figure 3-8 IPv4 label route release
 Support BGP GR functions and provide Graceful Restart Mechanism for BGP
(RFC4724)

 After restart, the restarted node relearns the pre-restart route information
from neighbors and ages the forwarding table items of forwarding plane.
The neighbors of restart nodes can send the route information, which was
sent to neighbors before restart, to the restarted node
 Support BGP FRR and backup route selection.
 Support BGP route aggregation to aggregate multiple routes into one route
according to aggregation policy and release it to remote end.
3.5 MPLS
3.5.1 MPLS Overview
Multi-protocol label switching (MPLS) was proposed first to increase the forwarding
speed of router. Currently MPLS is developing towards backbone router and VPN
solution.
MPLS combines powerful L3 routing function of IP network and efficient forwarding

mechanism of traditional L2 network, and adopts connection-oriented mode in the
forwarding plane, which is similar to existent L2 forwarding mode. This enables MPLS to
easily realize seamless convergence of IP and L2 network, such as ATM and Ethernet.
MPLS can also provide better solutions for Traffic Engineering (TE), Virtual Private
Network (VPN) and Quality of Service (QoS). Therefore, MPLS has become an important
standard for data network scale expansion and operability improvement.
3.5.2 MPLS Network Architecture
The typical MPLS network architecture is as shown in Figure 3-9. The basic element of
MPLS network is Label Switching Router (LSR). The network domain formed by LSR is
called MPLS Domain.
The LSR located at the edge of MPLS domain and connecting other networks is called
Label Edge Router (LER); the LSR inside MPLS domain is called Core LSR. If an LSR
has one or more adjacent nodes that do not run MPLS, this LSR is LER. If all the
adjacent nodes of an LSR run MSLS, this LSR is a core LSR.

ZXCTN 6150 equipment can work as LSR and LER equipment.
Figure 3-9 MPLS network architecture
3.5.3 MPLS Basic Functions
The MPLS system architecture of ZXCTN 6150 complies with the standard: Multiprotocol
Label Switching Architecture (RFC 3031).
The label stack architecture of ZXCTN 6150 complies with the standard MPLS Label
Stack Encoding (RFC 3032).
ZXCTN 6150 equipment supports the following MPLS functions:
 Per-platform label space management function.

Per-platform label management function includes creation and deletion of label
space, and distribution and advertisement of dynamic labels.
Distribution and advertisement of labels support the following label types:
 LSP label of RSVP-TE
 PW label distributed by LDP

 Distribution of network management label
 Distribution of VRF label of L3VPN
 Domain management of static/dynamic labels

Dynamic and static labels are distributed in unified label space, but they can be
managed in different domains.
 Inlet node service and label processing function

In the inlet node of LSP, perform Push operation for data messages by service
binding or layered LSP binding.
 Outlet node service and label processing function

In the outlet node of LSP, perform label Pop operation for messages.
 Intermediate node label processing function
In the intermediate node of LSP, perform label SWAP operation for messages.
3.5.4 LDP
MPLS system has multiple label distribution protocols. LDP (Label Distribution Protocol)
is one of the basic signaling of MPLS, mainly processing establishment and maintenance
of LSP/PW. It is the most commonly used LSP/PW signaling protocol in the current
network. In case of hybrid network of the equipment and traditional IP/MPLS router, the
LSP of LDP is established by interconnection of LDP and IP/MPLS router in the current
network.
LDP specifies various messages and related processing procedure during label
distribution. It is mainly used for LSR to negotiate session parameters and distribute
labels and established label switching path (LSP). LSR connects the incoming label,
next-hop node and outgoing label corresponding to a certain FEC in the local forwarding
table together and thus forms the label switching path that crosses the whole MPLS
domain.

3.5.4.1 LDP LSP Label Advertisement and Management
After LDP session is established, LDP protocol begins to switch information such as label
mapping to establish LSP. RFC5036 defines label advertisement mode, label distribution
control mode and label retention mode to decide how LSR advertises and manages
labels.
For ZXCTN 6150, we recommend the following combination: Downstream Unsolicited

(DU) + Independent label control mode + Liberal label retention mode.
3.5.4.2 LDP LSP Label Advertisement Mode
In MPLS system, the downstream LSR distributes the labels to specific FEC and then
notifies the upstream LSR. The label is designated by the downstream LSR and is
distributed in the direction from downstream to upstream.
Label Advertisement Mode can be divided into two types.
 Downstream Unsolicited
DU (Downstream Unsolicited) means for a specific FEC, LSR performs label
distribution without getting label request message from upstream.
Figure 3-10 Downstream Unsolicited
 Downstream on Demand
DoD (Downstream on Demand) means for a specific FEC, LSR performs label
distribution after getting label request message from upstream.

Figure 3-11 Downstream on Demand
The downstream LSR feedback label mapping message depends on the label
control mode used by this LSR.
 When ordered mode is adopted, only when receiving label mapping

message returned from the downstream, or when this LSR is the outlet
node of this FEC, it will sends label mapping message to the upstream.
 When Independent mode is adopted, whether receiving label mapping

message returned from the downstream or not, it will send label mapping
message to the upstream immediately.
3.5.4.3 LDP LSP Label Distribution Control Mode
Label Distribution Control Mode refers to the processing mode when LSR distributes
labels during the establishment of LSP.
Label Distribution Control Mode can be divided into two types.
 Independent Label Distribution Control

Independent Label Distribution Control means the local LSR can distribute a label to
bind with an FEC freely and notify it to the upstream LSR, without waiting for
downstream label.
 Ordered Label Distribution Control

Ordered Label Distribution Control means for the label mapping of an FEC on an
LSR, only when this LSR has the next-hop label mapping message of this FEC, or
when this LSR is the outlet node of this FEC, this LSR can send label mapping of
this FEC to the upstream.

3.5.4.4 LDP LSP Label Retention Mode
Label Retention Mode refers to the processing mode for label mapping received by LSR
that will not be used for the time being.
Label Retention Mode can be divided into two types.
 Liberal Label Retention Mode

Liberal Label Retention Mode means the LSR will retain the label mapping received
from the adjacent LSR no matter whether this adjacent LSR is its next-hop.
Figure 3-12 Liberal Label Retention Mode
 Conservative Label Retention Mode

Conservative Label Retention Mode means the LSR will retain the label mapping
received from the adjacent LSR only when this adjacent LSR is its next-hop.
Figure 3-13 Conservative Label Retention Mode
3.5.4.5 LDP LSP Establishment
The procedure of establishing LSP on ZXCTN 6150 equipment is to bind FEC and label,
and notify this binding to the adjacent LSR on LSP. This procedure is realized by LDP.
The following is a description of the major procedure for Downstream Unsolicited
Advertisement Mode and Ordered Label Distribution Control Mode.

 When the network route changes, if an edge node finds a new destination address
in its route table, and this address does not belong to any existing FEC, this edge
node needs to establish a new FEC for this destination address.
 If the outlet node of MPLS network has labels to be distributed, it distributes a label
to the FEC and sends label mapping message to the upstream initiatively. The label
mapping message includes the label distributed and the bound FEC.
 The LSR receiving label mapping message adds a corresponding item in its label
forwarding table and sends label mapping message of the specified FEC to the
upstream LSR initiatively.
 When the LSR in the inlet node receives label mapping message, it also needs to
add a corresponding item in its label forwarding table. At this time, LSP
establishment is completed. Next the data packet corresponding to this FEC can be
forwarded.
3.5.4.6 LDP MD-5 Certification
To increase the safety of LDP protocol, some safety measures should be taken for it.
One of the measures is MD-5 certification.
MD-5 certification is encryption certification. A key and a key ID are configured on each
piece of equipment. LDP transmits messages using TCP protocol which calculates the
digest by MD-5 algorithm and adds the digest to the end of the message. TCP protocol at
the receiving end also calculates digest by MD-5 algorithm and them compares it with the
digest calculated at the transmit end. If the two are consistent, LDP passes the
certification, otherwise, it fails.
The control plane configures TCP MD-5 configuration options separately for each LDP
peer. The options include:
 Whether support TCP MD-5 encryption;
 If TCP MD-5 encryption is supported, configure encryption password.
 Support separate password configuration by each neighbor.

LDP TCP MD-5 encryption design of ZXCTN 6150 should comply with the requirements
of RFC 3036.
3.5.4.7 LDP GR Function
For the label data forwarding problems caused by the restart of LSR control plane,
especially those caused by the restart of LDP control plane, ZXCTN 6150 solves them by
LDP Graceful Restart mechanism.
 Configuration mechanism: The user can enable and disable LDP GR (disabled by
default) and relevant timer.
 LSR can remain forwarding state upon session restart, node restart or LDP
signaling restart.
 Other non-LDP faults such as board reset and interface down will not trigger GR.
3.5.5 RSVP-TE
Resource Reservation Protocol (RSVP) is designed for integrated service model, used
for resource reservation on the nodes of an LSP. RSVP works on the transport layer but
does not participate in application data transport. It is a network control protocol, and
similar to ICMP.
Simply speaking, RSVP has the following major features: the receiver-oriented, the
receiver originates the request for resource reservation and maintains resource
reservation state. Soft state mechanism is used to maintain resource reservation
information.
The extended contents of RSVP-TE from RSVP include:
 Introduce Label Request object in the PATH message of RSVP to support

originating label request; introduce Label object in RSVP Resv message to support
label distribution. In this way, CR-LSP can be established.
 The extended message can not only carry label binding information but also
limitation information, so as to support the constrained routing function of CR-LSP.

 Besides, RSVP-TE supports related attributes of MPLS-TE by extending object to

enable it to have resource reservation function.
RSVP of ZXCTN 6150, after extension, can support distribution of MPLS labels and carry
resource reservation information while transporting label binding information. The
extended RSVP is called RSVP-TE, used to establish LSP tunnel as a signaling protocol
to implement the following function.
 Establishment and maintenance of TE LSP
 Removal of TE LSP
 Error notification
 For basic functions of RSVP-TE, the following functions defined in relevant standard
should be supported:
 Support soft state mechanism of RSVP
 Support FF (Fixed-Filter style) and SE (Shared-Explicit style) resource

reservation types of RSVP-TE, among which, SE is mainly used for MBB
(Make Before Break) function
 Support MBB (Make Before Break) mechanism
 Support basic messages and processing mechanisms of RSVP
 Support messages and processing mechanisms defined by RSVP-TE for

RSVP extension to establish TE LSP
 Support establishment of TE LSP via RSV-TE
 Support LSP maintenance and digest refresh
3.5.5.1 Explicit Path Function
RSVP-TE message supports designation function of LSP node and can establish explicit
path. By explicit path technology, it can specify the paths that must be passed and those

that are not passed to arrive at a destination. The LSP paths planned can be calculated
dynamically by taking explicit path as a constraint.
For explicit path function, ZXCTN 6150 supports the following modes:
 Strict explicit path: the next hop and the previous hop are connected directly.
 Loose explicit path: the loose mode can specify which node the path must pass, but
there can be other nodes between this node and the previous hop.
 Combination of strict mode and loose mode.
3.5.5.2 RSVP MD5 Certification Function
The interface with RSVP-TE enabled supports multiple message digest algorithms. The
major ones are hmac-md5 and hmac sha-1, which can be selected by the administrator
and the default one is MD5. The certification is only directed for the interface and not for
the neighbor. Each interface supports one key.
3.5.5.3 Constrained Path Calculation Function
IGP extension (OSPF-TE/ISIS-TE) can collect interface bandwidth resource information

of the whole network form TE link database, calculate CSPF by constrained path and
calculate LSP path information required by the customer so as to drive RSVP-TE to
establish corresponding LSP.
ZXCTN 6150 supports the following constrained path calculation functions:
 Support constraint: ordinary bandwidth, prioritized bandwidth, classified bandwidth,

explicit path, destination address.
 Support path exclusion calculation.
 Support path bandwidth shared calculation.

3.5.5.4 Interface TE Bandwidth Management Function
The interface bandwidth resource can be partly or fully distributed to TE for LSP
establishment. This information need be managed and distributed in the network via
OSPF-TE/ISIS-TE.
ZXCTN 6150 supports the following functions:
 For interface type, only ordinary physical interface supports this function. Interface
TE bandwidth management is not required for VLAN sub-interface and bound
interface.
 Basic management on ordinary bandwidth and prioritized bandwidth of TE interface.
 Provide interface for OSPF-TE and ISIS-TE to enable them to get bandwidth
information of TE interface and perform the flooding function.
3.5.5.5 Bidirectional LSP
To improve the network performance and protection capability, ZXCTN 6150 supports
establishment of bidirectional LSP, supports bidirectional same routing and supports
bidirectional LSP management in NMS as one entity.
 Support establishment of bidirectional LSP via Associated mode
 Support establishment of bidirectional LSP via Co-Routed mode
3.5.5.6 Cross-Domain RSVP-TE
In the application of ZXCTN 6150, in some case, cross-domain (AS) service dispatching
may be needed. For example, if the service of NodeB needs to be transported to the
remote RNC via the core layer router network, and if the core layer network also supports
cross-domain RSVP-TE, RSVP-TE can be used to establish cross-domain (AS) E2E
LSP.

Figure 3-14 Cross-domain RSVP-TE
When the service of NB1 needs to be dispatched to the remote RNC2, E2E RSVP-TE
LSP need be established, which is PE1->PE3->SR1->SR2->PE4.
RSVP-TE can specify cross-domain edge node, define loose ER-Hop, calculate path
using CSPF in the domain, establish an E2E cross-domain LSP in this way and thereby
provide PW service between PE1 and PE4.
3.5.5.7 RSVP-TE GR
Restart of RSVP-TE control plane will cause LSR restart and data flow interruption of its
neighbor. RSVP-TE Graceful Restart mechanism can be used to reduce the impact of
RSVP-TE control plane restart.
ZXCTN 6150 supports the following functions:
 Configuration mechanism: The user can enable and disable RSVP-TE GR and
relevant timer.
 LSR can remain forwarding state when RSVP-TE control plane is restarted.
 When the number of messages loss is detected exceed the limit, RSVP-TE GR will
also be triggered. Other non-LDP faults such as board reset and interface down will
not trigger GR.

 The head node, intermediate node and end node of the link established by
RSVP-TE all support RSVP-TE GR.
 In case of co-networking of GR and FRR, the right operation sequence can be

adopted to avoid irrecoverable faults when nodes and auxiliary restart nodes.
3.6 MPLS L2 VPN
MPLS L2 VPN is divided to VPLS and VPWS. VPWS is applicable to point-to-point

networking mode. VPLS can support point-to-multipoint and multipoint-to-multipoint
networking mode. In point of the user, the whole MPLS network is a L2 switching network
through which L2 connection can be established between different sites. ZXCTN 6150
equipment supports complete VPWS and VPLS functions.
3.6.1 VPWS
VPWS (Virtual Private Wire Service) is a L2 tunnel technology under MPLS technology,
used to provide point-to-point virtual private wire service. The PE equipment at the edge
of operator’s network and P equipment inside the operator’s network are all equipment to
be maintained and managed by the operator. The customer edge (CE) equipment
access the system via Ethernet link. VPWS transmits user L2 data transparently point to
point in MPLS networks.
Figure 3-15 VPWS basic model
ZXCTN 6150 product supports VPWS, including:
 Access AC types support: port, port + VLAN, port + QinQ, AC access of ATM
service and TDM service is supported.

 For VPWS NNI-side interfaces, all NNI interfaces including Ethernet should be
supported.
 PW establishment and maintenance:
 Support static configuration, establishment and maintenance of PW.
 Support dynamic establishment and maintenance of PW using LDP

extended signaling via Martini mode, in compliance with RFC 4447
(Packet PW) and RFC 5287 (TDM PW).
 Extended LDP protocol also supports the following functions besides the basic
functions:
 Support TLV that extends standard LDP to carry PW ID, including 128
types PW ID FEC TLV and 129 type general PW ID FEC TLV.
 During PW establishment, adopt DU (downstream unsolicited) mode for

label distribution sequence and label retention mode for liberal label
retention.
 Support the negotiation of PW data interface parameters, including the

negotiation of MTU, maximal number of ATM cascade cells and
fragmentation capability.
 Support control word negotiation.
 Support PW connectivity test mechanism and method (VCCV).
 Support PW state notification.
 VPWS tunnel technology can base on static LSP, LDP LSP or RSVP-TE LSP.
3.6.2 VPLS
VPLS (Virtual Private LAN Service), integrating the advantages of Ethernet and MPLS
technology, is a multipoint-to-multipoint L2 VPN technology. VPLS emulates all functions
of traditional LAN, with a purpose to connect multiple Ethernet sites that is scattered in
area via the operator’s IP/MPLS backbone network and make them work like a LAN.

Figure 3-16 VPLS basic model
ZXCTN 6150 product supports VPLS including:
 Comply with LDP extension protocol RFC 4762 to support establishment and
maintenance of different types of PW and so support VPLS service.
 Access AC types supported : port, port +VLAN and port +QinQ
 AC Filter modes include:
 traffic be filtered based on unicast packet on ACs
 traffic be filtering based on broadcast packet on ACs
 traffic be filtering based on multicast packet on ACs
 traffic be filtered based on unknown packet on ACs
 Support to establish managment instances for VPLS on PE.
 Support MAC address learning.
 Support broadcasting of broadcast messages on PW.

 VPLS tunnel technology can base on static LSP, LDP LSP or RSVP-TE LSP.
 Support VPLS forwarding plane encapsulation technology.
 Support MAC address aging function.
 Support controlling the number of MAC address tables under each VPN
 Support static MAC; Enable and disable MAC address learning function.
 Support TAG/RAW mode.
3.6.3 H-VPLS (Hub-Spoke)
VPLS requires full connection between PE. As a result, when VPLS network scale is
large, the number of PWs is huge; PW signaling overhead is high; and network
management and expansion will be very complicated. H-VPLS divides PE to UPE and
NPE. UPE is mainly used to connect CE and service provider network as MTU to access
VPN; NPE is located at the edge of the core areas of VPLS network, providing
transparent transmission of user messages on core network. UPE need not be
connected with all NPE; full connection only needs be established between NPE. By
classification, H-VPLS reduces the number of PW and signaling load.
 LSP access mode
As aggregation equipment MTU, UPE is accessed to the link U-PW only by a virtual
connection (to establish U-PW, establish VSI instance on NPE and UPE equipment,
specify peers and the PWID on the two devices must be the same), and no virtual
connection is established between UPE and other opposite ends.

Figure 3-17 H-VPLS (Hub-Spoke)
Data forwarding flow is as follows:
 UPE sends the message from CE to NPE 1 and places in VC label corresponding to
U-PW (VC label distributed to NPE 1 as a multi-PW multiplexing separation sign).
 After receiving the message, NPE 1 first decides VSI of the message according to
the VC label, and then presses in VC label corresponding to N-PW according to the
destination MAC and then forwards this message.
 After receiving the message from N-PW side, NPE 1 presses in VC label
corresponding to U-PW and sends the message to UPE, and then UPE forwards
the message to CE.
When data exchange between CE 1 and CE 2 is one between local CEs, if UPE has
bridging capability, UPE will complete message forwarding between the two directly
without sending the message to NPE 1. However, for the first data message or broadcast
message with destination MAC unknown, UPE will still forward the message to NPE1 via
U-PW while broadcasting the data to CE2 and then NPE copies the message and
forwards it to the opposite-end CE.
ZXCTN 6150 supports H-VPLS, in compliance with draft-ietf-l2vpn_vpls_ldp.

3.6.4 Multi-Segment Pseudo-Wire
Pseudo-wire is usually in single segment E2E mode. However, in the following three
cases, a single-segment pseudo-wire cannot meet the requirement:
 The source and sink PEs of the service are not in the same domain (AS) and
signaling connection or tunnel cannot be established between the two PEs.
 The source and sink PEs of the service run different signaling, for example, one end
runs LDP and the other run RSVP.
 If the access equipment can run MPLS but cannot establish substantial LDP
sessions, UFPE (User Facing Provider Equipment) can be used as U-PE;
high-performance equipment S-PE can be used as the switching node of LDP
sessions, like a signaling reflector to realize tunnel aggregation of pseudo-wire.
Multi-Segment Pseudo-Wire means there are multiple segmented PWs between U-PE
and U-PE, as shown in the Figure 3-18.
Figure 3-18 Multi-Segment pseudo-wire
The forwarding mechanism of U-PE in multi-segment PW is the same as that in

single-segment PW except that in multi-segment forwarding, label switching at PW Label
layer should be performed at S-PE (Switching PE). Multi-segment PW needs to connect
single-segment PW at both sides via PW switching equipment S-PE and complete label
switching at PW layer on S-PE.
ZXCTN 6150 supports static-static mode configuration of multi-segment PW.

3.6.5 PW State Notification
When LDP is used as PW signaling, when access chain AC is down, LDP signaling will
notify the neighbor to remove PW label. When AC is up again, LDP will negotiate again
to create PW label. This mechanism will lead to repeated deletion and creation of PW
label when AC chain oscillates, which will affect network stability.
To prevent PW label oscillates with the oscillation of AC, PE state notification technology
can be used. It is required that PW label created by LDP should not be affecte3d by AC
chain state. The notification does not serve as the standard for creation and deletion of
LDP PW label. The way to realize this is: on the basis of Martini, dynamic PW adds
optional state parameters in mapping message and supports Notification message.
When the network is unstable, Notification message can reduce message exchange. For
example, when AC chain oscillation occurs on PE equipment, it only needs to send
Notification message notifying the state of this AC; and the opposite end will not remove
VC when receiving this message. On the contrary, in Martini mode, when AC chain
oscillation occurs on PE equipment, it will send Withdraw message continuously, which
leads to repeated creation and deletion of PW.
ZXCTN 6150 product supports PW state notification.
3.7 BGP/MPLS L3 VPN
ZXCTN 6150 conforms to RFC4364 protocol with its L3 VPN adopting BGP/MPLS VPN.
The basic network architecture is shown in the Figure 3-19.
Figure 3-19 BGP/MPLS VPN network architecture

3.7.1 VRF
VPN functions are mainly implemented on PE, which sets up VRF (Virtual Routing and
Forwarding) table for each VPN. Any customer and station belong to VPN can access to
the VRF table of this VPN to realize routing and forwarding separation of different VPN
customers. ZXCTN 6150 completely support VRF forwarding instances.
ZXCTN 6150 supports distributing VRF per route mode as shown in Figure 3-20. PE1
distributes a different L3VPN label (ingress label) with each routing item it distributes to
PE2. The private network label corresponds to VPN route R1 is L1, and that corresponds
to R2 is L2. PE2 determines next-hop and egress based on the popping-up VPN label
matching VRF IP routing item. In this way forwarding from PE to CE can be directly
implemented.
Figure 3-20 Distributing VRF per route mode
3.7.2 L3 VPN Access
CE is client edge equipment. Acting as VPN managed by the operators, L3 VPN asks for
nothing special from CE equipment. CE can be host, Ethernet switch or router. PE-based
BGP/MPLS IP VPN is especially for IP services (the so-called L3 VPN services).
Customers can get access to operator’s network via any L2 services, which have been
terminated at the edge of operator’s network however.
ZXCTN 6150 supports multiple accesses to L3 VPN including IP service, VLAN

port-based IP service and VPWS/VPLS terminated to L3 VPN.

3.7.3 L3 VPN Tunnel
P is the core node in MPLS network. It uses common MPLS protocol and process.
ZXCTN 6150 supports the following three ways to pre-set up LSP tunnel between PE.
 Adopting RSVP-TE as signaling protocol to support traffic engineering
 Adopting LDP as signaling protocol without support for traffic engineering
 Adopting static tunnel with manually configured management plane
3.7.4 Customer Route Learning and Launching
In L3 VPN network PE and CE have to exchange route information. ZXCTN 6150 can
implement customer route learning in the following three ways as shown in Figure 3-21.
 Static route
 Open Shortest Path First (OSPF)
 Exterior gateway protocol BGP
Figure 3-21 Route exchange between PE and CE
After learning CE routes, PE transmit VPN composition message and VPN-IPv4 routes
via MP-BGP, which uses VPN-IP addresses (composed of RD and IPv4 address). Thus
different VPN can use the overlapped IPv4 address and avoid VPN-IP addresses
conflict.
ZXCTN 6150 supports control over VPN route launching via RT (Router Target). ZXCTN
6150 supports egress RT and ingress RT configuration. With RT control, it can easily

implement L3 VPN networking such as Intranet VPN, Extranet VPN and Hub-Spoke
VPN.
3.7.5 Cross-domain VPN
Usually MPLS VPN system architecture runs in an autonomous system. VPN routing
information can be only distributed on demands in the autonomous system. ZXCTN 6150
supports the following methods to implement cross-domain VPN:
 Cross-domain VPN Option A: VRF-to-VRF. Two edge ASBR of two AS domains

work as PE and CE for each other, as shown in the following figure.
Figure 3-22 VRF-to-VRF
3.7.6 VPN FRR
ZXCTN 6150 supports complete VPN FRR, making end-to-end service convergence
recovery time independent from the scale of private network route, and to achieve
reliable and easily deployed networks.
3.8 QoS feature
3.8.1 QoS function
ZXCTN 6150 provides standard-based support for DiffServ, including traffic classification,
policing, shaping, congestion control, queue scheduling, etc. Network carrier configures
the different QoS for access services to provide DiffServ.

The equipment supports 8 PHBs (Per-hop Behavior) defined in the standards, e.g., BE,
AF1, AF2, AF3, AF4, EF, CS6 and CS7, to enable network carrier to provide DiffServ for
users and transport data, voice and video services at the same time.
If there is no QoS or traffic classification or a message does not match any classification
rule, this message will be processed in the BE (Best-Effort) way.
 Traffic classification
ZXCTN 6150 supports the classification based on port, L2, L3 and L4 packet head,
e.g., physical interface, source address, destination address, MAC address, IP or
applications port number.
 Policing
ZXCTN 6150 supports traffic policing and CAR (Committed Access Rate), uses
ACL to control service access, and implements traffic-based CIR, CBS, EIR and
EBS. Message can be discarded or colored under some certain conditions. It also
supports ingress and egress policing.
 Congestion avoidance and control

Congestion control can discard few packets in network congestion.
ZXCTN 6150 congestion avoidance and control
 Support WRED (Weighted Random Early Detection) and queue

congestion control.
 Support TD (Tail Drop) cache policing.
 Queue scheduling
ZXCTN 6000 employs mixed queue scheduling which has the following functions.
 Each port supports at least 8 priority queues.
 Each queue supports the minimum/maximum bandwidth management.
 Support WRR (Weighted Round Robin) scheduling.
 Support SP (Strict Priority) scheduling.

 Support SP+WRR mixed scheduling.
 Shaping
Traffic shaping limits the traffic and the burst of a connection out of a network so
that the messages are transmitted at a smooth rate.
ZXCTN 6150 supports priority-queue-based and port-based traffic shaping.
 H-QoS
ZXCTN 6150 supports adequate flexible management hardware queues, which can
support multi-level HQOS scheduling, which matches precise user’s demands for
multi-service and QoS management.
3.8.2 MPLS QoS feature
ZXCTN 6150 supports the MPLS QoS based on DiffServ model. MPLS QoS fulfills
priority mapping among MPLS, IP and Ethernet messages, and differentiates data flows
of different services according to EXP value in the label to provide DiffServ and assure
QoS of voice, video, etc. ZXCTN 6150 supports two types of carrier MPLS QoS tunnels:
 Uniform Tunnel
 Pipe Tunnel
MPLS QoS based on DiffServ model supports good scalability and implements ETE QoS
via tunnel. The congestion certainly leads to delay and packet loss, which will affect QoS
of some services which are sensitive to delay and packet loss. MPLS-TE efficiently
manages bandwidth resources to improve network QoS, so as to prevent out-tunnel
congestion from affecting in-tunnel service. The bandwidth management and MPLS-TE
tunnel can implement the scheduling based on CoS. For example, when EF, AF and BE
services are in the same MPLS-TE tunnel, EF and AF services will be affected seriously.
ZXCTN 6150 combines MPLS-TE and DiffServ to enable IP/MPLS core network to
identify different services and create tunnels accordingly, so as to guarantee the
bandwidth of high-priority service. ZXCTN 6150 supports the QoS scheduling in MPLS
VPN and the Diff-Serv scheduling in VPN, so as to forward VPN key services in high
priority.

ZXCTN 6150 supports service based PW and maps and the PW to the corresponding
MPLS tunnel to implement service-based ETE QoS. It supports simple and easy
deployment, bandwidth planning & management to offer differentiated multiservice
management and operation.
3.8.3 Ethernet QoS feature
As metro network provides Ethernet-based service, DiffServ is needed. ZXCTN 6150

dispatches service and controls congestion according to VLAN frame priority. It can map
IP message priority or MPLS message EXP priority to Ethernet message VLAN priority
for unified service scheduling.
3.9 OAM Features
ZXCTN 6150 provides multiple OAM mechanisms. It supports MPLS/MPLS-TP, Ethernet

OAM, Ethernet link OAM and BFD. It can implement fast failure detection to trigger
protection switching and guarantee carrier-class service quality of service in packet
transport network.
3.9.1 MPLS OAM
3.9.1.1 Tunnel OAM
MPLS Tunnel OAM provides MPLS network with complete failure detection and
positioning mechanisms, and network performance monitoring at Tunnel layer.
MPLS Tunnel OAM mechanism can effectively detect, confirm and position the cache
and monitor network performance within MPLS layer. The equipment can use OAM
detection status to trigger protection switching and realize fast failure detection & service
protection.
ZXCTN series equipment supports MPLS Tunnel OAM functions such as Ping and
Traceroute etc.

 LSP BFD
LSP Ping expands the checkout of data layer while BFD defines a light-load
checkout measurement of data layer (the fixed frame length of BFD suits
implementation by hardware).
BFD for LSP carries BFD packets on the detected LSP tunnel. The gone-through
BFD packets data must be exactly the same with that for LSP path. When they go
out at the LSP egress, BFD packets are submitted to the upper layer module for
checkout.
If BFD is adopted to detect LSP defects and FRR is implemented for protection,
BFD detection period should be set larger than FRR protection speed. When FRR
protects LSP, it may cause BFD packet jitter or even loss. So when FRR completes
LSP protection, it’s not necessary for the upper layer to detect LSP failure.
Otherwise it may leads to frequent switching between upper and lower layers.
If BFD for LSP is not used with LSP Ping, parameters in BFD configuration process
should be manually specified.
3.9.1.2 PW OAM
PW OAM provides complete failure detection, positioning mechanism and network

performance monitoring at PW layer.
PW OAM mechanism can effectively detect, confirm and position the defects, and
monitor network performance in PW layer. The equipment can use OAM detecting status
to trigger protection switching and implement fast failure detecting and service protection.
ZXCTN series equipment supports PW OAM functions such as Ping and Traceroute.
 PW BFD
The specific requirements and processing process of BFD for PW is similar to BFD
for LSP. The major difference lies in the fact that BFD is encapsulated under PW.

3.9.2 MPLS-TP OAM Function
OAM functions which are implemented by TMS, TMP and TMC of MPLS-TP are shown
in the following table. Please refer to IETF draft-bhh-mpls-tp-oam-y1731-04.txt needs for
OAM functions.
MPLS-TP failure management functions are shown in the Table 3-8.
Table 3-8 MPLS-TP OAM failure management functions
Function type Description
Loss Of Continuity (LOC) check
Merger Mistakes (MMG) check

Continuity and connectivity (CC)
Abnormal MEP(UNM) check
Abnormal perios (UNP) check
Alarm Indication Signal (AIS) Alarm Indication Signal (AIS) check
Remote Defect Indication (RDI) Remote Defect Indication (RDI) check
Unicast loopback - bidirectional

LoopBack (LB)
connectivity confirmation
Lock (LCK) Lock (LCK) packet transport
ZXCTN 6150 MPLS-TP performance management functions are shown in the Table 3-9.
Table 3-9 MPLS-TP performance management functions
Function type Description
Local/remote frame loss check

Frame loss rate check
Loss Measurement (LM) Dual ends Local/remote errored second, severely
errored second and unavailable second
check.
Delay Measurement Dual Dual process frame delay check

(DM) processes Dual process delay change
 Y.1731-based MPLS-TP

OAM function of each hierarchy of MPLS-TP is based on Y.1731 PDU expanded

format. ZXCTN network adopts MPLS-TP and the OAM packets are composed of
Y.1731 OAM PDU & outer layer forwarding label stack. The label stack carried by
forwarding label stack is the same with that of the data packets to make sure that
OAM packets are correctly forwarded on MPLS-TP paths of different layers.
Based on IETF GACH coding format, referring to OAM PDU format definition of
ITU-T Y.1731 Ethernet service, OAM PDU coding format in ZXCTN network is
shown in Figure 3-23.
Figure 3-23 OAM PDU coding format
Table 3-10 OAM types that ZXCTN 6150 supports
Virtual Virtual Virtual

Type Function Section Path (VP) Channel
(VS) OAM OAM (VC) OAM
Continuity check
and connectivity
Support Support Support
verification
(CC/CV)
Active Failure
Remote Defect
OAM management Support Support Support
Indication (RDI)
Alarm suppression
NA Support Support
(FDI/AIS)
Lock (LCK) Support Support Support

Virtual Virtual Virtual

Type Function Section Path (VP) Channel
(VS) OAM OAM (VC) OAM
Customer Signal
NA Support Support
Failure (CSF)
Loss
Performance
Measurement Support Support Support
monitoring
(LM)
LoopBack (LB)
Support Support Support
Failure (OAM packets)
management
Trace(LT) NA Support Support
and
Test (TST) Support Support Support
positioning
Lock (LCK) Support Support Support
OAM on
demand Loss
Performance (LM)
monitoring Delay
(DM)
Others Automatic protection switching Support Support Support
Notes: NA represents Not Adaptive
3.9.3 Ethernet OAM
Ethernet OAM is implemented hierarchically.

Figure 3-24 Ethernet OAM implementation in hierarchy
As shown in the above figure, Ethernet OAM is divided into the following two levels:
 Link-level Ethernet OAM: mainly applied between PE-CE-user equipment (last mile)
Ethernet physical link to monitor the link status between user network and
operator’s network. The typical protocol is EFM OAM.
 Network-level Ethernet OAM: mainly applied in access aggregation layer of the

network to monitor the connectivity of the whole network and to position the
connectivity fault. The typical protocol is CFD.
The typical Ethernet OAM protocol for each level is shown in the Table 3-11.
Table 3-11 Typical Ethernet OAM protocol
Application Protocol
Protocol name Description
level standard
Providing link performance

monitoring, failure detecting,
EFM OAM Link level IEEE 802.3ah alarm, and loopback test for the
link directly connecting two
equipment

Application Protocol
Protocol name Description
level standard
Mainly applied in L2 network to

IEEE 802.1ag/ check link connectivity and to
CFD Network level
ITU-T Y.1731 confirm the location of the
failure
This section gives an introduction to ZXCTN 6150 network-level Ethernet OAM functions.
The next section will shed light on link-level OAM functions.
ZXCTN 6150 supports IEEE 802.1ag and ITU-T Y.1731 at the same time to realize fault
management and performance monitoring of Ethernet services, as shown in Table 3-12.
Table 3-12 ZXCTN 6150 Ethernet OAM functions
Function Description Conforms to

CCM Connectivity check
RDI Remote Defect Indication

IEEE 802.1ag
LB Unicast loopback
LT Link Track
ETH-CC Connectivity check
ETH-LB Loopback
ETH-LT Ethernet link track
ETH-AIS Alarm Indication Signal
ETH-RDI Remote Defect Indication
Bi-directional packet
Bi-directional LM dropping ratio
measurement ITU-T Y.1731
Single directional packet

Single directional LM dropping ratio
measurement
Bi-directional delay
Bi-directional DM
measureent
Single directional delay

Single directional DM
measurement

3.9.4 Ethernet Link OAM
ZXCTN 6150 supports 802.3ah-based Ethernet link layer OAM functions to realize
loopback and link monitoring of Ethernet access link.
Table 3-13 Ethernet Link OAM
Functions Description Conforms to
Near end OAM entity

discovers far end OAM
OAM discovery entity, and sets up stable
session with it, supporting
active and passive mode.
OAM packets receiving

OAM packet delivery
and sending
Monitoring link event,

IEEE 802.3ah
sending notifying packet
OAM link monitoring and reporting it to the
network management
system
Loopback command
OAM remote loopback
sending and responding
OAM variable request MIB Query request sending

query and responding
3.9.5 BFD
3.9.5.1 BFD Overview
BFD (Bidirectional Forwarding Detection) is a kind of failure detection function with light
load and short duration. It can implement failure detection on any type of channels
between systems including directly-connecting physical link, virtual circuit, tunnel, and
multi-hop route.
BFD can implement fast detection of communication failure between adjacent systems. It
sends detection packets regularly on the channel where BFD session is set up between
a pair of systems. If a system hasn’t received the detection packets from the peer end in

a specified time, a failure is considered to occur at a certain part on the bidirectional

channel between this system and its adjacent system. In this way a substituting channel
can be quickly set up or traffic can be quickly switched to other links. It’s similar to
neighbor detection part in many routing protocols with the advantage of quick detection.
BFD sends UDP (User Datagram Protocol) packets.
BFD provides the following functions:
 Providing failure detection with light load and short duration for channels with BFD
session set up.
 Implementing real-time detection of any media and any protocol layer with a single
mechanism.
 Reducing service data loss.
3.9.5.2 BFD for OSPF
Usually OSPF implements route convergence by using OSPF Hello frames detection
mechanism to determine link status. With this method, Hello frame sending period limits
cause slow route convergence in case of topology change. BFD is a universal fast
detection mechanism. Initiating BFD between OSPF neighbors can dramatically improve
failed link detection rate, so as to improve route recovery convergence rate.
At this time BFD encapsulation is delivered by signaling channel in the normal way of
IP/UDP. BFD session setting up process is established by management plane based on
OSPF instance interface.
BFD session detects alarm message and then notifies OSPF instance.
3.9.5.3 BFD for ISIS
ISIS relies on ISIS protocol frame detection mechanism to determine link status when it
implements route convergence. With this method, ISIS protocol frame sending period
limits cause slow route convergence in case of topology change. BFD is a universal fast
detection mechanism. Initiating BFD between ISIS neighbors can dramatically improve
failed link detection rate, so as to improve route recovery convergence rate.

ISIS interface.
BFD session detects alarm message and then notifies ISIS.
3.9.5.4 BFD for VRRP
VRRP group main/standby nodes check whether the other side has failures or not by
slow hello protocol. With this method, hello packets sending period limits cause second
level failures. BFD is a universal fast detection mechanism. Initiating BFD detection
between VRRP main/standby equipment can dramatically improve failed link detection
rate, so as to improve VRRP switching rate.
VRRP group interface.
BFD session detects alarm message and then notifies VRRP group to take switching.
3.10 Protection Features
3.10.1 Equipment-level protection
3.10.1.1 SME 1+1 protection
SME card consists of CONTROL unit, switching unit, clock unit and other communication
units. SME 1+1 protection is available when two cards are installed.
When SME software or hardware goes wrong or receives active/standby switching

indication, active/standby SME will make the switching for protection.
ZXCTN 6150 SME 1+1 protection parameters are shown in the following table:

Table 3-14 ZXCTN 6150 equipment-level protection
CONTROL unit
Protected unit Switching unit
Clock unit
Backplane hardware or software fault

Manual delivery of switching command
Switching
Manual SME pullout
condition
Backplane soft reset
Backplane hard reset
Restoration
Non-return mode
mode
Protection
< 50ms
time
3.10.1.2 Power board 1+1 protection
ZXCTN 6150 is equipped with two -48V DC power boards both of which act as hot
backup for each other. When one power board fails, the other will keep the equipment in
normal operation.
3.10.2 MPLS Network-level protection
3.10.2.1 MPLS Tunnel Protection
Linear protection based on MPLS single directional path is implemented by hot-standby.
Hot-standby LSP initiates set-up after main tunnel LSP is created. When main tunnel
LSP failure message is delivered to ingress router, the traffic will be switched to
Hot-standby path LSP. When main tunnel LSP recovers, the traffic will be switched back.
The protection process is shown in the Figure 3-25.

Figure 3-25 MPLS Tunnel 1:1 protection
Because of permanent Merge dual-receiving at destination end for path protection based
on single directional MPLS tunnel, it is unnecessary to implement APS protocol for
switching. Sending port is determined at source end based on the failure status of work
path and protection path.
 Checking methods:
 Delivery and delete of manual switching command
 Link failure in physical layer or path service layer
 Path OAM check failure
3.10.2.2 FRR Protection
FRR (Fast Reroute) is a protection implemented by reserving extra resource for fast local
protection. It is usually deployed in network with high reliability requirement. When there
is a local failure in network, FRR can quickly switch the traffic to Bypass Tunnel with little
impact on data service.
 Basic concept of FRR
 Bypass: Facility Backup. Using one protection path to protect multiple

LSP. The protection path is called Bypass LSP.
 PLR: Point of Local Repair. Head node of Bypass LSP. It must be on the
main LSP path and not be the tail node.

 MP: Merge Point. Tail node of Bypass LSP. It must be on the main LSP
path and not be the head node.
 Link protection: there is a link directly connecting PLR and MP. Main LSP
goes through this link. When the link fails, traffic can be switched to
Bypass LSP.
 Node protection: PLR and MP are connected by a node. When main

Tunnel goes through this node, traffic can be switched to Bypass LSP.
 FRR protection conforms to RFC 4090 protocol.
 FRR protection mode

FRR is a kind of local protection. It protects the link or node connected to PLR
between PLR and MP. The basic principle of FRR is to use a pre-setup Tunnel to
protect one or multiple Tunnels. The equipment supports Bypass mode.
Bypass Tunnel is a Tunnel without FRR attribute. When the tunnel is designated to
protect other Tunnels going through a physical interface, the Tunnel becomes
Bypass Tunnel. Bypass Tunnel setup is triggered by manual configuration on PLR.
That is to say, this Tunnel cannot be embedded and protected by FRR.
FRR protection is shown in the following figure.
Figure 3-26 FRR protection
Bypass is shown in the above figure. The blue one is main LSP and the red one is
Bypass Tunnel. FRR protects link and node connecting to PLR. When the link or

node fails, data on main Tunnel will be switched to Bypass Tunnel. After the
switching, the original LSP path information will be deleted.
 FRR protection parameters
 ZXCTN 6150 supports FRR at the following interface types: 100M

Ethernet interface, GE interface 10GE interface and CPOS interface.
 Supporting node protection and link protection.
 Providing protocol layer and physical layer failure detection.
 Performance indexes: when the protected LSP fails, user traffic is

switched to backup tunnel within 50ms.
 Head node can configure multiple optional paths for protection LSP and
permit re-optimization of LSP. The principle of path optimization is less
hops, more available resource, and smaller metric.
 Supporting two types of backup bandwidth: guaranteed backup

bandwidth, and non-guaranteed backup bandwidth. With finite backup
bandwidth, backup tunnel provides bandwidth protection and the sum of
required bandwidth for all protected LSP using this backup tunnel should
not exceed backup bandwidth. While with infinite backup bandwidth,
backup tunnel does not provide bandwidth guarantee.
 By expanding FAST-REROUTE object, users can select whether to take

backup path control at the head node. Configuration interface information
(bandwidth, link attribute, and hop limit) will be provided when it is
necessary.
3.10.3 MPLS-TP Network-Level Protection
3.10.3.1 MPLS-TP Tunnel/PW 1+1 and 1:1 Protection
In Tunnel 1+1 protection, services are transmitted simultaneously in both working &
protection channels and received selectively. When a fault occurs to working channel,

the receiving end selectively receives the services from protection channel for service
switching.
Figure 3-27 Unidirectional 1+1 protection switching
In 1+1 architecture, the protection tunnel is private for each working tunnel. The working
tunnel bridges the protection tunnel at the source end of the protection domain. 1+1
tunnel protection is a kind of unidirectional switchover, which means only the links under
affection switches over to the protection tunnel. To avoid single-point fault, the working
tunnel and protection tunnel should use independent routes.
Figure 3-28 Unidirectional 1+1 Tunnel Protection Switching (Working Link Fault)
Tunnel 1:1 protection reserves unidirectional service sending and receiving. Extension
APS protocol is transferred via the protection tunnel, sending mutual protocol status and
switchover status. Devices of both sides implement service switchover as per protocol
and switchover status.
Figure 3-29 Bidirectional 1: 1 Tunnel Protection Switching Architecture)
In 1:1 architecture, the protection tunnel is private for each working tunnel. The
switchover of 1:1 path protection is bidirectional switchover. In other words, the affected
connections and unaffected connections are switched over to the protection tunnel. To

avoid single-point fault, the working tunnel and the protection tunnel should follow
independent routes.
Figure 3-30 Bidirectional 1:1 Tunnel Protection Switching (Working Connection Z-A
Fails)
When ZXCTN 6150 configures PW 1+1/1:1 protection, it supports services with the sink
source but different sink destination. According to customer service failure signal, it
implements protection switchover.
When ZXCTN 6150 configures 1:1 protection, it usually allows the protection tunnel to
bear services.
3.10.3.2 Ring Protection
Ring protection saves fiber and network resource, and fulfills protection switching within
50ms in compliance with strict protection time requirements of the transport network.
ZXCTN 6150 supports Wrapping and Steering ring protection, and shared ring
protection.
 Wrapping Protection
When network node is found failed, the neighbor node of the fault will send
switchover request to the neighbor node via APS protocol. When one node inspects
fault or switchover request, common services sent to the invalid node will be
switched over to another direction (far from the invalid node). When the network
recovers or APS protocol request disappears, services will be restored to the
original path. The protection principle is as shown in the following table.

Figure 3-31 Wrapping Protection

 Shared Ring Protection

Shared Ring protection adopts nested LSPs to achieve the open working loop and
the closed protection loop, which is on the reverse direction of the working loop, for
each node on the ring. When the service is added onto the ring , the added service
tunnel is label stacked on the shared working tunnel and only the shared working
tunnel is protected by Wrapping protection. As a result, there are 3 layers of labels,
which are PW label, service LSP label and outer shared ring LSP label, when the
service is transport on the ring. The service LSP is transported transparently on the
shared ring LSP and the inner labels cannot be handled and processed during the
transmission. All the services that dropped in the same node share the same
working and protection ring tunnel. If some parts of ring fail and are detected by
TMS, only the shared the working tunnel need to be protected, which increases the
switching efficiency.

3.10.3.3 Dual-Homing Protection
Dual homing is a network topology in which base station services go through the bearer
network and then terminate at two service access point equipments, both of which
connect the RNC. Based on this network topology, dual homing protection is
implemented by employing some related technique to provide protection for the service
access point equipments and access links. When failures occur in the main access point
equipment or access link, service frames can be transported to the RNC through the
redundant access point device or access link.
Figure 3-32 Dual-Homing Protection

As shown above, the bearer network connects to the main and redundant GE interfaces
of the RNC through two access devices, of which one is working (device B here) and the
other is redundant (device C here). In normal state, the working path is shown as red real
line by NodeB-A-B-RNC. When a failure occurs at device B or on the access link
between device B and the RNC, related OAM frames will sent to device A. Dual homing
protection works and switchover happens at device A. Meanwhile the RNC detects the
failure and switches to device C for transmitting and receiving service frames. The
working path now is shown as the red dashed line.
3.10.3.4 DNI (Dual Node Interconnection) Protection
In the case bearer networks employ ring protection mechanisms, two architectures can
be deployed when two rings interwork with each other, one of which is single node
interconnection and the other one is dual-node interconnection. There is only one
interworking node in the single node interconnection case, so this architecture is fragile
and the interconnection services will interrupt when the interworking node fails. Therefore
dual-node interconnection (DNI) can be deployed to enhance the reliability of the
interconnection services. In the architecture two rings interwork through dual nodes with
the redundant mechanism, DNI can be adopted to ensure that the interconnection
services between the two rings be transported through the redundant interconnection
node in case that the working one fails.
Figure 3-33 DNI Protection
ZXCTN 6150 supports DNI protection of two architecture models shown as above, and
provides protection against interconnection node defects, link defects and multi-node
failures.

3.10.4 Other Protection Manners
3.10.4.1 Ethernet LAG Protection
Link Aggregation binds a group of same-rate physical Ethernet interfaces as a logic

interface (link aggregation group) to increase the bandwidth and provide link protection.
ZXCTN 6150 supports LAG protection of UNI-side Ethernet port.
Ethernet LAG protection can share or not share port load. In load sharing mode, the
device will share services to multiple physical ports of the aggregation group
automatically. When one physical port fails, the traffic on this port will be shared to other
physical ports automatically. When the failure recovers, the traffic will be redistributed to
make sure the load shared by all aggregated ports. In non-load sharing mode, services
only exist in the active link in the aggregation group and the LAG is only a backup
mechanism. When the active link of the aggregation group fails, the system will activate
the standby link to protect the traffic of the failed link.
3.10.4.2 Ethernet Spanning Tree Protection
STP (Multiple Spanning Tree Protocol) can be used to eliminate network loop. STP
blocks some redundant paths with some algorithms and break down loop networks into
no-loop tree networks to prevent messages from growing and unlimitedly recycling in
loop network to avoid broadcast storm. The main difference between MSTP and STP &
RSTP is that MSTP can carry out the forwarding according to VLAN message and
balance VLAN load.
3.11 Synchronization feature
3.11.1 System clock function
ZXCTN 6150, the network-level clock synchronization Multi-Service Bearer platform,

supports multiple synchronous clock sources as system clock for the network clock
synchronization.
ZXCTN 6150 has the following system clock functions:

 Provide BITS external clock input and output interfaces. ZXCTN 6150 has
1*external clock input/output interface (2.048 Mbit/s).
 Support time synchronization interface and provide 1PPS+TOD signal. ZXCTN

6150 has two 1PPS+TOD input/output interface.
 Support GPS interface function and provide one GPS antenna interface to connect
GPS receiver, which can be used to provide the system clock and distribute clock
for other systems.
 Support synchronous Ethernet interface and synchronous Ethernet clock source

configuration.
 Support network clock synchronization via E1 interface and provide clock signal
compliant with ITU-T G.813.
 Clock unit supports SSM for clock synchronization to automatic select the
high-priority clock and avoids time loop.
 Support working modes trace, hold-on, locked and free-run.
 System and board clock alarm monitoring and report function.
3.11.2 Synchronous Ethernet clock
ZXCTN 6150 supports Synchronous Ethernet clock at physical layer compliance with
G.8261.
Synchronous Ethernet extracts clock from physical-layer bit stream to obtain SDH-like
clock precision for network clock synchronization. The accuracy of Synchronous
Ethernet clock is related to physical layer but is independent to Ethernet link-layer load
and packet forwarding delay.
3.11.3 IEEE 1588v2 clock
ZXCTN 6150 supports IEEE 1588v2 protocol for clock and time synchronization.

IEEE 1588v2 is a precise time synchronization protocol (PTP protocol for short). It is a
master/slave synchronization system. In system synchronization, the master equipment
periodically releases PTP protocol and time information, and the slave clock port
receives the time stamp information from master clock port. The system calculates time
delay on the cable and the time difference between master and slave, and adjusts local
time according to this difference. As a result, the slave equipment time can follow the
both frequency and phase of the master equipment time.
3.11.4 Time synchronization Ethernet function
Most vendors in the industry use IEEE 1588v2 for time synchronization. With deep
research in clock synchronization and data networks area, ZTE thinks that 1588
message may has uncontrolled jitter and asymmetry in complex data network scenarios,
which will cause some difficulties in restoring clock and time precision. Combining
several packet synchronization technologies, ZTE proposes unique "time
synchronization Ethernet" solution, which carries out 1588V2 time synchronization over
synchronization Ethernet, and insert & extract of 1588 protocol precise time stamp over
hardware so as to improve time synchronization precision.
3.11.5 1588 frequency recovery
ZXCTN 6150 supports 1588v2-based frequency recovery function and implements the
clock synchronization via frequency recovery of the 1588v2 protocol frames.
Employing this function, the clock synchronization reference can be transported through
the asynchronous switch networks to implement clock synchronization.
3.11.6 Clock protection function
ZXCTN 6150 employs SSM/BMC-based protocol to fulfill automatic protection switching

of clock link and achieve reliable transmission of synchronization.
 Calculate the optimal synchronization information path according to clock path

selection algorithm to avoid clock loop.

 Make protection switching of clock information according to clock path algorithm in

the case of network fault.
 Provide synchronous locking, hold-on and free-run of clock information.
3.11.7 Clock synchronization way for CES service
To ensure the performance of CES operations, ZXCTN 6150 supports the following CES
clock restoring mechanisms:
 Adaptive mode
 Retiming mode
3.12 Security
3.12.1 AAA ID verification
ZXCTN 6150 supports AAA (Authentication, Authorization and Accounting) mechanism

to authenticate and authorize login users in cooperation with command-line hierarchical
protection mechanism and to verify NM users in the network management. AAA-based
ZXCTN 6150 can prevent the login of illegal users.
The equipment offers different AAA functions for different user authentication policies.
According to different access authentication requirement, different access authentication
policy can be configured to provide different authentication and authorization for different
users.
AAA supports three types of user authentications:
 Local account authentication
 RADIUS (Remote Authentication Dial-In User Service) authentication
 TACACS+ (Terminal Access Controller Access Control System) authentication
AAA supports four types of authorizations:

 Direct trust authorization: Direct authorization made due to the trust in users,
without account.
 Local account authorization: Authorization made according to local user account.
 TACACS+ authorization: TACACS+ detachable authentication & authorization.

TACACS+ server authorize the users.
 Authorization after successful RADIUS authentication: RADIUS protocol

authentication & authorization are not detachable.
3.12.1.1 Command-line hierarchical protection
ZXCTN 6150 enables a user to make Telnet login via Ethernet interface. The equipment
needs to authenticate login users for the consideration of security. Only authenticated
users can log in and perform configuration & maintenance operations.
ZXCTN 6150 supports hierarchical protection for operation and maintenance command
lines. The command lines have 4 levels: visit, supervision, configuration and
administration, and the login users have the corresponding 4 levels. After logging in
ZXCTN 6000, the user can only operation the commands which are equal to lower than
the lever of the user.
ZXCTN 6150 can extend command levels and user levels (level mapping) to map 4
levels to 16 levels, so as to make fine management of user levels.
3.12.1.2 Protocol security authentication
ZXCTN 6150 has different protocol security authentication functions for SSH, PPP,
routing protocol, SNMP, etc.
 SSH protocol security authentication
 Support MD5 authentication.
 Support SHA1 authentication.
 Routing protocol security authentication

 OSPF support message authentication.
 OSPF support MD5-based authentication.
 SNMP security authentication
 Support SNMPv3 encryption and authentication.
3.12.2 Network security
3.12.2.1 VPN isolation
ZXCTN 6150 isolates interfaces with VLAN and extension technologies such as PVLAN
and QinQ to shield client network from carrier network for the security of client service
network, and to control unnecessary broadcast to increase network throughput.
IP VPN based on IP/MPLS MPLS-TP can isolate services very well with good QoS,
scalability and manageability.
3.12.2.2 Ethernet VLAN/MAC spoofing and attack against
ZXCTN 6150 filters illegal messages with "VLAN+MAC" to improve network security. The
administrator adds static table item to MAC address table and binds a specific MAC
address to an interface to prevent the attack based on MAC address spoofing.
ZXCTN 6150 can filter illegal MAC. When the maintenance staff is aware of the
possibility of the attack by the message of a MAC address, the MAC will be configured
manually to illegal MAC. When the equipment receives a message, it will compare the
source or destination MAC address of the message with the items in the MAC address. If
the MAC is illegal MAC in the table, the message will be discarded and the source will not
be notified.
In addition, ZXCTN 6150 applies ACL to port. By analyzing the information such as
VLAN, IP address, port number and protocol number, it can automatically filter illegal
messages to prevent network attack.

3.12.2.3 Other attack against features
ZXCTN 6150 also supports the following check and features to against attack:
 Source Address spoofing
 LAND
 SYN Flood (TCP SYN)
 Smurf
 Ping Flood (ICMP Echo)
 Teardrop
 Ping of Death
4 System structure
4.1 System hardware
4.1.1 Hardware architecture
ZXCTN 6150 adopts the large-capacity rack structure. Its hardware system comprises
chassis, backplane, fan plug-in box, power module, SME and LIC
ZXCTN 6150 size: 440mm (width) * 88.9mm (height) * 199mm (depth)
4.1.1.1 ZXCTN 6150 architecture
 Subrack
Structure and slot: ZXCTN 6150 horizontal-insertion subrack consists of LIC area, SME
area, power board area and fan area.

Figure 4-1 ZXCTN 6150 subrack structure
The areas have the following functions:
 Fan area: Inserted with fan and dust filter.
 Power board area: Inserted with power board.
 LIC area: Inserted with LIC.
 SME area: Inserted with SME.
 Slot allocation
ZXCTN 6150 subrack has 11 board slots: 6 for LIC, 2 for SME, 2 for power board and 1
for fan
Figure 4-2 ZXCTN 6150 subrack slot
4.1.2 Working principle of ZXCTN 6150 hardware system
ZXCTN 6150 adopts the centralized switching structure. For ordinary service flow, after
processed by physical-layer chip, packets are directly sent to the switching chip of SME
and then to the corresponding board ports via the switching network. For some special
service messages, e.g. 1588 PTP message or OAM message, before sent to the
switching network, packets are pre-processed by the boards and then sent to the
switching chip of SME for termination or forwarding.

ZXCTN 6150 hardware system comprises SME, service boards, power, fan and
backplane. It adopts the centralized structure. The core is 1+1 SME which have main
control, switching and clock functions and communicate with other components via
backplane. ZXCTN 6150 working principle is shown:
 Data channel
There is data channel between service board and active/standby SME via bidirectional
serdes bus.
 Control channel
Active SME provides service board with management control channel connected to
standby SME. Control information connection diagnoses service board, power and fan,
controls information access and monitors alarms, e.g., access PHY-layer status, control
port indicator, and monitor the signals of board type, board in-position, resetting,
disconnection and fan abnormality.
 Clock control
Clock control channel transfers the following clock information:
Line restoration clock reference and 1588 clock information sent from service board to
SME.
2M BITS clock, GPS PPS (Pulse per Second) and TOD signals received by SME.
System clock delivered by SME.

4.2 System boards
4.2.1 ZXCTN 6150 boards
4.2.1.1 Overview
ZXCTN 6150 have processing boards (including protection board), SME, fan control
board and power control board. ZXCTN 6150 board type and function are shown inTable
4-1.
Table 4-1 ZXCTN 6150 board type and functio
Type Board Function

XGEx2(O), XGEx1(O),
Access and process
GEx8(O), GEC(OE)x4,
10GE, GE, FE,
GECHx4(OE), FEx8(E),
LIC Channelized STM-1,
FEx8(OE), STM-1x4(O),
CEP STM-1, and E1
E1x16-75, E1x16-120,
signals.
GPCB
Switch client-side and

system-side services.
Provide standard system
Switching control & clock
SME clock or time for the
board
system.
Provide the interface
between system and NM.
Access external power

and prevent the
Power control board PW2D
interference caused by
abnormal power.
Dissipate the heat for the

Fan control board FC2A
equipment.
4.2.1.2 Processing boards
1. XGEx2(O)

This section introduces XGEx2(O) function, panel, slot, etc.
i. Function and feature
XGEx2(O) is 2-Port 10 Gigabit Ethernet Optical interface Board which has 2*10GE
SFP+ optical interface. It supports the following function:
Table 4-2 XGEx2(O) board function
Function and
Description
feature
Support Ethernet port shutdown and disabling.

Configure port to full-duplex mode.
Support port creation and deletion. Default port mode is LAN
mode.
Basic function Support port type query and port mode query & modification.
Configure port MTU, port flow control, message transceiving
statistics, port loopback mode, port status, optical interface type
query, etc.
Obtain the parameters of 10G optical module.
Support QoS and provide export scheduling, bandwidth limitation

QoS
and relative statistics information.
LAG Support
Support internal and external loopback of Ethernet port PHY layer.

Loopback Support internal loopback of Ethernet port MAC layer.
Support automatic de-loopback of the port.
Support synchronization Ethernet and extraction of port

physical-layer clock whose quality meets the requirements of
Packet clock clock source.
Transmit and receive SSM of synchronization Ethernet port.
Support IEEE 1588 v2 clock.
ii. Panel

Figure 4-3 XGEx2(O) panel
XGEx2(O) has pluggable SFP+ optical interface supporting several

transmission distances.
XGEx2 has 6indicators on the panel. 2 port indicators below each optical
interface indicate port link and data transmission. RUN and ALM indicate
board operation.
2. XGEx1(O)
This section introduces XGEx1(O)function, panel, slot, etc.
XGEx1(O) is 1-Port 10 Gigabit Ethernet Optical interface Board which has 1*10GE
SFP+ optical interface. It supports the following function:
Table 4-3 XGEx1 board function
Function and
Description
feature
Support Ethernet port shutdown and disabling.

Configure port to full-duplex mode.
Support port creation and deletion. Default port mode is LAN
mode.
Basic function Support port type query and port mode query & modification.
Configure port MTU, port flow control, message transceiving
statistics, port loopback mode, port status, optical interface type
query, etc.
Obtain the parameters of 10G optical module.

QoS
LAG Support

Function and
Description
feature
Support internal and external loopback of Ethernet port PHY layer.

Loopback Support internal loopback of Ethernet port MAC layer.

ii. Panel
Figure 4-4 XGEx1(O) panel
XGEx1(O) has pluggable SFP+ optical interface supporting several

XGEx1(O) has 4 indicators on the panel. 2 port indicators below the optical
interface indicate port link and data transmission. RUN and ALM indicate
board operation.
3. GEx8(O)
This section introduces GEx8(O) (8-Port Gigabit Ethernet Optical Interfaces Board)
function and feature, principle, panel, slot, etc.
GEx8(O) is the Gigabit Ethernet board which has 8-port Gigabit SFP optical
interface. It supports the following function:

Table 4-4 GEx8(O) board function
Function and
Description
feature
Support QoS and provide export scheduling, bandwidth

QoS
limitation and relative statistics information.
Intra/inter-LAG Support
Support internal and external loopback of Ethernet port PHY

layer.
Loopback
Support internal loopback of Ethernet port MAC layer.

ii. Panel
Figure 4-5 GEx8(O) panel
GEx8(O) has 8-port pluggable Gigabit SFP optical interface supporting several
GEx8(O) has 18 indicators on the panel. 16 indicators of port 1-8 indicate port
link and data transceiving. RUN and ALM indicate board operation.
4. GECHx4(O)
This section introduces GECHx4(O) (High Performance Gigabit Ethernet Combo

interface Board) function, panel, slot, etc.
GECHx4(O) is the enhanced Combo board which has 4 Gigabit SFP optical
interfaces and 4 Gigabit Ethernet electrical interfaces. Optical interface and

electrical interface of the same number cannot be used at the same time. For
example, when No.1 electrical interface is used, No.1 SFP optical interface will
be disabled. It supports the following function:
Table 4-5 GECHx4(O) board function
Function and
Description
feature

QoS

layer.
Loopback

Optical interface supports the following functions:
a) Configuration of interface rate
b) Digital diagnosis of optical interface
c) ALS of optical interface
d) Synchronization Ethernet
Electrical interface supports the following functions:
a) Full-duplex/half-duplex working mode
b) 10/100/1000M automatic negotiation
c) Forced mode
d) Automatic cross in the task mode

e) a) Cable test
f) Synchronization Ethernet
ii. Panel
Figure 4-6 GECHx4(O) panel
GECHx4(O) has pluggable SFP optical module supporting several Gigabit

Ethernet transmission distances, and 4-port RJ45 electrical interface
supporting several Gigabit Ethernet transmission distances.
GECHx4(O) has 18 indicators on the panel. 16 indicators are above 4

electrical interfaces and 4 optical interfaces. RUN and ALM indicate board
operation.
5. GECx4(O)
This section introduces GECx4 V2(Enhanced Gigabit Ethernet Combo interface Board)
function, panel, slot, etc.
iii. Function and feature
GECx4(O) is the Combo board which has 4 Gigabit SFP optical interfaces
and 4 Gigabit Ethernet electrical interfaces. The difference between
GECHx4(O) and GECx4(O) is that GECx4(O) adopts the new generation
chips. Optical interface and electrical interface of the same number cannot be
used at the same time. For example, when No.1 electrical interface is used,
No.1 SFP optical interface will be disabled. It supports the following function:
Table 4-6 GECx4 V2 board function
Function and
Description
feature

Function and
Description
feature

QoS

layer.
Loopback

c) Forced mode
e) b) Cable test
iv. Panel

Figure 4-7 GECx4(O) panel
GECx4(O) has pluggable SFP optical module supporting several Gigabit

supporting several Gigabit Ethernet transmission distances.
GECx4(O) has 18 indicators on the panel. 16 indicators are above 4 electrical

interfaces and 4 optical interfaces. RUN and ALM indicate board operation.
6. FEx8(E)
This section introduces FEx8(E) (8-Port Fast Ethernet Electrical Interface Board) function
and feature, principle, panel, slot, etc.
FEx8(E) is the 8 Port Fast Ethernet Electrical Interface Board which has 8
RJ45 electrical interfaces. It supports the following function:
Table 4-7 FEx8(E) board function
Function and
Description
feature
Support QoS and provide export scheduling, bandwidth

QoS
limitation and relative statistics information.

layer.
Loopback


ii. Panel
Figure 4-8 FEx8(E) panel
FEx8(E) has 8-port RJ45 electrical interface supporting several transmission

distances.
FEx8(E) has 18 indicators on the panel. 16 indicators of port 1-8 indicate port link and
data transceiving. RUN and ALM indicate board operation.
7. FEx8(OE)
This section introduces FEx8(OE) (Fast Ethernet Optical & Electrical Interface Board)
function, panel, slot, etc.
FEx8(OE) is the enhanced Combo board which has 4 Fast Ethernet SFP
optical interfaces and 4 RJ45 electrical interfaces. It supports the following
function:
Table 4-8 FEx8(OE) board function
Function and
Description
feature

QoS

layer.
Loopback

Function and
Description
feature

c) Forced mode
e) c) Cable test
ii. Panel
Figure 4-9 FEx8(OE) panel

FEx8(OE) has pluggable SFP optical module supporting several Fast

supporting several Fast Ethernet transmission distances.
FEx8(OE) has 18 indicators on the panel. 16 indicators are above 4 electrical interfaces
and 4 optical interfaces. RUN and ALM indicate board operation.
8. STM-1x4(O)
STM-1x4(O) processes channelized or CEP STM-1 service simultaneously via STM-1

ports. Each port has 155M bandwidth and can be configured to support CEP or CES
function.
i. When the port is configured as channelized STM-1, STM-1x4 board maps E1

data into VC12 to support E1 CES and support the following functions
a) One CES is related to one PW.
b) CES supports timeslot compression. The user selects any two or more
among 1 ~ 31 timeslots of channelized E1 to transmit services.
c) Support CESoPSN and SAToP encapsulations.
d) Support external clock and adaptive clock.
e) PSN jitter tolerance of CES is 0.375ms ~ 16ms.
f) 1~5ms CES delay can be configured at the granule of 125us.
Other features are:
a) Support clock extraction of any two ports (configurable) and SSM.
b) Support pluggable optical interface.
c) Support LMSP 1+1 and 1:1 protection. Switching time is smaller than
50ms. When inter-board LMSP protection is configured, optical interface
numbers should be consistent.

d) If T3 enables ALS, when a board is unavailable, its external optical

interface will be automatically shut down.
e) Support S1 byte extraction and insertion.
f) Support internal and external loopback of services.
g) Support configuration of port rate.
h) Support port digital diagnosis.
i) Support port ALS.
j) Support SDH functions, including standard SDH frame structure, SDH

frame delimitation, clock restoration, section overhead processing, alarm
and performance statistics.
k) Support telecom OAM (LM and ETH-DM) and MPLS-TP OAM.
l) Support PWE3 service encapsulation & bearing.
ii. When the port is configured as CEP STM-1, STM-1x4 board maps VC4 data to
PW to support CEP and the following functions
a) One VC4 is emulated to one PW.
b) The default payload length is 783 bytes (TUG0-3), the length can be
configured between 783 bytes and 9170 bytes.
c) Support external clock, differential clock and adaptive clock.
Other features are:
a) Support clock extraction of any two ports (configurable) and SSM.
b) Support pluggable optical interface.
c) Support LMSP 1+1 and 1:1 protection. Switching time is smaller than
50ms. When inter-board LMSP protection is configured, optical interface
numbers should be consistent.

d) Support S1 byte extraction and insertion.
e) Support internal and external loopback of services.
f) Support configuration of port rate.
g) Support port digital diagnosis.
h) Support port ALS.
i) Support SDH functions, including standard SDH frame structure, SDH

frame delimitation, clock restoration, section overhead processing, alarm
and performance statistics.
j) Support PWE3 service encapsulation & bearing.
iii. Panel
9. Figure 4-10 STM-1x4(O) panel
STM-1port has pluggable SFP optical module supporting several transmission

distances. STM-1x4 has 10 indicators on the panel. 8 indicators are above 4
STM-1 optical interfaces. RUN and ALM indicate board operation.
10. E1x16-75
E1x16-75, the E1 circuit emulation board, has 16 *E1 75 ohm interfaces and supports
TDM E1 function. TDM E1 supports structured or unstructured circuit emulation.
E1x16-75 processes 16 channels of multi-protocol packets such as CES

services. The pluggable board may be configured with clock extraction of any
two E1 ports.

a) Each E1 interface can be configured to TDM E1
b) Support E1 interface framing and framing detection.
c) Set independent distance attribute to each E1 port.
d) Support alarm and performance report by E1 interface.
e) Support TDM E1 service restoration in adaptive clock restoration mode or

retiming mode.
f) Support structured and unstructured TDM E1 services in the case of E1

CES. Structured service supports E1 framing and timeslot compression.
g) Support PWE3 encapsulation and de-encapsulation of TDM services.
h) Support adaptive clock restoration and CES output clock drift control.
E1x16-75 accesses at most 16 *E1 via interface board to support CES with
features as below.
a) Each board supports at most 16*E1 CES and one CES is related to one
PW.
ii. Panel

Figure 4-11 E1x16-75 panel
E1x16-75 has 1 circuit emulation jacks and supports 16*E1 interfaces.

E1x16-75 has 2 indicators: RUN and ALM indicate board operation.
11. E1x16-120
E1x16-120, the E1 circuit emulation board, has 16 *E1 120 ohm interfaces and supports
TDM E1 function. TDM E1 supports structured or unstructured circuit emulation.
E1x16-120 processes 16 channels of multi-protocol packets such as CES

services. The pluggable board may be configured with clock extraction of any
two E1 ports.
a) Each E1 interface can be configured to TDM E1.
b) Support E1 interface framing and framing detection.
c) Set independent distance attribute to each E1 port.
d) Support alarm and performance report by E1 interface.
e) Support TDM E1 service restoration in adaptive clock restoration mode or

retiming mode.
f) Support structured and unstructured TDM E1 services in the case of E1

CES. Structured service supports E1 framing and timeslot compression.
g) Support PWE3 encapsulation and de-encapsulation of TDM services.
h) Support adaptive clock restoration and CES output clock drift control.
E1x16-120 accesses at most 16 *E1 via interface board to support CES with
features as below.

Features for CES:
a) Each board supports at most 16*E1 CES and one CES is related to one
PW.
ii. Panel
Figure 4-12 E1x16-120 panel
E1x16-120 has 1 circuit emulation jacks and supports 16*E1 interfaces. E1x16-120 V2
has 2 indicators: RUN and ALM indicate board operation
12. GPCB
GPCB, the GPCB (GPS PTP Clock) board, has 1 port GPS antenna interface, 1 port 2M
output interface and 1 port 2M input interface.
a) Provide 1 port GPS antenna interface which can be directly connected to

GPS antenna feed cable to achieve frequency synchronization and time
synchronization.
b) Provide 1 port 2M output, compliant to SSU requirements.
c) Provide 1 port 2M input, compliant to SSU requirements.

iii. Panel
Figure 4-13 GPCB panel
GPCB has 6 indicators: MOD, Rx, LA, SP, ALM & RUM indicate board operation
4.2.1.3 SME
The ZXCTN 6150 SME, consists of control unit, switching unit and clock synchronization
unit. The system core board adopts 1+1 backup. SME units carry out such functions as
system control, routing, NM protocol, forwarding table maintenance, service data
forwarding and clock synchronization. SME in 1+1 redundant configuration can make
active/standby switching.
1. Panel
Figure 4-14 SME panel
SME has 5 RJ45 functional interfaces, e.g., BTS/GPS, GPS, ALM (external alarm
input/output), LCT (local management interface) and Qx (NM interface),.
SME has 6 indicators, e.g., RUN, ALM, MST, CLK,GPS1 & GPS2.
SME has 2 buttons, e.g. RST and B OFF
4.2.1.4 Power boards
1. DC power Supply
The panel of ZXCTN 6150 DC power supply board is shown as follows:

Figure 4-15 ZXCTN 6150 DC power module
4.2.1.5 Fan board
1. Brief introduction
ZXCTN 6150 has several fans drawing cool air from right intake vent to left outtake vent.
The cool air dissipates the heat from boards which employ aluminum heat-sink parts.
The air filter at the vent can be taken down for maintenance and cleanness.
2. ZXCTN 6150 FAN
ZXCTN 6150 FAN panel is shown in the following figure
Figure 4-16 ZXCTN 6150 FAN panel
ZXCTN 6150 FAN panel has 2 indicators. “RUN” indicates the fan operation status and
“ALM” indicates the fan fault. FAN has control circuit controlling fan speed. SME monitors
the temperature of the whole system and controls fan speed with FAN control circuit.

4.3 Software architecture
ZXCTN 6150 system software structure comprises three planes which are management
plane, control plane and data plane. Board software runs on various planes based on
functions, and implements management and control of boards, NEs and the whole
network.
ZXCTN 6150 software is designed with a hierarchical architecture. Each layer performs
specific functions and serves its upper layer.
4.3.1 EMS software
The EMS software NetNumen U31 is used to manage and monitor ZXCTN 6150 NEs. It
provides the functions of configuration management, fault management, performance
management, maintenance management, end-to-end circuit management, security
management, system management and report management. The following figure
illustrates the architecture of NetNumen U31 EMS software.
Figure 4-17 EMS software architecture
 Manager
Also called "Server", Manager acts as the service of GUI. It exchanges information
with Agent via Qx interface. Manager provides the following fucntions:

 Receive requests from GUI, analyze the requests and forward related
information to Agent or just send the information to Database.
 Receive processed information from the Database, analyze the

information and forward it to GUI
 Receive information from Agent, analyze the information and then forward
it to Database or GUI.
 GUI
Also called "Client", GUI has following functions:
 Provide graphic user interface for users.
 Provide service interface for configuration management, fault

management, performance management, security management,
maintenance management, system management and online help.
 Support user security control.
 Database
Database is mainly responsible for the query of information of interface and

management functional modules, saving configuration and alarm information, and
processing of data consistency.
4.3.2 Communication protocols and interfaces
Interfaces in the software system of ZXCTN 6150 and corresponding communication

protocols used by them are introduced in the following table.
Table 4-9 ZXCTN 6150 software system interface description
Name Description

Name Description
Qx interface is the interface between Agent and Manager,

that is, the interface between the NE control processor
board and the computer where the EMS server is running.
Qx interface
As to ZXCTN 6150, it is located on the system interface
board. It complies with TCP/IP, ITU-T Q.811 and ITU-T
Q.812.
4.3.3 Brief introduction to ZXROS platform
ZXCTN 6150 leverages on ZXROS (Router Operation System) platform to offer varieties
service functions and performances required by metro Ethernet switch. Its software
architecture is shown in following figure.
Figure 4-18 Software architecture
Diagnosis and
Alarm log VPWS VPLS ACL QOS
debugging
Monitoring and
S NMP PBB - TE MPLS - TP Routing tunnel IP VPN
maintenance
Equipment Cluster
Remote logon IPTV ETHoTDM TDMoE
management management
File L2L3
Command line VLAN MAC ZESR
management multicast
System
System service
management Business & service
Operation system support platform
Hardware & drive
Function of each component is described as below:
 Hardware & drive: provide software drive for main control board, line card,
backplane, fan and power supply;
 Operation system support platform: provide real-time operation system. It is the

core of ZXCTN 6000 software architecture. The downwards is responsible for
managing the hardware architecture of the whole routing switch and upwards
provides a unified running platform for the applications of the software system. The

features include high reliability, real-time, self-healing ability, maintainability and

encapsulation;
 System management: provide file management, equipment management (power

supply fan module), monitoring & maintenance and diagnosis & debugging,
ensuring the equipment in reliable operation state;
 System service: provide command line CLI, remote logon (telnet and ssh), SNMP
(Simple Network Management Protocol) and alarm log; diversified system service
offerings ease equipment operation and maintenance;
 Business and service: provide varieties of Ethernet-based business and services,

which include VLAN, MAC, ZESR, L2/L3 multicast, cluster management, L3 routing
and tunnel, IPTV, TDMoE, MPLS-TP, L2 VPN (VPWS&VPLS), L3 VPN (IP VPN),
ACL and QOS data services.
ZXROS is a multi-task and fully distributed real-time network operation system. It

provides unified IP protocol support to all ZTE equipments. With mature and stable
architecture, ZXROS has been widely deployed by various operators in recent years.
Current ZXROS platform is enhancement and extension to original platform. It bases on
customers’ service demands, whilst considering the requirements more on user
operation & maintenance cost, service scalability and application, as listed below:
 Good encapsulation
 Support multiple operation systems, and smooth upgrade of these

operation systems.
 All product configurations are in consistent style, easing operation &

maintenance for users.
 Strong monitoring function
 Monitor exceptions of proceeding, memory.
 Monitor power supply operating/exceptions, fan rpm/failure, voltage,

current and environment temperature.

 Provide fast fault localization; fully ensure the high stability of product
version.
 Agile modular assembly mode
 All ZXROS-based software functions are easy to scale or remove, and

help speed development of new functions based on original architecture.
 Enable flexible customization on users demand and quick response to

customers’ requirements.
 Extension of new carrier Ethernet services based on unified platform.
 Support MPLS-TP, flexibly implement various connection modes like

E-LINE, E-LAN, E-TREE, and enable safe and agile deployment of
multi-branch network.
 Support L2/L3 VPN and H-VPLS to address the requirement for

hierarchical deployment of services. Support multicast function within
VPN, implement fast deployment of VPN via unified NM, and enable rapid
delivery of multicast services such as user video, IPTV.
 Support IEEE 1588 v2 and synchronous Ethernet clock modes, handling

the stringent requirements of mobile network for service latency and jitter.
 Good interoperability, comply with protocols and standards listed below:
1. L2 protocol and standard:

L2 protocol and standard
IEEE 802.1d Bridging IEEE802.1x Port Based Network Access
EEE 802.1s Multiple Spanning Tree IEEE 802.3ad Link Aggregation
IEEE 802.1w Rapid Spanning Tree IEEE 802.3ag Service Layer OAM
IEEE 802.1Q VLAN tagging IEEE 802.3ah Provider Backbone B
9216 bytes jumbo frame forward on IEEE 802.1ab LLDP(Link Layer Discovery
Ethernet and pos interface Protocol)
IEEE 802.1ad VLAN stacking, Select

IGMP v1/v2 snooping/proxy
QinQ, VLAN translate

L2 protocol and standard
IEEE 802.3 10BaseT IEEE 802.3ae 10Gpbs Ethernet
IEEE802.3ah Ethernet OAM IEEE 802.3x Flow Control
IEEE 802.3 100BaseT IEEE 802.3z 1000BaseSX/LX
IEEE 802.3u 100BaseTx IEEE 802.3ae 10Gbps Ethernet
IEEE 802.1p VLAN Priority
2. TCP/IP protocol and standard:

TCP protocol and standard
RFC 768 UDP RFC 791 IP
RFC 792 ICMP RFC 793 TCP
RFC 826 ARP RFC 854 Telnet
RFC 951 BootP RFC 1350 TFTP
RFC 1812 Requirements for IPv4

RFC 1519 CIDR
Routers
RFC 2328 TFTP Blocksize Option RFC 2347 TFTP option Extension
RFC2349TFTPTimeoutIntervaland RFC 2401 Security Architecture for

TransferSize option Internet Protocol
draft-ietf-bfd-mib-00.txt Bidirectional
draft-ietf-bfd-base-02.txt Bidirectional
Forwarding Detection Management
Forwarding Detection
Information Base
draft-ietf-bfd-v4v6-1hop-02.txt BFD IPv4

and IPv6(Single Hop)
3. RIP protocol and standard:

RIP protocol and standard
RFC 1058 RIP Version1 RFC 2453 RIP Version2
RFC 2082 RIP-2 MD5 Authentication
4. OSPF protocol and standard:

OSPF protocol and standard
RFC 1765 OSPF Database Overflow RFC 2328 OSPF Version 2
RFC 2370 Opaque LSA Support RFC 2740 OSPF for IPv6(OSPFv3)
RFC 3137 OSPF Stub Router

RFC 3101 OSPF NSSA Option
Advertisement

OSPF protocol and standard
RFC 3623 Graceful OSPF Restart-GR

helper
5. BGP protocol and standard:

BGP protocol and standard
RFC 1397 BGP Default Route RFC 1772 Application of BGP in the
Advertisement Internet
RFC 1965 Confederations for BGP RFC 1997 BGP Attribute Communities
RFC 2385 Protection of BGP Sessions

RFC 2439 BGP Route-Flap Dampening
via MD5
RFC 2547bis BGP/MPLS VPNs RFC 2796 BGP Route Reflection
draft-ietf-idr-rfc2796bis-02.txt draft-ietf-idr-rfc2858bis-09.txt
RFC 2918 Route Refresh Capability for

RFC 3065 Confederations for BGP
BGP4
RFC 3392 Capabilities Advertisement

draft-ietf-idr-rfc3065bis-05.txt
with BGP4
RFC 4360 BGP Extended Communities

RFC 4271 BGP-4 (previously RFC 1771)
Attribute
RFC 4364 BGP/MPLS IP Virtual Private

RFC 2547bis BGP/MPLS VPNs
Networks (VPNs)
RFC 4724 Graceful Restart Mechanism RFC 4760 Multi-protocol Extensions for
for BGP-GR helper BGP
RFC 4203 for Shared Risk Link Group

(SRLG) sub-TLV
6. ISIS standard:
ISIS standard
RFC 1142 OSI IS-IS Intra-domain Routing RFC 1195 Use of OSI IS-IS for
Protocol (ISO 10589) routing in TCP/IP & dual environments
RFC 2763 Dynamic Hostname Exchange

RFC 2973 IS-IS Mesh Groups
for IS-IS
RFC 3373 Three-Way Handshake for

RFC 2966 Domain-wide Prefix
Intermediate System to Inter-mediate
Distribution with Two-Level IS-IS
System (IS-IS) Point-to-Point Adjacencies

ISIS standard
RFC 3567 Intermediate System to

Cryptographic Authentication
Intermediate System(IS-IS)
RFC 3719 recommendations for RFC 3784 Intermediate System to

Interoperable Networks using IS-IS Intermediate
System(IS-IS) Extensions for Traffic RFC 3787 Recommendations for

Engineering (TE) Interoperable IP Networks
RFC 3847 Restart Signaling for IS-IS-GR RFC 4205 for Shared Risk Link Group
helper (SRLG) TLV
draft-ietf-isis-igp-p2p-over-lan-05.txt
7. VRRP standard:
VRRP standard
RFC 2787 Definitions of Managed

RFC 3768 Virtual Router Redundancy
Objects for the Virtual Router
Protocol
Redundancy Protocol
8. LDP standard:
LDP standard
RFC 3036 LDP Specification draft-jork-ldp-igp-sync-03
RFC 3478 Graceful Restart Mechanism for

RFC 3037 LDP Applicability
LDP-GR helper
9. IPV6 standard
IPV6 standard
RFC 2375 IPv6 Multicast Address

RFC 1981 Path MTU Discovery for IPv6
Assignments
RFC 2460 Internet Protocol Version

RFC 2461 Neighbor Discovery for IPv6
6(IPv6) Specification
RFC 2463 Internet Control Message

RFC 2462 IPv6 Stateless Address Auto
Protocol(ICMPv6) for the Internet Protocol
configuration
Version 6 Specification
RFC 2464 Transmission of IPv6 Packets RFC 2529 Transmission of IPv6 over IPv4
over Ethernet Networks Domains without Explicit Tunnels
RFC 2545 Use of BGP-4 Multi-protocol RFC 2710 Multicast Listener Discovery
Extension for IPv6 Inter-Domain Routing (MLD) for IPv6

IPV6 standard
RFC 3306 Unicast-Prefix-based IPv6

RFC 2740 OSPF for IPv6
Multicast Addresses
RFC 3587 IPv6 Global Unicast Address

RFC 3315 Dynamic Host Configuration
Format
Protocol for IPv6
RFC 3590 Source Address Selection for

RFC 3810 Multicast Listener Discovery
the Multicast Listener Discovery (MLD)
Version 2 (MLDv2) for IPv6
Protocol
RFC 4007 IPv6 Scoped Address RFC 4193 Unique Local IPv6 Unicast
Architecture Addresses
RFC 4659 BGP-MPLS IP Virtual Private

RFC 4291 IPv6 Addressing Architecture
Network(VPN) Extension for IPv6 VPN
RFC 5072 IP Version 6 over PPP
10. Multicast standard:

Multicast standard
RFC 1112 Host Extensions for IP RFC 2236 Internet Group Man-agement
Multicasting(Snooping) Protocol
RFC 2362 Protocol Independent RFC 3376Internet Group Management

Multicast-Sparse Mode(PIM-SM) Protocol Version3
RFC 3446 Anycast Rendezvous

Point(RP) mechanism using Protocol
RFC 3618 Multicast Source Discovery
Independent Multicast(PIM) and
Protocol (MSDP)
Multicast Source Discovery
Protocol(MSDP)
RFC 4601 Protocol Independent RFC 4604 Using IGMPv3 and MLDv2 for
Multicast-Sparse Mode(PIM-SM) Source-Specific Multicast
RFC 4607 Source-Specific Multicast for RFC 4608 Source-Specific Protocol

IP Independent Multicast in 232/8
RFC 4610 Anycast-RP Using Protocol

draft-ietf-pim-sm-bsr-06.txt
Independent Multicast(PIM)
draft-rosen-vpn-mcast-08.txt draft-ietf-mboned-msdp-mib-01.txt
11. MPLS standard:

MPLS standard

MPLS standard
RFC 3031 MPLS Architecture RFC 3032 MPLS Label Stack
RFC 4182 Removing a Restriction on the RFC 4379 Detecting Multi-Protocol Label
use of MPLS Explicit NULL Switched (MPLS) Data Plane Failures
12. RSVP-TE standard:

RSVP-TE standard
RFC 2430 A Provider Architecture RFC 3209 Extensions to RSVP for

DiffServ & TE Tunnels
RFC 2747 RSVP Cryptographic RFC 3097 RSVP Cryptographic

Authentication Authentication
RFC 2702 Requirements for Traffic RFC 4090 Fast reroute Extensions to
Engineering over MPLS RSVP-TE for LSP Tunnels
13. Differentiated Services standard:
Differentiated Services standard

RFC 2474 Definition of the DS Field the
RFC 2598 An Expedited Forwarding PHB
IPv4 and IPv6 Headers(Rev)
RFC 2597 Assured Forwarding PHB RFC 3140 Per-Hop Behavior

Group (rev3260) Identification Codes
14. PPP standard:

PPP standard
RFC 1332 PPP IPCP RFC 1377 PPP OSINLCP
RFC 1662 PPP in HDLC-like Framing RFC 1638/2878 PPP BCP
RFC 1661 PPP RFC 1989 PPP Link Quality Monitoring
RFC 1990 The PPP Multilink RFC 2516 A Method for Transmitting
Protocol(MP) PPP Over Ethernet
RFC 2615 PPP over SONET/SDH
15. ATM standard:

ATM standard
RFC 2514 Definitions of Textual

RFC 2515 Definition of Managed
Conventions and OBJECT_IDENTI-TIES
Objects for ATM Management
for ATM Management

ATM standard
ITU-T Recommendation I.610-B-ISDN ITU-T Recommendation I.432.1-BISDN

Operation and Maintenance Principles and user-network interface-Physical layer
Functions version 11/95 specification: General characteristics
GR-1248-CORE-Generic Requirements for

AF-TM-0121.000 Traffic Management
Operations of ATM Network
Specification Version 4.1
Elements(NEs),Issue 3
RFC 1626 Default IP MTU for use over RFC2684 Multi-Protocol Encapsulation
ATM AAL5 over ATM Adaptation Layer 5
GR-1113-CORE-Asynchronous Transfer
Mode (ATM) and ATM Adaptation AF-ILMI-0065.000 Integrated Local
Layer(AAL) Protocols Generic Management Interface(ILMI) Version4.0
equirements,IssuE1
AF-TM-0150.00 Addendum to Traffic

Management v4.1 optional minimum
desired cell rate indication for UBR
16. DHCP standard:

DHCP standard
RFC 2131 DynamicHost-Configuration RFC 3046DHCP Relay Agent

Protocol(REV) Information Option(Option 82)
17. VPLS standard:

VPLS standard
RFC 4762 Virtual Private LAN Services

Using LDP(previously draft-ietf-l2vpn-vpls-mcast-reqts-04.txt
draft-ietf-l2vpn-vpls-ldp-08.txt)
18. PW standard:
PW standard
RFC 4385 Pseudo Wire Emulation

Edge-to-Edge(PWE3) Control Word for
Edge-to-Edge(PWE3)
Use over an MPLS PSN
RFC 3916 Requirements for PWE3 RFC 4446 IANA Allocations for PWE3

PW standard

Edge-to-Edge(PWE3) Control Word for
Edge-to-Edge(PWE3)
Use over an MPLS PSN
RFC 4448 Encapsulation Methods for

RFC 4447 Pseudowire Setup and
Transport of Ethernet over MPLS
Maintenance Using
Networks(draft-ietf-pwe3-ethernet-enca
LDP(draft-ietf-pwe3-control-protocol-17.txt)
p-11.txt)
RFC 4619 Encapsulation Methods for RFC 4717 Encapsulation Methods for
Transport of Frame Relay over MPLS Transport ATM over MPLS Networks
Networks(draft-ietf-pwe3-frame-relay-07.txt) (draft-ietf-pwe3-atm-encap-10.txt)
RFC 4816 PWE3 ATM Transparent Cell RFC 5085,Pseudowire Virtual Circuit
Transport Connectivity Verification (VCCV):A
Service(draft-ietf-pwe3-cell-transport-04.txt) Control Channel for Pseudowires
draft-ietf-l2vpn-vpws-iw-oam-02.txt draft-ietf-pwe3-oam-msg-map-05-txt
draft-ietf-l2vpn-arp-mediation-04.txt draft-ietf-pwe3-ms-pw-arch-02.txt
draft-hart-pwe3-segmented-pw-vccv-0
draft-ietf-pwe3-segme nted-pw-05.txt
2.txt
draft-muley-dutta-pwe3-redundancy-bit-02.t
draft-muley-pwe3-redundancy-02.txt
xt
MFA Forum 9.0.0 The Use of Virtual trunks MFA Forum 12.0.0 Multiservice
for ATM/MPLS Control Plane Interworking Interworking-Ethernet over MPLS
MFA Forum 13.0.0-Fault Management for MFA Forum 16.0.0-Multiservice

Multiservice Interworking v1.0 Interworking-IP over MPLS
19. NM standard:
NM standard
ITU-T M.3010, PrincIPles for a

ITU-T M.3000, Overview of TMN
Telecommunications management
recommendations
network
ITU-T M.3020, TMN Interface

ITU-T M.3016, TMN security overview
Specification Methodology
ITU-T M.3101, Managed Object

ITU-T M.3100 Generic Network
Conformance Statements for the Generic
Information Model
Network Information Model

NM standard
ITU-T M.3200, TMN management

ITU-T M.3300, TMN F interface
services and telecommunications
requirements
managed areas: overview
ITU-T Temporary Document 69 (IP

ITU-T M.3400, TMN Management
Experts): Revised draft document on IP
Function
access network architecture
ITU-T X.701-X.709, Systems ITU-T X.710-X.719, Management

Management framework and architecture Communication Service and Protocol
ITU-T X.720-X.729, Structure of ITU-T X.730-X.799, Management

Management Information functions
RFC1213, Management Information

RFC1157, Simple Network Management
Base for Network Management of TCP/IP
Protocol
based internets: MIB-II
RFC1902, Structure of Management

RFC1901, Introduction to Information for Version 2 of the Simple
Community-based SNMPv2 Network Management Protocol
(SNMPv2)
RFC1903, Textual Conventions for RFC1905, Protocol Operations for

Version 2 of the Simple Network Version 2 of the Simple Network
Management Protocol (SNMPv2) Management Protocol (SNMPv2)
RFC2233, The Interface Group MIB

RFC2037, Entity MIB using SMIv2
using SMIv2
RFC1558, A String Representation of RFC1558, A String Representation of

LDAP Search Filters LDAP Search Filters
RFC1777, Lightweight Directory Access RFC1778, The String Representation of

Protocol Standard Attribute Syntaxes
RFC2251, Lightweight Directory Access

RFC1959, An LDAP URL Format
Protocol (v3)
RFC1493, Definitions of Managed GB901, A Service management Business

Objects for Bridges Process Model
GB909,Generic Requirements for

GB910,Telecom Operations Map Telecommunications Management
Building Blocks
RFC1757, Remote Network Monitoring GB908,Network Management Detailed

Management Information Base Operations Map

NM standard
RFC1757, Remote Network Monitoring

GB914,System Integration Map
Management Information Base
GB917, SLA Management Handbook NMF038, Bandwidth Management

V1.5 Ensemble V1.0
TMF508, Connection and Service TMF801, Plug and Play Service

Management Information Model Business Fulfillment Phase 2 Validation
Agreement Specification V1.0
TMF605, Connection and Service NMF037, Sub-System Alarm

Management Information Model Surveillance Ensemble V1.0
TMF053, NGOSS Architecture TMF053A, NGOSS Architecture

Technology Neutral Specification V1.5 Technology Neutral Specification V1.5
TMF053B, NGOSS Architecture TMF821, IP VPN Management Interface

Technology Neutral Specification V1.5 Implementation Specification V1.5
TMF816, B2B Managed Service for DSL

Interworking Between CORBA and TMN
Interface Implementation Specification
System Specification V1.0
V1.5
YD/T 852-1996 TMN General Design YD/T 871-1996 TMN Generic Information
Principle model
YD/T XXXX-2001 General Technical YD/T XXXX-2001 IP Network Technical

Requirements of Broadband Metro Requirements - Network Performance
Network Indexes and Availability
YD/T XXXX-2000 IP Network Technical YDN 075-1998 China Public Multimedia

Requirements - General Network Telecommunication Network
Structure Management Specifications
YDN 075-1998 China Public Multimedia

RFC 1215 A Convention for Defining
Telecommunication Network
Traps for use with the SNMP
Management Specifications
RFC 1657 BGP4-MIB RFC 1724 RIPv2-MIB
RFC 1850 OSPF-MIB RFC 1907 SNMPv2-MIB
RFC 2096 IP-FORWARD-MIB RFC 2011 IP-MIB
RFC 2012 TCP-MIB RFC 2013 UDP-MIB
RFC 2138 RADIUS RFC 2206 RSVP-MIB
RFC 2452 IPv6 Management Information

RFC 2454 IPv6 Management Information
Base for the Transmission Control
Base for the User Datagram Protocol
Protocol

NM standard
RFC 2987 VRRP-MIB RFC 3014 NOTIFICATION-LOGMIB
RFC 3019 IP Version 6 Management

Information Base for The Multicast RFC 3164 Syslog
Listener Discovery Protocol
draft-ietf-disman-alarm-mib-04.txt draft-ietf-ospf-mib-update-04.txt
draft-ietf-isis-wg-mib-05.txt draft-ietf-mpls-lsr-mib-06.txt
draft-ietf-mpls-te-mib-04.txt draft-ietf-mpls-ldp-mib-07.txt
5 Technical indices and specifications
5.1 Physical performance
Table 5-1 Equipment physical performance list
Equipment Subrack mm (width *

physical height * depth) (without 440*88.9*199
dimensions ear)
Equipment
Subrack mm (width *
physical 482.6*88.9*199
height * depth) (with ear)
dimensions
Parameters Weight <7.5kg
Total slot number 11

Slot number
Service slot 6
Power supply condition

-48V+/- 20%
(DC)
Rated current (DC) 5.9A

Power supply Maximal power
consumption in full <280W
configuration
Fuse specification 20A

Operating environment
-10°C~+50°C
temperature
Storage environment
-40°C~+70°C
temperature
Environment
requirements Relative humidity 5%~95%, non-congealing
Noise <55dB
Earthquake-resistance Resist earthquake of magnitude 9
MTBF >200000 hours
MTTR <0.5 hours
Reliability ≥99.999%
All boards are hot pluggable, rather than

Equipment Hot pluggable
interface sub-modules
reliability
Redundancy backup for
1+1 redundancy
main control
Redundancy backup for

1+1 redundancy
power supply
Heat Heat load with full

256W
dissipation capacity
5.2 Interface indices
Table 5-2 E1 interface electric performance
Electric performance Index
Nominal rate 2.048Mbit/s
Code pattern HDB3 (High Density Bipolar 3 code)
Allowable attenuation of input interface

0dB~6dB, 1024kHz
(attenuation in square root pattern)
Allowable frequency deviation of input

>±50ppm
interface
Bit rate error tolerance of output interface <±50ppm
Compliant with the Table 1/Figure 1 in

Output interface jitter
ITU-T G823

Electric performance Index
Compliant with the template specified

Output signal waveform
in ITU-T G.703
Anti-interference capability of input interface

18dB
(S/N)
Compliant with the Figure 13 in ITU-T

Input jitter and wander tolerance
G823
Compliant with the Chapter 9.3 of

Reflection attenuation
ITU-T G.703
Table 5-3 STM-1 optical interface performance
Type Performance
Nominal rate 155520kbit/s
NRZ scrambling codes (scrambling codes to meet the ITU-T

Code pattern G.707 requirements for seven synchronization scrambler
scrambling code)
Optical type S1.1 L1.1 L1.2
wavelength(nm) 1310nm 1310nm 1550nm
Transmission
<15km <40km <80km
distance
Connector LC/PC LC/PC LC/PC
Mean transmitting
-15~-8 dBm -5~0 dBm -5~0dBm
power
Minimum extinction
8.2dB 10.2dB 10.2dB
ratio
Receiver sensitivity -28 dBm -34 dBm -34 dBm
Receiver overload
-8dBm -10dBm -10dBm
optical power
Allowable frequency
deviation of optical >±20 ppm
input interface
AIS rate of optical

Within ±20 ppm
output interface

Table 5-4 STM-1/OC-12 optical interface performance
Type Performance
Nominal rate 620080kbit/s
NRZ scrambling codes (scrambling codes to meet the ITU-T

Code pattern G.707 requirements for seven synchronization scrambler
scrambling code)
Optical type S4.1 L4.1 L4.2
wavelength(nm) 1310nm 1310nm 1550nm
Transmission
<15km <40km <80km
distance
Connector LC/PC LC/PC LC/PC
Mean transmitting
-15~-8 dBm -3~2 dBm -3~2dBm
power
Minimum extinction
8.2dB 10dB 10dB
ratio
Receiver sensitivity -28 dBm -28 dBm -28 dBm
Receiver overload
-8dBm -8dBm -8dBm
optical power
Allowable frequency
deviation of optical >±20 ppm
input interface
AIS rate of optical

Within ±20 ppm
output interface
Table 5-5 10/100Base-TX interface electric performance
Type Performance
Standard compliance IEEE 802.3z
Nominal rate 10/100Mbit/s
10Mbit/s Manchester Encoding

Pattern
100Mbit/s MLT-3 Encoding
Interface RJ45
Maximum transmission
100m
distance
Transmission medium Use CAT 5 unshielded twisted pair (UTP)

Table 5-6 GE interface optical performance
Type Performance
Nominal rate 1000 Mbit/s
1000BASE 1000BASE- 1000BASE 1000BASE- 1000BASE

Interface type -SX LX -LH ZX -EZX
(0.5km) (10km) (40km) (80km) (800km)
Connector
LC LC LC LC LC
type
multimode single mode single single mode single

Fiber type
fiber fiber mode fiber fiber mode fiber
wavelength(n
850 1310 1310 1550 1550
m)
Transmitting
power -9.5~-4 -9~-3 -4~5 0~5 0~5
range(dBm)
receiving
sensitivity(dB ≤-17 ≤-20 ≤-22 ≤-22 ≤-30
m)
Table 5-7 10GE interface optical performance
Type performance
Nominal rate 10000 Mbit/s
Interface 10GBASE-S 10GBASE-LR 10GBASE-ER 10GBASE-ZR(80k

type R(0.3km) (10km) (40km) m)
Connector
LC LC LC LC
type
multimode single mode single mode

Fiber type single mode fiber
fiber fiber fiber
wavelength(
850 1310 1550 1550
nm)
Transmitting
power -7.3~-1 -5~-1 0~2 1~4
range(dBm)

Type performance
receiving
sensitivity(d ≤-11.1 ≤-14 ≤-16.5 ≤-26
Bm)
5.3 System Function List
5.3.1 L2 Feature
Table 5-8 L2 Feature
VLAN Support port-based VLAN
Support QinQ-based forwarding

Support regular QinQ and port-based outer label.
Support Selected QinQ and traffic-based outer label.
QinQ
Support Selected QinQ inner priority mapping.
Support TPID modification
Support 1:1, 1:2 and 2:1 mode QinQ service.
Support MAC address learning and aging

Support static MAC address setting
Support MAC address add, deletion, display, search
MAC and count
L2 features Support MAC address number restriction
Support MAC address attack protection
Support SVL address learning
Support static configuration and dynamic protocol

(LACP) automatic configuration
LAG
Support traffic-based load balance
Support cross-line card aggregation
Support broadcasting packet suppression

Support multicast packet suppression
Storm
Support unknown packet suppression
Suppression
Support unknown unicast/multicast discard
Support unknown unicast/multicast broadcast

Support unknown unicast/multicast designating
forwarding port
Support static ARP configuration

ARP Support dynamic ARP learning
Support dynamic ARP entry aging
Support STP, RSTP and MSTP

STP Shut down spanning tree protocol on the basis of
port and entity
Support ingress mirroring, egress mirroring and CPU

Port mirroring
Support port traffic control service
Support IGMP Snooping

L2 multicast
Support Proxy
DHCP Support DHCP Relay
5.3.2 L3 Feature
Table 5-9 L3 Feature
Support VLAN L3 interface
Support VCG-based L3 interface

L3 interface
Support L3 interface based upon Qx port
Support L3 interface based upon DCC tunnel
Support ARP protocol
Support ICMP protocol
L3 feature Support UDP protocol
Support TCP protocol

Protocol and
Support VRRP protocol
service
Support IP FRR
Support IPv4 unicast route forwarding
Support static route
Support OSPF routing protocol

Support IS-IS routing protocol
Support BGP routing protocol
Support ECMP
5.3.3 QoS Feature
Table 5-10 QoS Feature
Traffic Support physical-port traffic classification

classification Support ACL-based traffic classification
Support 802.1priority, IP Precedence, IP DSCP, IP

Message
TOS, MPLS EXP relabeling
relabeling
Support dual-layer label mapping
Support inward port CAR

Support flow-based CAR
Traffic policing Support ingress/egress traffic policing.
Support two token buckets.
Support the relabeling after traffic policing
Support flow-based bandwidth control

QoS feature
Congestion Support WRED
control Support CAC
Support Tail Drop
Each port supports at least 8 priority queues. Each

Queue queue supports the minimum/maximum bandwidth
scheduling management.
Support WRR, SP scheduling
Support outward port-based shaping

Traffic shaping
Support outward queue-based shaping
Hierarchical Support ingress/egress H-QoS, 4 levels

QoS

5.3.4 Service Management
Table 5-11 Service Management
Service
Support AAA authentication
management
5.3.5 Reliability
Table 5-12 Reliability
Object Under Protection

Protection Type Protection Mode
Protection Time
1:1 Tunnel protection < 50ms

MPLS Linear protection
FRR < 50ms
1+1 Tunnel protection < 50ms
1:1 Tunnel protection < 50ms

Linear protection
1+1 PW protection < 50ms
MPLS-TP
1:1 PW protection < 50ms
Wrapping protection < 50ms

Ring protection
Shared ring protection < 50ms
Ch.STM-1 interface 1+1 protection < 50ms

LMSP 1:1 protection < 50ms
ATM STM-1 interface 1+1 protection < 50ms

LMSP 1:1 protection < 50ms
GE interface
STM-N Link 1:1/1+1,
dual-homing < 50ms
return/non-return
protection
Intermediate node
has additional
/ < 50ms
assistant protection
group

Object Under Protection

Protection Type Protection Mode
Protection Time
STP
MSTP (Multi STP)
(Spanning Tree < 250ms
protection
Protocol) protection
Intra-board Ethernet port

LAG protection
LAG protection < 200ms
Inter-board Ethernet port
LAG protection
5.3.6 Clock Synchronization
Table 5-13 Clock Synchronization
Clock Synchronization Support port-based clock restoration.

synchronization Ethernet Support clock distribution of the overall
system.
Support clock extraction (line, external
2Mbit clock and GPS clock).
Support SSM processing.
IEEE 1588v2 Support clock transparent transmission.

Support precise time synchronization.
Support multi-session.
Support BCM algorithm.
Pulse phase Support 1Hz second pulse interface.

synchronization
5.3.7 Tunnel Feature
Table 5-14 Tunnel Feature
PWE3 circuit SupportE1 and Ethernet FE/GE interface PWE3
PWE3
emulation circuit emulation.
feature
TDM circuit Support self-adaptive clock recovery

timeslot Support E1 retiming
Support MPLS-TP tunnel

Support 1+1 and 1:1 linear protection
MPLS-TP
Support 1+1 and 1:1 SNC linear protection
tunnel
Support steering/wrapping ring protection
Support APS switchover
5.3.8 Security Feature
Table 5-15 Security Feature
Support anti-DOS attack

Support anti-BPDU attack
Support CPU protection
Support ARP attack
Support IPv4 uRPF
Support hierarchical command protection
Support malformed message and error message
protection
Support anti-IP fragment
Anti-attack Support anti-LAND attack
protection Support anti-SMURF attack
Security
Support anti-SYN FLOOD attack
feature
Support anti-PING FLOOD attack
Support anti-Teardrop attack
Support anti-Ping of Death attack
Support RFC2267 interface filtration
Support unidirectional session control
Support Packet header logging
Support Session hi jacking
Support anti-fake source IP address attack
Support protocol priority processing switch service

CPU security
Support protocol packet protection service
protection
Support upstreaming CPU message matching

filtration service
Support data log monitoring

Advanced Support broadcasting storm automatic suppression
security Support control/signaling MD3 encryption and
feature authentication
Support DPI, FIREWALL,
5.3.9 Operation and Maintenance
Table 5-16 Operation and Maintenance
Support command line service
Support hierarchical management authority
Support password aging and confirmation service
Support console management service
Support user access service management service
Support SSH, TELNET, WEB, SNMP and SSL
remote access service.
Support multiple sorts of alarm (audio and light
alarm platform)
Operation Operation and Support unified network management

and maintenance Support CLI to support hierarchical network
maintenance management
service Support user access control service
Support configuration storage recovery service
Support operation log record service
Support alarm log management service
Support basic MIB service
Support traffic statistics service
Support Ping
Support Trace
Cluster
LLDP
management

Support MPLS-TP OAM

Support Ethernet link OAM
OAM
Support Ethernet OAM
Support MPLS OAM
6 Operation and maintenance
6.1 Unified NM platform
ZXCTN 6150 employs NetNumen U31 to perform unified management and monitoring
for all NEs, offering configuration management, fault management, performance
management, Maintenance management, ETE circuit management, security
management, system management and report management functions.
NetNumen U31 is the network management system based on distributed and plug-in
design, serving as the unified management platform for all ZTE optical transmission
series. With multiple network management techniques, the system is designed and
developed in line with ITU-T TMN concept, enabling management and control of NE and
regional network on basis of ensuring transmission equipment functions. It offers robust
NE management function, end-to-end management function and flexible networking
capability.
6.2 Maintenance and management
6.2.1 Equipment management
 Support maintenance and management interface running in command line, and

perform NE management and configuration.
 Support console management. Common user or privileged user logs in to the

console to configure NE parameters and monitor the running state.

 Support remote access via SSH. Support remote access via SSH V1/V2, and allow
NM server to communicate with the equipment.
 Support Telnet management.
 The equipment allows up to four Telnet users to log in to NE for

configuration management;
 Support ACL access control of Telnet access users.
 Support SNMP protocol.
 Enable query of NE parameter setting and running state via GET/SET

operations in SNMP protocol;
 Support ACL access control of SNMP access users.
 Provide NM interface management. Enable access of NE via this interface to

implement NE management and configuration.
 Provide FTP/Telnet interface. The equipment has FTP/Telnet server and client
functions.
 NE communication management.
 Intercommunication of in-band management control information;
 Intercommunication of out-of-band management control information;
 Network management interoperability;
 Routing and forwarding of NM information;
 Unified NM function.
6.2.2 Supervision and maintenance
ZXCTN 6150 can perform equipment monitoring, management and maintenance via
multiple options, enable the equipment to perform corresponding exception handling in

case of the occurrence of various exceptions, and offer user with all running parameters
during equipment operation.
 Offer four external alarm input/output interfaces, to ease equipment operation and
maintenance
 Running, alarm state indicators are available at power supply, fan, main control and
all service boards, helping network administrator localize and handle failures in time
 Support automatic online optical power detection and automatic shutdown of laser
for optical interface
 The system monitors the software running state, and performs line card restart or
master-slave switching of main control board in case of the equipment’s normal
operation affected by the occurrence of exceptions
 Command line offers agile online help for network management
 Support online backup and loading of database, restore system configuration

based on database
 Provide hierarchical user authority management and hierarchical command
 Support query of operation log, enable trace back of maintenance operations to

localize fault reason and demarcate the liability of fault;
 Support packet loading and remote loading of board and host software, and provide
mis-loading prevention and segmented download functions.
6.2.3 Diagnosis and debugging
 ZXCTN 6000 provides multiple diagnosis and debug measures, allowing users to
have a wider variety of methods and acquire more debug information during
equipment debug.
 Ping and TraceRoute: check whether network connection is reachable; record the
transmission route of packet online, serving as reference for fault localization.

 Debugging: provide rich debug commands targeting each software feature, each
debug command supports multiple debug parameters under flexible control. Debug
command can be used to output in details the processing, message
transmitting/receiving and error checking information during running of the feature.
 Mirror function: support port-based mirror function, the messages from input, output
or both directions of observed interface are copied intact to the observing interface.
6.2.4 Software upgrade
ZXCTN 6150 supports local or remote FTP online upgrade.
Main control board can be upgrade with main control unit redundant protection to avoid
disconnecting services during upgrade.
When upgrading other boards (in addition to main control board) with redundant
protection, the services will not be disconnected typically, or the disconnection time is
less than 50ms.
Support mis-loading prevention for software, rollback when upgrade fails, and the
reversible upgrade process.
7 Environment indices
7.1 Storage
7.1.1 Climate environment
The climate requirements for equipment storage are described in Table 7-1.
Table 7-1 Requirements for climate (storage environment)
Item Index
Altitude ≤5000 m
Air pressure 70 kPa ~ 106kPa

Item Index
Temperature -40°C ~ +75°C
Temperature variance ratio ≤1°C /min
Relative humidity 10% ~ 100%
Solar radiation ≤1120 W/s2
Heat radiation ≤600 W/s2
Wind speed ≤20 m/s
7.1.2 Water-proof requirement
Storage requirements for on-site equipments: keep the equipments indoor.
There must be no water on the storage room floor, so that the water will not leak on the
packing container of the equipment. Furthermore, the storage position should be far
away from the leaking places of the firefighting equipment and heating system.
If the equipment has to 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 can not damage
the pack of the equipment.
 Ensure no water in the storage place, so that the packing container of the
equipment will not be leaked.
 Keep the packing container out of direct sunlight.
7.2 Transportation
7.2.1 Climate environment
The climate requirements for equipment transportation are described in Table 7-2.

Table 7-2 Requirements for climate (transportation environment)
Item Index
Altitude ≤4000 m
Temperature -40°C ~ +70°C
Temperature variance ratio ≤1°C /min
Relative humidity 10% ~ 100%
Wind speed ≤20 m/s
7.2.2 Water-proof requirements
Storage requirements for equipments transportation: keep the equipments indoor.
There must be no water on the floor during the transportation so that the water will not
leak on the packing container of the equipment. Furthermore, the storage position should
be far away from the leaking places of the firefighting equipment and heating system.
If the equipment has to be stored outdoor, requirements are listed as follows:
 Ensure that the packing of the equipment is in good condition without any damages.
 Rainwater-proof transportation tools should be provided, so that the rainwater can

not damage the pack of the equipment.
 Ensure that no water in transportation tools.
7.3 Running
The environment temperature and relative humidity requirements for equipment running
are described in Table 7-3, other climate environment requirements are described in
Table 7-3.

Table 7-3 Temperature and humidity requirements (running environment)
Item Specifications
Environment Long term running -10°C ~+50°C

temperature Short term running -10°C ~+55°C
Relative Long term running 5%~95%

humidity Short term running 5%~95%
Note: temperature and humidity are measured 1.5m above the floor and 0.4m in front of
the equipment. Short term running means that the equipment working continuously for no
more than 96 hours and works for no more than 15 days in one year.
Table 7-4 Other climate environment requirements (running environment)
Item Index
Altitude ≤4000 m
Temperature variance ratio ≤30°C /h
Wind speed ≤5 m /s
7.4 Electromagnetic compatibility (EMC)
EMC include anti-interference and interference.
7.4.1 Criteria
The following four criteria for test results should be determined before describing the
requirements for electromagnetic compatibility, as shown in the following table.
Table 7-5 Criteria for test results
Criteria Description

Criteria Description
Digital signal port: The equipment runs normally in the test. The bit
error quantity does not exceed the maximum limit of the normal
requirement after single electromagnetic interference (The
Performance A maximum is 0 here).
Analog audio signal port: The connection is always normal in the
test. The noise signal of the test equipment (EUT), measured with
600Ohm impedance, does not exceed -40 dBm.
Digital signal port: The electromagnetic interference temporarily

lowers the functions of the equipment which will automatically
return to normal after the interference disappears. There is no
Performance B frame loss, synchronization loss and alarm between interferences.
Analog audio signal port: The connection is always normal, but the
disconnection is allowed in the surge test. The test equipment
(EUT) will return to normal after the interference disappears.
The electromagnetic interference temporarily lowers the functions

Performance C of the equipment which will return to normal automatically or
manually after the interference disappears.
The equipment has no loss or fault (e.g., software damage and

wrong operation of protection equipment), and runs properly in the
defined range after Transient EMC phenomenon disappears. The
Performance R
interference may affect the fuse or other defined equipment. The
fuse can be replaced or the equipment can be reset before normal
operation.
7.4.2 Anti-interference
Electronic Static Discharge (ESD) immunity
ESD immunity index is shown in .following table
Table 7-6 ESD immunity
Contact discharge Air discharge Criterion for test results

6 kV 8 kV Performance B
8 kV 15 kV Performance R
Note: It is compliant with IEC61000-4-2 and GB/T 17626.2-1998.

1. RF electromagnetic field radiation immunity (RS)
RF electromagnetic field radiation immunity index is shown in Table 7-7.
Table 7-7 RF electromagnetic field radiation immunity Resistance
Test frequency 80 MHz ~2 GHz

Electric field intensity Amplitude modulation Criterion for test results
10 V/m 80%AM (1 kHz) Performance A
Note: It is compliant with IEC61000-4-3, GB/T 17626.3-1998, 73/23/EEC and

89/336/EEC.
2. Electric Fast Transient (EFT) immunity
i. DC port immunity (direct coupling)
DC port immunity is shown in Table 7-8.
Table 7-8 DC port immunity
Generator Repetition Criterion for test

Test voltage
waveform frequency results
5 ns/50 ns ±1 kV 5 kHz Performance B
ii. AC port immunity (direct coupling)
AC port immunity index is shown in Table 7-9.
Table 7-9 AC port immunity

Test voltage

iii. Signal line and control line port immunity (using capacitor coupling pliers)
Signal line and control line port immunity index is shown in Table 7-10.
Table 7-10 Signal line and control line port immunity

Test voltage
3. Lightning surge immunity
DC lightning surge immunity index is shown in Table 7-11.
Table 7-11 DC lightning surge immunity
Generator waveform:1.2 μs/50 μs (8 μs/20 μs)

Test mode Test mode Test mode Test mode
Line-to-line Line-to-line Line-to-line Line-to-line
Line-to-ground Line-to-ground Line-to-ground Line-to-ground
AC lightning surge immunity index is shown in Table 7-12.
Table 7-12 AC lightning surge immunity
Internal
Test mode Test voltage Criterion for test results
resistance
Line-to-line 2Ω ±4 kV Performance B
Line-to-ground 12 Ω ±6 kV Performance B
Outdoor signal line surge immunity index is shown in Table 7-13.

Table 7-13 Outdoor signal line surge immunity
Generator waveform:10 μs/700 μs
Internal
resistance
Signal line (>10m) surge immunity index is shown in Table 7-14.
Table 7-14 Signal line (>10m) surge immunity
Internal
resistance
4. RF field conductivity immunity (CS)
RF field conductivity immunity index is shown in Table 7-15.
Table 7-15 RF field conductivity immunity
Test frequency: 0.15 MHz~80 MHz
Test intensity Amplitude modulation Criterion for test results
3V 80%AM (1 kHz) Performance A
5. Transient voltage dip and short interruption immunity
AC transient voltage dip and short interruption immunity index are shown in Table
7-16.
Table 7-16 AC transient voltage dip and short interruption immunity
Voltage reduction rate Duration (ms) Criterion for test results

>95% 50 Performance B
30% 500 Performance C

>95% 5000 Performance C
Note: The index is only applied to AC power supply (PWB board). It is compliant with
IEC61000-4-11 and GB/T 17626.11-1999.
DC transient voltage dip and short interruption immunity index are shown in Table 7-17.
Table 7-17 DC transient voltage dip and short interruption immunity
Voltage Additional Criterion for

Index Duration (ms)
variation rate condition test results
0.01 - Performance B
70%
1 - Performance C
Voltage dip
0.01 - Performance B
40%
1 - Performance C
0.001 High Performance B

impendence
(Trial
0
5 generator Performance C
outputs the
Short impedance)
interruption 0.001 High Performance B
impendence
(Trial
0
5 generator Performance C
outputs the
impedance)
0.1 - Performance A
80%
Voltage 10 - Performance A
variation 0.1 - Performance A
120%
10 - Performance A
Note: The index is only applied to DC power supply (PWA board). It is compliant with
IEC61000-4-11 and GB/T 17626.11-1999.
6. Voltage fluctuation and flicker immunity

AC port voltage fluctuation immunity index is shown in Table 7-18.
Table 7-18 AC port voltage fluctuation immunity

95% 10 Performance B
7.4.3 Interference
The interference consists of conducted emission and radiated emission. The indexes are
compliant with CISPR 22 and GB 9254 Class A.
1. Conducted emission
DC/AC port conducted emission index is shown in Table 7-19.
Table 7-19 DC/AC port conducted emission
Voltage limit value (dBμV)

Test frequency (MHz)
Quasi-peak value Average value
0.15~0.50 79 66
0.50~30.00 73 60
Ethernet/E1 port conducted emission index is shown in Table 7-20.
Table 7-20 Ethernet/E1 port conducted emission
Voltage limit value (dBμV)

Quasi-peak value Average value
0.15~0.50 97~87 84~74
0.50~30.00 87 74
2. Radiated emission
Radiated emission strength index is shown in Table 7-21.

Table 7-21 Radiated emission strength
Quasi-peak limit value (dBμV/m)

Test distance 10m Test distance 3m
30~230 40 50
230~1000 47 57
8 Abbreviation
Abbreviation Full name
ACL Access Control List
AG Access Gateway
APC Automatic Power Control
APS Automatic Protect Switch
ASIC Application Specific Integrated Circuit
ARPU Average Revenue Per User
ATCA Advanced Telecom Computing Architecture
ATM Asynchronous Transfer Mode
BCB Backbone Core Bridge
BEB Backbone Edge Bridge
BFD Bidirectional Forwarding Detection
BGP Border Gateway Protocol
B-MAC Backbone MAC
BPDU Bridge PDU
CAC Connection Access Control
CAM Content-addressable Memory
CAN Controller-area Network
CAPEX Capital Expenditures
CDN Content Distribution Network
CDR Call Detail Record
CE Carrier Ethernet
CESoPSN Circuit Emulation Services over PSN
CMS Center Media Server

CV Connectivity Verification
DoS Denial of Service
DPI Deep Packet Inspection
DVMRP Distance vector Multicast Routing Protocol
EAPS Ethernet Automatic Protection Switching
ECMP Equal Cost of Multi-path
E-LAN Ethernet LAN
E-LINE Ethernet LINE
EMS Edge Media Server
ESRP Ethernet standby Routing Protocol
E-TREE Ethernet TREE
FDDI Fiber Distributed Digital Interface
FFD Fast Failure Detection
FR Frame-relay Protocol
FRR Fast Reroute
GFP General Format Protocol
GPS Global Position System
GR Graceful restart
HDLC High Level Data Link Control
H-VPLS Hierarchical Virtual Private Lan Servie
IAD Integrated Access Device
ICMP Internet Control Message Protocol
IGMP Internet Group Management Protocol
IMA Inverse Multiplexing for ATM
IPMS Intelligent Platform Message sub-system
IPMC Intelligent Platform Message control
IPOE IP over Ethernet
IPS Intrusion Detection Systems
IPMB Intelligent Platform Message Bus
ISIS Intermediate System-Intermediate System
LACP Link Aggregation Control Protocol

LIC Line Interface Card
LPC Line Process Card
LSP Label Switch Path
MCE Multi-instance Customer Edge
MPLS Multi-Protocol Label Swtiching
MSG Media Service Gateway
MSTP Multiple Spanning Tree Protocol
MTU Maximum Transmission Unit
MVR Multicast VLAN Registration
NE Network Element
NGN Next Generation Network
OAM Operations Administration and Maintenance
OPEX Operation Expense
OSPF Open Shortest Path First
PIM Protocol Independent Multicast
PIM-DM Protocol Independent Multicast-Dense Mode
PIM-SM Protocol Independent Multicast-Sparse Mode
PIM-SSM Protocol Independent Multicast-Source Specific Multicast
PMD Physical Medium Dependent
POS Packet over SDH
PPP Point to Point Protocol
PPPoE PPP over Ethernet
PRV Preview
PSN Packet Switch Network
PUPSPV Per User Per Service Per VLAN
PVLAN Private VLAN
PW Pseudo-wire
PWE3 PW Emulation End to End
RED Random Early Detection
RIP Routing Information Protocol
RNC Radio Network Controller

ROS Routing Operation System
RP Rendezvous Point
RPR Resilient Packet Ring
RSTP Rapid Spanning Tree Protocol
SAToP Structure-Agnostic TDM over PSN
SDH Synchronous Digital Hierarchy
SLA Service Level Agreement
SMS Service Management System
SNMP Simple Network Management Protocol
SSM Source Specific Multicast
STP Spanning Tree Protocol
SyncE Synchronization Ethernet
SVLAN Select VLAN
TCO Total Cost of Ownership
TCP Transport Control Protocol
TDM Time Division Multiplex and Multiplexer
TL1 Transaction Language 1
TM Traffic Manager
UDP User Datagram Protocol
URPF Unicast Reverse Path Forwarding
VLL Virtual Leased Line
VOIP Voice over IP
VPLS Virtual Private LAN Service
VPN Virtual Private Network
VPWS Virtual Private Wire Service
VRF Virtual Routing and Forwarding
VRRP Virtual Router Redundancy Protocol
WRED Weighted Random Early Detection
WFQ Weighted Fair Queuing
ZESR ZTE Ethernet Smart Ring
ZESS ZTE Ethernet Smart Switching

ZGMP ZTE Group Management Protocol
ZGMS ZTE General Multicast System
ZTP ZTE Topology Discovery Protocol
9 Standards and recommendations
9.1 IETF
RFC 1661 Point-to-Point Protocol
RFC 1990 PPP Multilink Protocol
RFC 2475 Architecture for Differentiated Services
RFC 2686 Multi-Class Extension to Multi-Link PPP
RFC 2858 Multiprotocol Extensions for BGP-4
RFC 2974 Session Announcement Protocol
RFC 2961 RSVP Refresh Overhead Reduction Extensions
RFC 3086 Definition of Differentiated Services Per Domain Behaviors and Rules for
their Specification
RFC 3246 An Expedited Forwarding PHB (Per-Hop Behavior)
RFC 3247 Supplemental Information for the New Definition of the EF PHB (Expedited
Forwarding Per-Hop Behavior)
RFC 3260 New Terminology and Clarifications for Diffserv
RFC 3916 PWE3 requirements

RFC 3965 PWE3 structure
RFC 4026 Provider Provisioned Virtual Private Network (VPN) Terminology
RFC 4127 Russian Dolls Bandwidth Constrains Model for Diffserv-aware MPLS
Traffic Engineering.
RFC 4446 IANA Allocations for PWE3
RFC 4448 Encapsulation of Ethernet over MPLS
RFC 4553 Structure-Agnostic TDM over Packet
RFC 4664 L2VPN structure
RFC 4665 L2VPN requirements
RFC 4717 Encapsulation for ATM over MPLS
RFC 4816 ATM Transparent Cell Transport Service
RFC 4950 ICMP Extensions for Multiprotocol Label Switching
RFC 5086 Structure-aware TDM Circuit Emulation Service over Packet Switched
Network (CESoPSN)
9.2 ITU-T
G.703 Physical/electrical characteristics of hierarchical digital interfaces
G.704 Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44 736
kbit/s hierarchical levels
G.706 Frame alignment and cyclic redundancy check (CRC) procedures relating
to basic frame structures defined in Recommendation G.704
G.707 Network Node Interface for the Synchronous Digital Hierarchy (SDH)
(V2003)

G.774 Synchronous Digital Hierarchy (SDH) - Management Information Model
G.774.01 Synchronous Digital Hierarchy (SDH) performance monitoring for the

network element view
G.774.02 Synchronous digital hierarchy (SDH) configuration of the payload structure

for the network element view
G.774.03 Synchronous digital hierarchy (SDH) management of multiplex-section

protection for the network element view
G.774.05 Synchronous Digital Hierarchy (SDH) management of connection

supervision functionality (HCS/LCS) for the network element view
G.774.06 Synchronous digital hierarchy (SDH) unidirectional performance

monitoring for the network element view
G.774.07 Synchronous Digital Hierarchy (SDH) management of lower order path

trace and interface labeling for the network element view
G.7041 Generic framing procedure (GFP)
G.7042 Link capacity adjustment scheme (LCAS) for virtual concatenated signals
G.780 Terms and definitions for SDH networks
G.783 Characteristics of SDH equipment functional blocks
G.784 Synchronous digital hierarchy (SDH) management
G.803 Architecture of transport networks based on the synchronous digital

hierarchy (SDH)
G.805 Generic functional architecture of transport networks
G.810 Definitions and terminology for synchronization networks
G.811 Timing characteristics of primary reference clocks

G.812 Timing requirements of slave clocks suitable for use as node clocks in
synchronization networks
G.813 Timing characteristics of SDH equipment slave clocks (SEC)
G.823 Control of Jitter and Wander within Digital Networks Which Are Based on
the 2048 KBIT/S Hierarchy Series
G.824 Control of Jitter and Wander within Digital Networks Which are Based on
the 1544 kbit/s Hierarchy
G.825 The control of jitter and wander within digital networks which are based on
the synchronous digital hierarchy (SDH)
G.826 Error performance parameters and objectives for international, constant bit
rate digital paths at or above the primary rate
G.831 Management capabilities of transport networks based on the synchronous

digital hierarchy (SDH)
G.832 Transport of SDH elements on PDH networks - Frame and multiplexing

structures
G.841 Types and characteristics of SDH network protection architectures
G.842 Interworking of SDH network protection architectures
G.957 Optical interfaces for equipments and systems relating to the synchronous
digital hierarchy
G.958 Digital line systems based on the synchronous digital hierarchy for use on
optical fiber cables
G.8101 Terms and Definitions for Transport MPLS
G.8110.1 Architecture of Transport MPLS (T-MPLS) Layer Network
G.8112 Interfaces for the Transport MPLS (T-MPLS) Hierarchy
G.8113 Requirements for OAM function in T-MPLS based networks

G.8114 Mechanism for OAM function in T-MPLS based networks
G.8121 Characteristics of T-MPLS equipment functional blocks
G.8131 T-MPLS Linear Protection Switching
G.8132 T-MPLS shared protection ring
I.361 B-ISDN ATM layer specification
K.41 Resistibility of internal interfaces of telecommunication centers to surge

overvoltage
M.20 Maintenance principle of telecommunications network
M.2100 Performance limits for bringing-into-service and maintenance of

international PDH paths, sections and transmission systems
M.2101 Performance limits for bringing-into-service and maintenance of

international SDH paths and multiplex sections
M.2120 International multi-operator paths, sections and transmission systems fault

detection and localization procedures
M.3010 Principles for a Telecommunications management network
M.3400 TMN management functions
Q.811 Lower layer protocol profiles for the Q3 and X interfaces
Q.812 Upper layer protocol profiles for the Q3 and X interfaces
Y.1413 TDM-MPLS network interworking - User plane interworking
Y.1731 OAM functions and mechanisms for Ethernet based networks
I.432.2 B-ISDN user-network interface -155520kbit/s and 620080kbit/s physical

layer specification
I.432.3 B-ISDN user-network interface -1544kbit/s and 2048kbit/s physical layer

specification

I.761 Inverse multiplexing for ATM (IMA)
9.3 IEEE
IEEE 802.3 Carrier Sense Multiple Access with Collision Detection (CSMA/CD)
Access Method and Physical
IEEE 802.1ad Virtual bridged local area networks
IEEE 802.1ag Virtual Bridged Local Area Networks - Connectivity Fault Management
IEEE 802.3ah Media Access Control (MAC) Parameters, Physical Layers and
Management Parameters for Subscriber Access Networks
9.4 MEF
MEF 4 Metro network structure frame part 1 - Generic frame
MEF 6 Metro Ethernet service definition stage 1
MEF 8 PDH circuit emulation service transport specification over Metro Ethernet
MEF 10.1 Ethernet service attributes stage 2
MEF 11 UNI requirement and frame

ZXCTN 6150 V3.00 Product Description - 20140106 - EN

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ZXCTN 6150 V3.00 Product Description - 20140106 - EN

Uploaded by

Copyright:

Available Formats

ZXCTN 6150 V3.

ZXCTN 6150 V3.0 Product Description

Zhao Yue, Pan

© 2018 ZTE Corporation. All rights reserved.

ZTE Confidential & Proprietary 1

3 Functions and features ................................................................................... 11

2 ZTE Confidential & Proprietary

3.7.6 VPN FRR ........................................................................................................... 54

4 System structure ............................................................................................. 83

5 Technical indices and specifications ........................................................... 119

ZTE Confidential & Proprietary 3

5.3 System Function List ........................................................................................ 124

6 Operation and maintenance ......................................................................... 131

7 Environment indices ..................................................................................... 134

8 Abbreviation .................................................................................................. 144

9 Standards and recommendations ................................................................ 148

4 ZTE Confidential & Proprietary

Figure 3-1 ZXCTN 6000 E-LINE service model..................................................................16

ZTE Confidential & Proprietary 5

Figure 3-29 Bidirectional 1: 1 Tunnel Protection Switching Architecture)............................71

6 ZTE Confidential & Proprietary

ZTE Confidential & Proprietary 7

Table 5-12 Reliability .......................................................................................................127

8 ZTE Confidential & Proprietary

ZXCTN 6110(F)/6120/6120S/6130XG-S is the compact IP transport network platform.

ZXCTN 6000 series are often used for:

 VIP access and VPN service

ZTE Confidential & Proprietary 9

 Leading time synchronization technology to achieve high-precision synchronization

 Good end-to-end QoS to provide differentiated service (Differ-Serv)

 Powerful hierarchical OAM to increase network availability

 Multiple reliability mechanisms to guarantee network security

10 ZTE Confidential & Proprietary

 Open technology platform to support high growth of service network

 Unified NMS to simplify OAM

3 Functions and features

3.1 Capacity and interfaces

3.1.1 Service processing capability

ZTE Confidential & Proprietary 11

3.1.2 Switching capability

Table 3-1 ZXCTN 6150 switching capability

Service processing ZXCTN 6150

Switching capacity 90 Gbps(Unidirectional)

Access capacity 60~90G Gbps

Packet forwarding rate 89.28~133.92Mpps

3.1.2.1 Access capability

Note: Ch. =Channelized.

Table 3-2 ZXCTN 6150 maximum access capability

Interface Board port Overall port

PDH TDM E1 16 112

STM-N Ch. STM-1 4 28

12 ZTE Confidential & Proprietary

3.1.3 Interface type

3.1.3.1 ZXCTN 6150 interface type and number

Table 3-3 ZXCTN 6150 service interface

Type Description Remark

FE interface Electrical UNI/NNI

GE interface Electrical interface:1000BASE-T UNI/NNI

10GE interface Optical interface: 10GBASE-SR, UNI/NNI

STM-1 interface Ch. STM-1 optical interface Ch.STM-1 optical interface

E1 interface E1 interface UNI (TDM E1)

Table 3-4 ZXCTN 6150 auxiliary interface type and number

Auxiliary interface Number Parameter Remark