Learning Materials For ZXA10 C300M and C350M

Learning Materials for ZXA10
C300M/C350M
LEGAL INFORMATION
By accepting this certain document of ZTE CORPORATION you agree to the following terms. If you do
not agree to the following terms, please notice that you are not allowed to use this document.
Copyright © 2020 ZTE CORPORATION. Any rights not expressly granted herein are reserved. This
document contains proprietary information of ZTE CORPORATION. Any reproduction, transfer,
distribution, use or disclosure of this document or any portion of this document, in any form by any
means, without the prior written consent of ZTE CORPORATION is prohibited.
are registered trademarks of ZTE CORPORATION. ZTE’s company name, logo and product
names referenced herein are either trademarks or registered trademarks of ZTE CORPORATION.
Other product and company names mentioned herein may be trademarks or trade names of their
respective owners. Without the prior written consent of ZTE CORPORATION or the third party owner
thereof, anyone’s access to this document should not be construed as granting, by implication,
estoppel or otherwise, any license or right to use any marks appearing in the document.
The design of this product complies with requirements of environmental protection and personal
security. This product shall be stored, used or discarded in accordance with product manual, relevant
contract or laws and regulations in relevant country (countries).
This document is provided “as is” and “as available”. Information contained in this document is subject
to continuous update without further notice due to improvement and update of ZTE CORPORATION’s
products and technologies.
ZTE CORPORATION
Address: NO. 55
Hi-tech Road South
ShenZhen
P.R.China
518057
Website: http://support.zte.com.cn
Email: 800@zte.com.cn
TABLE OF CONTENTS
1 MSAN Basics .................................................................................................. 1

1.1 MSAN Introduction............................................................................................ 1
1.1.1 MSAN Development History ............................................................................. 1
1.1.2 MSAN Features ................................................................................................ 1
1.2 Background story of NGN ................................................................................. 2
1.2.1 PSTN network evolution history ........................................................................ 2
1.2.2 Development of VOIP ....................................................................................... 4
1.3 Basic concepts ................................................................................................. 7
1.3.1 Basic concepts of data-communication ............................................................. 7
1.3.2 xDSL Access Technology ............................................................................... 13
1.3.3 FTTX .............................................................................................................. 19
1.3.4 PON ............................................................................................................... 19
1.3.5 H.248 Overview .............................................................................................. 19
2 ZXA10 C300M/C350M Introduction .............................................................. 21

2.1 Product Position ............................................................................................. 21
2.2 Features ......................................................................................................... 22
2.2.1 Narrowband Service Features ........................................................................ 22
2.2.2 Broadband Service Features .......................................................................... 25
2.3 Hardware Architecture .................................................................................... 26
2.3.1 ZXA10 C300M Shelves .................................................................................. 26
2.3.2 ZXA10 C350M Shelf ....................................................................................... 32
2.4 Cards .............................................................................................................. 33
3 Hardware Installation ................................................................................... 47

3.1 Installation Flow .............................................................................................. 47
3.2 Installation Preparations ................................................................................. 48
3.2.1 Environment Check ........................................................................................ 48
3.2.2 Tools Preparation ........................................................................................... 49
3.3 Unpacking and Checking Equipment .............................................................. 53
3.4 Removing Cabinet Doors ................................................................................ 55
3.4.1 Removing the Front Door ............................................................................... 55
3.4.2 Removing a Side Door .................................................................................... 58
3.5 Cabinet Installation ......................................................................................... 58
3.5.1 Installing the Cabinet on the Adjustable Base ................................................. 59
3.5.2 Installing the Cabinet on the Floor .................................................................. 76
3.6 Power Cable and Grounding Cable Installations for the Cabinet ..................... 88
3.6.1 Cabling Requirements .................................................................................... 89
3.6.2 Connecting a Protective Grounding Cable ...................................................... 93
3.6.3 Connecting Power Cables .............................................................................. 96
3.7 Device Installation in the Cabinet .................................................................... 98
3.7.1 Installing a Shelf ............................................................................................. 98
3.7.2 Installing a Subrack ...................................................................................... 103
3.7.3 Installing a Board .......................................................................................... 104
3.8 Power Cable Installation for the Shelf ........................................................... 107
3.9 Signal Cable Installation ............................................................................... 110
3.9.1 Signal Cable Installation Requirements ........................................................ 110
3.9.2 Signal Cable Overview ................................................................................. 113
Document Title
3.9.3 Connecting Signal Cables............................................................................. 121

3.10 Installing Cabinet Doors ................................................................................ 122
3.10.1 Installing the Cabinet Side Door.................................................................... 122
3.10.2 Installing the Front Door ............................................................................... 123
3.11 Installation Inspection ................................................................................... 125
3.11.1 Checking the Cabinets.................................................................................. 125
3.11.2 Checking the Assemblies in the Cabinets ..................................................... 126
3.11.3 Checking the Power Cables and Grounding Cables ..................................... 127
3.11.4 Checking the Signal Cables .......................................................................... 128
3.12 Powering on the Devices .............................................................................. 129
3.13 Site Clean-Up ............................................................................................... 132
4 Initial Configuration .................................................................................... 133

4.1 Initial Data Configuration Flow ...................................................................... 133
4.2 Using SD Card to Quickly Configure in-band Network Management Parameters
133
4.3 Configuration Preparation ............................................................................. 136
4.3.1 Hardware and Software Requirements ......................................................... 136
4.3.2 Entering the Specified Configuration Modes ................................................. 137
5 Basic Data Configuration ........................................................................... 139

5.1 Configuring In-Band NM (SNMP v1/v2) ........................................................ 139
5.2 Configuring In-Band NM (SNMP v3) ............................................................. 143
5.3 Configuring a Trap Server............................................................................. 149
5.4 Configuring the System Log Function ........................................................... 151
5.5 Hardware Configuration ................................................................................ 152
5.5.1 Adding a Rack .............................................................................................. 152
5.5.2 Adding Shelves............................................................................................. 153
5.5.3 Adding Cards ................................................................................................ 154
5.5.4 Adding Daughter Cards ................................................................................ 156
5.6 Configuring Management Channel Between the OLT and the GPON ONU .. 158
6 Basic Service Configuration ...................................................................... 161

6.1 VoIP Service Configuration Flow .................................................................. 161
6.1.1 VoIP POTS Configuration Flow (H.248) ........................................................ 162
6.1.2 VoIP POTS Configuration Flow (SIP) ........................................................... 165
6.1.3 VoIP ISDN Configuration Flow ...................................................................... 168
6.2 Basic VoIP Service Configurations ............................................................... 171
6.2.1 Configuring the MGC .................................................................................... 171
6.2.2 Configuring the MG....................................................................................... 176
6.2.3 Configuring Media and Signaling IP Addresses ............................................ 178
6.2.4 Configuring Termination IDs for VoIP Resources .......................................... 180
6.2.5 Configuring Termination IDs for Narrowband Subscriber Circuits ................. 183
6.2.6 Configuring Media NAT ................................................................................ 187
6.2.7 Configuring a VoIP VLAN ............................................................................. 188
6.2.8 Binding the Uplink Port to the VLAN ............................................................. 189
6.2.9 Configuring SIP Parameters ......................................................................... 190
6.2.10 Configuring the AS, ASP, and Association .................................................... 193
6.2.11 Configuring the D Channel............................................................................ 195
6.2.12 Configuring Termination IDs for ISDN Subscriber Circuits ............................ 196
6.3 VoIP Related Configurations ......................................................................... 198
ZTE Confidential Proprietary © 2016 ZTE Corporation. All rights reserved. III(324)
6.3.1 VoIP Resource Configurations ...................................................................... 198
6.3.2 Configuring VoIP QoS .................................................................................. 200
6.3.3 Configuring Call Control Management .......................................................... 201
6.3.4 Configuring the Self-Switching Function ....................................................... 203
6.3.5 Configuring an Uplink Port Protection Group ................................................ 204
6.3.6 Configuring the Ring Mode ........................................................................... 208
6.3.7 Configuring PBX DDI Function ..................................................................... 209
6.4 VoIP Service Configuration Instances ........................................................... 209
6.4.1 Configuring the VoIP POTS Service (H.248)................................................. 210
6.4.2 Configuring the VoIP POTS Service (SIP) .................................................... 213
6.4.3 Configuring the ISDN BRA Service ............................................................... 217
6.4.4 Configuring the ISDN PRA Service ............................................................... 219
6.4.5 Using DSWU/DSWB Card with VoIP Daughter Card to Configure ISDN PRA
Service ......................................................................................................... 222
6.4.6 Configuring the IP-Based Fax Service .......................................................... 223
6.5 xDSL Service Basic Configuration ................................................................ 225
6.5.1 Creating a Service VLAN .............................................................................. 227
6.5.2 Configuring Configuration Profiles ................................................................ 228
6.5.3 Configuring an MAC Address Pool ............................................................... 259
6.5.4 Configuring a User Port PVC ........................................................................ 260
6.5.5 Activating an xDSL Port ................................................................................ 261
6.6 Configuration Instances ................................................................................ 262
6.6.1 Configuring the ADSL/ADSL2 Service .......................................................... 262
6.6.2 Configuring the VDSL2 Service .................................................................... 268
6.6.3 Configuring the SHDSL Service .................................................................... 279
6.6.4 Configuring the IPoA Service ........................................................................ 283
6.6.5 Configuring Annex J ..................................................................................... 286
6.7 ADSL Service Configuration ......................................................................... 287
6.7.1 Configuring the ADSL Link Establishment Rate ............................................ 287
6.7.2 Configuring the ADSL Link Type ................................................................... 289
6.7.3 Configuring the Data Transmission Mode for an ADSL Port ......................... 290
6.8 VDSL2 Service Configuration ....................................................................... 292
6.8.1 Configuring the Data Transmission Mode for a VDSL Port ........................... 297
6.8.2 Configuring a VDSL2 Port VLAN .................................................................. 299
6.8.3 Querying the VDSL2 Link Performance Data ................................................ 300
6.8.4 Configuring the VDSL2 Bonding Function..................................................... 301
6.9 SHDSL Service Configuration ....................................................................... 304
6.9.1 Configuring the SHDSL Link Establishment Rate ......................................... 304
6.9.2 Configuring the Data Transmission Mode for an SHDSL Port ....................... 306
6.9.3 Configuring an SHDSL Port VLAN ................................................................ 308
6.9.4 Querying the SHDSL Link Performance Data ............................................... 309
6.10 Basic LAN Service Configuration .................................................................. 310
6.10.1 Adding a Service Card .................................................................................. 311
6.10.2 Creating a Service VLAN .............................................................................. 312
6.10.3 Configuring a User Port ................................................................................ 313
6.10.4 Activating a User Port ................................................................................... 314
6.10.5 Configuring LAN Services ............................................................................. 315
Learning Materials for ZXA10 C300M/C350M
1 MSAN Basics
1.1 MSAN Introduction

MSAN(Multiplex Access Network) is the implementation system formed by a series of
transmission entities and providing the required bearing capability for information
transmission service between the service node interface (SNI) and the relative user
network interface (UNI)
 Functions of cross connection ,multiplexing and transmission
 Irrelevant to service type
 Transmitting the subscriber signaling transparently without any explanation
1.1.1 MSAN Development History
 The first period：Pure voice service and optical fiber transmission.
 The second period－Primary Integration：POTS、ISDN、DDN etc.
 The third period －Broadband and Narrowband integration
 The fourth period
 Smooth evolution to NGN
 Comprehensive evolution to packet network
1.1.2 MSAN Features
Abundant service types
Provides integrated access capacity including POTS, ADSL/ ADSL 2/ ADSL 2+,
VDSL, ISDN, DDN, SHDSL (TDM/ATM) and Ethernet to satisfy users’ demands for
varied services.
Excellent networking capability
It has a built-in integrated service scheduling system, adopts

155M/622M/2.5G-compatible architecture, satisfies SDH, Ethernet, ATM and RPR
demands, provides diverse networking modes and protection modes. It, therefore,
ZTE Confidential Proprietary © 2016 ZTE Corporation. All rights reserved. 1(324)
can accommodate different network conditions and enable fast network setup and
service provisioning.
Series products
Series ONUC units with different capacity values and applicable environments are
provided to match different networking requirements.
Convenient management
The complete range of products support centralized device management and

service management, which are very convenient and easy to use. It provides
topology management and supports hierarchical management by device type and
management layer to facilitate management by level and by area. It provides
point-to-point network-level automatic/semi-automatic service configured to simplify
service provisioning and modification.
Carrier-class reliability
System design is totally based on carrier-class applications; it provides perfect

active/standby switchover and flexible configuration capabilities; multiple QoS
policies can ensure communication quality.
It supports smooth evolution to the next-generation IP network to accommodate

future development and protect carrier investment.
It adopts IP  TDM technology and therefore can be upgraded smoothly as MSAG

to be involved in the NGN network.
1.2 Background story of NGN

As the world is now becoming a small “village”, people, who locate in different places in
the earth, can communicate with each other in no time with telephone, email or video etc.
The credit of such advantage goes to the development of modern telecommunication
technology. Going through the history of the telecommunication will help us to
understand the reason and underlying philosophy of all sorts of current techs, and give us
the insight of what will happen tomorrow.
1.2.1 PSTN network evolution history
As known to all, Dr. Alexander Graham Bell is the father of telephone, born in 1847,
Scotland, 28 year-old Bell braced his invention device with tears while confirming that his
device is able to transmit voice. At that night, he wrote to his mother and announced that
“the day friends staying at their home can still talk to each other is coming!” During the
following long period, telephone business has been supported merely by
2 © 2020ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

manual-switching, the experiencing maching-switching and programmed-switching. As

shown in Figure 1.
1.2.1.1 Birth of Telephone

Figure 1 Telephone history (switching history)
The first automatic dialing system was patented in 1891 by a Kansas City undertaker who
believed that crooked operators were sending his business elsewhere, with his main
objective being to eliminate the operators. The first coin telephone was installed in
Hartford, Connecticut in 1900. Party lines were soon developed to lower the cost of the
telephone for individual families, especially those in rural locations In 1920s, nearly 15%
of the telephone in the world is automatic dialing phone, with the development of
automatic dialing technology, almost 80% of the telephone in the world is automatic
phone by the end of 1950s.
1.2.1.2 From “analog” to “digit”
There are two principal means by which telephone signals are transmitted: analog or
digital radio signals. As the electronic current that transmit the voice is actually
“imitating “ the voice behavior, it has the various shape.; while the telegraph transmits
only “yes” or “no” with definite meanings, which belongs to data-communication. In
the early days of telephone history, the switching system is controlled by analog switches.
As technology had advanced enough by the late 1970s where 100% digital systems were
being developed for use in the telephone industry. Digital systems "sample" the analog
signal and handle telephone calls internally as binary digits, then convert them back to
analog to be compatible with regular telephones. This again made the switch smaller and
more reliable. It also allowed new technologies to be added faster by using modular
techniques (adding systems to the original system without complete
redesign/reinstallation) and by using advanced computer software.
1.2.1.3 Emergence of “time-switching”
While traditionally, telephone switches connected physical circuits (e.g., wire pairs),
modern telephone switches use a combination of space- and time-division switching. In
other words, each voice channel is represented by a time slot (say 1 or 2) on a physical
wire pair (A or B). In order to connect two voice channels (say A1 and B2) together, the
telephone switch interchanges the information between A1 and B2. It switches both the
time slot and physical connection. To do this, it exchanges data between the time slots
and connections 8000 times per second, under control of digital logic that cycles through
electronic lists of the current connections. Using both types of switching makes a modern
switch far smaller than either a space or time switch could be by itself.
The structure of a switch is an odd number of layers of smaller, simpler subswitches,

interconnected by a web of wires that goes from each subswitch, to a set of the next layer
of subswitches. In most designs, a physical (space) switching layer will alternate with a
time switching layer. The layers are symmetric, because every call is symmetric (there's a
connection in both directions).
A space-division subswitch uses digital multiplexers controlled by a cyclic memory. This

takes physical space for the wiring.
A time-division subswitch reads a complete cycle of time slots into a memory, and then
writes it out in a different order, also under control of a cyclic computer memory. This
causes some delay in the signal.
1.2.2 Development of VOIP
Telephone systems have been slowly adopting the "IP" (Internet Protocol) technology
over the last decades. Early experiments proved that voice can be converted to digital
"packets" and sent over the Internet. The packets would be collected and converted back
to analog voice. The quality of the calls was not great but it showed that it could be done.
The major problem was something called "packet loss" which is common with TCP/IP
connections.
By the early 2000s, the IP telephony (or "VoIP" - Voice over Internet Protocol) technology
had improved. Using "classes" of service, reliable connections could be obtained and
packet loss reduced to minimum levels. Business systems started using VoIP technology
in their PBX (Private Branch Exchange) switches. The telephones themselves were
almost like small computers that had their own analog/digital conversion systems and
TCP/IP networking technology all the same system. The phone could "piggy-back" on
their existing computer network system. Hence having voice AND data traffic over the
same wires! As we see the history of VOIP, it can be divided into 3 phases:

1.2.2.1 Phase 1 of the VoIP project: early 1998 to 1 October 1999
This phase was to get the VoIP technology working and to test it in a large pilot between
PABXs. During this phase Cisco provided significant support which was to the mutual
benefit of Cisco, CSIRO and AARNet. This phase was completed on 1 October 1999.
Key successes of this phase:
VoIP from PABX to PABX became fully functional, as indicated by the testing and major
pilot implementations.
The VoIP technology acted as a fully transparent ISDN or Q.Sig network to the PABXs.
The Q.Sig included all the advanced PABX features including Call Back, Centralised
Operator, Message Waiting indicator, Calling Name Display as well as Calling Number
Display.
During the initial setup of a voice call the originating PABX was triggered to route the call
to the Public Switched Telephone Network (PSTN) if a problem was encountered in the
data network while setting up the call, without either of the users being aware.
A light weight Network Management program was written to stop VoIP during outages,
usually on microwave links.
The voice quality was near toll quality.
Facsimile traffic was supported up to 14,400 bits per second, i.e. up to ITU G.3.
A Billing System was written that invoiced the caller and generated MIS reports.
CSIRO had seven Gateways that connected PABXs into the AARNet Voice Service. All
Long Distance telephone traffic from CSIRO sites to the major capital cities (not Hobart or
Darwin) was sent via AARNet. Calls to the local call area hopped out of AARNet into a
CSIRO PABX, which then completed the call by making a Local call into the PSTN.
CSIRO was averaging 3,500 calls per working day with an average call duration of 237
seconds per call, with a 90% saving on call charges (60% of CSIRO calls were between
CSIRO sites and thus did not include the Local call charges). Other AARNet Members
were likely to achieve savings of 70% to 80%.
Gatekeepers worked and vastly simplified routing tables.
Key caveats of Phase 1:
Modem traffic WAS NOT SUPPORTED, and was not likely to be in the future.
Past generation Video Conference equipment that relied on clear 64kbps ISDN channels
WAS NOT SUPPORTED. However the H.323 VoIP technology, which was initially
designed to support video, would enable advanced video technology using IP.
1.2.2.2 Phase 2 of the VoIP Project: 1 October 1999 to 2001
This phase was to roll the technology out to all the AARNet Members and to install
Gateways where it was cost effective to do so, that is, there was enough traffic to the
local area to warrant the installation of a Gateway. This phase had several parallel
components:
Installed Gateways to allow Member telephone traffic to hop out of the AARNet Voice
Service at key areas. Initially they were in Canberra, Sydney, Brisbane, Perth, Adelaide
and Melbourne.
Selected a Carrier to carry the Local call from the above Gateways into the Public Switch
Telephone Network (Last one installed October 2000). Public information about the
Tender is available.
Wrote and deployed a Network Monitoring Application AARNet call VoIPMonitor that was
scalable to a network the size of AARNet and stopped VoIP over links that were failing.
Assisted AARNet Members to connect to the AARNet Voice Service.
A loose status of the installation of VoIP at each member institution was maintained.
This phase of the roject suffered a massive delay while negotiating a contract with the
Carrier for the ISDN connections to connect the AARNet Gateway back into the PSTN
(several months). There was also an average 124 day delay waiting for installation (some
3.5 months late).
1.2.2.3 Phase 3 On-going operation
This phase is the ongoing operational component of the project and includes:
support; and dimensioning the network to carry the traffic.
Projects that may begin where this project ends are:
Video over IP;
User directory services for global roaming; and User Authentication and Authorization for
roaming Voice and Video over IP.

1.3 Basic concepts
1.3.1 Basic concepts of data-communication
1.3.1.1 OSI Model
The Open Systems Interconnection Reference Model (OSI Model or OSI Reference
Model for short) is a layered abstract description for communications and computer
network protocol design, developed as part of the Open Systems Interconnect initiative. It
is also called the OSI seven layers model.
The OSI model divides the functions of a protocol into a series of layers. Each layer has
the property that it only uses the functions of the layer below, and only exports
functionality to the layer above. A system that implements protocol behavior consisting of
a series of these layers is known as a 'protocol stack' or 'stack'. Protocol stacks can be
implemented either in hardware or software, or a mixture of both. Typically, only the lower
layers are implemented in hardware, with the higher layers being implemented in
software
The physical layer defines all electrical and physical specifications for devices. This
includes the layout of pins, voltages, and cable specifications. Hubs and repeaters are
physical-layer devices.
The data link layer provides the functional and procedural means to transfer data
between network entities and to detect and possibly correct errors that may occur in the
Physical layer. The addressing scheme is physical which means that the addresses
(MAC address) are hard-coded into the network cards at the time of manufacture
The network layer provides the functional and procedural means of transferring variable
length data sequences from a source to a destination via one or more networks while
maintaining the quality of service requested by the Transport layer. The Network layer
performs network routing, flow control, segmentation/desegmentation, and error control
functions. The router operates at this layer -- sending data throughout the extended
network and making the Internet possible, although there are layer 3 (or IP) switches.
This is a logical addressing scheme - values are chosen by the network engineer. The
addressing scheme is hierarchical.
The transport layer provides transparent transfer of data between end users, thus
relieving the upper layers from any concern with providing reliable and cost-effective data
transfer. The transport layer controls the reliability of a given link. Some protocols are
stateful and connection oriented. This means that the transport layer can keep track of
the packets and retransmit those that fail. The best known example of a layer 4 protocol
is TCP.
The session layer provides the mechanism for managing the dialogue between end-user
application processes. It provides for either duplex or half-duplex operation and
establishes checkpointing, adjournment, termination, and restart procedures. This layer

is responsible for setting up and tearing down TCP/IP sessions.
The presentation layer relieves the Application layer of concern regarding syntactical
differences in data representation within the end-user systems. MIME encoding,
encryption and similar manipulation of the presentation of data is done at this layer. An
example of a presentation service would be the conversion of an EBCDIC-coded text file
to an ASCII-coded file.
The application layer interfaces directly to and performs common application services for
the application processes. The common application services provide semantic
conversion between associated application processes. Examples of common application
services include the virtual file, virtual terminal (for example, Telnet), and "Job transfer
and Manipulation protocol".
Figure 2 OSI Model

Figure 3 OSI Model and its protocols
1.3.1.2 TCP/IP protocol suite
TCP/IP was initially designed to meet the data communication needs of the U.S.
Department of Defence (DOD). In the late 1960s the Advanced Research Projects
Agency (ARPA, now called DARPA) of the U.S. Department of Defence began a
partnership with U.S.universities and the corporate research community to design open,
standard protocols and build multi-vendor networks.
Together, the participants planned ARPANET, the first packet switching network. The
first experimental four-node version of ARPANET went into operation in 1969. These four
nodes at three different sites were connected together via 56 kbit/s circuits, using the
Network Control Protocol (NCP). The experiment was a success, and the trial network
ultimately evolved into a useful operational network, the "ARPA Internet". In 1974, the
design for a new set of core protocols, for the ARPANET, wasproposed in a paper by
Vinton G. Cerf and Robert E. Kahn. The official name for the set of protocols was TCP/IP
Internet Protocol Suite, commonly referred to as TCP/IP, which is taken from the names
of the network layer protocol (Internet protocol [IP]) and one of the transport layer
protocols (Transmission Control Protocol [TCP]).
TCP/IP is a set of network standards that specify the details of how computers
communicate, as well as a set of conventions for interconnecting networks and routing
traffic. The initial specification went through four early versions, culminating in version 4
in 1979.
Figure 4 TCP/IP protocol
1.3.1.3 IPv4 Address Introduction
For a node in the network, the Internet protocol address (IP address for short) is a logic
address. It is independent from any network hardware and network configuration. It has
the same format no matter the type of the physical network. An IP address is a 4-byte
number, which is actually composed of two parts: the first part is the IP network No. while
the second part is the host No. Generally, such a 4-byte IP address is separated with
small dots, in which each byte is indicated with a decimal number. For example: for
130.130.71.1, the network No. is 130.130 and the host No. is 71.1.
Figure 5 IP address example
IP addresses can be divided into five classes, i.e., Class A, Class B, Class C, Class D
and Class E. Indicates with binary codes, the highest bit of Class A addresses is 0; the
highest two bits of Class B addresses are 10; the highest three bits of Class C addresses
are 110; the highest four bits of Class D addresses are 1110; and the highest five bits of
Class E addresses are 11110. Since Class D addresses are only used in special

definition of the host group and Class E addresses are reserved for future use, only one
type in Class A, B and C addresses can be allocated for a specific network.
Figure 6 IP address illustration
IP地址
32 bits
Dotted
Decimal Network Host
Maximum 255 255 255 255

1 8 9 16 17 24 25 32
Binary 11111111 11111111 11111111 11111111
8
4
2
1
128
64
32
16
128
64
32
16
8
4
2
1
64
32
16
8
4
2
1
64
32
16
8
4
2
1
128
128
Example
Decimal 172 16 122 204
Example 10101100 00010000 01111010 11001100
Binary
中兴通讯学院 www.
www.univ
www.univ .zte.com.
univ.zte.com.cn
.zte.com.cn
The IP addressing mechanism allows three types of possible network configuration. IP
addresses are the basis for inter-node communication that uses the IP protocol. This is
true for either the private TCP/IP network or public Internet.
If a user does not hope to add a network to the public Internet, the user can select IP
addresses by forced stipulation. If this method is adopted, the IP addresses for all nodes
on this network should meet the following stipulations:
1. The network No. part of each IP address is the same;
2. The IP address of each node on the network should be sole.
The highest bit 0 of a Class A address and its subsequent 7 bits belong to the network No.
part; while the remaining 24 bits indicate the intra-net host No. In this case, there may be
126 Class A networks in an interconnected network (network No. ranging between 1~126.
0 and 127 are reserved). While in a Class A network, there may be 16,000,000 nodes.
Therefore, Class A addresses are only used in very large regional networks, e.g., MLNET
in the U.S. and some large-scale commercial networks.
The highest two bits 10 of a Class B address and the subsequent 14 bits belong to the
network No. part; while the remaining 16 bits indicate the intra-net host No. In this case,
there may be about 16,000 Class B networks. While in a Class B network, there may be
more than 65,000 nodes. Class B addresses are generally used in networks constructed
by large institutions and companies.
The highest three bits 110 of a Class C address and the subsequent 21 bits belong to the
network No. part; while the remaining 8 bits indicate the intra-net host no. In this case, an
interconnected network is allowed to include 2,000,000 Class C networks. In each Class
network, there can be a maximum of 254 nodes. Class C addresses are used in
small-scale institutions and companies.
If you do not like to use the binary system, you can also divide the three types of
networks according to the decimal numbers of the first bytes of IP addresses. Class A
address range between 1~126; Class B addresses range between 128~191; and Class C
addresses range between 192~223.
As in the convention, when the binary codes of the entire network No. part (the first byte
for Class A; the first two bytes of Class B; and the first third bytes for Class C) are all
zeros, the network No. is considered as the local network; when the binary codes of the
host No. part (the last three bytes for Class A; the last two bytes for Class B; and the last
byte of Class C) are all ones, the host No. is considered as the broadcast address within
the local network.
Figure 7 IP address classes

IP地址分类
8 bits 8 bits 8 bits 8 bits
• Class A: Network
Network Host Host
Host Host
• Class B: Network
Network Network Host
Host Host
• Class C: Network
Network Network Network Host
• Class D: Multicast
• Class E:
Research
中兴通讯学院 www.
www.univ
www.univ .zte.com.
univ.zte.com.cn
.zte.com.cn
1.3.1.4 Network category
Local Area Networks:
Local Area Networks (LANs) accommodate users within a building or on a campus.

Ethernet is the leading network technology for LANs or networks contained in buildings or
on a single site. Ethernet was first implemented as a shared network using hubs, but high
usage caused congestion that could dramatically slow or even shut down the network.
Subsequently Ethernet was implemented using a switched architecture scaling
performance of the network. The Ethernet ports operated in full duplex, gradually the
speed increased form 10 Mbps to 10 Gbps, packet processing at higher layers and
routing were added.
Wide-Area Networks and Remote Access:

Wide-Area Networks (WANs) connect LANs in campuses across cities, states, and
countries. Remote access refers to the connection of an individual user or very small
branch office to the central network. A single user can dial up the corporate network
directly or gain access via the Internet. Internet Service Providers (ISPs) aggregate
multiple users through a router to the campus. In general, LAN speeds are greater than
WAN and remote-access speeds. WAN technologies:
1. Dedicated and Dial-Up Access
2. Integrated Services Digital Network (ISDN)
3. Asynchronous Digital Subscriber Line (ADSL)
4. Cable Access
5. Wireless Access
Metropolitan Area Network:
Metropolitan Area Networks (MANs) channel traffic within the metro-domain (i.e.,
inter-business, inter-office, metropolitan connectivity) to and from large long-haul POPS
(points of presence). With the successful deployment of many long-haul fiber networks,
the focus has shifted towards MANs. The goal is to bring the cost benefits and networks
efficiencies of the optical networking to end-users wanting to link campuses with
multi-gigabit LANs.
1.3.2 xDSL Access Technology
In 1988, Bellcore first advanced the concept of digital subscriber loop.
Now, China has 420 million telephone subscribers, which are all connected to the
network through copper wires. Such a huge hardware basis is the best platform that
allows the DSL technology to exhibit its advantages. In addition, DSL access does not
need any modification to the line, reducing additional cost. Therefore, to provide Internet
access through copper telephone wires are more appealing to subscribers.
The Digital Subscriber Loop (DSL) is the combination of the transmission technologies
that use copper telephone wires as the media. In other words, copper subscriber line is
used to implement broadband access, to allow high-speed data to be transmitted on the
copper cable. Such technologies are collectively called xDSL, where “x” represents
different type of digital subscriber line loop technologies, including HDSL, SDSL, IDSL,
VDSL and ADSL.
DSL technologies differ in that signal transmission speeds vary depending on the
transmission distance, whether the uplink rate and the downlink rate are symmetric, and
different DSL technologies can be used in different cases.
The xDSL technology falls into the rate symmetric category and the rate asymmetric
category, depending on whether the uplink rate (from the subscriber to the Telecom office)
and the downlink stream (from the Telecom office to the subscriber) are the same. The
symmetric category consists of HDSL, SDSL and IDSL; the asymmetric category
consists of ADSL, VDSL and RADSL.
Table 1-1 compares a few xDSL technologies.
Table 1-1 Comparison of xDSL Technologies
Downlink Uplink
DSL Rate Rate Transmission Line Splitter
Type Distance (km) Pair Required
(bit/s) (bit/s)
HDSL 2.048M 2.048M 5 (up to 12km, when 2 No
an amplifier is used)
SDSL 2.048M 2.048M 5 (depending on the 1 No
coding method used
and the quality of the
line)
IDSL 128 k 128 k 5.5 1 No
ADSL 8M 768 k 5 (at full rate) 1 Yes
RADS 8M 768 k 5 1 Yes
L
VDSL 13.6M or 6M or 1.5 1 Yes
56M 13M
HDSL can implement symmetric transmission of 2Mbit/s signals on two pairs of

twisted-pair cables; SDSL can implement symmetric transmission of 2Mbit/s signals on
one pair of twisted pair cables; similar to the basic rate interface of ISDN, IDSL can
continue to use the terminal equipment of ISDN, to provide bi-directional transmission of
integrated data, voice at 128kbit/s; VDSL can provide transmission rates up to 50Mbit/s
(downlink) and 1.5Mbit/s (uplink) within 300m; while, ADSL is an excellent type of xDSL
technology, and the is first choice xDSL technology for broadband Internet access.
ADSL uses common twisted pair copper wires, and its uplink rate and downlink rate are
asymmetric. It provides rates and transmission distance very suitable for broadband
access. ADSL is developed initially for the purpose of using twisted pair copper wires to
implement VoD services. However, now ADSL is primarily driven by the demands for
high-speed Internet access. ADSL provides a leased access method as different from
dial-up access when used for Internet access, offering a good solution to the problem of
telephone network congestion due to dial-up Internet access. In theory, ADSL can
implement data transmission at a downlink rate of 8Mbit/s and uplink rate of 1M/bits
within the range of 5km, and can provide voice and data services at the same time. In
addition, the actual rate of ADSL is adaptive automatically, based on the condition of the
subscriber line and the transmission distance. In addition to the standard ADSL, a “Light
ADSL”—G.lite, which is only for data transmission (no voice division) (providing up to

1.5Mbit/s downlink bandwidth) and is cheaper, is starting to appear in the market. G.lite
can be built as a PCI card, which can be directly inserted into a PC.
1.3.2.1 ADSL2+
ADSL2+ is a new generation of ADSL broadband access technology, applying to the

transmission with asymmetric rate. ADSL2+ is compatible to ADSL. In addition, it has the
features below:
Adding new operation mode
ADSL supports three operation modes.
annex A: It stands for ADSL over POTS, with POTS service on the same pair of
lines.
annex B: It stands for ADSL over ISDN, with ISDN service on the same pair of lines.
annex C: The ADSL service exists in the environment with TCM-ISDN interference.
Except the above three modes, ADSL2+ supports the three modes below.
annex I: It is compatible to the complete digital mode of ADSL over POTS (annex A)
frequency spectrum. The available uplink band can be expanded as 3 kHz to 138
kHz if there is no POTS service on the line. It supports 31 sub-bands at the
maximum. The utmost uplink rate exceeds 1 Mbit/s.
annex J: It is compatible to the complete digital mode of ADSL over ISDN (annex B)
frequency spectrum. The available uplink band can be expanded as 3 kHz to 276
kHz if there is no ISDN service on the line. It supports 64 sub-bands at the maximum.
The utmost uplink rate reaches to 2.3 Mbit/s.
annex M: It is ADSL over POTS with the uplink bandwidth expanded. The uplink
sub-band starts from 6. The sub-bands ends at 32, 36, 40, 44, …, 63 according to
different bandwidth requirements. The total transmission power keeps the same. In
this way, 3 M uplink rate is available. For the downlink, there are overlap and
non-overlap, similar to annex B.
Higher rate
Compared with ADSL, ADSL2+ supports higher rate, wider frequency and more
sub-bands (512 sub-bands). The maximum downlink rate can reach to 24 Mbit/s. If
ADSL2 annex J is used, the uplink rate is increased to 2.3 Mbit/s.
Longer transmission distance
ADSL2+ supports longer transmission distance. For ADSL, the longest transmission
distance is less than 6 km. For ADSL2+, the longest transmission distance is 7 km in
theory.
Lower power consumption
ADSL2+ provides power management function, as shown below;
Reduce the noise tolerance beyond requirements by decreasing transmission

power consumption. Decrease useless power consumption on the precondition of
ensuring stable operation.
Add the low consumption mode L2 mode. Decrease the transmission power
consumption in case that no user data is transmitted. Ensure the necessary power
consumption for transmitting required management message and synchronous
signal. Resume the power consumption when user data is transmitted. The power
consumption of DSLAM is about 30% of that in usual operation when it is running in
L2 mode.
The central office (CO) and customer premises equipment (CPE) of ADSL2+ has
the function of power cut back. The power attenuation ranges from 0 dB to 40 dB.
The transmission power consumption can be effectively cut down when the
transmission power is too large, ensuring the normal receiving of data.
More stable running capability and frequency compatibility
ADSL2+ has a more stable running capability and frequency compatibility, as shown
below:
The carrier sequence and pilot tone the receiver decided upon the channel analysis
results can truly reflect the channel situation and select the best tone as the pilot,
useful to stable ADSL connection.
In training, the receiver can test RFI distribution by RFI closing tone channels or
control the transmit power of tone through CO-MIB, effectively avoiding RFI and
reducing the interference on the ambient devices.
Fine dynamic adaptability
The bit swap is enhanced and the line rate can be changed seamlessly and
dynamically in the status of keeping show time, enhancing the adaptability to
changeable line parameters.
The training is shortened. It takes a little time to resume connection from mistakes.
Line diagnosis function
ADSL2+ supports test function at both ends. Parameters below can be tested.

Line transmission feature
Background noise power spectrum
Signal-noise ratio of each sub-band
Noise tolerance and bearable bits of each sub-band
Reachable connection rate
Better interworking capability
Based on different functions, ADSL2+ classifies ADSL transceivers into TPS-TC

(transmission protocol related convergence sub-layer), PMS-TC (physical medium
related convergence sub-layer), PMD (physical medium related sub-layer) and
MPS-TC (management protocol related convergence sub-layer, used for NM
interface). Encapsulating each sub-layer and defining the message among
sub-layers help implement interworking of various devices from different factories.
1.3.2.2 SHDSL
G.SHDSL is an ITU-T standard for symmetrical high bit rate digital subscriber loop.
G.SHDSL has some advantages over other DSL technologies. It supports symmetric
variable rates of 192 kbps ~ 2.036 Mbps over a pair of copper cables, and has a
transmission distance longer than other DSL technical products. The core technology of
G.SHDSL is close to the HDSL2 standard of the current ANSI T1.418. The modulation
technology of G.SHDSL is called TC/FONT>PAM (Trellis Coded Pulse Amplitude
Modulation). Being rate/distance adaptive, G.SHDSL is superior in performance to the
2B1Q technology-based HDSL standard, and matches ADSL in complying with the
G.991.2 standard. The G.SHDSL standard provides a detailed description of time division
multiplex (TDM) and ATM network adaptability. SHDSL equipment supports TDM and
ATM operations, and SHDSL will also continuously find application in ATM-based
networks.
The G.SHDSL products are more suitable for small commercial users that need
symmetrical services. The G.SHDSL technology supports multi-channel access of
telephone, data and videoconferences, supports long-distance LAN access, and
subscriber leased line services.
SHDSL technology provides high-speed symmetric data service on a pair of twisted pairs
or two pairs of twisted pairs.
Overview
For SHDSL with a single pair of twisted pairs, the transmission rate ranges from 200kbit/s
to 2312kbit/s. The rate adjustment granularity is 64kbit/s. For SHDSL with two pairs of
twisted pairs, the transmission rate ranges from 400kbit/s to 4624kbit/s. The rate
adjustment granularity is 128kbit/s. SHDSL can automatically adjust to a reasonable rate
upon the line condition, such as the influence of distance and noise whatever it is a single
pair of twisted pairs or two pairs of twisted pairs.
1.3.2.3 VDSL
VDSL (Very High Speed Digital Subscriber Line) is one of the technologies to
provide high-bandwidth access, applying to the transmission with symmetric
rate. Overview: VDSL transmits high-speed data through the existing
subscriber telephone line. It provides voice, video and data through multimedia
network. VDSL transmits the voice service and data service simultaneously on
the same subscriber line with the frequency division multiplexing (FDM) mode.
At the both ends of the subscriber line, the splitter is used to separate the voice
signal from the data signal. The VDSL band is independent of POTS service
band, therefore, there is not any influence on POTS service and it is not
required to make any change on the network distribution. VDSL provides the
transmission rate of 68 Mbit/s for downlink and 45 Mbit/s for uplink. With 0.4 mm diameter,
the transmission can reach to 3.5 km. VDSL band is divided into the uplink band and the
downlink band. In addition, it has a certain protection band, effectively avoiding the band
of amateur broadcasting station.
Function Features:
Comply with VDSL standard YD/T 1239-2002 Access Network

Requirement----Very-High-Speed Digital Subscriber Line (VDSL) System issued by
the national telecommunications industry department. Support the standards below:
ETSI TS 101270-2 V1.1.1 (2002-2) and ITU-T VDSL Standard (G.993.1,
26-Oct.-2001)
Employ the discrete multitone (DMT) modulation mode.
Employ FDM uplink/downlink band division mode.
The transmission mode can be symmetric or asymmetric.
Automatically adjust rate upon the line condition while initialization.
Query and configure parameters of VDSL line, including uplink/downlink rate, noise
tolerance, output power and line attenuation.
Support line alarm maintenance and message report function.
As the development of internet, VDSL couldn’t meet the user’s requirement. Then
VDSL2 is born.
VDSL2 was consented by the ITU in May 2005 and is designed to increase both
rate and reach over the copper network achieving data rates in excess of 25 Mbps
over long loops (4-6kft) and symmetrical data rates of 100 Mbps over short loops

(<1kft). The new VDSL2 standard includes many of the features and functionality
contained in the ADSL2+ standard, including advanced diagnostics, a common
management interface and the ability to maximize the use of bandwidth and bit rate,
making it an ideal access technology for delivering video.
VDSL2 has numerous configuration profiles to meet regional service provider

requirements. The frequency bandwidth of VDSL2 has increased from 1.1 and 2.2
MHz for ADSL and ADSL2+ respectively with configuration options at 8.5MHz,
12MHz, 17.7MHz and 30 MHz. VDSL2 also allows the frequency range between 12
to 30 MHz to be used for upstream and downstream to achieve symmetrical rates.
1.3.3 FTTX
FTTX is the all-inclusive term for access technologies which use fiber-optics.
Fiber-to-the-X (FTTX) refers to several marketplaces, Optical Access portion of the
network will bring: Fiber to the Home (FTTH), Fiber to the Business (FTTB) ,Fiber to the
Curb or Cabinet (FTTC), i.e. to a service node in a nearby location outside the customer
premises
FTTx bring us many advantages:
Less expensive: Several miles of optical cable can be made cheaper than
equivalent lengths of copper wire. This saves your provider (cable TV, Internet) and
your money.
Thinner: Optical fibers can be drawn to smaller diameters than copper wire.
Less signal degradation: The loss of signal in optical fiber is less than in copper wire.
Light signals: Unlike electrical signals in copper wires, light signals from one fiber do
not interfere with those of other fibers in the same cable. This means clearer phone
conversations or TV reception.
1.3.4 PON
Optical access networks include positive optical network and passive optical network
(PON), the latter of which has a more appealing prospect in access networks. PON
further includes narrowband optical network and BPON/EPON/GPON. Common PON
equipments are ONUs (Optical Network Unit), optical network terminals, optical line
terminals, optical dividers and fibers.
In terms of network structure, PON often uses passive double-star or tree architecture,
and uses special point-to-multipoint multiple access protocols to allow multiple ONUs to
share optical fiber line terminals and allow multiple subscribers to share ONUs, reducing
the initial cost for building the optical access network.
1.3.5 H.248 Overview
H.248 (Media Gataway Control Protocol or Megaco as coined by IETF ) is an

implementation of the Media Gateway Control Protocol architecture for controlling Media
Gateways on Internet Protocol (IP) networks and the public switched telephone network
(PSTN). The general base architecture and programming interface was originally
described in RFC 2805 and the current specific Megaco/H.248 definition is ITU-T
Recommendation H.248.1.
Megaco/H.248 defines the protocol for Media Gateway Controllers to control Media
Gateways for the support of multimedia streams across computer networks. It is typically
used to provide Voice over Internet Protocol (VoIP) services (voice and fax) between IP
networks and the PSTN, or entirely within IP networks.
The protocol was the result of collaboration of the MEGACO/H.248 working group of the
Internet Engineering Task Force (IETF) and International Telecommunication Union
ITU-T Study Group 16. The IETF originally published the standard as RFC 3015, which
was later replaced by RFC 3525. The term Megaco/H.248 is the IETF designation. The
ITU later took ownership of the protocol and IETF's version has been reclassified as
historic. The ITU has published three versions of H.248.1, the most recent in September
2005.
H.248 encompasses not only the base protocol specification in H.248.1, but many
extensions defined throughout the H.248 Sub-series.
Another implementation of the Media Gateway Control Protocol architecture exists in the
similarly named MGCP protocol. This is used over the same interface and similar in
application and service functionality, however, it is a different protocol and the underlying
differences make them incompatible.
This makes possible to implement services like voice-enriched e-commerce, web page
click-to-dial or Instant Messaging with buddy lists in an IP based environment.
There are a number of competing protocols, including MGCP (the combination of SGCP
and IPDC) and MDCP. This protocol is considered complementary to H.323 and SIP, in
that an MGC will control MGs using H.248, but will communicate between one another
via H.323 or SIP.

2 ZXA10 C300M/C350M Introduction
2.1 Product Position

• Multiplay service offering various bundled high-speed data, voice and video services
to the subscribers is becoming a driving force for growth in the domain of access
network. To meet all these challenges, ZTE launches an integrated optical-copper
multi-service access equipment solution consisting of ZXA10 C300M/C350M
products, which guarantees full integrated broadband and narrowband access
services in various application scenarios. The ZXA10 C300M is a large-capacity
device, and the ZXA10 C350M is a medium-capacity device. ZXA10 C300M/C350M
can be deployed as an OLT, IP DSLAM, MSAN, AG, MDU or any mixed role of
above.
Figure 1 shows the ZXA10 C300M/C350M in the network.
Figure 1 ZXA10 C300M/C350M in the Network
POTS: Plain Old Telephone Service ISDN: Integrated Services Digital Network
BRA: Basic Rate Access PRA: Primary Rate Access
PBX: Private Branch Exchange NT: Network Terminal
CPE: Customer Premises Equipment FXO: Foreign Exchange Office-side
ADSL: Asymmetric Digital Subscriber Line VDSL: Very High Speed Digital Subscriber Line
SHDSL: Single-pair High Digital Subscriber Line MDU: Multiple Dwelling Unit
ONT: Optical Network Terminal GPON: Gigabit Passive Optical Network
P2P: Point to Point NGN: Next Generation Network
GPON: Gigabit Passive Optical Network IMS: IP Multimedia Subsystem
HLR: Home Location Register IPTV: Internet Protocol Television
The ZXA10 C300M/C350M supports various kinds of access services, from

narrowband services to GPON/P2P access services:
• Voice services
→ Voice services in NGN/IMS based on H.248 and SIP, including

POTS/ISDN voice, FAX, MODEM, PBX, and various
supplementary services.
→ Voice services in conventional PSTN based on V5.2, including

POTS/ISDN voice, FAX, MODEM, PBX, and various
supplementary services.
• Leased line services
Leased line services based on E1 or SHDSL.TDM, providing

N×64K/E1 private line.
• Broadband access services
→ Broadband access services based on copper, such as

ADSL2/2+, VDSL2, and SHDSL.bis, with enhanced DSL
features like system level vectoring of VDSL2.
→ Broadband access services based on fiber, such as GPON,

XG-PON1 and P2P FE/GE.
2.2 Features
2.2.1 Narrowband Service Features

2.2.1.1 VoIP Service Features
For a description of the VoIP service features, refer to Table 1.
Table 1 VoIP Service Feature Descriptions

Fea Description
ture
Su • H.248 v3
pp • SIP
ort • IUA
ed • V5UA
pro • SCTP
toc • RTP and RTCP
ols • V5.2 interface in PSTN
• Voice Coding Schemes: G.711 a-law/µ-law; G.726; G.723.1.

VoI • Voice Quality Techniques: Echo cancellation (G.165/G.168); Voice Activation Detection
P (VAD); Comfortable Noise Generation (CNG); DTMF relay (RFC 2833); Packet Loss
tec Compensation (PLC); Jitter Buffer Dynamic Adjustment; Tx/Rx Gain Control.
hn • Stream separation and tagging features: Different VLANs or Class of Service (CoS) or
olo Type of Service (TOS) or Differentiated Service Code Point (DSCP) for VoIP media,
gie signaling, management, broadband and stream.
s • Voice service related traffic monitoring.
• Quality monitoring of VoIP service.
• Basic PSTN/ISDN voice service.

• Supplementary services, including Call Forwarding on Busy (CFB), Call Forwarding
Unconditional (CFU), Call Forwarding on No Reply (CFNR), Calling Line Identification
PO Presentation (CLIP), Calling Line Identification Restriction (CLIR), Abbreviated Dialing
TS (AD), Absentee Service (AB), Automatic Call Memory Service (ACM), Automatic Redial
/IS Service (AR), Call Waiting (CW), Collection Call Screening (CCS), Distinctive Ringing
DN Service (DR), Do-Not-Disturb Service (DND), Hot Line Service (HOT), Outgoing call
ser Screening (OCS), Wake-up Service, Three Party Call Service, and Conference Call
vic Service.
es • FoIP: T.30 Voice Band Data (VBD) mode , T.38 relay mode.
• MoIP.
• IP Centrex Service.
• PBX access service.
An
alo
g
su
bs
cri • Metallic line test features, such as AC voltage test, DC voltage test, insulating resistance
ber test, capacitance test, loop resistance test, loop current test, and feeding current test.
lin • Service availability test features, such as dial tone test, ring subscriber test, and DTMF
e signal test.
tes
t
fea
tur
es
Voi
ce • Supports authentication when connecting to MGC.
ser • Dual Homing, that is, the ZXA10 C300M/C350M is configured to connect four MGCs, one
vic is active and the others are standby. When the active MGC is down, the ZXA10
e C300M/C350M can automatically register to standby MGC without service interruption.
reli • Uplink protection technologies, including RSTP, Link Aggregation, UAPS and ERPS.
abi • Hairpin function, for the communication between the subscribers in the same MSAN,
lity which is adopted to switch directly in TDM domain, no need the procedure of VoIP
en transformation.
ha • Overload control capability, according to CPU load, VoIP channels, and bandwidth.
nc • Stand alone function (also called self switching, internal switching without MGC), when the
em connection to MGC is broken or MGC is down, the ZXA10 C300M/C350M supports self
ent switching so that subscribes in the same ZXA10 C300M/C350M can communicate with
fea each other. When the connection to MGC is recovered, the ZXA10 C300M/C350M
tur automatically registers to MGC and restores normal state.
es
2.2.1.2 Leased Line Service Features
For a description of the leased line service features, refer to Table 2.
Table 2 Leased Line Service Feature Descriptions

Fea Description
ture
Le
as
ed
lin • N × 64K leased line service
e • E1 leased line service
ser
vic
es
Us
er-
sid
e • E1 interface
int • SHDSL.TDM interface
erf
ac
e
Ne
tw
ork
-si
• Native E1 interface for CSN
de
• IP/MPLS interface with PWE3 technology for PSN
int
erf
ac
e

2.2.2 Broadband Service Features
For a description of the broadband service features, refer to Table 3.
Table 3 Broadband Service Feature Descriptions

Fea Description
tur
e
Br
oa
db
• ADSL/ADSL2/ADSL2+ access interface
an
• VDSL2 access interface
d
• VDSL2 access interface with system level vectoring function
ac
• SHDSL access interface
ce
• GPON OLT access interface
ss
• XG-PON1 OLT access interface
int
• P2P GE access interface
erf
ac
es
• MAC address management

• MAC address learning
• VLAN management
La • Basic VLAN (802.1q)
ye • QinQ and 802.1ad VLAN
r2 • 1:1 VLAN forwarding
fe • N:1 VLAN forwarding
at • VLAN translation and Selective QinQ
ur • Layer 2 forwarding policy
es • Layer 2 Traffic classification
• VLAN switching policy
• Bridging
• TDM PWE3
• Layer 3 VLAN interface, Loopback interface

La • ARP
ye • ARP proxy
r3 • DHCP relay agent with option82
fe • DHCP option 60
at • Static routing
ur • RIP v2 dynamic routing
es • OSPF v2 dynamic routing
• IS-IS dynamic routing
M
ult • Multicast VLAN management
ic • IGMPv2/v3 snooping
as • IGMPv2/v3 proxy routing
t • Multicast channel management
fe • Multicast user management
at • Multicast Channel Access Control (CAC)
ur
es
Q • Traffic classification
oS • Traffic policing
fe • Traffic management
at • Congestion management
ur • Queue scheduling with SP, WRR or SP + WRR
es • HQoS
N
et
w
or • STP
k • RSTP
re • MSTP
sili • LAG with LACP
en • GPON type B/type C redundancy
ce • Ethernet UAPS (uplink)
fe • ERPS (ITU-T G.8032)
at
ur
es
• IPv6 basic features

IP
• IPv6 layer 2 forwarding
v6
• IPv6 static route
fe
• ICMPv6 with Neighbor Detection, Ping
at
• DHCPv6 Lightweight DHCPv6 Relay Agents (LDRA) with Option18/37
ur
• DHCPv6 Layer 3 Relay Agent
es
• IPv6 ACL
2.3 Hardware Architecture
2.3.1 ZXA10 C300M Shelves
2.3.1.1 ETSI 21-inch Shelf
Figure 1 shows the ETSI 21-inch shelf shelf. Its dimensions are 449 mm × 535 mm ×
270 mm (Height × Width × Depth). The distance between the panel and the ear
mounting surface is 217 mm.
Figure 1 ETSI 21-inch Shelf Outline

Figure 2 shows the slot number and card allocation for the ETSI 21-inch shelf.
Figure 2 Slot Number and Card Allocation for ETSI 21-inch Shelf
Table 1 describes the shelf configuration.
Table 1 ETSI 21-inch Shelf Configuration

Slot Card
0/1 Power card (for mutual power assistance)
2~9, 12~19 Subscriber card
10/11 Switching and control card
20 Narrowband subscriber card or CIC card
21/22 Uplink card
Note:
Width of Slot 0/1/10/11/21/22 is 25 mm. Width of other slots is 22.5 mm.
Figure 3 shows the ETSI 21-inch splitter shelf. Its dimension is 399 mm × 535 mm ×
Figure 3 ETSI 21-inch Splitter Shelf Outline
The splitter cards are installed in the splitter shelf. Figure 4 shows the ETSI 21-inch

splitter shelf configuration.
Figure 4 ETSI 21-inch Splitter Shelf Configuration
2.3.1.2 IEC 19-inch Shelf
Figure 5 shows IEC 19-inch shelf. Its dimensions are 443.7 mm × 482.6 mm × 270
mm (Height × Width × Depth). The distance between the panel and the ear mounting
surface is 217 mm.
Figure 5 IEC 19-inch Shelf Outline
Figure 6shows the slot number and card allocation for the IEC 19-inch shelf.
Figure 6 Slot Number and Card Allocation for IEC 19-inch Shelf
Table 2 describes the IEC 19-inch shelf configuration.
Table 2 IEC 19-inch Shelf Configuration

Slot Card
0/1 Power card

18 Narrowband subscriber card or CIC card
19/20 Uplink card
Note:
Width of Slot 0/1/10/11/19/20 is 25 mm. Width of other slots is 22.5 mm.
Figure 7 shows the IEC 19-inch splitter shelf. Its dimension is 399 mm × 482.6 mm ×
Figure 7 IEC 19–inch Splitter Shelf Outline
The splitter cards are installed in the splitter shelf.Figure 8 shows the IEC 19–inch
splitter shelf configuration.
Figure 8 IEC 19–inch Splitter Shelf Configuration
2.3.2 ZXA10 C350M Shelf

Figure 1 shows the C350M shelf. Its dimensions are 263.9 mm × 482.6 mm × 240
mm (Height × Width × Depth).
Figure 1 ZXA10 C350M Shelf Outline
Figure 2 shows the card slot number and card allocation for the ZXA10 C350M shelf.
Figure 2 Slot Number and Card Allocation for ZXA10 C350M

Table 1 describes the shelf configuration.
Table 1 ZXA10 C350M Shelf Configuration

Slot Card
0/1 Uplink card
6/7 Switching and Control card (active/standby)
10 Common interface card/CIC
11/12 Power card (for mutual power assistance)
The C350M shelf adopts the front leading-out mode. The subscriber cables,
monitoring cables, and maintenance cables are led out from the front panel and
connected to the MDF.
2.4 Cards
The ZXA10 C300M/C350M shelf is composed of cards and a fan set. Table 1lists all the
cards supported.
Table 1 ZXA10 C300M/C350M Cards
Type Name Description Remark

• System kernel of services and management
• Local and remote OAM
SCXN • Active / Standby redundancy
• Support load sharing mode
• 10 GE to any subscriber card

Switchin switching
g and and
Control control
SCGM
card card
• Active / Standby redundancy
• GE to any subscriber card

SCXMC
• Active / Standby redundancy
• 10 GE to any subscriber card
• Each system switching and control card supports

one VOPSE card
• VOIP process resources：

256 lines G.711 /20
VOPSE
or 80 lines G.723.1
or 100 lines G.729a
or 128 lines G.726 /20
Voice or 80 lines T.38 Fax
VoIP or 256 lines G.711 VBD
processor
daughter
daughter- • Each system switching and control card supports
-card
card one VOPSF card
• VOIP process resources：

512 lines G.711 /20
VOPSF
or 170 lines G.723.1
or 256 lines G.729a
or 256 lines G.726 /20
or 170 lines T.38 Fax
or 512 lines G.711 VBD
Precise
Clock
Clock • Support Precise Time Protocol
Processin
daughter CKWSA
g
-card • Working with SCXN/SCXM only
daughter-
Card


System
Service Level
Support system level G.Vector function
Processi SVWM Vectoring
384 channels (64×6)
ng Card Process
Card
• 64 POTS service channels

64-port
POTS • Built-in MELT
PTWV
subscriber
card • Supports both polarity reversal and metering
pulse functions
• 64 POTS service channels
• Built-in MELT
64-port
POTS • Supports both polarity reversal and metering
PTWVN
subscriber pulse functions
card
• Same functions as PTWV except minor
difference on the location of subscriber cable
outlets
16-port
• 16 ISDN BRA service channels
ISDN BRA
DBWD
subscriber
• 2B1Q encoding mode
card
Narrowb
16-port
and
SHDSL • 16 SHDSL TDM service channels
subscrib
and E1
er card
DSWB (balanced • 16 E1 (balanced interface) service channels
interface)
subscriber • ISDN PRI or Leased line
card
16-port
SHDSL
• 16 SHDSL TDM service channels
and E1
(unbalanc
DSWU • 16 E1 (unbalanced interface) service channels
ed
interface)
• ISDN PRI or Leased line
subscriber
card
16-port • 16 SHDSL TDM service channels

SHDSL
and E1 • 16 E1 (balanced interface) service channels
DSWC (balanced
interface) • ISDN PRI or Leased line
subscriber
card • Support TDM PWE3
DSWD 16-port • 16 SHDSL TDM service channels

SHDSL
AND E1 • 16 E1 (unbalanced interface) service channels
(unbalanc
ed • ISDN PRI or Leased line
interface)
subscriber • Support TDM PWE3
card
• 64 ADSL2+ over POTS service channels (need

external splitters)
• Recommended splitter card: PWVNA / PWVNE

64-port
• G.992.1 ANNEX A, G.992.3 ANNEX A/L/M,
ADSL2+
G.992.5 ANNEX A/M
over
or
POTS/ISD
• 64 ADSL2+ over ISDN service channels (need
N
external splitters)
subscriber
AMWV
card with
• Recommended splitter card: IWVNA
MELT
function
• G.992.1 ANNEX B, G.992.3 ANNEX B, G.992.5
(without
ANNEX B
built-in
splitters)
• SELT, DELT, and MELT
• Up to 4-pair bonding
• Wetting Current
Broadba
nd • 64 ADSL2+ over ISDN service channels (built-in
subscrib 64-port splitters)
er card ADSL2+
over ISDN • G.992.1 ANNEX B, G.992.3 ANNEX B, G.992.5
ANWV subscriber ANNEX B
card with
built-in • SELT, and DELT
splitter
• 64 ADSL2+ over POTS service channels (built-in

splitters)
64-port
ADSL2+
subscriber
APWV G.992.5 ANNEX A/M
card with
built-in
• SELT, and DELT
splitter
64-port • 64-port ADSL2+ over POTS service channels

ADSL2+ (need external splitters)
ASWV over
POTS • Recommended splitter card: PWVNA / PWVNE
subscriber


card • G.992.1 ANNEX A, G.992.3 ANNEX A/L/M,
(without G.992.5 ANNEX A/M
build-in
splitters) • SELT, and DELT
• G.INP
• 2-pair bonding
• 64 VDSL2 over ISDN service channels (need

external splitters)
64-port • Recommended splitter card: IWVNA

VDSL2
over ISDN • G.993.2 17A US0-ANNEX B
subscriber
card with • SELT, DELT, and MELT
VIWV
MELT
function • G.INP
(without
build-in • INM
splitters)
• SOS
• 2-pair bonding
• 32 VDSL2 over POTS service channels (need

external splitters)
32-port
• Recommended splitter card: VWVNA/VWVNE
High
Performan
• G.993.2 30A
ce VDSL2
over
• SELT, DELT and MELT
POTS
VMWG subscriber
• G.INP
card with
MELT
• INM
function
(without
• SOS
build-in
splitters)
• 2-pair bonding
• Wetting Current
64-port • 64 VDSL2 over POTS service channels (need

VDSL2 external splitters)
over
POTS • Recommended splitter card: VWVNA/VWVNE
VMWVS subscriber
card • G.993.2 17A US0-ANNEX A
(without
built-in • SELT, and DELT
splitters)

• G.INP
• INM
• SOS
• 2-pair bonding

external splitters)
• Recommended splitter card: VWVNA/VWVNE

64-port
VDSL2
• G.993.2 17A US0-ANNEX A
over
POTS
subscriber
VMWVC card with
• G.INP
MELT
function
• INM
(without
built-in
• SOS
splitters)
• 2-pair bonding
• Wetting Current

external splitters)
• Recommended splitter card: PWKNA/PWKNE

48-port
VDSL2
over
POTS
subscriber
VMWKC card with
• G.INP
MELT
function
• INM
(without
built-in
• SOS
splitters)
• 2-pair bonding
• Wetting Current
64-port • 64 VDSL2 over POTS service channels (without

VDSL2 built-in splitters)
over
POTS • System level G.Vector features
VGWVS
subscriber
card with • G.993.2 17A US0-ANNEX A
G.Vector
function • SELT and DELT


(without
built-in • G.INP
splitters)
• INM
• SOS
• 2-pair bonding
• 64 VDSL2 over POTS service channels (without

built-in splitters)
64-port
VDSL2 • System level G.Vector features
over
POTS • G.993.2 17A US0-ANNEX A
subscriber
card with • SELT, DELT and MELT
VGWV
G.Vector
and MELT • G.INP
function
(without • INM
built-in
splitters) • SOS
• 2-pair bonding
• 64 VDSL2 over POTS service channels (built-in

splitters)
64-port • System level G.Vector features

VDSL2
over • G.993.2 17A US0-ANNEX A
POTS
subscriber • SELT and DELT
VHWV
card with
G.Vector • G.INP
function
(build-in • INM
splitter)
• SOS
• 2-pair bonding
• 64 VDSL2 over ISDN service channels (built-in

64-port splitters)
VDSL2
over ISDN • System level G.Vector features
subscriber
VHWVI card with • G.993.2 17A US0-ANNEX B
G.Vector
function • SELT and DELT
(built-in
splitters) • G.INP

• INM
• SOS
• 2-pair bonding
• 64 VDSL2 service channels (built-in splitters)
• System level G.Vector features

64-port
• G.993.2 17A US0-ANNEX B
VDSL2
subscriber
• SELT and DELT
card with
VHWVE
G.Vector
• G.INP
function
(built-in
• INM
splitters)
• SOS
• 2-pair bonding
32-port
SHDSL
over
POTS Supports the processing of 1600-byte packets in
SLWG
subscriber EFM mode
card with
MELT
function
• 32 SHDSL bis service channels
• Supports both SHDSL bis EFM mode and

32-port
SHDSL ATM mode
SHDSL
bis
• G.991.2 ANNEX A/B/F/G
SMWG subscriber
card with
• MELT
MELT
function
• Wetting Current
• 32 SHDSL bis service channels

32-port
• Supports both SHDSL bis EFM mode and
SHDSL
SHDSL ATM mode
SSWG bis
subscriber
• G.991.2 ANNEX A/B/F/G
card
DSL and 48-port • 48 ADSL2+ and POTS combined service

ACWKC
POTS ADSL2+ channels (built-in splitters)


combo and POTS
card COMBO • G.992.1 ANNEX A, G.992.3 ANNEX A/L/M,
subscriber G.992.5 ANNEX A/M
card with
build-in • SELT and DELT
splitters
• G.INP
• 64 ADSL2+ and POTS combined service

64-port
channels(built-in splitters)
ADSL2+
and POTS
COMBO
ACWVC G.992.5 ANNEX A/M
subscriber
card with
• SELT, and DELT
build-in
splitters
• G.INP
• 48 VDSL2 and POTS combined service

channels (built-in splitters)
48-port • G.993.2 17A US0-ANNEX A

VDSL2
and POTS • SELT, and DELT
COMBO
VCWKC
subscriber • G.INP
card type
C build-in • INM
splitters
• SOS
• 2-pair bonding
• 64 VDSL2 and POTS combined service

channels (built-in splitters)
64-port
VDSL2
and POTS
COMBO
• SELT, and DELT
subscriber
VDWVD card type
• G.INP
D with
G.Vector
• INM
function
build-in
• SOS
splitters
• 2-pair bonding
64-port • Separating ADSL/2/2+ signals with POTS

ADSL signals
DSL
over
Splitter PWVNA
POTS • Real Impedance (600 ohms)
card
splitter
card • Interfaces: 64 DSL & 64 POTS & 64 USER

64-port • Separating ADSL/2/2+ signals with POTS
ADSL signals
over
PWVNE
POTS • ETSI standard Impedance
splitter
card • Interfaces: 64 DSL & 64 POTS & 64 USER
64-port
• Separating VDSL2 signals with POTS signals
VDSL2
over
VWVNA • Real Impedance (600 ohms)
POTS
splitter
• Interfaces: 64 DSL & 64 POTS & 64 USER
card
64-port
• Separating VDSL2 signals with POTS signals
VDSL2
over
VWVNE • ETSI standard Impedance
POTS
splitter
• Interfaces: 64 DSL & 64 POTS & 64 USER
card
64-port • Separating DSL signals with ISDN signals, either

over ISDN ADSL/2/2+ or VDSL2
IWVN
splitter
card • Interfaces: 64 DSL & 64 ISDN & 64 USER
• 8 SFP GPON OLT optical service channels

8-port
GPON • Class B+ and Class C+ optical modules
GTGO OLT
subscriber • Maximum split ratio 1:128
card
• Working with SCXN/SCXM only
• 16 SFP GPON OLT optical service channels

16-port
GPON • Class B+ and Class C+ optical modules
GPON GTGH OLT
interface subscriber • Maximum split ratio 1:128
card card
• Working with SCXN only
• 8 XFP XG-PON1 OLT optical service channels
8-port XG • Maximum split ratio 1:256

PON1
GTXO OLT • Supports optical power monitoring.
subscriber
card • Supports optical module ALS
• Working with SCXN only
Ethernet 8-port GE • 8 SFP GE P2P optical service channels

interface HDTT optical
card interface • Working with SCXN/SCXM only


• 48 CSFP or 24 SFP GE P2P optical service
channels
P2P 48-port
interface FTGK GE optical
• Ethernet clock synchronization
card interface
• Working with SCXN/SCXM only
1-port
GPON • Uplink
GPUC ONT
interface • 1 GPON ONT uplink port
card
1-port
XG-PON1 • Uplink
XPUC ONT
interface • 1 XGPON1 ONT uplink port
card
2-port GE
• Uplink or cascading
optical
GCFD
interface
• 2 SFP GE ports
card
2-port GE
electrical
GCTD
interface
• 2 GE electrical ports
card
2-port GE
Network optical
interface and 2-port • Uplink or cascading
card GUSQ GE
electrical • 2 SFP GE ports and 2 GE electrical ports
interface
card
4-port GE
optical
GUFQ
interface
• 4 SFP GE ports
card
4-port GE
electrical
GUTQ
interface
• 4 GE electrical ports
card
2-port
10GE
opticial • Uplink or cascading
HUTQ and 2-port
GE optical • 2 SFP 10GE ports and 2 SFP GE ports
interface
card
HUVQ 2-port • Uplink or cascading

10GE
optical • 2 SFP 10GE ports and 2 SFP GE ports
and 2-port
GE optical • Ethernet clock synchronization
interface
card
32-port
Analog analog • 32 analog trunk/FXO service channel
trunk TRWG trunk
card subscriber • Support DDI
card
BITS clock interfaces, Maintenance interfaces,

Temperature/ Humidity/ Smog/ Flood/ Entrance
sensor interfaces.
2 * BITS clock input interface (75W)
1 * BITS clock output interface (75W)
2 * BITS clock input interface(120W)
1 * BITS clock output interface(120W)
1 * Out-of-band maintenance Ethernet interface
1 * Maintenance serial port
CICG 1 * Dry contact control input interface (support four
pairs of digital inputs)
1 * Dry contact control output interface (support four
pairs of digital outputs)
1 * Temperature sensor interface
1 * Humidity sensor interface
1 * Smog sensor interface
1 * Flood sensor interface
Common 1 * Entrance sensor interface (support four pairs of
interface inputs)
Common
card BITS clock interfaces, Maintenance interfaces,
interface
supporting Temperature/ Humidity/ Smog/ Flood/ Entrance
card
environme sensor interfaces.
nt monitor 2 * BITS clock input interface (75W)
1 * BITS clock output interface (75W)
2 * BITS clock input interface(120W)/ 1PPS+TOD
clock input interface
1 * BITS clock output interface(120W)/ 1PPS+TOD
clock output interface
1 * Out-of-band maintenance Ethernet interface
CICK 1 * Maintenance serial port
1 * Dry contact control input interface (support four
pairs of digital inputs)
1 * Dry contact control output interface (support four
pairs of digital outputs)
1 * Temperature sensor interface
1 * Humidity sensor interface
1 * Smog sensor interface
1 * Flood sensor interface
1 * Entrance sensor interface (support four pairs of
inputs)


• One -48V power input port
• Filtering and current-limiting for the input power

PRWG
• Power status monitor and alarm indicator, i.e.
over-voltage, under-voltage, power loss etc
• One -48V power input port

PRWGS
Power
Power over-voltage, under-voltage, power loss etc
interface
card
card • One -48V power input port and two RJ-45 ports

over-voltage, under-voltage, power loss etc.
PRWH
• Support electrical serial number
• Embedded temperature sensor
• Voltage, current and power meter functions
ZXA10
C300M
Backplane
MWEB Support 16 or 17 subscriber cards
of 21-inch
service
shelf
ZXA10
C300M • Support 16 or 17 subscriber cards
Backplane
MWEC
of 21-inch • Support system level vectoring：2 vectoring
service groups up to 384 channels each
Backpla shelf
ne ZXA10
C300M
Backplane
MWIB Support 14 or 15 subscriber cards
of 19-inch
service
shelf
ZXA10
C300M • Support 14 or 15 subscriber cards
Backplane
MWIC
of 19-inch • Support system level vectoring：2 vectoring
service groups up to 384 channels each
shelf

• Support 6 or 7 subscriber cards
ZXA10
MWRV C350M
• Support system level vectoring: 1 vectoring
Backplane
group up to 384 channels

3 Hardware Installation
3.1 Installation Flow

Figure 1 shows the hardware installation flow for the ZXA10 C300M/ZXA10 C350M
Figure 1 Hardware Installation Flow
3.2 Installation Preparations

You must know the procedure for installing the hardware, and have knowledge on system
network structure, power supply, cable connection, and hardware maintenance.
Before installation, you need to check the environment and prepare required tools and
documents.
3.2.1 Environment Check
Before installation, it is necessary to check the equipment environment to ensure that the
environment meets the operating requirements of the equipment.
Caution!
It is not allowed to install the equipment if the installation environment is unsatisfactory.
Take an indoor equipment room as an example, the environmental checklist includes but
not limited to the following:
• Architectural conditions
Check the size, height, load-bearing capacity, and layout of the

equipment room.
• Environmental conditions
Check illumination, air-conditioning, ventilation, antistatic measures,

shockproof measures, lightning protection measures, and fire-fighting
devices of the equipment room.
• Power supply conditions
Check AC power supply facilities, DC power supply facilities, and

accumulator batteries.
• Grounding conditions
The equipment room must have good grounding conditions. Ground

resistance must meet local technical requirements. In general, ground
resistance cannot be greater than 1 Ω.

• Auxiliary devices
Check Digital Distribution Frames (DDF), cable trays, and cable

distribution frames.
• Other facilities
Check workbenches, power outlets, alarm boxes, and other peripheral

devices.
The outdoor cabinet environmental checklist is similar to the indoor environmental

checklist. For a detailed environmental checklist, refer to Environment Acceptance
Report of the equipment.
3.2.2 Tools Preparation
For a list of the tools and meters that must be prepared before installation, see Table 1.
Note:
Instruments and meters are subject to local standards. The pictures in the table are for
reference only.
The meters cannot be used unless strictly calibrated and proven qualified.
Table 1 Tools and Meters

Picture Name Purpose
Cross head
Tightens cross head screws.
screwdriver
Flathead
Tightens flathead screws.
screwdriver
Adjustable wrench Tightens bolts.
Torque wrench Tightens bolts.
Loosens or tightens fasteners to

Socket wrench set
adjust the level of the cabinet.
Floating-nut driver Installs floating nuts.
Tape measure Measures length.
Measures length or draws right

Angle square
angles.
Checks the level of adjustable

Spirit level
bases and cabinets.
Checks vertical deviation of a

Plumb line
cabinet.
Marks the positions of drilled

Marker pen
holes on the floor.
Marks lines on the ground to

Powder marker determine the position where a
socket bolt is installed.
Installs socket bolts and opens

Claw hammer
wooden cases.
Percussion drill Drills holes.

Cleans installation holes and the

Vacuum cleaner
floor.
Prunes cable ties and cuts

Diagonal pliers
packing straps of cartons.
Paper knife Cuts adhesive tapes on cartons.
Network cable
Tests network cables.
tester
Tests the insulation condition of

cabinets, connection condition
of cables, and electric
Multimeter
performance indexes of devices,
such as voltage, current, and
electric resistance.
Measures the current in a cable

Current clamp under the condition that the
meter loading operation is not
interrupted.
Network cable Crimps connectors of network

crimping pliers cables.
Coaxial-cable Crimps the metal sheath at the

crimping pliers end of a coaxial cable.
Wire strippers Strips off the cable sheath.
Crimps O-type terminals and JG

Hydraulic pliers
terminals.
Work gloves Used during installation.
Antistatic gloves Used during installation.
Hacksaw Cuts wood floor or metal.
Ties up power cables, protective

Cable tie grounding wires, and signal
cables.
Ladder Used for working at heights.
Used to locate a drill bit for

Punch making an indentation at the
hole location.
Required Documents
Before the device installation, the personnel responsible for installation must prepare all
necessary engineering and technical documents as follows:
• Read and understand the technical requirements, engineering projects,

and the schedule in the Order Contract (copy) and Technical Proposal.

• Conduct site survey, check the installation environment, and submit the
Engineering Survey Report and Environment Acceptance Report. If the
engineering survey or installation environment does not meet the
requirements, complete the Project Delay/Resumption Report, notifying
the user of the items that must be corrected to meet installation
requirements.
• Prepare the Project Installation Plan, determine the Project

Commencement Schedule, and submit the Project Commencement
Application.
• Prepare the Unpacking Acceptance Report and Installation Acceptance

Report after being approved.
• Read the Hardware Installation carefully before installation.
• Fill in the Project Memorandum for unaccepted items that cannot be

corrected。
3.3 Unpacking and Checking Equipment

Steps >>
1.
Check the total number of equipment in accordance with the Packing List, and then
verify that the outer packing is complete.
2
. Remove the outer packing of the wooden case.
a.
Move the wooden case with a fork truck to the cabinet installation site in the equipment
room.
b
. Open all tongue pieces with a flathead screwdriver, remove the upper cover of the case,
and then remove the sideboards, see Figure 1.
Figure 1 Unpacking a Wooden Case
1. Flathead screwdriver
2. Tongue
c.
Take out the equipment list, technical documents, and tools for equipment installation
from Package 1.
d.
Make the bottom of the cabinet downwards.
e.
Remove foam corner protectors, foam edge protectors, and plastic package.
3
. Remove the outer packing of the carton, see Figure 2.
a. Cut the packing straps of a carton by using diagonal pliers.
b. Cut the adhesive tapes sealing the carton.
c. Open the carton, and then take out the foam board and board boxes.
Figure 2 Removing the Outer Packing of a Carton

1. Carton label
2. Packing strap
3. Carton
4. Adhesive tape
5. Foam board
6. Board box
4
. Remove the board package.
a.
Wear antistatic gloves (or an ESD wrist strap).
b.
Remove the board package, see Figure 3.
Figure 3 Removing the Board Package
1. ESD wrist strap

c.
For the board that is not installed immediately, put it back in its original package, and
then seal the package.
5.
Check to ensure that the equipment is in good condition and the quantity is correct
before equipment hand-over and storage.
3.4 Removing Cabinet Doors
3.4.1 Removing the Front Door

1.
Open the door lock, and then open the cabinet door, see Figure 1.
Figure 1 Opening the Door Lock
2.
Disconnect the end of the grounding cable on the cabinet by using a cross head
screwdriver (it is recommended to only disconnect the end connected to the cabinet),
see Figure 2.
Figure 2 Disconnecting the Grounding Cable
3.
Install the screws back to the cabinet to avoid losing them.
4.
Disassemble the cabinet door, see Figure 3.
a. Hold the door with your right hand.
b. Pull down the spring pin located in the middle part of the door with your
left hand, and then hang the spring pin in the gap on one side of the
door.
c. Pull down the spring pin on the upper part of the door.

d. Lift the door upwards, and then move the door outwards.
Figure 3 Disassembling the Cabinet Door
Note:
Put the cabinet at a safe place.
Ensure that the lock of the cabinet door is opened, which prevents the lock rod on the
lower part of the door from being distorted because of pressure.
3.4.2 Removing a Side Door

5.
Loosen the screws on the side door with a screwdriver.
6.
Remove the side door, see Figure 4.
Figure 4 Disassembling the Side Door
3.5 Cabinet Installation

A cabinet can be installed in either of the following ways:
• Installed on an adjustable base, suitable for the equipment room with

static conductive floor.
• Installed on the floor, suitable for the equipment room without static
conductive floor.
3.5.1 Installing the Cabinet on the Adjustable Base
Abstract >>
This procedure describes how to install a cabinet on the adjustable base.
Before installing a cabinet, you need to determine the installation position of the
adjustable base, adjust the base height, and install the adjustable base, ensuring that the
upper plane of the base is aligned with the upper plane of the antistatic floor.
Prerequisite >>
• The related design documents are ready.
• A drilling template is ready.
• The dust inside and outside all the holes is cleared with a cleaner before
base installation.
Context >>
For the installation position of the cabinet in the equipment room, see Figure 1.
Figure 1 Installation Position of the Cabinet
Adjustable bases fall into three types. For the types of adjustable bases, see Table 1.
Table 1 Adjustable Heights for an Adjustable Base

Adjustable Base Type Adjustable Height
Type A 160 mm – 260 mm
Type B 260 mm – 460 mm
Type C 460 mm – 660 mm
The three types of adjustable bases have the same width and depth, but differ only in
adjustable height. For an overview of the adjustable base (type A), see Figure 2.
Figure 2 Adjustable Base (Type A)

Caution!
• Before installing a cabinet, ensure that the work over the cabinet (for
example, cable tray installation) is completed, so that dust or metal
scraps will not drop into the cabinet from the top during cabinet
installation.
• Hole position determination and drilling are fundamental for hardware

installation, and must be completed accurately.
Steps >>
Positioning an Adjustable Base
1. Remove the static conductive floor and its braces at the place where the
cabinet is to be installed.
2
. Mark the mounting hole positions.
Determine the installation position in accordance with the design drawing and base dimensions, determ
•
For the position of holes for installing a single cabinet, see Figure 3.
Figure 3 Marking Holes for Installing a Single Cabinet (Unit: mm)
1.
2.
•
For the mounting holes of socket bolts for the adjustable bases to install two cabinets, see Figure 4
Figure 4 Marking Holes for Installing two Cabinets (Unit: mm)
1.
2.

•
For the mounting holes of socket bolts for the adjustable bases to install multiple cabinets, see Figu
Figure 5 Marking Holes for Installing Multiple Cabinets (Unit: mm)
1.
2.
3.
Place the drilling template on the specified positions, and check whether the template
holes are aligned with the mounting holes marked in Step 2.
• Yes → Mark the positions of all the mounting holes of the adjustable
base with a marker pen.
• No → Verify that positions are correctly marked in Step 2.

4
. Drills holes.
a.
In accordance with the position of the socket bolt marked on the floor, make an
indentation at the hole location first by using a punch to help locate the drill bit, see
Figure 6.
Figure 6 Drilling Indentations
b
. Adjust the scale that determines the depth of the hole, and then press the percussion
drill downward vertically to drill holes. Use the vacuum cleaner to remove the dust inside
and outside the holes, see Figure 7.
Figure 7 Drilling a Hole
1. Vacuum cleaner
2. Percussion drill
Note:

• Ensure that the drill is perpendicular to the floor when drilling holes and
hold the drill handler securely.
• The hole depth is equal to the sum of the expansion tube length of the
expansion bolt and the conical head length. The depth of each hole
should be the same. Dust must be removed from each hole when you
measure the hole depth.
5.
Measure the distance between holes. If there is a large error, reposition and drill the
holes.
6
. Remove the expansion bolt, spring washer, gasket, and the insulating washer.
For an overview of the expansion bolt, see Figure 8.
Figure 8 Expansion Bolt
1. Bolt
2. Spring washer
3. Gasket
4. Insulating washer
5. Expansion tube
7. Install the socket bolt vertically into the hole. Hammer the socket bolt by
using the claw hammer until the expansion tube enters the hole
completely, see Figure 9.
Figure 9 Hammering a Socket Bolt
Mounting the Adjustable Base

8.
Measure the height between the concrete floor and the surface of the static conductive
floor by using a tape measure.
9.
Adjust the adjustable base to make the scale indication on the base equal to the height
of the static conductive floor, see Figure 10.
Figure 10 Adjusting the Height of an Adjustable Base
10. Place the adjustable base in the installation position, and adjust its
height.
1 Install gaskets for pressing plates at the four mounting holes, so that one end of
1 each pressing plate presses against the base leg, and the other end against the

. gasket, see Figure 11.
Figure 11 Installing the Gasket and Pressing Plate
1. Pressing plates
2. Gasket
1 Install four M12×90 expansion bolts with spring washers, gaskets, and insulating
2 washers into the expansion tubes buried in the ground through the pressing plate
. holes, and secure the bolts, see Figure 12.
Figure 12 Installing the Adjustable Base
1. Spring washer
2. Gasket
Adjust the base with an adjustable wrench, and ensure that the adjustable base is
13. level with the floor by using a level bar, see Figure 13.
Figure 13 Leveling the Adjustable Base

Note:
The horizontal deviation must be less than 3 mm. If the adjustable base is not level
with the floor, adjust the leg. Tighten the locking nuts for the adjustable base, and
tighten the expansion bolts with an adjustable wrench.
(Optional) If multiple adjustable bases are mounted in parallel, measure the level of
14. the adjustable bases with a level bar.
Installing a Cabinet
Move a cabinet onto the adjustable base, and ensure that the mounting holes at the
15. bottom of the cabinet are aligned with those at the top of the adjustable base, see
Figure 14.
Figure 14 Aligning the Cabinet With the Adjustable Base
Open the cabinet door.

16.
Install M12×40 bolts with gaskets and spring washers into the mounting holes,
17. and screw on and tighten nuts, see Figure 15.
Figure 15 Installing a Cabinet

1. M12×40 hexagon bolt
2. Spring washer
3. Gasket
18. Measure the level of the cabinet with the level bar.
The horizontal deviation must be less than 3 mm. If the cabinet is not
level with the floor, increase insulating gaskets between the cabinet and
the adjustable base, see Figure 16.
Figure 16 Adjusting the Cabinet Level
Perform the following procedures as required:

19. To... Do...
Install a single cabinet Go to step 22.
Install multiple cabinets Go to step 20.

Install cabinets side by side.
20. The spacing between the neighboring cabinets in a row should be smaller than 3 mm.
The sides of cabinet rows that are along the walkway must be aligned with a deviation
less than 5 mm, see Figure 17.
Figure 17 Space Between Side-by-Side Cabinets

Connect neighboring cabinets with junction kits, see Figure 18.

21. Figure 18 Connecting Neighboring Cabinets
(Optional) Install a shockproof assembly on the cabinet if necessary.

•For the shockproof
2 assembly installation diagram when all the mounting holes are under the cable
ladder in 2the equipment room, see Figure 19.
Figure 19 Installing the Shockproof Assembly (1)
.

1. Horizontal support
2. Vertical support
3. Cable ladder
4.M12×25/M8×25 hexagon socket cap head bolt (Spring washer, gasket, and insulating washer)
5. Insulating gasket
6. Lock rod (M8 hexagon nut, spring washer, and gasket)
7. Bolt (M8 nut, spring washer, and gasket)
•
For the shockproof assembly installation diagram when the vertical connection
plates are not close to the cable ladder, see Figure 20.
2. Vertical support
3. Cable ladder
4.M12×25/M8×25 hexagon socket cap head bolt (Spring washer, gasket, and insulating washer)
Restore the static conductive floor. Adjust the support kit for the static conductive floor
23. again. Install the static conductive floor.
Note:
If bottom routing is used, ensure that cabling is complete.
3.5.2 Installing the Cabinet on the Floor
Abstract >>
This procedure describes how to install a cabinet on the concrete floor.
Prerequisite >>
• A drilling template is ready.

• The dust inside and outside all the holes is cleared with a cleaner before
cabinet installation.
Context >>
To install a cabinet on the concrete floor, you only need to fasten the cabinet onto the
floor with hexagon bolts and nuts.
Caution!
• Before installing a cabinet, ensure that the work over the cabinet (for
example, cable tray installation) is completed, so that dust or metal
scraps will not drop into the cabinet from the top during cabinet
installation.
• Hole position determination and drilling are fundamental for hardware

installation, and must be completed accurately.
For the installation position of the cabinet in the equipment room, see Figure 21.
Figure 21 Installation Position of the Cabinet
Steps >>
Determining Installation Positions
1 Mark the mounting hole positions.

Determine. the installation position in accordance with the design drawing and cabinet dimensions,
determine the cabinet fixing positions by using a tape measure, and mark the positions with an ink
fountain.
•For the position of holes for installing a single cabinet, see Figure 22.
Figure 22 Marking Holes for Installing a Single Cabinet (Unit: mm)
1. Wall
2. Installation hole
•For the mounting holes of socket bolts for the adjustable bases to install two cabinets, see Figure
23.
Figure 23 Marking Holes for Installing two Cabinets (Unit: mm)

1. Wall
•For the mounting holes of socket bolts for the adjustable bases to install multiple cabinets, see
Figure 24.
Figure 24 Marking Holes for Installing Multiple Cabinets (Unit: mm)
1. Wall
Place the drilling template on the specified positions, and check whether the holes of
2. the template match the installation holes marked in Step 1.
Yes → Mark the positions of all the installation holes of the adjustable base with a
marker pen.
No → Verify that positions are correctly marked in Step 1.
Drill holes.
a. In accordance
3 with the position of the socket bolt marked on the floor, make an indentation at the
hole location
. first by using a punch to help locate the drill bit, see Figure 25.
Figure 25 Drilling Indentations
bAdjust the scale that determines the depth of the hole, and then press the percussion drill
.downward vertically to drill holes. Use the vacuum cleaner to remove the dust inside and outside
the holes, see Figure 26.
Figure 26 Drilling a Hole
1. Vacuum cleaner
2. Percussion drill
Installing expansion bolts
4. Measure the distance between holes. If there is a large error, reposition

and drill the holes.
5. Remove the expansion bolt, spring washer, gasket, and the insulating
washer.
For an overview of the expansion bolt, see Figure 27.
Figure 27 Expansion Bolt
1. Bolt
2. Spring washer
3. Gasket
5. Expansion tube
6. Install the socket bolt vertically into the hole. Hammer the socket bolt by
using the claw hammer until the expansion tube enters the hole
completely, see Figure 28.
Figure 28 Hammering a Socket Bolt
Installing a Cabinet
7. Mount insulating pads in parallel, and ensure that the pad holes are
aligned with mounting holes on the concrete floor, see Figure 29.
Figure 29 Installing Insulating Pads
8. Move a cabinet to the installation position, and align the mounting holes
of the cabinet with those on the floor, see Figure 30.
Figure 30 Installing a Cabinet (1)

9. Open the cabinet door.
10. Install four M12×90 expansion bolts with spring washers, gaskets, and
insulating washers from top to bottom into the mounting holes through
the cabinet, and tighten them, see Figure 31.
Figure 31 Installing a Cabinet (2)
1. M12×90 expansion bolt
2. Spring washer
3. Gasket
11. Perform the following procedures as required:
To... Do...
Install a single cabinet Go to step 14.
Install multiple cabinets Go to step 12.
1 Install cabinets side by side.

2

.
The spacing between the neighboring cabinets in a row should be
smaller than 3 mm. The sides of cabinet rows that are along the walkway
must be aligned with a deviation less than 5 mm, see Figure 32.
Figure 32 Space Between Side-by-Side Cabinets
13. Connect neighboring cabinets with junction kits, see Figure 33.
Figure 33 Connecting Neighboring Cabinets
1. M5×16 combination screw
2. Connecting plate
1 (Optional) Install a shockproof assembly on the cabinet if necessary.

4
. • For the shockproof assembly installation diagram when all the mounting holes
are under the cable ladder in the equipment room, see Figure 34.

2. Vertical support
3. Cable ladder
4. M12×25/M8×25 hexagon socket cap head bolt (Spring washer, gasket, and insulating
washer)
• For the shockproof assembly installation diagram when the vertical connection
plates are not close to the cable ladder, see Figure 35.
2. Vertical support
3. Cable ladder
4. M12×25/M8×25 hexagon socket cap head bolt (Spring washer, gasket, and insulating
washer)
3.6 Power Cable and Grounding Cable Installations

for the Cabinet
The power cable refers to the cable that connects the -48 V/-60 V DC power supply in the
equipment room to the PDU in the cabinet.
The grounding cable refers to the cable that connects the grounding point at the top of
the cabinet to the grounding busbar in the equipment room.

3.6.1 Cabling Requirements
3.6.1.1 Routing Principles >>
• Power cables and grounding cables should be routed in a smooth and straight
manner, see Figure 1.
Figure 1 Routing of Power Cables and Grounding Cables
1. Power Cable
2. Grounding Cable
• If a cable is not long enough, use a longer cable. Do not connect or solder
two or more short cables to make a long one.
• Cut off any surplus parts of cables instead of coiling them.
• If two O-type terminals are installed, the terminals should be

cross-connected (see A of Figure 2), or one O-type terminal is bent at an
angle of 45 degrees or 90 degrees (see B of Figure 2).
O-type terminals must not be overlaid (see C of Figure 2). The larger
O-type terminal cannot be placed on the smaller one (see D of Figure 2).
Figure 2 Installation Modes of O-Type Terminals
• The horizontal distance between power cables (or grounding cables) and other
cables should be greater than 300 mm, see Figure 3.
Figure 3 Distance Between Power Cables and Signal Cables

1. Signal Cable
2. Power Cable
• Cable bends should have the same radius, which should be between 50
mm and 100 mm (the radius requirement varies with different
cross-sectional sizes).
• Cables should be routed in a flat and straight manner, without any

crossover or cable coiling.
3.6.1.2 Binding Principles >>
• Power cables and grounding cables should be bundled separately from

other cables.
• The distance between two neighboring ties should be 200 mm.
• Avoid cables from being squeezed or stretched by rotatable parts such as

a door. Do not bind the cables at the bends, see Figure 4.
Figure 4 Cable Binding
• Cable ties should face the same direction. The surplus part of cable ties
should be trimmed.
3.6.1.3 Top Routing Principles >>
Power cables and grounding cables are routed from the top of the DC power distribution
box to the cable ladder, and then to the cabinet top along the cable ladder, see Figure 5.
Figure 5 Top Routing of a Cabinet
1. Cable ladder
2. Cover plate for power cables
3. PDU
3.6.1.4 Bottom Routing Principles >>
Power cables and grounding cables are routed from the bottom of the DC power
distribution box to the cabinet bottom through the static conductive floor, see Figure 6.
Figure 6 Bottom Routing of a Cabinet

1. PDU
2. Cover plate for power cables
3. Vertical cable tray in a cabinet
3.6.2 Connecting a Protective Grounding Cable
Abstract >>
If the equipment room uses a DC power distribution cabinet, you must connect a
protective grounding cable from the cabinet to the PE end of the DC power distribution
cabinet.
If no DC power distribution cabinet is available, you need to connect the protective

grounding cable from the cabinet to the copper grounding busbar in the equipment room.
Prerequisite >>
• The power distribution switch is set to OFF.
Context >>
The grounding point of the cabinet is at the top of the cabinet, see Figure 7.
Figure 7 Grounding Points on the Cabinet
Steps >>
1. Determine how to route the protective grounding cable in accordance

with on-site requirements.

2. Determine the connection terminals used at both ends of cables and the
accurate length of each cable.
3. Make a protective grounding cable. For how to make a grounding cable,

refer to Making a Power Cable and a Grounding Cable.
4 Connect the grounding cable to the cabinet, see Figure 8.

.
Figure 8 Protective Grounding Cable Wiring
5. Connect the yellow-green grounding cable to the PE terminal of the DC
power distribution cabinet.
3.6.3 Connecting Power Cables
Abstract >>
This procedure uses the scenario where a DC power distribution cabinet supplies -48
V/-60 V power to the cabinet as an example to describe how to connect power cables.
If a DC power distribution cabinet is not available, connect cables as follows:
• Connect the -48 V/-60 V power cable of the cabinet to the DC distribution
panel or the -48 V/-60 V negative busbar of the DC power supply.
• Connect the RTN power cable of the cabinet to the DC distribution panel
or the -48 V/-60 V positive busbar of the DC power supply.
• Connect the grounding cable of the cabinet to the copper grounding

busbar.
Prerequisite >>
• The power distribution switch is set to OFF.
Context >>
The DC power distribution cabinet provides two channels of -48 V/-60 V DC power to the
PDU, and the PDU can provide eight channels of power to the modules in the cabinet (in
general, four channels are used).
For the PDU wiring diagram, see Figure 9 (takes -48 V as an example).
Figure 9 PDU Wiring Diagram

Steps >>
1. Determine how to route the power cables in accordance with on-site

requirements.
2. Determine the connection terminals used at both ends of cables and the
accurate length of each cable.
3. Make power cables. For how to make a power cable, refer to Making a
Power Cable and a Grounding Cable.
4. Connect the power cables to the DC power distribution cabinet.
a. Connect the blue power cable to the -48 V/-60 V

connection terminal of the DC power distribution cabinet.
b. Connect the black RTN cable to the RTN connection

terminal of the DC power distribution cabinet.
5. Loosen the screws on the protective panel of the PDU with a cross
screwdriver, and remove the protective panel.
6. Connect the power cables to the PDU.
a. Connect the blue power cable to the -48 V/-60 V

connection terminal of the PDU.
b. Connect the black RTN cable to the RTN connection
terminal of the PDU.
7. Use the multimeter to measure the resistance between the -48 V/-60 V
input terminal and the RTN input terminal of the PDU.
If the multimeter does not give out any sound, no short circuit exists.
8. Install the protective panel of the PDU, and tighten the screws.
3.7 Device Installation in the Cabinet

Different devices can be installed in the cabinet as required, such as the PDU, shelf
(including boards), and cable routing subrack.
3.7.1 Installing a Shelf
Abstract >>
This procedure describes how to install a shelf in a cabinet in accordance with the layout
plan.
Note:
Normally, a shelf is already installed in a cabinet, so you only need to verify that the
screws for securing the shelf are tightened. A shelf is separately packed if it is used for
system expansion, and you must install the shelf.
You should maintain balance of the shelf to prevent it from falling or inclining.
Caution!
Do not move or install a shelf containing boards (such as the switching board or
processing board).
Do not apply force on vulnerable parts such as extractors on a power module, cable tray,
or vents when moving or installing a shelf. Failure to comply can result in damage or
distortion.
Prerequisite >>
• The shelf to be installed is intact without deformation.

• The connectors on the backplane of the shelf are intact and neat without
bent pins.
• The installation location supports easy installation operations and ensures good
ventilation of the equipment.
3.7.1.1 Installing a ZXA10 C300M Shelf

1.
Determine the installation position of the C300M shelf in the cabinet.
2.
Install mounting brackets at the right positions of the cabinet, see Figure 1.
Figure 1 Installing mounting brackets
3.
Install floating nuts at the right positions of the cabinet, see Figure 2.
Figure 2 Installing floating nuts
4.
Place the shelf on the brackets, and push it until it is aligned with the bolt holes.
5.
Tighten bolts in a clockwise direction to secure the shelf, see Figure 3.
Figure 3 Installing a C300M Shelf
3.7.1.2 Installing a ZXA10 C350M Shelf
1.
Determine the installation position of the C350M shelf in the cabinet.
2.
Install floating nuts at the right positions of the cabinet, see Figure 4.
Figure 4 Installing floating nuts
3.
Install mounting brackets at the right positions of the cabinet, see Figure 5.
Figure 5 Installing mounting brackets
4.
Install floating nuts on the brackets for securing the shelf, see Figure 6.
Figure 6 Installing floating nuts on the brackets
5.
Place the shelf onto the bracket, and align the shelf with the bolt holes.
6.
Tighten bolts in a clockwise direction to secure the shelf, see Figure 7.
Figure 7 Installing a C350M Shelf
3.7.2 Installing a Subrack
Abstract >>
This procedure describes how to install a subrack in the cabinet, for example, a PDU or
cable routing subrack.
Note:
Normally, subracks are already installed in a cabinet, so you only need to verify that the
screws for securing the subracks are tightened. Subracks are separately packed if they
are used for system expansion, and you must install them.
Steps >>
1. Install floating nuts at the right positions of the cabinet.
2. Place a subrack at the right position of the cabinet, and align it with bolt
holes.
3. Tighten bolts in a clockwise direction to secure the subrack, see Figure

2.
Figure 2 Installing a Subrack
Note:
Four bolts are used to secure a subrack. You can determine the position
of the subrack in the cabinet as required.
3.7.3 Installing a Board
Abstract >>
This procedure describes how to install a board in a shelf.
Prerequisite >>
Before installing a board, ensure that the cabinet and shelf are clean, and perform the
following checks:
• Verify that the board name is the same as that on the packing list.
• Verify that the board is in good condition.
• Verify the board software version.
Context >>
Blank panels are installed on the board slots before delivery to protect the components in
the shelf. Before installing a board on the site, you should first remove the blank panel in
the corresponding position.
A shelf can be pre-installed with blank panels with or without extractors. This procedure
uses a blank panel without extractors as an example.
Steps >>
Removing a Blank Panel
1. Wear the ESD wrist strap (or antistatic gloves), and then connect the
grounding terminal of the strap to the ESD jack on the shelf, see Figure
3.
Figure 3 Wearing an ESD Wrist Strap
1. ESD wrist strap
2. Loosen captive screws on the blank panel in a counterclockwise

direction, see ① in Figure 4.
Figure 4 Removing a Blank Panel
3. Hold the captive screws on the blank panel, and pull the panel from the
shelf, see ② in Figure 4.
Installing a Board
4. Take the new board out of an antistatic bag, see ① in Figure 5.
Note:
The ZXA10 C300M/C350M supports full-height boards (9U) and

half-height boards (4.5U). The installation methods for the two types of
boards are similar. The following uses a full-height board as an example.
Caution!
Do not touch the circuit when you take the board out of the bag.
Figure 5 Installing a Board
5. Hold the bottom of the board with one hand, and grasp the board panel
with the other hand. Slowly install the board into the slot along the guide
rails, see ② in Figure 5.
6. Push the extractors inward until they are close against the board panel,
see ③ in Figure 5.
7. Tighten the captive screws on both ends of the board in a clockwise

direction to secure the board, see ④ in Figure 5.
3.8 Power Cable Installation for the Shelf

The ZXA10 C300M/ZXA10 C350M shelf uses –48 V/–60 V DC power input to supply
power for each board in the shelf. This procedure describes how to connect a power
cable from the PDU to the shelf.
Figure 1 shows a power cable for the shelf. End A is connected to the PWR socket on the
power card, and end B is connected to an output terminal of the PDU.
Figure 1 Power Cable for a Shelf
Takes a -48V PDU as an example, the PDU supports two channels of -48 V input and
eight channels of -48 V output, see Figure 2.
Figure 2 PDU Wiring Diagram
Steps >>
1. Wear antistatic gloves.
2. Loosen the screws on the protective panel of the PDU with a cross
screwdriver, and remove the protective panel.
3. Connect the blue end (B1) of the power cable to the -48 V/-60 V output
terminal of the PDU, and tighten the screw.
4. Connect the black end (B2) of the power cable to the RTN output
terminal of the PDU, and tighten the screw.
5. Connect the other end (A) of the power cable to the PWR socket on the
power card.
6. Install the protective panel of the PDU, and tighten the screws.
Result >>
Figure 3 shows a cabinet in which power cables are connected for the shelves.
Figure 3 Power Cables Connected
3.9 Signal Cable Installation
3.9.1 Signal Cable Installation Requirements
3.9.1.1 Cabling Principles >>
• Before installation, signal cables must pass the continuity test. Both sides
of each signal cable should be marked or labeled correctly.
• Signal cables must be free of damage, breakage, and joints.
• Do not route signal cables on ventilation holes because this will affect
heat dissipation and cable life.
• During the cabling, it is not allowed to bind power cables and signal
cables together.
• Cabling in the cabinet must not affect door installation.
• Cables must be routed along the horizontal and vertical cable trays in a
flat and straight manner, without crossovers or folds.
• For a small number of optical fibers, the optical fibers can be routed
together with other cables and protected in soft management sets. For a
great number of optical fibers, the optical fibers should be routed along
vertical cable trays and protected in sylphon bellows.
3.9.1.2 Binding Principles >>
• Cables should be bound with appropriate force and tightened properly.

Cable ties should be arranged in the same direction.
• The surplus part of the cable tie should be cut off from the root without
any jagged edge.
• Take protective measures when attaching a signal cable to a sharp

structural component.
• Optical fibers should be bound with the optical fiber ties for protection.
3.9.1.3 Bending Principles >>
• Cable bends should be identically even and smooth. The bending radius
of optical fiber should be larger than 30 mm.
• The turning points of cables cannot be bound with cable ties. A surplus
length should be reserved for all signal cables. For how to bind the
cables, see Figure 1.
Figure 1 Cable Binding
Top Routing Principles >>
Three anti-rodent screens are provided on each side of the cabinet top (see A – F of
Figure 2). The anti-rodent screen should be cut in accordance with the number of cables
routed out of the cabinet.
If the horizontal cable ladder is more than 0.8 m above the cabinet, a vertical cable ladder
must be used to secure and protect cables.
Figure 2 Cable Outlets on the Cabinet Top
1. Anti-rodent screen
3.9.1.4 Bottom Routing Principles >>
Three anti-rodent screens are provided on each side of the cabinet bottom. The
anti-rodent screen should be cut in accordance with the number of cables routed out of
the cabinet, see Figure 3.
The height of the signal cable bundles cannot exceed two thirds of the floor height to
avoid negative effects on ventilation and heat dissipation.
Figure 3 Cable Outlets on Cabinet Bottom
1. Anti-rodent screen
3.9.2 Signal Cable Overview
3.9.2.1 Supported Signal Cables >>
The ZXA10 C300M/ZXA10 C350M supports the following types of signal cables:
• Subscriber Cables
• Splitter Cables
• Uplink Cables
• Optical Fibers
• Monitoring Cables
3.9.2.2 Subscriber Cables >>
ZXA10 C300M/ZXA10 C350M subscriber cables are routed to the side face through
wiring box, and overhead led to the cable outlet at the top of the cabinet.
Figure 4 shows subscriber cable connection.
Figure 4 Subscriber Cable Connection
3.9.2.3 Splitter Cables >>
Splitter cables are used to connect the xDSL service cards and the splitter cards, when
the ZXA10 C300M/ZXA10 C350M is configured with splitter cards.
Figure 5 shows the splitter cable connection when the xDSL service cards and the splitter
cards are configured in the same service shelf.
Figure 5 Internal Splitter Cables Connection
Note:
The xDSL service card and the splitter card are 1:1 configured in the adjacent slots when
they are in the same service shelf.
Figure 6 shows the splitter cable connection when the xDSL service cards and the splitter
cards are configured in the adjacent shelves.
Figure 6 External Splitter Cables Connection
Note:
The xDSL service card and the splitter card are configured in the same slot of the
adjacent shelves.
Uplink Cables >>
ZXA10 C300M/ZXA10 C350M uplink network cables are routed in the overhead mode.
Figure 7 shows uplink cable connection, taking 3 ZXA10 C300M service shelves
configuration as example.
Figure 7 Uplink Cable Connection
3.9.2.4 Optical Fibers >>
ZXA10 C300M/ZXA10 C350M optical fibers are routed in the overhead mode. Optical
fibers include subscriber optical fibers and uplink optical fibers.
• Subscriber Optical Fibers Connection
Subscriber optical fibers are used to connect with P2P card.Figure 8

shows subscriber optical fibers connection, taking 3 ZXA10 C300M
service shelves configuration as example.
Figure 8 Subscriber Optical Fibers
•
Uplink Optical Fibers
Figure 9 shows uplink optical fibers connection, taking 3 ZXA10 C300M service shelves
configuration as example.
Figure 9 Uplink Optical Fibers Connection
3.9.2.5 Monitoring Cables >>
Monitoring Cables include door-control cable, smog monitoring cable, liquid level
monitoring cable, temperature monitoring cable and humidity monitoring cable.
Figure 10 shows the monitoring cable connections, taking 3 ZXA10 C300M service
shelves configuration as example.
Figure 10 Monitoring Cable Connection
Monitoring cables are connected to the common interface card (CICG and CICK).Table 1
lists the monitoring cable connections.
Table 3-1 able Connection

No. Port of Common Interface Card Environment Sensor
1 DOR Security sensor
2 SMO Smoke sensor
3 HUM Humidity sensor
4 TEM Temperature sensor
5 LIQ Soak sensor
3.9.3 Connecting Signal Cables
The ZXA10 C300M/ZXA10 C350M supports multiple types of interface cards, and
different types of signal cables are used, but the cabling method is similar.
Prerequisite >>
• The detailed cable connection plan is obtained.
• The interface card to which a signal cable is to be connected is already

installed in the shelf.
Context >>
Monitoring cables are special signal cables, and can be classified into the following types:
access monitoring cables, smoke monitoring cables, liquid level monitoring cables,
temperature monitoring cables, and humidity monitoring cables. You need to connect one
end of a monitoring cable to the public interface card, and the other end to the
corresponding monitored position.
For signal cable routing, refer to “Signal Cable Overview”.
Steps >>
1. Wear antistatic gloves.
2. Confirm the installation position and length of each cable in accordance

with the cable connection plan.
3. (Optional) Make cables. For how to make a network cable, refer to

“Making a Network Cable”.
4. Connect one end of each cable to the corresponding board interface in

accordance with the connection plan.
5. Connect the other end of the cable.
To... Do...
Connect the other end to another board in Route the other end of the cable along
the same shelf or a board in another shelf the cable tray to the target board
of the same cabinet interface.
Connect the other end to another cabinet Route the other end of the cable along
the cable tray in the equipment room to
the target cabinet.
6. Verify that the cables are connected properly, and then bind the cables.
3.10 Installing Cabinet Doors
3.10.1 Installing the Cabinet Side Door
1. Remove the grounding screw of the side door. Connect one end of the
grounding cable to the grounding point of the side door, and tighten the
screw, see Figure 1.
Figure 1 Installing a Grounding Cable for a Side Door
For how to connect the other end of the grounding cable, see Figure 3.
2. Align the side door screws with the mounting holes on the cabinet.
3. Tighten the screws with a screwdriver see Figure 2.
Figure 2 Installing the Cabinet Side Door
3.10.2 Installing the Front Door
4. Install the front door.
a. Align the shaft-pin side of the door with the front door
post of the cabinet, and plug the lower shaft pin into the
shaft pin holder on the door post.
b. Pull down the spring pins in the middle of the door and
on the top of the door to plug the spring pins into the pin
holes in the cabinet.
5 Install the grounding cable of the door.

.
a Use the crosshead screwdriver to remove the screw of the
. grounding point on the cabinet.
b Connect the other end of the grounding cable on the door and
. the side door to the grounding point of the cabinet, see Figure
3.
Figure 3 Installing a Grounding Cable for a Door
c Use the multimeter to measure the resistance of the grounding

. cable and verify that the grounding cable is connected
properly, see Figure 4.
Figure 4 Measuring the Resistance of a Grounding Cable
6. Verify that the front and rear doors can be opened and closed properly.
For how to open a door of the cabinet, refer to Removing Cabinet Doors.
3.11 Installation Inspection
3.11.1 Checking the Cabinets
Abstract >>
This procedure describes how to verify that the cabinet installation complies with the
related design files and related standards.
Steps >>
1. Verify that the cabinets are installed in a proper position in accordance

with the design requirements.
2. Verify that the cabinet installation meets the shockproof requirements.
3. Verify that the horizontal and vertical deviations of the cabinets are less
than 3 mm, and that cabinet fronts installed in a row are aligned, with a
deviation less than 5 mm.
4. Use the multimeter to measure the resistance between the cabinets and
ground, and verify that the resistance is larger than 5 MΩ.
5. Verify that all screws are tightened properly.
6. Verify that no waste material, such as scrap of cable ties or cables, is left
in the cabinets, and that there is no dirt or handprint inside or outside the
cabinets.
7. Verify that all inlets and outlets on the cabinets are covered with cover
plates or rodent-resistant bags.
8. Verify that the ESD wrist strap is connected to the ESD jack of the
cabinet.
3.11.2 Checking the Assemblies in the Cabinets
Abstract >>
This procedure describes how to verify that the assembly installation in the cabinets
complies with the related design files and related standards.
Steps >>
1. Verify that the assemblies in the cabinets are installed in a proper

position in accordance with the design requirements.
2. Verify that all fastening screws of the assemblies are tightened properly,
and the board extractors are locked in position.
3. Verify that the surfaces of the assemblies are free of dirt.
4. Verify that all labels are properly attached.
5. Verify that blank panels are installed in the empty slots.
6. Verify that the air inlets and air outlets of the fans are not blocked, and
the fan modules are present.
Caution!
The fan modules have been installed in a shelf when the shelf is
delivered. It is not allowed to remove the fan modules to prevent
hardware damage.
3.11.3 Checking the Power Cables and Grounding Cables
Abstract >>
This procedure describes how to verify that the installation of power cables and
grounding cables complies with the related design files and related standards.
Steps >>
1. Verify that the power devices (such as power distribution boxes) are
installed in a proper position in accordance with the design requirements.
2. Verify that the power cables and grounding cables are properly installed.
3. Verify that the power cables and grounding cables used are free from
joints or welding points in between.
4. Verify that all power cables and grounding cables are connected reliably
and correctly.
5. Verify that all exposed wires and O-type terminals are wrapped with
insulation tape or fitted with heat-shrink tubes.
6. Verify that the power cables and grounding cables are properly labeled
at both ends.
3.11.4 Checking the Signal Cables
Abstract >>
This procedure describes how to verify that the signal cable installation complies with the
related design files and related standards.
Steps >>
1. Verify that cable routing meets the engineering design requirements.
2. Verify that each signal cable is connected correctly and reliably at both
ends.
3. Verify that no cable is routed through ventilation holes.
4. Verify that all cables are routed along the horizontal and vertical cable
trays in the cabinet and bound properly with cable ties.
5. Verify that all cable bends are identically even and smooth, with a
bending radius of optical fiber larger than 30 mm.
6. Verify that all cables are properly labeled at both ends, and that the
labels and cable ties face the same direction. Verify that the labels are
attached 20 mm away from the connectors.
7. Verify that the surplus part of the cable ties is cut off without any jagged
edge.
3.11.4.1 Checking the Other auxiliary Devices
Abstract >>
This procedure describes how to verify that the installation of power plugs, sockets, and
peripheral devices complies with the related design files and standards.
Steps >>
1. Verify that the terminal devices are installed in a proper position in

accordance with the design requirements.
2. Verify that there are sufficient AC power sockets for the terminal devices,
and that these sockets are within the reach of the power cables of the
terminal devices.
3. Verify that no waste material, such as desiccant or scrap of cable ties or

cables, is left in the cable trunking, on the cable ladder, or around the
cabinets.
4. Verify that the articles in the equipment room are kept in order.
3.12 Powering on the Devices

Abstract >>
After all the devices are installed, you must power on the cabinet before using the
devices. You must perform checks before powering on the system.
Prerequisite >>
You must check the temperature and humidity in the equipment room and power supply
voltage before power-on, including the following:
• Voltage fluctuation range (-48 V DC): -57 V to -41 V
• Voltage range (–60 V DC): –72 V to –48 V
• Working temperature: –5 ºC to 45 ºC
• Relative humidity: 10% to 95%
You must check the power cables and signal cables in the cabinet before power-on,
including the following:
• The power wires and earthing wires of each shelf are correctly and
securely connected without reverse polarity.
• All the modules and units are installed in correct positions with secure
connections.
• Jumpers on each board are properly set.
• All cables are properly connected.
• The boot version on each board is correct.
Steps >>
1. Verify that all switches are set to the off position.
2. Use a multimeter to measure the resistance of the ground bar in the

cabinet to ensure that no short circuit exists between the power supply
(-48 V) and different grounds (GND, GNDP, and -48 VGND). Verify that
the grounds GND, GNDP, and -48 VGND are short-circuited.
3. Use the multimeter to measure the voltage at the external power input
terminal of the cabinet when the cabinet has zero load, and ensure that
the voltage of the primary power supply is within the allowable range.
4. Turn on the external power supply of the cabinet. If any exception

occurs, turn off the power supply immediately, troubleshooting the
problem, and then turn on the power supply again.
5. Turn on the PDU in the cabinet. If any exception occurs, turn off the PDU
immediately, troubleshooting the problem, and then turn on the PDU
again.
6. Install and power on the power supply module. If any exception occurs,
turn off the power supply immediately, troubleshooting the problem, and
then turn on the power supply again.
7. Install all the boards.
8. Set the switch of the power supply module to the on position. If any
exception occurs, set the switch to the off position immediately,
troubleshooting the problem, and then set the switch to the on position
again.
Example >>
The following example shows how to power on the system in normal cases:
1. Set the external power supply switch to the on position to supply power
to the cabinet. Set the PDU switch to the on position. If any exception
occurs, set the PDU switch to the off position immediately,
troubleshooting the problem, and then set the switch to the on position
again.
2. Set the secondary power switch on the power supply module in each
shelf to the on position. If any exception occurs, turn off the
corresponding power supply module immediately, troubleshooting the
problem, and then turn on the power supply module again.
3. Turn on the power supply. If any exception occurs, turn off the power
supply immediately, troubleshooting the problem, and then turn on the
power supply again.
Related Tasks >>
Normally, the devices can be used properly after being powered on. If you do not need to
use the devices, power off the devices.
Perform the following steps:
1. Turn off the secondary power switch of the power supply module in each
shelf.
2. Turn off the PDU.
3. Turn off the external power supply outside the cabinet.
3.13 Site Clean-Up

Before leaving the site, perform the following procedures:
• Store the installation tools.
• Hand over remaining materials.
• Remove installation leftovers.
Remove installation leftovers from the equipment room and dispose of

the leftovers in accordance with applicable local laws and regulations.
• Complete the installation report.
Submit the installation report to the person in charge.
4 Initial Configuration
4.1 Initial Data Configuration Flow

Table 1 describes the initial data configuration workflow.
Table 1 Initial Data Configuration Flow

Sequence Step Description
Introduce the hardware and software requirements, and how
Configuration
1 to enter the specified configuration mode.
Preparation
For more information, see Configuration Preparation.
Introduce the in-band network management configuration,

Basic Data
2 trap server configuration, and hardware configuration.
Configuration
For more information, see Basic Data Configuration.
Introduces the interconnection configuration between the

device and upper-layer device, and the interconnection
Interconnection
3 configuration between the OLT and ONU.
Configuration
For more information, see Configuring Management Channel
Between the OLT and the GPON ONU.
Introduce the xDSL service configuration, LAN service

Basic Service configuration, multicast configuration, and GPON service
4
Configuration configuration.
For more information, see Basic Service Configuration.
4.2 Using SD Card to Quickly Configure in-band

Network Management Parameters
Abstract >>
The control and switch card of the device is equipped with a SD card slot, and the device
can read the SD card and load the configuration file when the device is restarting.
This procedure introduce how to use the customized SD card tool to configure the
in-band network management parameters, including the in-band IP address and VLAN,
and save the configuration in the SD card. Then the SD card can be used for the in-band
network management configuration at the working site.
The SD Manager is used as an example.
Prerequisite >>
Before the operation, make sure that:
• The SD card is formated in the LINUX form of ext3.
• The related tool, such as Ext2Fsd, has been installed on the PC, and the
maintenance PC can recognize and read the SD card.
• The SD card tool runs in the Java environment, JRE of v1.6 or higher
must be installed in advance, and cannot be installed in the default
destination folder, and the specified destination folder must not contain
any space or Asain language characters.
• The template file of startrun.dat must be created in advanced. The

startrun.dat comes from the NE that has the same networking as the one
to be configured.
Steps >>
Creating the configuration file in the SD card
1. Go to the installation folder of SD manager and run sdmanager.bat under

the folder sdmanager\bin to run the SD manager program, see Figure 1.
Caution!
Install the SD manager under any drive or folder without Asian language
characters included in the file path.
Figure 1 SD Tool Window
2. In the window, select the template file from the Template File drop-down
list. The configuration information in the template file is displayed on the
Template Information tab.
Note:
The template file must be copied to the sdmanager\template folder

before it can be selected in the drop-down list.
3. Configure the IP address, mask, gateway, and VLAN according to the

request.
4. Insert the SD card into the SD Card reader, and then click Write SD. The
system creates a start.fw file under the cfg folder in the SD card.
Loading the configuration file
5. Insert the SD card into the SD card slot of the control and switch card,
and then restart the device.
6. Take out the SD card from the SD card slot after the device has finished
restarting.
4.3 Configuration Preparation
4.3.1 Hardware and Software Requirements
Before the configuration of the ZXA10 C300M/C350M device, make sure that the
hardware and software meet the requirements listed in Table 1.
Table 1 Hardware and Software Requirements

Ite Requirement
m
S
of
tw The card software is installed.
ar
e
H
ar
• The rack, shelf, and cards are installed.
d
• The connections between the cards and the shelf are correct.
w
• The ZXA10 C300M/C350M is powered on and has started.
ar
e
One end of the serial port cable of the ZXA10 C300M/C350M is 8–pin RJ45 registered
jack connector, connecting the CLI port of the control and switch card. The other end of
the serial port cable of the ZXA10 C300M/C350M is DB9 female connector, connecting
the maintenance console computer.Figure 1 shows the serial port cable structure.
Figure 1 Serial Port Cable Structure
For a description of the serial port cable connections, refer to Table 2.
Table 2 Serial Port Cable Connections

End A (connecting the CLI End B (connecting the serial
port on the main control card) port on the maintenance
console computer)
3 3
4 5
5 5
6 2
Note:
Table 2 only lists the used pins.
4.3.2 Entering the Specified Configuration Modes
Context >>
The ZXA10 C300M/C350M supports two login modes: HyperTerminal and Telnet.
• HyperTerminal: You can log in to the device through HyperTerminal

before the in-band network management parameters are configured.
• Telnet: You can log in to the device through Telnet after the in-band
network management parameters are configured.
Steps >>
Logging in to the device
1. Use a local maintenance serial port cable to connect the serial port of the
maintenance PC and the console port on the control and switch card.
2. Run the hyperterminal program on the maintenance PC and specify the

parameters.
3. On the login window, enter enable after the prompt and then enter the
password zxr10 to enter the system management mode ZXAN#.
Entering the specified configuration mode
4. In the ZXAN# mode, run the configure terminal command to enter the
global configuration mode ZXAN(config)#.
5. In global configuration mode, run the following commands to enter the

specified configuration mode.
To Do This
Enter the interface configuration mode Run the interface command.
Enter the MSAG configuration mode for the VoIP Run the msag command.
service configuration
Enter the CES configuration mode for the CES service Run the ces command.
configuration
Enter the VLAN configuration mode Run the vlan command.
Enter the GPON configuration mode Run the gpon command.
Enter the PON configuration mode Run the pon command.
Enter the GPON OLT interface configuration mode Run the interface gpon-olt
command.
Enter the GPON ONU interface configuration mode Run the interface gpon-onu
command.
5 Basic Data Configuration
5.1 Configuring In-Band NM (SNMP v1/v2)

Abstract >>
This procedure describes how to configure in-band Network Management (NM)

parameters.
The SNMP v2c protocol is used for example.
Context >>
In in-band NM mode, the NMS manages the ZXA10 C300M/C350M through the service
channel of the ZXA10 C300M/C350M. Flexible in-band networking modes are provided,
requiring no additional devices. It reduces the costs but the maintenance is not
convenient.
The SNMP v1 and SNMP v2c protocols are described as follows:
• The SNMP v1 protocol is a simple request/response protocol. After the

network management system sends a request to an NE, the NE will
return a response.
The SNMP v1 protocol does not support encryption and authorization. It

provides simple authentication through community names contained in
SNMP. The basic security system is achieved by communities, which
enable authentication when the SNMP network administrator accesses
an NE agent.
• The SNMP v2c protocol, which evolves from the SNMP v1 protocol, adds
and enhances protocol-related operations. It simplifies the trap message
to make it have the same format as other messages. It also provides
verification, encryption, and synchronization mechanisms, which greatly
improve the system security.
Configuration Data >>
For the in-band NM configuration data used in the example, refer to Table 1.
Table 1 In-Band NM Configuration Data

Item Data
Item Data
NE type ZXA10 C300M
In-band NM VLAN ID 1000
In-band NM IP address 10.63.156.129
Uplink port number gei_1/20/1
10.63.11.15
NetNumen NM server IP address
Type: zte-nms
Next-hop gateway IP address 10.63.184.254
IP address: 10.63.11.15
Version: v2c
SNMP server Community name: public
Alarm level: NOTIFICATIONS
UDP Port: 162
Steps >>
Configuring In-band NM parameters at the NE side
1. Enter the global configuration mode.
ZXAN#configure terminal
%Info 20272: Enter configuration commands, one per line. End with
CTRL/Z.
ZXAN(config)#
2. Create an NM VLAN.
ZXAN(config)#vlan 1000
ZXAN(config-vlan1000)#exit
3. Enter the uplink port configuration mode, and add the uplink port to the VLAN.
To Do This
Add the uplink port to the VLAN in tag ZXAN(config)#interface gei_1/20/1
mode ZXAN(config-if)#switchport vlan 1000 tag
ZXAN(config-if)#exit
Add the uplink port to the VLAN in ZXAN(config)#interface gei_1/20/1

untag mode ZXAN(config-if)#switchport mode hybrid
ZXAN(config-if)#switchport default vlan 1000
4. Enter the VLAN port configuration mode.
ZXAN(config)#interface vlan 1000
ZXAN(config-if-vlan1000)#
5. Use the ip address command to configure the in-band NM IP address.
ZXAN(config-if-vlan1000)#ip address 10.63.156.129 255.255.255.0
ZXAN(config-if-vlan1000)#exit
6 (Optional) Use the snmp-server community command to configure an SNMP

. community.
ZXAN(config)#snmp-server community private view allview rw
Note:
The NE SNMP Community name must be consistent with that configured in the NM.
By default, the NE's community name is public.
• When the community name configured in the NM is public, the

default SNMP community name of the NE is used.
• When the SNMP community name configured in the NM is private,

you can set the NE's SNMP community name to private without
deleting the original configuration.
7. Use the snmp-server host command to configure the NM server IP

address.
ZXAN(config)#snmp-server host 10.63.11.15 version 2c public enable
NOTIFICATIONS target-addr-name zte isnmsserver udp-port 162
8. (Optional) If the NM server and the NE are in different network segments,

use the ip route command to confogure the default route of the NM
server (namely, the next-hop gateway IP address).
ZXAN(config)#ip route 0.0.0.0 0.0.0.0 10.63.184.254
ZXAN(config)#exit
9. Save the configuration data.
ZXAN#write
Configuring In-band NM parameters at the network management system side
10. Log in to the NetNumen U31 unified network management system.
11. In the topology view of the NetNumen U31 Unified Management

System - Client window, right-click and choose Create Object > Create
Wireline NE. The Management - New window is displayed.
12 In the left NE Type navigation tree, select C300M for example, and set relevant
. NE parameters in the right pane, see Figure 1.
Figure 1 Management - New Dialog Box
Enter C300M in the Name text box, enter the NE description information in the
Description text box, and enter the NE IP address in the IP text box. Use default
values for other parameters in this dialogue box.
Note:
The Read Community and Write Community parameter values configured on the NE
must be the same as those configured in the network management system.
13. Click New to create the NE.
14. (Optional) Query the configuration result.
ZXAN(config)#show interface vlan 1000
vlan1000 is up, line protocol is up, detect status is OK
Description is none
MAC address is 00d0.0345.2345
ARP Timeout:00:05:00
Internet address is 10.63.156.129/24 /*In-band NM IP

address*/
5.2 Configuring In-Band NM (SNMP v3)

Abstract >>
This procedure describes how to configure in-band NM parameters, including in-band

NM VLAN ID. in-band NM IP address, and Next-hop gateway IP address.
The SNMP v3 protocol is used for example.
In in-band NM mode, the network management exchange information is transmitted

through service channels. Comparing with the SNMP v1/v2, the SNMP v3 protocol
enhances the security and remote configuration capabilities, and messages are
transmitted in encryption mode.
Context >>
The SNMP v3 protocol defines a user-based security model, which consists of the
following three modules:
• Authentication module
• Encryption module
• Time limit module
For the in-band NM configuration data used in the example, refer to Table 2.
Table 2 In-Band NM Configuration Data

Item Data
NE type ZXA10 C300M
In-band NM VLAN ID 1000
In-band NM IP address 10.63.156.129
Uplink port number gei_1/20/1
10.63.11.15
NetNumen NM server IP address
Type: zte-nms
Next-hop gateway IP address 10.63.184.254
view name: allview

Community name: group
SNMP server User name: user
Version: v3
Alarm level: NOTIFICATIONS
Steps >>
Configuring In-band NM parameters at the NE side
CTRL/Z.
ZXAN(config)#
2. Create an NM VLAN.
Enter the uplink port configuration mode, and add the uplink port to the VLAN.
3.
To Do This
Add the uplink port to the VLAN in tag ZXAN(config)#interface gei_1/20/1

mode ZXAN(config-if)#switchport vlan 1000 tag
Add the uplink port is to the VLAN in ZXAN(config)#interface gei_1/20/1

untag mode ZXAN(config-if)#switchport default vlan
1000
4. Enter the VLAN port configuration mode.
ZXAN(config-if-vlan1000)#
5. Use the ip address command to configure the in-band NM IP address.
ZXAN(config-if-vlan1000)#ip address 10.63.156.129 255.255.255.0
6. (Optional) If the view name does not use the default value allview, use
the snmp-server view command to configure SNMP view.
ZXAN(config)#snmp-server view view org included
Note:
In this procedure, the default value allview is used, thus this step can be
skipped.
7. Use the snmp-server community command to configure an SNMP

community.
ZXAN(config)#snmp group group v3 priv write allview
8. (Optional) If it requires to report alarm messages, use the snmp-server

host command to enable the Trap alarm reporting function.
ZXAN(config)#snmp-server host 10.63.11.15 trap version 3 priv private
enable NOTIFICATIONS target-addr-name v3test
Note:
The trap message is automatically transmitted by a managed NE to the

NM server, reporting some emergent events. The ZXA10 C300M/C350M
supports six trap types: SNMP, BGP, OSPF, RMON, STALARM, and
VPN.
9. (Optional) If the NM server and the ZXA10 C300M/C350M are in

different network segments, use the ip route command to set the default
route of the NM server (namely, the next-hop gateway IP address).
ZXAN(config)#exit
ZXAN#write
Configuring In-band NM parameters at the network management system side
11. Log in to the NetNumen U31 unified network management system.
12. In the topology view of the NetNumen U31 Unified Management

System - Client window, right-click and choose Create Object > Create
Wireline NE. The Management - New window is displayed.
1
3 In the left NE Type navigation tree, select C300M, and set relevant NE parameters in the
. right pane.
a.
Click the Basic Parameters tab, and set relevant NE parameters, see Figure 2.
Figure 2 Basic Parameters Tab
Enter C300M in the Name text box, enter the NE description information in the
Description text box, enter the NE IP address in the IP text box, and select v3 from the
SNMP Version drop-down list. Use default values for other parameters in this dialog
box.
Note:
The Read Community and Write Community parameter values set on the NE must be
the same as those set in the network management system.
b.
Click the SNMPv3 tab, and set SNMPv3 parameters, see Figure 3.
Figure 3 SNMPv3 Tab
Enter the SNMP user name in the UserName text box, select auth, priv from the
Security Level drop-down list, select MD5 from the Auth Protocol drop-down list, and
respectively enter the authentication password and private password in the Auth
Password text box and Priv Password text box.
14. Click New to create the NE.
After in-band NM is configured, you can execute the show command to

query configured in-band NM IP addresses and VLAN IDs.
ZXAN(config)#show interface vlan 1000
vlan1000 is up, line protocol is up, detect status is OK
Description is none
MAC address is 00d0.0345.2345
ARP Timeout:00:05:00
Internet address is 10.63.156.129/24 /*In-band NM IP

address*/
5.3 Configuring a Trap Server

Abstract >>
This procedure describes how to configure the IP address of the server that alarms are
reported to. After the IP address is configured, the current alarms are displayed on the
NM server.
For the trap server configuration data used in the example, refer to Table 3.
Table 3 Trap Server Configuration Data

Item Data
Trap server IP address 10.63.11.109
SNMP version ID 2c
Community name private
UDP port number 162
View name allview
Read and write permissions rw
Alarm level NOTIFICATIONS
Steps >>
ZXAN(config)#
2. Use the snmp-server host command to configure the trap server

parameters.
ZXAN(config)#snmp-server host 10.63.11.109 version 2c private enable
NOTIFICATIONS target-addr-name isnmsserver udp-port 162
3. Use the snmp-server community command to configure the view name

and read and write permissions for the allocated community name.
ZXAN(config)#snmp-server community private view allview rw
ZXAN#show snmp config
snmp-server location No.889 BiBo Rd. PuDong District, ShangHai,

China
snmp-server contact +86-021-68895000
snmp-server packetSize 5000
snmp-server engine-id 80000f3e0300d0d032345401
snmp-server engine-id mode mac
snmp-server group GroupPriv0 v3 priv read AllView
snmp-server group GroupPriv5 v3 priv read AllView write ViewPriv5
snmp-server group GroupPriv10 v3 priv read AllView write ViewPriv10
snmp-server group GroupPriv15 v3 priv read AllView write AllView
snmp-server community public view AllView rw
snmp-server community private view allview rw
snmp-server view AllView 1.2 included
snmp-server view AllView 1.3 included
snmp-server view ViewPriv5 1.2 included
snmp-server view ViewPriv5 1.3.6.1.4.1.3902.1082.10.1 excluded
snmp-server host 10.63.11.109 version 2c public enable

NOTIFICATIONS target-add
r-name 1 isnmsserver udp-port 162
5.4 Configuring the System Log Function

Abstract >>
This procedure describes how to configure the system log function to monitor and
maintain the NE in accordance with the system logs. The system logs are transmitted to
the Syslog server.
For the system log function configuration data used in the example, refer to Table 4.
Table 4 System Log Function Configuration Data

Item Data
Syslog server IP address 10.1.1.200
Alarm log level NOTIFICATIONS
Alarm log clearing mode fullcycle
Steps >>
1. In global configuration mode, use the syslog-server host command to

configure the Syslog server IP address and the message type to be
transmitted.
ZXAN(config)#syslog-server host enable 10.1.1.200 alarmlog level

NOTIFICATIONS
snmplog set facility local1
2. Enable the system log function.
ZXAN(config)#logging snmplog enable
ZXAN(config)#logging alarmlog enable
3. (Optional) Query the system log configuration.
ZXAN(config)#show syslog configuration
syslog facility local0
syslog severity 6
syslog-server host enable 10.1.1.200 fport 514 lport 514 alarmlog
level notification snmplog SET facility local1
ZXAN(config)#exit
ZXAN#write
5.5 Hardware Configuration
5.5.1 Adding a Rack

Abstract >>
This procedure describes how to add a rack for the NE.
Context >>
The ZXA10 C300M/C350M can be configured with only one rack.
• The ZXA10 C300M can be configured with an ETSI21 rack or an IEC19

rack.
• The ZXA10 C350M can be configured with a C350MB rack.
For the rack configuration data used in the example, refer to Table 5.
Table 5 Rack Configuration Data

Item Data
NE type ZXA10 C300M
Rack type ETSI21
Steps >>
1. In global configuration mode, add a rack.
ZXAN(config)#add-rack rackno 1 racktype ETSI21
ZXAN(config)#exit
Note:
To add a rack of a different type, you should set the racktype parameter
to the required type.
ZXAN#write
ZXAN(config)#show rack
Rack RackType SupShelfNum CfgShelfNum
-------------------------------------------------
1 ETSI21 3 3
5.5.2 Adding Shelves
Abstract >>
This procedure describes how to add shelves for the NE.
Context >>
•
For the shelf types supported by the ZXA10 C300M, refer to Table 6.
Table 6 Shelf Types Supported by the ZXA10 C300M

NE Type Rack Type Primary Shelf Type Secondary Shelf Type
ETSI21 ETSI_SHELF ETSI_SHELF_EX

ZXA10 C300M
IEC19 IEC_SHELF IEC_SHELF_EX
In configuring the ZXA10 C300M, the shelfno parameter of the secondary

shelf ranges from 2 to 3, and the connectid parameter of the secondary shelf
ranges from 1 to 2. In other words, one primary shelf can be connected to at
most two secondary shelves.

•
For the shelf types supported by the ZXA10 C350M, refer to Table 7.
Table 7 Shelf Types Supported by the ZXA10 C350M

NE Type Rack Type Primary Shelf Type Secondary Shelf Type
ZXA10 C350M C350MB C350MB_SHELF -
The ZXA10 C350M can be configured with only one shelf, and no
secondary shelf can be configured.
For the shelf configuration data, refer to Table 8.
Table 8 Shelf Configuration Data

Item Data
NE type ZXA10 C300M
Primary shelf type ETSI_SHELF
Steps >>
1. In global configuration mode, add a shelf.
ZXAN(config)#add-shelf shelfno 1 shelftype ETSI_SHELF
ZXAN(config)#show shelf
Rack Shelf ShelfType CleiCode Serial-Number

ShelfPower(W)
--------------------------------------------------------------------------------
1 1 ETSI_SHELF UNKNOWN
0.000
5.5.3 Adding Cards
Abstract >>
This procedure describes how to add cards for the NE.
Context >>
You can use either of the following two methods to add cards for the NE:
• Enable the automatic card configuration function.
After the function is enabled, the rack, primary shelf, and the main control
card and service card of the primary shelf are added automatically. The
secondary shelf must be added manually. After a secondary shelf is
added manually, the control and switch card and service card of the
secondary shelf are added automatically by the PnP function.
• Manually add cards.
With this method, when a primary shelf is added, its control and switch
card is automatically added. The service card of the primary shelf and the
control and switch card and service card of the secondary shelf must be
manually added by executing the add-card command.
Table 9 describers the card configurations for 19-inch shelf.
Table 9 Card configuration for a 19-inch Shelf

Slot Number Card Type
0/1 Power card
2-9, 12-17 Subscriber card, Pon interface card, and P2P interface card
18 Common interface card
19/20 Uplink card
Table 10 describers the card configurations for 21-inch shelf.
Table 10 Card configuration for a 21-inch Shelf

Slot Number Card Type
0/1 Power card
2-9, 12-19 Subscriber card, Pon interface card, and P2P interface card
20 Common interface card
21/22 Uplink card
For the card Configuration data used in the example, refer to Table 11.
Table 11 Card Configuration Data
Item Data
NE type ZXA10 C350M
Shelf/rack/slot number 1/1/8
Card name DBWD
Steps >>
1.
In global configuration mode, add a card.
To Do This
Enable the automatic card configuration function ZXAN(config)#set-pnp enable

ZXAN(config)#show pnp
Equipment PNP function is enable.
Run the add-card command to add a card ZXAN(config)#add-card rackno 1

shelfno 1 slotno 8 DBWD
2.
(Optional) Query the configuration result.
ZXAN(config)#show card
Rack Shelf Slot CfgType RealType Port HardVer SoftVer Status
-------------------------------------------------------------------------------
1 1 0 PRWG PRWG 0 090301 INSERVICE
1 1 2 FTGKN 48 OFFLINE
1 1 3 VCWKC 48 OFFLINE
1 1 4 ACWKC 48 OFFLINE
1 1 5 GDFOU 0 OFFLINE
1 1 6 DSWC 32 OFFLINE
1 1 7 ACWKC ACWKC 48 110401 V4.0.2 INSERVICE
1 1 8 DBWD 48 OFFLINE
1 1 9 SMWGF SMWGF 32 111101 V4.0.2 INSERVICE
1 1 10 SCXN SCXN 4 120900 V4.0.2 INSERVICE
1 1 11 SCXN SCXN 4 120900 V4.0.2 STANDBY
1 1 12 VCWKC VCWKC 48 110702 V4.0.2 INSERVICE
1 1 13 VCWKC 48 OFFLINE
1 1 16 DBWD DBWD 32 080501 V4.0.2 INSERVICE
1 1 19 HUTQ HUTQ 4 100101 V4.0.2 INSERVICE
1 1 20 GUTQ 4 OFFLINE
5.5.4 Adding Daughter Cards
Abstract >>
This procedure describes how to add daughter cards for the NE.
Context >>
For the daughter card types supported by the ZXA10 C300M/C350M, refer to Table 12.
Table 12 Sub-Card Types

NE Type Sub-Card Type Description
Network processor daughter card, implementing functions
including IP address conversion for the VoIP service and
MAPP daughter
control flow.
ZXA10 card
It is inserted on the control and switch card, and works
C300M with the VoIP processing card.
VoIP daughter Implements bidirectional signal conversion between voice

card TDM signals and IP packets.
ZXA10 VoIP daughter Implements bidirectional signal conversion between voice

C350M card TDM signals and IP packets.
For the working modes supported by the NE in voice services, refer to Table 13.
Table 13 Working Modes

NE Type Mode Description Remarks
The MAPP daughter card works with the
Common VoIP processing card. In this case, the
mode VoIP daughter card is inserted on the VoIP The MAPP daughter card is
processing card. added by default. Before
ZXA10 configuring the VoIP
C300M Only the VoIP daughter card is used to daughter card, you must
process voice signals, and there is no first delete the MAPP
Compact
need to configure the VoIP processing daughter card.
mode
card. In this case, the VoIP daughter card
is inserted on the control and switch card.
Only the VoIP daughter card is used to

process voice signals, and there is no The VoIP daughter card is
ZXA10 Compact
need to configure the VoIP processing added to the ZXA10
C350M mode
card. In this case, the VoIP daughter card C350M by default.
is inserted on the control and switch card.
For the daughter card configuration data used in the example, refer to Table 14.
Table 14 Sub-Card Configuration Data

Item Data
NE type ZXA10 C300M
NE mode Compact mode
Sub-card slot number 10
Sub-card number 1
Sub-card type VoIP
Steps >>
1.
Enter the global configuration mode.
ZXAN(config)#
2.
Add a VoIP daughter card.
ZXAN(config)#del-subcard shelfno 1 slotno 10 subcardno 1
ZXAN(config)#add-subcard shelfno 1 slotno 10 subcardno 1 voip
Table 15 describes the slotno parameter of the VoIP daughter card.
Table 15 Command Parameter Description

Parameter Description
For ZXA10 C300M device,
In common mode, slotno is the number of slot where the VoIP card is located.
In compact mode, slotno is the number of slot where the control and switch card
slotno is located.
For ZXA10 C350M device

slotno is set to the number of slot where the control and switch card is located.
3.
(Optional) Query the configuration result.
ZXAN(config)#show subcard
Rack Shelf Slot Subcard CfgType RealType Port SoftVer Status PhySlot
-------------------------------------------------------------------------------
1 1 10 1 VOIP VOIP 0 N/A. INSERVICE N/A
1 1 11 1 VOIP VOIP 0 N/A. INSERVICE N/A
5.6 Configuring Management Channel Between the

OLT and the GPON ONU
Abstract >>
When the ZXA10 C300M/C350M serves as an OLT and is connected to an GPON ONU,
it delivers the management IP address of the ONU. This procedure describes how to
configure the management channel between the OLT and the GPON ONU. The
management channel is used to log in to the ONU for configuration.
Table 1 lists the configuration data for configuring the management channel between the
OLT and the GPON ONU.
Table 1 Configuration Data Configuring the Management Channel Between the OLT
and the GPON ONU
Item Data
VLAN ID 100
In-band management IP address 1.2.3.100
T-CONT 1
T-CONT name t1
GEM Port 1
GEM port name g1
IP address pool 1.2.3.4–1.2.3.10
Steps >>
1. Configure the in-band EMS VLAN and IP address of the OLT.
ZXAN(config-if)#ip address 1.2.3.100 255.255.255.0
2. Configure the VLAN unicast channel for the OLT side.
ZXAN(config)#interface gpon-onu_1/4/1:1
ZXAN(config-if)#tcont 1 name t1 profile default
ZXAN(config-if)#gemport 1 name g1 tcont 1
ZXAN(config-if)#service-port 1 vport 1 user-vlan 100 vlan 100
3. Use the pon-onu-mng command to configure the VLAN unicast channel

for the ONU side.
ZXAN(config)#pon-onu-mng gpon-onu_1/4/1:1
ZXAN(gpon-onu-mng 1/4/1:1)#gemport 1 flow 1

4.
Allocate an IP address to the ONU by one of the following methods:
To Do This
Use the mgmt-ip command to ZXAN(gpon-onu-mng 1/4/1:1)#mgmt-ip 1.2.3.4

configure the address directly 255.255.255.0 vlan 100 priority 0
in pon-onu-mng mode route 1.2.3.0 255.255.255.0 1.2.3.100
ZXAN(gpon-onu-mng 1/4/1:1)#exit
Allocate the address In pon mode, create an IP address pool and then
automatically by the IP bind the address pool to the pon port. In
address pool pon-onu-mng mode, allocate an IP address
automatically.
ZXAN(config)#pon
ZXAN(config-pon)#ip-pool test begin 1.2.3.2
end 1.2.3.10
255.255.255.0 vlan 100 priority 0 route 1.2.3.0
255.255.255.0 1.2.3.100
ZXAN(config-pon)#ip-pool-bind gpon-olt_1/6/1
test
ZXAN(config-pon)#exit
ZXAN(config)#pon-onu-mng gpon-onu_1/4/1:1
ZXAN(gpon-onu-mng 1/4/1:1)#mgmt-ip auto-assign
Configure the address in ZXAN(gpon-onu-mng 1/4/1:1)#switchport-bind

pon-onu-mng mode switch_0/1 iphost 1
ZXAN(gpon-onu-mng 1/4/1:1)#ip-host 1 ip 1.2.3.4
mask 255.255.255.0 gateway 1.2.3.100
ZXAN(gpon-onu-mng 1/4/1:1)#vlan-filter-mode
iphost 1 tag-filter vlan-filter
untag-filter discard
ZXAN(gpon-onu-mng 1/4/1:1)#vlan-filter
iphost 1 pri 0 vlan 100
5.
To release the IP address on the ONU, perform the following operations
as required:
To Do This
Release the IP address directly in Run the following command:

pon-onu-mng mode or automatically ZXAN(gpon-onu-mng 1/4/1:1)#mgmt-ip
release
Allocate the IP address in pon-onu-mng Run the following commands:

mode ZXAN(gpon-onu-mng 1/4/1:1)#no
vlan-filter-mode iphost 1
ZXAN(gpon-onu-mng 1/4/1:1)#ip-host 1
ip 0.0.0.0
mask 0.0.0.0
6 Basic Service Configuration
6.1 VoIP Service Configuration Flow

The Voice over Internet Protocol (VoIP) service compresses voice signals by using a
voice compression algorithm, packetizes the compressed voice data in accordance with
TCP/IP, and then sends the data packets to the receiver over an IP network. On the
receiving side, the data packets are received and decompressed to produce the original
voice signals. In this way, voice signals can be transported over the Internet.
The VoIP service takes advantage of the Internet that connects to all IP networks around
the world to provide more and better services. It transmits voice, fax, video, and data
services over IP networks with less cost.
Before the VoIP narrowband service is provisioned, the following information needs to be
configured:
• Media Gateway Controller (MGC)
• Media Gateway (MG)
• VoIP resources
Before the configuration of the VoIP service, you need to obtain the ZXA10
C300M/C350M configuration data from the Soft Switch (SS) and the basic configuration
data of the ZXA10 C300M/C350M. For a description of the configuration parameters,
refer to Table 1.
Table 1 Data Required Before Configuration

Equipment Data
Type and basic properties.
IP address and protocol port number (or domain name).
Interface registration mode between the SS and the ZXA10

C300M/C350M, including domain name (or IP address) and protocol
SS port number.
IP address, port number, and domain name of the ZXA10

C300M/C350M configured on the SS.
Termination ID and VoIP resources configured on the SS for the

ZXA10 C300M/C350M's narrowband subscriber card.
Equipment Data
Upper-layer networking mode.
Address of the next hop.

ZXA10 Whether the uplink switch port is assigned to a VLAN. If yes, the
C300M/C350M VLAN mode and VLAN ID are required.
Phone numbers of all subscribers (area code + phone number) are

required if the self-switching function is supported.
Note:
• The H.248 port number is generally 2944.
• When the ZXA10 C300M/C350M registers on the SS in domain name

mode, the domain name that the SS configures for the ZXA10
C300M/C350M must be known.
6.1.1 VoIP POTS Configuration Flow (H.248)
Overview >>
This section describes the VoIP Plain Old Telephone Service (POTS) configuration
workflow when the H.248 protocol is used between the Media Gateway Controller (MGC)
and Media Gateway (MG), including the networking diagram, configuration workflow
chart, and the description of the configuration steps.
Related Information >>
The VoIP POTS service uses a media access gateway to implement the compression,
packetization, and address translation of analog voice signals and then transports the
data packets through the connectionless UDP over IP packet switched networks.
The compact mode is available for provisioning H.248 compliant VoIP POTS service. In
this mode, a VoIP daughter card installed on a control and switch card implements the
conversion between TDM voice signals into IP packets. The VoIP daughter card does not
occupy an independent slot.
The compact mode can be used for both the ZXA10 C300M and ZXA10 C350M. During
the VoIP POTS service for media NAT configuration, you are required to select the slot
number of the control and switch card on which the VoIP daughter card is located.
Networking Diagram >>
Figure 1 shows the VoIP POTS networking diagram when the H.248 protocol is used
between the ZXA10 C300M/C350M and the SS.
In the actual configuration, the SS is known as the MGC and the ZXA10 C300M/C350M
is known as the MG. The ZXA10 C300M/C350M accesses the IP network through an
uplink interface and communicates with the SS through H.248. The MGC implements MG
resource registration and management, and call control. The MG processes and
packetizes media streams and sends data packets to the IP network. In the reverse
direction, the MG receives data packets from the IP network and decodes the packets.
Figure 1 VoIP POTS Networking Diagram (H.248)
SS: Soft Switch
Configuration Work Flow >>
Figure 2 shows the VoIP POTS configuration workflow when the H.248 protocol is used
between the ZXA10 C300M/C350M and the SS.
Figure 2 VoIP POTS Configuration Work Flow (H.248)
The configuration procedure can be divided into three parts:
• Card configuration
Add all required cards for service provisioning.
• Narrowband data configuration
Configure the MGC, the MG, and the IP addresses of the MG's media
stream and signaling stream (route information).
• Broadband data configuration
Configure a VoIP VLAN, bind the physical port to the VLAN, and
configure a static route.
Note:
When the ZXA10 C300M/C350M and the SS are not located in the same network
segment, a static route (the next hop address) must be configured for the ZXA10
C300M/C350M.
Table 2 describes the VoIP POTS configuration workflow when the H.248 protocol is
used between the ZXA10 C300M/C350M and the SS.
Table 2 VoIP POTS Configuration Work Flow Description (H.248)
Operation Description
Use the add-card command to add all cards required for
Add cards.
Configure the IP address, port number, and protocol type

Configure the MGC.
of the MGC. For details, refer to Configuring the MGC.
Configure the protocol port that interworks with the MGC.

Configure the MG.
For details, refer to Configuring the MG.
Configure the media and The signaling IP address and the media IP address of the
signaling IP addresses MG can be the same or different. For details, refer to
and routes. Configuring Media and Signaling IP Addresses.
Configure termination For details, refer to Configuring Termination IDs for VoIP
IDs for VoIP resources. Resources.
Configure termination
For details, refer to Configuring Termination IDs for
IDs for narrowband
Narrowband Subscriber Circuits.
subscriber circuits.
Configure media NAT. For details, refer to Configuring Media NAT.
Configure a VoIP VLAN. For details, refer to Configuring a VoIP VLAN.
Bind the physical port to

For details, refer to Binding the Uplink Port to the VLAN.
the VLAN.
6.1.2 VoIP POTS Configuration Flow (SIP)
Overview >>
This topic describes the VoIP POTS configuration workflow when the Session Initiation
Protocol (SIP) is used between the MGC and MG. This section provides the networking
diagram, configuration workflow chart, and the description of configuration steps.
The VoIP POTS service uses a media access gateway to implement the compression,
packetization, and address translation of analog voice signals and then transports the
data packets through the connectionless UDP over IP packet switched networks.
The compact mode is available for provisioning H.248 compliant VoIP POTS service. In
this mode, a VoIP daughter card installed on a control and switch card implements the
conversion between TDM voice signals into IP packets. The VoIP daughter card does not
occupy an independent slot.
The compact mode can be used for both the ZXA10 C300M and ZXA10 C350M. During
the VoIP POTS service for media NAT configuration, you are required to select the slot
number of the control and switch card on which the VoIP daughter card is located.
Figure 3 shows the VoIP POTS networking diagram when the SIP is used between the
ZXA10 C300M/C350M and the SS.
In the actual configuration, the SS is known as the MGC and the ZXA10 C300M/C350M
is known as the MG. The ZXA10 C300M/C350M accesses the IP network through an
uplink interface and communicates with the SS through SIP. The MGC implements MG
resource registration and management, and call control. The MG processes and
packetizes media streams and sends data packets to the IP network. In the reverse
direction, the MG receives data packets from the IP network and decodes the packets.
Figure 3 VoIP POTS Networking Diagram (SIP)
SS: Soft Switch SIP: Session Initiation Protocol
Configuration Work Flowc >>
Figure 4 shows the VoIP POTS configuration workflow when the SIP is used between the
ZXA10 C300M/C350M and the SS.
Figure 4 VoIP POTS Configuration Work Flow (SIP)
The configuration procedure can be divided into three parts:
• Card configuration
Add all required cards for service provisioning.
• Narrowband data configuration
Configure the MGC, the MG, the IP addresses of the MG's media stream
and signaling stream (route information), and SIP data.
• Broadband data configuration
Configure a VoIP VLAN, bind the physical port to the VLAN, and
configure a static route.
Table 3 describes the VoIP POTS configuration workflow when the SIP is used between
the ZXA10 C300M/C350M and the SS.
Table 3 VoIP POTS Configuration Work Flow Descriptions (SIP)
Use the add-card command to add all cards required for
Add cards.
Configure the IP address, port number, and protocol type

Configure the MGC.
of the MGC. For details, refer to Configuring the MGC.
Configure the protocol port that interworks with the MGC.

Configure the MG.
For details, refer to Configuring the MG.
Configure the media and The signaling IP address and the media IP address of the
signaling IP addresses MG can be the same or different. For details, refer to
and routes. Configuring Media and Signaling IP Addresses.
Configure the SIP data, including the SIP port number,

Configure the SIP data. SIP number analysis table, SIP user, and SIP user ID. For
details, refer to Configuring SIP Parameters.
Configure termination IDs For details, refer to Configuring Termination IDs for VoIP
for VoIP resources. Resources.
Configure media NAT. For details, refer to Configuring Media NAT.
Configure a VoIP VLAN. For details, refer to Configuring a VoIP VLAN.
Bind the physical port to

For details, refer to Binding the Uplink Port to the VLAN.
the VLAN.
6.1.3 VoIP ISDN Configuration Flow
Overview >>
The VoIP ISDN services include ISDN BRA service and ISDN PRA service:
• ISDN BRA service
The VoIP-based ISDN BRA service is also known as 2B+D service. It

uses a twisted-pair copper cable to access two 64-Kbps data channels
simultaneously. The two channels are called B channels, which carry
voice or data information. There is another channel called D channel,
which works at the rate of 16 Kbps and transmits signaling information.
The general data rate of ISDN BRA is 144 Kbps. ISDN BRA is applicable
in low-capacity scenarios, such as a family network or a small business
network.
• ISDN PRA service
The VoIP-based ISDN PRA service is also known as 30B+D service. There are 30 B
channels and one D channels on one PRA interface. The rate of each B channel or D
channel is 64 Kbps, and the total rates for all the channels are 1.920 Mbps, which is
known as 2-Mbps link. Each PRI can be a PRA user cluster or multiple PRIs
compose a user cluster.
The 30B+D service is applicable in the following scenarios:
→ Internet high-speed connection
→ Remote education, video conference, and telemedicine
→ Sales management of chain stores
→ Remote login and LAN interconnection
→ Private Branch Exchange (PBX) connection, providing voice

channels
Two networking diagrams are provided depending on different VoIP ISDN services.
• VoIP ISDN BRA networking diagram
Figure 5 shows the networking diagram of the ZXA10 C300M/C350M for

VoIP ISDN BRA service. The DEWD card of the ZXA10 C300M/C350M
provides a BRI to connect the NT-1 to which telephones are connected.
Figure 5 VoIP ISDN BRA Networking Diagram
SS: Soft Switch SCTP: Stream Control Transmission Protocol
VoIP ISDN PRA networking diagram
Figure 6 shows the networking diagram of the ZXA10 C300M/C350M for VoIP ISDN
PRA service. The ZXA10 C300M/C350M serves as a trunk gateway. The DEWU card of
the NE provides an E1 interface to connect the PBX. The PRA protocol is used between
the NE and the PBX.
Figure 6 VoIP ISDN PRA Networking Diagram
Configuration Flowchart >>
Figure 7 shows the configuration workflow chart of the ZXA10 C300M/C350M for
provisioning VoIP ISDN services.
Figure 7 VoIP ISDN Configuration Flowchart
Table 4 describes the VoIP ISDN configuration workflow.
Table 4 VoIP ISDN Configuration Flow Descriptions

Use the add-card command to add a subscriber card
Add a subscriber card.
that supports the ISDN service.
The SCTP is used between the ZXA10 C300M/C350M

Configure the SCTP port
and the SS. Use the crtlport add command to configure
number.
the SCTP port number.
Configure the AS, ASP, and the

For details, refer to Configuring the AS, ASP, and
association between the AS and
Association.
ASP.
Configure the D channel. For details, refer to Configuring the D Channel.
Configure termination IDs for For details, refer to Configuring Termination IDs for
ISDN subscriber circuits ISDN Subscriber Circuits.
6.2 Basic VoIP Service Configurations
6.2.1 Configuring the MGC
Abstract >>
This procedure describes how to configure the IP address, port number, and protocol
type of the MGC that connects to the NE. The MGC is responsible for MG resource
registration and management, and call control.
Context >>
The relations between MGC types and port numbers are described in Table 5.
Table 5 Relations Between MGC Types and Port Numbers

MGC Protocol Between Port Remarks
Type the MGC and MG Number
H.248 2944 If another port number is to be used,
SS configure the port number as required and
MGCP 2427 add NAT port numbers.
SIP
SIP 5060 -
server
Table 6 describes the MGC configuration data used in the example.
Table 6 MGC Configuration Data

Item Data
NE type ZXA10 C300M/C350M
MGC IP 10.61.198.200
MGC ID 1
Protocol type H.248
Port number 2944
MGC type zte
Steps >>
1. Enter the MSAG configuration mode.
ZXAN(config)#msag
ZXAN(config-msag)#
2. Use the mgc add command to configure the IP address, port number,
and protocol type of the MGC.
ZXAN(config-msag)#mgc add 1 10.61.198.200 port 2944 type 1
3. (Optional) Query the MGC configuration.
ZXAN(config-msag)#show msag mgc
MGCID:1
MGCTYPE:1
MGCIP:10.61.198.200
MGCPORT:2944
MGCDOMAINNAME:
MGCINFORMATION:0
MGCMD5-PROFILE:0
-------------------------------------
1 rows are effected
Example >>
To set the MGC port number to 11000, perform the following operations:
1. Use the show msag ctrlport command to query the existing port numbers
and find an unused serial number, such as 13.
ZXAN(config-msag)#show msag ctrlport
ctrlid:3
info:TCP
port:23
portcount:1
type:ROS
-------------------------------------
ctrlid:4
info:UDP
port:161
portcount:1
type:ROS
-------------------------------------
ctrlid:5
info:UDP
port:162
portcount:1
type:ROS
-------------------------------------
ctrlid:6
info:TCP
port:5001
portcount:1
type:ROS
-------------------------------------
ctrlid:7
info:TCP
port:21
portcount:1
type:ROS
-------------------------------------
ctrlid:8
info:UDP
port:5100
portcount:1
type:ROS
-------------------------------------
2. Use the ctrlport add command to set the MGC port number to 11000.
ZXAN(config-msag)#ctrlport add 13 11000 info 0
3. Query the configuration result.
ZXAN(config-msag)#show msag ctrlport
ctrlid:3
info:TCP
port:23
portcount:1
type:ROS
-------------------------------------
ctrlid:4
info:UDP
port:161
portcount:1
type:ROS
-------------------------------------
ctrlid:5
info:UDP
port:162
portcount:1
type:ROS
-------------------------------------
ctrlid:6
info:TCP
port:5001
portcount:1
type:ROS
-------------------------------------
ctrlid:7
info:TCP
port:21
portcount:1
type:ROS
-------------------------------------
ctrlid:8
info:UDP
port:5100
portcount:1
type:ROS
-------------------------------------
ctrlid:13
info:UDP
port:11000
portcount:1
type:VXWORKS
-------------------------------------
6.2.2 Configuring the MG
Abstract >>
This procedure describes how to configure the MG and the parameters for connecting the
MGC.
An MG is a device that converts media formats between two networks. The MG, being
controlled by an MGC, packetizes media streams in a PSTN and sends the packets to an
IP network. In the reverse direction, the MG receives data packets from the IP network,
decodes the packets to media streams, and then sends the media streams to the PSTN.
If an SS connected to the MG serves as the MGC, the protocol port number used by the
MG must be configured. If an SIP server connected to the MG serves as the MGC, the
domain name of the MG must be configured for the MG. Table 7 describes the MG
configuration data used in the example.
Table 7 MG Configuration Data

Item Data
MG ID 1
SS MGC ID 1
MG protocol port number 2944
MG ID 1
MGC ID 1
SIP server
MG domain name ims.fj.mobile.com
MG protocol port number 5060
Steps >>
ZXAN(config)#msag
ZXAN(config-msag)#
2. Configure the MG parameters.
To Do This
Configure the protocol port if the MGC connected to ZXAN(config-msag)#mg add 1 1

the MG is an SS port 2944
Configure the protocol port if the MGC connected to ZXAN(config-msag)#mg add 1 1

the MG is an SIP server domain-name
ims.fj.mobile.com port 5060
3.
(Optional) Query the configuration of the MG to which an SS is connected.
ZXAN(config-msag)#show msag mg
the base attribute of MG:
mgid:1
protype:H248
version:1
encodetpr:TEXT
mgport:2944
translay:IP
transpro:UDP
domname:
mginfo:0
mgcid1:1
mgcid2:0
mgcid3:0
mgcid4:0
curmgc:0
-------------------------------------
1 rows are effected
6.2.3 Configuring Media and Signaling IP Addresses
Abstract >>
This procedure describes how to configure the media IP address and signaling IP
address of the MG. The signaling IP address is used for the communication between the
MGC and the MG. The media IP address is used for media stream (such as voice and fax
signals) transmission between terminals.
Context >>
The media IP address and the signaling IP address can be the same IP address or two IP
addresses in different network segments.
Media stream and signaling stream are usually assigned to different VLANs. The media
stream and signaling stream can be accessed by the uplink device through the same
uplink port or different uplink ports.
Table 8 describes the configuration data for media IP address and signaling IP address
configuration.
Table 8 Configuration Data for Media and Signaling IP Address Configuration

Item Data
Media IP address/signaling IP address 10.63.86.113/255.255.255.0
Next hop IP address for media stream 10.63.86.254
Note:
The next hop IP address is the static route of the media IP address. The next hop IP
address must be configured when the MG and the MGC are located in different network
segments.
Steps >>
ZXAN(config)#msag
ZXAN(config-msag)#
2. Use the voip interface add command to configure the MG media IP

address and signaling IP address.
ZXAN(config-msag)#voip interface add ctrl-ip 10.63.86.113 ctrl-mask

255.255.255.0
media-ip 10.63.86.113 media-mask 255.255.255.0
ZXAN(config-msag)#exit
3. (Optional) Configure the next hop IP address for media stream.
4. (Optional) Query the media IP address and signaling IP address

configuration.
ZXAN(config)#show msag voip-ipaddr
mgid:1
ctrl-ip:10.63.86.113
ctrl-mask:255.255.255.0
media-ip:10.63.86.113
media-mask:255.255.255.0
route-mode:L3
-------------------------------------
1 rows are effected
6.2.4 Configuring Termination IDs for VoIP Resources
Abstract >>
This procedure describes how to configure termination IDs for VoIP resources.
Context >>
A narrowband VoIP resource is uniquely identified by a termination ID. The VoIP

resource termination ID is a character string with a maximum length of 64 bytes. In
general, only one type of termination IDs can be used in a system.
Table 9 describes the available types of VoIP resource termination IDs supported by the
ZXA10 C300M.
Table 9 VoIP Resource Termination ID Types

Type Description
Type 2 termination IDs have flexible lengths and are added for VoIP resources
Type 2
directly.Format: RTP0–RTP59.
Type 3 termination IDs have a fixed length and the length can be configured as
Type 3
required.Format: RTP001–RTP059.
Note:
The parameter digit-length (default: 3) must be configured when type 3 termination IDs
are set for VoIP resources.
Table 10 describes the configuration data for the configuration of VoIP resource
termination IDs.
Table 10 Configuration Data for VoIP Resource Termination IDs

Ite Data
m
N
E
ZXA10 C300M
ty
pe
M
G 1
ID
St
ar
tin
g
0
nu
m
be
r
Pr
efi RTP
x
Ty
pe
of
V
oI
P
re
so
• Type 2
ur
• Type 3
ce
te
r
mi
na
tio
n
ID
Steps >>
ZXAN(config)#msag
ZXAN(config-msag)#
2. Use the rtp terminationid add command to configure termination IDs for
VoIP resources.
To Do This
Configure termination IDs for VoIP resources if ZXAN(config-msag)#rtp

type 2 termination IDs are used for VoIP resources terminationid add
RTP 240 mgid 1 type 2
begin-no 0
Configure termination IDs for VoIP resources if ZXAN(config-msag)#rtp

type 3 termination IDs are used for VoIP resources terminationid add
RTP 240 mgid 1 type 3
digit-length 3
begin-no 0
3 (Optional) Query the termination ID configurations (the termination ID configurations

. of six resources are displayed below).
• When type 2 termination IDs are set and the termination ID prefix is
RTP, the configuration results are as follows:
ZXAN(config-msag)#show msag rtp terminationid
seq mgid terminationid
1 1 RTP0
2 1 RTP1
3 1 RTP2
4 1 RTP3
5 1 RTP4
6 1 RTP5
• When type 3 termination IDs are set, the termination ID prefix is

RTP, and the digital length is 3, the configuration results are as
follows:
ZXAN(config-msag)#show msag rtp terminationid
seq mgid terminationid
1 1 RTP000
2 1 RTP001
3 1 RTP002
4 1 RTP003
5 1 RTP004
6 1 RTP005
6.2.5 Configuring Termination IDs for Narrowband Subscriber Circuits
Abstract >>
This procedure describes how to configure termination IDs for narrowband subscriber
circuits.
Context >>
A narrowband subscriber circuit is uniquely identified by a termination ID. The

narrowband subscriber circuit termination ID is a character string with a maximum length
of 64 bytes. In general, only one type of termination IDs can be used in a system.
Table 11 describes the available types of narrowband subscriber circuit termination IDs
supported by the ZXA10 C300M/C350M.
Table 11 Narrowband Subscriber Circuit Termination ID Types

Type Description Format Remarks
Type 2 termination IDs have flexible Type 2 is used when the
Type USER0–USE
lengths and are added for narrowband MG connects to an SS
2 R31
subscriber circuits directly. provided by HUAWEI.
Type 3 termination IDs have a fixed Type 3 meets all

Type USER000–U
length and the length can be requirements of
3 SER031
configured as required. subscribers.
Note:
The parameter digit-length (default: 3) must be configured when type 3 termination IDs
are set for narrowband subscriber circuits.
Table 12 describes the configuration data for the configuration of narrowband subscriber
circuit termination IDs.
Table 12 Configuration Data for Narrowband Subscriber Circuit Termination IDs

Ite Data
m
N
E
ZXA10 C300M/C350M
ty
pe
M
G 1
ID
St
art
in
g
0
nu
m
be
r
Pr
efi USER
x
R
ac
k
N
o./
S
he
lf
N
o./
Sl
ot
N 1/1/3
o.
of
th
e
V
oI
P
su
bs
cri
be
r
Ite Data
m
ca
rd
Ty
pe
of
na
rr
o
w
ba
nd
su
bs
• Type 2
cri
• Type 3
be
r
cir
cu
it
ter
mi
na
tio
n
ID
Steps >>
ZXAN(config)#msag
ZXAN(config-msag)#
Use the slc terminationid add command to configure the narrowband subscriber circuit
2. termination IDs.
To Do This
Configure the narrowband subscriber circuit ZXAN(config-msag)#slc

termination IDs if type 2 termination IDs are used terminationid add rackno 1
for narrowband subscriber circuits shelfno 1 3 USER type 2 1
Configure the narrowband subscriber circuit ZXAN(config-msag)#slc

termination IDs if type 3 termination IDs are used terminationid add rackno 1
for narrowband subscriber circuits shelfno 1 3 USER type 3
begin-no 0
digit-length 3 1
3 (Optional) Query the termination ID configurations of narrowband subscriber circuits.
.
• When type 2 termination IDs are set, the configuration results are as
follows:
ZXAN(config-msag)#show msag slc terminationid 3
rack:1 shelf:1 slot:3
--------------------------------------------------
Index Mgid Terminationid
1 1 USER0
2 1 USER1
3 1 USER2
4 1 USER3
5 1 USER4
6 1 USER5
• When type 3 termination IDs are set, the configuration results are as
follows:
ZXAN(config-msag)#show msag slc terminationid 3
rack:1 shelf:1 slot:3
------------------------------------------------
Index Mgid Terminationid
1 1 USER000
2 1 USER001
3 1 USER002
4 1 USER003
5 1 USER004
6 1 USER005
6.2.6 Configuring Media NAT
Abstract >>
This procedure describes how to configure media NAT address and UDP port number.
The NE assigns private network addresses to VoIP media streams. A NAT process must
be completed before the media streams are transported to a public network. During the
NAT process, the private network addresses are translated to public network addresses
and UDP ports are assigned to the media streams.
Context >>
The NAT configuration difference between the ZXA10 C300M and ZXA10 C350M is that
the locations of the daughter cards that provide the NAT function are different.
Table 13 describes the media NAT configuration data.
Table 13 Media NAT Configuration Date

Item Data
Main control card SCXN
Slot number of the VoIP daughter card 10
Serial number of the VoIP daughter card 1

ZXA10
Slot number of the MAPP daughter card 10
C300M
Ouput/input physical port number 5
Output IP address 10.63.86.113
UDP port number 20000
Main control card SCXN
Slot number of the VoIP daughter card 6
ZXA10 Serial number of the VoIP daughter card 6

C350M Ouput/input physical port number 5
Output IP address 10.63.86.113
UDP port number 24000
Note:
The minimum UDP port number is 20000. Each daughter card requires a range of 4000
port numbers.
Steps >>
ZXAN(config)#msag
ZXAN(config-msag)#
Use the media-nat add command to configure the media NAT
2. parameters.
To Do This
Configure media NAT ZXAN(config-msag)#media-nat add

parameters for the ZXA10 voip-rack 1
C300M voip-shelf 1 10 1 10 5 5 10.63.86.113
20000
Configure media NAT ZXAN(config-msag)#media-nat add

parameters for the ZXA10 voip-rack 1
C350M voip-shelf 1 6 1 6 5 5 10.63.86.113
24000
6.2.7 Configuring a VoIP VLAN
Abstract >>
This procedure describes how to configure a VoIP VLAN and bind the media and
signaling IP addresses to this VLAN.
Table 14 describes the VLAN configuration data.
Table 14 VLAN Configuration Data

Item Data
NE type ZXA10 C300M
VLAN ID 120
Steps >>
1. Enter the global configuration mode and create a VLAN.
ZXAN(config-vlan120)#
2. Use the voip-bind command to set the created VLAN as a VoIP VLAN.
ZXAN(config-vlan120)#voip-bind
3. (Optional) Query the VLAN configuration.
ZXAN(config-vlan120)#show vlan voip-bind
All created voip vlan:
120
6.2.8 Binding the Uplink Port to the VLAN
Abstract >>
This procedure describes how to configure the VoIP uplink port and bind the uplink port to
the VLAN to enable the transport of VoIP signaling streams and media streams through
the uplink port.
Context >>
The default status of the uplink port is "shutdown". The uplink port must be enabled
before being used.
Note:
It is not recommended to modify the uplink port information when the service is normal,
the uplink port information does not need to be modified. Incorrect configuration may
cause operation failure on the ZXA10 C300M/C350M.
Table 15 describes the configuration data for binding the uplink port to the VLAN.
Table 15 Configuration Data for Binding the Uplink Port to the VLAN
Item Data
NE type ZXA10 C300M
Uplink port gei_1/20/2
VoIP VLAN 120
Uplink port mode Adaptive
Steps >>
1. Enter the port configuration mode.
ZXAN(config)#interface gei_1/20/2
ZXAN(config-if)#
2. Use the switchport default vlan command to bind the uplink port to the
VoIP VLAN in untagged mode.
3. Set the uplink port to the adaptive mode.
ZXAN(config-if)#negotiation auto
4. Enable the uplink port.
ZXAN(config-if)#no shutdown
ZXAN(config-if)#end
ZXAN#
5. (Optional) In compact mode, you are also required to bind the media and
signaling IP addresses to the VLAN:
ZXAN(config-if)#ip address 10.63.86.113 255.255.255.0
6.2.9 Configuring SIP Parameters
Abstract >>
This procedure describes how to configure the required SIP parameters when the SIP is
used between the MGC and the MG.
Context >>
Table 16 describes the available termination ID types of SIP subscriber circuits.
Table 16 SIP Subscriber Circuit Termination ID Types

Type Description
Type 1 termination IDs have a fixed length, and the length cannot be
Type 1 configured. A type 1 termination ID consists of unit ID, subunit ID, and
circuit ID.
Type Description
Format: SIP00100100000–SIP00100100031.
Type 2 termination IDs have flexible lengths and are added for SIP
Type 2 subscriber circuits directly.
Format: SIP0–SIP31.
Type 3 termination IDs have a fixed length, and the length can be
Type 3 configured.
Format: SIP000–SIP031.
Table 17 describes SIP configuration data.
Table 17 SIP Configuration Data

Ite Data
m
N
E
ty ZXA10 C300M
p
e
SI
P
p
or
t
5060
n
u
m
b
er
SI
P
n
u
m
b • Serial number DAS: 1
er • Name: SIPDM
a • Value: EFX.F|EX.F|FX.F|EX.EX.|X.|59100X|67050XXX|EXFX.|EXF
n • MG ID: 1
al • Service type: two (SIP)
ys
is
ta
bl
e
SI • Circuit ID: 3/1–64

P • The first complete number: +8659167050110
s • Number analysis table name: SIPDM
Ite Data
m
u • Password: 123456
b • Prefix (user name authentication): 111670501
sc • Starting number: 0
ri • ID length without the prefix: 2
b • Type 3
er • SIP subscriber number: +8659167050110 – +8659167050173
SI
P
pr
o
xy IP address: 10.16.113.27
s
er
v
er
Steps >>
ZXAN(config)#msag
ZXAN(config-msag)#
2. Use the ctrlport add command to set the SIP port number to 5060.
ZXAN(config-msag)#ctrlport add 15 5060
3. Use the digitmap add command to configure the SIP number analysis
table.
ZXAN(config-msag)#digitmap add 1 SIPDM digit-map

EFX.F|EX.F|FX.F|
EX.EX.|X.|59100X|67050XXX|EXFX.|EXF. mgid 1 servicetype 2
Note:
The SIP number analysis table must be consist with that of the
connected device.
4 Use the sip user add command to configure a SIP subscriber.

.
ZXAN(config-msag)#sip user add 3 begin-index 1 num 64 3000
digitmapname SIPDM
password 123456 authUsername 30 begin-no 0 digitlen 2 type 3
For a description of the SIP subscriber parameters, refer to Table 18.
Table 18 SIP Subscriber Parameters

begin-index Starting circuit ID
num Number of circuits
digitmapname Name of the number analysis table
authUsername Authenticated user name
begin-no Starting number
digitlen Number of digits except the prefix
type Type of the SIP subscriber termination ID
5. Use the sip userid add command to configure the SIP subscriber ID.
ZXAN(config-msag)#sip userid add 3 begin-index 1 num 64 30 begin-no

0 digitlen 2
type 3
6. Use the sip proxy-server add command to configure the SIP proxy
server.
ZXAN(config-msag)#sip proxy-server add 1 5060 10.16.113.27
7. Use the sip user-agent add command to configure the SIP user agent.
ZXAN(config-msag)#sip user-agent add 1 1 domname

ims.fj.chinamobile.com port 5060
6.2.10 Configuring the AS, ASP, and Association
Abstract >>
This procedure describes how to configure the AS, ASP, and the association between the
AS and the ASP.
Context >>
An AS is a logical entity that serves for specific application events. An AS can be an MGC
that handles Q.931 messages and calling processes that are terminated on the D
channel of a Signaling Gateway (SG). The SG generally considers the AS as a sequence
consisting of one or multiple application server processes.
An ASP is a process instance of an application server. For example, the primary or

secondary MGC can be considered as an ASP.
An SCTP association can be created between the AS and ASP to support message
transmission of Q.921 user protocol data units and IUA peer messages.
Table 19 describes the configuration data for the AS, ASP, and the SCTP association.
Table 19 Configuration Data for AS, ASP, and SCTP Association

Item Data
AS ID 1
Protocol 5 (IUA protocol)
ASP ID 1
Destination port number 9930 (SCTP port number on the SS side)
Local port number 9931 (SCTP port number on the local side)
Lower-layer protocol 1 (UDP)
Destination IP address 10.63.193.200 (active IP address of the SS)
5 (number of ingress/egress streams)

instream/outstream
An SCTP association may contain multiple streams.
Steps >>
ZXAN(config)#msag
ZXAN(config-msag)#
2. Use the as add command to configure the AS.
ZXAN(config-msag)#as add 1 protocol 5
3. Use the asp add command to configure the ASP.
ZXAN(config-msag)#asp add 1 9930 9931 1 10.63.193.200 instream 8

outstream 8
4. Use the asasp add command to configure the SCTP association

between the AS and the ASP.
ZXAN(config-msag)#asasp add 1 1
6.2.11 Configuring the D Channel
Abstract >>
This procedure describes how to configure the D channel for ISDN service. A subscriber
interface ID can be mapped to a physical interface on the SG by the SS.
Table 20 describes the D channel configuration data.
Table 20 D Channel Configuration Data

Item Data
Shelf No./Slot No. of the ISDN card 1/3
Link number 3
16
Index
Range for 2B+D service: 1–16
BRA service Subscriber interface ID 3 (corresponding to IID on the SS)
AS ID 1
16
Link quantity
Range for 2B+D service: 1–16
pcm-no 1
Link number 1
17
Index
Range for E1: 1–31
PRA service Subscriber interface ID 3 (corresponding to IID on the SS)
AS ID 1
1
Link quantity Only one link can be configured for 30B+D
service.
Steps >>
ZXAN(config)#msag
ZXAN(config-msag)#
2. Use the isdn dlink span add command to configure the D channel
parameters.
To Do This
Configure the D channel for BRA service ZXAN(config-msag)#isdn dlink span

add 3 3 16 3 1 link-number 16
Configure the D channel for PRA service ZXAN(config-msag)#isdn dlink span

add 3 pcm-no 1 1 17 3 1 link-number 1
Note: During D channel configuration for BRA service, the subscriber

circuit ID must be configured, meaning the corresponding subscriber.
During D channel configuration for PRA service, the E1 slot occupied by
the D channel must be configured.
6.2.12 Configuring Termination IDs for ISDN Subscriber Circuits
Abstract >>
This procedure describes how to configure termination IDs for ISDN) subscriber circuits.
An ISDN subscriber circuit termination ID is used to uniquely identify an ISDN subscriber
circuit.
Table 21 describes the configuration data for termination ID configuration of ISDN

subscriber circuits.
Table 21 Configuration Data for ISDN Subscriber Circuit Termination IDs

Item Data
Rack No./Shelf No./Slot No. of the ISDN

1/1/3
card
Starting circuit number 1
BRA service Circuit quantity 8
Prefix BRA
Item Data
Termination ID type 3
3
ID length without the
This parameter is only valid for type 3
prefix
termination IDs.
Starting number 0
MG ID 1
pcm-no 6
Prefix PRA
PRA service Termination ID type 3
Quantity 30
MG ID 1
Steps >>
ZXAN(config)#msag
ZXAN(config-msag)#
2. Use the slc terminationid add command to configure ISDN subscriber

circuit termination IDs.
To Do This
Configure termination IDs for ISDN BRA ZXAN(config-msag)#slc terminationid

subscriber circuits add 3
begin-index 1 num 8 BRA type 3
digit-length
3 begin-no 0 1
Configure termination IDs for ISDN PRA ZXAN(config-msag)#trunk

subscriber circuits terminationid add 3
6 PRA type 3 num 30 mgid 1
6.3 VoIP Related Configurations
6.3.1 VoIP Resource Configurations
6.3.1.1 Configuring IPS
Abstract >>
This procedure describes how to display and configure the circuit information of the
Intelligent Protection Switching (IPS) module.
Context >>
Two types of termination IDs can be set for IPS circuits of a daughter card:
• Type 1 termination IDs have flexible length and are added for IPS circuits
directly.
• Type 2 termination IDs have a fix length and the length can be
configured.
Steps >>
ZXAN(config)#msag
ZXAN(config-msag)#
2. Configure the IPS parameters.
To Do This
Modify the IPS circuit duration ZXAN(config-msag)#rtp attribute modify 10 1

property begin-index 1 num 1 max-package-time 100
min-package-time 10
Set the IPS circuit termination ID of ZXAN(config-msag)#rtp terminationid add RTP

a daughter card 240
mgid 1 type 2 begin-no 0
Delete a termination ID ZXAN(config-msag)#rtp terminationid del fix

RTP 240 mgid 1 type 2 begin-no 0
Block IPS circuits ZXAN(config-msag)#rtp block rack 1 shelf 1 10

1
begin-index 1 num 10
Unblock IPS circuits ZXAN(config-msag)#rtp unblock rack 1 shelf 1

10 1
begin-index 1 num 10
Note: When the prefix of a termination ID is set, all the IPS resources
under the same child device number are set with this prefix. When the
prefix of a termination ID is deleted, the prefixes of all the IPS resources
under the same child device number are deleted.
ZXAN(config)#exit
ZXAN#write
6.3.1.2 Configuring VoIP Parameters
Abstract >>
This procedure describes how to configure VoIP parameters, including Dual-Tone

Multi-Frequency (DTMF), Echo Canceller (EC), Rxhandle, Fax-Modem, and Voice.
Context >>
For a description of the VoIP parameters, refer to Table 22.
Table 22 VoIP Parameter Descriptions

The DTMF signaling between telephones and switches is usually used
DTMF
for sending called numbers.
EC Echo cancellation used for removing echo from voice signals.
Rxhandle Quantity of jitter buffers that receive media packets.
Fax mode that determines which device can control the changeover
Fax-Modem between voice service and fax service. This parameter is usually set to
enable the SS to control the service changeover.
Voice Voice coding/decoding mode.
Steps >>
ZXAN(config)#msag
ZXAN(config-msag)#
2 Configure the VoIP parameters.
To Do This
Set the DTMF parameter ZXAN(config-msag)#rtp vpwl-parameter dtmf

dtmfpayload 98
dtmfredundant 97 dtmfrelaymode 1
Set the EC parameter ZXAN(config-msag)#rtp vpwl-parameter ec ecenable 1

ectaillen 32 ectxf 1 nlpaggress 0
Set the Rxhandle parameter ZXAN(config-msag)#rtp vpwl-parameter rxhandle

maxdelay 100 mindelay 10 nomdelay 40
Set the Fax-Modem parameter ZXAN(config-msag)#rtp vpwl-parameter fax-modem

faxmode 11
Set the Voice parameter ZXAN(config-msag)#rtp vpwl-parameter voice

g723-rate 0
6.3.2 Configuring VoIP QoS
Abstract >>
This procedure describes how to configure VoIP Quality of Service (QoS). When the
ZXA10 C300M/C350M detects that the QoS value of the user media stream exceeds the
threshold, it reports an alarm.
Steps >>
ZXAN(config)#msag
ZXAN(config-msag)#
2. Use the qovs profile modify command to modify the QoS delay, packet
loss rate, and jitter parameter.
ZXAN(config-msag)#qovs profile modify 1 delay 200 jitter 100 loss 5
3. Use the slc attribute modify command to bind the VoIP QoS profile to the
user port.
ZXAN(config-msag)#slc attribute modify 5 begin-index 1 num 32

qovs-profile 1
Note:
The VoIP QoS profile takes effect only when it is bound with the user
port.
6.3.3 Configuring Call Control Management
Abstract >>
This procedure describes how to configure call control management, including

configuring the fixed voice chip, tone fax, call limit switch, and uplink port call limit.
Prerequisite >>
The control and switch card, VoIP resource card, and the uplink card are installed and
operating properly.
Context >>
The voice chip is of the Digital Signal Processing (DSP) or Intelligent Protection
Switching (IPS) type.
Steps >>
ZXAN(config)#msag
ZXAN(config-msag)#
2. Configure call control management.
To Do This
Configure a voice chip ZXAN(config-msag)#tone chip 1 (DSP)

ZXAN(config-msag)#tone chip 2 (IPS)
Configure tone fax ZXAN(config-msag)#tone fax-event 1

t38-fax-end 1
Enable or disable call limit during ZXAN(config-msag)#call-limit on-off

busy time call-limit 1 ips-resource-limit 2
Modify the call limit parameters of the ZXAN(config-msag)#call-limit upport 1

uplink port modify
rack 1 shelf 1 21 1 receive-threshold
50000000 send-threshold 60000000
3 (Optional) Query the configuration results.

.
• To query the voice chip configuration
ZXAN(config-msag)#show msag tone chip
fix-tone-chip:DSP
• To query the tone fax configuration
ZXAN(config-msag)#show msag tone fax-event 1
mgid:1
fax-cng-tone:0
v21-flags-tone:1
t38-fax-end:1
ansamwi-tone:0
ansamwo-tone:0
answi-tone:0
answo-tone:0
(0-not report; 1-report)
• To query the busy-time call limit configuration
ZXAN(config-msag)#show msag call-limit on-off
call-limit:limit by mg
cpu-busy-limit:not limit
upport-busy-limit:not limit
ips-resource-limit:not limit
nic-limit:allway limit
• To query the uplink port call limit configuration
ZXAN(config-msag)#show msag call-limit upport
config-id:1
rack:1
shelf:1
slot:21
port:1
send-threshold:60000000
receiver-threshold:50000000
6.3.4 Configuring the Self-Switching Function
Abstract >>
This procedure describes how to configure the self-switching function. When this function
is enabled and the NE fails to connect the SS due to an IP network failure, the
subscribers can still communicate with each other through the NE
Steps >>
ZXAN(config)#msag
ZXAN(config-msag)#
2. Configure the self-switching function.
To Do This
Enable the self-switching function of ZXAN(config-msag)#mg capability 1

the MG self-exchange 1
Configure call protection ZXAN(config-msag)#mg capability 1

protect-call 1
Configure the self-switching digit ZXAN(config-msag)#digitmap add 1 ZTE

analysis selector digit-map 1983XXXX|1981XXXX servicetype
1
Configure the self-switching number ZXAN(config-msag)#slc phone-number

modify 3
begin-phone-number 19830000
6.3.5 Configuring an Uplink Port Protection Group
Abstract >>
This procedure describes how to configure an uplink port protection group.
Context >>
There are four types of system service data streams:
• VoIP media stream
• VoIP signaling stream
• Network Management (NM) stream
• Broadband data stream
The VoIP media stream, signaling stream, and NM stream are transmitted to layer 3, and
the broadband data stream is transmitted to layer 2.
The four types of service data streams can share one uplink port, or use four uplink ports
separately. In addition, four service data stream types can be combined in different ways
before uplink transmission.
One or multiple types of the service data streams can be put into a group for
active/standby protection, and this group is called the uplink port protection group. When
the active port is faulty, the data streams are switched to the standby port.
One uplink port protection group contains an active port group and a standby port group.
The active port group is enabled, and the standby port group is disabled. When
active/standby switchover is implemented, the active port group is disabled and the
standby port group is enabled. The ports in the same group are in the same state. For the
relations between the active and standby ports, refer to Figure 8.
Figure 8 Relations Between the Active Port and Standby Port
Up to four uplink port protection groups can be configured, that is, each type of service
data stream occupies one protection group.
The number of active ports in an uplink port protection group ranges from 1 to 4. The total
number of ports is from 1 × 2 to 4 × 2.
The NM stream and VoIP media stream are in different network segments. Therefore,
when the NM stream and VoIP media stream use different ports for uplink, the ports
cannot be configured in the same protection group.
Note:
An uplink port protection group is different from a VLAN and they are irrelevant to each
other. Therefore, the active and standby ports need to be added to a VLAN. Otherwise,
the data streams are interrupted even if active/standby protection is enabled.
The active protection group and the standby protection group cannot be enabled at the
same time. When a port in the active protection group is faulty, the standby protection
group is enabled.
Static aggregation can be enabled for the uplink ports that are added to a protection
group. The standby protection group is enabled only when all the ports in the aggregated
group are faulty.
Note:
The Link Aggregation Control Protocol (LACP) and uplink protection group conflict with
each other and they cannot be enabled at the same time.
Steps >>
1 In global configuraiton mode, configure an uplink port protection group.

To . Do This
Create an uplink port protection group ZXAN(config)#uaps-group 1
Delete an uplink port protection group ZXAN(config)#no uaps-group 1
Add a port to an uplink port protection group ZXAN(cfg-uaps-1)#port master-port

gei_1/21/1 slave-port gei_1/21/2
Delete a port from an uplink port protection ZXAN(cfg-uaps-1)#no port master-port

group gei_1/21/1
Enable switchover ZXAN(cfg-uaps-1)#revertive enable
Disable switchover ZXAN(cfg-uaps-1)#revertive disable
Select a link detection type ZXAN(cfg-uaps-1)#next-hop 10.63.173.200

link-type normal
Delete a link detection type ZXAN(cfg-uaps-group-id)#no next-hop
Set the link detection period ZXAN(cfg-uaps-1)#interval-link-detect 2
Set the number of link detection retry times ZXAN(cfg-uaps-1)#retry-link-detect 4
Force uplink port protection switchover ZXAN(cfg-uaps-1)#swap
The following information is related to the configuration of the uplink port protection
group.
• When an uplink port protection group is created, it is enabled.
• When an uplink port protection group is deleted, the configurations of

the ports in this group are deleted and restored to the default
settings.
• When ports are added to an uplink port protection group, the

protection function of the group takes effect. The ports should be
added in pairs. You can add the existing ports to a protection group
or delete some ports from the group.
• When the active uplink port is faulty, the services are switched over
to the standby port. When the active uplink port is recovered, the
services are switched back to it.
• The following information is related to the selection or deletion of the link

detection type:
→ When the next-hop IP address is configured, link detection is

enabled.
→ The default normal parameter indicates to detect the link

between the control and switch card and the next-hop IP
address, that is, to ping the next-hop IP address from the main
control card. The media parameter indicates to detect the
media stream link.
→ When the port state is linkup, the link is connected.
• The link detection period and the number of link detection retry times
are effective only when the next-hop IP address is configured.
2 (Optional) Query the configuration data of the uplink port protection group.
.
• When the uplink port protection group ID is not selected, the created
uplink port protection group is displayed.
ZXAN(cfg-uaps-1)#show uaps
Group List :
----------------------------
• When an uplink port protection group ID is selected, the detailed

information on the group is displayed, including the port that is being
used and the port states.
Revertive control : enable
PortLight control : enable
Protect-time : 300s
Next-hop : 10.63.173.200
Bfd next_hop : 0.0.0.0
Link-type : normal
Link-detect-retry : 5
Link-detect-interval : 3
Link status : connected or NA
Bfd Link status : connected or NA
Switch-type : common port
Master ports status :
Slave ports status :
6.3.6 Configuring the Ring Mode
Abstract >>
This procedure describes how to configure the ring mode. The MGC controls the MG to
send a ring tone to the called equipment. Different rings can be set depending on the
customs in different countries and regions or different types of end equipment.
Steps >>
ZXAN(config)#msag
ZXAN(config-msag)#
2. Modify the ring mode parameters.
ZXAN(config-msag)#ring modify mgid 1 immediaattr 1 immediaon 60

immediaoff 200
ringprofile 4
3. (Optional) query the configuration result.
ZXAN(config-msag)#show msag ring
mgid:1
immediaattr:1
immediaon:60
immediaoff:200
ringprofile:4 (RUSSIA)
---------------------------------
1 rows are effected
6.3.7 Configuring PBX DDI Function
Abstract >>
ZXA10 C300M is connected to the PBX by using the TRK card, and provides DDI calling
services.
Steps >>
1. Use the add-card command to add the TRK card.
ZXAN(config)#add-card slotno 5 trwgb
2. Use the slc terminationid add command to configure termination IDs for
narrowband subscriber circuits.
ZXAN(config)#msag
ZXAN(config-msag)#slc terminationid add 5 begin-index 1 num 32 USER
type 3 digit-length 3 begin-no 0 1
3. Configure the attributes of the subscriber users.
ZXAN(config-msag)#trk attribution modify 5 dial-mode 1 ddi-alarm 1
6.4 VoIP Service Configuration Instances

The following information is related to VoIP service configuration:
• The MG IP address should be consistent with that configured on the SS.
• If the Media Gateway Control Protocol (MGCP) is used, the domain name
needs to be configured, and the data can be obtained from the SS. If a
ZTE SS is used, the domain name should be in lower case.
• Only one MG can be created on each NE.
6.4.1 Configuring the VoIP POTS Service (H.248)
Abstract >>
This procedure describes how to configure the VoIP POTS service. In this instance, the
H.248 protocol is used between the NE and the SS. The VoIP daughter card has been
installed on the main control and switch card (instead of a VoIP card). The daughter card
is used for conversion between TDM signals and IP packets. After the configuration is
completed, subscribers are allowed to make VoIP calls.
Prerequisite >>
• The physical configuration is completed.
• The MG configuration data on the SS and the basic configuration data of

the MG are obtained.
Table 23 provides the planning data for H.248-based VoIP POTS service configuration.
Table 23 Configuration Data for VoIP POTS Service Configuration (H.248)

Item Data
NE type ZXA10 C300M
Uplink port 1/21/2
User port 1/3/1–64
Slot number of the VoIP daughter

10
card
VoIP VLAN 120
MGC ID: 1
Protocol port number: 2944
MGC (SS) Type: zte
IP address: 10.61.198.200
Mode for connecting the ZXA10 C300M: IP+Port
MG ID: 1
MG (ZXA10 C300M)) Corresponding MGC ID: 1
IP address: 10.63.198.227
Media stream and signaling Mask: 255.255.255.0
stream Next hop address: 10.63.198.254
VLAN ID: 120
Prefix: USER
Narrowband subscriber circuit
Termination ID type: 3
termination ID
Starting number: 0
Item Data
ID length without the prefix: 3 digits
Prefix: RTP
Starting number: 1 (default)
VoIP resource termination ID
VoIP resource quantity: 240
Steps >>
1. Enter the global configuration mode and use the add-card command to
add the POTS subscriber card.
ZXAN(config)#add-card rackno 1 shelfno 1 slotno 3 PTWVB
2. Use the add-subcard command to add the VoIP daughter card.
ZXAN(config)#del-subcard slotno 10 subcardno 1
ZXAN(config)#add-subcard slotno 10 subcardno 1 voip
Note:
The MAPP daughter card is added in the ZXA10 C300M by default.

Before adding the VoIP daughter card, you are required to remove the
MAPP daughter card.
3. Enter the MSAG configuration mode, and then use the mgc add
command to configure the IP address, port number, and protocol type of
the MGC that connects to the MG.
ZXAN(config)#msag
ZXAN(config-msag)#mgc add 1 10.63.198.200 port 2944 type 1
4. Use the mg add command to configure the H.248 protocol port number
on the MG side, which must be consistent with the protocol port number
on the SS side.
ZXAN(config-msag)#mg add 1 1 port 2944
5. Use the voip interface add command to configure the media IP address
and the signaling IP address.
255.255.255.0 media-ip 10.63.198.227 media-mask 255.255.255.0
VoIP resources.
ZXAN(config-msag)#rtp terminationid add RTP 240 mgid 1 type 2

begin-no 0
narrowband subscriber circuits.
ZXAN(config-msag)#slc terminationid add 3 begin-index 1 num 64 USER
type 3 digit-length 3 begin-no 0 1
8. Use the media-nat add command to configure media NAT.
ZXAN(config-msag)#media-nat add 10 1 10 5 5 10.63.198.227 20000
9. Configure the VoIP VLAN.
10. Enter the port configuration mode and bind the uplink port to the VLAN.
ZXAN(config-if)#negotiate auto
11. (Optional) If the ZXA10 C300M and the SS belong to different network
segments, use the ip route command to configure a static route for the
ZXA10 C300M.
ZXAN(config)#exit
ZXAN#write
13. (Optional) View the operating status of the H.248 protocol.
ZXAN#show msag h248-status
-------------------------------------
H248-SS link status(H248Trkplink) :OK
-------------------------------------
6.4.2 Configuring the VoIP POTS Service (SIP)
Abstract >>
This procedure describes how to configure the VoIP POTS service for the ZXA10 C300M.
In this instance, the SIP is used between the ZXA10 C300M and the SS. A VoIP daughter
card has been installed on the main control and switch card (instead of a VoIP card). The
daughter card is used for conversion between TDM signals and IP packets.
Prerequisite >>
• The physical configuration is completed.
• The MG configuration data on the SS and the basic configuration data of

the MG are obtained.
Table 24 provides the configuration data for SIP-based VoIP POTS service configuration.
Table 24 Configuration Data for VoIP POTS Service Configuration (SIP)

Item Data
NE type ZXA10 C300M
Uplink port 1/21/2
Item Data
Slot number of the VoIP daughter

10
card
VoIP VLAN 120
MGC ID: 1
IP address: 10.61.198.200
MGC (SS) Protocol port number: 5060
Type: zte
Mode for connecting the ZXA10 C300M: IP+Port
MG ID: 1
Corresponding MGC ID: 1
MG (ZXA10 C300M)
Domain name: ims.fj.mobile.com
IP address: 10.63.198.227
Media stream and signaling
Mask: 255.255.255.0
stream
Next hop address: 10.63.198.254
• Serial number DAS: 1

• Name: SIPDM
• Value:
SIP number analysis table EFX.F|EX.F|FX.F|EX.EX.|X.|59100X|67050XXX|E
XFX.|EXF.
• MG ID: 1
• Service type: 2 (SIP)
• Circuit ID: 3/1–64

• First complete number: +8659167050110
• Number analysis table: SIPDM
• Password: 123456
• Prefix (authentication user name): 111670501
SIP subscriber
• Starting number: 10
• SIP number length without the prefix: 2
• Type: 3
• SIP subscriber ID: +8659167050110 to
+8659167050173
Prefix: RTP
VoIP resource termination ID ID length without the prefix: 3 digits
Starting number: 0
RTP resource quantity: 240
Steps >>
1. In global configuration mode, use the add-card command to add the

POTS subscriber card.
ZXAN(config)#add-card rackno 1 shelfno 1 slotno 3 PTWVB
2. Use the add-subcard command to add the VoIP daughter card.
ZXAN(config)#del-subcard slotno 10 subcardno 1
ZXAN(config)#add-subcard slotno 10 subcardno 1 voip
Note:
The MAPP daughter card is added in the ZXA10 C300M by default.

Before adding the VoIP daughter card, you are required to remove the
MAPP daughter card.
3. Enter the MSAG configuration mode, and then use the mgc add
command to configure the IP address, port number, and protocol type of
the MGC that connects to the MG.
ZXAN(config)#msag
ZXAN(config-msag)#mgc add 1 10.61.198.200
4. Use the mg add command to configure the domain name of the SIP
server on the MG side.
ZXAN(config-msag)#mg add 1 1 domain-name ims.fj.mobile.com
5 Configure the SIP data.

.
a. Use the digitmap add command to configure the SIP number
analysis table.
ZXAN(config-msag)#digitmap add 1 SIPDM digit-map

EFX.F|EX.F|FX.F|
EX.EX.|X.|59100X|67050XXX|EXFX.|EXF mgid 1 servicetype 2
b. Use the sip group add command to configure the SIP subscriber
group.
ZXAN(config-msag)#sip group add 1 grouptype 0 groupname 1
c. Use the sip user add command to configure SIP subscribers.
ZXAN(config-msag)#sip user add 3 begin-index 1 num 64
+8659167050110
digitmapname SIPDM password 123456 authUsername 111670501

begin-no 10
digitlen 2 type 3
d. Use the sip userid add command to configure the SIP subscriber
IDs.
ZXAN(config-msag)#sip userid add 3 begin-index 1 num 6

+86591670501
begin-no 10 digitlen 2 type 3
e. Use the sip proxy-server add command to configure the SIP proxy
server.
ZXAN(config-msag)#sip proxy-server add 1 5060 10.61.198.200
f. Use the sip user-agent add command to configure the SIP user
agent.
ZXAN(config-msag)#sip user-agent add 1 1 port 5060 domname

10.61.198.200
6. Use the voip interface add command to configure the media IP address
and the signaling IP address.
255.255.255.0 media-ip 10.63.198.227 media-mask 255.255.255.0
VoIP resources.
ZXAN(config-msag)#rtp terminationid add RTP 240 type 3 digit-length 3
begin-no 0
8. Use the media-nat add command to configure media NAT.
9. Configure the VoIP VLAN.
10. Enter port configuration mode and then bind the uplink port to the
VLAN.
ZXAN(config-if)#negotiate auto
11. (Optional) If the ZXA10 C300M and the SS belong to different network
segments, use the ip route command to configure a static route for the
ZXA10 C300M.
ZXAN(config)#exit
ZXAN#write
6.4.3 Configuring the ISDN BRA Service
Abstract >>
This procedure describes how to configure the ISDN BRA service for the ZXA10 C300M.
Prerequisite >>
• The ISDN service port number is configured on the SS side.
• The configurations of the MGC, MG, VoIP resources, and the DBWD
subscriber card are completed on the AG side.
Configuraiton Data >>
Table 25 provides the configuration data for ISDN BRA service configuration.
Table 25 Planning Data for ISDN BRA Service Configuration

Item Data
NE type ZXA10 C300M
Slot number of the VoIP card 10
IP address:
Media stream and signaling stream
10.63.198.227
ISDN service
VoIP resource Type 3
Subscriber resource Type 3
AS 1
ASP 1
ISDN BRA link 1
Type zte
IP address 10.61.198.200
SS
H.248 protocol port number 2944
Mode for connecting the ZXA10 C300M IP+Port
Steps >>
1. Enter the global configuration mode and use the add-card command to
add the ISDN BRA subscriber card and the VoIP card.
ZXAN(config)#add-card rackno 1 shelfno 1 slotno 3 DBWD
2. Enter the MSAG configuration mode, and use the ctrlport add command
to configure the SCTP port number.
ZXAN(config)#msag
3. Use the as add, asp add, and asasp add commands to configure the AS,
ASP, and the SCTP association between the AS and the ASP.

outstream 8
4. Use the isdn dlink span add command to configure the D channel.
ZXAN(config-msag)#isdn dlink span add 3 1 1 100 1 link-number 16
2B+D subscriber circuits.
ZXAN(config-msag)#slc terminationid add 3 begin-index 1 num 8 BRA
digit-length 3 begin-no 0 type 3 1
ZXAN(config)#exit
ZXAN#write
6.4.4 Configuring the ISDN PRA Service
Abstract >>
This procedure describes how to configure the ISDN PRA service for the ZXA10 C300M.
The DSWU card without VoIP daughter card is used as an example.
Prerequisite >>
• The ISDN service port number is configured on the SS side.
• The configurations of the MGC, MG, VoIP resources, and the DEWU
subscriber card are completed on the AG side.
Table 26 provides the configuration data for ISDN PRA service configuration.
Table 26 Configuration Data for ISDN PRA Configuration

Item Data
NE type ZXA10 C300M (comom mode)
Slot number of the VoIP card 10
Media stream and signaling stream IP address: 10.63.198.227

ISDN
VoIP resource Type 3
service
Subscriber resource Type 3
AS 1
ASP 1
ISDN PRA link 1
Type zte
IP address 10.61.198.200
SS
H.248 protocol port number 2944
Mode for connecting the ZXA10 C300M IP+Port
Steps >>
1. Enter the global configuration mode and use the add-card comand to
add the ISDN PRA subscriber card and the VoIP card.
ZXAN(config)#add-card rackno 1 shelfno 1 slotno 3 DSWU
2. Enter the MSAG configuration mode and use the ctrlport add command
to configure the SCTP port number.
ZXAN(config)#msag
3. Use the as add, asp add, and asasp add commands to configure the AS,
ASP, and the SCTP association between the AS and the ASP.

outstream 8
For a description of the ASP parameters, refer to Table 27.
Table 27 ASP Parameter Descriptions

SCTP port number on the SS side, which must be
9930
consistent with the local port number of the SS.
Local SCTP port number, which must be consistent with

9931
the peer port number on the SS side.
2 Downlink protocol type.
10.61.198.200 IP address of the SS.
Number of ingress/egress streams in the association.

instream/outstream
An SCTP association may contain multiple streams.
4. Use the isdn dlink span add command to configure the D channel.
ZXAN(config-msag)#isdn dlink span add 3 pcm-no 1 1 17 3 1
For a description of the D channel parameters, refer to Table 28.
Table 28 D Channel Parameter Descriptions

3 Slot number of the ISDN PRA subscriber card
pcm-no E1 link number
1 Link number in the ZXA10 C300M
17 E1 link index
3 Trunk group number configured on the SS
1 AS ID
5. Use the trunk terminationid add command to configure termination IDs

for 30B+D subscriber circuits.
ZXAN(config-msag)#trunk terminationid add 3 1 PRA type 3 beginindex

2 num 30
ZXAN(config)#exit
Note:
A maximum of 30 termination IDs can be configured. Termination ID 0

and channel D are unavailable. Termination IDs 1–30 correspond to
circuit timeslots 1-15 and 17-31.
ZXAN#write
6.4.5 Using DSWU/DSWB Card with VoIP Daughter Card to Configure ISDN
PRA Service
Abstract >>
ZXA10 C300M can work as a TG device, and provides PRA service for the subscribers at
the PBX side.
This procedure introduces how to configure the media network address translation
function for the DSWU/DSWB VoIP daughter card.
Context >>
If the media NAT function is not configured for the VoIP daughter card, the PRA service
subscribers use the IPS resources of the control and switch card.
If the media NAT function is not configured for the VoIP daughter card, the PRA service
subscribers of the DSWU/DSWB card use the IPS resources of the IPS DSWU/DSWB
card.
Steps >>
1. In global configuration mode, use the add-card comand to add the ISDN
PRA subscriber card and the VoIP card.
ZXAN(config)#add-card rackno 1 shelfno 1 slotno 3 DSWU
2. Configure the PRA services. For more information, see Configuring the
ISDN PRA Service.
3. Use the media-nat add command to configure the media network

address translation function.
6.4.6 Configuring the IP-Based Fax Service
Abstract >>
This procedure describes how to configure the IP-based fax service.
Prerequisite >>
The PSTN or ISDN service is configured and provisioned.
Context >>
• The system supports T.30 and T.38 fax modes.
• When the system changes from voice mode to fax mode, some
parameters, such as VAD, are modified whatever the changeover is
automatic or is controlled by the MGC.
• The MGC selects the fax mode and controls the changeover of the fax
mode, T.38 or T.30. The MG only reports the detected fax tone to the
MGC, without automatic changeover.
• The port fax mode must be consistent with the fax mode in RTP
configuration.
Table 29 provides the planning data for IP-based fax service configuration.
Table 29 Configuration Data for IP-Based Fax Service Configuration

Item Data
NE type ZXA10 C300M
Slot number of the subscriber card 3
Fax mode T.38
Protocol H.248
Fax control type SS
Steps >>
1. Use the show msag h248-status command to check the voice service
configuration and make sure that the service is normal.
ZXAN(config)#show msag h248-status
-------------------------------------
H248-SS link status(H248Trkplink) :OK
-------------------------------------
ZXAN(config)#msag
ZXAN(config-msag)#
3. Configure the fax mode.

To Do This
Configure the fax mode if the global fax mode ZXAN(config-msag)#slc attribute
is required modify 3
begin-index 1 num 1 fax-modem 1
Configure the fax mode if the single-user fax ZXAN(config-msag)#slc attribute

mode is required modify 3
fax-modem 1
Note:
The system supports single-user fax mode configuration. If the global fax mode is not
configured, configure in single-user fax mode.
4. Use the rtp vpwl-parameter fax-modem command to configure the fax

property of the VoIP resource card.
ZXAN(config-msag)#rtp vpwl-parameter fax-modem faxmode 11
5. (Optional) Use the tone fax-event command to configure the fax tone
event.
ZXAN(config-msag)#tone fax-event 1 t38-fax-end 1 v21-flags-tone 1
ZXAN(config)#exit
ZXAN#write
6.5 xDSL Service Basic Configuration

Overview >>
xDSL services refer to the so-called broadband services, which provide high-speed
Internet accesses for users. They are secure and feature real-time Internet access
without dialup, separated phone conversation and Internet access, and diversified
multimedia services.
This section describes how to provide xDSL services, including network diagrams,
configuration workflow and operations.
xDSL services include:
• ADSL: Provides broadband Internet access services through a pair of

common telephone copper wires. It was originally designed for the VOD
service and has developed into a convenient broadband access
technology. The upstream rate is generally 1 Mpbs and the downlink rate
is 8 Mbps.
• VDSL: Provides faster data transmission than ADSL. In a short distance,

the downstream rate is up to 55 Mbps and the upstream rate reaches
19.2 Mbps or even higher. Currently, in the upstream and downstream
directions, the symmetrical transmission rate of 10 Mbps is available.
• SHDSL: Provides broadband services by using a pair of telephone wires,

supporting multiple transmission types such as voice, data, and video.
The SHDSL transmission distance is directly proportional to the
telephone wire diameter. Symmetrical transmission rates are provided,
ranging from 192 kbps to 15.4 Mbps.
Network Diagram >>
Figure 14 shows an xDSL service network diagram. The user PC is connected to a user
interface card through a modem. The upper-layer BAS access mode determines the
mode for the user to get on the Internet:
• If the BAS uses PPP access mode, the user uses the PPP dial-up
software to get on the Internet.
• If the BAS uses dedicated line access mode, the user can ping the IP
address of the uplink router interface and get on the Internet.
Figure 14 xDSL Service Network Diagram
Configuration Flow >>
Figure 15 shows the configuration workflow of xDSL services.
Figure 15 xDSL Service Configuration Flow
Table 56 describes how to configure an xDSL service.
Table 56 xDSL Service Configuration Flow

Create a service Creates a service VLAN, and adds user ports and uplink ports to the
VLAN. service VLAN. For details, refer to Creating a Service VLAN.
When line parameters or alarm parameters need to be modified, a

Configure a
line configuration profile and alarm configuration profile should be
configuration
configured and applied to the line. For details, refer to Configuring
profile.
Configuration Profiles.
If a user gets on the Internet through PPPoA or IPoA, the NE

Configure an
converts PPPoA or IPoA packets into PPPoE or IPoE packets. In
MAC address
this case, the MAC address pool assigns a source MAC address for
pool.
the user. For details, refer to Configuring an MAC Address Pool.
Configure the
For details, refer to Configuring a User Port PVC.
user pot PVC.
Activate the port. For details, refer to Activating an xDSL Port.
6.5.1 Creating a Service VLAN
Abstract >>
This procedure describes how to create a service VLAN and add a user port and an
uplink port to the service VLAN.
Steps >>
1. Run the configure terminal command to enter the global configuration

mode.
2. Run the vlan command to create a service VLAN.
3. Run the interface command to enter the port configuration mode.
4. Run the switchport command to add a user port to the service VLAN.
5. Run the interface command to enter the uplink interface configuration

mode.
6. Run the no shutdown command to activate the port.
7. Run the switchport command to add the uplink port to the service VLAN.
Example >>
Table 57 lists the configuration data for creating a service VLAN.
Table 57 Service VLAN Configuration Data

Item Data
NE type ZXA10 C300M
VLAN ID 1000
Port: adsl_1/4/1-16
ADSL users
pvc: 1
User port VDSL users Port: vdsl_1/5/1-16
Port: shdsl_1/6/1-16
SHDSL users
pvc: 1
User port mode access
Item Data
Uplink port mode trunk
%Info 20272: Enter configuration commands, one per line. End with CTRL/Z.
ZXAN(config)#interface adsl_1/4/1-16
ZXAN(config-if-range)#switchport mode access
ZXAN(config-if-range)#switchport default vlan 1000 pvc 1
ZXAN(config-if-range)#exit
ZXAN(config)#interface vdsl_1/5/1-16
ZXAN(config-if-range)#switchport default vlan 1000
ZXAN(config)#interface shdsl_1/6/1-16
ZXAN(config-if)#switchport mode trunk
ZXAN(config-if)#switchport vlan 1000 tag
6.5.2 Configuring Configuration Profiles
Abstract >>
This procedure describes how to configure the xDSL service configuration profiles and
apply the configuration profiles to the corresponding xDSL ports.
Context >>
You can use the system default configuration profiles. The default configuration profiles
cannot be modified. If the line parameters in the profiles other than the default profiles
need to be modified, you can modify the configuration profiles. Table 58 lists the system
default configuration profiles.
Table 58 System Default Configuration Profiles

xDSL Service Default File
DEF1M.PRF
DEF2M.PRF
Line configuration profile DEF8M.PRF
ADSL service DEFHM.PRF
DEFVAL.PRF
Alarm configuration profile DEFVAL.PRF
Downstream data rate profile VDDRPDEFVAL.PRF
Upstream data rate profile VUDRPDEFVAL.PRF
UPBO profile VUPDEFVAL.PRF
DPBO profile VDPDEFVAL.PRF
RFI profile VRPDEFVAL.PRF
Spectrum profile VSPDEFVAL.PRF
SNR margin profile VSMPDEFVAL.PRF

VDSL2 service
Delay INP profile VIDPDEFVAL.PRF
Virtual noise profile VVNPDEFVAL.PRF
Extension profile VEXTDEFVAL.PRF
Emergency rate adjustment (SOS)

VSOSDEFVAL.PRF
profile
INM profile VINMDEFVAL.PRF
Alarm configuration profile VDEFVAL.PRF
SDEFVAL.PRF
Line configuration profile
SHDSL service FOURWIRE.PRF
Alarm configuration profile SDEFVAL.PRF
Steps >>
•
Configure ADSL profiles.

mode.
22. Run the adsl profile command to create an ADSL line profile.
.
Table 59 lists the parameters to configure an ADSL/ADSL2+ line profile.
Table 59 Parameter Description for Configuring an ADSL/ADSL2+ Line

Profile
Upstream/Downstream channel rate
mode
→ 1: fixed
AturConfRateMode/AtucConfRateMode → 2: adaptAtStartup, adaption at

start-up
→ 3: adaptAtRuntime: adaption
during operation
Upstream/Downstream target noise

AtucConfTargetSnrMgn/AturConfTargetSnrMgn margin
Default: 8dB.
Upstream/Downstream maximum
noise margin
During ADSL/ADSL2+ connection
establishment, the system limits the
AtucConfMaxSnrMgn/AturConfMaxSnrMgn maximum noise margin to the preset
value if the actual noise margin is
greater than this value and the peer
end should reduce the output power
to optimize operations.
Upstream/Downstream minimum
noise margin
During ADSL/ADSL2+ connection
establishment, the port fails to be
AtucConfMinSnrMgn/AturConfMinSnrMgn
activated if the actual noise margin is
less than this value and the peer end
should increase the output power to
optimize operations.
Noise margin threshold for

upstream/downstream rate decrease
AtucConfDownshiftSnrMgn/AturConfDownshiftS For ADSL2/ADSL2+, if the noise
nrMgn margin is less than this value, the line
rate is decreased to increase the
noise margin.
Noise margin threshold for

AtucConfUpshiftSnrMgn/AturConfUpshiftSnrMgn
upstream/downstream rate increase
For ADSL2/ADSL2+, if the noise

margin is greater than this value, the
line rate is increased to maximize the
use of resources.
Minimum duration for

upstream/downstream rate increase
For ADSL2/ADSL2+, if the current
noise margin is greater than
AtucConfMinUpshiftTime/AturConfMinUpshiftTim
AtucConfUpshiftSnrMgn/AturConfUp
e
shiftSnrMgn, the
upstream/downstream rate starts to
be increased after this duration
expires.
Minimum duration for

upstream/downstream rate decrease
For ADSL2/ADSL2+, if the current
noise margin is less than
AtucConfMinDownshiftTime/AturConfMinDownsh
AtucConfDownshiftSnrMgn/AturConf
iftTime
DownshiftSnrMgn, the
upstream/downstream rate starts to
be decreased after this duration
expires.
Line type:
→ 1: fast-only
ConfProfileLineType
→ 2: interleaved-only
Downstream/Upstream maximum
activation rate when a channel is
configured to fast-only
If this value fails to be achieved due
to bad line condition and the channel
rate mode is adaptAtStartup, the line
automatically adapts an activation
AtucChanConfFastMaxTxRate/AturChanConfFa rate between
stMaxTxRate ChanConfFastMinTxRate and
ChanConfFastMinTxRate.
→ Downstream rate range:
0–131040 kbps (1024 kbps by
default)
→ Upstream rate range: 0–10240

kbps (512 kbps by default)
Downstream/Upstream minimum
configured to fast-only
If this value is configured too large,
AtucChanConfFastMinTxRate/AturChanConfFas
the link may not be activated.
tMinTxRate
→ Downstream rate range: 0–1024
→ Upstream rate range: 0–512 kbps
(32 kbps by default)
configured to interleaved-only
If this value fails to be achieved due
to bad line condition and the channel
rate mode is adaptAtStartup, the line
automatically adapts an activation
AtucChanConfInterleaveMaxTxRate/AturChanCo rate between
nfInterleaveMaxTxRate ChanConfInterleaveMinTxRate and
ChanConfInterleaveMaxTxRate.
→ Downstream rate range:
0–131040 kbps (1024 kbps by
default)
→ Upstream rate range: 0–10240

Downstream/Upstream minimum
configured to interleaved-only
If this value is configured too large,
AtucChanConfInterleaveMinTxRate/AturChanCo the link may not be activated.
nfInterleaveMinTxRate → Downstream rate range: 0–1024
→ Upstream rate range: 0–512 kbps

(32 kbps by default)
interleave delay
This parameter is applicable for
interleave channels. If it is set to a
large value, the immunity against
AtucChanConfMaxInterleaveDelay/AturChanCon
pulse interference and the stability of
fMaxInterleaveDelay
an ADSL/ADSL2+ connection may
be increased, but the delay in
transmission may be long.
Upstream/Downstream rate range:
0–255 ms (16 kbps by default)
This parameter enables or disables

the selection of custom-defined
AtucDMTConfFreqBinsOperType/AturDMTConfF downstream/upstream sub-channels.
reqBinsOperType → 1: Open
→ 2: Cancel
EOC operation mode:

→ 1: byte
LineDMTConfEOC
→ 2: streaming
Grill code, on by default.

LineDMTConfTrellis
→ 1: on
→ 2: off

sub-channels for users.
This function works at the end of
AtucConfUseCustomBins training.
→ 1: on
→ 2: off

downstream/upstream bit swap.
AtucConfDnBitSwap/AtucConfUpBitSwap → 1: on
→ 2: off

READSL.
AtucConfREADSL2Enable → 1: on
→ 2: off
Power Spectrum Density (PSD)

profile:
→ 1: DMT_PSD_MSK
→ 2: ADSL2_PSD_MSK
→ 3:
AtucConfPsdMaskType ADSL2_READSL_WIDE_PSD_M
SK
→ 4:
ADSL2_READSL_NARROW_PSD
_MSK
Default:
ADSL2_READSL_WIDE_PSD_MSK
Automatic power management mode:

→ 1: DISABLE
→ 2: L3_ENABLE
AtucConfPMMode
→ 3: L2_ENABLE
→ 4: L3_ENABLE | L2_ENABLE
Default: DISABLE
Minimum duration of L0 power state.

A longer duration indicates a more
AtucConfPML0Time stable state of a link.
Value range: 0–255 s (240 s by
default)
Minimum duration from the start of L2

AtucConfPML2Time
power state to the start of power
decrease.
Value range: 0–255 s (120 s by
default)
Maximum power decrease during

every power attenuation in L2 power
AtucConfPML2ATPR state.
Value range: 0–31 dB (3 dB by
default)
1: adlu32Eu32 - ADLU-32 / EU-32

2: adlu36Eu36 - ADLU-36 / EU-36
3: adlu40Eu40 - ADLU-40 / EU-40
4: adlu44Eu44 - ADLU-44 / EU-44
zxAnXdsl2LConfPsdMaskSelectUs 5: adlu48Eu48 - ADLU-48 / EU-48
6: adlu52Eu52 - ADLU-52 / EU-52
7: adlu56Eu56 - ADLU-56 / EU-56
8: adlu60Eu60 - ADLU-60 / EU-60
9: adlu64Eu64 - ADLU-64 / EU-61
Target activation rate of the line in L2

power state
AtucConfPML2Rate
Value range: 512–1024 (512 kbps by
default)
0: INP_AUTO
1: INP_0
2: INP_POINT5
3: INP_1
AtucConfMinInp/AturConfMinInp
4: INP_2
5: INP_4
6: INP_8
7: INP_16
3. Run the adsl alarm-profile command to create an ADSL alarm profile.
Table 60 lists the parameters to configure an ADSL/ADSL2+ alarm

profile.
Table 60 Parameter Description for Configuring an ADSL/ADSL2+

Alarm Profile
Alarm profile name Alarm profile name, 32 bytes.
Alarm threshold of the number

of upstream frame loss
seconds in 15 minutes
During a performance data
AtucThresh15MinLofs collection period of 15
minutes, an alarm occurs if
the number of upstream frame
loss seconds is greater than
this threshold.

of upstream erroneous
AtucThresh15MinESs collection period of 15
the number of upstream
erroneous seconds is greater
than this threshold.

of upstream signal loss
seconds in 15 minutes.
AtucThresh15MinLoss collection period of 15
the number of upstream signal
this threshold.

of local power loss seconds in
15 minutes
AtucThresh15MinLprs collection period of 15
the number of local power
this threshold.

of upstream link loss seconds
in 15 minutes.
AtucThresh15MinLols collection period of 15
the number of upstream link
this threshold.
Alarm threshold of
downstream fast channel rate
increment
If the link establishment rate
AtucThreshFastRateUp
increment of a downstream
fast channel is greater than
this threshold, an alarm
occurs.
Alarm threshold of
downstream interleave
channel rate increment
AtucThreshInterleaveRateUp If the link establishment rate
increment of a downstream
interleave channel is greater
than this threshold, an alarm
occurs.
Alarm threshold of
downstream fast channel rate
decrement
AtucThreshFastRateDown
decrement of a downstream
fast channel is greater than
occurs.
Alarm threshold of
downstream interleave
channel rate decrement
AtucThreshInterleaveRateDown
decrement of a downstream
occurs.

of downstream frame loss
AturThresh15MinLofs collection period of 15
the number of downstream
frame loss seconds is greater

of downstream erroneous
AturThresh15MinESs collection period of 15
erroneous seconds is greater

of downstream signal loss
AturThresh15MinLoss collection period of 15
signal loss seconds is greater

of remote power loss seconds
in 15 minutes
AturThresh15MinLprs
collection period of 15
the number of remote power

this threshold.
Alarm threshold of upstream

fast channel rate increment
AturThreshFastRateUp
increment of a upstream fast
channel is greater than this
threshold, an alarm occurs.

interleave channel rate
increment
AturThreshInterleaveRateUp
increment of a upstream
occurs.

fast channel rate decrement
AturThreshFastRateDown
decrement of a upstream fast
channel is greater than this
threshold, an alarm occurs.

interleave channel rate
decrement
AturThreshInterleaveRateDown
decrement of a upstream
occurs.
This parameter enables or

disables the TRAP reporting
function in case of local
initialization failure.
→ 1: enabled: An alarm
AtucInitFailureTrapEnable
occurs if local initialization
fails.
→ 2: disabled: No alarm
occurs.

of local quick retraining failure
AtucThreshold15MinFailedFastR collection period of 15
the number of local quick
retraining failure seconds is
greater than this threshold.

of upstream severely
erroneous seconds in 15
minutes
AtucThreshold15MinSesL
severely erroneous seconds
is greater than this threshold.

of upstream unavailable
AtucThreshold15MinUasL collection period of 15
unavailable seconds is

of downstream severely
erroneous seconds in 15
minutes
AturThreshold15MinSesL
severely erroneous seconds
is greater than this threshold.

of downstream unavailable
AturThreshold15MinUasL collection period of 15
unavailable seconds is
Alarm threshold of the local

rate deviation
If the percentage of the local
AtucConnRateTolerance
rate deviation is greater than
occurs.
Alarm threshold of the local

actual rate
ThreshAtucConnRate If the local actual rate is less
occurs.
AturConnRateTolerance Alarm threshold of the remote
rate deviation
If the percentage of the
remote rate deviation is
greater than this threshold, an
alarm occurs.
Alarm
MinThreshAturConnRate/MaxThreshAturConnRate Minthreshold/Maxthreshold of
the local actual rate
Alarm threshold of the remote

actual rate
ThreshAturConnRate If the remote actual rate is
less than this threshold, an
alarm occurs.
Alarm threshold of the

ThreshAtucInpLeftr/ThreshAturInpLeftr
error-free throughput
4. Run the interface command to enter the interface configuration mode.
5. Run the adsl profile command to apply the ADSL base profile to an
ADSL port.
6. Run the adsl alarm-profile command to apply the ADSL alarm profile to
an ADSL port.
•
Configure VDSL2 profiles

mode.
2. Run the vdsl2 dsdatarate-prf command to create a VDSL2

downstream rate profile.
Table 61 lists the parameters to configure a VDSL2 downstream rate

profile.
Table 61 Parameter Description for Configuring an VDSL2

Downstream Rate Profile
Downstream channel rate adaptation ratio
zxAnXdsl2ChConfChannRaRatioDs Value range: 0 - 100
Recommended value: 100
Minimum downstream rate

zxAnXdsl2ChConfMinDataRateDs Value range: 0 - 200000 kbps
Maximum downstream rate

zxAnXdsl2ChConfMaxDataRateDs
Value range: 32 kbps - 200000 kbps
Minimum downstream reserved rate

zxAnXdsl2ChConfMinResRateDs Value range: 0 - 200000 kbps
Minimum downstream rate in low power

consumption mode
zxAnXdsl2ChConfMinRateLowPwrDs
Value range: 0 - 200000 kbps
Downstream rate decreased threshold

zxAnXdsl2ChConfDsDataRateDs Value range: 0 - 200000 kbps
Downstream rate increased threshold

zxAnXdsl2ChConfUsDataRateDs Value range: 0 - 200000 kbps
Minimum downstream SOS rate

zxAnXdsl2ChConfMinSosBitRateDs Value range: 0 - 200000 kbps
3. Run the vdsl2 usdatarate-prf command to create a VDSL2 upstream

rate profile.
Table 62 lists the parameters to configure a VDSL2 upstream rate

profile.
Table 62 Parameter Description for Configuring an VDSL2 Upstream

Rate Profile
Upstream channel rate adaptation ratio
zxAnXdsl2ChConfChannRaRatioUs Value range: 0 - 100
Minimum upstream rate

zxAnXdsl2ChConfMinDataRateUs Value range: 0 - 200000 kbps
Maximum upstream rate

zxAnXdsl2ChConfMaxDataRateUs Value range: 32 kbps - 200000 kbps
Minimum upstream reserved rate

zxAnXdsl2ChConfMinResRateUs Value range: 0 - 200000 kbps
Minimum upstream rate in low power

consumption mode
zxAnXdsl2ChConfMinRateLowPwrUs
Value range: 0 - 200000 kbps
Upstream rate decreased threshold

zxAnXdsl2ChConfMaxBerUs Value range: 0 - 200000 kbps
Upstream rate increased threshold

zxAnXdsl2ChConfUsDataRateUs Value range: 0 - 200000 kbps
Minimum upstream SOS rate

zxAnXdsl2ChConfMinSosBitRateUs Value range: 0 - 200000 kbps
4 Run the vdsl dpbo-prf command to create a VDSL2 DPBO profile.

.
Table 63 lists the parameters to configure a VDSL2 DPBO profile.
Table 63 Parameter Description for Configuring a VDSL2 DPBO

Profile
Defaul
t
DPBO profile name DPBO profile name, 32 bytes. -
Work mode of downstream power rollback

1: adsl mode
2: adsl2 mode
zxAnXdsl2LConfDpboEPsd 3: adsl2+ mode 3
4: vdsl2 998_M2x_A mode
5: vdsl2 998E17-M2x-NUS0 mode
6: custom
Electrical length at the switch side

If this parameter is configured to 0, the
DPBO function is disabled and other
zxAnXdsl2LconfDpboEsEL 0
DPBO parameters cannot be configured.
Value range: 0–511
Actual range: 0–255.5 dB
Cable model parameter A at the switch

side (characteristic parameter vector A of
central office cables)
This parameter indicates the actual
attenuation characteristics of cables, for
example, characteristics of the cables with
different diameters, 0.4 mm or 0.5 mm.
zxAnXdsl2LConfDpboEscm The frequency loss of the cable at end E is
263
A calculated from the electrical length at the
switch side. Then, it is estimated from
zxAnXdsl2LConfProfDpboEsCableModelA
,
zxAnXdsl2LConfProfDpboEsCableModelB
, and
zxAnXdsl2LConfProfDpboEsCableModelC
.
Value range: 0 – 640

Actual range: –1 to 1.5
Value increment: 2e-8
Cable model parameter B at the switch

side (characteristic parameter vector B of
zxAnXdsl2LConfDpboEscm central office cables)
509
B Value range: 0–640
Cable model parameter C at the switch

side (characteristic parameter vector C of
zxAnXdsl2LConfDpboEscm central office cables)
261
C Value range: 0–640
Minimum available signal PSD

zxAnXdsl2LConfDpboMus 190
Actual range: 0 to –127.5 dBm
Value increment: 0.5 dBm
Minimum frequency for downstream power

rollback
zxAnXdsl2LConfDpboFMin Value range: 0–2048 32
Actual range: 0–8832 kHz
Value increment: 4.3125 kHz
Maximum frequency for downstream

power rollback
zxAnXdsl2LConfDpboFMax Value range: 32–6956 511
Actual range: 138 kHz – 29997.75 kHz
Value increment: 4.3125 kHz
5. Run the vdls2 upbo-prf command to create a VDSL2 UPBO profile.
Table 64 lists the parameters to configure a VDSL2 UPBO profile.
Table 64 Parameter Description for Configuring a VDSL2 UPBO

Profile
Parameter Description Default
UPBO profile name UPBO profile name, 32 bytes. -
Upstream electrical length (a

distance attenuation forcibly
configured by users through the CO
MIB). This parameter is effective
zxAnXdsl2LConfUpboKL only when 0
zxAnXdsl2LConfProfUpboKLF is
set to override(2).
Actual range: 0–128 dBm
Value increment: 0.1 dBm
This parameter indicates whether to

force the remote end to calculate
upstream power rollback from the
electrical length configured at the
zxAnXdsl2LConfUpboKLF 3
central office.
1: auto
2: override
3: disableUpbo
Parameter A for upstream

frequency band US1 to calculate
upstream power rollback
zxAnXdsl2LconfUpboU1bandPsdA 5650
Actual range: 40–80.95 dBm/Hz
Value increment: 0.01 dBm/Hz
Parameter B for upstream

zxAnXdsl2LconfUpboU1bandPsdB 1020







This parameter defines the UPBO

reference electrical length used to
compute the upstream power
back-off for U1 upstream band
zxAnXdsl2LConfUpboU1bandKLRef 0
except US0, for the optional
Equalized FEXT UPBO method.
Value range: 1.8 dB – 63.5 dB
Value increment: 0.1 dB



6. Run the vdsl2 spectrum-prf command to create a VDSL2 spectrum

profile.
Table 65 lists the parameters to configure a VDSL2 spectrum profile.
Table 65 Parameter Description for Configuring an VDSL2 Spectrum

Profile
VDSL2 carrier channel

power mask VDSL2
0: no change
zxAnXdsl2LConfVdsl2CarMask
1: modify the bands
2: delete all bands
Upstream/downstream
minimum overhead
based on messages
zxAnXdsl2LConfMsgMinDs/zxAnXdsl2LConfMsgMinUs
Value range: 4 - 248
kbps
Enable intersymbol
interference
zxAnXdsl2LConfCeFlag 1: Enable
2: Disable
Line power management

mode
Allow transitions to idle
→ 0: disable
→ 1: enable
zxAnXdsl2LConfPmMode
Allow transitions to low
power
→ 0: disable
→ 1: enable
Minimum interval of
exiting L2 status and
entering L2 status
zxAnXdsl2LConfL0Time
Value range: 0 - 255 ms
Recommended value:
255
Minimum interval of the

first power attenuation
when entering L2 status
and each power
zxAnXdsl2LConfL2Time
attenuation in L2 status
Value range: 0- 255 ms
Recommended value:
255
Maximum each power

attenuation in L2 status
zxAnXdsl2LConfL2Atpr
Value range: 0 - 31 dB
Maximum total power

zxAnXdsl2LConfL2Atprt attenuation in L2 status
Value range: 0 - 31 dB
Recommended value:
31
Standard VDSL2 profile

profiel_8A, profiel_8B,
profiel_8C, profiel_8D,
profiel_12A, profiel_12B,
StandardProfile
profiel_17A, profiel_30A
→ 0: disable
→ 1: enable
7. Run the vdsl2 rfi-prf command to create a VDSL2 RFI profile.
8 Run the vdsl2 snrmargin-prf command to create a VDSL2 snr margin

. profile.
Table 66 lists the parameters to configure a VDSL2 SNR margin profile.
Table 66 Parameter Description for Configuring an VDSL2 SNR

Margin Profile
Upstream/downstrea
m target SNR margin
zxAnXdsl2LConfTargetSnrmDs/zxAnXdsl2LConfTargetSnr Value range: 0 - 310
mUs dB
Recommended
value: 80
Upstream/downstrea
m maximum SNR
margin
zxAnXdsl2LConfMaxSnrmDs/zxAnXdsl2LConfMaxSnrmUs Value range: 81 -
310 dB
Recommended
value: 300
Upstream/downstrea
m minimum SNR
margin
zxAnXdsl2LConfMinSnrmDs/zxAnXdsl2LConfMinSnrmUs
Value range: 0 - 79
dB
Recommended 0
Upstream/downstrea
m Up-Shift SNR
margin
zxAnXdsl2LConfRaUsNrmDs/zxAnXdsl2LConfRaUsNrmUs Value range: 0 - 310
dB
Recommended
value: 90
Upstream/downstrea
m Up-Shift time
zxAnXdsl2LConfRaUsTimeDs/zxAnXdsl2LConfRaUsTime Value range: 0 -
Us 16383 s
Recommended
value: 60
Upstream/downstrea
m Down-Shift SNR
margin
zxAnXdsl2LConfRaDsNrmDs/zxAnXdsl2LConfRaDsNrmUs Value range: 0 - 310
dB
Recommended
value: 30
Upstream/downstrea
m Down-Shift time
zxAnXdsl2LConfRaDsTimeDs/zxAnXdsl2LConfRaDsTime Value range: 0 -
Us 16383 s
Recommended
value: 60
Upstream/downstrea
m virtual noise
enable
zxAnXdsl2LConfSnrModeDs/zxAnXdsl2LConfSnrModeUs 1: UNDisabled
2: UNEnabled
Recommended
value: 1
Upstream/downstrea
m rate adaptation
mode
1: fixed
zxAnXdsl2LConfRaModeDs/zxAnXdsl2LConfRaModeUs
2: raInit
3: dynamicRa
Recommended
value: 2
99. Run the vdsl2 delayinp-prf command to create a VDSL line delay profile.
.
Table 67 lists the parameters to configure a VDSL2 line delay profile.
Table 67 Parameter Description for Configuring an VDSL2 Line Delay

Profile
Upstream/downstre
am channel
maximum delay
zxAnXdsl2ChConfMaxDelayDs/zxAnXdsl2ChConfMaxDelay
Value range: 0 - 63
Us
ms
Recommended
value: 16
Upstream/downstre
am channel
minimum noise
zxAnXdsl2ChConfMinProtectDs/zxAnXdsl2ChConfMinProte protection
ctUs Value range: 1 - 18
Symbol
Recommended
value: 1
Upstream/downstre
am channel
minimum noise
protection in 30a
zxAnXdsl2ChConfMinProtect8Ds/zxAnXdsl2ChConfMinProt
mode
ect8Us
Value range: 1 - 17
Symbol
Recommended
value: 1
Upstream/downstre
am channel
minimum noise
protection enable
zxAnXdsl2ChConfForceInpDs/zxAnXdsl2ChConfForceInpUs
1: Enable
2: Disable
Recommended
value: 1
Maximun channel
delay variant
Value range: 1 - 255
zxAnXdsl2ChConfMaxDelayVar
ms
Recommended
value: 255
Channel
Initialization policy
1: policy0
zxAnXdsl2ChConfInitPolicy
2: policy1
Recommended
value: 16
10. Run the vdsl2 virtualnoise-prf command to create a VDSL2 virtual

noise profile.
11. Run the vdsl2 ext-prf command to create a VDSL2 extension profile.
12. Run the vdsl2 sos-prf command to create a VDSL2 emergency rate
adjustment (SOS) profile.
13. Run the vdsl2 inm-prf command to create a VDSL2 INM profile.
14. Run the vdsl2 alarm-prf command to create a VDSL2 alarm profile
Table 68 lists the parameters to configure a VDSL2 alarm profile.
Table 68 Parameter Description of VDSL2 Alarm Profile

Within 15 minutes, if central office
FECS exceeds the threshold, the
zxAnXdsl2XtucThreshFecs system generates an alarm
Value range: 0 – 900 s
Default: 0
Within 15 minutes, if downstream ES

exceeds the threshold, the system
zxAnXdsl2XtucThreshEs generates an alarm
Default: 0
Within 15 minutes, if downstream SES

zxAnXdsl2XtucThreshSes generates an alarm
Default: 0
Within 15 minutes, if the downstream

signal loss exceeds the threshold, the
zxAnXdsl2XtucThreshLoss system generates an alarm
Default: 0

frame loss second exceeds the
threshold, the system generates an
zxAnXdsl2XtucThreshLofs
alarm
Default: 0

link loss second exceeds the threshold,
zxAnXdsl2XtucThreshLols the system generates an alarm
Default: 0
Within 15 minutes, if central office

power loss second exceeds the
zxAnXdsl2XtucThreshLprs
alarm
Default: 0
Within 15 minutes, if downstream UAS

zxAnXdsl2XtucThreshUas generates an alarm
Default: 0
zxAnXdsl2XtucThreshPtmCrcErrs Within 15 minutes, if downstream CRC
error packets exceed the threshold, the

system generates an alarm
Value range: 0 – 2147483647
Default: 0
Within 15 minutes, if downstream PTM

code violation exceeds the threshold,
zxAnXdsl2XtucThreshPtmCodViol the system generates an alarm
Value range: 0 – 2147483647
Default: 0
Within 15 minutes, if remote FECS

zxAnXdsl2XturThreshFecs generates an alarm
Default: 0
Within 15 minutes, if upstream signal

ES exceeds the threshold, the system
zxAnXdsl2XturThreshEs generates an alarm
Default: 0
Within 15 minutes, if upstream SES

zxAnXdsl2XturThreshSes generates an alarm
Default: 0
Within 15 minutes, if the upstream

signal loss second exceeds the
zxAnXdsl2XturThreshLoss
alarm
Default: 0
Within 15 minutes, if the upstream

frame loss second exceeds the
zxAnXdsl2XturThreshLofs
alarm
Default: 0
Within 15 minutes, if remote power loss

second exceeds the threshold, the
zxAnXdsl2XturThreshLprs system generates an alarm
Default: 0
Within 15 minutes, if upstream UAS

zxAnXdsl2XturThreshUas generates an alarm
Default: 0
Within 15 minutes, if upstream CRC

zxAnXdsl2XturThreshPtmCrcErrs
error packets exceed the threshold, the

Value range: 0 – 2147483647
Default: 0
Within 15 minutes, if upstream PTM

zxAnXdsl2XturThreshPtmCodViol the system generates an alarm
Value range: 0 – 2147483647
Default: 0
Within 15 minutes, if full initialization

failure exceeds the threshold, the
zxAnXdsl2ThreshFailedFullInt system generates an alarm
Value range: 0 – 2147483647
Default: 0
Within 15 minutes, if fast initialization

failure exceeds the threshold, the
zxAnXdsl2ThreshFailedShrtInt system generates an alarm
Value range: 0 – 2147483647
Default: 0

zxAnXdsl2Ch1XtucThrshCodeViol the system generates an alarm
Value range: 0 – 2147483647
Default: 0
Within 15 minutes, if downstream

corrected data blocks exceed the
zxAnXdsl2Ch1XtucThrshCorrected
alarm
Value range: 0 – 2147483647
Default: 0
Within 15 minutes, if upstream code

violation exceeds the threshold, the
zxAnXdsl2Ch1XturThrshCodeViol system generates an alarm
Value range: 0 – 2147483647
Default: 0
Within 15 minutes, if upstream

corrected data blocks exceed the
zxAnXdsl2Ch1XturThrshCorrected
alarm
Value range: 0 – 2147483647
Default: 0
Within 15 minutes, if the percentage of

the difference between the local-end
rate and the actual rate among the
configured rate exceeds the set
zxAnXdsl2XtucLowDataRateTolerance
alarm
Default: 0
Within 15 minutes, if the percentage of

the difference between the remote-end
rate and the actual rate among the
configured rate exceeds the set
zxAnXdsl2XturLowDataRateTolerance
alarm
Default: 0
Within 15 minutes, if the local-end rate

is lower than the set threshold, the
zxAnXdsl2XtucLowDataRateThresh system generates an alarm
Default: 0
Within 15 minutes, if the remote-end

rate is lower than the set threshold, the
zxAnXdsl2XturLowDataRateThresh system generates an alarm
Default: 0
When this parameter is enabled, when

local-end initialization fails, the system
zxAnXdsl2XtucInitFailTrapEnable
generates an alarm
Default: disable
When this parameter is enabled, when

remote-end initialization fails, the
zxAnXdsl2XturInitFailTrapEnable
Default: disable
When the downstream low-speed

no-error data throughput exceeds the
set threshold, the system generates an
zxAnXdsl2XtucThreshInpLeftr
alarm
Default: 0
When the upstream low-speed no-error

data throughput exceeds the set
zxAnXdsl2XturThreshInpLeftr
alarm
Default: 0
When the packet loss ratio of

downstream vector error sampling
packets exceeds the set threshold, the
zxAnXdsl2XtucEsLossRatioThresh
Default: 0
When the packet loss ratio of upstream

vector error sampling packets exceeds
zxAnXdsl2XturEsLossRatioThresh the set threshold, the system generates
an alarm
Default: 0
When the number of error seconds for

downstream low-speed no-error data
exceeds the set threshold, the system
zxAnXdsl2XtucThreshInpLeftrs
generates an alarm
Default: 0
When the number of error seconds for

upstream low-speed no-error data
exceeds the set threshold, the system
zxAnXdsl2XturThreshInpLeftrs
generates an alarm
Default: 0
15. Run the interface command to enter interface configuration mode.
16. Run the vdsl2 ch1dsdatarate-prf command to apply the downstream

data rate profile to a VDSl2 port.
17. Run the vdsl2 ch1usdatarate-prf command to apply the upstream

data rate profile to a VDSl2 port.
18. Run the vdsl2 upbo-prf command to apply the UPBO profile to a
VDSl2 port.
19. Run the vdsl2 dpbo-prf command to apply the DPBO profile to a
VDSl2 port.
20. Run the vdsl2 spectrum-prf command to apply the spectrum profile to
a VDSl2 port.
21. Run the vdsl2 rfi-prf command to apply the RFI profile to a VDSl2
port.
22. Run the vdsl2 snrmargin-prf command to apply the SNR margin
profile to a VDSl2 port.
23. Run the vdsl2 ch1delayinp-prf command to apply the delay INP
24. Run the vdsl2 virtualnoise-prf command to apply the virtual noise
25. Run the vdsl2 ext-prf command to apply the extension profile to a
VDSl2 port.
26. Run the vdsl2 sos-prf command to apply the emergency rate
adjustment (SOS) profile to a VDSl2 port.
27. Run the vdsl2 inm-prf command to apply the INM profile to a VDSl2
port.
28. Run the vdsl2 alarm-prf command to apply the VDSL2 alarm profile
to a VDSl2 port.
•
Configure SHDSL profiles
1. Run the configure terminal command to enter global configuration

mode.
2
2. Run the shdsl profile command to create an SHDSL line profile.
.
Table 69 lists the parameters to configure an SHDSL line profile.
Table 69 Parameter Description for Configuring an SHDSL Line Profile

Line configuration file
SHDSL profile name
name, 32 bytes
SHDSL line interface

mode:
Value range:
→ 1: twoWire
→ 2: fourWire
→ 3: sixWire
→ 4: eightWire
SpanConfWireInterface
→ 5:
gsfourWireBitInterleave
→6:
fourWireByteInterleaveE
nhanced
→7:
fourWireBitInterleaveEn
hanced
Default: 1 (twoWire)
Minimum SHDSL line rate

Value range: 192kbps –
SpanConfMinLineRate
30000 kbps
Default: 200 kbps
SpanConfMaxLineRate Maximum SHDSL line rate
During SHDSL connection

establishment, the system
limits the rate to this
configured maximum rate
if the calculated rate is
greater than this
configured value. In this
case, the noise tolerance
is increased. If the
calculated rate is less than
this configured value, the
system establishes the
connection based on the
calculated rate while
keeping the target noise
tolerance.
Value range: 200 kbps –
30000 kbps
Default: 1552 kbps
Power spectrum density

mode
Value range:
SpanConfPSD → 1: symmetric
→ 2: asymmetric
Default: 1 (symmetric)
SHDSL line transmission

mode
Two options are available:
SpanConfTransmissionMode → 0: default
→ 1: custom
Default: 0

disables the management
on remote equipment
SpanConfRemoteEnabled
→ 1: enable
→ 2: disable
Line detection setting

Value range:
→ 1: noPower
SpanConfPowerFeeding
→ 2: powerFeed
→ 3: wettingCurrent
Default: 1 (noPower)
Downstream/Upstream
SpanConfCurrCondTargetMarginDown/SpanConfCurrCon current target
dTargetMarginUp signal-to-noise ratio
margin
This parameter is a noise

ratio tolerance reserved
during regular data
communication to ensure
normal communication in
case of bad line condition.
This is a reservation
measure. A larger
signal-to-noise ratio
margin (reserved
tolerance) indicates a
lower error probability
during data transmission
and a higher system
stability but a lower
maximum rate that can be
reached. In real-world
applications, the
signal-to-noise ratio is
selected based on line
condition.
Value range: 0–10 dB
Default: 5 dB
Downstream/Upstream
worst target
SpanConfWorstCaseTargetMarginDown/SpanConfWorst signal-to-noise ratio
CaseTargetMarginUp margin
Value range: –10 to 21 dB
Default: 0
User-configured target
margin
Value range:
→ 0: default
SpanConfUsedTargetMargins
→ 1: custom
By default, the current
downstream target
margin is effective.
Reference clock
Value range:
1: LocalClk
SpanConfReferenceClock 2: NetworkClk
3: DataOrNetworkClk
4: DataClk
Default: 1 (LocalClk)

disables the detection
SpanConfLineProbeEnable function.
→ 1: Disabled, the system
skips the line rate
adaption process to
reduce the duration for
G.SHDSL line
establishment.
→ 2: Enabled, the system

performs the line
detection function to
find a best line rate.
The detection function is
disabled by default.
3. Run the shdsl alarm-profile command to create an SHDSL alarm profile.
Table 70 lists the parameters to configure an SHDSL alarm profile.
Table 70 Parameter Description for Configuring an SHDSL Alarm

Profile
Alarm profile name 32 bytes
Loop attenuation threshold

During a performance data collection period of
15 minutes, an alarm occurs if the loop
EndpointThreshLoopAttenuation
attenuation parameter value is greater than this
threshold.
Default: 0
Signal-to-noise ratio redundancy threshold

During a performance data collection period of
15 minutes, an alarm occurs if the signal-to-noise
EndpointThreshSNRMargin
ratio of line is greater than this threshold.
Value range: –127 to 128 dB
Default: 0
Erroneous second threshold

During a specific period of 15 minutes, an alarm
occurs if the number of erroneous seconds is
EndpointThreshES
Value range: 0 to 900 dB
Default: 0
Severely erroneous second threshold

occurs if the number of severely erroneous
EndpointThreshSES
seconds is greater than this threshold.
Default: 0
Error CRC threshold

EndpointThreshCRCanomalies
occurs if the number of error CRCs is greater

Default: 0
LOSWS threshold
occurs if the number of LOSWS seconds is
EndpointThreshLOSWS
Default: 0
Unavailable second threshold

occurs if the number of unavailable seconds is
EndpointThreshUAS
Default: 0
5. Run the shdsl profile command to apply the SHDSL line profile to an
SHDSL port.
6. Run the shdsl alarm-profile command to apply the SHDSL alarm profile
to an SHDSL port.
Example >>
The following example shows how to create an ADSL base profile ADSL and an ADSL
alarm profile ALARM-ADSL and apply the profiles to the ADSL port adsl_1/3/1.
ZXAN(config)#adsl profile ADSL
This profile does not exist. Would you like to create? [y/n][y]
ZXAN(config)#adsl alarm-profile ALARM-ADSL
ZXAN(config)#interface adsl_1/3/1
ZXAN(config-if)#adsl profile ADSL
ZXAN(config-if)#adsl alarm-profile ALARM-ADSL
6.5.3 Configuring an MAC Address Pool
Abstract >>
This procedure describes how to configure an MAC address pool for a port of the ZXA10
C300M/C350M. When a subscriber accesses a network through PPPoA or IPoA, the NE
converts the PPPoA or IPoA packets into PPPoE or IPoE packets. Then the MAC
address pool allocates a source MAC address to the subscriber.
Steps >>

mode.
2. Run the mac pool command to configure an MAC address pool.
3. Run the show mac pool command to view the configuration result.
Example >>
Table 71 lists the configuration data of MAC address pool configuration.
Table 71 Configuration Data of MAC Address Pool Configuration

Item Data
Index of an MAC address pool 1
Starting MAC address 1214.1215.1212
Number of MAC addresses 10
ZXAN(config)#mac pool 1 1214.1215.1212 10
ZXAN(config)#show mac pool
Total mac: 10 Free mac: 10 Used mac: 0
Index startMac num/free/used
--------------------------------------
1 1214.1215.1212 10/10/0
6.5.4 Configuring a User Port PVC
Abstract >>
This procedure describes how to configure the PVC for a user port, that is, how to
establish a virtual (logical) connection between a user and the host by using the internal
control mechanism of the device, and how to ensure correct and ordered data
transmission on the connection.
Context >>
Table 72 describes the data transmission modes supported by VDSL and SHDSL ports.
Table 72 Data Transmission Modes

User Port Data Description
Type Transmission
Modes
The default mode is PTM.
In PTM mode, the port does not support PVC configuration,
PTM meaning that VPI/VCI and encapsulation modes are not
supported. Therefore, PVC parameters are not required for
VDSL port configuration.
In ATM mode, the port supports PVC configuration. The

ATM configurations for VDSL ports are the same as those for
ADSL ports.
The default mode is EFM.

In EFM mode, the port does not support PVC configuration,
EFM meaning that VPI/VCI and encapsulation modes are not
supported. Therefore, PVC parameters are not required for
SHDSL port configuration.
In ATM mode, the port supports PVC configuration. The

ATM configurations for SHDSL ports are the same as those for
ADSL ports.
Steps >>

mode.
3. Run the atm command to configure the user port PVC.
Example >>
The following example shows how to set the ADSL user port PVC to 1:
ZXAN(config-if-range)#atm pvc 1 vpi 8 vci 81
Note:
If the VDSL and SHDSL user ports operate in ATM mode, the port PVC needs to be
configured.
6.5.5 Activating an xDSL Port
Abstract >>
This procedure describes how to activate an xDSL port, which is required after xDSL
service data configuration.
Steps >>

mode.
Example >>
The following example shows how to activate the ADSL port 1/4/1–16:
ZXAN(config-if-range)#no shutdown
6.6 Configuration Instances
6.6.1 Configuring the ADSL/ADSL2 Service
Abstract >>
This procedure describes how to configure the ADSL/ADSL2 service.
Table 73 lists the configuration data of the ADSL/ADSL2+ service.
Table 73 ADSL/ADSL2 Configuration Data

Item Data
NE type ZXA10 C300M
Service VLAN 2000
User port adsl_1/4/1–16
Downstream rate 2 Mbps
Upstream rate 512 Kbps
VPI: 8
Modem PVC
VCI: 81
Steps >>
1. Create a service VLAN.
2. Enter the user port configuration mode and add the user port to the
service VLAN in untagged mode.
3. Enter the uplink port configuration mode and add the uplink port to the
service VLAN in tagged mode.
4 Configure the line profile, and set the upstream and downstream rates.
.
ZXAN(config)#adsl profile 2Mprofile
This profile does not exist. Would you like to create? [y/n][y]y
ZXAN(config)#adsl profile 2Mprofile
AtucConfRateMode(1-fixed,2-adaptAtStartup,3-adaptAtRuntime):[2]
AtucConfRateChanRatio(0..100%):[0]
AtucConfTargetSnrMgn(0..310(0.1dB)):[80]
AtucConfMaxSnrMgn(80..310(0.1dB)):[310]
AtucConfMinSnrMgn(0..80(0.1dB)):[0]
AtucConfDownshiftSnrMgn(0(0.1dB)):[0]
AtucConfUpshiftSnrMgn(0(0.1dB)):[0]
AtucConfMinUpshiftTime(0..16383s):[0]
AtucConfMinDownshiftTime(0..16383s):[0]
ConfProfileLineType(1-fast-only,2-interleaved-only):[2]
AtucChanConfFastMaxTxRate(0..131040kbps):[1024]
AtucChanConfFastMinTxRate(0..1024kbps):[32]
AtucChanConfInterleaveMaxTxRate(0..131040kbps):[1024] /*Maximum
downstream
rate of fast channel*/
AtucChanConfInterleaveMinTxRate(0..1024kbps):[32]
AtucChanConfMaxInterleaveDelay(0..255ms):[16]
AturConfRateMode(1-fixed,2-adaptAtStartup,3-adaptAtRuntime):[2]
AturConfRateChanRatio(0..100%):[0]
AturConfTargetSnrMgn(0..310(0.1dB)):[80]
AturConfMaxSnrMgn(80..310(0.1dB)):[310]
AturConfMinSnrMgn(0..80(0.1dB)):[0]
AturConfDownshiftSnrMgn(0(0.1dB)):[0]
AturConfUpshiftSnrMgn(0(0.1dB)):[0]
AturConfMinUpshiftTime(0..16383s):[0]
AturConfMinDownshiftTime(0..16383s):[0]
AturChanConfFastMaxTxRate(0..10240kbps):[512] /*Maximum
upstream
rate of fast channel*/
AturChanConfFastMinTxRate(0..512kbps):[32]
AturChanConfInterleaveMaxTxRate(0..10240kbps):[512]
AturChanConfInterleaveMinTxRate(0..512kbps):[32]
AturChanConfMaxInterleaveDelay(0..255ms):[16]
AtucDMTConfFreqBinsOperType(1-open,2-cancel):[2]
AturDMTConfFreqBinsOperType(1-open,2-cancel):[2]
LineDMTConfEOC(1-byte ,2-streaming ):[1]
LineDMTConfTrellis(1-on,2-off):[1]
AtucConfMaxBitsPerBin(0..15):[15]
AtucConfUseCustomBins(1-on,2-off):[2]
AtucConfDnBitSwap(1-on,2-off):[2]
AtucConfUpBitSwap(1-on,2-off):[2]
AtucConfREADSL2Enable(1-on,2-off):[2]
AtucConfPsdMaskType(1-DMT_PSD_MSK,2-ADSL2_PSD_MSK,3-ADSL2_
READSL_WIDE_PSD_MSK,4-
ADSL2_READSL_NARROW_PSD_MSK):[3]
AtucConfPMMode(1-DISABLE,2-L3_ENABLE,3-L2_ENABLE,4-L3_ENABL
E|L2_ENABLE):[1]
AtucConfPML0Time(0..255s):[240]
AtucConfPML2Time(0..255s):[120]
AtucConfPML2ATPR(0..31db):[3]
zxAnXdsl2LConfPsdMaskSelectUs:
(1)adlu32Eu32 - ADLU-32 / EU-32
(2)adlu36Eu36 - ADLU-36 / EU-36
(3)adlu40Eu40 - ADLU-40 / EU-40
(4)adlu44Eu44 - ADLU-44 / EU-44
(5)adlu48Eu48 - ADLU-48 / EU-48
(6)adlu52Eu52 - ADLU-52 / EU-52
(7)adlu56Eu56 - ADLU-56 / EU-56
(8)adlu60Eu60 - ADLU-60 / EU-60
(9)adlu64Eu64 - ADLU-64 / EU-61
Please choose the PsdMaskSelectUs(1-9):[1]
AtucConfPML2Rate(512..1024kbps):[512]
AtucConfMinInp(0-INP_AUTO,1-INP_0,2-INP_POINT5,3-INP_1,4-INP_2,5-I
NP_4,6-INP_8,7
-INP_16):[2]
AturConfMinInp(0-INP_AUTO,1-INP_0,2-INP_POINT5,3-INP_1,4-INP_2,5-I
NP_4,6-INP_8,7
-INP_16):[2]
ZXAN(config)#
5. (Optional) Configure an alarm profile.
ZXAN(config)#adsl alarm-profile alarm
This profile do not exist. Would you like to create? [y/n][y]y
ZXAN(config)#adsl alarm-profile alarm
AtucThresh15MinLofs(0..900s):[0]
AtucThresh15MinESs(0..900s):[0]
AtucThresh15MinLoss(0..900s):[0]
AtucThresh15MinLprs(0..900s):[0]
AtucThresh15MinLols(0..900s):[0]
AtucThreshFastRateUp(0..65535):[0]
AtucThreshInterleaveRateUp(0..65535):[0]
AtucThreshFastRateDown(0..65535):[0]
AtucThreshInterleaveRateDown(0..65535):[0]
AturThresh15MinLofs(0..900s):[0]
AturThresh15MinESs(0..900s):[0]
AturThresh15MinLoss(0..900s):[0]
AturThresh15MinLprs(0..900s):[0]
AturThreshFastRateUp(0..65535):[0]
AturThreshInterleaveRateUp(0..65535):[0]
AturThreshFastRateDown(0..65535):[0]
AturThreshInterleaveRateDown(0..65535):[0]
AtucInitFailureTrapEnable(1-enable,2-disable):[2]
lossOfFraming (0-disable,1-enable)[0]
lossOfSignal (0-disable,1-enable)[0]
lossOfPower (0-disable,1-enable)[0]
lossOfSignalQuality (0-disable,1-enable)[0]
AtucThreshold15MinFailedFastR(0..900s):[0]
AtucThreshold15MinSesL(0..900s):[0]
AtucThreshold15MinUasL(0..900s):[0]
AturThreshold15MinSesL(0..900s):[0]
AturThreshold15MinUasL(0..900s):[0]
AtucConnRateTolerance[Less than (0..100%) of the Prf will send

trap.]:[0]
MinThreshAtucConnRate[Less than(0..100000 kbps)will send trap.]:[0]
AturConnRateTolerance[Less than (0..100%)of the Prf will send trap.]:[0]
MinThreshAturConnRate[Less than(0..100000 kbps)will send trap.]:[0]
AtucConnRateTolerance[Exceed (0..100%) of the Prf will send trap.]:[0]
MaxThreshAtucConnRate[Exceed(0..100000 kbps)will send trap.]:[0]
AturConnRateTolerance[Exceed (0..100%) of the Prfwill send trap.]:[0]
MaxThreshAturConnRate[Exceed(0..100000 kbps)will send trap.]:[0]
ThreshAtucInpLeftr [Exceed(0..100)will send trap.]:[0]
ThreshAturInpLeftr [Exceed(0..100)will send trap.]:[0]
ZXAN(config)#
6. Enter the user port configuration mode and apply the line profile and
alarm profile to the specified ADSL ports.
ZXAN(config-if-range)#adsl profile 2Mprofile
ZXAN(config-if-range)#adsl alarm-profile alarm
7. Configure the user port PVC.
Note:
The modem VPIs and VCIs from different providers are configured in
different ways.
8. Activate the ports.
ZXAN(config-if-range)#end
ZXAN#write
6.6.2 Configuring the VDSL2 Service
Abstract >>
This procedure describes how to configure the VDSL2service.
Table 74 lists the configuration data of the VDSL2 service.
Table 74 VDSL2 Configuration Data

Item Data
NE type ZXA10 C300M
Service VLAN 2000
User port vdsl_1/3/1–16
Downstream rate 20 Mbps
Item Data
Upstream rate 20 Mbps
Steps >>
ZXAN(config-if-range)#switchport default vlan 2000
4 Configure the profiles.

.
a. Configure the VDSL downstream rate profile.
ZXAN(config)#vdsl2 dsdatarate-prf vdslds
This dsdatarate profile does not exist. Would you like to create?
[y/n][y]
ZXAN(config)#ZXAN(config)#vdsl2 dsdatarate-prf vdslds
zxAnXdsl2ChConfChannRaRatioDs(0..100):[100]
zxAnXdsl2ChConfMinDataRateDs(0..200000(kbps)):[32]
zxAnXdsl2ChConfMaxDataRateDs(32..200000(kbps)):[120000]
zxAnXdsl2ChConfMinResRateDs(0..200000(kbps)):[64]
zxAnXdsl2ChConfMinRateLowPwrDs(0..200000(kbps)):[128]
zxAnXdsl2ChConfMaxBerDs(eminus3(1), eminus5(2),
eminus7(3)):[3]
zxAnXdsl2ChConfDsDataRateDs(0..200000(kbps)):[0]
zxAnXdsl2ChConfUsDataRateDs(0..200000(kbps)):[200000]
zxAnXdsl2ChConfMinSosBitRateDs(0..200000(kbps)):[32]
b. Configure the VDSL upstream rate profile.
ZXAN(config)#vdsl2 usdatarate-prf vdslus
This usdatarate profile does not exist. Would you like to create?
[y/n][y]
ZXAN(config)#
ZXAN(config)#vdsl2 usdatarate-prf vdslus
zxAnXdsl2ChConfChannRaRatioUs(0..100):[100]
zxAnXdsl2ChConfMinDataRateUs(0..200000(kbps)):[32]
zxAnXdsl2ChConfMaxDataRateUs(32..200000(kbps)):[120000]
zxAnXdsl2ChConfMinResRateUs(0..200000(kbps)):[64]
zxAnXdsl2ChConfMinRateLowPwrUs(0..200000(kbps)):[128]
zxAnXdsl2ChConfMaxBerUs(eminus3(1), eminus5(2),
eminus7(3)):[3]
zxAnXdsl2ChConfDsDataRateUs(0..200000(kbps)):[0]
zxAnXdsl2ChConfUsDataRateUs(0..200000(kbps)):[200000]
zxAnXdsl2ChConfMinSosBitRateUs(0..200000(kbps)):[32]
c. Configure the VDSL SNR margin profile.
ZXAN(config)#vdsl2 snrmargin-prf vdslsnr
This snrmargin profile does not exist. Would you like to create?
[y/n][y]
ZXAN(config)#
ZXAN(config)#vdsl2 snrmargin-prf vdslsnr
zxAnXdsl2LConfTargetSnrmDs(0..310(0.1dB)):[80]
zxAnXdsl2LConfTargetSnrmUs(0..310(0.1dB)):[80]
zxAnXdsl2LConfMaxSnrmDs(81..310(0.1dB)):[300]
zxAnXdsl2LConfMaxSnrmUs(81..310(0.1dB)):[300]
zxAnXdsl2LConfMinSnrmDs(0..79(0.1dB)):[0]
zxAnXdsl2LConfMinSnrmUs(0..79(0.1dB)):[0]
zxAnXdsl2LConfRaUsNrmDs(0..310(0.1dB)):[90]
zxAnXdsl2LConfRaUsNrmUs(0..310(0.1dB)):[90]
zxAnXdsl2LConfRaUsTimeDs(0..16383(s)):[60]
zxAnXdsl2LConfRaUsTimeUs(0..16383(s)):[60]
zxAnXdsl2LConfRaDsNrmDs(0..310(0.1dB)):[30]
zxAnXdsl2LConfRaDsNrmUs(0..310(0.1dB)):[30]
zxAnXdsl2LConfRaDsTimeDs(0..16383(s)):[60]
zxAnXdsl2LConfRaDsTimeUs(0..16383(s)):[60]
zxAnXdsl2LConfSnrModeDs(1-VNDisabled 2-VNEnabled):[1]
zxAnXdsl2LConfSnrModeUs(1-VNDisabled 2-VNEnabled):[1]
zxAnXdsl2LConfRaModeDs(1-fixed 2-raInit 3-dynamicRa):[2]
zxAnXdsl2LConfRaModeUs(1-fixed 2-raInit 3-dynamicRa):[2]
d. Configure the VDSL line delay profile.
ZXAN(config)#vdsl2 delayinp-prf vdsldelay
This delayinp profile does not exist. Would you like to create? [y/n][y]
ZXAN(config)#
ZXAN(config)#vdsl2 delayinp-prf vdsldelay
zxAnXdsl2ChConfMaxDelayDs(0..63(ms)):[16]
zxAnXdsl2ChConfMaxDelayUs(0..63(ms)):[16]
Please configure MinProtection:
noProtection (1) - INP not required
halfSymbol (2) - INP length = 1/2 symbol
singleSymbol (3) - INP length = 1 symbol
twoSymbols (4) - INP length = 2 symbols
threeSymbols (5) - INP length = 3 symbols
fourSymbols (6) - INP length = 4 symbols
fiveSymbols (7) - INP length = 5 symbols
sixSymbols (8) - INP length = 6 symbols
sevenSymbols (9) - INP length = 7 symbols
eightSymbols (10) - INP length = 8 symbols
nineSymbols (11) - INP length = 9 symbols
tenSymbols (12) - INP length = 10 symbols
elevenSymbols (13) - INP length = 11 symbols
twelveSymbols (14) - INP length = 12 symbols
thirteenSymbols (15) - INP length = 13 symbols
fourteenSymbols (16) - INP length = 14 symbols
fifteenSymbols (17) - INP length = 15 symbols
sixteenSymbols (18) - INP length = 16 symbols
zxAnXdsl2ChConfMinProtectDs(1..18(Symbol)):[1]
zxAnXdsl2ChConfMinProtectUs(1..18(Symbol)):[1]
Please configure MinProtection8:
noProtection(1) - INP not required
singleSymbol(2) - INP length = 1 symbol
twoSymbols(3) - INP length = 2 symbols
threeSymbols(4) - INP length = 3 symbols
fourSymbols(5) - INP length = 4 symbols
fiveSymbols(6) - INP length = 5 symbols
sixSymbols(7) - INP length = 6 symbols
sevenSymbols(8) - INP length = 7 symbols
eightSymbols(9) - INP length = 8 symbols
nineSymbols(10) - INP length = 9 symbols
tenSymbols(11) - INP length = 10 symbols
elevenSymbols(12) - INP length = 11 symbols
twelveSymbols(13) - INP length = 12 symbols
thirteenSymbols(14) - INP length = 13 symbols
fourteenSymbols(15) - INP length = 14 symbols
fifteenSymbols(16) - INP length = 15 symbols
sixteenSymbols(17) - INP length = 16 symbols
zxAnXdsl2ChConfMinProtect8Ds(1..17(Symbol)):[1]
zxAnXdsl2ChConfMinProtect8Us(1..17(Symbol)):[1]
zxAnXdsl2ChConfForceInpDs(1-Enable,2-Disable):[1]
zxAnXdsl2ChConfForceInpUs(1-Enable,2-Disable):[1]
zxAnXdsl2ChConfMaxDelayVar(1..255(0.1ms)):[255]
zxAnXdsl2ChConfInitPolicy(1-policy0 , 2-policy1):[1]
e. Configure the VDSL spectrum profile.
ZXAN(config)#vdsl2 spectrum-prf vdslspec
This spectrum profile does not exist. Would you like to create?
[y/n][y]
ZXAN(config)#
ZXAN(config)#vdsl2 spectrum-prf vdslspec
First configure vdsl2 transmode bits:
Preferred modes:
[0] None
[1] G.993.2 Region A (North America) (Annex A/G.993.2)
[2] G.993.2 Region B (Europe) (Annex B/G.993.2)
[3] G.993.2 Region C (Japan) (Annex C/G.993.2)
Please choose one from the preferred modes:[2]
Second configure adsl2 transmode bits:
Preferred modes:
[0] None
[1] T1.413 G.dmt(fdm)
[2] T1.413 G.dmt(ec)
[3] Adsl2(fdm) Adsl2+(fdm) G.dmt(fdm) ReAdsl2(fdm)
[4] Adsl2(fdm) Adsl2+(ec) G.dmt(fdm) ReAdsl2(fdm)
[5] Adsl2(fdm) Adsl2+(fdm) G.dmt(fdm) ReAdsl2(fdm) T1.413
[6] Adsl2(fdm) Adsl2+(ec) G.dmt(fdm) ReAdsl2(fdm) T1.413
[7] Custom
[8] All Capability
Please choose one transmode to change to (0-8):[3]
zxAnXdsl2LConfVdsl2CarMask:
There are 0 bands been set, please to choose (0-no change,

1-modify the bands, 2
-delete all bands):[0]
zxAnXdsl2LConfMsgMinDs(4..248(kbps)):[4]
zxAnXdsl2LConfMsgMinUs(4..248(kbps)):[4]
zxAnXdsl2LConfCeFlag(1-Enable,2-Disable):[2]
Please configure zxAnXdsl2LConfPmMode:
allowTransitionsToIdle(0-disable,1-enable)[0]
allowTransitionsToLowPower(0-disable,1-enable)[0]
zxAnXdsl2LConfL0Time(0..255(s)):[255]
zxAnXdsl2LConfL2Atpr(0..31(dB)):[3]
zxAnXdsl2LConfL2Atprt(0..31(dB)):[31]
please configure the StandardProfile:
profile_8A (0-disable,1-enable)[0]
profile_8B (0-disable,1-enable)[0]
profile_8C (0-disable,1-enable)[0]
profile_8D (0-disable,1-enable)[0]
5. (Optional) Configure the alarm profile.
ZXAN(config)#vdsl2 alarm-prf vdslalarm
This alarmprofile does not exist. Would you like to create? [y/n][y]
ZXAN(config)#
ZXAN(config)#vdsl2 alarm-prf vdslalarm
zxAnXdsl2XtucThreshFecs(0..900(s)) :[0]
zxAnXdsl2XtucThreshEs(0..900(s)) :[0]
zxAnXdsl2XtucThreshSes(0..900(s)) :[0]
zxAnXdsl2XtucThreshLoss(0..900(s)) :[0]
zxAnXdsl2XtucThreshLofs(0..900(s)) :[0]
zxAnXdsl2XtucThreshLols(0..900(s)) :[0]
zxAnXdsl2XtucThreshLprs(0..900(s)) :[0]
zxAnXdsl2XtucThreshUas(0..900(s)) :[0]
zxAnXdsl2XtucThreshPtmCrcErrs(0..2147483647) :[0]
zxAnXdsl2XtucThreshPtmCodViol(0..2147483647) :[0]
zxAnXdsl2XturThreshFecs(0..900(s)) :[0]
zxAnXdsl2XturThreshEs(0..900(s)) :[0]
zxAnXdsl2XturThreshSes(0..900(s)) :[0]
zxAnXdsl2XturThreshLoss(0..900(s)) :[0]
zxAnXdsl2XturThreshLofs(0..900(s)) :[0]
zxAnXdsl2XturThreshLprs(0..900(s)) :[0]
zxAnXdsl2XturThreshUas(0..900(s)) :[0]
zxAnXdsl2XturThreshPtmCrcErrs(0..2147483647) :[0]
zxAnXdsl2XturThreshPtmCodViol(0..2147483647) :[0]
zxAnXdsl2ThreshFailedFullInt(0..2147483647) :[0]
zxAnXdsl2ThreshFailedShrtInt(0..2147483647) :[0]
zxAnXdsl2Ch1XtucThrshCodeViol(0..2147483647) :[0]
zxAnXdsl2Ch1XtucThrshCorrected(0..2147483647) :[0]
zxAnXdsl2Ch1XturThrshCodeViol(0..2147483647) :[0]
zxAnXdsl2Ch1XturThrshCorrected(0..2147483647) :[0]
zxAnXdsl2XtucLowDataRateTolerance(0..100) :[0]
zxAnXdsl2XturLowDataRateTolerance(0..100) :[0]
zxAnXdsl2XtucLowDataRateThresh(0..200000) :[0]
zxAnXdsl2XturLowDataRateThresh(0..200000) :[0]
zxAnXdsl2XtucInitFailTrapEnable :
lossOfSignalNotify (0-disable,1-enable)[0]
lossOfPowerNotify (0-disable,1-enable)[0]
initFailure (0-disable,1-enable)[0]
lossOfLink (0-disable,1-enable)[0] lossOfSignalAlarm

(0-disable,1-enable)[0]
zxAnXdsl2XturInitFailTrapEnable :
lossOfSignalNotify (0-disable,1-enable)[0]
lossOfPowerNotify (0-disable,1-enable)[0]
lossOfSignalAlarm (0-disable,1-enable)[0]
lossOfPowerAlarm (0-disable,1-enable)[0]
zxAnXdsl2XtucThreshInpLeftr(0..100) :[0]
zxAnXdsl2XturThreshInpLeftr(0..100) :[0]
zxAnXdsl2XtucEsLossRatioThresh(0..100) :[0]
zxAnXdsl2XturEsLossRatioThresh(0..100) :[0]
zxAnXdsl2XtucThreshInpLeftrs(0..900(s)) :[0]
zxAnXdsl2XturThreshInpLeftrs(0..900(s)) :[0]
6. Enter the user port configuration mode and apply the profiles to the
specified user ports.
ZXAN(config-if-range)#vdsl2 ch1dsdatarate-prf vdslds
ZXAN(config-if-range)#vdsl2 ch1usdatarate-prf vdslus
ZXAN(config-if-range)#vdsl2 snrmargin-prf vdslsnr
ZXAN(config-if-range)#vdsl2 ch1delayinp-prf vdsldelay
ZXAN(config-if-range)#vdsl2 spectrum-prf vdslspec
ZXAN(config-if-range)#vdsl2 alarm-prf vdslalarm
ZXAN(config-if-range)#data-path-mode atm
Note:
The Modem VPIs and VCIs vary with the vendors. For details, refer to
the corresponding instructions.
ZXAN#write
6.6.3 Configuring the SHDSL Service
Abstract >>
This procedure describes how to configure the SHDSLservice.
Table 75 lists the configuration data of the SHDSL service.
Table 75 SHDSL Configuration Data

Item Data
NE type ZXA10 C300M
Service VLAN 2000
User port shdsl_1/3/1–16
Minimum transmission rate of the user line 1000 Kbps
Maximum transmission rate of the user line 3000 Kbps
VPI: 8
Modem PVC
VCI: 81
Steps >>
44. Configure the line profile, and set the user line rate.
.
ZXAN(config)#shdsl profile shuserprofile
ZXAN(config)#shdsl profile shuserprofile
SpanConfWireInterface:
[1]-twoWire
[2]-fourWire
[3]-sixWire
[4]-eightWire
[5]-gsfourWireBitInterleave
[6]-fourWireByteInterleaveEnhanced
[7]-fourWireBitInterleaveEnhanced
SpanConfWireInterface:[1]
SpanConfMinLineRate(192..30000kbps):[200]1000 /*Minimum user line

rate*/
SpanConfMaxLineRate(200..30000kbps):[1552]3000 /*Maximum user

line rate*/
SpanConfPSD(1-symmetric,2-asymmetric):[1]
SpanConfTransmissionMode(0-default,1-custom):[0]
SpanConfRemoteEnabled(1-enable,2-disable)):[1]
SpanConfPowerFeeding(1-noPower,2-powerFeed,3-wettingCurrent):[1]
SpanConfCurrCondTargetMarginDown(-10..21dB):[5]
SpanConfWorstCaseTargetMarginDown(-10..21dB):[0]
SpanConfCurrCondTargetMarginUp(-10..21dB):[5]
SpanConfWorstCaseTargetMarginUp(-10..21dB):[0]
SpanConfUsedTargetMargins(0-default,1-custom):[0]
SpanConfReferenceClock(1-LocalClk,2-NetworkClk,3-DataOrNetworkClk,
4-DataClk):[1]
SpanConfLineProbeEnable(1-disable,2-enable):[1]
ZXAN(config)#
5. (Optional) Configure an alarm profile.
ZXAN(config)#shdsl alarm-profile shalarm
ZXAN(config)#shdsl alarm-profile shalarm
EndpointThreshLoopAttenuation(-127..128dB):[0]
EndpointThreshSNRMargin(-127..128dB):[0]
EndpointThreshES(0..900s):[0]
EndpointThreshSES(0..900s):[0]
EndpointThreshCRCanomalies(0..100000):[0]
EndpointThreshLOSWS(0..900s):[0]
EndpointThreshUAS(0..900s):[0]
ZXAN(config)#
6. Enter the user port configuration mode and apply the line profile and
alarm profile to the specified ADSL ports.
ZXAN(config-if-range)#shdsl profile shuserprofile
ZXAN(config-if-range)#shdsl alarm-profile shalarm
ZXAN(config-if-range)#data-path-mode atm
Note:
The modem VPIs and VCIs from different providers are configured in
different ways.
ZXAN#write
6.6.4 Configuring the IPoA Service
Abstract >>
This procedure describes how to configure the IPoA service.
Context >>
The IPoA is a technology for transferring IP data packets over ATM-LAN. It specifies IP
data communication that uses the ATM network to establish connections, especially
Switched Virtual Circuits (SVCs), between ATM terminals.
In IPoA, the IP packet payload is carried on the corresponding Ethernet frame and sent to
the upper-layer network. The IPoE packets are conversed into IPoA packets and
forwarded to users in the downlink direction.
The IPoA is normally used for dedicated accesses, meeting the requirements of smooth
evolution from ATM network to IP network.
Table 76 lists the configuration data of the IPoA service.
Table 76 IPoA Configuration Data

Item Data
NE type ZXA10 C300M
User port adsl_1/3/1
MAC address pool 1a22.2222.2222/1024
Gateway IP address 172.1.1.1
VLAN ID of user interface and uplink interface 2
Aging time of the gateway MAC address 5 minutes
Aging time for automatically learning user IP address 5 minutes
Steps >>
1. Configure the MAC address pool of the IPoA.
ZXAN(config)#mac pool 1 1a22.2222.2222 1024
2. (Optional) Configure the default gateway of the IPoA.
ZXAN(config)#ipoa l2-default-gateway 172.1.1.1
3. Enable the ARP extraction function.
ZXAN(config)#arp-agent vlan 2
4. Enter the user interface configuration mode and configure the circuit
encapsulation format.
ZXAN(config-if)#encapsulation IPOA_LLC pvc 1
Note:
The prerequisite of this command is that the MAC address pool has been
configured and there are available MAC addresses.
5. Configure the circuit VCI and VPI.
ZXAN(config-if)#pvc 1 enable
ZXAN(config-if)#atm pvc 1 vpi 8 vci 8
6. Configure the VLANs of the user interface and uplink interface.
ipo
ZXAN(config-if)#switchport default vlan 2 pvc 1
7. Configure the IPoA users. The following takes dynamic IPoA users as an
example.
ZXAN(config-if)#ipoa pvc 1 inatmarp l2 gateway 172.1.1.1
8. Configure the IPoA timers, which are the aging time of the gateway MAC
address and aging time for automatically learning the user IP address.
ZXAN(config)#ipoa gateway-arp-interval 5
ZXAN(config)#ipoa inatmarp-interval 5
ZXAN(config)#exit
9. Save the configuration.
ZXAN#write
10. Configure the modem.
On the modem, configure an IPoA PVC1 with the VPI as 8, VCI as 1, IP

address as 172.1.1.2, and gateway IP address as 172.1.1.1.
1 (Optional) View the configuration results.

1
. ZXAN(config)#show ipoa user
Total ipoa user: 1
---------------------------------------------------------
interface adsl_1/3/1 pvc 1 vlan 2 inatmarp ipoa enable
user ip: 172.1.1.2 user mac: 1a22.2222.2222
gateway ip: 172.1.1.1 gateway mac: 0013.4666.9ACB
Note:
• If the IPoA is in disable state, it indicates that the circuit

encapsulation format does not support the IPoA. In this case, the
circuit encapsulation format needs to be configured.
• If the user IP address is 0.0.0.0, it indicates that the user IP address

is not learned, which may be caused by incorrect VPI or VCI.
• If the user MAC address is 0000.0000.0000, it indicates that the

gateway MAC address is not learned, which may be caused by
incorrect gateway connection or disabled ARP extraction function.
6.6.5 Configuring Annex J
Abstract >>
This procedure describes how to configure Annex J parameters. Annex J applies to

all-digital services, enabling digital DSL signals to be transmitted in the traditional voice
band. The downstream transmission rate reaches 12 Mbps and the upstream
transmission rate reaches 3.5 Mbps.
Steps >>
1. Enter ADSL user interface configuration mode.
ZXAN(config-if)#
2. Configure the Annex transmission mode.

ZXAN(config-if)#adsl trans-mode
Preferred modes:
[1] T1.413 G.dmt
[2] T1.413 G.dmt g.lite
[3] Adsl2 Adsl2+ G.dmt ReAdsl2
[4] Adsl2 Adsl2+ G.dmt ReAdsl2 AnnexM
[5] Adsl2 Adsl2+ G.dmt ReAdsl2 T1.413
[6] Adsl2 Adsl2+ G.dmt ReAdsl2 T1.413 AnnexM
[7] AnnexB T1.413
[8] Custom
[9] Transcap-All
Please choose one transmode to change to (1-9):[3]8
| t1.413 |--------------|-----|(0-disable,1-enable)[0]
| etsi |--------------|-----|(0-disable,1-enable)[0]
| g.dmt | annex a | fdm |(0-disable,1-enable)[1]
| g.dmt | annex a | ec |(0-disable,1-enable)[0]
| g.dmt | annex b | fdm |(0-disable,1-enable)[0]
| g.dmt | annex b | ec |(0-disable,1-enable)[0]
| g.lite | annex a | fdm |(0-disable,1-enable)[0]
| g.lite | annex a | ec |(0-disable,1-enable)[0]
| adsl2 | annex a | fdm |(0-disable,1-enable)[1]
| adsl2 | annex a | ec |(0-disable,1-enable)[0]
| adsl2 | annex b | fdm |(0-disable,1-enable)[0]
| adsl2 | annex b | ec |(0-disable,1-enable)[0]
| adsl2 | annex i | fdm |(0-disable,1-enable)[0]

| adsl2 | annex i | ec |(0-disable,1-enable)[0]
| adsl2 | annex j | fdm |(0-disable,1-enable)[0]1
| adsl2 | annex j | ec |(0-disable,1-enable)[0]
| adsl2 | annex l | fdm |(0-disable,1-enable)[1]
| adsl2 | annex l | ec |(0-disable,1-enable)[0]
| adsl2 | annex m | fdm |(0-disable,1-enable)[0]
| adsl2 | annex m | ec |(0-disable,1-enable)[0]
| adsl2+ | annex a | fdm |(0-disable,1-enable)[1]
| adsl2+ | annex a | ec |(0-disable,1-enable)[0]
| adsl2+ | annex b | fdm |(0-disable,1-enable)[0]
| adsl2+ | annex b | ec |(0-disable,1-enable)[0]
| adsl2+ | annex i | fdm |(0-disable,1-enable)[0]
| adsl2+ | annex i | ec |(0-disable,1-enable)[0]
| adsl2+ | annex j | fdm |(0-disable,1-enable)[0]1
| adsl2+ | annex j | ec |(0-disable,1-enable)[0]
| adsl2+ | annex m | fdm |(0-disable,1-enable)[0]
| adsl2+ | annex m | ec |(0-disable,1-enable)[0]
6.7 ADSL Service Configuration
6.7.1 Configuring the ADSL Link Establishment Rate
Abstract >>
This procedure describes how to configure the Asymmetric Digital Subscriber Line (ADSL)
link establishment rate, that is, the uploading and downloading rates of the ADSL service.
Steps >>

mode.
2. Run the adsl profile command to create a line parameter profile.
3. Run the adsl profile command again to modify the line profile.
5. Run the adsl profile command again to apply the line profile to a user
port.
6. Run the show adsl port-status command to query the configuration

results.
Example >>
The following example shows how to configure the ADSL link establishment rate. In this
example, the maximum fast channel downstream rate is set to 2 M, the maximum
interleave channel downstream rate to 2 M, and other parameters use the default values.
ZXAN(config)#adsl profile adsl
This profile does not exist. Would you like to create? [y/n][y]y
ZXAN(config)#adsl profile adsl
...... Some information displayed is omitted here.
AtucChanConfFastMaxTxRate(0..131040kbps):[1024]2048 /*Maximum fast channel

downstream rate*/
AtucChanConfFastMinTxRate(0..1024kbps):[32] /*Minimum fast channel

downstream rate*/
AtucChanConfInterleaveMaxTxRate(0..131040kbps):[1024]2048 /*Maximum interleave

channel downstream rate*/
AtucChanConfInterleaveMinTxRate(0..1024kbps):[32] /*Minimum interleave

channel downstream rate*/
AturChanConfFastMaxTxRate(0..10240kbps):[512] /*Maximum fast channel

upstream rate*/
AturChanConfFastMinTxRate(0..512kbps):[32] /*Minimum fast channel

upstream rate*/
AturChanConfInterleaveMaxTxRate(0..10240kbps):[512] /*Maximum interleave

channel upstream rate*/
AturChanConfInterleaveMinTxRate(0..512kbps):[32] /*Minimum interleave

channel upstream rate*/
ZXAN(config-if)#adsl profile ADSL
Note:
The command applying the line profiles to user ports supports batch configuration.
ZXAN(config-if-range)#adsl profile ADSL
6.7.2 Configuring the ADSL Link Type
Abstract >>
This procedure describes how to configure and modify the ADSL link types.
There are two ADSL link types:
• FastOnly
This type of link has high speed, and is applicable when the line is short
and of good quality, for example, for short-distance demonstration.
• InterleavedOnly
This type of link has low downloading rate, but it is stable. It is applicable
when the line is in bad condition.
Context >>
The ADSL link type can only be configured in the line profile. You can change the link
type by modifying the line profile.
The link type can be modified in the following ways:
• Use the adsl profile command to modify the ConfProfileLineType

parameter to modify the link type.
• Use the line-type command.
This topic takes the line-type command as an example.
Steps >>

mode.
2. Run the adsl-profile command to enter the adsl-profile configuration

mode.
3. Run the line-type command to configure the ADSL link type.
4. Run the show adsl profile command to view the configuration results.
Example >>
The following example shows how to set the ADSL link type to fast channel:
ZXAN(config)#adsl-profile ADSL
ZXAN(cfg-adsl-prf)#line-type fast-only
ZXAN(cfg-adsl-prf)#show adsl profile adsl
ConfProfileLineType :fast-only /*ADSL link type*/
6.7.3 Configuring the Data Transmission Mode for an ADSL Port
Abstract >>
Transmission equipment must comply with some standards, such as G.dmt, G.lite, and
AnnexM, which stipulate the upstream and downstream transmission rates and effective
transmission distance of ADSL links.
This procedure describes how to configure the data transmission mode for an ADSL port.
Context >>
Table 77 lists the ADSL equipment's upstream and downstream transmission rates
stipulated in some standards.
Table 77 ADSL Line Transmission Mode and Rate

Standard Upstream/Downstream Rate
Standard Upstream/Downstream Rate

Upstream rate: 1.5 Mbps
G.dmt
Downstream rate: 8 Mbps

G.lite
Downstream rate: 512 kbps

Annex M
Upstream rate: 896 kbps

ANSI T1.413 Issue #2
Steps >>

mode.
3. Run the adsl trans-mode command to configure the ADSL link

transmission mode
4. Run the show adsl port-config command to view the configuration

results.
Example >>
The following example shows how to setthe link transmission of the ADSL port 1/5/1 to
G.dmt ReAdsl2:
ZXAN(config-if)#adsl trans-mode
Preferred modes:
[1] T1.413 G.dmt
[2] T1.413 G.dmt g.lite
[3] Adsl2 Adsl2+ G.dmt ReAdsl2
[4] Adsl2 Adsl2+ G.dmt ReAdsl2 AnnexM
[5] Adsl2 Adsl2+ G.dmt ReAdsl2 T1.413
[6] Adsl2 Adsl2+ G.dmt ReAdsl2 T1.413 AnnexM
[7] AnnexB T1.413
[8] Custom
[9] Transcap-All
ZXAN(config)#show adsl port-config adsl_1/5/1
LineConfProfile : DEFVAL.PRF
LineExtProfile : VEXTDEFVAL.PRF
AlarmConfProfile : DEFVAL.PRF
AdslLinePMConfPMSF : L0_FullOn
AdslLineTransMode : | g.dmt | annex a | fdm |
| adsl2 | annex a | fdm |
| adsl2 | annex l | fdm |
| adsl2+ | annex a | fdm |
Note:
Generally, the ADSL link transmission mode does not need to be modified and mode 3 is
used by default. Mode 3 is an ADSL/ADSL2/ADSL2+ compatible mode and is compatible
with various modems.
6.8 VDSL2 Service Configuration

Abstract >>
This procedure describes how to configure the VDSL2 link establishment rate, that is, the
uploading and downloading rates of the VDSL2 service.
Context >>
There is one default Base profile, one default Downstream Power Back Off (DPBO)
profile, one default Service profile, and one default Upstream Power Back-Off (UPBO)
profile. The NE supports 80 Base profiles, 256 DPBO profiles, 256 Service profiles, and
40 UPBO profiles, including the default ones.
Steps >>

mode.
2. Run the vdsl2 spectrum-prf command to create a spectrum profile.
3. Run the vdsl2 dpbo-profile command to create a DPBO profile.
4. Run the vdsl2 upbo-profile command to create a UPBO profile.
6. Run the vdsl2 spectrum-prf command to apply the spectrum profiles to a

port.
7. Run the vdsl2 dpbo-prf command to apply the DPBO profiles to a port.
8. Run the vdsl2 upbo-prf command to apply the UPBO profiles to a port.
Example >>
The following example shows how to create a spectrum profile, a DPBO profile, and a
UPBO profile with all default parameter values and apply the profiles to the VDSL port
vdsl_1/7/1:
ZXAN(config)#vdsl2 spectrum-prf vdslspnew
This spectrum profile does not exist. Would you like to create? [y/n][y]
ZXAN(config)#
ZXAN(config)#vdsl2 spectrum-prf vdslspnew
First configure vdsl2 transmode bits:
Preferred modes:
[0] None
Please choose one from the preferred modes:[2]
Second configure adsl2 transmode bits:
Preferred modes:
[0] None
[1] T1.413 G.dmt(fdm)
[2] T1.413 G.dmt(ec)
[3] Adsl2(fdm) Adsl2+(fdm) G.dmt(fdm) ReAdsl2(fdm)
[4] Adsl2(fdm) Adsl2+(ec) G.dmt(fdm) ReAdsl2(fdm)
[5] Adsl2(fdm) Adsl2+(fdm) G.dmt(fdm) ReAdsl2(fdm) T1.413
[6] Adsl2(fdm) Adsl2+(ec) G.dmt(fdm) ReAdsl2(fdm) T1.413
[7] Custom
[8] All Capability
zxAnXdsl2LConfVdsl2CarMask:
There are 0 bands been set, please to choose (0-no change, 1-modify the bands,
2-delete
all bands):[0]
zxAnXdsl2LConfMsgMinDs(4..248(kbps)):[4]
zxAnXdsl2LConfMsgMinUs(4..248(kbps)):[4]
zxAnXdsl2LConfCeFlag(1-Enable,2-Disable):[2]
Please configure zxAnXdsl2LConfPmMode:
allowTransitionsToIdle(0-disable,1-enable)[0]
allowTransitionsToLowPower(0-disable,1-enable)[0]
zxAnXdsl2LConfL2Atpr(0..31(dB)):[3]
zxAnXdsl2LConfL2Atprt(0..31(dB)):[31]
please configure the StandardProfile:
profile_8C (0-disable,1-enable)[0]
profile_8D (0-disable,1-enable)[0]
ZXAN(config)#vdsl2 dpbo-prf vdsldpbo
This dpbo profile does not exist. Would you like to create? [y/n][y]
ZXAN(config)#
ZXAN(config)#vdsl2 dpbo-prf vdsldpbo
zxAnXdsl2LConfDpboEPsd:
[1] adsl mode
[2] adsl2 mode
[3] adsl2+ mode
[4] vdsl2 998_M2x_A mode
[5] vdsl2 998E17-M2x-NUS0 mode
[6] custom
zxAnXdsl2LConfDpboEPsd:[3]
zxAnXdsl2LConfDpboEsEL(0..511(0.5dB)):[0]
zxAnXdsl2LConfDpboEscmA(0..640(2^-8)):[263]
zxAnXdsl2LConfDpboEscmB(0..640(2^-8)):[509]
zxAnXdsl2LConfDpboEscmC(0..640(2^-8)):[261]
zxAnXdsl2LConfDpboMus(0..255(-0.5dBm/Hz)):[190]
zxAnXdsl2LConfDpboFMin(0..2048(4.3125KHz)):[32]
zxAnXdsl2LConfDpboFMax(32..6956(4.3125KHz)):[511]
ZXAN(config)#vdsl2 upbo-prf vdslupbo
This upbo profile does not exist. Would you like to create? [y/n][y]
ZXAN(config)#
ZXAN(config)#vdsl2 upbo-prf vdslupbo
zxAnXdsl2LConfUpboKL(0..1280(0.1dB)):[0]
zxAnXdsl2LConfUpboKLF:
[1] auto
[2] force
[3] disableUpbo
[4] max
[5] min
[6] always_CO
[7] always_CPE
zxAnXdsl2LConfUpboKLF:[3]
zxAnXdsl2LConfUpboU1bandPsdA(4000..8095(0.01dBm/Hz)):[5650]
zxAnXdsl2LConfUpboU1bandPsdB(0..4095(0.01dBm/Hz)):[1020]
zxAnXdsl2LConfUpboU1bandKLRef(0 or 18..635(0.1dB)):[0]
ZXAN(config)#interface vdsl_1/7/1
ZXAN(config-if)#vdsl2 spectrum-prf vdslspnew
ZXAN(config-if)#vdsl2 dpbo-prf vdsldpbo
ZXAN(config-if)#vdsl2 upbo-prf vdslupbo
6.8.1 Configuring the Data Transmission Mode for a VDSL Port
Abstract >>
This procedure describes how to configure the data transmission mode for a VDSL port.
Context >>
The VDSL port supports the following transmission modes:
• PTM, which is the default mode
In this mode, the port does not support PVC operations, that is, does not
support the configuration of the VPI, VCI, or the encryption mode.
Therefore, you do not need to set PVC parameters for port configuration.
• ATM
In this mode, the port supports PVC operations. The VDSL port
configuration is the same as the ADSL port configuration.
Steps >>

mode.
3. Run the data-path-mode command to configure the data transmission

mode of a VDSL port.
4. Run the show interface command to view the configuration result.
Example >>
The following example shows how to configure the data transmission mode of the VDSL
port vdsl_1/7/1:
ZXAN(config-if)#data-path-mode ptm
ZXAN(config-if)#show interface vdsl_1/7/1
vdsl_1/7/1 is deactivate,line protocol is down.
Description is none.
The port is deactivate.
The port link up/down notification is trap disable.
The DataPathMode is PTM. // The VDSL2 port transmission mode is PTM.
Last up time is unavailable.
Last down time is unavailable.
Default vlanid :1
Multicast snooping :enable
Num of up stream packets :0
Num of up stream bytes :0
Num of down stream packets :0
Num of down stream bytes :0
6.8.2 Configuring a VDSL2 Port VLAN
Abstract >>
This procedure describes how to configure a VDSL2 port VLAN.
Context >>
A port can be added to a VLAN in tagged or untagged mode.
• When a port is added to a VLAN in tagged mode, the Ethernet packets

forwarded from the port to the VLAN carry the VLAN tag.
• When a port is added to a VLAN in untagged mode, the Ethernet packets

forwarded from the port to the VLAN do not carry any VLAN tag.
Which mode is used depends on the port of the uplink switch connected to the port.
Steps >>

mode.
3. Run the switchport mode command to configure the work mode of a

VDSL2 port.
4. Run the switchport vlan command to add the VDSL2 port to a VLAN.
Example >>
The following example shows how to set the VLAN mode of the VDSL port vdsl_1/7/1 to
trunk, with the VLAN ID of 4:
6.8.3 Querying the VDSL2 Link Performance Data
Abstract >>
This procedure describes how to query the link performance data of a connected VDSL2
port.
Prerequisite >>
The VDSL2 port is connected.
Steps >>
Query the physical performance data of the VDSL2 port.
To Do This
Query the history performance data of the ZXAN(config)#show vdsl2 15min-init

VDSL2 link initialization during 15–minute
timeslot vdsl_1/7/1
Query the history performance data of the ZXAN(config)#show vdsl2 1day-init

VDSL2 link initialization during one-day vdsl_1/7/1
timeslot
Query the history performance data of the ZXAN(config)#show vdsl2

VDSL2 link during 15–minute timeslot 15min-interval vdsl_1/7/1
Query the history performance data of the ZXAN(config)#show vdsl2

VDSL2 link during one-day timeslot 1day-interval vdsl_1/7/1
Query the history channel-layer performance ZXAN(config)#show vdsl2

data of the VDSL2 link during 15–minute chan-15min-interval
timeslot. vdsl_1/7/1
Query the history channel-layer performance ZXAN(config)#show vdsl2

data of the VDSL2 link during one-day timeslot chan-1day-interval
vdsl_1/7/1
Query the current channel-layer performance ZXAN(config)#show vdsl2 chan-curr

data of the VDSL2 link vdsl_1/7/1
Query the current channel-layer status of the ZXAN(config)#show vdsl2 chan-status

VDSL2 link vdsl_1/7/1
Query the current performance data of the ZXAN(config)#show vdsl2 curr

Query the current initialization data of the ZXAN(config)#show vdsl2 curr-init

Query the detailed inventory information on the ZXAN(config)#show vdsl2 inventory

Query the detailed information on the VDSL2 ZXAN(config)#show vdsl2 line

link vdsl_1/7/1
Query the detailed bandwidth information on ZXAN(config)#show vdsl2 line-band

the VDSL2 link vdsl_1/7/1
6.8.4 Configuring the VDSL2 Bonding Function
Abstract >>
This procedure describes how to configure the Bonding function.
Context >>
The ZXA10 C300M/C350M supports VDSL2 port Bonding, where multiple ports are
physically provisioned to the end user and the total bandwidth is equal to the sum of all
provisioned ports.
Steps >>
1. Add interfaces to a Bonding group.
ZXAN(config)#add-bonding 1 interface vdsl_1/2/1
ZXAN(config)#add-bonding 1 interface vdsl_1/2/2
2. Configure the Bonding group properties.
ZXAN(config)#bonding 1
gBondAdminScheme(0-unknown,1-g9981,2-g9982,3-g9983):[2]
gBondTargetUpDataRate(1..1000000|9999999) kbps:[9999999]
gBondTargetDownDataRate(1..1000000|9999999) kbps:[9999999]
gBondThreshLowUpRate(1..1000000) kbps:[1]
gBondThreshLowDownRate(1..1000000) kbps:[1]
gBondLowRateCrossingEnable(1-true,2-false) :[2]
3. (Optional) Query the bonding group configuration.
ZXAN(config)#show bonding 1
Bonding Id: 1
shelf slot port
------------------------------------
1 2 1
1 2 2
4. (Optional) Query the bonding group properties.
ZXAN(config)#show bonding-config 1
AdminScheme :g9982
TargetUpDataRate :9999999
TargetDownDataRate :9999999
ThreshLowUpRate :1
ThreshLowDownRate :1
CrossingEnable :false
5. (Optional) Query the bonding group status.
ZXAN(config)# show bonding-status 1
GBOND PortStatus Table :
OperScheme : g9982
PeerOperScheme : g9982
UpDataRate :0
DownDataRate :0
FltStatus : no
PortSide : office(2)
NumBCEs :2
EthTcOperType : tcHDLC(2)
EthInErrors :0
EthInSmallFragments :0
EthInLargeFragments :0
EthInBadFragments :0
EthInLostFragments :0
EthInLostStarts :0
EthInLostEnds :0
EthInOverflows :0
6.9 SHDSL Service Configuration
6.9.1 Configuring the SHDSL Link Establishment Rate
Abstract >>
This procedure describes how to configure the Single-pair High Digital Subscriber Line
(SHDSL) link establishment rate, that is, the uploading and downloading rates of the
SHDSL service.
Context >>
The NE supports 128 line profiles, including two default profiles.
Steps >>

mode.
2. Run the shdsl profile command to create an SHDSL line profile.
3. Run the shdsl profile command again to modify the parameters of the
SHDSL line profile.
5. Run the shdsl profile command to apply the line profile to an SHDSL
port.
6. Run the show shdsl profile command to query the configuration result:
Example >>
Table 78 lists the configuration data of an SHDSL line profile.
Table 78 SHDSL Line Profile Configuration Data

Item Data
Item Data
Profile name SHDSL
Minimum line rate 1024 kbps
Maximum line rate 2048 kbps
ZXAN(config)#shdsl profile shprofile
ZXAN(config)#
ZXAN(config)#shdsl profile shprofile
SpanConfWireInterface:
[1]-twoWire
[2]-fourWire
[3]-sixWire
[4]-eightWire
[5]-gsfourWireBitInterleave
[6]-fourWireByteInterleaveEnhanced
[7]-fourWireBitInterleaveEnhanced
SpanConfWireInterface:[1]
SpanConfMinLineRate(192..30000kbps):[200]1024
SpanConfMaxLineRate(1024..30000kbps):[1552]2048
SpanConfPSD(1-symmetric,2-asymmetric):[1]
SpanConfTransmissionMode(0-default,1-custom):[0]
SpanConfRemoteEnabled(1-enable,2-disable)):[1]
SpanConfPowerFeeding(1-noPower,2-powerFeed,3-wettingCurrent):[1]
SpanConfCurrCondTargetMarginDown(-10..21dB):[5]
SpanConfWorstCaseTargetMarginDown(-10..21dB):[0]
SpanConfCurrCondTargetMarginUp(-10..21dB):[5]
SpanConfWorstCaseTargetMarginUp(-10..21dB):[0]
SpanConfUsedTargetMargins(0-default,1-custom):[0]
SpanConfReferenceClock(1-LocalClk,2-NetworkClk,3-DataOrNetworkClk,4-DataClk):[1]
SpanConfLineProbeEnable(1-disable,2-enable):[1]
ZXAN(config)#interface shdsl_1/2/1
ZXAN(config-if)#shdsl profile shprofile
ZXAN(config-if)#show shdsl profile shprofile
SpanConfWireInterface :twoWire
SpanConfMinLineRate :1024
SpanConfMaxLineRate :2048
SpanConfPSD :symmetric
SpanConfTransmissionMode :region 2 Indicates ITU-T G.991.2 Annex B.
SpanConfRemoteEnabled :enable
SpanConfPowerFeeding :noPower
SpanConfCurrCondTargetMarginDown :5
SpanConfWorstCaseTargetMarginDown :0
SpanConfCurrCondTargetMarginUp :5
SpanConfWorstCaseTargetMarginUp :0
SpanConfUsedTargetMargins :currCondDown
SpanConfReferenceClock :LocalClk
SpanConfLineProbeEnable :disable
6.9.2 Configuring the Data Transmission Mode for an SHDSL Port
Abstract >>
This procedure describes how to configure the data transmission mode for an SHDSL
port.
Context >>
An SHDSL port supports the following two data transmission modes:
• Ethernet in the First Mile (EFM), which is the default mode
In this mode, the port does not support PVC operations, that is, does not
support the configuration of the VPI, VCI, or the encryption mode.
Therefore, you do not need to select PVC parameters for port
configuration.
• ATM
In this mode, the port supports PVC operations. The SHDSL port
configuration is the same as the ADSL port configuration.
Steps >>

mode.
3. Run the data-path-mode command to configure the data transmission

mode of an SHDSL port.
4. Run the show interface command to query the configuration result.
Example >>
The following example shows how to configure the data transmission mode of an SHDSL
port to EFM:
ZXAN(config-if)#data-path-mode efm
ZXAN(config-if)#show interface shdsl_1/2/1
shdsl_1/2/1 is deactivate,line protocol is down.
Description is none.
The port is deactivate.
The port link up/down notification is trap disable.
The DataPathMode is EFM. // The SHDSL port data transmission mode is EFM
Last up time is unavailable.
Last down time is unavailable.
Default vlanid :1
Num of up stream packets :0
Num of up stream bytes :0
Num of down stream packets :0
Num of down stream bytes :0
Note:
After the data transmission mode is modified, all the existing configuration data on the
port is cleared and restored to the default settings.
6.9.3 Configuring an SHDSL Port VLAN
Abstract >>
This procedure describes how to configure an SHDSL port VLAN.
Context >>
A port can be added to a VLAN in tagged or untagged mode.
• When a port is added to a VLAN in tagged mode, the Ethernet packets

forwarded from the port to the VLAN carry the VLAN tag.
• When a port is added to a VLAN in untagged mode, the Ethernet packets

forwarded from the port to the VLAN do not carry any VLAN tag.
Which mode is used depends on the port of the uplink switch connected to the port.
Steps >>

mode.
3. Run the switchport mode command to configure the work mode of an

SHDSL port.
4. Run the switchport vlan command to add the SHDSL port to a VLAN.
Example >>
The following example shows how to set the VLAN mode of the SHDSL port shdsl_1/6/1
to trunk, with the VLAN ID of 2:
6.9.4 Querying the SHDSL Link Performance Data
Abstract >>
This procedure describes how to query the link performance data on an SHDSL port,
including the link establishment rate, current Signal to Noise Ratio (SNR) margin,
attenuation, and attainable rate.
Prerequisite >>
The SHDSL port is connected.
Steps >>
Query the link performance on an SHDSL port.
ZXAN(config)#show shdsl port-status shdsl_1/6/1
Port Link Speed Curr. SNR Attenuation Attainable Rate
ADM/OPR (kbps) UP/DOWN UP/DOWN (kbps)
---------------------------------------------------------------------------
6/01 up/ up 1544 15/ 20 0/ 1 1544
6.10 Basic LAN Service Configuration

Overview >>
LAN services use the Ethernet access technology to provide network accesses in the
bandwidth resource sharing mode. With network cables directly connected to users from
WAN nodes through switches and hubs, a large-scale high-speed LAN can be
established.
Network Diagram >>
Figure 22 shows a network diagram of the LAN service. The service card HDDT of the
ZXA10 C300M/C350M provides an optical interface and is directly connected to the
switch in a residential quarter or building through a optical fiber and then to the users
through network cables. The upstream and downstream rates are symmetric with a small
delay.
Figure 22 Network Diagram of the LAN Service
Configuration Flow >>
Figure 23 shows a configuration workflow to configure the LAN service.
Figure 23 Configuration Flow of the LAN Service
Table 93 lists the description of the configuration workflow of the LAN service.
Table 93 Configuration Flow Description of the LAN Service

Configuration Description
Operation
Creates a card supporting the LAN service by running the
Creating a card
add-card command. For details, refer to Adding a Service Card.
Creating a service Creates a service VLAN and adds service ports to the service
VLAN VLAN. For details, refer to Creating a Service VLAN.
Configures the user interface mode, TPID, and port adaption

Creating a service
mode in user port configuration mode. For details, refer to
port
Configuring a User Port.
Activating the Activates the port that is configured. For details, refer to Activating
service port a User Port.
6.10.1 Adding a Service Card
Abstract >>
This procedure describes how to add an HDTT card to provide LAN services. The HDTT
card of the ZXA10 C300M/C350M is an 8-GE optical interface Ethernet card.
Steps >>

mode.
2. Run the add-card command to add a service card.
Example >>
The following example shows how to add an HDTTU subscriber card in slot 7:
ZXAN(config)#add-card slot 7 HDTTU
6.10.2 Creating a Service VLAN
Abstract >>
This procedure describes how to create a service VLAN and add a service port to the
VLAN.
Steps >>

mode.
2. Run the vlan command to create a service VLAN.
4. Run the switchport command to add a service port to the VLAN.
Example >>
The following example shows how to create a service VLAN based on the ZXA10 C300M
and add a tagged or untagged user port to the service VLAN. Table 94 lists the
configuration data for creating the service VLAN.
Table 94 Service VLAN Configuration Data

Item Data
NE type ZXA10 C300M
VLAN ID 100
Service port gei_1/7/1
The following example shows how to add a tagged service port to a VLAN.
Item Data
• The following example shows how to add an untagged service port to a VLAN.
CTRL/Z.
6.10.3 Configuring a User Port
Abstract >>
This procedure describes how to configure the interface mode of a user port.
Steps >>

mode.
2. Run the tpid command to configure the global TPID list.
4. Run the switchport mode command to configure the interface mode.
5. Run the switchport tpid command to configure a TPID.
6. Run the negotiation command to configure the adaption mode of the
port.
Example >>
The following example shows how to set the interface mode of an upstream port to
"hybrid", TPID to "0x9999", and adaption mode to "auto":
ZXAN(config)#tpid outer 0x9999,0x8100 inner 0x8100
ZXAN(config-if)#switchport mode hybrid
ZXAN(config-if)#switchport tpid 0x9999
6.10.4 Activating a User Port
Abstract >>
A user port must be activated after the LAN service data is configured. This procedure
describes how to activate a user port.
Steps >>

mode.
Example >>
The following example shows how to activate the user port gei_1/7/1 after the LAN
service data is configured:
6.10.5 Configuring LAN Services
Abstract >>
This procedure describes how to configure LAN services, including the interface mode
configuration and user port activation.
Table 95 lists the configuration data of LAN service configuration.
Table 95 LAN Service Configuration Data

Item Data
Slot number of the HDTTU card 7
VLAN ID 100
TPID 0x9999
Steps >>
1. Add the HDTTU card.
ZXAN(config)#add-card slot 7 HDTTU
2. Configure the global TPID list.
ZXAN(config)#tpid outer 0x9999,0x8100 inner 0x8100
3. Enter interface configuration mode.
ZXAN(config-if)#
4. Add the interface to the VLAN.

To Do This
Add the interface in tagged mode ZXAN(config-if)#switchport vlan 100 tag
Add the interface in untagged mode ZXAN(config-if)#switchport default vlan 100
5. Configure the interface mode.
ZXAN(config-if)#switchport mode hybrid
6. Configure the TPID number.
ZXAN(config-if)#switchport tpid 0x9999
7. Set the interface to self-adaptive mode.
8. Enable the interface.
ZXAN(config-if)#end
9. Save the configuration.
ZXAN#write

Learning Materials For ZXA10 C300M and C350M

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Learning Materials For ZXA10 C300M and C350M

Caricato da

Copyright:

Formati disponibili

Learning Materials for ZXA10

1 MSAN Basics .................................................................................................. 1

2 ZXA10 C300M/C350M Introduction .............................................................. 21

3 Hardware Installation ................................................................................... 47

3.9.3 Connecting Signal Cables............................................................................. 121

4 Initial Configuration .................................................................................... 133

5 Basic Data Configuration ........................................................................... 139

6 Basic Service Configuration ...................................................................... 161

1.1 MSAN Introduction

 Functions of cross connection ,multiplexing and transmission

 Irrelevant to service type

 Transmitting the subscriber signaling transparently without any explanation

1.1.1 MSAN Development History

 The first period：Pure voice service and optical fiber transmission.

 The second period－Primary Integration：POTS、ISDN、DDN etc.

 The third period －Broadband and Narrowband integration

 The fourth period

 Smooth evolution to NGN

 Comprehensive evolution to packet network

1.1.2 MSAN Features

Abundant service types

Excellent networking capability

It has a built-in integrated service scheduling system, adopts

The complete range of products support centralized device management and

System design is totally based on carrier-class applications; it provides perfect

It supports smooth evolution to the next-generation IP network to accommodate

It adopts IP  TDM technology and therefore can be upgraded smoothly as MSAG

1.2 Background story of NGN

1.2.1 PSTN network evolution history

2 © 2020ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

manual-switching, the experiencing maching-switching and programmed-switching. As

1.2.1.1 Birth of Telephone

1.2.1.2 From “analog” to “digit”

1.2.1.3 Emergence of “time-switching”

The structure of a switch is an odd number of layers of smaller, simpler subswitches,

A space-division subswitch uses digital multiplexers controlled by a cyclic memory. This

1.2.2 Development of VOIP

4 © 2020ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

1.2.2.1 Phase 1 of the VoIP project: early 1998 to 1 October 1999

Key successes of this phase:

The voice quality was near toll quality.

Gatekeepers worked and vastly simplified routing tables.

Key caveats of Phase 1:

1.2.2.2 Phase 2 of the VoIP Project: 1 October 1999 to 2001

Assisted AARNet Members to connect to the AARNet Voice Service.

1.2.2.3 Phase 3 On-going operation

support; and dimensioning the network to carry the traffic.

Projects that may begin where this project ends are:

Video over IP;

6 © 2020ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

1.3 Basic concepts

1.3.1 Basic concepts of data-communication

1.3.1.1 OSI Model

establishes checkpointing, adjournment, termination, and restart procedures. This layer

Figure 2 OSI Model

8 © 2020ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

Figure 3 OSI Model and its protocols

1.3.1.2 TCP/IP protocol suite

Figure 4 TCP/IP protocol

1.3.1.3 IPv4 Address Introduction

10 © 2020ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

Maximum 255 255 255 255

Binary 11111111 11111111 11111111 11111111