Professional Documents
Culture Documents
Equipment
V200R003C00
Product Description
Issue 01
Date 2013-10-31
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Purpose
This document describes the networking application, functions, structure, features of the ATN
device.
Related Version
The following table lists the product version related to this document.
Intended Audience
This document is intended for:
Symbol Conventions
Symbol Description
Command Conventions
Convention Description
GUI Conventions
Convention Description
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Contents
2 Product Architecture.....................................................................................................................6
2.1 Physical Architecture......................................................................................................................................................7
2.2 Software Architecture...................................................................................................................................................11
3 Technical Specifications.............................................................................................................12
3.1 ATN 910 Technical Specifications...............................................................................................................................13
3.2 ATN 910I Technical Specifications.............................................................................................................................21
3.3 ATN 910B Technical Specifications............................................................................................................................30
3.4 ATN 950B Technical Specifications............................................................................................................................39
4 Boards............................................................................................................................................50
4.1 ATN 910 Boards...........................................................................................................................................................51
4.1.1 Board Type................................................................................................................................................................51
4.1.2 Ethernet Service Interface Board...............................................................................................................................53
4.1.3 E1/T1 Service Interface Board..................................................................................................................................54
4.1.4 xDSL Service Interface Board...................................................................................................................................56
4.2 ATN 950B Boards........................................................................................................................................................58
4.2.1 Board Type................................................................................................................................................................58
4.2.2 Ethernet Service Interface Board...............................................................................................................................60
4.2.3 E1 Service Interface Board........................................................................................................................................60
4.2.4 STM-1 Service Interface Board.................................................................................................................................62
5 PoE..................................................................................................................................................65
6 Link Features................................................................................................................................66
6.1 Ethernet Link Features..................................................................................................................................................67
6.2 POS/CPOS Link Features.............................................................................................................................................67
6.3 xDSL Link Features......................................................................................................................................................68
6.4 E1 Link Features...........................................................................................................................................................68
6.5 T1 Link Features...........................................................................................................................................................69
7 Service Features...........................................................................................................................70
7.1 Ethernet Features..........................................................................................................................................................71
7.1.1 Layer-2 Ethernet Features.........................................................................................................................................71
7.1.2 Layer-3 Ethernet Features.........................................................................................................................................71
7.1.3 RRPP Link Features..................................................................................................................................................71
7.1.4 STP/RSTP/MSTP Features........................................................................................................................................72
7.1.5 G.8032 Link Features................................................................................................................................................72
7.2 IP Features....................................................................................................................................................................72
7.2.1 IPv4/IPv6 Stack.........................................................................................................................................................72
7.2.2 IPv4 Features.............................................................................................................................................................73
7.2.3 IPv6_Features............................................................................................................................................................73
7.2.4 IPv4/IPv6 Transition Technology.............................................................................................................................74
7.3 Routing Protocol...........................................................................................................................................................74
7.4 MPLS............................................................................................................................................................................76
7.5 VPN Features................................................................................................................................................................78
7.5.1 Tunnel Policy.............................................................................................................................................................78
7.5.2 VPN Tunnel...............................................................................................................................................................79
7.5.3 MPLS L2VPN...........................................................................................................................................................79
7.5.4 BGP/MPLS L3VPN..................................................................................................................................................80
7.5.5 MPLS VE..................................................................................................................................................................80
7.6 Network Reliability......................................................................................................................................................80
7.7 QoS...............................................................................................................................................................................82
7.8 Security Features..........................................................................................................................................................86
7.9 Maintainability..............................................................................................................................................................88
7.10 Traffic Statistics..........................................................................................................................................................92
7.11 Clock...........................................................................................................................................................................93
8 Applicable Environment............................................................................................................95
9 Operation and Maintenance......................................................................................................96
9.1 System Configuration Modes.......................................................................................................................................97
9.2 System Management and Maintenance........................................................................................................................97
9.3 Device Running Status Monitoring..............................................................................................................................98
9.4 System Service and Status Tracking............................................................................................................................99
9.5 System Test and Diagnosis...........................................................................................................................................99
9.6 NQA............................................................................................................................................................................100
9.7 In-Service Debugging.................................................................................................................................................100
9.8 System Software Upgrade..........................................................................................................................................101
9.9 Other Operation and Maintenance Features...............................................................................................................101
10 NMS...........................................................................................................................................102
11 Compliant North American Standards and Protocols......................................................104
Taking the challenges faced by carriers with respect to resources, cost, and services at the access
layer during the evolvement of mobile networks, the ATN series, which adhere to Huawei's
"Any Media" conception, provide sustainable IP RAN solutions to 2G, 3G, and Long Term
Evolution (LTE) applications.
l ATN 910I:
l ATN 910B:
l ATN 950B:
Interfaces
The ATN series provide dense and various interfaces, to meet different access services and
scenarios.
l Supports FE interfaces.
l Supports GE interfaces.
l Supports E1 interfaces.
l Supports colored optical modules, saving optical fiber resources.
l Only the ATN 910 supports T1 interfaces.
l Only the ATN 910 supports ADSL2+, G.SHDSL, and VDSL2 interfaces.
Service Bearing
The ATN series provide Layer 2, Layer 3, MPLS, and Layer 2/3 VPN functions, to provide
flexible and comprehensive bearing solutions for different scenarios, which helps Metro services
become more intelligent. Among them, MPLS function, which is based on MPLS/MPLS-TP
series standards, adopts a connection-oriented packet switching technology to provide wider
bandwidth and low delays to help the current transport network to evolve into an LTE network
and to fully protect customers' investment.
Reliability
l Supports IP FRR, LDP FRR, TE FRR, and VPN FRR.
l Supports 1:1 APS of TE-Tunnels.
l Supports PW redundancy protection.
l Supports Bit-Error-Triggered protection switching.
l Only the ATN 950B supports 1+1 hot backup of system control, switching and timing board
(CXP)
l Only the ATN 910 and ATN 950B support N:1 (1 ≤ N ≤ 16) protection group of TE-
Tunnels.
l Only the ATN 910, ATN 910I, and ATN 910B support 1:1 PW APS.
l Only the ATN 950B supports Non-Stop Routing (NSR).
QoS
The ATN series support simple and complex traffic classification, three levels of hierarchical
quality of service (HQoS) scheduling, able to provide flexible and reliable differentiated services
for users by using refined traffic scheduling and shaping.
Maintainability
l Supports a visual network management system to simplify network management, improve
O&M capability, and help performance measuring and fault diagnosis for the whole
topology or End-to-End.
l Supports Plug-and-Play based on DHCP or DCN. NMS can automatically detect and
configure the new online devices in order to realize remote batch commissioning.
l Supports (Network Quality Analysis) NQA.
l Supports BFD, Ethernet OAM, ATM OAM, MPLS OAM, and MPLS-TP OAM.
l Supports Y.1731.
l Support IP FPM.
l Support RFC 2544: Before service provisioning or migration, an ATN NE newly going
online can transmit packets to test the throughput, packet loss rate, and latency. In this
manner, site visits with meters are not required.
l Only the ATN 950B supports ISSU: When the device is configured with two system control
boards, it can be upgraded in ISSU mode without causing service interruption.
l Only the ATN 910I and ATN 910B support dying gasp: When the device is powered off,
it reports a dying gasp alarm to the NMS software. By default, the dying gasp function of
the device is enabled.
Synchronization
Supports perfect clock synchronization solutions to provide precious frequency or time
synchronization.
l Supports physical layer synchronization, including Ethernet clock synchronization.
l Supports Network Time Protocol (NTP).
l Supports 1588v2 to meet the LTE network's requirements for clock synchronization and
to better transport mobile backhaul services.
l Supports 1588 Adaptive Clock Recovery (ACR).
Others
l Energy saving: Idle ports can be manually disabled.
l Power over Ethernet (PoE): Only the ATN 910I-PoE provide PoE interfaces and it can
provide a maximum output power of 30 W for other devices.
2 Product Architecture
FE FE
EF8F/EF8T EF8F/EF8T
GE GE
EG2/EG4F EG2/EG4F
E1 E1
ML1/ML1A/ML1B Service ML1/ML1A/ML1B
E1 processing and E1
MD1A/MD1B switching module MD1A/MD1B
T1 T1
MO1C MO1C
ADSL2+
AVD8A
VDSL2
AVD8B
G.SHDSL
SHD4/SHD4I
Control board
CXPI/CXPL
ATN 910 is a four-slot 1 U (44.45 mm or 1.75 in.) product. The boards housed in slots 1 and 2
integrate the functions of controlling the system, timing the system, and forwarding packets.
The other two slots house PICs. The bandwidth for each PIC slot is 2 Gbit/s.
SLOT 3 (2 x GE) SLOT 4 (2 x GE)
SLOT SLOT
5 6 SLOT 1 and SLOT 2
ATN 910 has an integrated structure and provides the system control board with the functions
of controlling the system, timing the system, and forwarding packets and PICs with the function
of processing link-layer services. ATN 910 can house only one system control board.
ATN 910I
Service
GE processing GE
and
forwarding
module
E1 E1
ATN 910I is a box device having fixed boards configured, and its height is 1 U (44.45 mm or
1.75 in.). It supports AC and DC power supplies and 12 Gbit/s switching capacity. To meet
diverse customer requirements, ATN 910I provides a variety of models that support different
power supplies and interfaces.
NOTE
Some models do not support E1 interfaces. For details, please refer to Product Positioning.
ATN 910B
GE Service GE
processing
10GE and 10GE
forwarding
module
E1 E1
ATN 910B is a box device having fixed boards configured, and its height is 1 U (44.45 mm or
1.75 in.). To meet diverse customer requirements, ATN 910B provides a variety of models that
support different switching capacity and interfaces.
NOTE
Some models do not support E1 interfaces. For details, please refer to Product Positioning.
ATN 950B
Control and
User side management module Network side
Clock module
FE/GE FE/GE
EM4F/EM4T EM4F/EM4T
FE/GE FE/GE
EM8F/EM8T EM8F/EM8T
10GE 10GE
EX1 EX1
E1 Service E1
ML1/ML1A/ML1B ML1/ML1A/ML1B
processing and
E1 switching module E1
MD1A/MD1B MD1A/MD1B
CPOS CPOS
STM-1 STM-1
CQ1B CQ1B
POS POS
STM-1 STM-1
PQ1 PQ1
Control board
CXPA/CXPB/CXPE
ATN 950B is an eight - slot 2 U (88.9 mm or 2.5 in.) product. The boards housed in slots 7 and
8 integrate the control, forwarding, and timing functions, and they serve as backups for each
other. The other six slots house PICs.
SLOT 7 SLOT 8
SLOT
10 SLOT 5 (10GE/GE) SLOT 6 (10GE/GE)
SLOT
11 SLOT 3 (10GE/4 x GE) SLOT 4 (10GE/4 x GE)
SLOT
9 SLOT 1 (8 x GE) SLOT 2 (8 x GE)
NOTE
The figure shows the slot distribution of the ATN 950B equipped with the AND1CXPA or AND1CXPB
board.
When ATN 950B is equipped with the AND1CXPA board, each of slots 3 and 4 has a bandwidth of 4 x
GE and does not support 10GE interface boards.
l The bandwidth for slot 1 or 2 is 8 Gbit/s; and slot 1-2 support 8*GE/FE boards, 4*GE/FE
boards and GE bandwidth boards.
l The bandwidth for slot 3 or 4 is 10 Gbit/s, and slot 3-4 support 10GE boards, 4*GE/FE
boards and GE bandwidth boards.
l The bandwidth for slot 5 or 6 is 10 Gbit/s, and slot 5-6 support 10GE boards and GE
bandwidth boards.
SLOT 7 SLOT 8
SLOT
10 SLOT 5 (10GE/4 x GE) SLOT 6 (10GE/4 x GE)
SLOT
11 SLOT 3 (10GE/4 x GE) SLOT 4 (10GE/4 x GE)
SLOT
9 SLOT 1 (10GE/8 x GE) SLOT 2 (10GE/8 x GE)
NOTE
The figure shows the slot distribution of the ATN 950B equipped with the AND2CXPA, AND2CXPB, or
AND2CXPE board.
When ATN 950B uses the AND2CXPA, AND2CXPB, or AND2CXPE board as its control board, and the
AND1EM4T, AND1EM4F, AND1EM4C, or AND1EX1 board as the Ethernet interface board, slot
bandwidth limitation is the same as that when ATN 950B uses the AND1CXPA or AND1CXPB board as
its control board.
l The bandwidth for slot 1 or 2 is 8 Gbit/s; and slot 1-2 support 10GE boards, 8*GE/FE
boards, 4*GE/FE boards and GE bandwidth boards.
l The bandwidth for slot 3 to 6 is 10 Gbit/s, and slot 3-4 support 10GE boards, 4*GE/FE
boards and GE bandwidth boards.
ATN 950B has an integrated structure and provides system control boards and PICs. The system
control boards integrate the control, forwarding, and timing functions; the PICs process link-
layer services. ATN 950B can house two system control boards, each of which is connected to
all PICs.
The software platform is the VRP platform, which is composed of four sub-systems, that is, SSP,
SMP, IPOS, and NSP.
l SSP: The SSP sub-system is the basic running platform for software systems. It includes
components such as task management, communication management, HA, timer, start and
loading, patch management, system commissioning, and tools.
l SMP: The SMP sub-system is a uniform configuration platform for ATN products. It
includes components such as configuration interfaces (CLI, SNMP, and MML),
configuration management, multi-language support, and alarm tracing, and performance
l IPOS: The IPOS sub-system is a routing protocol platform. It includes components such
as BGP protocol, IGP protocol, MPLS TE, and L3VPN.
l NSP: The NSP sub-system includes components such as link-layer protocol, Layer 2
features (MSTP, RRPP, and Trunk), IP protocol (IP protocol stack, ARP, and address
management), packet transmitting/receiving, L2VPN (PW protocol, PWE3, and VPLS),
SLA (NQA), BAS (AAA, TACAS, and RADIUS), QoS, network security, network
monitoring (OAM and BFD), and interface management.
3 Technical Specifications
Dimensions (width x 442 mm x 220 mm x 1U (17.40 in. x 8.66 in. x 1U), 1U=44.45
depth x height) mm (1.75 in.)
Environment Requirements
l Storage requirements
NOTE
The storage environment must comply with ETSI EN 300 019-1-1 standard.
– Climate requirements
Item Description
Temperature ≤ 1ºC/min
change rate
– Waterproof requirements
When storing equipment at a customer site, you are recommended to store the equipment
indoors.
Ensure that no water remains on the floor or leaks to the equipment package. Keep the
equipment away from places where water leakage is possible, such as the places near
the automatic fire-fighting facilities and heating facilities.
If the equipment has to be stored outdoors, the following conditions must be satisfied:
– The package is intact.
– Required rainproof measures are provided to prevent water from entering the
package.
– No water is on the ground where the package is placed.
Mechanical Content
Active
Substance
– The density of chemical active substances must comply with the requirements
defined in the following table.
HF ≤ 0.01 mg/m3
O3 ≤ 0.05 mg/m3
Frequency l 5 Hz to 10 Hz
l 10 Hz to 50 Hz
l 50 Hz to 100 Hz
Item Description
Temperature ≤ 1ºC/min
change rate
– Waterproof requirements
The following conditions must be present for transportation:
– The package is intact.
– Required rainproof measures are provided for the transportation tools to prevent
water from entering the package.
– No water is on the transportation tools.
– Biological environment requirements
– Avoid reproduction of microbe, such as eumycete and mycete.
– Take anti-rodent measures.
– Air cleanness requirements
– The air must be free from explosive, electric-conductive, magnetic-conductive, or
corrosive dust.
– The density of mechanical active substances must comply with the requirements
defined in the following table.
Mechanical Content
Active
Substance
– The density of chemical active substances must comply with the requirements
defined in the following table.
HF ≤ 0.03 mg/m3
O3 ≤ 0.10 mg/m3
Frequency l 5 Hz to 20 Hz
l 20 Hz to 200 Hz
dB/oct -3
NOTE
The operating environment must comply with ETSI EN 300 019-1-3 standard.
– Climate requirements
Item Description
Altitude ≤ 4000 m (13123.2 ft) [When the altitude is lower than 1800
m (5905.44 ft), the equipment operates normally; when the
altitude is within the range of 1800 m to 4000 m (3280.8 ft to
13123.2 ft), the actual equipment operating temperature
decreases by 1ºC (1.8ºF) for every 220 m (721.78 ft) increase in
altitude.]
Temperature ≤ 0.5ºC/min
change rate
Mechanical Content
Active
Substance
– The density of chemical active substances must comply with the requirements
defined in the following table.
HF ≤ 0.01 mg/m3
O3 ≤ 0.05 mg/m3
Acceleration ≤ 2 m/s2
Frequency l 5 Hz to 62 Hz
l 62 Hz to 200 Hz
Reliability Specifications
Item Description
MTTR 2 hours
System Configurations
Item Description
Number of system control board slots 2 (One system control board occupies two slots)
Item Description
Standard/Protocol Description
Dimensions (width x 442 mm x 220 mm x 1U (17.40 in. x 8.66 in. x 1U), 1U=44.45mm
depth x height) (1.75 in.)
Environment Requirements
l Storage requirements
NOTE
The storage environment must comply with ETSI EN 300 019-1-1 standard.
– Climate requirements
Item Description
Temperature ≤ 1ºC/min
change rate
– Waterproof requirements
When storing equipment at a customer site, you are recommended to store the equipment
indoors.
Ensure that no water remains on the floor or leaks to the equipment package. Keep the
equipment away from places where water leakage is possible, such as the places near
the automatic fire-fighting facilities and heating facilities.
If the equipment has to be stored outdoors, the following conditions must be satisfied:
– The package is intact.
– Required rainproof measures are provided to prevent water from entering the
package.
– No water is on the ground where the package is placed.
– The package is free from direct exposure to sunshine.
– Biological environment requirements
– Avoid reproduction of microbe, such as eumycete and mycete.
– Take anti-rodent measures.
– Air cleanness requirements
– The air must be free from explosive, electric-conductive, magnetic-conductive, or
corrosive dust.
– The density of mechanical active substances must comply with the requirements
defined in the following table.
Mechanical Content
Active
Substance
– The density of chemical active substances must comply with the requirements
defined in the following table.
HF ≤ 0.01 mg/m3
O3 ≤ 0.05 mg/m3
Frequency l 5 Hz to 10 Hz
l 10 Hz to 50 Hz
l 50 Hz to 100 Hz
Item Description
Temperature ≤ 1ºC/min
change rate
– Waterproof requirements
The following conditions must be present for transportation:
– The package is intact.
– Required rainproof measures are provided for the transportation tools to prevent
water from entering the package.
– No water is on the transportation tools.
– Biological environment requirements
– Avoid reproduction of microbe, such as eumycete and mycete.
– Take anti-rodent measures.
– Air cleanness requirements
– The air must be free from explosive, electric-conductive, magnetic-conductive, or
corrosive dust.
– The density of mechanical active substances must comply with the requirements
defined in the following table.
Mechanical Content
Active
Substance
– The density of chemical active substances must comply with the requirements
defined in the following table.
HF ≤ 0.03 mg/m3
O3 ≤ 0.10 mg/m3
Frequency l 5 Hz to 20 Hz
l 20 Hz to 200 Hz
dB/oct -3
Item Description
Altitude ≤ 4000 m (13123.2 ft) [When the altitude is lower than 1800
m (5905.44 ft), the equipment operates normally; when the
altitude is within the range of 1800 m to 4000 m (3280.8 ft to
13123.2 ft), the actual equipment operating temperature
decreases by 1ºC (1.8ºF) for every 220 m (721.78 ft) increase in
altitude.]
Temperature ≤ 0.5ºC/min
change rate
Mechanical Content
Active
Substance
– The density of chemical active substances must comply with the requirements
defined in the following table.
HF ≤ 0.01 mg/m3
O3 ≤ 0.05 mg/m3
Acceleration ≤ 2 m/s2
Frequency l 5 Hz to 62 Hz
l 62 Hz to 200 Hz
Reliability Specifications
Item Description
MTTR 2 hours
System Configurations
Item Description
Standard/Protocol Description
Dimensions (width x 442 mm x 220 mm x 1U (17.40 in. x 8.66 in. x 1U), 1U=44.45
depth x height) mm (1.75 in.)
Environment Requirements
l Storage requirements
NOTE
The storage environment must comply with ETSI EN 300 019-1-1 standard.
– Climate requirements
Item Description
Item Description
Temperature ≤ 1ºC/min
change rate
– Waterproof requirements
When storing equipment at a customer site, you are recommended to store the equipment
indoors.
Ensure that no water remains on the floor or leaks to the equipment package. Keep the
equipment away from places where water leakage is possible, such as the places near
the automatic fire-fighting facilities and heating facilities.
If the equipment has to be stored outdoors, the following conditions must be satisfied:
– The package is intact.
– Required rainproof measures are provided to prevent water from entering the
package.
– No water is on the ground where the package is placed.
– The package is free from direct exposure to sunshine.
– Biological environment requirements
– Avoid reproduction of microbe, such as eumycete and mycete.
– Take anti-rodent measures.
– Air cleanness requirements
– The air must be free from explosive, electric-conductive, magnetic-conductive, or
corrosive dust.
– The density of mechanical active substances must comply with the requirements
defined in the following table.
Mechanical Content
Active
Substance
– The density of chemical active substances must comply with the requirements
defined in the following table.
HF ≤ 0.01 mg/m3
O3 ≤ 0.05 mg/m3
Frequency l 5 Hz to 10 Hz
l 10 Hz to 50 Hz
l 50 Hz to 100 Hz
Item Description
Temperature ≤ 1ºC/min
change rate
– Waterproof requirements
The following conditions must be present for transportation:
– The package is intact.
– Required rainproof measures are provided for the transportation tools to prevent
water from entering the package.
– No water is on the transportation tools.
– Biological environment requirements
– Avoid reproduction of microbe, such as eumycete and mycete.
– Take anti-rodent measures.
– Air cleanness requirements
– The air must be free from explosive, electric-conductive, magnetic-conductive, or
corrosive dust.
– The density of mechanical active substances must comply with the requirements
defined in the following table.
Mechanical Content
Active
Substance
– The density of chemical active substances must comply with the requirements
defined in the following table.
HF ≤ 0.03 mg/m3
O3 ≤ 0.10 mg/m3
Frequency l 5 Hz to 20 Hz
l 20 Hz to 200 Hz
dB/oct -3
NOTE
Do not install the air-conditioner above the equipment and ensure that the air exhaust vent of the
air-conditioner is not directly towards the equipment. Keep the air-conditioner away from a
window as possible to ensure that no moisture from the window is blown towards the equipment
through the air-conditioner.
Item Description
Altitude ≤ 4000 m (13123.2 ft) [When the altitude is lower than 1800
m (5905.44 ft), the equipment operates normally; when the
altitude is within the range of 1800 m to 4000 m (3280.8 ft to
13123.2 ft), the actual equipment operating temperature
decreases by 1ºC (1.8ºF) for every 220 m (721.78 ft) increase in
altitude.]
Temperature ≤ 0.5ºC/min
change rate
Mechanical Content
Active
Substance
– The density of chemical active substances must comply with the requirements
defined in the following table.
HF ≤ 0.01 mg/m3
O3 ≤ 0.05 mg/m3
Acceleration ≤ 2 m/s2
Frequency l 5 Hz to 62 Hz
l 62 Hz to 200 Hz
Reliability Specifications
Item Description
MTTR 2 hours
System Configurations
Item Description
SDRAM 1G Byte
Standard/Protocol Description
Dimensions (width x 442 mm x 220 mm x 2U (17.40 in. x 8.66 in. x 2 U), 1 U = 44.45
depth x height) mm (1.75 in.)
Environment Requirements
l Storage requirements
NOTE
The storage environment must comply with ETSI EN 300 019-1-1 standard.
– Climate requirements
Item Description
Temperature ≤ 1ºC/min
change rate
– Waterproof requirements
When storing equipment at a customer site, you are recommended to store the equipment
indoors.
Ensure that no water remains on the floor or leaks to the equipment package. Keep the
equipment away from places where water leakage is possible, such as the places near
the automatic fire-fighting facilities and heating facilities.
If the equipment has to be stored outdoors, the following conditions must be satisfied:
– The package is intact.
– Required rainproof measures are provided to prevent water from entering the
package.
– No water is on the ground where the package is placed.
– The package is free from direct exposure to sunshine.
– Biological environment requirements
– Avoid reproduction of microbe, such as eumycete and mycete.
– Take anti-rodent measures.
– Air cleanness requirements
– The air must be free from explosive, electric-conductive, magnetic-conductive, or
corrosive dust.
– The density of mechanical active substances must comply with the requirements
defined in the following table.
Mechanical Content
Active
Substance
– The density of chemical active substances must comply with the requirements
defined in the following table.
HF ≤ 0.01 mg/m3
O3 ≤ 0.05 mg/m3
Frequency l 5 Hz to 10 Hz
l 10 Hz to 50 Hz
l 50 Hz to 100 Hz
Item Description
Temperature ≤ 1ºC/min
change rate
– Waterproof requirements
The following conditions must be present for transportation:
– The package is intact.
– Required rainproof measures are provided for the transportation tools to prevent
water from entering the package.
– No water is on the transportation tools.
– Biological environment requirements
– Avoid reproduction of microbe, such as eumycete and mycete.
– Take anti-rodent measures.
Mechanical Content
Active
Substance
– The density of chemical active substances must comply with the requirements
defined in the following table.
HF ≤ 0.03 mg/m3
O3 ≤ 0.10 mg/m3
Frequency l 5 Hz to 20 Hz
l 20 Hz to 200 Hz
dB/oct -3
Item Description
Altitude ≤ 4000 m (13123.2 ft) [When the altitude is lower than 1800
m (5905.44 ft), the equipment operates normally; when the
altitude is within the range of 1800 m to 4000 m (3280.8 ft to
13123.2 ft), the actual equipment operating temperature
decreases by 1ºC (1.8ºF) for every 220 m (721.78 ft) increase in
altitude.]
Item Description
Temperature ≤ 0.5ºC/min
change rate
Mechanical Content
Active
Substance
– The density of chemical active substances must comply with the requirements
defined in the following table.
HF ≤ 0.01 mg/m3
O3 ≤ 0.05 mg/m3
Acceleration ≤ 2 m/s2
Frequency l 5 Hz to 62 Hz
l 62 Hz to 200 Hz
Power consumption and l Typical configuration I (with two system control boards)
heat consumption (with Power consumption: 141.17 W
typical configuration, Heat consumption: 141.17 W
room temperature)
Configuration: 2 x 10GE (optical interface) + 6 x GE (optical
interface) + 4 x FE (optical interface) + 4 x FE (electrical
interface) + 32 x E1
l Typical configuration II (with two system control boards)
Power consumption: 131.54 W
Heat consumption: 131.54 W
Configuration: 2 x 10GE (optical interface) + 4 x GE (optical
interface) + 8 x FE (optical interface) + 16 x E1
l Typical configuration III (with two system control boards)
Power consumption: 136.44 W
Heat consumption: 136.44 W
Configuration: 2 x 10GE (optical interface) + 4 x GE (optical
interface) + 8 x FE (optical interface) + 8 x FE (electrical
interface)
l Typical configuration IV (with two system control boards)
Power consumption: 129.21 W
Heat consumption: 129.21 W
Configuration: 2 x 10GE (optical interface) + 4 x GE (optical
interface) + 4 x GE (optical interface) + 8 x FE (electrical
interface)
l Typical configuration V (with two system control boards)
Power consumption: 131.4 W
Heat consumption: 131.4 W
Configuration: 2 x 10GE (optical interface) + 16 x GE
(optical interface)
l Typical configuration VI (with two system control boards)
Power consumption: 104.37 W
Heat consumption: 104.37 W
Configuration: 8 x GE (optical interface) + 4 x GE (electrical
interface)/FE (electrical interface) + 16 x E1
Reliability Specifications
Item Description
MTTR 2 hours
System Configurations
Item Description
Standard/Protocol Description
4 Boards
NOTE
ATN 910I and ATN 910B, which are box devices having fixed boards configured, do not have flexible
boards.
NOTE
The control board of the ATN 910 also provides the Ethernet service interface. For details about applications
of the service interface boards, see the Ethernet service interface board.
The physical interface boards are classified into the following types based on the service access
mode: Ethernet service interface boards, E1/T1 service interface boards, and xDSL service
interface boards.
Table 4-2 Ethernet service interface boards supported by the ATN 910
Table 4-3 E1/T1 service interface boards supported by the ATN 910
Table 4-4 xDSL service interface boards supported by the ATN 910
Power Board
Power boards lead in power for supplying power to the device. For details about power
distribution, see Power Distribution.
Ethernet service interface boards are widely used in various network environments. They can
accept base station services on the user side, and transmit services upstream on the network side.
The Ethernet service interface board supports Layer 2 services, Layer 3 services, and hybrid
transmission of Layer 2 and Layer 3 services. (When the main interface is in Layer 2 mode,
configure the sub-interface to transmit Layer 2/Layer 3 services.)
Table 4-7 shows the Ethernet service interface boards supported by the ATN 910 and the
differences between the boards.
ATM
Figure 4-1 shows the application of the E1 service interface board using the ATM protocol.
Figure 4-1 Application of the E1 service interface board using the ATM protocol
An ATN device uses the E1 service interface board on the user side to support ATM over E1.
When the ATM service access rate is between E1 and E3, multiple E1 links are bound into an
IMA group to increase service bandwidth. On the network side, the E1 service interface board
implements ATM service emulation and transparently transmits the ATM services over the
packet switched network (PSN), such as MPLS or Ethernet. For detailed information, see the
chapter "ATM IMA application" in the Feature Description.
PPP
Figure 4-2 and Figure 4-3 show the applications of the E1/T1 service interface board using the
PPP protocol.
Figure 4-2 Application of the E1/T1 service interface board using the PPP protocol (user side)
Figure 4-3 Application of the E1 service interface board using the PPP protocol (network side)
The ATN device uses the E1/T1 service interface board to support IP/MPLS services carried
over ML-PPPs on both user side and network side. For example, in the Offload scenario, services
(such as voice service) that require high reliability can be carried over an SDH network through
E1 private lines using ML-PPP.
NOTE
An independent PPP link cannot carry service. PPP links must be added to an ML-PPP group to carry
services.
TDM
Figure 4-4 shows the application of the E1/T1 service interface board using the TDM protocol.
Figure 4-4 Application of the E1 service interface board using the TDM protocol
The ATN device uses the E1 service interface board to access the TDM service, encapsulate the
service signals into packets, and transparently transmit the packets through PWs over the PSN
network. This achieves CES service emulation. For detailed information, see the chapter "CES
application" in the Feature Description.
Interface E1 E1 E1 T1
type
Number of 16 16 32 8
interfaces
Interface Master clock mode Master/slave clock Master/slave clock Master/slave clock
clock mode mode mode mode
Link-layer ATM, PPP, TDM ATM, PPP, TDM ATM, PPP, TDM PPP, TDM
protocols
Minimum 2 1 1 -
number of
timeslots in
CE1 mode
l ADSL2+: has a long delay and asymmetric upstream and downstream bandwidth. The
downstream bandwidth is higher than the upstream bandwidth. Therefore, the ADSL2+ is
suitable to carry data services, especially HSDPA services.
l VDSL2 is compatible with ADSL2+. VDSL2 has symmetrical upstream and downstream
bandwidths, and 100 Mbit/s transmission in a short distance within 300 m. It is suitable to
carry voice services, data services, and video services.
l G.SHDSL: has a stable delay and symmetric upstream and downstream bandwidth.
Compared with the ADSL2+, the G.SHDSL is suitable to carry high-priority services, such
as voice services.
The combination of ADSL2+ line and G.SHDSL line meets requirements on data and voice
services access. In addition, the Offload is also an important scenario in the mobile
communication network. In other words, the received base station services are classified and
transmitted by ATN devices. Traditional voice services (2G, 3G R99 CS) are transmitted using
the E1 private line to ensure high QoS, low delay, and high reliability. High-bandwidth packet
services, such as HSDPA services with low requirements on delay, are backhauled using the
xDSL technology. For detailed information, see the chapter "xDSL application" in the Feature
Description.
Table 4-9 shows the xDSL service interface boards supported by ATN devices and the
differences between the boards.
Number of 8 8 4 4
interfaces
Number of binding 4 4 1 1
groups
Working mode ATM mode PTM mode ATM mode IMA mode
EFM mode
The physical interface boards are classified into the following types based on the service access
mode: Ethernet service interface boards, E1 service interface boards, STM-1 service
interface boards.
Table 4-11 Ethernet service interface boards supported by the ATN 950B
Table 4-12 E1 service interface boards Supported by the ATN 950B and Valid Slots
Table 4-13 STM-1 service interface boards supported by the ATN 950B
Power Board
Power boards lead in power for supplying power to the device. For details about power
distribution, see Power Distribution.
Ethernet service interface boards are widely used in various network environments. They can
accept base station services on the user side, and transmit services upstream on the network side.
The Ethernet service interface board supports Layer 2 services, Layer 3 services, and hybrid
transmission of Layer 2 and Layer 3 services. (When the main interface is in Layer 2 mode,
configure the sub-interface to transmit Layer 2/Layer 3 services.)
Table 4-16 shows the Ethernet service interface boards supported by the ATN 950B and the
differences between the boards.
ATM
Figure 4-6 shows the application of the E1 service interface board using the ATM protocol.
Figure 4-6 Application of the E1 service interface board using the ATM protocol
An ATN device uses the E1 service interface board on the user side to support ATM over E1.
When the ATM service access rate is between E1 and E3, multiple E1 links are bound into an
IMA group to increase service bandwidth. On the network side, the E1 service interface board
implements ATM service emulation and transparently transmits the ATM services over the
packet switched network (PSN), such as MPLS or Ethernet. For detailed information, see the
chapter "ATM IMA application" in the Feature Description.
PPP
Figure 4-7 shows the application of the E1 service interface board using the PPP protocol.
Figure 4-7 Application of the E1 service interface board using the PPP protocol (user side)
The ATN device uses the E1 service interface board to support IP services carried over ML-
PPPs on user side.
NOTE
An independent PPP link cannot carry service. PPP links must be added to an ML-PPP group to carry
services.
An ML-PPP does not support MPLS services.
TDM
Figure 4-8 shows the application of the E1 service interface board using the TDM protocol.
Figure 4-8 Application of the E1 service interface board using the TDM protocol
The ATN device uses the E1 service interface board to access the TDM service, encapsulate the
service signals into packets, and transparently transmit the packets through PWs over the PSN
network. This achieves CES service emulation. For detailed information, see the chapter "CES
application" in the Feature Description.
Interface type E1 E1 E1
Number of 16 16 32
interfaces
Interface clock Master clock mode Master/slave clock mode Master/slave clock mode
mode
Link-layer ATM, PPP, TDM ATM, PPP, TDM ATM, PPP, TDM
protocols
Minimum 2 1 1
number of
timeslots in CE1
mode
Figure 4-9 and Figure 4-10 show the applications of STM-1 service interface boards on a
network.
Figure 4-9 Application of the STM-1 service interface board (user side)
Node B
POS/CPOS STM-1
CXP PIC
MSTP Board
Node B
Figure 4-10 Application of the STM-1 service interface board (network side)
STM-1 POS/CPOS
PIC CXP
Board
The AND2CQ1B on the ATN 950B is used as the STM-1 service interface board, which provides
four CPOS interfaces. Each CPOS interface supports 63 E1 channels. The supported services
are almost the same as those of the E1 service interface board.
On ATN 950B, AND2PQ1 and AND2CQ1B are the interface boards that support STM-1
services. The AND2PQ1 board provides 4 POS interfaces. It uses the SONET as the physical-
layer protocol and PPP to control links at the data link layer. The AND2PQ1 board runs IP
services at the network layer. The AND2CQ1B board provides 4 CPOS interfaces. The CPOS
physical ports are no longer used as service ports, but the channelized 63 E1 channels are used
as synchronization serial ports that support the same services as an E1 service interface board.
l The AND2PQ1 board can be used on the user or network side. It carries IP services over
POS interfaces.
l The AND2CQ1B board can be used on the user or network side. It supports ML-PPP and
carries IP services over E1 channels on CPOS interfaces.
l The AND2CQ1B board on the user side can access and converge ATM and TDM services
over E1 channels on CPOS interfaces. It implements service emulation and transparent
transmission over a packet switched network, achieving ATM PWE3 and TDM PWE3
(CES) services.
NOTE
Services supported by the E1 channel on the CPOS interface are basically the same as those provided by
the E1 service interface board. The differences are listed as follows:
l The E1 channel of the AND2CQ1B supports IP and MPLS services carried over ML-PPPs; the E1
service interface board only supports IP services.
l The E1 channel of the AND2CQ1B does not support fractional E1; the E1 service interface board
supports fractional E1 when the TDM protocol is used.
5 PoE
NOTE
Only the ATN 910I (AC) supports PoE.
l A maximum of 4 PoE-enabled ports. Each port provides a maximum of 30 W power supply
capability. By default, the PoE function is enabled for each port.
l Power supply for a PoE port within a specified time range: A time range is specified for a
port. Within the time range, the PD connected to the port is kept powered off.
l Overload protection
l Short-circuit protection
l IEEE 802.3af and IEEE 802.3at
6 Link Features
The E1 interface channelized from a CPOS interface, in compliance with CESoPSN, can
transparently transmit structured TDM services through PWs on an MPLS network.
l Provides CPOS interfaces at 155 Mbit/s. At the link layer, CPOS interfaces support the
following protocols:
– PPP
– TDM
– ATM
– ATM IMA
PPP on CPOS interfaces supports the following protocols:
– LCP
– IPCP
– MPLSCP
– ML-PPP
l Interface loopback, including local loopback and remote loopback.
l CPOS Trunk interface and CPOS Trunk protection.
The E1 interface supports the following link protocols: PPP, ATM, TDM
The E1 interface supports the loopback function on an interface, including local loopback and
remote loopback.
l LCP
l IPCP
l MPLSCP
l MP
T1 ports support port loopback, including local loopback and remote loopback.
l LCP
l IPCP
l MPLSCP
l MLPPP
7 Service Features
7.2 IP Features
7.4 MPLS
7.7 QoS
7.9 Maintainability
7.11 Clock
l IPv4
l IPv6
l MPLS
l VLANIF interfaces
l QoS
l Ethernet sub-interfaces
l VE interfaces
l Polling mechanism
l Link status change notification
l Mechanism of checking the channel status of the sub-ring protocol packets on the major
ring
l STP
l RSTP
l MSTP
MSTP provides BPDU protection to defend against such attacks. After the BPDU protection is
enabled, the device shuts down the edge port that receives BPDUs. At the same time, the device
informs the NMS of the situation. The edge port can be enabled by the network administrator.
The device can restrict the sending of Layer 2 and Layer 3 protocol packets such as RSTP and
DHCP through CP-CAR. This avoids influencing device performance.
7.2 IP Features
IPv4/IPv6 Application
TCP UDP
IPv4 IPv6
Link Layer
l TCP/IP protocol suite, including ICMP, IP, TCP, UDP, socket (TCP/UDP/Raw IP), and
ARP
l ACL
l FTP server/client and TFTP client
l DHCP relay agent
l DHCP client
l Ping, traceroute, and NQA
l NQA can detect the status of ICMP, TCP, UDP, DHCP, FTP, HTTP, and SNMP services
and test the response time of the services. The system supports NQA in UDP jitter and
ICMP jitter tests by sending and receiving packets on LPUs. The minimum interval at which
packets are transmitted can be 10 ms. The entire system supports up to 32 concurrent jitter
tests.
l Configuration of secondary IP addresses for all physical and logical interfaces
7.2.3 IPv6_Features
ATN supports the following IPv6 features:
The integer of the calculated result is the link cost. If the calculated result is smaller
than 1, the cost is 1. The link cost can be changed by changing the reference bandwidth.
By default, the reference bandwidth of ATN is 100 Mbit/s. The value can be changed
to one in the range of 1 to 2147483648 in Mbit/s by running commands.
l IS-IS
– Two-level IS-IS in a routing domain
– Association between IS-IS and LDP
– IS-IS GR helper
– IS-IS I-SPF (I-SPF re-calculates only the affected routes of a shortest path tree (SPT)
rather the entire SPT)
l BGP
– BGP indirect next hop and dynamic update peer-groups
– Policy-based route selection by BGP when there are multiple routes to the same
destination
– BGP GR helper
– BGP route reflector (RR), which addresses the problem of high costs of full-mesh
requirement when there are many IBGP peers
– Sending of BGP Update packets that carry no private AS number
– Route dampening, which suppresses unstable routes (unstable routes are neither added
to the BGP routing table nor advertised to other BGP peers)
– BGP fast convergence
ATN adopts a new route convergence mechanism and algorithm, which speeds up
convergence of BGP routes. The features are as follows:
– Indirect next hop
– On-demand route iteration
l Filtering of PIM neighbors, control of the forwarding boundary, and control of the BSR
service and management boundary
l Filtering and suppression of PIM Register messages
l MSDP authentication
l IGMP packet rate limiting
l Multicast group-based, multicast source-based, multicast source/group-based, stable-
preferred, and balance-preferred load splitting
l Multicast fast leave
7.4 MPLS
ATN supports MPLS features, and static and dynamic LSPs. Static LSPs require that the
administrator configure the Label Switch Routers (LSRs) along the LSPs and set up LSPs
manually. Dynamic LSPs are set up dynamically in accordance with the routing information
through the Label Distribution Protocol (LDP) and RSVP-TE.
The delay for MPLS packets can be controlled in the following aspects:
l In the case that there is no traffic congestion, the device adopts a high-speed processor to
ensure line-rate forwarding and low delay.
l In the case of traffic congestion, the device ensures preferential forwarding and low delay
for traffic with high priority through mechanisms such as QoS, HQoS, and MPLS TE.
MPLS TE
The MPLS TE technology combines the MPLS technology with traffic engineering. It can
reserve resources by setting up LSP tunnels for a specified path in an attempt to avoid network
congestion and balance network traffic.
In the case of resource scarcity, MPLS TE allows the preemption of bandwidth resources of
LSPs with low priorities. This meets the demands of important services or the LSPs with large
bandwidth. When an LSP fails or a node is congested, MPLS TE can ensure smooth network
communication through the backup path and the fast reroute (FRR) function. Through automatic
re-optimization, MPLS TE improves the self-adaptation capability of tunnels and properly
allocates network resources.
The process of updating the network topology through the TEDB is as follows: When a link
goes Down, the CSPF failed link timer is enabled. If the IGP route is deleted or the link is changed
within the timeout period of the CSPF failed link timer, CSPF deletes the timer and then updates
the TEDB. If the IGP route is not deleted or the link is not changed after the timeout period of
the CSPF failed link timer expires, the link is considered Up.
l RSVP-TE
RSVP authentication complies with RFC 3097.
l Auto routing
Auto routing works in either of the following modes:
– IGP shortcut: An LSP is not advertised to neighboring routers. Therefore, other routers
cannot use the LSP.
– Forwarding adjacency: An LSP is advertised to neighboring routers. Therefore, other
routers can use the LSP.
l Fast reroute (FRR)
The switchover through FRR is within 50 ms, which minimizes the data loss when network
faults occur.
l Backup CR-LSP
l Supports the following backup modes:
– Hot backup: A backup CR-LSP is established immediately after the primary CR-LSP
is established. When the primary CR-LSP fails, MPLS TE switches traffic immediately
to the backup CR-LSP.
– Ordinary backup: A backup CR-LSP is set up when the primary CR-LSP fails.
l Make-before-break
Make-before-break is a technology for ensuring highly reliable CR-LSP switchover. The
original path is not deleted until a new path has been created. Before a new CR-LSP is
created, the original CR-LSP is not deleted. After a new CR-LSP has been created, the
traffic is switched to the new CR-LSP first, and then the original CR-LSP is deleted. This
ensures non-stop traffic forwarding.
VLL
Supports the following VLL functions:
l Martini VLL
l The Martini mode supports double labels. The inner label adopts extended LDP for
signaling in compliance with RFC 4096.
l CCC VLL
l CCC VLL supports the local inter-board switching of packets in 802.1Q mode
l SVC VLL
l VLL heterogeneous interworking, that is, interworking between ML-PPP and ETH.
l Interfaces can be configured to transparently transmit BPDU or LACP packet.
VPLS
In a VPLS network, PEs can be all connected to each other and enabled with split horizon to
prevent Layer 2 loops.
The implementations of VPLS control plane through LDP is called Martini VPLS respectively.
l Martini VPLS
l Martini VPLS has poor scalability. With Martini VPLS, LDP is adopted for signaling, and
the peers of a PE need to be manually specified. PEs in a VPLS network are all connected
to each other. Therefore, adding a new PE requires configurations on all the other associated
PEs to be modified. A pseudo wire (PW) is actually a point-to-point link. This means that
using LDP to create, maintain, and delete the PW is more effective.
Supports the following VPLS functions:
l One MAC address space for each VSI
l VPLS learns MAC addresses in the following modes:
l Unqualified mode: In this mode, a VSI can contain multiple VLANs sharing a MAC address
space and a broadcast domain. When learning MAC addresses, VPLS also needs to learn
VLAN IDs.
PWE3
Supports the following PWE3 functions:
7.5.5 MPLS VE
ATN supports the following MPLS virtual Ethernet (VE) functions:
l One VE group
l IPv4 addresses configured for Layer 3 VE interfaces
l Static virtual circuit (SVC) and Martini virtual leased line (VLL) configured for Layer 2
VE interfaces
l ma-def bound to Layer 3 VE, which is used to filter packets to be sent upstream
l Egress port queue configured for packets sent from the CPU
PW Protection
l PW redundancy protection
NOTE
Supports the master/slave mode only in the scenario where the PE on one side of the bearer network
is configured with VLL and the PE on the other side of the network is configured with VPLS.
l Only the ATN 910, ATN 910I, and ATN 910B support 1:1 PW APS.
The function of bit-error-triggered protection switching includes interface bit error detection,
Trunk interface bit-error-triggered protection switching, section layer bit-error-triggered
protection switching, and tunnel bit-error-triggered protection switching.
FRR
Provides multiple fast reroute (FRR) features. You can deploy FRR as required to improve
network reliability.
l IP FRR
– FRR switching can be complete in 50 ms. In this manner, the data loss caused by network
failures is minimized to a great extend.
– FRR enables the system to monitor and save the status of LPUs and interfaces in real
time and to check the status of interfaces during packet forwarding. When faults occur
on an interface, the system can rapidly switch the traffic to another pre-set route, thus
reducing time between failures and the packet loss ratio.
l LDP FRR
LDP FRR switching can be complete in 50 ms.
l TE FRR
– TE FRR is an MPLS TE technology used to protect local networks. TE FRR switching
can be complete within 50 ms. It can minimize data loss when network failures occur.
– TE FRR protects traffic only temporarily. When the protected LSP becomes normal or
a new LSP is established, traffic is switched back to the original protected LSP or the
newly established LSP.
– When a link or a node on the LSP fails, traffic is switched to the protection link and the
ingress node of the LSP attempts to establish a new LSP, if an LSP is configured with
TE FRR.
– With different protected objects, TE FRR is classified into the following types: Link
protection and Node protection.
l VPN FRR
VPN FRR switching can be complete in 50 ms.
The device can be equipped with one CXP (System control, switching and timing board) or two
CXPs. The CXPs support hot backup. If the device is configured with two CXPs, the active CXP
works and the standby CXP is in the standby state. The standby CXP cannot be accessed by
users, but the active CXP can be accessed by the management network interface on the standby
CXP. The slave CXP exchanges information (including heartbeat messages and backup data)
with only the master CXP.
If the system detects that the active CXP becomes faulty or is reset through a command, the
system automatically performs the active/standby switchover of CXP boards, and the switchover
time is less than 100 us. The active/standby switchover of CXP boards does not result in phase
offsets or interrupt services.
The system supports two types of active/standby switchover of CXPs: failover and switchover.
The failover is triggered by serious faults in the active CXP or the reset of the active CXP. The
switchover is triggered by commands that are run on the console interface. You can also forbid
the active/standby switchover of the CXPs by using commands on the console interface. The
system generates alarms, records the faults in the log file, and reports the alarms to the NMS.
The cause of the active/standby switchover and the associated operations are recorded in the
system diagnosis information base for users to analyze.
When a device's control plane experiences a fault and there is a backup control plane, its peer
device will not sense the fault and the peers between the devices will remain unchanged. None
of routing protocol peers, MPLS protocol peers, and other supporting protocol peers will be
stopped.
When configured with two system control boards, the device supports NSR. When experiencing
a fault, upgrade, or service switching, the device does not need to exchange extended protocol
packets with other devices or depend on peer devices for restoration. This isolates devices' status
changes to the most extent and thereby the peer devices will not sense these changes, eliminating
or minimizing the impact on user services in case of a hardware fault.
Load Balancing
l IPv4 unicast routes load balancing
l VLL Tunnels load balancing (Tunnels that support load balancing include: LSP, TE
Tunnel, and GRE Tunnel.)
l L3VPN Tunnels load balancing (Tunnels that support load balancing include: LSP, TE
Tunnel, and GRE Tunnel.)
7.7 QoS
You can collect traffic statistics on the packets on which QoS is performed and view the statistics
result through corresponding display commands.
Diff-Serv Model
Multiple service flows can be aggregated into a Behavior Aggregate (BA) and then processed
based on the same Per-Hop Behavior (PHB). This simplifies the processing and storage of
services.
On the Diff-Serv core network, packet-specific QoS is provided. Therefore, signaling processing
is not required.
Also supports forced traffic classification, independent of the DS domain mapping table. Based
on the interface, Eth-Trunk interface, and Eth-Trunk sub-interface views, users can directly
specify CoS and drop priorities for packets. This enables received packets to be scheduled in
queues with specified CoS. Traffic Policing.
Traffic Policing
CAR is mainly used for rate limit. In the implementation of CAR, a token bucket is used to
measure the data flows that pass through the interfaces on a router so that only the packets
assigned with tokens can go through the router in the specified time period. In this manner, the
rates of traffic are controlled.
CAR is mainly implemented at the edge of a network to ensure that core devices on the network
process data properly. The device supports CAR for traffic.
Queue Scheduling
Supports PQ, WFQ for queue scheduling on interfaces.
Mps packets of different priorities to different queues and adopts Round Robin (RR) on each
interface for queue scheduling.
Priority Queues (PQs) are classified into four types: top PQs, middle PQs, normal PQs, and
bottom PQs. They are ordered in descending order of priorities. When packets leave queues, PQ
allows the packets in the top PQ to go first. Packets in the top PQ are sent as long as there are
packets in this PQ. The device sends packets in the middle PQ only when all packets in the top
PQ are sent. Similarly, the device sends packets in the normal PQ only when all packets in the
middle PQ are sent; the device sends packets in the bottom PQ only when all packets in the
normal PQ are sent. As a result, the packets in the PQ of a higher priority are always sent
preferentially, which ensures that packets of key services are processed preferentially when the
network is congested. Packets of common services are processed when the network is idle. In
this manner, the quality of key services is guaranteed, and the network resources are fully
utilized.
Weight Fair Queuing (WFQ) is a complex queuing process, which ensures that the services with
the same priority are fairly treated and the services with different priorities are weighted. WFQ
weights services based on their requirements for the bandwidth and delay. The weights are
determined by the IP precedence in the IP packet headers. Packets in one flow are placed in one
queue through the Hash algorithm. When flows enter queues, WFQ automatically places
different flows into different queues based on the Hash algorithm. When flows leave queues,
WFQ allocates bandwidths to flows on the outbound interface based on different IP precedence
of the flows. The smaller the precedence value of a flow, the smaller the bandwidth of the flow.
In this manner, services of the same precedence are treated fairly; services of different
precedence are treated based on their weights.
Congestion Avoidance
Congestion avoidance is a traffic control mechanism used to avoid network overload by adjusting
network traffic. With this mechanism, the device can monitor the usage of network resources
(such as queues and buffers in the memory) and discard packets when the network congestion
intensifies.
Random Early Detection (RED) or Weighted Random Early Detection (WRED) algorithms are
frequently used in congestion avoidance.
The RED algorithm sets the upper and lower limits for each queue and specifies the following
rules:
l When the length of a queue is below the lower limit, no packet is discarded.
l When the length of a queue exceeds the upper limit, all the incoming packets are discarded.
l When the length of a queue is between the lower and upper limits, the incoming packets
are discarded randomly. A random number is set for each received packet, and the random
number is compared with the drop probability of the current queue. The packet is discarded
when the random number is larger than the drop probability. The longer the queue, the
higher the drop probability. The drop probability, however, has an upper limit.
Unlike RED, the random number in WRED is based on the IP precedence of IP packets. WRED
keeps a lower drop probability for the packets that have a higher IP precedence.
RED and WRED employ the random packet drop policy to avoid global TCP synchronization.
The device adopts WRED to implement congestion avoidance.
Supports congestion avoidance in outbound directions of an interface. The WRED template is
applied in the outbound direction.
Supports congestion avoidance based on services. Reserves on each interface eight service
queues, that is, BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. Colors packets with red, yellow,
and green to identify the priorities of packets and discard certain packets.
HQoS
Supports the following HQoS functions:
l Provides three levels of scheduling modes to ensure diverse services.
l Sets parameters such as WRED, low delay, SP/WFQ, CBS, PBS, and statistics function
for each queue.
l Sets parameters such as the CIR, PIR, number of queues, and algorithm for scheduling
queues for each user.
l Provides the traffic statistics function. Users can learn the bandwidth usage of services and
properly distribute the bandwidth by analyzing traffic.
l Supports HQoS in the VPLS, L3VPN, and VLL scenarios.
l Supports interface-based and VLAN-based HQoS.
ATM QoS
l ATM traffic scheduling
This function is applicable to five types of traffic: CBR, RTVBR, NRTVBR, UBR, and
UBR+.
Traffic congestion management is supported. The sustainable cell rate (SCR) of services
is guaranteed in priority sequence of CBR (PCR) > RTVBR > NRTVBR > UBR+>UBR.
The idle bandwidth, if any after SCR is guaranteed for all services, will be allocated to
RTVBR, NRTVBR, UBR, and UBR+ services in the proportion of 13:1:1:1. Tail drop is
also supported.
URPF
Supports URPF for IPv4 traffic.
Entries in a MAC address forwarding table are classified into three types:
l Dynamic entries
l Dynamic entries are learnt by interfaces and stored in system control board. Dynamic
entries age. Dynamic entries will be lost in the case of the system reset.
l Static entries
l Static entries are configured by users and stored in system control board. Static entries do
not age. After static entries are configured and saved, they are not lost in the case of the
system reset.
l Blackhole entries
l Blackhole entries are used to filter out the data frames that contain specific destination
MAC addresses. Blackhole entries are configured by users and stored in system control
board. Blackhole entries do not age. After blackhole entries are configured and saved, they
will not be lost in the case of the system reset.
In this manner, the network bandwidth is properly used and the network security is guaranteed.
SSHv2
Supports the STelnet client and server and the SFTP client and server. Both support SSH 1.5
and SSH 2.0.
7.9 Maintainability
Plug-and-Play
Plug-and-Play (PNP) enables the NMS to automatically configure newly powered-on devices
with empty configurations on the network using the DHCP protocol. In this way, the NMS
remotely commissions devices.
On a mobile bearer network, the number of equipment is great, and as a result the deployment
cost is high. With PNP, the time taken for going to sites to perform software commissioning is
reduced greatly and operators are free of unfavorable outdoor working environment. As a result,
the engineering progress is speed up and engineering quality is improved.
DCN
DCN is the short form of data communication network. After a device is powered on, the initial
IP address is generated based on NEID, which enables the device to access the network using
the DCN protocol. Then the NMS automatically discovers and configures devices that go online,
and performs remote and centralized commissioning on these devices.
On a mobile bearer network, the number of equipment is great, and as a result the deployment
cost is high. With DCN, the time taken for going to sites to perform software commissioning is
reduced greatly and operators are free of unfavorable outdoor working environment. As a result,
the engineering progress is speed up and engineering quality is improved.
The ATN 950B integrates virtual routing and forwarding (VRF) routes on the control plane into
the hardware forwarding plane. Therefore, DCN packets are forwarded directly by chips,
accelerating DCN packet transmission and enabling larger coverage of a DCN.
PPPoE
NOTE
Only the ATN 910I supports PPPoE function.
The Point-to-Point Protocol over Ethernet (PPPoE) is a network protocol that encapsulates Point-
to-Point Protocol (PPP) frames into Ethernet frames. The PPPoE enables multiple hosts on an
Ethernet to connect to a broadband remote access server (BRAS). The PPPoE is implemented
in the client/server model:
l The device can only function as a PPPoE client to send a connection request to a PPPoE
server.
l The device can function as a PPPoE client to send a connection request to a PPPoE server,
and PPPoE services and DHCP services can be associated on the device.
Y.1731
Y.1731 supports the following functions:
l Statistics on single-end packet loss, dual-end packet loss, one-way jitter, two-way jitter,
and two-way delay
l VLL alarm indication signal (AIS), VPLS AIS, and VLAN AIS
l Performance statistics on packets with a certain priority
l Multicast LB
MPLS OAM
l MPLS ping and traceroute and detection of the availability of an LSP through the exchange
of MPLS Echo Request packets and MPLS Echo Reply packets
l TE LSP-based traffic statistics function
l Management functions such as the LSP loop detection mechanism
l MPLS trap function
MPLS TP OAM
MPLS TP OAM supports the following functions:
l Continuity check (CC) test
l Loopback (LB) test
l Remote defect indication (RDI) test
l Packet loss measurement (PLM) test, including measurement of single-end packet loss and
dual-end packet loss
l Packet delay measurement (PDM) test, including one-way jitter, two-way jitter, and two-
way delay measurement
802.1ag and provides additional OAM messages for fault management and performance
monitoring. Fault management includes alarm indication signal (AIS), remote defect
indication (RDI), locked signal (LCK), test signal, automatic protection switching
(APS), maintenance communication channel (MCC), experimental (EXP) OAM, and
vendor specific (VSP) OAM. Performance monitoring includes frame loss
measurement (LM) and delay measurement (DM).
By using performance management tools, the ISP can monitor the network status in real time
through the NMS. The ISP then check whether the forwarding capacity of the network complies
with the Service Level Agreement (SLA) signed with users and locate faults. The ISP does not
need to carry out detection on the user side, which greatly decreases maintenance costs.
BFD
BFD is a detection mechanism used uniformly in an entire network. It is used to rapidly detect
and monitor the connectivity of links or IP routes on a network.
BFD sends detection packets at both ends of a bidirectional link to check the link status in both
directions. The defect detection is implemented at the millisecond level. The device supports
single-hop BFD and multi-hop BFD.
ATM OAM
ATM OAM supports the following functions:
Dying Gasp
Reports a dying gasp alarm to the NMS software.
NOTE
Only the ATN 910I and ATN 910B support Dying Gasp.
IP FPM
IP flow performance monitor (FPM) is used to directly detect multipoint-to-multipoint
(MP2MP) service flows and obtain performance statistics such as packet loss ratio and service
trail delay.
l Packet loss detection, including single-ended packet loss detection and dual-ended packet
loss detection
l Delay and jitter detection, among which delay detection including single-ended delay
detection and dual-ended delay detection
RFC2544
IETF RFC2544 defines a series of test solution that describes performance of interconnected
equipment on a network. In this topic, RFC2544 refers to test functions implemented using the
test solutions defined in IETF RFC2544. RFC2544 includes initiating-end test and reflecting-
end test.
The test functions are divided into Layer 2 ETH RFC2544, Layer 3 IP RFC2544, and L2+L3
(accessing Layer 2 services at Layer 3) RFC2544 by application. The three applications supports
the throughput test, delay and jitter test, and packet loss test.
NOTICE
During an RFC2544 test, the system sends a certain number of packets that occupy some or even
all network bandwidth resources. Therefore, an RFC2544 test is service-affecting. Perform an
RFC2544 test only on a network where no services are deployed. In addition, the RFC2544
function is restricted by licenses. Specifically, to use the RFC2544 function, you need to obtain
both an NQA license and a 2544 license.
l The throughput test is used to detect the bandwidth supported by a network, in order to
identify the maximum bandwidth that meets the requirement of accuracy within a specified
bandwidth range.
l The delay and jitter test is used to detect delay and jitter on a network. Specifically, it detects
dual-ended delay and jitter with specified packet length and rate.
l The packet loss test is used to detect the stability of a network at a specified rate.
Specifically, it detects the rate at which packets are received or sent and the packet loss
ratio with specified packet length and rate.
l In traffic classification, the system can collect statistics on the traffic that matches rules
and fails to match rules.
l The traffic statistics function for traffic policing is implemented in the following manners:
– Collects the statistics on the total traffic that matches the CAR rule.
– Collects the statistics on the traffic that is permitted or discarded by the CAR rule.
– Supports the interface-based traffic statistics.
– Supports interface-based CAR traffic statistics when the same traffic policy is applied
to different interfaces.
On an L3VPN network, ATN functioning as a PE, can collect statistics on incoming and outgoing
traffic of various types of access users. The access users include:
7.11 Clock
Supports the following clock features:
clock signals are then used for data transmission. In this way, the clock signals are
transferred.
– Internal clock
Provides an internal clock and can extract clock information from LPUs. The clock
precision reaches 4.6 ppm, that is, 0.00002s.
l 1588v2
– Supports the input and output of the externally synchronized time.
– Supports FE/GE Ethernet interfaces.
– Supports OC, BC, E2ETC, P2PTC, E2ETCOC, and P2PTCOC.
– Allows the device to function as a GrandMaster.
– Supports slave-only when functioning as an OC.
– Supports the dynamic BMC algorithm.
– Supports two delay measurement methods: Delay and PDelay
– Supports one-step mode and two-step mode.
– Supports multicast MAC encapsulation (the VLAN and priority are configurable).
– Supports multicast UDP encapsulation (the source IP address, VLAN, and priority are
configurable).
– Supports unicast MAC encapsulation (the destination MAC, VLAN, and priority are
configurable).
– Supports unicast UDP encapsulation (the source IP address, destination IP address,
destination MAC, VLAN, and priority are configurable).
– Uses the clock recovered through the Precision Time Protocol (PTP) as the clock source
and supports the algorithm for dynamic clock source selection (based on the priority
and clock stratum).
– Implements clock recovery that complies with G.813.
– Implements frequency recovery that meets the requirements of the SDH equipment
clock (SEC) in G.823.
l 1588 ACR
– Supports FE/GE Ethernet interfaces.
– Supports the OC working mode.
– Supports the slave ACR mode.
– Enables configuration of two master IP addresses for one slave. If one master fails, the
slave maintains synchronization with the other master.
– Supports the UDP unicast mode.
– Supports priority configurations (DSCP) for 1588 ACR packets.
– Supports three clock modes: tracing, hold-over, and free-run.
– Supports two lockout options specific to the tracing mode: locked and unlocked.
– Supports "one way" mode or "two way" mode.
– Supports auto sensing of "one step"/"two step".
8 Applicable Environment
Figure 8-1 shows typical application of the device on an FMC MAN network. The device can
be deployed at the access layer of the FMC MAN network or at a site where a large number of
services are transmitted/received to enable multiservice access. Therefore, the device helps to
build an ALL IP-oriented bearer network with high efficiency.
RNC
NodeB Fiber
Enterprise
xDSL
BTS BSC
NOTE
Only the ATN 910 supports xDSL.
9.6 NQA
After the ATN device is powered on, it will automatically bind the management network interface
to the VPN for exclusive use (__LOCAL_OAM_VPN__) and configure the IP address 129.0.0.1/24
for the management network interface.
The user can configure any other IP address for the network segment 129.0.0.0/24 on the PC, and
directly log in to the ATN device using the user name and password for on-site equipment
maintenance.
The IP address of the management network interface can be changed or deleted. The management
interface can be disabled as required.
– As a command input interface, the management Ethernet interface can send command
lines to the control plane.
– As a debugging interface, the management Ethernet interface can receive debugging
information from the control plane and data plane, and deliver debugging commands
and control commands.
l Telnet/SSH.
NMS Configuration
SNMP-based NMS. For details, please refer to NMS.
l Supports board detection, hot swap detection, Watchdog, board resetting, RUN indicator
and debugging indicator control, fan and power supply control, and version query.
l Supports local and remote loading and upgrade of software and data, and functions such
as version rollback, backup, saving, and clearing of version information.
l Supports hierarchical user authority management, operation log management, command
line online help, and comments after the commands.
l Supports inband and outband NMS interfaces.
l Supports three user authentication modes: local authentication, RADIUS authentication,
and HWTACACS authentication, which authenticate and authorize users through
command lines and SNMP.
l Supports Plug and Play.
l Supports multi-user operation.
l Supports query on Layer 2 or Layer 3 interfaces.
l Supports hierarchical management, alarm classification, and alarm filtering.
l Support of the shutdown and undo shutdown commands on interfaces and optical
modules.
Syslog is a sub-function of the information center. Syslog is over UDP. It outputs log information
to the log host through port 514.
The information center receives and processes the following types of information:
l Log information
l Debugging information
l Trap information
Information is classified into eight severity levels. The following table shows the detailed
information.
0 Emer A fatal exception occurs on the device. The system is unable to function
gency properly and must be restarted. For example, the device is restarted due to
program exceptions or memory usage errors are detected.
1 Alert A serious exception occurs on the device, which requires immediate actions.
For example, the memory usage of the device reaches the upper threshold.
2 Critic A critical exception occurs on the device, which needs to be handled and
al analyzed. For example, the memory usage exceeds the alarm threshold; the
temperature exceeds the alarm threshold; and Bidirectional Forwarding
Detection (BFD) detects that a device is unreachable or detects error messages
generated by the local device.
4 Warn An abnormality that may cause the device to malfunction occurs on the
ing device, which requires attention. For example, a routing process is disabled
by the user; BFD detects packet loss; and error protocol packets are detected.
5 Notic A key operation is performed to keep the device running normally. For
e example, the user runs the shutdown command on the interface, a neighbor
is discovered, and the protocol state machine changes status.
6 Infor A routine operation is performed. For example, the user runs a display
matio command.
nal
The information center supports 10 channels, of which channels 0 through 5 each have a default
channel name. By default, the six channels correspond to six directions in which information is
output. The log information on the CF card is output to log files through Channel 9 by default.
This means that a total of seven default output directions are supported.
When multiple log hosts are configured, you can configure log information to be output to
different log hosts through one channel or multiple channels. For example, you can configure
some log information to be output to a log host through Channel 2 (loghost), and some log
information to a log host through Channel 6. In addition, you can change the name of Channel
6 to implement the desired channel management.
The device stores all alarms in a log file, and provides a CF card to store the log file. How long
the alarms can be stored depends on the number of the alarms. Generally, the alarms can be
stored for months.
Provides the system-based trace function to detect and diagnose running software, online
recording of important events such as task switchover and interruption, queue reading and
writing, and system abnormality. If the system is restarted after a fault occurs, the device can
read trace information that functions as a reference for fault location. Trace can be enabled and
disabled through commands on the console interface.
In addition, the device supports real-time query about CPU usage of the MPU.
Debugging and trace information provided by the device is classified into different levels.
Sensitive information with different levels can be output to different destinations as configured.
For example, information can be output to the console interface, Syslog server, or SNMP agent
to trigger traps.
9.6 NQA
Network Quality Analysis (NQA) measures the performance of each protocol running in the
network and helps the network operator to collect the network running indexes, such as the delay
of a TCP connection, rate of file transfer, and delay of an FTP connection. By controlling these
indexes, network operators provide users with services of various grades and charges users
differently. NQA is also an effective tool to diagnose and locate faults in a network.
The mirroring function, conforming to international standards, may be used to analyze the communication
information of terminal customers for a maintenance purpose. Before enabling the mirroring function,
ensure that it is performed within the boundaries permitted by applicable laws and regulations. Effective
measures must be taken to ensure that information is securely protected.
Provides port mirroring to map specific traffic to a certain monitoring interface. In this case, in-
service debugging can be performed for the advanced maintenance engineers to debug and
analyze the operating status of the network.
Upgrade Method
The device can be upgraded by means of resets. When ATN 950B is configured with two system
control boards, it can also be upgraded in ISSU mode without causing service interruption.
The rollback function provided by the device prevents the services from being affected by the
failure in system upgrade.
10 NMS
SNMP
Supports device operation and management by the network management station through SNMP.
Supports SNMPv1, SNMPv2c, and SNMPv3.
l SNMPv1
l SNMPv1 supports community name-based and MIB view-based access control.
l SNMPv2c
l SNMPv2c supports community name-based and MIB view-based access control.
l SNMPv3
l SNMPv3 inherits the basic functions of SNMPv2c, defines a management frame, and
introduces a User-based Security Model (USM) to provide a more secure access control
mechanism for users.
l SNMPv3 supports user groups, user group-based access control, user-based access control,
and authentication and encryption mechanisms.
NMS
The device adopts Huawei iManager U2000 network management system. It supports SNMPv1/
v2c/v3 and the client/server architecture. The network management system can run
independently on many operation systems, such as Windows NT/2000/XP, UNIX (Sun, HP, and
IBM). The device also provides a multi-lingual graphical user interface.
The U2000 can be seamlessly integrated with the NMS provided by the other fixed network
telecommunications devices developed by Huawei, ensuring uniform management of multiple
devices. In addition, the U2000 can be integrated with the widely applied NMSs such as HP
OpenView, IBM NetView, What's up Gold, and SNMPc, ensuring uniform management of
devices of different vendors. The U2000 manages topologies, faults, performance, configuration
tools, logs, users and user security, QoS policies, and VPN services in a real-time manner. The
device can download, store, modify, and upload configuration files on the U2000, and software
of the device can be upgraded through the U2000.
LLDP
The Link Layer Discovery Protocol (LLDP) is a Layer 2 protocol defined in IEEE 802.1ab.
LLDP specifies that the status information is stored on all interfaces and the device can send its
status to the neighbor stations. The interfaces can also send information about changes in the
status to the neighbor stations as required. The neighbor stations then store the received
information in the standard SNMP MIB. The NMS can search for Layer 2 information in the
MIB. As specified in the IEEE 802.1ab standard, the NMS can also discover unreasonable Layer
2 configurations based on information provided by LLDP.
When LLDP runs on the devices, the NMS can obtain Layer 2 information about all the devices
to which it connects and detailed network topology information. This is helpful to the rapid
expansion of the network and acquirement of detailed network topologies and changes. LLDP
also helps discover unreasonable configurations on networks and reports the configurations to
the NMS. This removes incorrect configurations in time.
NOTE
T1 of ATN 910 complies with North American standards and protocols.
AC Access Controller
AF Assured Forwarding
AP Access Point
BE Best-Effort
CE Customer Edge
DC Direct Current
DS Differentiated Services
EF Expedited Forwarding
FE Fast Ethernet
FR Frame Relay
GE Gigabit Ethernet
HA High availability
IP Internet Protocol
IPv4 IP version 4
MP Multilink PPP
NP Network Processor
PE Provider Edge
PQ Priority Queue
PT Protocol Transfer
RH Relative Humidity
RP Rendezvous Point
SP Strict Priority
TE Traffic Engineering
TM Traffic Manager
VC Virtual Circuit