Documente Academic
Documente Profesional
Documente Cultură
Access Equipment
V200R006C00
Product Description
Issue 01
Date 2015-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 applications, functions, structures, and features of
the ATN series.
The usage precautions are as follows:
l A device can store keys in simple, reversible algorithm encryption, or irreversible
algorithm encryption mode. The simple mode has the low security level, and the
irreversible algorithm encryption mode has the highest security level. Use different
storage modes for different scenarios. Exercise caution when using an insecure storage
mode. The system automatically selects the irreversible algorithm encryption mode to
store local user keys. Generally, the reversible algorithm encryption mode is used to
store protocol keys to meet interworking requirements.
l If the simple mode is used, a password is stored in simple in the configuration file. This
results in high security risks. The simple mode applies only to scenarios with special
requirements, such as compatibility and interworking requirements.
l Using a password or a key without a change leaves the password prone to being stolen or
cracked, which is more likely in a longer duration. Changing the password on a regular
basis may avoid such incidences, and therefore is recommended.
l The encryption algorithms DES/3DES/RC2/RSA (RSA-1024 or lower)/MD2/MD4/MD5
(in digital signature scenarios and password encryption)/SHA1 (in digital signature
scenarios) have a low security, which may bring security risks. If protocols allowed,
using more secure encryption algorithms, such as AES/RSA (RSA-2048 or higher)/
SHA2/HMAC-SHA2, is recommended.
Related Version
The following table lists the product versions related to this document.
Intended Audience
This document is intended for:
l Network planning engineers
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.
New
l ATN 910B-F was added in Product Positioning.
Modification
None
Deletion
None
Contents
2 Software Architecture................................................................................................................. 11
3 Technical Specifications and Environmental Requirements..............................................12
3.1 ATN 905 Technical Specifications............................................................................................................................... 13
3.2 ATN 910 Technical Specifications............................................................................................................................... 16
3.3 ATN 910I Technical Specifications.............................................................................................................................. 17
3.4 ATN 910B Technical Specifications.............................................................................................................................20
3.5 ATN 950B Technical Specifications.............................................................................................................................22
3.6 ATN 905 Environmental Requirements....................................................................................................................... 25
3.7 ATN 910 Environmental Requirements....................................................................................................................... 33
3.8 ATN 910I Environmental Requirements...................................................................................................................... 40
3.9 ATN 910B Environmental Requirements.....................................................................................................................47
3.10 ATN 950B Environmental Requirements...................................................................................................................55
4 Boards............................................................................................................................................ 63
4.1 ATN 910 Boards........................................................................................................................................................... 64
4.1.1 Board Type.................................................................................................................................................................64
4.1.2 Ethernet Service Interface Board...............................................................................................................................66
4.1.3 E1T1 Service Interface Board................................................................................................................................... 67
4.1.4 xDSL Service Interface Board...................................................................................................................................69
4.2 ATN 950B Boards........................................................................................................................................................ 71
4.2.1 Board Type.................................................................................................................................................................71
4.2.2 Ethernet Service Interface Board...............................................................................................................................73
4.2.3 E1 Service Interface Board........................................................................................................................................74
4.2.4 STM-1 Service Interface Board.................................................................................................................................76
5 PoE.................................................................................................................................................. 78
6 Link Features................................................................................................................................ 79
6.1 Ethernet Link Features..................................................................................................................................................80
6.2 POS/CPOS Link Features.............................................................................................................................................80
7 Service Features........................................................................................................................... 84
7.1 Ethernet Features.......................................................................................................................................................... 85
7.1.1 Layer 2 Ethernet Features..........................................................................................................................................85
7.1.2 Layer 3 Ethernet Features..........................................................................................................................................85
7.1.3 RRPP Link Features.................................................................................................................................................. 85
7.1.4 STP/RSTP/MSTP Features........................................................................................................................................86
7.1.5 G.8032 Link Features................................................................................................................................................ 86
7.2 IP Features.................................................................................................................................................................... 86
7.2.1 IPv4/IPv6 Stack......................................................................................................................................................... 86
7.2.2 IPv4 Features............................................................................................................................................................. 87
7.2.3 IPv6 Features............................................................................................................................................................. 87
7.2.4 IPv4/IPv6 Transition Technologies........................................................................................................................... 88
7.3 Routing Protocol...........................................................................................................................................................88
7.4 MPLS Features............................................................................................................................................................. 90
7.5 VPN Features................................................................................................................................................................92
7.5.1 Tunnel Policy.............................................................................................................................................................92
7.5.2 VPN Tunnel............................................................................................................................................................... 93
7.5.3 MPLS L2VPN........................................................................................................................................................... 93
7.5.4 BGP/MPLS L3VPN.................................................................................................................................................. 94
7.5.5 MPLS VE.................................................................................................................................................................. 94
7.5.6 IP Hard-Pipe.............................................................................................................................................................. 94
7.6 Network Reliability...................................................................................................................................................... 95
7.7 QoS............................................................................................................................................................................... 97
7.8 Security Features........................................................................................................................................................ 101
7.9 Maintainability............................................................................................................................................................103
7.10 Traffic Statistics........................................................................................................................................................ 107
7.11 Clock.........................................................................................................................................................................108
9.6 NQA............................................................................................................................................................................125
9.7 Port Mirroring.............................................................................................................................................................125
9.8 System Software Upgrade.......................................................................................................................................... 126
9.9 Other Operation and Maintenance Features............................................................................................................... 126
10 NMS........................................................................................................................................... 127
A North American Standards and Protocols Compliance.................................................... 129
B Acronyms and Abbreviations.................................................................................................130
Product Appearance
ATN 905
l Indoor ATN 905:
Figure 1-5 Appearance of the outdoor ATN 905A or 905A-P or 905A-V or 905A-C or
905A-D
NOTE
Outdoor ATN 905 devices configured with different boards have different internal interfaces. For
details, see Panel in the Hardware Description.
ATN 910
Figure 1-6 Appearance of the ATN 910 that has boards fully configured
ATN 910I
ATN 910B
ATN 950B
Figure 1-21 Appearance of the ATN 950B that has boards fully configured
and transmission efficiency, helps construct reliable carrier-class packet transport networks
(PTNs), and reduces the total cost of ownership (TCO).
Interfaces
The ATN provides the following high-density user- and network-side interfaces to meet the
deployment requirements of different services and scenarios:
l FE interfaces
l GE/10GE interfaces
NOTE
For the ATN 905, only the ATN 905-E supports E1 interfaces. Some ATN 910I/ATN 910B models
do not support E1 interfaces. For details, see Product Positioning.
l T1 interfaces (supported only by the ATN 910)
l ADSL2+, G.SHDSL, and VDSL2 interfaces (supported only by the ATN 910) For the
ATN 905: Only the outdoor ATN 905A-V supports VDSL2, Vectoring, and G.INP
retransmission at the physical layer and is connected to the DSLAM device. Only the
indoor ATN 905-V supports ADSL2+, VDSL2, Vectoring, and G.INP retransmission at
the physical layer and is connected to the DSLAM device.
Service Bearing
The ATN provides Layer 2, Layer 3, MPLS, and Layer 2/3 VPN functions to provide flexible
and comprehensive bearing solutions for different scenarios, which helps achieve Metro
services that are more intelligent. The MPLS function, which is based on MPLS/MPLS-TP
standards, adopts a connection-oriented packet switching technology, meeting the
requirements for the bearer network evolution to LTE and achieving the best cost-
effectiveness.
Reliability
The ATN uses the following technologies to ensure high reliability:
QoS
The ATN supports simple and complex traffic classification and three levels of hierarchical
quality of service (HQoS) scheduling. Therefore, the ATN can provide flexible and reliable
differentiated services for users by using refined traffic scheduling and shaping.
Security
The ATN uses the following technologies to ensure security:
l DHCP Snooping: The ATN functions as a firewall between the DHCP client and DHCP
server.
l URPF: used to prevent network attacks based on source IP address spoofing.
l Local attack defense: includes management and control plane protection, attack source
tracing, and alarm generation in the event that the discarded packet threshold is crossed.
l Whitelist association at the application layer
Maintainability
The ATN uses the following technologies to ensure maintainability:
l A network management system (NMS) with a graphical user interface, which simplifies
NE management, improves O&M capabilities, and facilitates network-wide or end-to-
end performance monitoring and fault diagnosis.
l Plug-and-play based on DHCP or DCN. The NMS can automatically detect and
configure the newly connected devices, which helps to implement remote batch
commissioning.
NOTE
Synchronization
The ATN supports complete clock synchronization solutions to provide precise frequency or
time synchronization. The following clock features are used:
NOTE
Different device models or devices equipped with different boards support different clock features. For
details, see 7.11 Clock.
l Physical-layer synchronization, including Ethernet clock synchronization
l Network Time Protocol (NTP)
l 1588v2, which meets the LTE network's requirements for clock synchronization
l G8275.1
l 1588 adaptive clock recovery (ACR)
l CES ACR/DCR
NOTE
Different device models or devices equipped with different boards support different clock features.
For details, see 7.11 Clock.
Others
l Energy conservation: Idle interfaces can be manually disabled.
l Power over Ethernet (PoE): Only the ATN 910I-POE/ATN 905A-P/ATN 905A-C/ATN
905A-D provides PoE interfaces to supply power to other devices.
l Outdoor ATN 905 device can be installed on a pole or outdoor wall. It features superior
waterproof and dustproof performance, meeting requirements of the IP65 protection
class, is adaptive to environments with different temperature and humidity ranges, and
provides the lightning protection function.
NOTE
Lightning protection standards:
l Power interface: 20 kA / 20 kA (differential mode/common mode)
l GE interface: 3 kA
2 Software Architecture
The software for ATN series includes a common software platform and product-specific
adaptive modules.
The software platform is the VRP platform, which is composed of four sub-systems: SSP,
SMP, IPOS, and NSP.
l SSP: the basic running platform for software systems. It includes functions such as task
management, communication management, HA, timer, start and loading, patch
management, system commissioning, and tools.
l SMP: a uniform configuration platform for ATN products. It includes functions such as
configuration interfaces (CLI, SNMP, and MML), configuration management, multi-
language support, and alarm tracing, and performance management.
l IPOS: a routing protocol platform. It includes functions such as BGP, IGP, MPLS TE,
and L3VPN.
l NSP: includes functions such as the link-layer protocol, Layer 2 features (MSTP and
Trunk), IP protocol (IP protocol stack, ARP, and address management), packet
transmission/reception, L2VPN (PW protocol, PWE3, and VPLS), SLA (NQA), BAS
(AAA, TACAS, and RADIUS), QoS, network security, network monitoring (OAM and
BFD), and interface management.
The heat consumption and power consumption are similar and can be considered the same. Heat
consumption is expressed in BTU/h, whereas power consumption is expressed in W. The conversion
between the two units is as follows: 1 BTU/h = 0.2931 W.
Technical Description
Specifications
Technical Description
Specifications
MTBF 40 years
MTTR 2 hours
Packet switching capacity l Indoor 905 AC/DC: 12 Gbit/s (6 Gbit/s for upstream traffic
and 6 Gbit/s for downstream traffic)
l Indoor 905-E: 8 Gbit/s (4 Gbit/s for upstream traffic and 4
Gbit/s for downstream traffic)
l Indoor 905-V: 12.2 Gbit/s (6.1 Gbit/s for upstream traffic
and 6.1 Gbit/s for downstream traffic)
l Outdoor 905A: 12 Gbit/s (6 Gbit/s for upstream traffic and
6 Gbit/s for downstream traffic)
l Outdoor 905A-P: 8 Gbit/s (4 Gbit/s for upstream traffic
and 4 Gbit/s for downstream traffic)
l Outdoor 905A-C: 8 Gbit/s (4 Gbit/s for upstream traffic
and 4 Gbit/s for downstream traffic)
l Outdoor 905A-D: 10 Gbit/s (5 Gbit/s for upstream traffic
and 5 Gbit/s for downstream traffic)
l Outdoor 905A-V: 8.4 Gbit/s (4.2 Gbit/s for upstream traffic
and 4.2 Gbit/s for downstream traffic)
SDRAM 512 MB
CF card 128 MB
NOTE
The CF card of ATN 905 is a virtual card and cannot be replaced.
The heat consumption and power consumption are similar and can be considered the same. Heat
consumption is expressed in BTU/h, whereas power consumption is expressed in W. The conversion
between the two units is as follows: 1 BTU/h = 0.2931 W.
Technical Description
Specifications
MTBF 40 years
MTTR 2 hours
Number of service 2
subboard slots
Packet switching CXPI: 13.6 Gbit/s (6.8 Gbit/s for upstream traffic and 6.8
capacity Gbit/s for downstream traffic)
CXPL: 24 Gbit/s (12 Gbit/s for upstream traffic and 12 Gbit/s
for downstream traffic)
Technical Description
Specifications
SDRAM 1 GB
CF card 512 MB
NOTE
The CF card of the ATN 910 is a physical card and can be replaced.
The heat consumption and power consumption are similar and can be considered the same. Heat
consumption is expressed in BTU/h, whereas power consumption is expressed in W. The conversion
between the two units is as follows: 1 BTU/h = 0.2931 W.
Technical Description
Specifications
Technical Description
Specifications
MTBF 40 years
MTTR 2 hours
Technical Description
Specifications
Technical Description
Specifications
The heat consumption and power consumption are similar and can be considered the same. Heat
consumption is expressed in BTU/h, whereas power consumption is expressed in W. The conversion
between the two units is as follows: 1 BTU/h = 0.2931 W.
Technical Description
Specifications
MTBF 40 years
MTTR 2 hours
Packet switching ATN 910B-A or ATN 910B-B: 88 Gbit/s (44 Gbit/s for
capacity upstream traffic and 44 Gbit/s for downstream traffic)
ATN 910B-D or ATN 910B-E or ATN 910B-F: 128 Gbit/s (64
Gbit/s for upstream traffic and 64 Gbit/s for downstream
traffic)
SDRAM 1 GB
CF card 512 MB
NOTE
The CF card of the ATN 910B is a virtual card and cannot be replaced.
The heat consumption and power consumption are similar and can be considered the same. Heat
consumption is expressed in BTU/h, whereas power consumption is expressed in W. The conversion
between the two units is as follows: 1 BTU/h = 0.2931 W.
Technical Description
Specifications
Technical Description
Specifications
Technical Description
Specifications
– Slot4: AND1EX1
– Slot5: AND1EX1
– Slot6: AND1EX1
– Slot7: AND2CXPB
– Slot8: AND2CXPB
Power consumption: 181 W
Heat consumption: 617.537 BTU/hour
l AND2CXPE (with two system control boards)
– Slot1: AND1EM8F
– Slot2: AND1EM8F
– Slot3: AND1EX1
– Slot4: AND1EX1
– Slot5: AND1EX1
– Slot6: AND1EX1
– Slot7: AND2CXPE
– Slot8: AND2CXPE
Power consumption: 181 W
Heat consumption: 617.537 BTU/hour
MTBF 40 years
MTTR 2 hours
Number of system 2
control board slots
Number of service 6
subboard slots
Technical Description
Specifications
Packet switching AND1CXPA: 88 Gbit/s (44 Gbit/s for upstream traffic and 44
capacity Gbit/s for downstream traffic)
AND1CXPB: 112 Gbit/s (56 Gbit/s for upstream traffic and 56
Gbit/s for downstream traffic)
AND2CXPA: 88 Gbit/s (44 Gbit/s for upstream traffic and 44
Gbit/s for downstream traffic)
AND2CXPB: 88 Gbit/s (44 Gbit/s for upstream traffic and 44
Gbit/s for downstream traffic)
AND2CXPE: 112 Gbit/s (56 Gbit/s for upstream traffic and 56
Gbit/s for downstream traffic)
SDRAM 1 GB
CF card 512 MB
NOTE
l The CF card of ATN 950B (AND1CXPA/AND1CXPB) is a
physical card and can be replaced.
l The CF card of ATN 950B (AND2CXPB/AND2CXPE) is a virtual
card and cannot be replaced.
Relative 5% to 100%
humidity
Temperature ≤ 1ºC/min
change rate
Item Description
– Waterproof requirements
For equipment at a customer site, it is recommended that the equipment be stored
indoors.
Ensure that no water accumulates on the floor or drops to the equipment packaging.
Keep the equipment away from places where water is apt to leak, such as the places
near automatic fire-fighting facilities and heating facilities.
If the equipment has to be stored outdoors, ensure that:
n The packaging is intact.
n Rainproof measures are taken to prevent water from entering the packaging.
n No water accumulates under the packaging.
n The packaging is not exposed to sunlight.
– Biological environment requirements
n Ensure that the location where the equipment is stored is free from microbial
infestation.
n There are no rodents, such as mice.
– Air cleanness requirements
n The air is free from explosive, electric-conductive, magnetic-conductive, or
corrosive dust.
n The concentrations of mechanically active substances meet the requirements
defined in the following table.
Mechanically Concentration
Active
Substance
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
Relative 5% to 95%
humidity
Temperature ≤ 1ºC/min
change rate
– Waterproof requirements
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
Temperature ≤ 0.5ºC/min
change rate
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
Standard/Protocol Description
Relative 5% to 100%
humidity
Temperature ≤ 1ºC/min
change rate
– Waterproof requirements
For equipment at a customer site, it is recommended that the equipment be stored
indoors.
Ensure that no water accumulates on the floor or drops to the equipment packaging.
Keep the equipment away from places where water is apt to leak, such as the places
near automatic fire-fighting facilities and heating facilities.
If the equipment has to be stored outdoors, ensure that:
n The packaging is intact.
n Rainproof measures are taken to prevent water from entering the packaging.
n No water accumulates under the packaging.
n The packaging is not exposed to sunlight.
– Biological environment requirements
n Ensure that the location where the equipment is stored is free from microbial
infestation.
n There are no rodents, such as mice.
– Air cleanness requirements
n The air is free from explosive, electric-conductive, magnetic-conductive, or
corrosive dust.
n The concentrations of mechanically active substances meet the requirements
defined in the following table.
Mechanically Concentration
Active
Substance
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
Relative 5% to 95%
humidity
Temperature ≤ 1ºC/min
change rate
– Waterproof requirements
n The equipment packaging is intact.
n Rainproof measures are taken for the transportation tools to prevent water
from entering the packaging.
n No water accumulates in the transportation tools.
– Biological environment requirements
n Ensure that the location where the equipment is placed is free from microbial
infestation.
n There are no rodents, such as mice.
– Air cleanness requirements
n The air is free from explosive, electric-conductive, magnetic-conductive, or
corrosive dust.
n The concentrations of mechanically active substances meet the requirements
defined in the following table.
Mechanically Concentration
Active
Substance
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.
– Climate requirements
Temperature Relative Humidity
Item Description
Temperature ≤ 0.5ºC/min
change rate
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
Standard/Protocol Description
Item Description
Relative 5% to 100%
humidity
Temperature ≤ 1ºC/min
change rate
– Waterproof requirements
For equipment at a customer site, it is recommended that the equipment be stored
indoors.
Ensure that no water accumulates on the floor or drops to the equipment packaging.
Keep the equipment away from places where water is apt to leak, such as the places
near automatic fire-fighting facilities and heating facilities.
If the equipment has to be stored outdoors, ensure that:
n The packaging is intact.
n Rainproof measures are taken to prevent water from entering the packaging.
n No water accumulates under the packaging.
n The packaging is not exposed to sunlight.
– Biological environment requirements
n Ensure that the location where the equipment is stored is free from microbial
infestation.
n There are no rodents, such as mice.
– Air cleanness requirements
n The air is free from explosive, electric-conductive, magnetic-conductive, or
corrosive dust.
n The concentrations of mechanically active substances meet the requirements
defined in the following table.
Mechanically Concentration
Active
Substance
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
Relative 5% to 95%
humidity
Temperature ≤ 1ºC/min
change rate
– Waterproof requirements
n The equipment packaging is intact.
n Rainproof measures are taken for the transportation tools to prevent water
from entering the packaging.
n No water accumulates in the transportation tools.
– Biological environment requirements
n Ensure that the location where the equipment is placed is free from microbial
infestation.
n There are no rodents, such as mice.
– Air cleanness requirements
n The air is free from explosive, electric-conductive, magnetic-conductive, or
corrosive dust.
n The concentrations of mechanically active substances meet the requirements
defined in the following table.
Mechanically Concentration
Active
Substance
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.
– Climate requirements
Temperature Relative humidity
Item Description
Item Description
Temperature ≤ 0.5ºC/min
change rate
Mechanically Concentration
Active
Substance
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
Standard/Protocol Description
– Climate requirements
Item Description
Relative 5% to 100%
humidity
Temperature ≤ 1ºC/min
change rate
– Waterproof requirements
For equipment at a customer site, it is recommended that the equipment be stored
indoors.
Ensure that no water accumulates on the floor or drops to the equipment packaging.
Keep the equipment away from places where water is apt to leak, such as the places
near automatic fire-fighting facilities and heating facilities.
If the equipment has to be stored outdoors, ensure that:
n The packaging is intact.
n Rainproof measures are taken to prevent water from entering the packaging.
n No water accumulates under the packaging.
n The packaging is not exposed to sunlight.
– Biological environment requirements
n Ensure that the location where the equipment is stored is free from microbial
infestation.
n There are no rodents, such as mice.
– Air cleanness requirements
n The air is free from explosive, electric-conductive, magnetic-conductive, or
corrosive dust.
n The concentrations of mechanically active substances meet the requirements
defined in the following table.
Mechanically Concentration
Active
Substance
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
Relative 5% to 95%
humidity
Temperature ≤ 1ºC/min
change rate
Item Description
– Waterproof requirements
n The equipment packaging is intact.
n Rainproof measures are taken for the transportation tools to prevent water
from entering the packaging.
n No water accumulates in the transportation tools.
– Biological environment requirements
n Ensure that the location where the equipment is placed is free from microbial
infestation.
n There are no rodents, such as mice.
– Air cleanness requirements
n The air is free from explosive, electric-conductive, magnetic-conductive, or
corrosive dust.
n The concentrations of mechanically active substances meet the requirements
defined in the following table.
Mechanically Concentration
Active
Substance
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 does not face the equipment. Keep the air conditioner away from a
window as far as possible to ensure that no moisture from the window is blown towards the
equipment through the air conditioner.
Item Description
Temperature ≤ 0.5ºC/min
change rate
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
Standard/Protocol Description
Relative 5% to 100%
humidity
Temperature ≤ 1ºC/min
change rate
– Waterproof requirements
For equipment at a customer site, it is recommended that the equipment be stored
indoors.
Ensure that no water accumulates on the floor or drops to the equipment packaging.
Keep the equipment away from places where water is apt to leak, such as the places
near automatic fire-fighting facilities and heating facilities.
If the equipment has to be stored outdoors, ensure that:
n The packaging is intact.
n Rainproof measures are taken to prevent water from entering the packaging.
n No water accumulates under the packaging.
n The packaging is not exposed to sunlight.
– Biological environment requirements
n Ensure that the location where the equipment is stored is free from microbial
infestation.
n There are no rodents, such as mice.
– Air cleanness requirements
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
– Climate requirements
Item Description
Relative 5% to 95%
humidity
Temperature ≤ 1ºC/min
change rate
– Waterproof requirements
n The equipment packaging is intact.
n Rainproof measures are taken for the transportation tools to prevent water
from entering the packaging.
n No water accumulates in the transportation tools.
– Biological environment requirements
n Ensure that the location where the equipment is placed is free from microbial
infestation.
n There are no rodents, such as mice.
– Air cleanness requirements
n The air is free from explosive, electric-conductive, magnetic-conductive, or
corrosive dust.
n The concentrations of mechanically active substances meet the requirements
defined in the following table.
Mechanically Concentration
Active
Substance
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
l When the equipment is installed in a network cabinet, the temperature at the air intake
vent of the network cabinet must be within the range of -20°C to 50°C (-4°F to 122°F).
For details on the requirements for network cabinets, see the Installation Guide.
l When the equipment is installed in an APM30 outdoor cabinet, the temperature at the air
intake vent of the outdoor cabinet must be within the range of -40°C to 50°C (-40°F to
122°F). If the cabinet has to run with the ambient temperature below -20 ºC (-4°F), a
heater is required. For details on the requirements for outdoor cabinets, see the
Installation Guide.
l If the equipment is installed in a cabinet, the impact of radiation can be ignored. If the
equipment is installed outdoors, proper protection must be provided for the equipment
against radiation.
l The temperature and relative humidity are measured at the place 1.5 m (4.92 ft) above
the floor and 0.4 m (1.31 ft) away from the front side of a cabinet without any front or
rear protection panel.
Item Description
Temperature ≤ 0.5ºC/min
change rate
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
Standard/Protocol Description
4 Boards
NOTE
The ATN 905, ATN 910I, and ATN 910B are case-shaped devices with fixed boards configured, and
they do not have pluggable 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
Board Name Board Description Supported Version
Table 4-4 xDSL service interface boards supported by the ATN 910
Board Name Board Description Supported Version
Power Board
Power boards lead in power for supplying power to the device.
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 type E1 E1 E1 T1
Number of 16 16 32 8
interfaces
Interface clock Master clock mode Master/slave clock Master/slave clock Master/slave clock
mode mode mode mode
Link-layer ATM, PPP, TDM ATM, PPP, TDM ATM, PPP, TDM PPP, TDM
protocols
Minimum number 2 1 1 -
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 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
Board Name Board Description Supported
Version
Table 4-12 E1 service interface boards Supported by the ATN 950B and Valid Slots
Board Name Board Description Supported
Version
Table 4-13 STM-1 service interface boards supported by the ATN 950B
Board Name Board Description Supported
Version
Power Board
Power boards lead in power for supplying power to the device.
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.
AND1 AND2
AND1 AND2
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 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 device 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 the device, 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-POE or ATN 905A-P or ATN 905A-C or ATN 905A-D supports PoE.
l ATN 910I-POE: provides a maximum of four PoE interfaces. Each interface supports a
maximum of 30 W power supply. The PoE function is enabled by default.
l ATN 905A-P: provides a maximum of three PoE interfaces. The PoE function is enabled
by default. The PoE specifications of the ATN 905A-P vary according to the PCB
version.
NOTE
l On an ATN 905A-P with the PCB version earlier than ANP1CXPE REV D, GE0/2/1 supports
a maximum of 130 W, and GE 0/2/2 and GE 0/2/3 share 60 W.
l On an ATN 905A-P with the PCB version ANP1CXPE REV D or later, GE 0/2/1 and GE
0/2/2 support a maximum of 150 W, GE 0/2/3 supports a maximum of 60 W, and the total
power of the three interfaces cannot exceed 210 W.
l ATN 905A-C: provides a maximum of three PoE interfaces among which one supports a
maximum of 150 W power supply and the left two each support a maximum of 60 W
power supply. The ATN supports a maximum of 210 W power supply. The PoE function
is enabled by default.
l ATN 905A-D: provides a maximum of four PoE interfaces among which one supports a
maximum of 150 W power supply and the left three each support a maximum of 60 W
power. The ATN supports a maximum of 180 W power supply. The PoE function is
enabled by default.
l A PoE interface supports power supply in a specified time segment. If a power-off time
segment is specified for a PoE interface on an ATN, the ATN stops supplying power to
the PD connected to this PoE interface in the specified time segment.
l A PoE interface supports overload protection.
l A PoE interface supports short-circuit protection.
l PoE complies with 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 155 Mbit/s CPOS interfaces that support the following protocols at the link layer:
– PPP
– TDM
– ATM
– ATM IMA
PPP on CPOS interfaces supports the following protocols:
– LCP
– IPCP
– MPLSCP
– ML-PPP
l Interface loopbacks, including local loopback and remote loopback
l CPOS Trunk interfaces and CPOS Trunk protection
Only the ATN 910 supports ADSL2+, G.SHDSL, and VDSL2 interfaces. For the ATN 905: Only the
outdoor ATN 905A-V supports VDSL2, Vectoring, and G.INP retransmission at the physical layer and is
connected to the DSLAM device. Only the indoor ATN 905-V supports ADSL2+, VDSL2, Vectoring,
and G.INP retransmission at the physical layer and is connected to the DSLAM device.
l Single-pair high-speed digital subscriber line (G.SHDSL) is a new symmetric digital
subscriber line technology developed based on HDSL, SDSL, and HDSL2, and it is
defined in ITU-T G.991.2. SHDSL uses the Trellis coded pulse amplitude modulation
(TC-PAM) technology to transfer high-speed data over common twisted pairs, providing
a new broadband access approach.
l Asymmetrical digital subscriber line (ADSL) is an asymmetrical transmission
technology that is used to transmit data at a high speed over common twisted pairs.
ADSL2+ is an extension of ADSL. ADSL2+ supports a maximum upstream rate of 2.5
Mbit/s, a maximum downstream rate of 24 Mbit/s, and a maximum transmission distance
of 6.5 km.
l Very-high-speed digital subscriber line 2 (VDSL2) is developed based on ITU-T
Recommendation G.993.2 and is an extension of VDSL1, which is developed based on
ITU-T Recommendation G.993.1. VDSL2 is designed to be compatible with ADSL,
ADSL2, and ADSL2+, but not with the less-common VDSL1.
The ATN provides VE interfaces to support xDSL. xDSL supports three types of interfaces:
l xDSL interfaces: physical interfaces on xDSL PICs. In the xDSL interface view, you can
disable or enable physical xDSL interfaces.
l DSL-group interfaces: link-layer logical interfaces. In the DSL-group interface view, you
can set link-layer attributes.
l VE interfaces: logical Layer 3 interfaces used only on the NNI side to carry ETHoA
services. You can also use the portswitch command to switch them to Layer 2
interfaces. In the VE interface view, you can configure services.
Different PICs support different working modes:
For the ATN 905, only the ATN 905-E supports E1 interfaces. For the ATN 910I/ATN 910B, some
models do not support E1 interfaces. For details, see Product Positioning.
E1 interfaces support the following link protocols: PPP, ATM, and TDM
NOTE
E1 interfaces on the ATN 905-E support only TDM as the link protocol.
E1 interfaces support the loopback function, including local loopback and remote loopback.
PPP on E1 interfaces supports:
l LCP
l IPCP
l MPLSCP
l MP
ATM on E1 interfaces supports:
l A single E1 ATM TC link
l Multiple E1 ATM links that are bound as an inverse multiplexing over ATM (IMA)
group
TDM on E1 interfaces supports:
l Emulation of TDM E1 services for transparent transmission
l Circuit emulation service (CES) implemented by using pseudo wire emulation edge-to-
edge (PWE3)
l Fractional E1. Different timeslots of an E1 can be bound into different CES PWs.
l Structure-Aware TDM Circuit Emulation Service over Packet Switched Network
(CESoPSN) and Structure-Agnostic Time Division Multiplexing over Packet (SAToP)
services
7 Service Features
l IPv4
l IPv6
l MPLS
l VLANIF interfaces
l QoS
l Ethernet sub-interfaces
l VE interfaces
NOTE
l Polling mechanism
l Link status change notification
l Mechanism of checking the channel status of sub-ring protocol packets on the major ring
7.2 IP Features
IPv4/IPv6 Application
TCP UDP
IPv4 IPv6
Link Layer
l 6VPE
l 6VPE VPN FRR protection
MPLS
The ATN supports the following MPLS functions:
l Basic MPLS functions and service forwarding
l LDP used as the signaling protocol, which distributes labels, sets up LSPs, and transfers
parameters used for setting up LSPs
– Label advertisement mode: downstream unsolicited (DU)
– Ordered label distribution control mode
– Liberal label retention mode
– Basic discovery mechanism and extended discovery mechanism of LDP sessions
l MPLS OAM
– MPLS ping and traceroute. MPLS echo request packets and MPLS echo reply
packets are used to check the availability of LSPs.
– TE LSP-based traffic statistics
– LSP loop detection mechanism
– MPLS trap function
l MPLS QoS
– Mapping from the ToS field in IP packets to the EXP field in MPLS packets in
MPLS uniform or pipe modes
MPLS TE
The MPLS TE technology combines the MPLS technology with traffic engineering. It can
reserve resources by setting up LSPs for specified paths 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, meeting the requirements of important services or high-bandwidth
LSPs. When an LSP fails or congestion occurs on a node, MPLS TE can ensure smooth
network communication using 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 starts. If the IGP route is deleted or the link is changed
before the CSPF failed link timer expires, CSPF deletes the timer and updates the TEDB. If
the IGP route is not deleted or the link is not changed after the CSPF failed link timer expires,
the link is considered Up.
MPLS TE provides the following functions:
l Processing of static CR-LSPs. MPLS TE can create and delete static CR-LSPs, which
require bandwidth and are manually configured.
l Processing of CR-LSPs of various types and route calculation using the CSPF algorithm
For CR-LSPs, MPLS TE support the following functions:
l RSVP-TE
RSVP authentication complies with RFC 3097.
l Automatic routing
Seamless MPLS
Seamless MPLS is a bearer technology that extends the MPLS technology to access networks.
Seamless MPLS sets up an end-to-end LSP across the access, aggregation, and core layers.
All services can be encapsulated using MPLS at the access layer and transmitted along the
end-to-end LSP across the three layers.
l LSPs
l TE tunnels
l GRE tunnels
VLL
The ATN supports the following VLL functions:
l Martini VLL
Martini VLL supports double labels. The inner label uses extended LDP as the signaling
protocol. Martini VLL complies with RFC 4096.
l CCC VLL
CCC VLL supports the local inter-board switching of packets in compliance with
802.1Q.
l SVC VLL
l VLL heterogeneous interworking, that is, interworking between ML-PPP and Ethernet
l Configuration of transparent BPDU or LACP packet transmission on interfaces
VPLS
In a VPLS network, Layer 2 loops can be prevented through fully-meshed connections
between PEs and the split horizon function.
The implementation of the VPLS control plane through LDP is called Martini VPLS. Martini
VPLS uses LDP as the signaling protocol. LDP peer relationships must be manually
configured between PEs on a full-mesh VPLS network. When a PE is added to the VPLS
network, the configurations on all the related PEs must be modified. Therefore, Martini VPLS
has poor scalability. Because PWs are point-to-point links, using LDP to create, maintain, and
delete PWs is more efficient.
Supports the following VPLS functions:
PWE3
Supports the following PWE3 functions:
7.5.5 MPLS VE
The 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 VLL configured for Layer 2 VE interfaces
l ma-def bound to Layer 3 VE interfaces, which is used to filter packets to be sent
upstream
l Egress interface queues configured for packets sent by the CPU
7.5.6 IP Hard-Pipe
IP hard pipe is an IP network-based access technology that strictly isolates soft and hard pipes
by reserving hardware on the device, so that the soft and hard pipes do not affect each other
when carrying leased line services of high-value customers, reserving bandwidth and ensuring
low delay for hard pipe services.
In the IP hard pipe solution, the U2000 manages bandwidth resources network-wide. The
physical interface bandwidth on the public network is divided and allocated to hard and soft
pipes. For example, on an Ethernet interface, a portion of bandwidth is allocated to the hard
pipe, and the remaining portion is allocated to the soft pipe. The hard and soft pipe
bandwidths are isolated and cannot be preempted.
IP hard pipe provides guaranteed bandwidth and low delay on IP networks, allowing the IP
networks to provide access services with SDH service quality. It also provides service-specific
granular OAM and SLA monitoring, which can accelerate the migration of SDH networks to
IP leased line networks.
U2000
Enterprise 1 Enterprise 1
Enterprise 2 Enterprise 2
PE P PE
3G bps
Physical Interface
Soft Pipe
2G bps
Hard Pipe
VRRP
The Virtual Router Redundancy Protocol (VRRP) groups several devices into a virtual router.
If the next-hop device of the master device in the VRRP backup group fails, VRRP switches
traffic to another device to ensure continuous and reliable communication.
PW Protection
l PW redundancy
l 1:1 PW APS
FRR
The ATN provides multiple types of fast reroute (FRR) features. You can deploy FRR as
required to improve network reliability.
l IP FRR
– IP FRR switching can be completed within 50 ms. It can minimize data loss caused
by network failures.
– IP 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 a
fault occurs on an interface, the system can rapidly switch traffic to another preset
route, thereby increasing the mean time between failures (MTBF) and reducing the
number of lost packets.
l LDP FRR
LDP FRR switching can be completed within 50 ms.
l TE FRR
– TE FRR is an MPLS TE technology used to protect part of a network. TE FRR
switching can be completed within 50 ms. It can minimize data loss caused by
network failures.
– TE FRR protects traffic temporarily. When the protected LSP becomes normal or a
new LSP is established, traffic is switched back to the protected LSP or the newly
established LSP.
– If an LSP is configured with TE FRR, traffic is switched to the protection link and
the LSP ingress node attempts to establish a new LSP when a link or node on the
LSP fails.
– TE FRR can provide link protection or node protection based on protected objects.
l VPN FRR
VPN FRR switching can be completed within 50 ms.
An ATN device can be equipped with one CXP (system control, switching, and timing board)
or two CXPs. The CXPs support hot backup. If an ATN 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 users through the management
network interface on the standby CXP. The standby CXP exchanges information (including
heartbeat messages and backup data) only with the active CXP.
If the system detects that the active CXP becomes faulty or is reset by a command, the system
automatically executes a switchover between the active and standby CXP boards. The
switchover time is less than 100 μs. The switchover does not result in phase offsets or
interrupt services.
The system supports two types of CXP switchover: automatic switchover and forcible
switchover. The automatic switchover is triggered by a critical fault in the active CXP or a
reset of the active CXP. The forcible switchover is triggered by a command that is run on the
console interface. You can forbid a CXP switchover by running a command on the console
interface. After a switchover, the system records log information and notifies the NMS. The
switchover cause and the associated operations are recorded in the system diagnosis
information base for users to analyze.
Non-stop routing (NSR) ensures that the control plane of a neighbor does not sense the fault
on the control plane of an ATN device that has a backup control plane. In this process, the
neighbor relationships set up through routing protocols, MPLS, and other protocols for
carrying services are not interrupted.
An ATN device configured with two CXPs supports NSR. When experiencing a fault,
upgrade, or service switchover, the ATN device does not need to exchange extended protocol
packets with other devices or depend on peer devices for recovery. This masks the device's
status changes to the most extent and therefore the peer devices do not sense these changes,
eliminating or minimizing the impact of hardware faults on user services.
Load Balancing
l Load balancing among IPv4 unicast routes
l Load balancing among VLL tunnels (Tunnels that support load balancing include LSPs,
GRE tunnels, and TE tunnels.)
l Load balancing among L3VPN tunnels (Tunnels that support load balancing include:
LSPs, GRE tunnels, and TE tunnels.)
7.7 QoS
You can collect traffic statistics on packets on which QoS is performed and view the statistics
results through the corresponding display commands.
This section describes the QoS functions supported by the ATN.
DiffServ 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 DiffServ core network, packet-specific QoS is provided. Therefore, signaling
processing is not required.
Traffic Policing
CAR is mainly used for rate limiting. With CAR enabled, a token bucket is used to measure
the data flows that pass through an interface, and only the packets assigned tokens can pass
through the interface in the specified period of time. In this manner, the traffic rate at the
interface can be controlled.
CAR is usually applied on the edge of a network to ensure that core devices process data
properly.
Queue Scheduling
The ATN supports PQ and WFQ for queue scheduling on interfaces.
Packets of different priorities are mapped into different queues. Round robin (RR) is used on
each interface for queue scheduling.
Priority queuing (PQ) classifies queues into four types: top queue, middle queue, normal
queue, and bottom queue, which are ordered in descending order of priorities. PQ always
allows packets in a queue with a higher priority to be sent preferentially. Specifically, the ATN
first sends packets in the top queue. After all packets in the top queue are sent, the ATN sends
packets in the middle queue. Similarly, the ATN sends packets in the normal queue only after
all packets in the middle queue are sent, and sends packets in the bottom queue only after all
packets in the normal queue are sent. In this manner, packets of key services are processed
preferentially when congestion occurs on the network. Packets of common services are
processed when the network is idle. This scheduling method ensures the quality of key
services and fully utilizes network resources.
Weight fair queuing (WFQ) is a complex queuing process, which ensures that services with
the same priority are treated equally and services with different priorities are treated based on
weights. WFQ weights services based on their requirements for the bandwidth and delay.
Weights are determined by the IP precedence in IP packet headers. Packets in the same flow
are placed in the same queue using the Hash algorithm. When flows enter queues, WFQ
automatically places different flows in different queues using the Hash algorithm. When flows
leave queues, WFQ allocates bandwidths to the flows based on IP precedence of the flows.
The smaller the IP precedence value of a flow, the smaller the bandwidth allocated to the
flow. In this manner, services of the same precedence are treated equally, and 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 ATN can monitor the usage of network
resources (such as queues and buffer) and discard packets when network congestion
intensifies.
Random early detection (RED) and weighted random early detection (WRED) are usually
used for 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, incoming packets are
discarded randomly. A random number is set for each incoming packet, and the random
number is compared with the drop probability of the queue. The packet is discarded
when the random number is greater than the drop probability. The longer the queue, the
higher the drop probability. The drop probability 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 higher IP precedence.
RED and WRED employ the random packet drop policy to avoid global TCP
synchronization. The ATN uses WRED for congestion avoidance.
The ATN supports congestion avoidance in the outbound direction of an interface. The
WRED template is applied in the outbound direction.
The ATN supports congestion avoidance based on services. Eight service queues (BE, AF1,
AF2, AF3, AF4, EF, CS6, and CS7) are reserved on each interface. Packets of different colors
(red, yellow, and green) correspond to different drop precedence.
HQoS
The ATN supports the following HQoS functions:
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 the priority sequence of CBR (PCR) > RTVBR > NRTVBR > UBR+ >
UBR. If there is idle bandwidth after SCR is guaranteed for all services, the idle
bandwidth is allocated to RTVBR, NRTVBR, UBR, and UBR+ services in the
proportion of 13:1:1:1. Tail drop is also supported.
Uplink and downlink UPC/NPC control is supported.
l Forced traffic classification
Forced traffic classification is supported. You can run a command to configure forced
traffic classification on the upstream interface to set the precedence and color for traffic.
Then, the traffic is forwarded to the downstream interface carrying the specified
precedence and color.
DHCP Snooping
Dynamic Host Configuration Protocol (DHCP) snooping filters out untrusted DHCP
messages through the functions of MAC address limit, DHCP snooping binding, IP+MAC
binding, and Option 82. In this manner, the DHCP denial of service (DoS) attacks, bogus
DHCP server attacks, ARP middleman attacks, and IP/MAC Spoofing attacks in DHCP
applications are prevented. DHCP snooping functions like a firewall between the DHCP
client and DHCP server.
URPF
The ATN supports unicast reverse path forwarding (URPF) for IPv4 traffic.
Entries in a MAC address forwarding table are classified into three types:
l Dynamic entries
l Dynamic entries are learned by interfaces and stored in the hardware of the system
control board. Dynamic entries will age. Dynamic entries will be lost when the system is
reset.
l Static entries
l Static entries are configured by users and stored on the system control board. Static
entries will not age. Static entries will not be lost when the system is 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 on the system
control board. Blackhole entries will not age. Blackhole entries will not be lost when the
system is reset.
In this manner, the network bandwidth is properly used and network security is guaranteed.
SSHv2
The ATN supports the STelnet client and server as well as the SFTP client and server, which
support SSHv1.5 and SSHv2.
7.9 Maintainability
Plug-and-Play
Plug-and-play (PNP) enables the NMS to automatically configure newly powered-on devices
with empty configurations using DHCP and allows commissioning engineers to remotely
commission the devices in a centralized manner.
PNP frees commissioning engineers from visiting sites for software commissioning,
significantly speeding up the engineering progress.
DCN
NOTE
After a device is powered on, the initial IP address is generated based on the NE ID. The
device uses the initial IP address to access the network through the data communication
network (DCN) protocol. Then the NMS automatically discovers and configures the new
device, and commissioning engineers remotely commission the new device.
DCN frees commissioning engineers from visiting sites for software commissioning,
significantly speeding up the engineering progress.
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 905, ATN 910B, and ATN 910I support the 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. PPPoE enables multiple hosts on
an Ethernet to connect to a broadband remote access server (BRAS). PPPoE uses the client/
server model:
l The ATN can function as a PPPoE client to send a connection request to a PPPoE server.
l The ATN can function as a PPPoE client to send an authentication request to a PPPoE
server. PPPoE services and DHCP services can be associated on the ATN.
Virtual Cluster
Virtual cluster is a promising technology for simplifying network O&M and management and
reducing device loads. The control layers of all devices on a network are centralized on a
single device. This device performs path calculation, service provisioning, and traffic control
for all the other devices.
ITU-T Y.1731
ITU-T Y.1731 supports the following functions:
l Statistics on single-ended packet loss, dual-ended 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. MPLS echo request packets and MPLS echo reply packets
are used to check the availability of LSPs.
l TE LSP-based traffic statistics
l 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-ended packet loss
and dual-ended packet loss
l Packet delay measurement (PDM) test, including one-way jitter, two-way jitter, and two-
way delay measurement
Per packet delivery time can be configured ranging from 100 ms to 1s.
l Network-level Ethernet OAM: connectivity fault management OAM (CFM OAM) and
ITU-T Y.1731
Network-level Ethernet OAM checks network connectivity, locates connectivity faults,
and monitors end-to-end network performance at the access and aggregation layers.
Network-level Ethernet OAM complies with protocols such as IEEE 802.1ag
(connectivity fault management) and ITU-T Y.1731.
– IEEE 802.1ag defines OAM functions, such as continuity check (CC), loopback
(LB), and link trace (LT), for Ethernet bearer networks. CFM applies to large-scale
end-to-end Ethernet networks.
– ITU-T Y.1731 covers the content defined in IEEE 802.1ag and defines more 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).
BFD
Bidirectional Forwarding Detection (BFD) is a detection mechanism used uniformly in an
entire network. It is used to quickly check 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. A link fault can be detected within milliseconds. The ATN supports single-
hop BFD and multi-hop BFD.
The ATN supports the following BFD applications:
l BFD for FRR
– BFD for LDP FRR
– LDP FRR switchover triggered after BFD detects faults on protected interfaces
– BFD for IP FRR and BFD for VPN FRR
IP FRR and VPN FRR are triggered after BFD detects faults and reports fault
information to the upper layer applications.
l BFD for static route
l BFD for IS-IS
Statically configured BFD sessions can check IS-IS adjacency.
ATM OAM
ATM OAM supports the following functions:
l CC
l LB
l RDI
l AIS
Dying Gasp
NOTE
Only the ATN 905, ATN 910I and ATN 910B support dying gasp.
IP FPM
NOTE
RFC2544
IETF RFC2544 defines a series of test schemes that are used to test performance of
interconnected equipment on a network. In this document, RFC2544 refers to test functions
implemented using the test schemes defined in IETF RFC2544. RFC2544 includes initiating-
end test and reflecting-end test.
The test functions are divided into three types of application: Layer 2 ETH RFC2544, Layer 3
IP RFC2544, and L2+L3 (Layer 2 service access to Layer 3) RFC2544 by application. The
three types of application support 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 affects services. Perform
an RFC2544 test only on a network where no services are deployed.
l The throughput test is used to check the maximum bandwidth that meets accuracy
requirements within a specified bandwidth range.
l The delay and jitter test is used to check two-way delay and jitter in the case of a
specified packet length and rate.
l The packet loss test is used to check the packet loss ratio in the case of a specified packet
length and rate.
TWAMP SERVER
The Two-Way Active Measurement Protocol (TWAMP) is a technology that measures the
round-trip performance of an IP network. TWAMP uses the client/server mode.
l The client establishes, starts, and stops a TWAMP session, and generates and maintains
statistics about the IP network performance.
l The server responds to the client's request for establishing, starting, or stopping a
TWAMP session.
Y.1564
Y.1564 is a specification for the test before the Ethernet service is activated. The test contents
include the configuration detection on multiple service flows and concurrent performance
detection. Y.1564 can be used to perform the IR, latency, jitter, sequence error, and QoS tests
at the same time to test the CIR, latency, jitter value, and sequence error value of different
packets, which greatly shortens the test period.
l In traffic classification, the system can collect statistics on traffic that matches rules and
traffic that does not match rules.
l The traffic statistics for traffic policing include:
– Statistics on the total traffic that complies with CAR
– Statistics on the traffic that is permitted or discarded by CAR
– Interface-based traffic statistics
– Interface-based CAR traffic statistics when the same traffic policy is applied to
different interfaces
7.11 Clock
The ATN supports the following clock features:
l Ethernet clock synchronization
The Ethernet interfaces of the ATN support Ethernet clock synchronization, which
ensures clock quality and stratum on the network.
NOTE
For the ATN 905, only the ATN 905-E supports E1 interfaces. Some ATN 910I/ATN 910B models
do not support E1 interfaces. For details, see Product Positioning.
l T1 clock synchronization
NOTE
Only the ATN 910 supports T1.
l Network Time Protocol (NTP) clock
The Network Time Protocol (NTP) is used for synchronizing clocks of all devices in a
network so that the devices can provide various applications based on the uniform time.
l NTR clock
NOTE
Only the ATN 910 supports NTR clock.
The NTR clock is a physical-layer clock synchronization technology, similar to the SDH
clock. With this technology, clock signals are extracted directly from serial bit streams
on xDSL links and then are used for data transmission. In this manner, the clock signals
are transferred.
l Internal clock
The ATN provides an internal clock and can extract clock information from LPUs. The
clock precision reaches 4.6 ppm.
l 1588v2
NOTE
ATN 905: 1588v2 is not supported on the ATN 905-E. 1588v2 frequency synchronization is
supported only on the ATN 905A-V and ATN 905 DC. 1588v2 frequency synchronization is not
supported the other ATN 905s. To implement 1588v2 time synchronization, configure physical-
layer frequency synchronization first.
The ATN supports the following 1588v2 features:
– Input and output of externally synchronized time
NOTE
ATN 905: Only the ATN 905 DC supports the externally synchronized time.
– FE/GE interfaces
– OC, BC, TC, E2ETC, P2PTC, TCandBC, E2ETCOC, and P2PTCOC
NOTE
ATN 905: Only the ATN 905A-V and ATN 905 DC support TCandBC.
– GrandMaster
– Slave-only in OC mode
– Dynamic BMC algorithm
– Two delay measurement methods: Delay and PDelay
– One-step mode and two-step mode
– Multicast MAC address encapsulation (The VLAN and priority are configurable.)
– Multicast UDP encapsulation (The source IP address, VLAN, and priority are
configurable.)
– Unicast MAC address encapsulation (The destination MAC address, VLAN, and
priority are configurable.)
– Unicast UDP encapsulation (The source IP address, destination IP address,
destination MAC address, VLAN, and priority are configurable.)
– Clock recovered through the Precision Time Protocol (PTP) being used as the clock
source; algorithm for dynamic clock source selection (based on the priority and
clock stratum)
– Clock recovery that complies with G.813
– Frequency recovery that meets the requirements of the SDH equipment clock (SEC)
in G.823
– Compliance with G8275.1
l 1588 ACR
The CES technology uses the adaptive clock recovery (ACR) or differential clock
recovery (DCR) algorithm to achieve clock (frequency) synchronization. When an
Ethernet transmits TDM services over emulated circuits, the Ethernet uses the ACR or
DCR algorithm to recover clock synchronization information from data packets.
8 Usage Scenarios
ATN 910:
Fiber
RNC
NodeB
Enterprise
NOTE
Only the ATN 910 supports xDSL.
Fiber
RNC
NodeB
SR/BRAS
Single Metro
Enterprise
BTS BSC
Outdoor ATN 905 device is recommended in this usage scenario. This section takes the ATN 905 device
for example to description small-cell base station bearer usage scenario.
Because macro base stations provide uneven and inflexible coverage, small-cell base stations
featuring small sizes, light weights, and adaptation to any installation environments are used
together with macro base stations on mobile networks.
However, installation and deployment of small-cell base stations and their bearer equipment
on live networks encounter many difficulties because of their large quantity, wide distribution
and various installation environments. In addition, site selection, maintenance, and power
supply also encounter many difficulties.
In the Huawei mobile bearer solution, ATN functions as bearer equipment for small-cell base
stations and benefits:
l Anywhere: ATN is available in the indoor and outdoor types and can be installed in
various environments where small-cell base stations are installed.
ATN 905
MME/SGW
CSG ASG RSG
Small
Cell
SR/BRAS
NOTE
For the IPRAN macro base station backhaul network solution, ATN is supported in the following modes:
l Native IP mode: If IPRAN uses a Layer 3 solution, such as, the hierarchy VPN (HVPN) solution, it
is recommended that ATN connect to the IPRAN macro base station backhaul network in Native IP
mode, which facilitates deployment of end to end (E2E) Layer 3 IP connectivity and performance
check schemes.
l Native ETH: If IPRAN uses E2E Layer 2 solution or L2+L3 mixed VPN, it is recommended that
ATN connect to the IPRAN macro base station backhaul network in Native ETH mode, which
facilitates transparent transmission and processing of E2E Layer 2 VLAN packets.
This section takes the ATN 905 device for example to description EDD usage scenario.
In the Huawei enterprise service bearer solution, ATN functioning as an EDD has the
following advantages:
l Supports IP flow performance measurement (FPM), tests without requiring meters at
sites, quality of service (QoS), and quick fault sectionalization and location complying
with RFC 2544.
l Supports 802.1Q in 802.1Q (QinQ) for separating user VLANs and carrier VLANs,
facilitating fault sectionalization.
l Supports dying gasp so that equipment reports an alarm when experiencing power
outage.
l Support real-time performance management through periodic tests and statistics on E2E
service performance including the throughput, delay, and packet loss rate, service level
agreement (SLA) compliance reports.
Figure 8-4 and Figure 8-5 show basic networking of the enterprise service bearer solution to
which ATN belongs.
l With the help of the current IPRAN, ATN can connect to the IPRAN macro base station
backhaul network. On the E2E ATN+CX network, enhanced ATN functions, such as
DCN plug and play and RFC 2544-compliant IP FPM, can be deployed to improve the
network operation and maintenance efficiency.
NOTE
For the IPRAN macro base station backhaul network solution, ATN can also connect to the macro
base station backhaul network in Native IP or Native ETH mode.
Macro BSC
Cell
EDD
RNC
CPE ATN CX
ATN 905
MME/SGW
CSG ASG RSG
Enterprise SR/BRAS
l Certainly, with the help of the current non-IPRAN or leased third-part network, ATN can
connect to a service router (SR) or broadband remote access server (BRAS).
NOTE
ATN can connect to a carrier network in Native IP mode or Native ETH mode based on service
deployment on the intermediate access network.
EDD
Enterprise
Figure 8-6 Integrated installation of an ATN 905A-P as a dock and a small-cell base station
(pole-mounted)
The small-cell base station and dock deployed on the access side of a mobile network connect
to UEs through air interfaces and connect to the mobile backhaul network through FE/GE
interfaces.
RNC
FE/GE
SR/BRAS
BSC
The ATN 905A-P can fast synchronize its time to the small-cell base station when the
small-cell base station is powered on again.
l Cascading: Considering QoS, reliability, and power deployment, the ATN 905A-P
supports no more than 3-level cascading.
NOTE
The default management IP address of a small-cell base station is 192.168.0.49, and the default IP
address of an ATN 905A-P interface that connects to a small-cell base station is 192.168.0.254.
The use of cascading may cause IP address conflicts. To prevent IP address conflicts, the ATN
905A-P provides the function to isolate ARP packets with specified source addresses, so that the
ARP packets with source IP addresses 192.168.0.49 and 192.168.0.254 can be filtered and
differentiated based on their source IP addresses.
RNC
When a user logs in to a local device with null configuration, the device has the plug-and-play function
enabled by default and automatically obtains protocol packets. If the user configures a service (for
example, VLAN, CCC, or VSI service) without specifying any service IP address for the device, some
protocol packets fail to be forwarded, adversely affecting services. Therefore, it is recommended that
you run the undo pnp enable command to disable the plug-and-play function before service
configuration.
l Users can configure the ATN after logging in through the ETH/OAM management
interface. The ETH/OAM management interface integrates the Ethernet NM interface
and console interface. The console interface applies the non-standard serial interface
communication cable sequence. For more information, see Management Cables in
Hardware Description.
NOTE
After the ATN is powered on, it automatically binds the management network interface to the
reserved VPN (__LOCAL_OAM_VPN__) and configures the IP address 192.168.0.1/24 for the
management interface.
A user can configure another IP address in the network segment 192.168.0.0/24 for a computer,
and log in to the ATN from the computer using a user name and password for on-site maintenance.
The IP address of the management interface can be changed or deleted. The management interface
can be disabled as required.
– As a command input interface, the management interface can send command lines
to the control plane.
– As a debugging interface, the management interface can receive debugging
information from the control plane and data plane, and deliver debugging
commands and control commands.
l Users can configure the ATN after remotely logging in through Telnet/SSH.
NMS-based Configuration
A user can use an SNMP-based NMS to configure the ATN. For details, see NMS.
l Board detection, hot swap detection, Watchdog, board reset, RUN indicator, fan and
power supply monitoring, system debugging, and version query
l Local and remote software upgrade and data loading, version rollback, and backup,
saving, and clearing of data
l Hierarchical user authority management, operation log management, command line help
information, and comments on commands
Syslog is a sub-function of the information center. Using UDP, Syslog outputs log information
to the log host through interface 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 levels in terms of severity, which are described in the
following table.
6 Infor A routine operation is performed. For example, a user runs the display
matio command.
nal
The information center supports 10 channels, of which channels 0 to 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 a log file through channel 9 by
default. Therefore, 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 facilitate channel management.
All alarms are stored in a log file on a CF card. How long alarms can be stored depends on the
number of alarms. Generally, alarms can be stored for months.
The ATN provides the system-based trace function to detect and diagnose running software.
The trace function supports online recording of important events such as task switchover and
interruption, queue reading and writing, and system exceptions. If the system is restarted after
a fault occurs, the ATN can read trace information, which functions as a reference for fault
diagnosis. The trace function can be enabled and disabled through commands on the console
interface.
The ATN supports real-time query of CPU usage of the system control board.
Debugging and trace information provided by the ATN is classified into several levels. The
information with different levels can be output to different destinations according to
configurations. For example, information can be output to the console interface, Syslog
server, or SNMP Trap.
9.6 NQA
Network quality analysis (NQA) measures the performance of each protocol running on a
network and helps carriers to collect network operation counters in real time, such as the FTP
connection delay, TCP connection delay, and file transmission rate. By controlling these
counters, carriers can provide differentiated services for users and charge users differently.
NQA is also an effective tool to diagnose network faults.
The mirroring function complies with industry standards. It can be used to analyze communication
information of specific end users for maintenance and operation purposes. Strictly observe the local laws
and regulations when using the mirroring function. Ensure that users' privacy is protected when you
collect and save communication information.
The ATN provides port mirroring to map specific traffic to a certain monitored interface.
Using the traffic information, senior maintenance engineers can perform in-service debugging
and analyze the network operating status.
Upgrade Method
The ATN can be upgraded by means of resets. When the ATN 950B is configured with two
system control boards, it can also be upgraded in ISSU mode without causing service
interruption.
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 the 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