Professional Documents
Culture Documents
Manual 6120s
Manual 6120s
Product Description
Version: V3.00
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2014 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
II
III
IV
Intended Audience
This manual is intended for:
l Maintenance engineers
l Network management personnel
Chapter 1, Overview Describes an external view, features and position of the ZXCTN 6120S
in the network.
Chapter 2, Architecture Describes the logical, hardware and software architectures of the
ZXCTN 6120S.
Chapter 3, Services Describes the service flow and service processing capability of the
ZXCTN 6120S.
Chapter 4, Functions Describes the functions of the ZXCTN 6120S, including the MPLS-TP,
MPLS, L2, L3, OAM, QoS, clock and time, security and reliability,
microwave functions.
Chapter 5, Protection Describes the equipment level,, network side, and network edge
protections supported by the ZXCTN 6120S.
Chapter 6, Interfaces Describes the board service interfaces and external interfaces of the
ZXCTN 6120S.
Chapter 7, Networking Describes service network applications and integrated solutions of the
Applications ZXCTN 6120S.
Chapter 8, Technical Describes the technical specifications of the ZXCTN 6120S, including
Specifications system performance, physical performance, power consumption index,
grounding requirements, lightning-proof requirements, electromagnetic
compatibility requirements, reliability specifications, and interface
specifications.
Appendix A, Standards Describes the standards and recommendations that the ZXCTN 6120S
and Recommendations complies with.
II
1.1 Overview
The ZXCTN 6120S is a carrier-class multi-service bearer product. It is dedicated to
carrying and transmitting services in an integrated mobile backhaul and multi-service
network.
For the overview of the ZXCTN 6120S, see Figure 1-1.
1-1
Synchronous Network
l Uses the G.8261 and 1588 V2 technologies to implement the accurate insertion and
extraction of timestamps in the 1588 protocol, which improves the accuracy of time
synchronization.
l Supports the Circuit Emulation Service (CES) clock transmission function and IEEE
1588 V2 Adaptive Clock Recovery (ACR) clock transparent transmission function.
l Supports flexible configuration of the boundary clock and transparent transmission
clock, out-of-band 1 Pulse Per Second (PPS) + Time of Delivery (ToD) interfaces,
and in-band synchronous Ethernet interfaces.
l Supports the synchronous Ethernet networking application. Each NE can be locked
to the same clock source, thus accomplishing synchronization in the entire network.
1-2
l Uses the Synchronization Status Message (SSM) protocol and Best Master Clock
(BMC) algorithm to implement the automatic protection switching of the clock and
time link, to guarantee reliable transmission of synchronous signals.
End-to-End QoS
l Provides the end-to-end Quality of Service (QoS) management function to satisfy the
requirements of various services for the delay, jitter, and bandwidth.
l Supports the Differentiated Service (DS)-based QoS scheduling.
l Implements traffic classification and labeling according to the port, Virtual Local Area
Network (VLAN), 802.1p, Differentiated Services Code Point (DSCP)/Type of Service
(ToS), Medium Access Control (MAC), and Internet Protocol (IP) address.
l Supports traffic monitoring, queue scheduling, congestion control, and traffic
shaping to control the user-level multi-service bandwidth and guarantees customer’s
refinement operation.
Hierarchical OAM
l Supports MPLS-TP Operation, Administration and Maintenance (OAM), Ethernet
OAM, and Multi Protocol Label Switching (MPLS) OAM.
l Uses the hierarchical monitoring OAM mode based on hardware to implement
fast fault detection and location, performance monitoring, and end-to-end service
management.
l Supports active and on-demand OAM, and ensures carrier-class service quality in the
packet transport network.
l Supports various hierarchical OAM based on the logical link, Pseudo Wire (PW),
tunnel, and section, which makes the network operation and management more
transparent and convenient.
Protection Mechanism
The ZXCTN 6120S provides complete equipment-level protection, network-side
protection, and client-side protection.
l Supports the following types of equipment-level protection:
à 1+1 hot backup protection of the main boards.
à 1+1 hot backup protection of the DC power boards.
l Supports the following types of network-side protection:
1-3
Compatibility
l Uses the open technical platform to accommodate traditional transmission and data
networks.
l Uses flexible system design, which applies to the development of various transmission
standards and supports the evolution of the service network.
1-4
2-1
l Clock unit: It provides clock signals for boards, and implements 1588 time
synchronization.
2-2
For the subrack structure description of the ZXCTN 6120S, refer to Table 2-1.
1 Power board area The power board is inserted here to supply power to the
equipment.
2 Board area The system main board and the service boards are inserted
here. Among them, the main control board provides the control,
switching and clock processing of the system and the service
boards provides external service interfaces.
4 Fan area It is inserted in the fan module and dissipates the heat of the
subrack.
2-3
The ZXCTN 6120S system software uses layered structure design with each layer
implementing specific function and providing service to the upper layer. For the software
structure of the ZXCTN 6120S, see Figure 2-3.
2-4
l Board agent program: implements the inter-communication within the main control
board.
l Service processing module: implements the service configuration and
alarm&performance processing.
l IP protocol stack module: applicable to gateway NE boards.
l Supporting module: implements the inter-communication between the service
processing module, IP protocol stack module, special protocol module for board
running and driving module.
2-5
2-6
1. The ZXCTN 6120S connects Ethernet services and TDM services of CE devices
through UNI interfaces.
2. The ZXCTN 6120S adapts the connected services and converts them to the Ethernet
message format on the NNI side for transmission.
3-1
PW Processing Layer
l The PW processing layer encapsulates services into PWE3 packets.
l The PW processing layer decapsulates PWE3 packets to restore services.
l The PW processing layer identifies services through PW labels. Each service
corresponds to a unique PW label, that is, one service can only correspond to one
PW.
3-2
Function Description
MPLS-TP OAM Supports layered OAM functions: PW OAM, LSP OAM, and Section OAM
function
4-1
4.2 MPLS
ZXCTN 6120S can implement seamless convergence of IP and L2 through MPLS.
Meanwhile, MPLS technology provides better solutions to the application of traffic
engineering and VPN.
The MPLS architecture of ZXCTN 6120S complies with Multiprotocol Label Switching
Architecture (RFC 3031).
Function Description
LDP Protocol l Support the following distribution and management mode of LDP
labels: Downstream Unsolicited (DU) mode + Independent label
control mode + Liberal label retention mode
l Bind FEC and label by LDP, and announce the information to the
neighbor LSR to establish the LSP.
l Support MD5 encryption authentication, which complies with
RFC-3036 requirements.
l Use the LDP GR function to solve the problem of label data
forwarding which is caused by the restart of LSR control layer
(especially cause by the restart of LDP control layer).
4-2
VPWS
Virtual Private Wire Service (VPWS) is used to provide point-to-point VPN service
transmission. PE devices in the MPLS network receive user services from the CE
devices. After being encapsulated by the PE devices, the user services are transparently
transmitted in the MPLS network and then finally transmitted to the destination.
For a typical network architecture of the VPWS, see Figure 4-1.
VPLS
Virtual Private LAN Service (VPLS) is a multipoint-to-multipoint layer-2 VPN technology
that integrates the superiority of the Ethernet technology and MPLS technology. VPLS
simulates the traditional Local Area Network (LAN) function to connect multiple separate
Ethernet sites in regions through the operator's MPLS backbone network, so that these
sites appear to operate in the same LAN.
For a typical network architecture of VPLS, see Figure 4-2.
4-3
H-VPLS
The VPLS mode requires full connections between PEs. Therefore, if the VPLS network
is in a large scale, the number of PWs is huge, and the PW signaling overhead is great,
so the network management and expansion will be complex.
The H-VPLS divides the PEs into UPEs and NPEs, see Figure 4-3.
4-4
l As an Multi-Tenant Unit (MTU) for the users to access the VPN, a UPE is used to
connect the CEs and the service provider's network.
l The NPEs are located at the core domain edge of the VPLS network to provide trans-
parent transmission of user packets over the core network.
The UPEs do not need to establish full connections between all NPEs. It only needs
to establish full connections between NPEs. The H-VPLS hierarchically decreases the
number of PWs and the burden of PW signaling.
MS-PW
Multi-Segment Pseudo-Wire (MS-PW) refers to multiple segment pseudo wires between
the UPEs. For the application scenario of MS-PW, see Figure 4-4.
4-5
PW Status Notification
If the LDP protocol is used as PW signaling and the Attachment Circuit (AC) is down, LDP
signaling announces the information to the neighbors to remove PW labels. If the AC is
restored, the LDP renegotiates to create PW labels. When the AC oscillates, PW labels
may constantly be deleted and created, which affects network stability.
To protect PW labels from being constantly deleted and created because of the oscillation
of the access link, the ZXCTN 6120S prevents the LDP PW labels from being affected
by the AC. In other words, the status of the AC is not used as the criterion for creating or
deleting LDP PW labels. On the basis of Martini, dynamic PWs add the optional status
parameters in mapping messages and supports notification messages. If the network
is unstable, notification messages can be used to reduce the number of exchanged
messages.
4-6
is used to forward VPN user data from one VPN site to another. The VPN implemented
by this technology is called BGP/MPLS VPN, which is an L3VPN mode for VPN devices.
For the basic network architecture of BGP/MPLS L3VPN, see Figure 4-5.
A routing protocol is used between CEs and PEs for route interaction. The routing
protocol can be configured dynamically (based on RFC 4364, including RIP, BGP,
or OSPF) or statically. On PEs, each attachment circuit between a CE and a PE is
associated with one or multiple Virtual Route Forwarding (VRF) tables. Between PEs,
the route information belonging to the same MPLS VPN is interacted through the BGP
protocol for VRF synchronization. The SCN network or MPLS tunnels are used between
PEs for forwarding routes. For the VPN network information that the operator router P
does not need to know, this transparent mode can effectively reduce the load of route P
and improve network expandability and service flexibility.
Through the route interaction between PEs and between PEs and CEs, client routers and
PE devices can acquire network topology information in the same VPN, so that client
services can be interacted in different sites.
VRF
The ZXCTN 6120S supports VRF forwarding instances and supports VRF label per route
mode. MPLS L3VPN can be implemented on PE devices. The PEs establish a VRF table
for each VPN. All the clients and sites belonging to one VPN can access the corresponding
VRF table of this VPN only, so that the routing and forwarding of different clients can be
isolated.
l Based on VLAN
4-7
Different VLAN subinterfaces of the same physical interface can connect different user
services.
l Based on physical Ethernet port
Different physical Ethernet ports can connect different user services.
L3VPN Tunnels
The ZXCTN 6120S can use the following modes to pre-create the LSP tunnel between
PEs.
l Use RSVP-TE as the signalling protocol and supports traffic engineering.
l Use LDP as the signalling protocol and doesn’t support traffic engineering.
l Use the static tunnels configured manually on the management platform.
4-8
l Option B
Option B is also called single hop MP-EBGP cross domain, see Figure 4-7. VPN
information is transported and the LSP tunnel is established by MPLS/BGP in AS
domains. VPN information is transported and the LSP tunnel is established by single
hop MP-EBGP protocol between AS domians.
4-9
L3VPN FRR
The ZXCTN 6120S supports the VPN FRR function, which can make the fault recovery
time of end-to-end service have nothing with the network scale of private routing. The
L3VPN FRR function is easy to deployment and reliable. For a typical network architecture
of L3VPN FRR, see Figure 4-8.
In normal cases, CE1 accesses CE2 through path 1. If PE2 fails, CE1 accesses CE2
through converged path 2.
4.3 L2
Function Description
Basic Ethernet The ZXCTN 6120S supports the following basic Ethernet functions.
functions l Supports the full-duplex working mode of interfaces.
l Supports MAC address learning, MAC address aging, and MAC address
filtering.
l Supports 1000Mbps electrical interfaces and the 10/100Mbps automatic
negotiation function.
l Supports setting the port rate, full-duplex mode, traffic control, and MTU.
l Supports the L2 switching function.
l Supports the interface traffic control function of the IEEE 802.3x Pause frame
mechanism based on full-duplex working mode.
l Supports the ingress and egress mirroring functions.
l Supports the storm suppression function of broadcast/multicast/unknown
unicast packets.
4-10
Function Description
Link The ZXCTN 6120S supports the following link aggregation functions.
aggregation l Supports the link aggregation in manual load balance mode
l Supports the link aggregation protocol (LACP) complying with the IEEE 802.3ad.
l Supports the binding function of FE and GE interfaces.
l Supports the load balance function based on the MAC and IP addresses.
l Supports the cross service board link aggregation.
Muticast The ZXCTN 6120S supports the following IGMP proxy/snooping multicast functions.
l Supports the IGMPv2 protocol.
l Supports configuring the static multicast table.
l Supports creating the multicast table based on IGMP proxy/snooping and then
forwarding multicast services based on the service interfaces in the multicast
table.
l If IGMP proxy/snooping is enabled, the ZXCTN 6120S forwards the created
multicast table based on the designated interface in the table and discards or
broadcasts unknown multicast as required.
l Supports dynamically creating, deleting, and maintaining the multicast table
based on VPLS/E-LAN services, and querying multicast.
4-11
4.4 L3
Function Description
Basic functions The ZXCTN 6120S supports the following basic L3 functions.
l Supports the following L3 interface.
Routing protocols The ZXCTN 6120S supports the following routing protocols.
l The OSPF protocol
l The BGP protocol
l The IS-IS protocol
As shown in Figure 4-9, the MPLS-TP divides the OAM into five layers, namely access
layer, service layer, PW layer, tunnel layer, and segment layer. The PW OAM, tunnel OAM,
and segment OAM belong to the network.
l PW-layer OAM (PW OAM): monitors the connections and performance of various
services and provides good conditions for end-to-end service management.
4-12
l Tunnel-layer OAM (Tunnel OAM): monitors and protects the LSP layer, and avoids
performance degradation caused by increasing number of OAM services.
l Section-layer OAM (Section OAM): provides ring network protection and saves
bandwidth.
4-13
Items Functions
LSP Trace LSP Trace refers to sending a series of MPLS Echo request packets at the starting
point of LSP. TTLs of these packets are one to a certain value. Each node on LSP
respectively receives request packet and returns reply packet. Thus, LSP starting
point can collect the information on LSP path
4-14
Items Functions
PW Ping PW Ping is similar to IP Ping. Realized by extending LSP Ping, PW Ping is a tool
which is used to manually detect virtual circuits connection status. PW Ping defined a
series of information to test the PW connectivity between PEs.
PW Trace PW Trace is similar to LSP Trace, but their layers are not same.
l LSP Trace uses LSP to forward MPLS Echo request, while PW Trace uses PW to
forward MPLS Echo request.
l PW Trace is classified into single section PW Trace and multi-section PW Trace.
VRF Ping / VRF Trace is similar to IP Ping/Trace, and is used to detect the reachability of L3
VRF Trace VPN private route.
The EFM supported by ZXCTN 6120S is an OAM function based on IEEE 802.3ah. For
the detailed function descriptions, refer to Table 4-5.
Function Description
Remote discovery Discoveries peer end of the OAM automatically through automatic
negotiation at both ends of the OAM.
Lnk monitoring Both ends of the OAM exchange data messages periodically, to monitor
the link connectivity in real time.
Lopback Controls the forwarding of data messages by enabling the remote loopback
function.
The CFM function supported by the ZXCTN 6120S is the OAM function based on ITU-T
Y.1731/IEEE 802.1ag, which supports two layers of Y.1731OAM/802.1ag nesting. For the
detailed function descriptions, refer to Table 4-6 and Table 4-7.
4-15
Function Description
Ethernet Continuity As an active OAM function, ETH-CC is used to check the connectivity
Check (ETH-CC) between two ME Groups (MEGs), or between any two MEG End Points
(MEPs) in an MEG.
ETH-CC provides the following features:
l Continuity loss check
l Error combination check
l Abnormal MEG End Point (MEP) check
l Abnormal period check
Ethernet Loopback ETH-LB is used to check the connectivity between the MEP and the MIP, or
(ETH-LB) detection between two MEPs.
ETH-LB can be classified into unicast ETH-LB and multicast ETH-LB.
l As an OAM function on demand, unicast ETH-LB is used to verify the
bidirectional connectivity between the MEP and MIP. If bidirectional
serve or service interruption diagnosis test is implemented between two
MEPs, unicast ETH-LB is also used to detect bandwidth or bit error ratio.
l As an OAM function on demand, multicast ETH-LB is used to verify the
bidirectional connectivity between two peer MEPs.
Ethernet Link Tracing As an OAM function on demand, ETH-LT is used to locate errors and confirm
(ETH-LT) neighbor relations.
Ethernet Alarm If the MEP detects faults at server layer, ETH-AIS is used to suppress all
Indication Signal the associated alarms of the peer MEP, no matter whether there is any
(ETH-AIS) connectivity between the MEP and its peer MEP.
Ethernet Remote ETH-RDI is an OAM function for exchanging faults between one MEP and its
Defect Indication peer MEP. It is used in unicast error management and remote performance
(ETH-RDI) monitoring.
Ethernet Lock signal ETH-LCK is used to send the server-layer EMP administrative lock notification
(ETH-LCK) and data service flow interruption notification to the MEP, so that the MEP
can distinguish normal faults from the server-layer EMP administrative lock.
Ethernet Test signal ETH-Test is used in the on-demand unicast service period, or in the diagnosis
(ETH-Test) test of service interruption, such as bandwidth flow verification, frame loss
verification, and bit error verification.
Ethernet frame Based on implementation modes, ETH-LM can be classified into dual-end
Loss Measurement ETH-LM and single-end ETH-LM.
(ETH-LM) l Dual-end ETH-LM is an active OAM function used for error management.
l Single-end ETH-LM is an OAM function on demand.
4-16
Function Description
Ethernet frame As an OAM function on demand, it is used to measure the frame delay and
Delay Measurement its variation in the network. Based on implementation modes, ETH-DM can
(ETH-DM/ETH-DVM) be classified into Unidirectional ETH-DM and Bidirectional ETH-DM.
l Unidirectional ETH-DM is used to measure the unidirectional frame
delay and its variation.
l Bidirectional ETH-DM is used to measure the bidirectional frame delay
and its variation
Function Description
Loopback (LB) As an OAM function on demand, it sends a unicast request to the destination
MP (MEP or MIP), and receives response messages from the destination MP,
in order to confirm the bidirectional connectivity between two maintenance
points.
Link Tracing (LT) As an OAM function on demand, it sends a multicast OAM messages, and
forwards the message along the route, in order to locate the fault.
Remote Defect Used to detect remote defects and send the CV frames with RDI.
Indication (RDI)
4-17
Function Description
CFM MIB Supports command line configuration, displays CFM status, and supports
MIB Get mode.
Traffic classification Traffic classification is to classify the data packets into several
priorities or types. The equipment provides differentiated services in
accordance with the service types.
The ZXCTN 6120S supports port, L2, L3, L4 packet header
content-based classification, including physical interface, source IP
address, destination IP address, MAC address, 802.1p, source IP,
sink IP address, IP protocol, port number of application program, and
combination of these classification modes.
Traffic monitoring Traffic monitoring is to limit the bandwidth of a service flow when it
enters a network, preventing it from exceeding the specified bandwidth
and causing impact to other service flows.
The ZXCTN 6120S supports the following traffic monitoring functions:
l Supports traffic monitoring based on input port or output port.
l Adopts Access Control List (ACL) to implement service traffic
access control.
l Implements Committed Information Rate (CIR), Committed Burst
Size (CBS), Excess Information Rate (EIR) and Excess Burst
Size (EBS) based on flow.
l Supports dual token bucket.
l Supports drop, color-mark and other policy actions for contracted
rate-beyond traffic.
l Supports ingress and egress traffic monitoring.
4-18
Traffic shaping Typical function of traffic shaping is to limit the traffic and the packet
burst in a network, making the packet sent externally in an even rate.
The ZXCTN 6120S supports the following traffic shaping functions:
l Port-based traffic shaping function
l Priority-based traffic shaping function
Congestion management Congestion avoidance is mainly used to implement service cache and
dropping, drop a few packets selectively when congestion occurs on
network node, which can relieve network congestion.
The ZXCTN 6120S supports the following congestion avoidance
function:
l Supports the Weighted Random Early Detection (WRED) drop
policy.
l Supports setting the upper-limit drop threshold, lower-limit drop
threshold, and drop ratio.
l Supports the tail drop caching policy.
Queue scheduling The ZXCTN 6120S uses mixed and flexible queue scheduling based
on different types of services. Queue scheduling modes include:
l Weighted Round Robin (WRR)
l Deficit Weighted Round Robin (DWRR) function.
l Strict Priority (SP)
l SP+WRR
l Each interface supports 8 levels of queue scheduling.
l Each queue supports maximum/minimum bandwidth
management.
Hierarchical QoS model If network congestion occurs, the data traffic with higher level has higher
priority during queue scheduling and resource occupation than the data
traffic with lower level.
DS domain creation The ZXCTN 6120S supports creating DS domains. It can create DS
domains on interfaces, PWs, and tunnels, and then set PHB groups
supported by the corresponding DS domain. Each DS domain supports
up to 8 PHBs.
4-19
NNI side, MPLS priority If the network passes through L2 Ethernet network, L2 Ethernet network
maps to VLAN priority provides transparent L2 connection for gateway device by Q-in-Q
encapsulation.
In order to guarantee the QoS end to end, the MPLS priority of gateway
device should be mapped to the priority of VLAN, thus, L2 Ethernet
network can implement differential service. The QoS of service can
be guaranteed.
The ZXCTN 6120S supports copying the MPLS EXP priority to VLAN
priority at NNI side.
Client service QoS and The ZXCTN 6120S supports the mapping between the client service
IPHB, OPHB QoS, Incoming PHB (IPHB) and Outgoing PHB (OPHB).
LSP QoS and IPHB The ZXCTN 6120S supports configuring the mapping between the LSP
QoS field (EXP) and IPHB on the middle node of the tunnel.
Mapping from OPHB to The ZXCTN 6120S supports configuring the mapping from OPHB to
tunnel-layer QoS, PW tunnel, PW, Section QoS at the ingress point and the middle point of
QoS, section QoS the LSP.
Reserved bandwidth For the repeated PW/LSP on the same path, the ZXCTN 6120S does
share not perform the CAC calculation repeatedly. It only calculates the CIR
bandwidth once.
4-20
Time Function
The ZXCTN 6120S uses the Ethernet interface to transfer time, which meets the
requirements of the IEEE 1588 V2 function.
The ZXCTN 6120S supports the following time transmission function:
l Supports setting the clock node type.
à Ordinary clock
à Border clock
à End-to-End (E2E) transparent transmission clock
à Peer-to-Peer (P2P) transparent transmission clock
à Ordinary clock + E2E transparent transmission clock
à Ordinary clock +P2P transparent transmission clock
l Supports setting the Precision Time Protocol (PTP) port mode.
à Master port
à Slave port
à Passive port
l Supports the switching of time format.
l Supports the time synchronization management function.
l Supports the TS protection switchover function.
l Supports the delay compensation function.
4-21
Only one port supports the IEEE 1588 V2 protocol. Users need to recover the clock.
Ordinary clock can work as a time source, that is master clock equipment, or the slave
equipment which is synchronized by other clock equipment.
l Border Clock (BC)
Multiple ports support IEEE 1588 V2 protocol. Users need to recover the clock. It can
work as an master/slave clock equipment.
l Transparent Clock (TC)
The node does not run IEEE 1588 V2 protocol but transparently transmits the clock
signal. Clock recovery is not needed. It needs to modify timestamp. It fills the time
at which the node processes one packet in the modification position when forwarding
time packet.
à E2E TC
4-22
4-23
4-24
Access Security
The ZXCTN 6120S provides the following functions to ensure the access security:
4-25
Function Description
ARP anti-attacking -
Protocol Security
The ZXCTN 6120S provides the following functions to ensure the protocol security:
Function Description
Preventing DoS attacks If the number exceeds the set alarm value, ZXCTN 6120S will give out
an alarm, shield the IP, and throw away all the packets from the IP till
the alarm is released. Thus to resist the DoS attacks.
Preventing BPDU attacks If ZXCTN 6120S detects abnormal traffic in BPDU data packets, it will
filter these data packets automatically to prevent BPDU attacks.
Preventing ARP attacks ZXCTN 6120S monitors the number of ARP messages received by the
same physical interface in a time. If the number exceeds the set alarm
value, ZXCTN 6120S will give out an alarm, and stops processing the
packets till the alarm is released. Thus to resist the ARP attacks.
Preventing LAND attacks The ZXCTN 6120S can filter SYN packets with attack purpose to
prevent the LAND attack and protect the server host.
Preventing SMURF attacks The ZXCTN 6120S use the CAR to restrict the traffic of ICMP. Thus to
prevent SMURF attacks, and to protect the server machine.
4-26
Function Description
Preventing SYN FLOOD The ZXCTN 6120Sprevents SYN FLOOD attacks by limiting SYN
attacks timeout time and connection times through configuration.
Preventing PING FLOOD If the ZXCTN 6120S detects the PING FLOOD attack, the equipment
attacks filters ICMP packets with attack purpose to prevent the PING FLOOD
attack.
Preventing Teardrop ZXCTN 6120S can filter data packets with overlapped fragment offset to
attacks prevent the Teardrop attack.
Preventing Ping of Death If the ZXCTN 6120S detects the Ping of Death attack, the equipment
attacks filters PING packets with attack purpose automatically to prevent the
attack.
CPU security protection The ZXCTN 6120S judges if it is attacked by the CPU uploading rate
of protocol packets. It initiates corresponding protection measures
if attacked.
Command authority graded The ZXCTN 6120S supports 16 levels of command authorities. Different
protection authority levels are set for different login users. The lower the authority
level is, the fewer the available commands are; the higher the authority
level is, the more the available commands are. The administrator (the
highest level, being 15) can set different commands with different
authority levels, which achieves customized configuration of command
authorities and provides great ensurance of equipment security.
Preventing abnormal If the ZXCTN 6120S detects a large number of abnormal packets and
packets and error packets error packets, the equipment filters these packets to prevent the attack
on the target system.
Function Description
NE login management Only the user with legal account and password can log into
the NE.
NE user switching At one client end, only one user can operate the NE at one
time. To operate the NE by a different user, it needs to
switch the user to ensure the data uniqueness.
4-27
Function Description
Forcing the NE user to log out To avoid the error caused by the simultaneous configuration
of multiple NE users or prevent other users from illegally
log in the NE, the NE user can force the NE user of a lower
level to exit the NE.
Querying the login user on the NE Including the login IP address, login time and login type of
the user.
Locking NE user If the wrong password input times of user login reaches the
preset value, the user's account will be locked.
Setting the user blacklist Users in the blacklist are forbidden to log into the system.
4-28
Over-Current Protection
ZXCTN 6120S supports the function of board over-current protection. As for over-current
protection function, it contains board over-current protection and device over-current
protection.
For restoration on AC/power loss, main board is restored firstly, service cards access
corresponding configuration information from storage on main board and thus services,
NM and clock get restored.
5-1
Table 5-1 Technology Comparisons Between 1:1 Protection and 1+1 Protection
1:1 protection Less than 50 ms Protection The APS function End-to-end, same
bandwidth is needs to be source and source
available enabled. destination
1:1 Protection
In the 1:1 path protection mode, the protection path is for the dedicated usage of each work
path. The protected work service is transmitted by the work path or the protection path.
The service is transmitted to the destination end of the protection domain through the work
path. The destination end selects to receive the service on the work path according to the
preset constraint rules.
The 1:1 path protection is in bidirectional switching. That is, both the affected and
unaffected connection ways are switched to the protection path. For bidirectional
switching, the Automatic Protection Switching (APS) protocol needs to be enabled to
coordinate both ends of the service path. To avoid the single-point failure, routes should
go through the work path and the protection path separately.
For the schematic diagram of 1:1 path protection, see Figure 5-1. In normal cases, the
service is transmitted through the working channel from node A to node Z in normal status.
There is not service on the protection channel. If the working channel is faulty, the service
is switched to the protection channel for transmission on node A, node Z receives the
service on the protection channel.
5-2
1+1 Protection
In the 1+1 path protection mode, the protection path is for the dedicated usage of each
work path. The work path and the protection path are bridged at the source end of the
protection domain. The service is transmitted to the destination end of the protection
domain through the work path and the protection path simultaneously. The destination
end selects to receive the service on the work path or the protection path according to the
preset constraint rules.
The 1+1 path protection is in unidirectional switching. That is, only the affected connection
way is switched to the protection path. To avoid the single-point failure, routes should go
through the work path and the protection path separately.
For the schematic diagram of 1+1 path protection, see Figure 5-2. In normal cases, the
service is transmitted through the working channel and the protection channel from node
A to node Z in normal status. Node Z selects to receive the service on the work channel
or the protection channel according to the preset constraint rules. If the working channel
is faulty, Node Z receives the service on the protection channel.
5-3
5-4
If the node on the network detects network failure, the fault adjacent node sends the
switching request to adjacent nodes through the APS protocol.
If a node detects the fails or receives the switching request, the service transmitted to the
failure node will be switched to another direction (far away from the failure node). If the
network failure or the APS protocol request disappears, the service returns to the previous
path.
5-5
is, two rings are interconnected through two nodes, so that the span-loop service can be
transferred by an intersectant node in case of failure in the other intersectant node.
For a typical network architecture of double-loop dual-node protection, see Figure
5-5. The ZXCTN 6120S supports A-B, A-C, B-D, E-C, E-F, F-D single-point fault or
two-point fault double-loop dual-node protection. C-D loop only supports single-point
fault double-loop dual-node protection, in which the protection mode is Wrapping and the
protection switching performance is 50 ms.
5.2.5 PW Protection
PW Dual-homing Protection
ZXCTN 6120S supports PW dual-homing protection and MS-PW protection.
Dual-homing protection is to protect the service transmitted over the work pseudo wire
(PW) by protecting the PW. In case of the work PW fault, peer-end single-point failure or
user side link fault, the service will be switched to the protection PW.
ZXCTN 6120S supports two dual-homing protection modes:
l 1+1 dual-homing protection
l 1:1 dual-homing protection
For a typical network architecture of dual-homing protection, see Figure 5-6. The PW
from P1 to P2 is the work PW, the PW from P1 to P3 is the protection PW. P2, P3 and
RNC set up the Multi-Chassis Link Aggregation Group (MC-LAG) protection. Normally, the
service of the base station (BTS) and RNC is transmitted through the work PW. In case
of P2 failure or the fault in the link between P2 and RNC, P1 will receive the CSF alarm
indication to trigger protection switching, and the service is then switched from the work
PW to the protection PW.
5-6
MS-PW Protection
MS-PW protection separates the management area of tunnel, which avoids the inter
communication between different routing areas.
For a typical network architecture of MS-PW protection, see Figure 5-7. There are multi
PWs between UPE and UPE. SPE switches the labels during transferring PW. That is,
SPE connects the single PW of two sides and switch the PW label.
If the PW100 fails, the service will be switched to PW300. SPE switches the PW label.
Then the service will be carried by PW400 and sent to the user side.
5-7
1+1 Protection
For the schematic diagram of MPLS 1+1 protection, see Figure 5-9. In normal cases, the
service is transmitted through the working LSP and the protection LSP from the source
end to the destination end and the destination end selects to receive the service on the
work channel or the protection LSP based on the preset constraint rules. If the working
LSP is faulty, the destination end receives the service on the protection LSP.
5-8
FRR protection is deployed in the network with high requirement for reliability. If the
network partially fails, FRR can fast switch to Bypass Tunnel. Thus, there is little impact
on the data services.
ZXCTN 6120S supports IP FRR, LDP FRR, PW FRR, VPN FRR, and RSVP-TE FRR
protection. IP FRR supports OSPF and IS-IS protocol, LDP FRR supports LDP protocol,
RSVP-TE FRR is based on RSVP-TE.
IP FRR is a most commonly used IP protection mode. The slave layer-3 port
protects the master layer-3 port. The detection mechanism of IP FRR is Bidirectional
Forwarding Detection (BFD), when BFD detects the fault, triggers the switch at
lsyer-3 port. IP FRR is deployed at the core layer.
5-9
For the schematic diagram of IP FRR protection, see Figure 5-10. If interface 12/8 of
PE2 is faulty, the system switches to standby IP FRR (PE2→PE3→CE2).
l LDP FRR
LDP FRR is based on LDP protocol. After the LDP protocol is configured, an FRR
table will be formed with MPLS out-label of master and slave. LDP FRR is performed
based on this FRR table. LDP FRR is deployed at the P device in the core network.
The ZXCTN 6120S supports FRR link protection and node protection. For the schematic
diagrams of FRR link protection and node protection, see Figure 5-11 and Figure 5-12
respectively.
5-10
5-11
PW FRR
PW FRR is a protection mode with same source and different destinations.
PW FRR is used to protect node or link by BFD mechanism.
Normally, PW FRR works together with tunnel protection. The tunnel protection is triggered
at first. If the tunnel protection is abnormal, then PW FRR starts to work. For the schematic
diagram of PW FRR protection, see Figure 5-13. The PW from P1 to P2 is the working
PW, PW from P1 to P3 is protection PW. Normally, the service between base station and
RNC is transported by the working PW. If the working PW or P2 is abnormal, P1 receives
the message which announces the P2 is disabled. Then the protection is triggered, the
service is switched from the working PW to the protection PW.
5-12
VPN FRR
Based on VPN routine fast switch technology, VPN FRR sets working and protection
transferring items on terminal PE in advance. The transferring items point to the working
PE and protection PE. Together with BFD, before finishing the VPN routine convergence,
switch the VPN traffic to the protection path. By this way , solve the problems about
recovering time of faulty node and the number of the routing carried by the faulty node.
Save the service interruption time of faulty node.
For the schematic diagram of VPN FRR protection, see Figure 5-14. If PE1 connecting
to CE1 transfers the message, PE1 can add the working routine message of PE2 in
the transferring item, meanwhile, it adds the protection routine message of PE3 in the
transferring item. If the PE2 is faulty, after PE1 gets the message that the working LSP
is disable by BFD check mechanism, PE1 will transfer the service through the protection
touting in the transferring item. So Perform the fast convergence when the PE2 is faulty.
5-13
RSVP-TE FRR
RSVP-TE FRR can only protect single node or single link by bypass mode. Multi Bypass
tunnel protect the working tunnel. A is the head node of the working tunnel, B and C
are head nodes of Bypass tunnel. Bypass1 protects the link between B and C, Bypass2
protects the link between C and D. For the schematic diagram of RSVP-TE FRR protection,
see Figure 5-15.
5-14
RSVP-TE hot-standby protection is to configure two LSPs for a service. Once the working
LSP is faulty, the service is switched to the protection LSP, that is RSVP-TE Hot-Standby.
For the schematic diagram of RSVP-TE hot-standby protection, see Figure 5-17
5-15
The working LSP and protection LSP are configured between PE1 and PE2. The LSP
BFD detection function is configured on the working LSP. In general, the service between
PE1 and PE2 is carried by the working LSP. If the working LSP is faulty, the BFD detects
the failure and sends alarm indication to PE1. PE1 triggers the switch after receiving the
alarm. Then the service is switched to the protection LSP.
Note:
During application, in order to guarantee the BFD can detect the fault as soon as possible,
the bidirectional routing of BFD between PE1 and PE2 should be consistent.
5-16
If some member link in the aggregation group is faultyy, the service signals on the faulty
link are loaded by other normal links to protect services, see Figure 5-19.
5.2.11 STP
The ZXCTN 6120S supports various STP protocols to avoid network looping, including
Multiple Spanning Tree Protocol (MSTP) defined by IEEE802.1s, Single Spanning Tree
Protocol (SSTP) defined by IEEE802.1d, and Rapid Spanning Tree Protocol (RSTP)
defined by IEEE802.1w.
The STP protocol runs on the interface of the network switch. It prescribes that the switch
exchanges configuration information with other switches in the fixed time interval. The
network topology structure can be modified by modifying the interface status of switches
(forwarding or blocked) to optimize the data transmission path and avoid redundant paths
caused by network looping. If the network topology changes, the status of the original
redundant switch interface can quickly migrate.
5-17
5-18
NMS interface ZXCTN 6120S provides one Qx interface for managing the equipment remotely.
The Qx interface is located on the system service main board. It uses the Ethernet
electrical interface of RJ45 type. The interface rate is self-adaptive.
6-1
Interfaces Descriptions
Local ZXCTN 6120S provides one external Local Craft Terminal (LCT) interface for the
Maintenance commissioning and maintenance of the local NEs.
Interface LCT interface is located on the system service main board. It uses the Ethernet
interface. The type of the interface is RJ45, and the rate is self-adaptive.
Alarm The ALM interface of the ZXCTN 6120S is located on the system service main
Interface board. It uses the Ethernet electrical interface of RJ45 type.
Each channel of alarm signals can be configured to alarm input signals, alarm output
signals, or alarm cascade input signals.
GPS Time Both the service main board and GPCB clock board provide two Global Positioning
Interface/BITS System (GPS) time interfaces/BITS interfaces.
Interface The GPS time interface/BITS interface of the service main board uses the Ethernet
electrical interface of RJ45 type.
The GPS time interface/BITS interface of the ZXCTN 6120S has the following
functions:
l Provides one BITS clock output (2.048 Mbit/s or 2.048 MHz) interface.
l Provides one BITS clock input (2.048 M bit/s or 2.048 MHz) interface.
l Provides the input of 1-path phase synchronization information and absolute
time for receiving time synchronization information.
l Provides the output of 1-path phase synchronization information and absolute
time for sending time synchronization information.
GPS Time Both the service main board and GPCB clock board provide GPS time interface.
Interface It uses the Ethernet electrical interface of RJ45 type.
The GPS time interface of the ZXCTN 6120S has the following functions:
l Provides 1-path BITS clock output (2.048 Mbit/s or 2.048 MHz) interface.
l Provides 1-channel BITS clock input (2.048 Mbit/s or 2.048 MHz) interface.
l Provides the input of 1-channel phase synchronization information and absolute
time for receiving time synchronization information.
l Provides the output of 1-channel phase synchronization information and
absolute time for sending time synchronization information.
1. The service main board supports two channels of GPS time signals. One is provided by the GPS time
interface (silkscreened as GPS), the other one is provided by the GPS time interface/BITS interface
(silkscreened as GPS/BITS).
6-2
7-1
For a typical application of EVPL service networking, see Figure 7-2. Services FE1 and
FE2 between users CE1 and CE2 are accessed through UNI ports of PE nodes NE1 and
NE10. FE1 and FE2 are isolated through VLAN's, allocated with exclusively used CIPs,
VIPs and PWs, and transmitted through tunnel between NE2, NE4, NE5, NE6, NE7 and
NE9.
7-2
For a typical application of EPLAN service networking, see Figure 7-3. Exclusive UNI ports
are used on PE nodes NE1, NE2 and NE11 for FE1 service among users CE1, CE2 and
CE3. 1 CIP and 2 VIPs are enabled on each PE node. PW and tunnel are exclusively used
in transmission. FE2 service among users CE1, CE2 and CE3 is similar to FE1 service
except for different UNI port, CIP, VIP, PW and tunnel.
7-3
For a typical application of EVPLAN service networking, see Figure 7-4. Services FE1
and FE2 between users CE1, CE2 and CE3 are accessed through UNI ports of PE nodes
NE1, NE2 and NE11. FE1 and FE2 are isolated through VLAN's, allocated with exclusively
7-4
used CIPs, VIPs and PWs, and transmitted through the same tunnel, thus implementing
isolation of services FE1 and FE2.
Each EPTREE service can contain multiple CIPs and VIPs on source node and sink node.
EPVLAN services are carried on private tunnels. Different services cannot share UNI
7-5
interface, CIP, VIP, PW and tunnel. L2 switching function and MAC learning capability are
not needed for point-to-point transmission.
For a typical network architecture of an EPTREE service, see Figure 7-5. Services FE
of users CE1 and CE2 converge on core switch NE5 through network. On convergence
node NE5, CIP port is the root node and ports VIP1 and VIP2 are leaf nodes. On NE1 and
NE10, CIP port is the root node and VIP port is leaf node.
7-6
and CE2 converge on UNI port of NE5. On convergence node NE5, CIP1, and CIP2 of
NE5 are used as root node and VIP1, VIP2, VIP3 and VIP4 are used as leaf nodes. On
NE1 and NE10, ports CIP1 and CIP2 are used as root node and ports VIP1 and VIP2 are
used as leaf nodes. Services are isolated through VLAN tags on UNI port.
7-7
For a typical network architecture of a TDM service, see Figure 7-7. Company 1 and
company 2 send voice services and mobile services to each other through NE2 and NE3.
User services are converged on NE4 and then sent to the convergence layer.
7-8
The networking application of ZXCTN 6120S in mobile Backhaul has the following features:
l Simulates various 2G/3G/LTE peer-to-peer services in Backhaul network through
PWE3.
l Supports efficient statistical multiplexing, meets the requirements of long-term
co-existence to guarantee the smooth evolution of the network.
l Provides carrier-level network protection and end-to end hierarchical OAM to
guarantee the high reliability of the Backhual service.
l Meets the various transmission requirements such as jitter and delay of different levels
of Backhaul services though service classification, priority marking, queue scheduling,
and peer-to-peer QoS deployment.
l Supports synchronous Ethernet (G.8261) and IEEE 1588V2 clock synchronization
technology, and meets the peer-to-peer lock synchronization requirement of Backhaul
network.
7-9
the access layer to meet the requirements of the downstream service traffic of the mobile
base station.
Application Scheme
For a typical application in the LTE network, see Figure 7-9.
Application Features
Application at LTE network stage has the following features:
l It meets the characteristics of flat LTE network in logic, adapts to LTE service bearing,
and meanwhile is completely compatible with 3G services.
l It implements function distribution for LTE service network and P2P characteristics,
and supports L3 function and flexible scheduling of X2 and S1.
l It supports L1/L2/L3 function, meets the demand of carrying full services, and
implements Fixed Mobile Convergence (FMC).
l The application provides SDH network reliability, supports point-to-point OAM and
protection, shows high QoS/SLA support, and reduces OPEX.
l It supports to synchronous Ethernet (G.8261) and IEEE 1588 V2 clock synchronization
technology.
l It owns special signaling control plane, which make configuration of network and OAM
more flexible.
7-10
Item Performance
Specification
QinQ 32K
VLAN quantity 4K
L3 interface table 2K
8-1
Item Performance
Specification
DS template quantity 16
8-2
Item Performance
Specification
Parameters Weight 5 kg
Service slot 2
Noise <55 dB
8-3
Note:
Cabinet is connected to the copper ground busbar in the equipment room through the
protection ground and thus maintains good electronic characteristics. Subrack is firmly
fastened to the cabinet back column for grounding.
8-4
Figure 8-1 Electric Power Line and Grounding Cable Diagram (Common
Bonding Network)
à If the user equipment room only provides one grounding busbar, the working
ground, protection ground and the chassis shell of ZXCTN 6120S are all
connected to the grounding copper busbar. Figure 8-2 uses the connection with
DC power as an example.
Figure 8-2 Electric Power Line and Grounding Cable Diagram (Common
Bonding Network)
Note:
If the ZXCTN 6120S is installed in the cabinet, the power cable is connected to the
output port of the power supply of the cabinet, the protection cable is connected to the
protection grounding busbar.
8-5
l If the user equipment room uses independent grounding, the ground resistances
should meet the requirements listed in Table 8-4.
The voltage between protection grounding terminals and working ground terminals
should be smaller than 50 mV.
If independent grounding is used in the user equipment room, the working ground
of the ZXCTN 6120S equipment is connected to the DC working ground, and the
protection ground is connected to the safety protection ground, see Figure 8-3.
Figure 8-3 Electric Power Line and Grounding Cable Diagram (Independent
Grounding)
l Copper busbar with cross section area no less than 120 mm2 shall be used as
grounding busbar or grounding bar for grounding. Galvanized flat steel with the
dimension not less than 40 mm×4 mm can also be used.
l Be sure to use copper lugs, bolts and spring washers to fasten the connections
between the device grounding cable and the grounding busbar or grounding bar.
One bolt can only be used to connect one grounding cable. Determine the dimension
of grounding busbar and the number of screws according to the number of grounding
cables of devices in computer room.
8-6
Note:
If the equipment room provides working ground and protective earth separately, the
working ground and protective earth of the device shall be connected to corresponding
grounding copper busbar. If the equipment room provides only one grounding copper
busbar, the working ground and protective earth of the device can be jointed for grounding.
The ground resistance shall meet the above requirements.
8-7
Item Standard
Radiated Susceptibility (RS) Immunity Comply with IEC 61000-4-3, GB/T 17626.3
Electrical DC Power Port Immunity (Direct Comply with IEC 61000-4-4, GB/T 17626.4.
Fast Coupling)
Transient
AC Power Port Immunity (Direct Comply with IEC 61000-4-4, GB/T 17626.4.
(EFT)
Coupling)
Immunity
Signal Cable Port and Control Cable Comply with IEC 61000-4-4, GB/T 17626.4.
Port Immunity (With Capacitive
Coupling Clamp)
8-8
Item Standard
Voltage Dip and Short Interruption Immunity This item only applicable to DC power supply,
comply with IEC 61000-4-11, GB/T 17626.11.
Item Description
Reliability ≥99.999%
8-9
EN55022 Class A
ETSI EN 300386
FCC Part 15
EN 61000-4-2
EN 61000-4-3
EN 61000-4-4
EN 61000-4-5
EN 61000-4-6
EN 60590-1
UL 60950-1
GB/T 4943
IEC 60825-2
EN 60825-1
EN 60825-2
GB/T 7247
IEC 60068-2-1
IEC 60068-2-2
IEC 60068-2-6
IEC 60068-2-14
IEC 60068-2-29
IEC 60068-2-78
8-10
Jitter and wander at the output port Complies with ITU‐T G.823 Table 1/Figure 1
Item Specifications
Interface RJ45
Item Specifications
Connector type LC LC LC
8-11
Item Specifications
Item Specifications
Connector type LC LC LC LC
Optical fiber type Multi-mode Single mode Single mode Single mode
Item Specifications
Connector type LC LC LC LC
Optical fiber type Multi-mode Single mode Single mode Single mode
8-12
Power Input Voltage Voltage Range (V) Max. Input Max. Output Fuse spec-
Module (V) Current (A) Power (W) ification
Code (A)
• PWA and PWB boards can not be used at the same time.
Item Requirement
9-1
Item Requirement
• The temperature and humidity are measured 1.5 m above the floor and 0.4 m in front of the equipm
ent.
• Short term running means that the equipment works continuously for no more than 96 hours and
works for no more than 15 days in one year.
Item Specifications
Altitude ≤ 4000 m
Biology Environment
l Avoid the propagation of animalcules, such as fungi and mold.
l Prevent rodents, such as mice.
l For the requirements of active chemical substance density, refer to Table 9-5.
9-2
SO2 ≤ 0.30
H2S ≤ 0.10
NO2 ≤ 0.50
NH3 ≤ 3.00
Cl2 ≤ 0.10
HCl ≤ 0.10
HF ≤ 0.01
O3 ≤ 0.05
NOx ≤ 0.50
Item Specifications
Altitude ≤4000 m
Waterproof Requirement
l Ensure that the packing of the equipment is in good condition without any damages.
l The transportation tool should have rainwater-proof measures, so that the rainwater
will not damage the pack of the equipment.
l If the equipment should be stored outside, the requirements are listed as follows:
9-3
à Ensure that the packing of the equipment is in good condition without any
damages.
à Rainwater-proof measures should be taken, so that the rainwater will not damage
the pack of the equipment.
à Ensure there is no water in the transportation tool.
Biology Environment
l Avoid the propagation of microorganism, such as fungi or mould.
l Avoid rodent (such as mouse) to damage the equipment.
l For the requirements for concentrations of chemical active substances, refer to Table
9-8.
HF ≤0.01 mg/m3
O3 ≤0.05 mg/m3
9-4
Item Specifications
Altitude ≤4000 m
Waterproof Requirement
l Store the equipment indoor.
l Ensure that there is no water on the storage room floor, so that the water will not leak
on the packing container of the equipment.
l The storage position should be far away from the possible leaking positions of the
automatic fire fighting equipment and the heating system.
l If the equipment should be stored outside, the requirements are listed as follows:
à Ensure that the packing of the equipment is in good condition without any
damages.
à Rainwater-proof measures should be taken, so that the rainwater will not damage
the pack of the equipment.
à Ensure there is no water on the floor or in the packing container of the equipment.
à Do not expose the packing to direct sunlight.
Biology Environment
l Avoid the propagation of microorganism, such as fungi or mould.
l Avoid rodent (such as mouse) to damage the equipment.
9-5
l For the requirements for concentrations of chemical active substances, refer to Table
9-11.
HF ≤0.01 mg/m3
O3 ≤0.05 mg/m3
9-6
IET-F RFC4446 IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)
IET-F RFC4448 Encapsulation Methods for Transport of Ethernet Over MPLS Networks
IET-F RFC4553 Using Packet to Transport TDM Service with Unknown Structure
IET-F RFC4717 Encapsulation Methods for Transport of ATM Over MPLS Networks
IETF RFC5086 TDM Circuit Emulation Service with Unknown Structure over Packet Switch
Network
ITU-T G0.704 Synchronous Frame Structures Used at 1544, 6312, 2048, 8448, and
44736kbit/s Hierarchical Levels
ITU-T G0.706 Frame Alignment and Cyclic Redundancy Check (CRC) Procedures
Relating to Basic Frame Structures Defined in Recommendation G.704
ITU-T G0.707 Network Node Interface (V2003) for the Synchronous Digital Hierarchy
(SDH)
ITU-T G0.773 Protocol Suites for Q Interfaces for Management of Transmission Systems
ITU-T G0.774 SDH Information Model for the Network Element View
A-1
ITU-T G.7740.02 SDH Configuration of the Payload Structure For the Network Element View
ITU-T G.7740.03 SDH Management of Multiplex-Section Protection for the Network Element
View
ITU-T G.7740.05 SDH Connection Monitoring for the Network Element View
ITU-T G.7740.06 SDH Unidirectional Performance Monitoring for the Network Element View
ITU-T G.7740.07 SDH Low-Order Path Trace and Interface Tag Management for the Network
Element View
ITU-T G0.780 Vocabulary of Terms for Synchronous Digital Hierarchy (SDH) Networks
and Equipment
ITU-T G0.810 Terms and Definitions for Synchronous Digital Hierarchy (SDH) Networks
ITU-T G0.813 Timing Characteristics of Slave Clocks Suitable for Operation in SDH
Equipment
ITU-T G0.823 The Control of Jitter and Wander Within Digital Networks Which are Based
on the 2048 kbit/s Hierarchy
ITU-T G0.825 The Control of Jitter and Wander Within Digital Networks Which are Based
on the Synchronous Digital Hierarchy (SDH)
ITU-T G0.826 Error Performance Parameters and Objectives for International, Constant
Bit Rate Digital Paths at or above the Primary Rate
ITU-T G0.832 Transport of SDH Elements on SDH Networks - Frame and Multiplexing
Structures
A-2
ITU-T G0.957 Optical Interfaces for Equipment and Systems Relating to the Synchronous
Digital Hierarchy (SDH)
ITU-T G0.958 Digital Line Systems Based on the Synchronous Digital Hierarchy for Use
on Optical Fibre Cables
ITU-T G0.8131 Linear Protection Switching for Transport MPLS (MPLS-TP) Networks
PDH path, section and transmission system and SDH path and multiplex
ITU-T M.2120
section fault detection and localization procedures
A-3
ITU-T M.2120 PDH Path, Section and Transmission System and SDH Path and Multiplex
Section Fault Detection and Localization Procedures
ITU-T I.432.2 B-ISDN User Network Interface-Physical Layer Specification for 155520
kbit/s and 622080 kbit/s
ITU-T I.432.3 B-ISDN User Network Interface-Physical Layer Specification for -1544kbit/s
and 2048 kbit/s
IEEE 802.3 Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access
Method and Physical Layer Specifications
IEEE 802.1ag Virtual Bridge Local Area Network-Connectivity Fault Management (CFM)
IEEE 802.3ah User Access Network MAC Parameter, Physical Layer Parameters and
Management Parameters
IEEE 1588v2 Precision Clock Synchronization Protocol for Networked Measurement and
Control Systems
A-4
GB/T 2423 Basic Environmental Testing Procedures for Electric and Electronic Products
GB 17625.1 The Limits for the Harmonic Current Emissions Caused by Low-Voltage
Electrical and Electronic Equipments (Equipment Input Current≤16A per
Phase)
A-5
A-6
II
III
IV
AS
- Autonomous System
BC
- Boundary Clock
BFD
- Bidirectional Forwarding Detection
BGP
- Border Gateway Protocol
BITS
- Building Integrated Timing Supply
BMC
- Best Master Clock
BTS
- Base Transceiver Station
CBS
- Committed Burst Size
CC
- Continuity Check
CCM
- Continuity Check Message
CE
- Customer Edge
CES
- Circuit Emulation Service
CFM
- Connectivity Fault Management
CIP
- Customer Interface Point
CIR
- Committed Information Rate
CLI
- Command Line Interface
CS
- Conducted Susceptibility
CSF
- Client Signal Failure
DHCP
- Dynamic Host Configuration Protocol
DM
- Delay Measurement
DS
- Differentiated Service
DSCP
- Differentiated Services Code Point
DU
- Downstream Unsolicited
DWRR
- Deficit Weighted Round Robin
DiffServ
- Differentiated Service
E-LAN
- Ethernet Private LAN Service
E-LINE
- Ethernet Private Line
E-TREE
- Ethernet Private Tree Service
VI
E2E
- End-to-End
EBS
- Excess Burst Size
ECMP
- Equal-Cost Multi-Path routing
EFM
- Ethernet in the First Mile
EFT
- Electrical Fast Transient
EIR
- Excess Information Rate
EMC
- Electromagnetic Compatibility
EMS
- Element Management System
EPL
- Ethernet Private Line
EPLAN
- Ethernet Private LAN
EPTREE
- Ethernet Private Tree
ESD
- Electrostatic Discharge
ETH-CC
- Ethernet Continuity Check
ETH-LB
- Ethernet Loopback
ETH-LT
- Ethernet Link Trace
ETS
- European Telecommunication Standard
ETSI
- European Telecommunications Standards Institute
EVPL
- Ethernet Virtual Private Line
EVPLAN
- Ethernet Virtual Private LAN
VII
EVPTREE
- Ethernet Virtual Private Tree
EXP
- Experimental
FCC
- Federal Communication Commission
FDI
- Forward Defect Indication
FE
- Fast Ethernet
FEB
- Floor Equipotential earthing terminal Board
FMC
- Fixed Mobile Convergence
FRR
- Fast Reroute
GE
- Gigabit Ethernet
GMC
- Grandmaster Clock
GPS
- Global Positioning System
H-VPLS
- Hierarchy of VPLS
HDB3
- High Density Bipolar of order 3
HSB
- Hot Standby
ICMP
- Internet Control Message Protocol
IEC
- International Electrotechnical Commission
IEEE
- Institute of Electrical and Electronics Engineers
IGMP
- Internet Group Management Protocol
IP
- Internet Protocol
VIII
IPHB
- Incoming PHB
IPv4
- Internet Protocol version 4
IS-IS
- Intermediate System-to-Intermediate System
ISO
- International Organization for Standardization
ITU-T
- International Telecommunication Union - Telecommunication Standardization
Sector
L1
- Layer 1
L2
- Layer 2
L2VPN
- Layer 2 Virtual Private Network
L3
- Layer 3
LACP
- Link Aggregation Control Protocol
LAG
- Link Aggregation Group
LAN
- Local Area Network
LB
- Loopback
LCT
- Local Craft Terminal
LDP
- Label Distribution Protocol
LLDP
- Link Layer Discovery Protocol
LM
- Loss Measurement
LSP
- Label Switched Path
LT
- Link Trace
IX
LTE
- Long Term Evolution
MAC
- Media Access Control
MC-LAG
- Multi-Chassis Link Aggregation Group
MCC
- Management Communication Channel
MD5
- Message Digest 5 Algorithm
MEG
- Maintenance Entity Group
MEP
- MEG End Point
MET
- Main Earthing Terminal
MFDFr
- Matrix Flow Domain Fragment
MIB
- Management Information Base
MIP
- MEG Intermediate Point
MPLS
- Multiprotocol Label Switching
MPLS-TP
- Multi-Protocol Label Switching Transport Profile
MS-PW
- Multi-Segment Pseudo Wire
MSTP
- Multiple Spanning Tree Protocol
MTBF
- Mean Time Between Failures
MTTR
- Mean Time To Recovery
MTU
- Maximum Transfer Unit
MTU
- Multi-Tenant Unit
NNI
- Network Node Interface
NPE
- Network Provider Edge
OAM
- Operation, Administration and Maintenance
OC
- Ordinary Clock
OPEX
- Operating Expenditure
OPHB
- Outgoing PHB
OSPF
- Open Shortest Path First
P2P
- Peer-to-Peer
PE
- Provider Edge
PPS
- Pulse Per Second
PTP
- Precision Time Protocol
PTP
- Point-To-Point
PW
- Pseudo Wire
PWE3
- Pseudo Wire Emulation Edge-to-Edge
QoS
- Quality of Service
RDI
- Remote Defect Indication
RIP
- Routing Information Protocol
RNC
- Radio Network Controller
RS
- Radiated Susceptiblility
XI
RSTP
- Rapid Spanning Tree Protocol
RSVP
- Resource Reservation Protocol
RSVP-TE
- Resource Reservation Protocol - Traffic Engineering
SCN
- Switched Circuit Network
SDH
- Synchronous Digital Hierarchy
SFP
- Small Form-factor Pluggable
SFP+
- Small Form-factor Pluggable Plus
SLA
- Service Level Agreement
SNMP
- Simple Network Management Protocol
SP
- Strict Priority
SPE
- Switching PE
SSM
- Synchronization Status Message
SSTP
- Single Spanning Tree Protocol
STP
- Spanning Tree Protocol
STP
- Signaling Transfer Point
TC
- Transparent Clock
TCP
- Transmission Control Protocol
TDM
- Time Division Multiplexing
TE
- Traffic Engineering
XII
TELNET
- Telecommunication Network Protocol
TLV
- Tag, Length, Value
TMC
- T-MPLS Channel
TMP
- T-MPLS Path
ToD
- Time of Delivery
ToS
- Type of Service
UDP
- User Datagram Protocol
UNI
- User Network Interface
UPE
- User facing Provider Edge
UTP
- Unshielded Twisted Pair
VIP
- Virtual Interface Point
VLAN
- Virtual Local Area Network
VLL
- Virtual Leased Line
VPLS
- Virtual Private LAN Service
VPN
- Virtual Private Network
VPWS
- Virtual Private Wire Service
VRF
- Virtual Route Forwarding
VRRP
- Virtual Router Redundancy Protocol
WRED
- Weighted Random Early Detection
XIII
WRR
- Weighted Round Robin
XIV